Site Totals

61162 Questions Answered 267 Categories

outgoing mail unable to connect to server

After solving the problem of receiving mail, I now am getting the same error message in trying to send email: cannot safely coect to server.

Using Samsung Android email app thats with the phone. Can send email through AOL and Mac Mail on home computer no problem.

Any suggestions?

Comments

ChipChairman1

My wife and were having the same problem.

I used this to reconfigure my outlook profile.

https://help.aol.com/articles/verizon-move-to-aol-mail-setting-up-your-new-aol-account-in-a-third-party-email-program-or-mobile-device-imap

kaleidic

I use Thunderbird to access my email. Until yesterday afternoon, everything was OK then the smtp.verizon.net server started timing out and I can not send emails. The pop server for incoming messages is fine. I went over it and over it with AOL on twitter and then they sent me a phone number to call, and they persist in claiming that there is no problem. Thunderbird error message is failure due to timing out. Telnet and ping show the same.

C:\Users\Jason>telnet smtp.verizon.net 465
Connecting To smtp.verizon.net...Could not open connection to the host, on port 465: Connect failed

C:\Users\Jason>ping smtp.verizon.net

Pinging smtp-verizonmail.egslb.aol.com [64.12.88.168] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 64.12.88.168:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

CRobGauth

Verizon has moved email to AOL servers.

Google FiOS AOL email for details.

kaleidic

I know that, that's who gave me the runaround and who want me to pay for support.

CRobGauth

Post here for better community support:

https://forums.verizon.com/t5/Verizon-net-Email/bd-p/emailissues

perryg1

Verizon send email stopped workin 3/1/18. Was using smtp.verizon.net. Any ideas why?

grybo1960

Same thing happened to me.

The outgoing mail server appears to have changed to smtp.aol.com. The new address for the Pop3 server is pop.aol.com, though pop.verizon.net is still working for the time being.

paulsidcup

I kept my verizon email address after transition to AOL. Incoming mail works well now. Outgoing mail worked well until 02/02/2018 when I started getting a message "The message could not be sent because the connection to Outgoing server (SMTP) smtp.verizon.net timed out. Try again." My settings are Server name: smtp.verizon.net ; Port: 365 ; Connection Security: SSL/TLS ; Authentication Method: Normal Password. I have tried Port 587 and STARTTLS; and Encrypted Password. Nothing works.

Decusgeek1

Okay, so I see that smtp.verizon.net stopped working around 3/1/18 and that the new SMTP server is supposed to be smtp.aol.com. Unfortunately neither one responds to a ping comand. Why not and what now?

Ray310

I had the same problem. I added @verizon.net to the end of my user name and outgoing started working again using the old settings.

Decusgeek1

OK, I changed both and it still had problems. I went back into the program, re-entered everything, now it works. I still don't know why nothing pings. Oh well, thanks.

Allen110

Hello,

I am having problems with receiving emails. I am using Microsoft Outlook Pro Plus 2010 with the outgoing settings of SMTP port 465 SSL, which did work good for quit a while since the Verizon to AOL transition. Then the last couple of months I started have problems receiving emails and get a pop-up window message with the following Error:

The Server that you are connected to is using a security certificate that cannot be verified. The target principle name is incorrect. (View Certificate) Do you want to continue using this Server ? Yes or No.

I looked at and Viewed the Certificate and is from: Baltimore Cyber Trust Root that is valid from: 5/12/2000 to 5/12/2025.

This Certificate is issued to: outgoing.verizon.net.
This Certificate is issued by: Verizon Public SureServer CA G14-SHA2
Valid from: 1/10/2018 to 1/10/2020
Certificate Information says that: All the Intended purposes of this Certificate could not be verified.

Hopefully someone can figure out what to do with the above Certificate. Maybe the Details of the Certificate need changed because of the Verizon/AOL transition ?

I also tried a different version of Microsoft outlook, and had exactly the same problem.

Anyone have any Idea's ?

Thanks,

DW57

I came here to see if anyone else was having this problem. I use Windows Live Mail 2012, and I sometimes use the AOL web-based mail... but mostly WLM. My outgoing mail was working fine until I tried to send an email this morning. It stayed in the Outbox. I googled the issue and found a suggestion to change the number in the smtp settings from 465 to 587. I tried it and it worked.

FedUpBoston

Just saying - the link you provided was apparently only for IMAP connection, not POP/SMTP

FedUpBoston

No offense, CRobGauth, but the changeover to AOL happened, like, a year ago. It is only in the last week that smtp.verizon.net has become unreliable or completely dead. This is either a failure to attend to business on Verizon's part, or a failure to inform customers that they must once again change their SMTP configuration.

FedUpBoston

In my case, first of all I've made no email configuration changes on either of my devices, in many months. So IMAO this is Verizon's fault. Thank you other posters for mentioning possible fixes. Unfortunately in my case I'll have to endure nearly endless waiting on hold with tech support. On my Win 7 PC every Send attempt fails. Appending '@verizon.net' in my Thunderbird SMTP settings did not fix it. Neither did changing smtp.verizon.net to smtp.aol.com - all subsequent server login attempts failed to authenticate me. BTW from my Android email client, with same configuration, sometimes outgoing mail will succeed but only after a minute or two.

