AquaMail Forum
English - Android => Bug reports => Topic started by: sparky on April 23, 2015, 07:50:59 am
-
What is going with my email app tonight? Sending - error 535 5.7.0, authentication rejected. My server is with Shaw Canada.
Any help appreciated...
-
A better question would be:
What is going on with your mail server tonight?
-
I had the same problem until I changed my outgoing server authentication from "Choose automatically" to "SASL PLAIN." I have no idea why this was necessary.
-
I had the same problem yesterday with mail provider Web.de.
However, just waited a few hours: it was a server-side problem - nothing to change in AquaMail.
8)
-
About web.de:
https://twitter.com/WEBDE/status/591617070619590656
I also got a couple of emails about how "AquaMail stopped working after last update" (from @web.de users).
-
>> I had the same problem until I changed my outgoing server authentication from "Choose automatically" to "SASL PLAIN." I have no idea why this was necessary.
Perhaps they "implemented" support for CRAM-MD5 authentication (the most secure method, which Aqua uses automatically if advertised by the server) -- and as is often the case, it actually does not work...
Just checked, yep, that's exactly what happened.
Verizon.net did the same last fall.
Wonder where they get enough brain-free monkeys to run those "mail services trusted by millions"...
And of course mail apps that don't support this -- most secure -- method of authentication just keep working (K9, Samsung Email, stock Android Email...)
-
If it's any consolation, I've dealt with the mindless monkeys long enough to know the problem wasn't your fault.