- What does the djurovicigoor/postmark-bounced-email-blocker package do?
- It is a Laravel package that keeps track of email addresses Postmark has reported as bounced or marked as spam, and gives your application a way to check those addresses before sending. The goal is to stop undeliverable recipients from being emailed again, which protects your sender reputation and avoids wasted sends. It works by syncing bounce data from Postmark webhooks into your application.
- How do I install postmark-bounced-email-blocker with Composer?
- Install it as a dev or production dependency with composer require djurovicigoor/postmark-bounced-email-blocker. Like most Laravel packages it should be discovered automatically through package discovery. After installing, check the repository README for any publish and migrate commands you need to run so the package's configuration and storage are set up in your app.
- How does the package receive bounce data from Postmark?
- It syncs bounce information through Postmark webhooks, so you register a webhook in your Postmark server settings that points at the endpoint the package exposes. Postmark then delivers bounce and spam complaint events to your Laravel application, where they are recorded. Make sure the webhook URL is publicly reachable and excluded from CSRF protection, since Postmark posts to it from outside your app.
- Does it block addresses that marked email as spam, or only hard bounces?
- The package is designed to handle addresses Postmark has reported as bounced as well as those that marked your email as spam. Both signals indicate a recipient you should stop mailing, so blocking them helps keep your sending reputation healthy. Check the package source or README for the exact event types it records.
- Which Laravel and PHP versions are supported?
- Support depends on the version constraints declared in the package's composer.json, so check those before installing. Running composer require will tell you quickly whether your Laravel and PHP versions satisfy the requirements. If you are on an older Laravel release, verify compatibility first or look for a tagged version that matches.
- How do I check whether an email address is blocked before sending?
- The package provides checks you can call with a recipient address so your code can decide whether to skip the send. Typical integration points are inside a Mailable's build method, a notification channel, or a validation rule on any form that collects email addresses. Consult the README for the exact class or facade name and method signature to use.
- Where does the package store bounced email addresses?
- Bounce and complaint records are persisted in your application's database, which means you need to run the package migrations after installing. Publishing the package assets lets you review the migration and configuration before applying them. Keeping this data locally also means your checks do not require a live call to Postmark on every send.
- Can I use it with queued mailables and notifications?
- Yes, the blocking check runs in your application code, so it works the same whether mail is sent immediately or queued. For queued mailables, perform the check as close to the actual send as possible, since an address could bounce between the time a job is dispatched and when it runs. Notifications that send mail can be filtered the same way.
- Does it work with mail providers other than Postmark?
- It is built around Postmark webhook payloads and Postmark's bounce and spam complaint reporting, so it is not a drop-in solution for other providers. If you use a different transactional email service, you would need to adapt the ingestion side or look for a provider-specific alternative. The blocking lookup itself is provider agnostic once the data is in your database.
- How should I test bounce blocking in my Laravel application?
- Write feature tests that post sample Postmark webhook payloads to the package endpoint and then assert the address is reported as blocked. From there, test that your mailables or notifications skip sending for blocked recipients, for example with Mail::fake or Notification::fake. Keeping fixture payloads for bounce and spam events makes these tests fast and repeatable.