This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
Alright, after more testing, I've determined the issue is with X.com's highest priority MX relay (seluimxhigh.X.com). My domino server tries to connect to seluimxhigh.X.com, but doesn't connect because of an ssl handshake error. The error indicates a bad peer certificate. I've gone over my servers certificate with a fine toothed comb and can find no problems with it. I started to look into X.com's side of things, and it really looks like the problem is on there end.
The certs on all of their relays are self signed, which seems like a bad setup, but isn't what is causing the problem. I needed to be able to test a connection to their relays from a source other than my own. I used CheckTLS.com, which just uses a perl script. You can see in the screenshot below that it fails to connect to seluimxhigh.X.com as well. It manages to connect to all of their other relays, which I can confirm because I am able to telnet to port 25 on them from my server. Since according to X.com, I'm the only domain which can't send mail to them, and because checktls.com also can't connect to seluimxhigh.X.com, I would guess that other mail servers simply send to one of their 5 other relays.
Assuming this is all correct (I could be wrong), then it makes me wonder why my server doesn't just send to one of the other relays after the highest priority one fails.
For those still following
Return to top
. . . . . . . . For those still following (~John Ellusonad... 19.Jul.12) 
