22f3dfe3cb
Fix that a storage upload error would leave behind a stuck-pending ActionMailbox::InboundEmail that could never be processed. The message isn't lost: the SMTP relay sees an HTTP server error and defers message delivery. We just have spurious, non-actionable InboundEmails stuck pending and tripping monitoring. This does still leave behind an unattached ActiveStorage::Blob with no corresponding object on the storage service, but that's less annoying. |
||
---|---|---|
.. | ||
app | ||
bin | ||
config | ||
db/migrate | ||
lib | ||
test | ||
.gitignore | ||
actionmailbox.gemspec | ||
CHANGELOG.md | ||
MIT-LICENSE | ||
Rakefile | ||
README.md |
Action Mailbox
Action Mailbox routes incoming emails to controller-like mailboxes for processing in Rails. It ships with ingresses for Mailgun, Mandrill, Postmark, and SendGrid. You can also handle inbound mails directly via the built-in Exim, Postfix, and Qmail ingresses.
The inbound emails are turned into InboundEmail
records using Active Record and feature lifecycle tracking, storage of the original email on cloud storage via Active Storage, and responsible data handling with on-by-default incineration.
These inbound emails are routed asynchronously using Active Job to one or several dedicated mailboxes, which are capable of interacting directly with the rest of your domain model.
You can read more about Action Mailbox in the Action Mailbox Basics guide.
License
Action Mailbox is released under the MIT License.