Alias Reply Headers Corrupting Address Books

We have aliases set up such as sales@example.com and support@example.com. The issue occurs with email client contact management and reply handling:

Initial Scenario:

1. Customer emails support@example.com
2. Agent3 responds
3. The client’s email system now associates “Agent3” as the display name for support@example.com
4. Subsequently, when users try to email Agent3, their email clients auto-complete to support@example.com instead of Agent3@example.com

This creates significant problems, especially with distribution lists. For example:

• We have flash@example.com that goes to all team members
• If CEO_Name@example.com replies to a flash email, their display name gets associated with flash@example.com for every recipients contact list
• Future attempts to email the president will often get misdirected to flash@example.com due to email client contact auto-completion

This issue has been reported multiple times in tickets and community posts. The only current workarounds appear to be:

1. Building a custom fork
2. Abandoning aliases in favor of shared mailbox logins

The core issue could be resolved by adding configurable display names for outbound alias emails. This seems like a crucial feature for any organization using aliases.

If there’s a better solution I’ve overlooked or if my understanding is incorrect, please let me know.