baspinall1

First off, I know they went to AOL. I made all the changes months ago. I use Thunderbird. As of three days ago I have problems with the SMTP server timing out and I can't send out emails. I revceive them fine. Never had any issues until a few days ago.

I use port 465 with smtp.verion.net

Did something else change Im not aware of?

Thanks for any help I need this back up fast for my company.

FedUpBoston

FYI, if, like me, you are plagued with SMTP send failures, allow me to relate my 1+ hour call to AOL tech support. This applies to Verizon customers using email clients such as Thunderbird on Windows, and Aquamail on Android.

The 2 reps were courteous and somewhat knowledgable, but it took most of the hour to get to the point. After much checking of settings (which I had not touched in months) and the 1st rep almost giving up, after I handed over a credit card number I got transfered to 2nd rep who did a remote connection and verfied that indeed my outgoing settings were right.

So now I await their phone call or email to say that the "issue" has been fixed. It would appear to me that sometime in late Feb. some AOL employee mucked with some part of their email infrastructure, causing a bit of havoc.

Hope to be able to report back that they have un-done their mistake.

Allen110

I figured out to make my outgoing SMTP work better...

I am using microsoft office pro plus with outlook 2010.

In my email settings, I did the following:

using my Verizon.net email.

Incoming Mail Server: pop.verizon.net

Outgoing Mail Server (SMTP): smtp.aol.com

Logon Info: AOL account email and password.

so far everything works good...

GusL

I had the same problem with Tbird - stopped sending outgoing mail as of 3/1/2018. I was able to fix it by going into my TB account settings and adding @verizon.net to my username for both the outgoing server and in the (incoming) server settings. I also changed the outgoing server name to smtp.aol.com. (When I tried the latter earlier, without changing the username, it didn't help. Changing the username too made it work for me).

Herd1

Many thanks for the instructions here. My email stopped sending on Friday and I could find NO help from AOL on this. I just stumbled on this forum. I did exactly what you suggested and it looks like my email is working again.

Herd1

You may have already seen this post, but in case not, I followed another poster's instructions and my outgoing server is back up. Here's what he wrote (and I did)

"In my email settings, I did the following:

using my Verizon.net email.

Incoming Mail Server: pop.verizon.net

Outgoing Mail Server (SMTP): smtp.aol.com

Logon Info: AOL account email and password"

My port is set to 465. After I made all these changes and tried to send an email, my computer asked for my AOL password. I entered it and the message sent.

Good luck!

FedUpBoston

Thanks to all who posted descriptions of their changes to work around AOL's mis-step. With your advice I now seem to have outgoing mail working again, using Tbird 52.6. The changes I made to Outgoing server settings were:

Appended '@verizon.net' to both Description and User Name field
Changed Server Name to 'smtp.aol.com'

[in both cases of course, not including those single quotes] The change to Description was probably unnecessary but no harm.

Once again the Verizon forums help other customers in ways that Verizon's own staff cannot, and you avoid the torture of many minutes on hold with suicide-inducing endless "music"!

tns2

Its been reported that SOME of the AOL servers uses for Verizon ids are using a certificate chain that incorrectly resolves. I haven't seen this myself. So if you happen to catch one it fails. Hopefully the next time you get one with a valid chain. And hopefully someone at AOL is working on resolving this if its really true.

Since the servers are now hosting more then just users from Verizon.net, the need for adding @verizon.net has been true for most of us for more than a year. Otherwise it cannot resolve userid@verizon.net and userid@aol.com, etc. So those who are just hitting this having looked through most of the solutions posted in this and other forums.

Allen110

I figured out to make my outgoing SMTP work better...

I am using microsoft office pro plus with outlook 2010.

In my email settings, I did the following:

using my Verizon.net email.

Incoming Mail Server: pop.verizon.net

Outgoing Mail Server (SMTP): smtp.aol.com

Logon Info: AOL account email and password.

so far everything works good...

This should work for most other email programs.

Mungoman

A member on this forum solved this for me. Gonna thank him as soon as I

find him again on this forum.

I was not receiving emails using Outlook since 2-19-18. Was getting the security

certificate not valid error. All I did was go into Outlook account settings and change the incoming mail server from pop.verizon.net to incoming.verizon.net. Then closed outlook and restarted. Bam all my emails strated pouring in

BakingDude

I use Outlook Express to normally send email via my vz email account which was switched to AOL almost a year ago. It has worked fine until a week ago, and since then I get "Socket Error" when trying to send emails. This is the first thread I have found that confirms others are having issues *sending* email. I had tried adding the domain, but not changing the server. My settings are EXACTLY as AOL has on a help page somewhere for VZ email accounts. I will try the array of solutions above (server, port, add domain) but this STINKS. Why haven't we been notified of a solution?

tns2

@Mungomanwrote:
A member on this forum solved this for me. Gonna thank him as soon as I
find him again on this forum.
I was not receiving emails using Outlook since 2-19-18. Was getting the security
certificate not valid error. All I did was go into Outlook account settings and change the incoming mail server from pop.verizon.net to incoming.verizon.net. Then closed outlook and restarted. Bam all my emails strated pouring in

Not a recommended solution as they were suppose to delete that URL.

They happen at the moment to resolve to totally different servers, one an AOL and one a yahoo server when I look them up using Opendns. Interestingly the correct name is the one that now resolves to yahoo.

> nslookup

> incoming.verizon.net.
Server: resolver1.opendns.com
Address: 208.67.222.222

Non-authoritative answer:
Name: pop-verizonmail.egslb.aol.com
Address: 64.12.88.168
Aliases: incoming.verizon.net

> pop.verizon.net
Server: resolver1.opendns.com
Address: 208.67.222.222

Non-authoritative answer:
Name: global-jpop-aol.mail.gm0.yahoodns.net
Addresses: 98.136.97.57
98.137.157.35
Aliases: pop.verizon.net

> smtp.verizon.net
Server: resolver1.opendns.com
Address: 208.67.222.222

Non-authoritative answer:
Name: smtp-verizonmail.egslb.aol.com
Address: 152.163.35.8
Aliases: smtp.verizon.net

Edison-99vs1

After many attempts, I found a solution that worked for me (Outlook 365 and iPhone 6). I changed the outgoing server to smtp.aol.com, made sure that the user name had @verizon.net, and for Outlook under More Setting...Outgoing Server ..selected Outgoing Server (SMTP) requires authentication and then selected use the same settings as incoming server

dcastromd1

Per Allen1 and Herd1 the solution below does work ...

on the iphone 8, my friend's verizon email started to do/have the same trouble, giving an error message when sending email (sorry I don't have the exact error any more).

