It stops sending "new post" notifications to those addresses.It collects bounced emails, counts them and marks user accounts as "do not send email".This helps keep your email from being marked as spam. It stops sending emails to addresses that are no longer valid. It is actually the best way to detect a bounce.This modification has been replaced by the full Bounced Email Handler. Note that current rules will catch almost all possible bounce types looking at the message subject. You can force eMail Bounce Handler to process every incoming mails clicking on the Skip all rules check box. All remaining rules will be discarded.Īll rules can be activated/deactivated individually using their associated check boxes.Īll rules can be activated/deactivated at once clicking on the Activate all rules check box. eMail Bounce Handler allows you to use either parts both for the rule and extraction.Įach rule takes a given message header from Subject, Sender, Body and Recipient, looks if it contains, is equal to, starts with or ends with a given text and finally extract e-mail addresses from the Entire Message, From or To header, all Headers or Message Body.Īn incoming message will be treated as soon as at least one rule is met. Body part contains the message contents themselves. Header contain sender and recipient addresses along with special information. This default set of rules cover 99% of bounce types.Īll internet e-mails are made of 2 parts called Header (or Headers) and Body. You can easily add new ones, modify or delete them. 14 rules are automatically added to that editor at startup. As a result eMail Bounce Handler is able to catch up to 99,9% bounces successfully.Īll that processing is not done on every single message but only on the messages that match at least one of the rules listed in the rule editor. This set was created after processing dozens of thousands bounces in the last years. In case the bounce is not a DSN and doesn't even contain an error code eMail Bounce Handler will then extract the server response and will lookup that response using a set of 60 error tracking and regex based rules. The list of error codes is available in RFC-3463. This code allows the application to find out if the bounce is a hard or a soft bounce (Fatal Error or Warning) and to get an explanation of the error that caused it. Note that 10 out of 9 bounces currently use that format.įor the bounce messages that are not formatted following the DSN standard eMail Bounce Handler lookup the Enhanced Mail System Status Code when available. eMail Bounce Handler includes an advanced parser that is able to extract all the valuable information from the notification and convert the error code into something human readable following error definitions contained in RFC-3463. The Delivery Status Notification specification is explained in RFC-3464. That includes a standard error code, a description and the addresses that cause the error. This format is widely used because it contains valuable information like for example the reason why a message could not be delivered successfully. It is a standard bounce format intended to provide detailed information about a delivery error. EMail Bounce Handler is able to process Delivery Status Notification, also known as DSN.
0 Comments
Leave a Reply. |