Smtp authentucation error 535

[anatoly@tkach.me]

Today I started receiving smtp authentication error 535 while sending email from both my LG G4 phone and the Pixel C tablet. I've recreated my account nany times wuthout any errors, but when I try to send a message the errir 535 is returned.
FIY, there is no such error returned when I use other nail apps such as wemail or gmail on these devices and with the same acvount settings, which are as follows:
Email:  anatoly @ tkach . me
Smtp: smtp.1and1.com
Security type: SRARTLS (stict check), have tried all other to no luck
Port: 587
Authentication: tried all

Please, advice!

[Kostya Vasilyev]

I'm not aware of any issues in AquaMail's SMTP authentication code.

Please ask your mail provider what they see from their side.


But just in case:

No reason to try different "security type" values, this has to do with the network connection which is obviously fine.

But please do try changing Authentication to "SASL PLAIN" and also "SASL LOGIN".

If it fails with "SASL PLAIN" and works with "SASL LOGIN" then please let your mail provider know that they've broken "SASL LOGIN".


Another thought is maybe your "user email" (= "your email") is wrong in the account's setup info. This is on the very first screen when adding your account.

It's used for the "From" header, and maybe it's not recognized by the mail provider.


In general, every time there is a "worked before and now doesn't" situation, the cause is most likely not AquaMail.

[anatoly@tkach.me]

Kostya, thanks a lot for your envolvement.
I've tried all authentication methids, and both p!ain and login work fine at the time of manual account setup - no errors. The error comes up only at tge time of sending a message,  and this is why I can still blame aqua, not the provider - it looks like aqua can connect, but cannot send.
Also, other mail apps work fine with the same creds.

[mikeone]

Hi,
It would be the best way to figure out what is going on to send a log file to Kostya.
Details how to create and send debug logs for in-depth diagnosticsa you will find here:
http://www.aqua-mail.com/?page_id=232

[Kostya Vasilyev]

According to the log:

The server advertises SASL PLAIN and SASL LOGIN.

SASL LOGIN works, SASL PLAIN doesn't.

Now the twist:

You've got an *identity* under the account, same email address, same password (I hope), same server.

( this doesn't make much sense to me, but maybe you've got a reason for it )

The *account* outgoing server settings are to use SASL LOGIN -- and in your log, I can see it work, you sent a message, it went through.

The *identity* is set to have its own outgoing server settings, and it has SASL PLAIN, and it fails, the server doesn't accept the login + password, says they are not recognized.

To fix:

Long press the account -> identities -> tap the identity

You'll see the identity's email address and "Use own outgoing server" enabled (checked).

Tap Manual.

You will now see the detailed outgoing server settings for the *identity*.

Now change authentication *here* to SASL LOGIN and it should work.


And yes it has to be a bug on the server side.