Decode returned emails is an automatic feature that lets b2evolution to scan the inbox of the Return-Path email account included in the emails sent from the site, and look for messages in order to classify their addresses according their behaviour.
This way, a status value could be automatically assigned or updated to those addresses. That status update is based in the severity of the errors found in the inbox mentioned before. Thus, the administrators could be aware about situations in the messages delivery that go from temporary errors (i.e.: email space quota exceed) to permanent errors (i.e.: inexistent email account).
Settings to decode the returned emails
- Enabled: This feature needs the php_imap extension.
- Retrieval method: Choose a between IMAP or POP3 as method to retrieve the emails.
- Mail Server: Hostname or IP address of your incoming mail server.
- Port Number: Port number of your incoming mail server (Defaults: POP3: 110, IMAP: 143, SSL/TLS: 993).
- Encryption method: None, SSL or TLS.
- Do not validate certificate: Do not validate the certificate from the TLS/SSL server. Check this if you are using a self-signed certificate.
- Account Name: User name for authenticating on your mail server. Usually it is your email address or a part before the @ sign.
- Password: Password for authenticating on your mail server.
- Delete processed emails: Check this if you want processed messages to be deleted from server after successful processing.
- Strings to match in titles to identify return path emails: Any email that has any of these strings in the title will be detected by b2evolution as the returned emails.
- Body Terminator: Starting from any of these strings, everything will be ignored, including these strings.
- Error message decoding configuration: The first letter means one of the following:
- Spam suspicion.
- Permament error.
- Temporary error.
- Configuration error.
- Unknown error (default).
The next string after space is an error text, it is case-insensitive string.
In order to get this feature working properly, you must create a "Process the return path inbox" scheduled job. For more information, please visit: Process the return path inbox
Created by • Last edit by on Oct 02, 2015