In the settings for the verizon account, scroll down to the Outgoing Mail Server, click to open SMTP, remove the Primary Server (which probably says verizon.net), below you should see the smtp.aol.com option, click it, enable it, use the @verizon.net for the username and use port 465. WHEW!!!! Shame on Verizon and/or AOL for not sharing this info with folks. But, a lot of us know ... it is likely a way to get everyone to change to IMAP (which I bet they'd prefer).

nori2

Thanks! Worked for me!

Clark6267

AOL changed their outgoing port:

Port is now: 587

for outgoing mail.

That was very painful to find.

HighTechInsider

To send outgoing Verizon email, now hosted on the AOL email servers, your email client or app must support *** OAuth 2.0 Token *** outgoing mail server authentication. If your client does not support this then you can only use web email to send emails. Thank you for wasting my time (please note sarcasm) large bureaucratic Verizon AOL for NOT PUBLISHING THIS ANYWHERE.

I tried the following experiment to verify that Verizon outgoing email server required OAuth 2.0 Token *** outgoing mail server authentication. For the Apple iOS Mail client on iPhone or iPad using iOS 10.x, I was UNABLE to send email to my Verizon email account, now hosted and converted to AOL email servers. I used smtp.aol.com as the host name for the outgoing email server, along with trying both port 465 and 587, both using Verizon DSL (Wifi On) and direct to my cell carrier (Wifi off) on my iPhone. I event deleted the account on the Apple Mail client and re-set it up using the builtin Apple Mail client set up utility for AOL which sets up my verizon.net (full email account name with verizon.net included) as an imap account. None of these worked.

I then set up the account on an iPad with iOS 12.1.4 and I again used the the builtin Apple Mail client set up utility for AOL which sets up my verizon.net (full email account name with verizon.net included) as an imap account. This time it worked easily. I could easily send emails. The only difference is that the APPLE iOS Mail client App for iOS 12.x supports *** OAuth 2.0 Token *** outgoing mail server authentication. [ioS 10.x does not and I am not sure if iOS 11.x does support this or not, though there is some articles that do suggest that the Apple Mail client does support OAuth 2.0 Token outgoing mail server authentication in iOS 11.x]

Also it is interesting to note that certain MS Exchange server versions now also require OAuth 2.0 Token outgoing mail server authentication support as well.
So the simplest solution to get your Apple iOS email client to send email using a AOL hosted verizon.net outgoing email server, is to upgrade to iOS 12.x or later on your ipad or iphone.

And once again, the issue is not Apple support of OAuth 2.0 Token outgoing mail server authentication, but rather the AOL-Verizon support organization in not notifying their end users about the requirement to use this to send outgoing emails starting back in 2018. This is just another one of the reasons that I have migrated away from using my verizon.net account except in rare situations. AOL-Verizon is simply unreliable.
And to AOL-Verizon Support management - Thank you for wasting my time (please note sarcasm) large bureaucratic Verizon AOL for NOT PUBLISHING THIS ANYWHERE.

[Deleted User]

This thread will be locked in order to keep discussions current. If you have the same or a similar question/issue we invite you to start a new thread on the topic.

Child Item