[Bug 150430] Sending Mail via SMTP-AUTH fails ... qmail mailserver with smtpauth + pop-before-smtp

[Valeriy Kassenbaev]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=150430         
vkassenbaev gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vkassenbaev gmail com



------- Additional Comments From vkassenbaev gmail com  2007-10-17 20:29 -------
>As you can see from my telnet session, qmail does accept authentication and print those AUTH=... lines

Was your telnet connection opened from the same host from which you authenticated via pop? Because, as you know, when smtp-after-pop authorization method enabled, qmail remebers the host after pop authetication so user from this host can use qmail as open relay without autentication during poplock time. If so, are you sure that you were in "poplock window" when opening that telnet conection?

Yes, seems like kmail is right when it throws the error. According to rfc server must return 503 error only when using AUTH command after it was used once and autentication was successfull. kmail uses AUTH first time, so it doesn't expect this error.

As I can see, thunderbird even doesn't try to autenticate (doesn't use AUTH command) if it's not needed:
Auth is not needed (pop auth has been used before, and we are in "poplock window"):
--------------------------------------------------------------------
 <...>

[pid  1444] write(1, "220 ##SERVER_HOSTNAME## ESMTP\r\n", 31) = 31
[pid  1444] select(1, [0], NULL, NULL, {1200, 0}) = 1 (in [0], left {1199, 964000})
[pid  1444] read(0, "EHLO ##LOCAL_HOSTNAME##\r\n", 1024) = 25
[pid  1444] select(2, NULL, [1], NULL, {1200, 0}) = 1 (out [1], left {1200, 0})
[pid  1444] write(1, "250-##SERVER_HOSTNAME##\r\n250-STARTTLS\r\n250-PIPELINING\r\n250 8BITMIME\r\n", 69) = 69
[pid  1444] select(1, [0], NULL, NULL, {1200, 0}) = 1 (in [0], left {1199, 960000})
[pid  1444] read(0, "MAIL FROM:<##SENDER##>\r\n", 1024) = 39
[pid  1444] select(2, NULL, [1], NULL, {1200, 0}) = 1 (out [1], left {1200, 0})
[pid  1444] write(1, "250 ok\r\n", 8)   = 8
[pid  1444] select(1, [0], NULL, NULL, {1200, 0}) = 1 (in [0], left {1199, 966000})
[pid  1444] read(0, "RCPT TO:<##RECIPIENT##>\r\n", 1024) = 32

 <...>
--------------------------------------------------------------------

Auth is needed:
--------------------------------------------------------------------
 <...>

[pid  1497] write(1, "220 ##SERVER_HOSTNAME## ESMTP\r\n", 31) = 31
[pid  1497] select(1, [0], NULL, NULL, {1200, 0}) = 1 (in [0], left {1199, 965000})
[pid  1497] read(0, "EHLO ##LOCAL_HOSTNAME##\r\n", 1024) = 25
[pid  1497] select(2, NULL, [1], NULL, {1200, 0}) = 1 (out [1], left {1200, 0})
[pid  1497] write(1, "250-##SERVER_HOSTNAME##\r\n250-AUTH=LOGIN CRAM-MD5 PLAIN\r\n250-AUTH LOGIN CRAM-MD5 PLAIN\r\n250-STARTTLS\r\n250-PIPELINING\r\n250 8BITMIME\r\n", 131) = 131
[pid  1497] select(1, [0], NULL, NULL, {1200, 0}) = 1 (in [0], left {1199, 967000})
[pid  1497] read(0, "AUTH CRAM-MD5\r\n", 1024) = 15

 <...>
--------------------------------------------------------------------

I think the kmail behaviour should be similar.