Can't access verizon.net mail servers over AT&T U-verse Internet connection
Posted on 2014-09-23
Stumped today at a client site, a home office with several different devices including Mac OS, Windows, iPhone, etc. I was called in to troubleshoot a POP3 connectivity issue accessing verizon.net mail servers over AT&T U-verse ISP connection. No problem accessing web mail, and ALL of the POP clients stopped working at the same time last Thursday. On his phones, he can access the email accounts over the cell network, but as soon as he gets on his Wi-Fi he loses email connectivity.
This client is paying Verizon for a mydomain account to keep his Verizon.net email addresses even though he is no longer a Verizon customer since moving away from his beloved FIOS connection. The mydomain tech support people confirmed that the client's mydomain account with Verizon was active and in good standing.
From there we connected with Verizon general tech support to verify POP3/SMTP settings. We had the correct settings. This tech went a step further and did some port testing for us and it was his determination that the traffic to the verizon.net mail servers was being blocked on the AT&T network. On to AT&T tech support. The level 1 tech did a thorough job of checking things out for us and could not find any issues. From there she referred us to AT&T Connect Tech to troubleshoot further. This group insisted that their services were available with prepayment only regardless of where they found the problem to be. This put the customer over the edge (putting it mildly :-), so we didn’t stay with that call too long. My final test was to connect one of client's laptops to my T-Mobile cell phone hot spot. Once I did that, email from verizon.net came pouring in, proving to me that the problem is on the AT&T network.
We could not get any resolution from the techs we talked to, so that's where I had to leave it. I did some reading in the Verizon user groups and it appears others have had similar issues but it's not clear how or if they were resolved. Any ideas on what's going on would be appreciated and particularly how to get past the issue.