I had updated my settings some time ago and this morning I'm not getting emails with Outlook 2010 or my iPhone. The incoming port is set to 995 and SSL is checked. Any help is appreciated.
Outgoing mail works fine on both devices.
Thanks
Same here,
I carefully changed the set up as directed by Verizon. Now my outlook will not download my e mail from the server, although it has done a couple of times - though not yet today....
Come omn Verizon sort it out!
Same problem here. It started last evening (7:30-8:00 PM EST, 1/5/2012). I am used to this kind of "improvement" from Microsoft, but I would have thought that Verizon IT engineers would have it together . . .
Changed the ports # this morning. Tested and it came back as error. Changed back to old settings, and it works fine.
Same here. The one computer in my office receiving email is the only one where the settings weren't updated to the new port.
Ditto.... Outbound may not be working either. As a test I sent messages to work account, neither were receieved.
Ironically, if I send from web mailbox, messages are sent and received. Verizon's issue......
Same issue here in Fredericksburg, Va area.
Thank you all. Just changed my port back to 110 and turned SSL off for Outlook and iPhone. All is good.
Same here in Northern Virginia, Can't receive any email with the settings Verizon wants us to use. Problem started late last night. Why doesn't Verizon at least post something on their homepage tghat they are having issues and an ETA when it will be fixed?????
I too set my incoming port back to the original and things are working again. Thanks Verizon @#!%*#. Things had been working fine with the new port and SSL for weeks. How do you let things like this happen?
Excellent question.
Same in Princess Anne, MD. Changed back to no SSL and defaults. All is well.
Everything appears to be back up and working normally (9AM EST) on both my and my wife's verizon e-mail accounts using the new settings.
So very sad. I just called Verizon and they said it is a "Microsoft outage" and that users of "Microsoft Outlook" pop3 clients were affected. I told the "support" lady that the issue was their servers, not with Microsoft, but she held her ground. When I told here I was using non-Microsoft clients, including an Android phone on the VZW network, then she said "Oh", and backed down. But then said I could just access my email using the phone's browser! What a tool.
I asked for a workaround, and she had nothing to offer. So, insead of telling people they screwed up their SSL implementation (or perhaps the Chinese did so they could force VZ to go back to clear text to better monitor our e-mails!) , they blame Microsoft? Maybe they should look at their own forums, because the answer is right here: change the port back to 110
Inane! #verizon #**bleep** #outage #email
Same here in Massachusetts this morning. I made the new settings at least a couple of weeks ago and all has worked fine until this morning. Changing incoming port back to 110 didn't help. On the web I can see that I have several messages, but I can't get them today from Thunderbird. I hope they fix it soon.
I have been having the same issue. Changed to defaults and all my accounts are working. I had changed the settings several weeks ago and they worked fine up until yesterday so I ask the same question, how can Verizon make changes that do not work? Where are the change checks and balances?
They seem to have fixed it now (9:15 am eastern), but of course not notified us that there was a problem at all.
Mine now works again using port 995, but it wouldn't using port 110 even when 995 didn't work.
Obviously Microsoft snuck into your computer and changed Outlook!
When I stopped getting mail yesterday, I went into each account and double-checked I had the right settings (I did) and suddenly everything worked. Until this morning. Didn't feel like doing this again, so I came to this community forum. Everyone who went back to the old settings were happy. I tried them and they worked!
So, until Microsoft sneaks back into your computer (that is, Verizon gets its act together), go back to your original settings. When, and if, they stop working, THEN consider using the new Verizon settings.
Or maybe Microsoft will sue Verizon for libel and you can pick up a few dollars as a witness.
...Received the changover message from Verizon last night. I changed my account settings on my ipod Touch and Outlook 2010, and except for a few hiccups at first, everything was working fine when I was done. This morning I have found I am unable to receive e-mail on either client. I rechecked and played around with the settings for a little while to fix it - even lengthening the timeout settings - to no avail. I then changed the settings back to the original default (no SSL, 110, 25) and everything is working fine. Unbelievable time waster! I have more important things to worry about, Verizon. Get it right! Good thing I had not yet gotten around to changing the settings on my wife's Android. I'd be in deep @%$!*%.
--Jeff
Like I posted elsewhere on these forums looking for an answer, It's not just Outlook and Microsoft. I use Netscape, and others use Eudora with the same issue. However, I switxched back to 110/25 and it still stops after Connecting to Verizon.
I have been using Netscape 7. something with no trouble up to this point. After changing the settings to the SSL I get to the "Connecting to Verizon" message but not the "Sending username and password". It just dies. I switched it back to the default 110 and 25 and no SSL and now it's still not working. I even tried the above settings that the fella that called the helpdesk got. No dice. So I downloaded Thunderbird and copied over one of my profiles and it still won't work. I'd hate to have to try Outlook for this. Not sure what to do if I put it back to default and it still won't connect to Verizon
What to do I don't know.
A couple of hours ago, my SSL connection stopped working - Outlook for Mac 2011 responded with the error message "Connection limit reached for your IP address". I changed the ports back to the default 110 & 25, respectively and removed the SSL and e-mail again works. My suspicion is there is a problem at Verizon that will eventually be cleared. It might be noted that with the change to the new settings I have had multiple time out or connection dropped errors over the time since the e-mail first arrived about the new settings, after wihich my settings were changed imppediately. Web client has always worked.
By about 9:15 Eastern my Verizon connection began working again using the new ports and SSL. Then an hour later it broke again. Clearly there is something broken at Verizon's end and they are making us all be their beta testers.
My best guess as to how to deal with it from our end at this point is (1) make the new settings in your email client, (2) use that if and when it works, and (3) when it doesn't work, try to get by with web mail until they manage to fix it.
As far as I've been able to tell, the problem is only with incoming mail, as I've been able to send mail from Thunderbird even when I couldn't receive it. Lets hope they fix it soon.
Regarding my last post, above: While port 25 works, it will only work from a Verizon customer, I believe. Some time a go, the change was made to using port 587 for outgoing mail (spam reduction, don't you know ) That also seems to continue to work - the port, not the spam reduction.
Same problem as the other posts here in Western NY. Using Windows Mail on a Win7 PC. On 12/14/2011 verizon sent an email with a link to new e-mail client settings: incoming port: change from 110 to 995 and check SSL. Outgoing port: change from 25 to 465 with SSL checked. This worked fine until 01/05/2012. Outgoing email works with new settings but no incoming.
Changed incoming back to default port 110 and no SSL. This works.
Contacted verizon online chat support agent named Randy. He said I did the right thing. They (verizon) are having problem with using port 995 and SSL.
Randy said to use port 110 and no SSL. I asked if verizon will send customers an email when 995 is working again. He said that is undetermined at this time. He said I should continue to use incoming port 110 without SSL until that doesn't work and then "try" switching back to 995 with SSL checked. Problem with that is that port 110 will always work, even when the 995 problem is fixed, you just won't have SSL security on port 110.
Seems like verizon doesn't want to admit in writing - via an email - that they have a problem.
What kind of customer support is that anyhow - keep using the solution you (the customer) came up with until that doesn't work, and then use the settings verizon told you to use that doesn't work. Without any heads up from verizon. ?????????????? Huh?????
And Oh, by the way, verizon is raising my rate by $10 per month and discontinuing my $15 monthly discount in February and changing my tv channel line up and I will have to dial my area code now for local calls. Oh, and that "special rate" coupon I got in the mail for $99.99 per month for triple play - that's for NEW customers, not me - you {please keep your posts courteous}
Updated the port seeting to 995 and turned SSL on and things seem to be working. Hopefully Verizon fixed the problem
There was problems with the Verizon email servers on Friday morning the 6th, I found out. So when I got home and tried the email with Netscape and the old settings (without SSL) everything worked as before. Happy day.
I have had the same problem on my iPhone. New incoming and outgoing server settings do work within Outlook on the PC, but not on the iPhone. As soon as I reset the email account information back to port 110, SSL off, I am able to receive verizon.net email on my iPhone.
Verizon should update it's instructions or resolve the issue.
