This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have on-premise Exchange deployment with EDGE server delivering email. The IPv6 has been disabled all along via Registry key. More and more local small companies are implementing IPv6 addressing and for some reason my EDGE server is trying o connect via IPv6 and can't, email goes to queue and sits there. If I tried to Retry email from the queue it get delivered via IPv4. Why is this happening?
Hi @Mr Mind ,
Have you checked the settings on the Connectors of Edge?
Also are you using the MX record or Smart host to route?
You can use the following command to check the IPAddress in using by your Edge send connector.
Get-SendConnector -Identity "EdgeSendConnectorName" | FL Name,SourceIPAddress
Regards,
Lou
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Yes, it is set to use MX record.
SourceIPAddress : 0.0.0.0
Hi @Mr Mind ,
Sorry for the delay of this reply.
Please first make sure you have disabled the IPv6 correctly: Use registry key to configure IPv6
Are there any error messages(NDR) after the emails stuck in queue?
In EMS run Get-Queue to check the queue.
And also you can enable the protocol log on the Edge send connector: EdgeSync - Default-First-Site-Name to Internet.
After sending the message, you could find the logs on the Edge server C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\Edge\ProtocolLog\SmtpSend
Best regards,
Zhengqi Lou
Yes, I see many emails stuck in the queue, many with IPv6 as destination. I see in teh logs that EDGE server with properly disabled IPv6 still tries to connect to IPv6 address. Once I retry the message in the queue it actually connects to IPv4 of that receiver address.
BTW, I have IPv6 enabled on HUB servers. I'm thinking that sine HUB server has IPv6 enabled it gets IPv6 from DNS and tries to deliver email via EDGE. It can connect and email get stuck in the queue, once I retry on EDGE, EDGE server checks DNS, and since it does not have IPv6 enabled, it sees IPv4 of recipient server and successfully delivers emails.
Hi @Mr Mind ,
Oh, you mean you're using Exchange 2010 right? Based on my knowledge, one of the function of the Hub transport server is to route e-mails sent from the internal organization to inside or outside. So you may consider to disable IPv6 on HUB server either to stop it.
Regards,
Lou
Exchange 2016.
Hi @Mr Mind ,
Based on my knowledge, there is no Hub Transport server in Exchange 2016, there are only Mailbox and Edge servers.
I may guess the IPv6 is enabled on your Mailbox server and disabled on your Edge server that causes this issue.
Regards,
Lou
Hi @Mr Mind ,
It has been a long time since last reply, did these suggestions help you? If the above suggestion helps, please click “Accept as answer” to mark helpful reply as an answer.Your action would be helpful to other users who encounter the same issue and read this thread.
Regards,
Lou
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Sign in to comment