- Can I use mlpz/postmark-bundle in a Laravel application?
- No. It is a Symfony bundle built around Symfony's kernel, dependency injection container, and services.yml configuration, and it ships no service provider, facade, or package auto-discovery. Its reusable core is a thin wrapper tied to Symfony 2.x Mailer/SwiftMailer abstractions, so the estimated reusable code for a Laravel target is near zero. For Laravel you want a native mail transport, not a bundle adapter.
- Is mlpz/postmark-bundle still maintained?
- No. The repository is archived and has been unmaintained since 2013-09-12, which means read-only issues and no incoming pull requests. There is no security patching, no CVE feed, and no issue triage. Zero public dependents also means nobody is exercising this code in public, so no de facto regression coverage exists.
- Does mlpz/postmark-bundle support PHP 8?
- Assume it is broken until proven otherwise. The code targets Symfony 2.0 through 2.3 and PHP 5.3/5.4, predating short array syntax, scalar type hints, and PSR-4. Composer constraints will almost certainly refuse to install on PHP 8.1, 8.2, or 8.3, and forcing --ignore-platform-reqs only replaces an install error with a fatal runtime error later.
- How do I install mlpz/postmark-bundle and what are its Composer constraints?
- The nominal command would be composer require mlpz/postmark-bundle, but installing it is not advisable. The package targets PHP 5.3/5.4 and Symfony 2.0-2.3, so modern Composer will reject it on current PHP versions. Note also that the mlpz vendor namespace does not match the miguel250 repository owner, which is a supply-chain signal to verify before any install.
- What is the best way to send Postmark email from Laravel?
- Use Postmark's maintained SDK, wildbit/postmark-php, behind Laravel's Mail transport contract, or adopt a maintained community Laravel Postmark transport. Implement the transport against /email and /email/batch, plus the templates API if your product needs it. The bundle is not a viable option because it is a Symfony bundle with no Laravel integration points.
- Does mlpz/postmark-bundle support Postmark message streams, templates, and batch sending?
- No, not in any reliable way. The bundle predates Postmark's message streams, templates API, batch endpoint, and the current account-versus-server token model. Any endpoint shapes it assumes are likely stale, so treat its request and response handling as a historical reference rather than a specification.
- How much code can I reuse from mlpz/postmark-bundle in a Laravel project?
- Near zero. The only reusable part is a thin wrapper around Postmark's /email endpoint, and it is entangled with Symfony's Mailer and SwiftMailer abstractions from the Symfony 2.x era. Writing fresh transport code is roughly 100 to 150 lines and a one-to-two-day task, which also eliminates the vendor dependency entirely.
- Is the mlpz/postmark-bundle vendor namespace a supply-chain risk?
- It is worth treating as one. The package is named mlpz/postmark-bundle but lives under the miguel250 GitHub account, and the mlpz namespace has been abandoned since 2013. An abandoned Packagist namespace can be reclaimed, so verify ownership before any install. Pinning to a commit hash does not resolve the underlying abandonment.
- What should I use instead of mlpz/postmark-bundle on Symfony?
- Use symfony/postmark-mailer, the officially maintained bridge, which makes this bundle redundant by definition. For direct API access you can also use wildbit/postmark-php without the bundle wrapper. Either choice removes the unmaintained dependency and gives you current Postmark API coverage.
- How do I migrate off mlpz/postmark-bundle and test the replacement?
- Do not migrate the bundle in; treat it as a specification document, read its request and response handling, then write a small transport against the current Postmark HTTP API. Add the operational surface the bundle never had, including retry and backoff, idempotency keys, structured logging, and a webhook receiver for bounces and inbound mail. Verify compatibility in an isolated container with real Composer constraints, confirm sandbox sending with a server token, message stream, and sender signatures, then archive any internal dependency on the bundle's interfaces.