Mike Hamrick wrote:
On Jan 7, 2008, at 12:23 AM, Johannes Weberhofer, Weberhofer GmbH wrote:
I have changed the field-size to VARCHAR(1), so I can give the users
who have forgotten their password a hint, but I do not see the real
passwords
As Erik pointed out, this will break the CRAM-MD5 authentication
method. Both client and server need to know the password for CRAM-MD5
to work properly. If you do this, it's likely that qmail will still
claim it supports CRAM-MD5, but if a client tries to authenticate
using this method it will fail. If none of your users authenticate
this way it's probably not a big deal though.
Mike
AFAIK,
Thurderbird use CRAM-MD5 auth first
if it fail then use PLAIN auth
but for Email Client on Nokia phones seem use CRAM-MD5 only
it wont try Auth Plain
see log below
Thunderbird Using Port 587 -- Success using AUTH PLAIN after failed
using AUTH CRAM-MD5
12-28 00:41:51 tcpserver: status: 1/100
12-28 00:41:51 tcpserver: pid 25324 from 10.10.105.181
12-28 00:41:51 tcpserver: ok 25324
server1.myholding.com:10.10.64.100:587 :10.10.105.181::3361
2-28 00:41:51 25324 > 220 server1.myholding.com - Welcome to MY Server
Ver. 1.3 SMTP Server ESMTP
2-28 00:41:51 25324 < EHLO [10.10.105.181]
2-28 00:41:51 25324 > 250-server1.myholding.com - Welcome to MY Server
Ver. 1.3 SMTP Server
2-28 00:41:51 25324 > 250-STARTTLS
2-28 00:41:51 25324 > 250-PIPELINING
2-28 00:41:51 25324 > 250-8BITMIME
2-28 00:41:51 25324 > 250-SIZE 20971520
2-28 00:41:51 25324 > 250 AUTH LOGIN PLAIN CRAM-MD5
2-28 00:41:51 25324 < AUTH CRAM-MD5
2-28 00:41:51 25324 > 334
PDI1MzI0LjExOTg3NzczMTFAc2VydmVyMS5ycHhob2xkaW5nLmNvbT4=
2-28 00:41:51 25324 <
YXl1bGlhc3RhbnRvIGQ3OTRhZWYzNDVlYTI0ZTc2MTdmN2NlMmZhZDMxMTA3
2-28 00:41:56 25324 > 535 authentication failed (#5.7.1)
2-28 00:41:56 25324 < AUTH PLAIN AGF5dWxpYXN0YW50bwBDSE9CSVRT
2-28 00:41:56 25324 > 235 ok, go ahead (#2.0.0)
2-28 00:41:56 25324 < MAIL FROM:<[EMAIL PROTECTED]> SIZE=612
Nokia 6120c Email client using port 25 w/ authentication -- Failed with
AUTH CRAM-MD5 but not trying using AUTH PLAIN
12-28 00:48:26 tcpserver: status: 1/100
12-28 00:48:26 tcpserver: pid 25434 from 202.3.217.2
12-28 00:48:26 tcpserver: ok 25434 server1.myholding.com:10.10.64.100:25
:202.3.217.2::33659
2-28 00:48:28 25434 > 220 server1.myholding.com - Welcome to MY Server
Ver. 1.3 SMTP Server ESMTP
2-28 00:48:28 25434 < EHLO [10.129.126.7]
2-28 00:48:28 25434 > 250-server1.myholding.com - Welcome to MY Server
Ver. 1.3 SMTP Server
2-28 00:48:28 25434 > 250-STARTTLS
2-28 00:48:28 25434 > 250-PIPELINING
2-28 00:48:28 25434 > 250-8BITMIME
2-28 00:48:28 25434 > 250-SIZE 20971520
2-28 00:48:28 25434 > 250 AUTH LOGIN PLAIN CRAM-MD5
2-28 00:48:29 25434 < AUTH CRAM-MD5
2-28 00:48:29 25434 > 334
PDI1NDM0LjExOTg3Nzc3MDlAc2VydmVyMS5ycHhob2xkaW5nLmNvbT4=
2-28 00:48:29 25434 <
YXl1bGlhc3RhbnRvIDYwZTFlNzU2MzI1YzU0NjNjODk5YjkxYTYwMTRiMzNj
2-28 00:48:34 25434 > 535 authentication failed (#5.7.1)
2-28 00:48:35 25434 < RSET
2-28 00:48:35 25434 > 250 flushed
2-28 00:48:36 25434 < MAIL FROM: <[EMAIL PROTECTED]>
12-28 00:48:36 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
<[10.129.126.7]:unknown:202.3.217.2> rcpt <> : sender accepted
2-28 00:48:36 25434 > 250 ok
2-28 00:48:36 25434 < RCPT TO: <[EMAIL PROTECTED]>
12-28 00:48:44 CHKUSER rejected relaying: from
<[EMAIL PROTECTED]::> remote
<[10.129.126.7]:unknown:202.3.217.2> rcpt <[EMAIL PROTECTED]> : client
not allowed to relay
2-28 00:48:45 25434 > 553 sorry, that domain isn't in my list of
allowed rcpthosts (#5.5.3 - chkuser)
2-28 00:48:46 25434 < QUIT
2-28 00:48:46 25434 > 221 server1.myholding.com - Welcome to MY Server
Ver. 1.3 SMTP Server
12-28 00:48:46 25434 > [EOF]
12-28 00:48:46 tcpserver: end 25434 status 0
12-28 00:48:46 tcpserver: status: 0/100
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
