resolved FORGED

[epic0000000]

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?

[xshkurti]

To resolve this issue, you have to configure and correctly implement SPF, DKIM, and DMARC for your domain. This is the fundamental solution to email authentication and preventing spoofing.
Second thing is to point out where do you see this and how Fortinet products are implemented in your infrastructure.

This is because the query is very general and we need to know if this is the correct forum to ask the question.
You may need to check with email-server vendor forum for further instructions.
If, on the other hand, you are using FortiMail, then you have to check policies:

1. Check Impersonation Analysis feature if it is configured properly
2. Sender Practices

You can find more info under FortiMail documentation:
Email concepts and process workflow | FortiMail Appliances and Virtual Machines 7.6.3 | Fortinet Doc...