Hi community!
One week ago, we installed on a Windows Hyper-V 2012 core server an Exchange 2013 CU1 on a Windows Server 2012 virtual machine. On our LAN, we have a Windows Server 2008 R2 web server, which is sending emails to customers over the Exchange 2013.
To make this relay function on the Exchange 2013 to work, we created an internal frontend relay receive connector. Our experience last week was, that this connector stops working for about 5 to 30 minutes whenever it would like to. The sender web server got"service not available" errors. On a thread in the internet we found the solution to deactivate the Microsoft antispam agent of the Exchange 2013 and replaced it by Symantec Mailsecurity for Exchange 7.0.1.
But today, 12 hours after the installation of the workaround, some smtp messages where not sent (but most of the mails where sent). We found in the relay connectors receive log, that he accepted the failed message for sending (250 2.6.0 <baab5dde-0b49-420f-97ba-907466047b05@servername.domain.lokal> [InternalId=734439407867] Queued mail for delivery), but instead of waiting for the senders QUIT-command, the relay connector raises the error "Remote(SocketError)".
We didn't find any other errors with reference to this behavour.
There is only one thing more: last week we recognized problems with the outlook connections to the new Exchange server. The connection goes on- and offline multiple times in short time intervalls. We switched off the default configured "Receive Side Scaling" on the Windows Server 2012 virtual machines NIC, as suggested on the internet for Exchange 2013, running on hyper-v-hosts. Could this be responsible for the socket errors on SMTP-communication?
Hope my English is good enough to give a good explanation of the problem.
Best regard,
Peter
One week ago, we installed on a Windows Hyper-V 2012 core server an Exchange 2013 CU1 on a Windows Server 2012 virtual machine. On our LAN, we have a Windows Server 2008 R2 web server, which is sending emails to customers over the Exchange 2013.
To make this relay function on the Exchange 2013 to work, we created an internal frontend relay receive connector. Our experience last week was, that this connector stops working for about 5 to 30 minutes whenever it would like to. The sender web server got"service not available" errors. On a thread in the internet we found the solution to deactivate the Microsoft antispam agent of the Exchange 2013 and replaced it by Symantec Mailsecurity for Exchange 7.0.1.
But today, 12 hours after the installation of the workaround, some smtp messages where not sent (but most of the mails where sent). We found in the relay connectors receive log, that he accepted the failed message for sending (250 2.6.0 <baab5dde-0b49-420f-97ba-907466047b05@servername.domain.lokal> [InternalId=734439407867] Queued mail for delivery), but instead of waiting for the senders QUIT-command, the relay connector raises the error "Remote(SocketError)".
We didn't find any other errors with reference to this behavour.
There is only one thing more: last week we recognized problems with the outlook connections to the new Exchange server. The connection goes on- and offline multiple times in short time intervalls. We switched off the default configured "Receive Side Scaling" on the Windows Server 2012 virtual machines NIC, as suggested on the internet for Exchange 2013, running on hyper-v-hosts. Could this be responsible for the socket errors on SMTP-communication?
Hope my English is good enough to give a good explanation of the problem.
Best regard,
Peter