Authentication error 530 or 535

[mickeyg]

I have been using AM very happily for about 1 year (still do!) but I recently had to change the password of my main account as I had lost it. I have many email POP accounts (GoDaddy) and IMAP (gmail)

After I changed the pop account password at godaddy, I automatically changed it in AM but got a 535 authentication error message. Eventually I removed AM and reinstalled

I setup 2 or 3 godaddy accounts and all got setup like a charm, but when it came to my main account I got, again, a 535 authentication error message.

I installed BlueMail and K9 and everything installed fine. Here is what I found out

In AM:

1) On the good godaddy accounts,
a) POP security set to SSL (strict check) port 995 authentication: choose automatically
b) SMTP security set to SSL (strict check) port 465 authentication: choose automatically

In BlueMail

1) POP has no security and PLAIN authentication
2) SMTP security is set SSL/TLS port 465 no sign-in required

In K9

1) POP security set to SSL/TLS, port 995, normal password
2) SMTP security is set SSL/TLS port 465 no sign-in required

Then I tried, based on K9 and BM security set to SSL (strict check) and "Do not login" but then I got a "530 authentication required" error message

Then I created a brand new email account at godaddy (with the offending domain name) and that worked fine

So I am guessing that in the AM directory structure, the original account file corresponding to the problematic email address, still resides "somewhere' and does not get overwritten with the new information.

Can I please be directed to that file so that I can manually delete it and recreate a new one, or does anyone have another suggestion

Thank you

[/list]

[Kostya Vasilyev]

Nope.

First, "no authentication" will only work if 1) either your account is setup to allow anyone to send (spammers sending from your name) or 2) will only "work" in K9 / BlueMail until you actually try to send.

AquaMail's "account setup" actually tries to start sending a message and then resets so it doesn't get sent. Can't speak for K9 and BlueMail but I guess they don't.

And then the app does not anything special for GoDaddy.

Re: still resides "somewhere' and does not get overwritten with the new information

Nope.

But please try either removing this account and adding it back.

Or try updating the password like this: long press on the account -> account setup -> Manual -> change the password for the incoming server -> Next -> change for the outgoing server -> choose "SASL PLAIN" as the authentication method.

If the "SASL PLAIN" helps, it would mean that GoDaddy's SMTP advertises "CRAM-MD5" authentication method but it does not actually work.

[mickeyg]

Thanks for the reply but
1) the account cannot be created since I cannot get passed the smtp validation.
2) I have tried your recommended settings but still get a 535 error

I don't understand why it would not work.

As example I'll used domain name 1dotcom

I originally had most important account me@1dotcom (please keep in mind that I deleted the app and reinstalled)

I tried to create      me@1dotcom but keep getting the 530 or 535 error messages
I then created     them@1dotcom and everything worked fine
I then created    yours@1dotcom and everything worked fine
I then tried again to re-create me@1dotcom but kept getting 530 or 535
(and my password is  accurately inputed)

I am quite puzzled by the fact that any email account I create at @1dotcom works fine in AM EXCEPT me@1dotcom

[Kostya Vasilyev]

I don't understand either, but at this point, it's best to ask GoDaddy support about this.

Esp. since K9 Mail gets same error unless you keep it from logging in (unless you set it to "do not log in" which is wrong, you don't want to make it possible for anyone to be able to send mail as you if they happen to know your email and server settings).

[brucesi]

1/14/2017: Similar issue here:
have used AqM for a couple years- Love it;
 just got a new phone and installed same email account with the same settings on new-as on old- phone, though AqM keeps showing failure to authenticate.
from my server/host (daily razor) site;


have tried *all options fro that and just other settings, but keep getting rejected....still works on the other phone and tablet with these settings (pop3, no ssl) is how those are set.
any thoughts or suggestions would be greatly appreciated.

BWC

[StR]

brucesi:
Is that happening with the login to IMAP server (incoming mail) or SMTP server (outgoing mail)?
Is it happening when you are creating account, or later on, when you are trying to receive or send a message?

The problem can be on the server side or on the client (phone/e-mail app) side.
1. If it is on the client side, - you need to check that the username and the password is entered exactly the same. (I assume that all other parameters are exactly the same.)
Since the password is the only field that is not seen, - consider check-marking "show password", when you are entering it, to make sure it is what you are entering.
One possible way to assure the "sameness" is to backup the settings on the old phone, transfer the backup file to the new one, and then "restore" it on the new phone.
(You can see a very recent (this week) thread on settings backup - for how to do that and the options of transferring the file to the new phone.)
2. It could be on the server side. E.g. Gmail these days wants each new device (and e-mail client) to be "authorized" before it can actually connect to the account and download messages. I had never heard about your provider, so, I don't know what its MO is.

[brucesi]

imap and pop and smtp; during setup-creating account- on the new phone.
user and pw are definitely correct

will check out the backup and xfr settings end of things.
Will inform.
thanks

[brucesi]

Backup from old phone and restored to new via DropBox......
it Worked; thanks so much; God bless; have a nice weekend.

BWC

 

[Kostya Vasilyev]

Some mail servers want "user@domain.com" as the login, some want just "user".

Aqua Mail defaults to the former (more common, in my experience), K9 Mail defaults to the latter (guess they think this is the more common one).

In theory, mail servers should be able to accept either variation (as long as it's not ambiguous).

Either way, this is easy to edit in Aqua Mail while setting up the account -- tapping Manual (after entering your email and password) takes you to screens with detailed server settings, editable of course.

Another fairly common issue is SMTP (outgoing) servers which advertise support for CRAM-MD5 login method but it actually is broken. In this case, forcing the login method setting to SASL PLAIN or SASL LOGIN often works.