Exchange server SE issue, single email received mutiple times

Usman 0 Reputation points
2026-08-03T09:28:08.0066667+00:00

hi

we have just upgraded to Exchange Sever SE from Exchange server 2019

we are facing an issue regarding the single email received multiple time for some users. header shows the different Message_ID for email with same subject.

we have recently installed the certificate on WAF and on exchange server.

we have checked the queue and it seems normal.

our queue toolbox was showing some error which is now solved.

any one have faced this issue?

any solution?

i can provide more information if required.

thanks in advance.

Exchange | Exchange Server | Management
Exchange | Exchange Server | Management

The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.

0 comments No comments

1 answer

Sort by: Newest
  1. Kien 980 Reputation points Independent Advisor
    2026-08-03T10:01:36.91+00:00

    Dear @Usman,

    To resolve this, Microsoft’s support team will need to step in. A technical support engineer can perform a remote session to investigate the situation verify the backend configurations and run any necessary synchronization tools to resolve the problem. If the issue requires further attention, they can refer it to a specialized team for deeper analysis.   

    I would recommend raising a support ticket through the Microsoft Engage Center, where support engineers can perform a deeper investigation and help troubleshoot the issue further. Please note that this is a paid ticket.

    In the meantime, kindly review the message logs and the Exchange Server logs for any relevant issue or additional details:

    Compare the message-tracking logs for both Message-ID values. Different Message-ID values usually suggest separate submissions, so identify the first transport event, source, client host, connector, and timestamp for each copy. Message tracking | Microsoft Learn

    Review all relevant transport logs, not only the active queues. Check connectivity, protocol, agent, and message-tracking logs to determine whether the duplicate originated from Exchange, the WAF, an SMTP gateway, or another relay. Transport logs in Exchange Server | Microsoft Learn

    Check connectors and migration routing. Make sure the former Exchange 2019 server and the new Exchange SE server are not both receiving the same SMTP traffic through DNS, load balancing, relay configuration, or application settings. Transport logs in Exchange Server | Microsoft Learn

    Confirm message tracking is enabled on every Exchange server. Also verify the log path, retention period, and maximum directory size so that entries from the affected period are available. Configure message tracking | Microsoft Learn

    As a forum user, I do not have the tools to investigate your specific account directly, as this is a support forum between users. Moderators and collaborators, including external Microsoft employees, may not directly intervene in the functionality of Microsoft products or access internal systems. My role is limited to providing technical guidance on reported problems, requests, or ideas. However, I will do my best to guide you as clearly as possible.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.