Issue Gmail SMTP problem; SASL auth failure: incorrect digest response

[Tempest]

Hello,

I have a problem with a few email clients having trouble using my SMTP (one of them being gmail, but thunderbird is ok).

the gmail comes back with 'authentication failed. Please check your username/password. Server runtime error: "334 (...) authentication failure code (535)'

the /var/log/maillog shows:
'warning: SASL authentication failure: incorrect digest response'

My server is on CentOS 6.9.

I did search for similar gmail resolvevd issues, but I don't think anyone had the 'incorrect digest response'

Would you have any ideas, please?

Many thanks!

 

[UFHH01]

Hi Tempest,

I assume that you use TLS and might not use a valid certificate?


For further investigations, pls. include your corresponding mail - logs entries and try not to shorten them to one line and consider as well to post your corresponding configuration files for your mail - server.

=> Plesk for Linux services logs and configuration files ( KB - article: 213403509 )​

 

[Tempest]

I have an externally purchased certificate added in plesk/tools&settings/ssltls certs - Certificate for securing mail
Is there anything else needed to validate a cert?

Please find the files attached.

 

[UFHH01]

Hi Tempest,

the /var/log/maillog shows:
'warning: SASL authentication failure: incorrect digest response'

Can't be found within your provided mail - log. Pls. add a correspnding log - file, where your issue/error/problem exists.


In addition, you have this issue for your certificate:

Cert VALIDATION ERROR(S): unable to get local issuer certificate, certificate not trusted, unable to verify the first certificate

Pls. make sure, that you inserted as well the INTERMEDIATE certificate from Comodo. If you need help here, pls. contact the COMODO - Support ( or use the FORUM - SEARCH, where your issue has been discussed within earlier threads )

 

[Tempest]

Thank you for looking into this!

Please find the fresh maillog attached.

I'll look into the cert issue, I thought everything got uploaded.

 

[Tempest]

Hi,

Just wondered if you had any further thoughts on this.

I contacted the comodo team but they said that to them the certificates look perfectly installed. If this is not the case, could you let me know how you verified the installation, please?

Many thanks!

 

[UFHH01]

Hi Tempest,

If this is not the case, could you let me know how you verified the installation, please?

Pls. visit for example: => Secure Email and insert the desired eMail - address, to where you desire to send an eMail. ( I used inXX@tuiXX.XXot )
The result is still an error here:

[001.193] Cert Hostname DOES NOT VERIFY (mail.tuina.scot != vps453544.ovh.net | DNS:vps453544.ovh.net | DNS:www.vps453544.ovh.net)

If you test it with postmasXXX@vps453XXX.ovh.net, the result is o.k now.

 

[Tempest]

Alright, please help me understand the logic of the plesk cert installation.
Let's sum up the current situation.

let's use: "Cert A" - to mean an externally purchased cert
"Cert B" - a Let's Encrypt cert.

- in server level: Certificate for securing Plesk - 'Cert A' from server pool
- in server level: Certificate for securing mail - 'Cert A' from server pool

- in domain level: vps453544.ovh.net - 'Cert A' installed in that domain's 'SSL/TLS Certs' section

- in domain level: tuina.scot - 'Cert B' installed in that domain's 'SSL/TLS Certs' section

On my previous server with plesk, I had the same cert installed for domain tuina.scot and for securing mail on a server lever and everything was fine. Likewise, at the moment it's fine only for emails for the domain which cert is used for securing mail on the server level.
Does this mean that among all domains run on the server only the one may be secured fully, which cert is used for securing mail on the server level?