resolved FORGED
We use a common email address (e.g., no-reply@mydomain.com) to send emails from various systems. To distinguish between services, we dynamically change the display name—such as:
MYDOMAIN Payroll no-reply@mydomain.com
MYDOMAIN Marketing no-reply@mydomain.com
MYDOMAIN Invoicing no-reply@mydomain.com
However, these emails are being resolved as forged. This issue arises because the inconsistent display names triggers anti-spoofing/anti-spam checks, especially when combined with a shared sender address.
How can we prevent this issue and ensure reliable delivery of these emails across systems?
