locked
My email router problems only get worse. RRS feed

  • Question

  • I'm really having a hard time diagnosing my email router all of a sudden failing. It was working like a charm for 2 weeks. The other day it just stopped working, saying the TLS security was bad. We got it to start working somehow yesterday (not sure what really worked) but now it's back to failing to deliver anything. The funny thing is that I can Load Data in the router and the mailboxes show up. Here's one of the errors I'm seeing in the EVent Viewer:

    System.Net.Mail.SmtpException: Failure sending mail. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host.

    I'm really at a loss and really stressed out as I'm now in my testing stages and need to have this rolled out within the next 2 weeks. I don't need this right now. :(

    Thursday, April 30, 2009 5:36 PM

Answers

  • Hi DevRock,

    This may be something to do with your SMTP email provider. Are you using your exchange server or an external email provider?

    HiH,
    Karlo
    Karlo Swart - http://www.ver206.com
    • Marked as answer by Jim Glass Jr Friday, May 1, 2009 6:23 PM
    Friday, May 1, 2009 6:30 AM

All replies

  • Hi DevRock,

    This may be something to do with your SMTP email provider. Are you using your exchange server or an external email provider?

    HiH,
    Karlo
    Karlo Swart - http://www.ver206.com
    • Marked as answer by Jim Glass Jr Friday, May 1, 2009 6:23 PM
    Friday, May 1, 2009 6:30 AM
  • Internal.

    I got it working again yesterday. Frankly, I'm not sure what the heck worked. I re-did a bunch of configs, etc and it works the way it did originally for 2 weeks. I'm just hoping this is the last time I have to mess around with this. I don't need it to stop working at random when we get this in production.
    Friday, May 1, 2009 2:43 PM
  • So, I'm frustrated yet again. After working for a few days, it just stopped working. Here is the error generated on our Exhange server:

    Microsoft Exchange couldn't find a certificate that contains the domain name ***.***.com in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector *****-CRM1 with a FQDN parameter of ****.****.com. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key

    Now, here's what I'm wondering. Our SSL certificate that is installed on our mail server is NOT the same as the machine's domain name. It's the same as our external OWA DNS name. Could that be the issue?

    Wednesday, May 6, 2009 7:01 PM