Verizon blocking port 465 to godaddy?
-
I have a client that is using godaddy email for their domain. A couple weeks ago, all the office computers lost the ability to send email. They are using Outlook 2013/2016 They tried calling Verizon and GoDaddy. Support on each side basically did all the usual setting changes:
port 465 SSL
port 587 TLS
And then pointed the finger at the other end.We tried disabling the firewall and AV on the client, and lowering the firewall settings on the Verizon router.
One of the computers is a laptop and the owner can take it home (She has Verizon FIOS at home as well.) and it works there. She comes in to the office and it doesn't work.
I tried to use putty to telnet to smtpout.secureserver.net port 465 and got the error: Network error: Software caused the connection abort
I then tried it on my system since I had never tried to telnet to 465 before and got the same error, so that test didn't tell me anything.I can ping smtpout.secureserver.net
Can anyone suggest a test that I can do to narrow down where 465 is being blocked?
-
In one spot, I got the error:
0x800CCC1A: server does not support the connection encryption typeand it seems that this was related to older versions of outlook. I would suspect an older version being installed was tripping it up, but then I go back to the fact that it works when she takes her laptop home.
-
Try different router, the one Verizon gives you is low grade consumer junk. It does look like Verizon is doing something with that port since your user can access it outside of your network. It could be Godaddy as well, they run Cpanel I think, there are some filters there that can block certain traffic based on whatever triggers the filters. Perhaps someone got infected and was sending too much spam and now they filter that ip address?
Call both companies and threaten to close the checkbook if this is not resolved promptly - give them 24h, then start shopping. Both Verizon and Godaddy are scumbags, so really no reason to stick with them.
-
You can always work around this with an SMTP relay as well, in a pinch.
-
I found out that two weeks ago Verizon turned off their smtp relay, which is what set this whole thing in to motion.
-
@Mike-Davis said in Verizon blocking port 465 to godaddy?:
I found out that two weeks ago Verizon turned off their smtp relay, which is what set this whole thing in to motion.
Why would they want to be releasing their outbound email through a third-party in the first place? That is just crazy.
-
Verizon has always been funky with e-mail.
I think they just started supporting IMAP a little bit ago. (If they even do yet.)
-
@BRRABill said in Verizon blocking port 465 to godaddy?:
Verizon has always been funky with e-mail.
I think they just started supporting IMAP a little bit ago. (If they even do yet.)
But we're not talking about Verizon email it email from Go Daddy just Verizon is the carrier and should have nothing to do with anything
-
@JaredBusch said in Verizon blocking port 465 to godaddy?:
@BRRABill said in Verizon blocking port 465 to godaddy?:
Verizon has always been funky with e-mail.
I think they just started supporting IMAP a little bit ago. (If they even do yet.)
But we're not talking about Verizon email it email from Go Daddy just Verizon is the carrier and should have nothing to do with anything
They do all sorts of nutty stuff.
We use them for our corporate Internet, and it took me a few days to realize they monkey with the DNS servers they provide you. Because they return "search" results with them.
They have alternative DNS servers that funtion more like proper DNS server that have to be used. (.12 vs .14)
Anyway. my point is that Verizon does all sorts of weird stuff.
-
@BRRABill said in Verizon blocking port 465 to godaddy?:
@JaredBusch said in Verizon blocking port 465 to godaddy?:
@BRRABill said in Verizon blocking port 465 to godaddy?:
Verizon has always been funky with e-mail.
I think they just started supporting IMAP a little bit ago. (If they even do yet.)
But we're not talking about Verizon email it email from Go Daddy just Verizon is the carrier and should have nothing to do with anything
They do all sorts of nutty stuff.
We use them for our corporate Internet, and it took me a few days to realize they monkey with the DNS servers they provide you. Because they return "search" results with them.
They have alternative DNS servers that funtion more like proper DNS server that have to be used. (.12 vs .14)
Anyway. my point is that Verizon does all sorts of weird stuff.
Again that's nothing to do with being at Stephen and less you choose to use theirs. They are the carrier and if you're not using their service for a certain thing and it should not be affecting anything and actually probably certain it is not in this case. If you don't use their DNS he certainly would not have any of those issues that you had
-
@BRRABill Does Verizon require you to relay email through their proxy? That would majorly suck if they did.
Sounds like they are screwing with DNS. I know Cox does the same thing, at least on the consumer side. If their DNS server can't find an answer, it returns the IP of their failure page website instead of an IP not found message.
I avoid ISP DNS servers most times. Much prefer to use Google or others.
-
@Dashrender said in Verizon blocking port 465 to godaddy?:
@BRRABill Does Verizon require you to relay email through their proxy? That would majorly suck if they did.
Sounds like they are screwing with DNS. I know Cox does the same thing, at least on the consumer side. If their DNS server can't find an answer, it returns the IP of their failure page website instead of an IP not found message.
I avoid ISP DNS servers most times. Much prefer to use Google or others.
Not through the business side of things.
And the DNS is fixable if you use a different set of DNS servers.
I'm not saying anything other than Verzion does some screwy things, so you never know what they are doing on their end.
-
@BRRABill said in Verizon blocking port 465 to godaddy?:
@Dashrender said in Verizon blocking port 465 to godaddy?:
@BRRABill Does Verizon require you to relay email through their proxy? That would majorly suck if they did.
Sounds like they are screwing with DNS. I know Cox does the same thing, at least on the consumer side. If their DNS server can't find an answer, it returns the IP of their failure page website instead of an IP not found message.
I avoid ISP DNS servers most times. Much prefer to use Google or others.
Not through the business side of things.
And the DNS is fixable if you use a different set of DNS servers.
I'm not saying anything other than Verzion does some screwy things, so you never know what they are doing on their end.
This is all distracting from the question at hand with irrelevant information.
How to test telnetting our on port 465.
-
I profusely apologize to all for possibly adding any information that doesn't belong in this thread.
I know ML is built on the philosophy of keeping threads real short and tight, and never deviating from the original post, so again I apologize to anyone I offended with my three sentences.
Well, 5 now with these additional 2 sentences.
Oh no, it's now 6 ... 777 ARGH!!!!!!!!!!
-
@Mike-Davis said in Verizon blocking port 465 to godaddy?:
I found out that two weeks ago Verizon turned off their smtp relay, which is what set this whole thing in to motion.
Do I understand this correctly -
The old way it worked was - your email client while at your location would connect to Verizon's SMTP relay, which would then send your emails onto GoDaddy's email servers, which would then send out your email?
(it's also possible that your email client, while at your location, would connect to Verizon's SMTP relay and deliver the email direct to the end recipients server).
Did you have to enter Verizon's SMTP into the settings? Or was Verizon simply intercepting all outbound SMTP traffic and routing it forcefully through their own servers? -
But - really, as JB would say.
FFS - who cares, because SMTP is not used on port 465 normally, so Verizon's use of a SMTP gateway shouldn't affect 465 traffic.
-
@Mike-Davis said in Verizon blocking port 465 to godaddy?:
Can anyone suggest a test that I can do to narrow down where 465 is being blocked?
Looks like
openssl s_client -connect localhost:465Should get you a connection. If the cert appears to be from someone other than your email provider (i.e. Godaddy) then it's a good bet that that is where your issue is.
If you don't have a linux box to run this from, you can install bash on Windows 10 and run the command, worked fine for me.
I found the info over here http://serverfault.com/questions/64411/whats-the-best-way-to-check-if-an-smtp-server-is-ssl-enabled-or-not
-
@BRRABill said in Verizon blocking port 465 to godaddy?:
I profusely apologize to all for possibly adding any information that doesn't belong in this thread.
I know ML is built on the philosophy of keeping threads real short and tight, and never deviating from the original post, so again I apologize to anyone I offended with my three sentences.
Well, 5 now with these additional 2 sentences.
Oh no, it's now 6 ... 777 ARGH!!!!!!!!!!
A flowing discussion is fine, but at some point you need to get back to the question at hand or reply as a new thread and make your own topic. Additionally my opinion on where that line should be is significantly different than @scottalanmiller's.
I got stuck on a bunch of calls, but it looks like @Dashrender found the solution.
-
@JaredBusch said in Verizon blocking port 465 to godaddy?:
@BRRABill said in Verizon blocking port 465 to godaddy?:
I profusely apologize to all for possibly adding any information that doesn't belong in this thread.
I know ML is built on the philosophy of keeping threads real short and tight, and never deviating from the original post, so again I apologize to anyone I offended with my three sentences.
Well, 5 now with these additional 2 sentences.
Oh no, it's now 6 ... 777 ARGH!!!!!!!!!!
A flowing discussion is fine, but at some point you need to get back to the question at hand or reply as a new thread and make your own topic. Additionally my opinion on where that line should be is significantly different than @scottalanmiller's.
I got stuck on a bunch of calls, but it looks like @Dashrender found the solution.
I find this post distracting and unnecessary.
I kid, Kid.
I also originally read your post as you got stuck on a bunch of cats, which is odd.
-
So I went over there today and swapped out the Verizon Actiontec modem for a Ubiquiti EdgeRouter. Same results. I'm going to try the command that @Dashrender posted.
