SMTP password method

Support
1

What can I do if my server not support CRAM-MD5, and app not work on normal password auth or cipher ???

StartTLS or SSL said the same.

250-AUTH LOGIN

250-SIZE 0

250-HELP

250-AUTH=LOGIN

250-STARTTLS

1000103195
10001031951080×2400 167 KB

2

Hi virmix

Are you the email server administrator?

Can you post what error is displayed when using normal password. Do you know if the server is expecting a different authentication type (eg. scram-sha) or did you select encrypted password purely as a fault finding / trial and error attempt?

Is it possible the server is requiring an app password to be used, or oAuth authentication?

3

Yes it is my server with admin permissions.

The CRAM-MD5 is disabled but MS Outlook or others mail clients work fine.

https ://www. gmass .co /smtp-test

Connected to mail.comain.com:587

<< 220 domain .com ESMTP MAIL Service ready at 09/20/26 12:21:06

>> EHLO [1.1.1.1]

<< 250-domain .com [1.1.1.1], this server offers 7 extensions

<< 250-AUTH CRAM-MD5 LOGIN

<< 250-SIZE 0

<< 250-HELP

<< 250-AUTH=LOGIN

<< 250-STARTTLS

<< 250-XSAVETOSENT

<< 250 X-SAVETOSENT

>> AUTH CRAM-MD5

<< 504 CRAM-MD5 is disabled.

>> AUTH LOGIN

<< 334 VXNlcm5hbWU6

>> *************

<< 334 UGFzc3dvcmQ6

>> ********

<< 235 Authenticated

4

Your GMass test shows that the server accepts AUTH LOGIN and successfully authenticated.

<< 235 Authenticated

When you select normal password in K9, what error is displayed?
It should not be trying CRAM-MD5 if “normal password” is selected.

K9 uses AUTH LOGIN when AUTH PLAIN is not advertised by the server.

Have you configured K9 to use StartTLS?

Your trace doesn’t show the SMTP capabilities advertised after STARTTLS. K-9/Thunderbird performs a second EHLO after establishing TLS and uses that response to determine the available authentication mechanisms.

Can you capture a debug log from K9. Guide here.
Have a look at the server capability response following the second EHLO.

Its possible the server may require a capability that K9 doesn’t support.

5

Yes, always same error CRAM-MD5 as screenshot

With StartTLS , SSL or without it.

I test all settings and show same error.

6

The code uses CRAM-MD5 only when “Encrypted password” is selected in the UI.

fun AuthenticationType.toAuthType(): AuthType {
    return when (this) {
        AuthenticationType.None -> AuthType.NONE
        AuthenticationType.PasswordCleartext -> AuthType.PLAIN
        AuthenticationType.PasswordEncrypted -> AuthType.CRAM_MD5
        AuthenticationType.ClientCertificate -> AuthType.EXTERNAL
        AuthenticationType.OAuth2 -> AuthType.XOAUTH2
    }
}

Without a K9 debug log, opportunities to help you trace why CRAM-MD5 errors are observed when “Normal password” is selected in the UI are limited.

You can try posting an bug/issue report on Github and see if the developers can offer insight.

SMTP Auth
SMTP Auth270×603 31.5 KB

7

Plain Text was disabled too, only allow base64

Dont worries, I enable encryption on server