Internal bounce message does not conform to domain settings
Problem reported by CLEBER SAAD - Today at 5:23 AM
Submitted
Hi everyone,

I'd like to know if anyone else has experienced this situation. Bounce messages generated internally by SM are being rejected when trying to be delivered to a Gmail account, for example, because they don't have the DKIM for the domain.

I'll explain what's happening:

- If you try to deliver a message to an account that has a forwarding address to another account that doesn't exist, a bounce will be generated. If the sender is an account from the same domain, the bounce is successfully delivered. If the sender is an external account, the bounce will not be delivered because the DKIM will not be present in the message, for example.

How to test:

1) Create an account like test@yourdomain.com and in the forward address field, enter existingaccount@yourdomain.com and nonexistentaccount@yourdomain.com.

2) Send an external message to test@yourdomain.com. It will be successfully delivered to existingaccount@yourdomain.com and a bounce will be generated when delivering to nonexistentaccount@yourdomain.com.
3) The bounce must be delivered to the sender. In the case of Gmail, if the domain has DKIM, the bounce must also comply. If it does not, the bounce message will be rejected.

Detail: the bounce has the sender as noreply@yourdomain.com (default of the new SM), however when making the delivery, the mail from will be <> and not noreply@yourdomain.com

Using the latest version of SM 9504 in Linux (Windows has the same situation)

Reply to Thread

Enter the verification text