Incoming/Outgoing Auth errors for my Verizon.net account

[makoti]

Hello all,

Two days ago, my Aquamail started to have trouble receiving/sending mail from my Verizon.net account. My Yahoo & Gmail appear to be working fine.
In searching this, I found a few things so I'll mention what I have.
Auth: Choose Automatically
Auth is set to "SASL PLAIN"
Server port 995 & 465
I think there was an update a few days ago. I haven't changed anything from when it was working like a champ.
Ideas on how to fix this?
Thanks!

[mikeone]

Hello all,

Two days ago, my Aquamail started to have trouble receiving/sending mail from my Verizon.net account. My Yahoo & Gmail appear to be working fine.
In searching this, I found a few things so I'll mention what I have.
Auth: Choose Automatically
Auth is set to "SASL PLAIN"
Server port 995 & 465
I think there was an update a few days ago. I haven't changed anything from when it was working like a champ.
Ideas on how to fix this?
Thanks!

Have you made any changes in the account configuration recently?
If not, the issue should be rather outside the app... on the server side.

[makoti]

No, no changes. If it's on Verizon's side (who'd be surprised?), how do I figure out how to make it work again?

[mikeone]

What AquaMail version are you using?
What is the exact error message?

... and please have a look into this thread:
http://www.aqua-mail.com/?p=1716

[mikeone]

What AquaMail version are you using?
What is the exact error message?

... and please have a look into this thread:
http://www.aqua-mail.com/?p=1716

Or maybe Verizon broke something else this time?

You are welcome to capture the issue in a debug log with "raw session data".

In the application’s settings, open “Debug” section (at the bottom) and enable “Debug logging” there. Set “Log output location” to “File (log-AquaMail.txt)”.

Once logging is enabled, please repeat whatever was causing the issue.

After having done this, please send the log file to kmansoft / at sign / gmail / dot com (and disable logging afterwards). The log file is called log-AquaMail.txt and is stored at the root of your device’s memory card or large built-in storage.

I recommend to copy a link to this thread:
https://www.aqua-mail.com/forum/index.php?topic=4425.msg24437#msg24437

[makoti]

Did this & sent the log. Thanks. The error say "Incoming login error -ERR internal server error" I've re-checked the password & long in several times. I'll look over that other thread.
Thanks again.

[mikeone]

Okay.

@Kostya:
Thank you for your effort I've caused. [German saying]

[Kostya Vasilyev]

The "latest update" (of AquaMail) was January 19.

I started getting messages about Verizon auth failures about two or three days ago.

Zero (zilch, nada) messages about this issue from last update until then.

And then "internal server error" really speaks for itself.

So yes, it's not the app, it's Verizon.

---

Being a mail app developer, I see some fairly major mail service break something about once a month (between them all).

Right now, in addition to this one, there a fairly major issue with Yandex (a major Russian web portal / search engine / mail provider).

[makoti]

Just to close this out, in case it ends up in anyone's search... it solved itself. Or, more likely, Verizon de-screwed it up. Life is good again. Thanks for the help.

[mikeone]

Just to close this out, in case it ends up in anyone's search... it solved itself. Or, more likely, Verizon de-screwed it up. Life is good again. Thanks for the help.

Thanks for your feedback.
Verizon servers seems to be magical 

[Kostya Vasilyev]

Re: Or, more likely, Verizon de-screwed it up

And I haven't gotten another email about it since Friday.

So I'm happy too

[mikeny]

Hi,

I was having similar authentication issues as late as last night when it was reported here that it was resolved so maybe something is still up.

Curiously when I am home on my own WiFi, there aren't any issues.  This has repeated itself over the last several days. 

I do think it's Verizon because I tried another app and had the same results. I couldn't get it to authenticate on 4G but it did work when I returned home to my WiFi network.

[mikeny]

Hi,

I was having similar authentication issues as late as last night when it was reported here that it was resolved so maybe something is still up.

Curiously when I am home on my own WiFi, there aren't any issues.  This has repeated itself over the last several days. 

I do think it's Verizon because I tried another app and had the same results. I couldn't get it to authenticate on 4G but it did work when I returned home to my WiFi network.

Update.  It seems to be working now and I'm currently on 4G. Maybe it's an intermittent or hopefully solved issue.