Weave Code
Laravel Mailcoach Ses Setup Laravel Package
spatie/laravel-mailcoach-ses-setup
Prepares and configures Amazon SES accounts for use with Mailcoach, enabling proper setup for email campaign sending and feedback handling (bounces/complaints). Intended for internal Mailcoach use; minimal documentation or support provided.
[READ ONLY] Setup SES for use with Mailcoach
Frequently asked questions about Laravel Mailcoach Ses Setup
- How do I set up Amazon SES feedback loops for Mailcoach in Laravel?
- First, ensure SES is configured in AWS with verified domains/ips and SNS topics for bounce/complaint notifications. Then install the package via Composer, publish its config, and update your `.env` with SES/SNS credentials. Finally, configure the SNS topic ARNs in `config/mailcoach-ses-setup.php` and run queue workers to process feedback.
- Does this package work with Laravel 10?
- The package is compatible with Laravel 9 and 10, but verify your Mailcoach version (last updated in 2023) supports these Laravel releases. Check Mailcoach’s docs for version-specific requirements, as this package extends its functionality.
- What AWS permissions are required for SES feedback processing?
- You need IAM roles with `ses:Receive` permissions and `sns:Publish` access. The package assumes SES and SNS are pre-configured with topics subscribed to SES notifications (bounces/complaints). Use policies like `AmazonSESFullAccess` and `AmazonSNSFullAccess` for testing, then restrict in production.
- Can I use this package without Mailcoach?
- No, this package is a Mailcoach extension and requires Mailcoach to be installed in your Laravel app. It’s designed to handle SES feedback specifically for Mailcoach’s email campaigns, not standalone SES integration.
- How do I test if SES feedback is being processed correctly?
- Send test emails via Mailcoach to known bounce addresses (e.g., `bounce@example.com`) or use AWS’s SES sandbox to simulate complaints. Check Mailcoach’s logs or database for processed feedback events. Monitor queue workers for errors during processing.
- What happens if SNS notifications fail to reach Laravel?
- Configure a dead-letter queue (DLQ) in AWS SNS to capture failed notifications. The package relies on queue workers to process SNS messages, so ensure your Laravel queues (e.g., SQS, Redis) are running and scaled to handle feedback volume. Monitor DLQs for undelivered messages.
- Are there alternatives to this package for SES feedback in Laravel?
- For Mailcoach users, this is the official package. For generic SES feedback handling, consider AWS’s native SDK or third-party tools like Postmark or Mailgun, which offer built-in bounce/complaint processing. However, these won’t integrate with Mailcoach’s campaign system.
- How do I handle DKIM/SPF setup for SES with this package?
- This package focuses solely on SES feedback loops (bounces/complaints) and doesn’t manage DKIM/SPF records. Configure these in AWS SES under your domain’s email authentication settings. Use tools like MXToolbox to verify your records before sending campaigns.
- Will this package break if Mailcoach updates its API?
- There’s a risk of compatibility issues if Mailcoach changes its internal event listeners or queue job structures, as this package tightly couples with them. Monitor Mailcoach’s changelog and test updates in a staging environment before deploying to production.
- How do I monitor SES feedback processing failures in production?
- Set up Laravel’s queue failure channels (e.g., database or SQS DLQ) to log failed jobs. Use tools like Laravel Horizon or AWS CloudWatch to track SNS delivery errors and queue worker crashes. Implement alerts for critical failures via services like PagerDuty or Slack.
Weaver
How can I help you explore Laravel packages today?