Strange situation: Trying to use an automated web-based scheduling system at a well-known medical provider in the Bay Area, and it doesn't work: can't get any confirmation e-mails from them at my regular e-mail ralph@lr.los-gatos.ca.us (which is hosted by Sonic). Call them on the phone, they look: Their logs show TLS errors (!) sending to that e-mail. To help debug it, I simply change my e-mail system on their servers, to <user>@sonic.net: same problem. Change it to <user>@gmail.com, and everything works. Oops, this seems bad; this would indicate the root cause really is some misconfiguration that's specific to Sonic overall, not just to my domain.
Anyway, that's really weird, because I otherwise my regular e-mail works great, and I haven't heard any complaints from any other senders that they can't get through. Now it gets weirder: The tech support person at that medical provider is able to send e-mails to ralph@lr.los-gatos.ca.us and receive replies, and that works fabulously well. Let me summarize this (and I'm using a fake domain name for the company's name for privacy)
Anyone have a good idea how to debug it? Question for the Sonic tech people watching this: is there a point to opening a trouble ticket with Sonic, and asking them to look at their inbound mail logs to see any failed attempts from @medical.example.com (obviously I'll give you the real name)? Are there even logs of failed inbound attempts?
Obviously, this is not critical or urgent, otherwise I would have opened a trouble ticket right away.
Anyway, that's really weird, because I otherwise my regular e-mail works great, and I haven't heard any complaints from any other senders that they can't get through. Now it gets weirder: The tech support person at that medical provider is able to send e-mails to ralph@lr.los-gatos.ca.us and receive replies, and that works fabulously well. Let me summarize this (and I'm using a fake domain name for the company's name for privacy)
- From <automated>@medical.example.com to ralph@lr.los-gatos.ca.us: BROKEN
- From <automated>@medical.example.com to <user>@sonic.net: BROKEN
- From <automated>@medical.example.com to <user>@gmail.com: works
- From <support>@medical.example.com to ralph@lr.los-gatos.ca.us: works
Anyone have a good idea how to debug it? Question for the Sonic tech people watching this: is there a point to opening a trouble ticket with Sonic, and asking them to look at their inbound mail logs to see any failed attempts from @medical.example.com (obviously I'll give you the real name)? Are there even logs of failed inbound attempts?
Obviously, this is not critical or urgent, otherwise I would have opened a trouble ticket right away.