SMTP down?

[sharpstick]

 Sometime since last night, A problem with the SMTP server must have happened. I can't send email. I get a password error.  Same with my wife's account. I have rebooted, tried three different Windows computers using Thunderbird and went to the verizon webmail page.

 I am properly logged in, can receive email, but cannot send. Webmail says "cann not send mail for unknown reason"

 I contacted verizon on a chat window but the agent was unable to help. Does anyone know if there is a known SMTP issue, or if there is a network status webpage?

 Location: Tampa FL

[Stenzack1]

As of 9:30 am eastern time today, the SMTP server for Central PA is down. This is the second time in less than week this has happened. The previous time I had to wait over an hour before sending was successful. Using a fully updated T'bird in a Win7 environment.

[starrin]

Good to see users have resurrected this thread, since Verizon has resurrected the problem.  That makes twice for me this month (mid January the last) and we will again see random lengthy outages nationwide, denials by VZ, and lots of frustrated customers.  Too bad they don't care.

   Well, don't forget you can send/recieve by logging in to MyVerizon and use that site which apparently is directly on the server.  That creates many problems for me  -  no one makes money on yesterday's news  (except, perhaps, TIME magazine.

    Does anyone know of a way to still get traffic posted by subscribing to  a separate (private) SMTP server?  It works for DNS servers.

[YankeeDoodle1]

SMTP down on Long Island - runs like the Long Island Rail Road - sproradically

[starrin]

As of 1730 the remainder of the problems (multiple addresses) with Verizon SMTP servers has resolved itself here in Virginia Beach as far as I'm concerned.

[Asweens]

I have been having problems for 2 days.  Restarted everything, routers, wireless router, computer.  Setup account again. Cleaned my computer.  Finally called Verizon to be told that there is a nationwide problem.  What would have been nice is if they actually told customers there was a problem so they don't waste time and go crazy trying to figure out what is wrong.  This is completely unacceptable.  Now I am told it could take 24-48 hours to resolve the issues.  Seriously??? 

[starrin]

Problem has returned in Virginia Beach.  One of the things I learned from discussions elsewhere on other forums is that part of the problem is that verizon has shifted (or, is shifting) to the AOL servers.  Don't believe me?  Run a DNS WHOIS search on your SMTP address.  It will return with a long string ending in aol.com.  Same holds true for incoming (POP) accounts. 

It's not a matter of changing your account settings - again.  Verizon bought AOL.  Apparently we are just going to have to wait while Verizon tinkers with their new toy.

    starrin

[aibek]

So even though they say they are only transitioning users from yahoo to AOL in a few states, EVERYBODY is getting hammered by this outage? Which does not appear to be officially acknowledged?

[Thistle]

Here in MD noticed the switch to AOL SMTP 2/6/2016 due to the certificate change. It worked until today using port 465. SMTP sessions then then started timing out - initially only for email containing MIME attachments (forwarded emails, as multipart/mixed), but not for simple emails or emails with other kinds of attachments. It then degraded to timing-out during authentication for anything with attachments, no matter how small or innocuous. Have long used port 465 for SMTP. Now even simple 1-line text test messages don't make it - they all seem to timeout in the authentication phase in which the SMTP server doesn't respond for well over 20 seconds Also once got a SMTP server down code. Incoming POP3 email is working using port 995. That switched to AOL pop3 servers here 2/10/2016.

[tns2]

---

@doubois wrote:

So even though they say they are only transitioning users from yahoo to AOL in a few states, EVERYBODY is getting hammered by this outage? Which does not appear to be officially acknowledged?

---

Everyone is getting changed to AOL.  Just the final change to the actual AOL interface is in waves.

However all the servers have to switch over first.  After all a Florida user like myself might be in NY.  In fact many Florida residents are Snowbirds from various states and have homes at both locations.  We would be terribly upset if we couldn't access our mail when in a different state.

[scififan2]

I've been having problems with both sending and downloading mail using Thunderbird since last night (2/11/2016). Still having problems tonight, but so far primarily with sending messages. Incoming seems to be working better than yesterday.

I'm in Maryland.

[Bob1692]

Started having problems in Northern Virginia about three days ago.  Email client times out, then the "enter new password" dialog pops up. 

I also had a heck of a time trying to log into the forums yesterday as the sign-on went into a continuous loop and would never sign me in.  It took several tries this morning to get signed in, too.

If everyone is being switched over to AOL, I've never received any notification about it, let alone any instructions on whether or not I need to change any instructions.

[Thistle]

SMTPs problems with Vz/AOL servers (using port 465) have continued for me in MD since 2/10/2016. Today outbound emails have failed pretty much continuously even for simple test messages with little text. smtp.verizon.net has resolved to both 64.12.91.200 and 152.163.35.8 in the failure cases. The failures are sometimes server down, but mostly are server timeouts exceeding 10 seconds in the authentication phase in which the server doesn't reply. The ESMTP interaction has involved more than 2 proxy servers as identified by the 220 response (vz-proxy-####-mx.aol.com, where #### has been m002, m003, m004, 1001, 1003 and 1004 for the failure cases I've observed). I received no notification of these changes, specifically timing, impact, or implications - nor any notification that the problem exists and is being worked on.. The Verizon/AOL page does NOT mention this area.

[kcferrick]

I was told by an automated voice that it wont be fixed till Monday 2/15/2016 9:45 a.m.This was in addition  to the past 6 days of promises of it being repaired.It is a horrible day when you cant access your emails especially when they are your bread and butter!!!