My Mautic version is: 2.16.0
My problem is: I cannot get bounce processing to work, now matter how I configure it.
If Mautic email configuration screen is set to send bounces to firstname.lastname@example.org, then indeed they appear in my bounce email box, but they each appear in a unique folder (presumably named after the reply path created on the outgoing email) and so are ignored by bound management, which can only monitor a set folder.
If I remove this setting, I get no bounce notices at all.
However, if I set the bounce address under email config in Mautic, send a test email to a bogus address, and wait for the bounce to hit my bounce mailbox–then go to email config in Mautic and select the unique folder into which that bounce notice email appears, bounce processing works and Mautic will flag the test account with the bogus email “DO NOT CONTACT” just as it should. So bounce processing works–except there is no way to tell Mautic to monitor all possible inboxes, so it never sees bounce notices, and instead, they just build up in the mailbox.
I use Amazon SES to send mail and have an Amazon SNS topic set up to forward bounce notices via email to the same bounce mailbox (and it’s confirmed), but it has no impact on whether bounces are received and processed. This notification doesn’t appear ever do anything. Clearly, the bounce notices are being delivered via email according to the reply path header set in the outgoing email, not by the Amazon topic–so why does the documentation even tell us to set up the bounce and complain topics?
I tried configuring to use a webhook topic subscription instead, but as many, many, many people have reported over the last couple of years, this doesn’t work either. Amazon sends the confirmation request, but Mautic doesn’t reply, instead logging, a SwiftMail “you have requested an unknown service”.
This is very frustrating. ALL documentation I’ve found for bounce handling is very simple and straightforward–but none mentions the weird “stick each bounce in an inaccessible folder” behavior, and none seems to match the overall behaviour I am seeing in my very simple, straight out of the box installation.
Any light anyone can shed would be greatly appreciated. Thanks.