Listing
Last updated
Last updated
The default rules will handle most cases so you should not have to add any other rule.
If the regex matches the message, AcyMailing will execute the corresponding actions (on the detected user and on the e-mail) and then will handle the next message. If the regex does not match the e-mail, AcyMailing will try to execute the next rule. The final rule is only executed if none of the previous rules can be applied to the message.
Not all the rules are shown on this screenshot, here are the default rules in AcyMailing:
Action required: It will be executed on messages which require an action from you. This kind of message will be manually handled so you should forward them to a webmaster and handle them one by one. This rule will handle all "click here to confirm you're a human" automatic answers or "reply to this Newsletter and leave the subject intact".
List-Unsubscribe handling: AcyMailing can add a "List-Unsubscribe" header to the sent emails to let your users unsubscribe easily and avoid you to be considered as a spammer. This sends a "Please unsubscribe user ID xxx" email to you. This bounce rule will automatically handle this kind of email so you don't have to unsubscribe users manually.
Acknowledge of receipt - in subject: It will delete notification messages such as "I'm on vacation" or "thank you for your message" on the subject line. We just want to ignore these ones.
Feedback loop - in body: will handle the previous rule, when the message is located in the body of the bounce email.
Mailbox Full: will handle messages not delivered because the receiver had his mailbox full. We don't want to immediately block that user so by default AcyMailing will wait 3 soft bounce messages before executing an action on that subscriber.
Blocked by Google Groups: handles bounces caused by Google groups blocking
Mailbox does not exist 1: handles bounce messages indicating that the mailbox could not be reached because it does not exist.
Message blocked by recipient filters: handles messages which could not be delivered because your message has been blocked by a filter. By default Acy will forward you these messages so you can investigate the issue.
Mailbox does not exist 2: handles bounce messages indicating the mailbox could not be reached because it does not exist. Both rules are necessary to cover most bounce messages of this type.
Domain does not exist: handles bounce messages indicating the mailbox could not be reached because the domain name does not exist. The mailbox or receiver domain does not exist so we want to immediately block the user to not contact him any more.
Temporary failures: handles other soft bounces such as mailbox temporary unavailable. By default AcyMailing will only execute an action on the subscriber if it receives at least 3 soft bounces from this user.
Failed permanently: handles what we call "hard bounces". This rule will handle messages we could not catch with the previous Mailbox does not existand Domain does not exist rules.
Acknowledgement of receipt - in body: will delete notification messages such as "thank you for contacting us..." if it's included in the body of the bounce email. The first Acknowledge or receipt - in subject rule will only be detected based on the subject line compared to that one which checks the body.
The Final rule will be executed in case of the message didn't match any of the previous rules. By default we redirect this kind of message to your e-mail address so you may handle it manually or improve the rules so next time it will be handled automatically.
You can modify all our default rules, re-order them, add new ones, delete them... but you don't have to!
By default, users with wrong e-mail addresses will be blocked from AcyMailing but their subscription won't change. That's perfect so you can see who bounced (and unblock it if necessary) and you will still keep track of its old subscription even if he won't receive e-mails any more as he's blocked.
You can either launch the bounce handling manually or use your cron task to automatically trigger it.
Configure your bounce system on the configuration page, tab "Bounce handling".
Then, test your configuration by clicking on the "Run bounce handling" button, AcyMailing will try to connect to your mailbox and return the actual number of messages in your mailbox.
If you don't have any error and you have some e-mails in your mailbox, then AcyMailing will display a message to trigger the real bounce handling.
Now that you've successfully tested the whole process, you can tell AcyMailing to do the job automatically using your cron task.
Turn on the option Enable the automatic bounce handling option then configure the frequency used to connect to your mailbox. Connecting to your mailbox to handle messages can take some time. We don't recommend you to do it too often (once a day should be enough)
The process is simple:
AcyMailing sends a Newsletter to a wrong e-mail address
A bounce message is returned by the recipient server (between 10 minutes and 7 days, depending on the server) saying the e-mail address we try to reach does not exist
AcyMailing reads this bounce message in your mailbox and applies an action on your subscriber (block him, unsubscribe him, delete him...)
You should test each step to make sure it's working as it should and identify the problem if there is one:
Via AcyMailing, send a test campaign to a non-existing e-mail address (via the Test tab)
You should receive a bounce message on your bounce mailbox... Did you? If not, please check the bounce e-mail address used.
Once you see that bounce message in your bounce mailbox, Acy will be able to handle it. Go on the AcyMailing bounce handling and click on the button "run bounce handling" to make sure it does.
Feedback loop: It will handle .
