Verizon blocking port 465 to godaddy?
-
I'd open a ticket to Verizon and ask.
-
And a ticket to GoDaddy, as well. Lots of relays block port ranges because they are common SPAM host locations.
-
I don't know the first thing about SSL, but I noticed on my openssl session and @Mike-Davis working one, that neither have the message
Loading 'screen' into random state - doneBut @Mike-Davis bad one and @BRRABill working one they both have that. This makes me think Verizon is adding this.
-
@scottalanmiller said in Verizon blocking port 465 to godaddy?:
And a ticket to GoDaddy, as well. Lots of relays block port ranges because they are common SPAM host locations.
What relays though? @Mike-Davis is trying to connect directly to his email service provider. He's not using a relay anymore.
@Mike-Davis mentioned earlier in the thread that Verizon discontinued their relay a little while ago, which is when all these troubles started.
That's one more reason I think this is a Verizon issue. Verizon used to prevent connections to SMTP servers (obviously port 25, but apparently port 465 as well) to non Verizon IPs I'm guessing in the hopes of cutting down on spam leaving their network.
-
@Dashrender said in Verizon blocking port 465 to godaddy?:
@scottalanmiller said in Verizon blocking port 465 to godaddy?:
And a ticket to GoDaddy, as well. Lots of relays block port ranges because they are common SPAM host locations.
What relays though? @Mike-Davis is trying to connect directly to his email service provider. He's not using a relay anymore.
Host, relay... same thing. The MTA.
-
One other question I have is ... do ALL of the clients on the bad network have this issue? Or do some of them work?
From what I have seen from your testing and the testing @Dashrender and I have done, the connection is going through. But the SSL handshake is failing with:
15712:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:./ssl/s23_lib.c:188: -
@BRRABill said in Verizon blocking port 465 to godaddy?:
One other question I have is ... do ALL of the clients on the bad network have this issue? Or do some of them work?
yes, all their outlook clients and iphones are having this issue.
-
@Mike-Davis said in Verizon blocking port 465 to godaddy?:
@BRRABill said in Verizon blocking port 465 to godaddy?:
One other question I have is ... do ALL of the clients on the bad network have this issue? Or do some of them work?
yes, all their outlook clients and iphones are having this issue.
OK.
The reason I asked was that some of the Google responses seemed to get that handshake error when the remote server was blocking due to too many connections. There were also a lot of AV issues, but since it's happening with the phone, that's not the issue.
-
@scottalanmiller said in Verizon blocking port 465 to godaddy?:
@Dashrender said in Verizon blocking port 465 to godaddy?:
@scottalanmiller said in Verizon blocking port 465 to godaddy?:
And a ticket to GoDaddy, as well. Lots of relays block port ranges because they are common SPAM host locations.
What relays though? @Mike-Davis is trying to connect directly to his email service provider. He's not using a relay anymore.
Host, relay... same thing. The MTA.
OK sure - but in this case, @Mike-Davis is trying to connect to the service he paid for - that's all, something the service he paid for is telling him to do.
So unless Verizon is messing with the connection, or GoDaddy (the service provider in his case for email) is blocking @Mike-Davis for some reason, this should just work.
-
@Dashrender said in Verizon blocking port 465 to godaddy?:
@scottalanmiller said in Verizon blocking port 465 to godaddy?:
@Dashrender said in Verizon blocking port 465 to godaddy?:
@scottalanmiller said in Verizon blocking port 465 to godaddy?:
And a ticket to GoDaddy, as well. Lots of relays block port ranges because they are common SPAM host locations.
What relays though? @Mike-Davis is trying to connect directly to his email service provider. He's not using a relay anymore.
Host, relay... same thing. The MTA.
OK sure - but in this case, @Mike-Davis is trying to connect to the service he paid for - that's all, something the service he paid for is telling him to do.
Right, which doesn't change what I said. And there is no easy to know if it is actually a relay or not. In a standard email situation, the system that you connect to is always a relay no matter what because a relay MTA normally sits on the network edge and another MTA is protected behind it. That's why we use the term relay loosely with any MTA that you are hitting, because it will return a relay error either way.
-
@Dashrender said in Verizon blocking port 465 to godaddy?:
And a ticket to GoDaddy, as well. Lots of relays block port ranges because they are common SPAM host locations.
So unless Verizon is messing with the connection, or GoDaddy (the service provider in his case for email) is blocking @Mike-Davis for some reason, this should just work.
Right, so you see why my statement above about GoDaddy's relay probably blocking his IP address makes sense then? You just repeated what I said as if I hadn't said it.
-
@scottalanmiller said in Verizon blocking port 465 to godaddy?:
@Dashrender said in Verizon blocking port 465 to godaddy?:
@scottalanmiller said in Verizon blocking port 465 to godaddy?:
@Dashrender said in Verizon blocking port 465 to godaddy?:
@scottalanmiller said in Verizon blocking port 465 to godaddy?:
And a ticket to GoDaddy, as well. Lots of relays block port ranges because they are common SPAM host locations.
What relays though? @Mike-Davis is trying to connect directly to his email service provider. He's not using a relay anymore.
Host, relay... same thing. The MTA.
OK sure - but in this case, @Mike-Davis is trying to connect to the service he paid for - that's all, something the service he paid for is telling him to do.
Right, which doesn't change what I said. And there is no easy to know if it is actually a relay or not. In a standard email situation, the system that you connect to is always a relay no matter what because a relay MTA normally sits on the network edge and another MTA is protected behind it. That's why we use the term relay loosely with any MTA that you are hitting, because it will return a relay error either way.
OK I agree there -
Question - if it is a relay, would his SSL connection be happening with the relay box or with the internal box that the relay is protecting? If it's with the relay box, then who cares if it's a relay or not, that's not relevant to the problem at hand.
-
@Dashrender said in Verizon blocking port 465 to godaddy?:
Question - if it is a relay, would his SSL connection be happening with the relay box or with the internal box that the relay is protecting? If it's with the relay box, then who cares if it's a relay or not, that's not relevant to the problem at hand.
Hence why in email world we call ANYTHING you connect to somewhere else a relay, whether it is the only system or not. And yes, no matter what, only the relay (external facing MTA) matters for connection, nothing past it matters to you.
-
Are you able to send an email without SSL?
-
@tiagom said in Verizon blocking port 465 to godaddy?:
Are you able to send an email without SSL?
587 with TLS doesn't work either.
-
@Mike-Davis I wasn't clear. What about with encryption set to none and outgoing port using 25, 80 or 3535.
-
@tiagom said in Verizon blocking port 465 to godaddy?:
@Mike-Davis I wasn't clear. What about with encryption set to none and outgoing port using 25, 80 or 3535.
I'm pretty sure I tried all but port 25 while I was on site with Outlook with no success. I tried telnetting to port 80 and 3535 and didn't get a response.
-
@Mike-Davis Sounds like there is a bigger problem then just on port 465.
Do you get any response when you telnet to a port that doesn't require encryption(25, 80 or 3535)?
ie..
220 p3plsmtpa09-03.prod.phx3.secureserver.net :SMTPAUTH: ESMTP -
A recommendation for debugging if you get past the 220 banner.
Capture the communication using wireshark when you attempt to send an email using outlook. Usually its pretty clear what it is unhappy about.
Make sure to set outlook's SMTP encryption settings to "NONE" and use the appropriate ports(25, 80 or 3535 according to the link below) so the traffic is in plain text.
https://www.godaddy.com/help/what-do-i-do-if-i-have-trouble-connecting-to-my-email-account-319
-
Looks like someone's mail server doesnt support the version of ssl/tls you are trying to connect with.
http://www.checktls.com/index.html - i suspect godaddy doesnt support the ssl/tls youre using(if at all), and verizon does. Perhaps they require tls/ssl connections now and if godaddy doesnt support ssl/tls, no mail can be sent between the two.
Had a similar problem at last job; we required tls/ssl for SEC reasons, couldnt send email to hotmail and a few other email providers(wasnt supported by them at the time)
