Highlighted

Why can't I sign in?

Member

For about the last 8 weeks, I get random warning notifications that say

"Couldn't sign in" referring to my Verizon email account. No password

changes have been made, and subsequent emails come through later.

It seems like these warnings pop up randomly 3-4 times a day, as if

the phone were polling for email, encountering a problem, and then

posting the error. This is on a Droid Maxx which is less than a year

old, but worked fine until about late October /early November. There

may have been an Android version update around that time.

Anyone else seeing these problems,

Thanks...

Labels (1)
Tags (1)
1 Solution

Correct Answers
Highlighted

Re: Couldn't sign in

Novice

I did some research and determined that Verizon recently changed their defaults.  Try these settings:

Incoming mail server (POP3): pop.verizon.net

Incoming Server Port Number: 995

Outgoing mail server (SMTP): smtp.verizon.net

Outgoing Server Port Number: 465

Make sure SSL encryption is enabled for the incoming and outgoing mail server.

View solution in original post

Highlighted

Re: Couldn't sign in

Novice

Have you tried deleting the account and re-adding it?  If not, that will likely solve the issue.

0 Likes
Highlighted

Re: Couldn't sign in

Member

I tried doing as you suggested this afternoon. The error appeared about 2 hours

again after I re-created the account.

Any other suggestions?

0 Likes
Highlighted

Re: Couldn't sign in

Novice

Hmm, I have a few more questions.  I'm assuming that you are referring to an @verizon.net email account.  Do you have any other email accounts (yahoo, gmail, etc) setup on your phone?  If so, do you have the same issue with those? 

0 Likes
Highlighted

Re: Couldn't sign in

Member

I have the same issue on both phones... Separate accounts... All other accounts work fine

0 Likes
Highlighted

Re: Couldn't sign in

Member

The errors continued overnight.

The only other email account tied to this phone is Gmail, and I have

no issues with it with respect to warnings, just the @Verizon.net

account.

The account was recreated with the default values for incoming pop3

server, incoming.verizon.net at port 110, and outgoing.verizon.net at

port 587.

These were the same values used since I got the phone 6+ months

ago.

0 Likes
Highlighted

Re: Couldn't sign in

Member

I've been having the same thing happen, for a couple of months. And I just upgraded to a new phone, so it happened on my old one too. If I open email app & click refresh, the notification goes away. If go to account settings & click sync, likewise the notification goes away. If I just wait til the email automatically syncs again... it goes away.

So, it seems the verizon verification system, burps every now & then.

Like everything, nothing will be done until it effects the masses.

0 Likes
Highlighted

Re: Couldn't sign in

Novice

I did some research and determined that Verizon recently changed their defaults.  Try these settings:

Incoming mail server (POP3): pop.verizon.net

Incoming Server Port Number: 995

Outgoing mail server (SMTP): smtp.verizon.net

Outgoing Server Port Number: 465

Make sure SSL encryption is enabled for the incoming and outgoing mail server.

View solution in original post

Highlighted

Re: Couldn't sign in

Community Manager
Community Manager

c_beute,

I understand your concern with your Verizon personal email address. It's important to have your access back, we can help. Normally, this is a matter of adjusting settings. You will find the information here http://vz.to/1CJSHP0.

AdaS_VZW
Follow us on Twitter at @VZWSupport 

0 Likes
Highlighted

Re: Couldn't sign in

Member

After 36 hours without an error, I'm reasonably sure that the settings

changes did work, so thanks to Mikeg803 for identifying it.

My response to Verizon support is - why are the old default values

still there on your newest phones, and why do your store reps continue

to set up phones with the old values? Why hasn't Verizon pushed a

change through with a phone update to correct those values? That's

very disappointing.

Chris

0 Likes