>I'm currently trying to write a tool to test, if SMTP AUTH
>works or not. (Every few weeks, the SMTPD stops authenticating
>users. This seems to be a known problem and does still exist
>in v6.05a)
>
>My questions is: How is the dialog with the SMTP server when
>SMTP AUTH is used? I've read the RFCs but didn't understand
>how the challenge between client and server is done.

Here's a byte-level loggin by  Eudora:

210  64:16.49 Rcvd: "220 X1 NT-ESMTP Server ms1.meiway.com (IMail 
6.04 1253-1)\r\n"
210  32:16.49 Sent: "EHLO sv.Go2France.com\r\n"
210  64:16.49 Rcvd: "250-ms1.meiway.com says hello\r\n"
210  64:16.49 Rcvd: "250-SIZE 0\r\n"
210  64:16.49 Rcvd: "250-8BITMIME\r\n"
210  64:16.49 Rcvd: "250-DSN\r\n"
210  64:16.49 Rcvd: "250-ETRN\r\n"
210  64:16.49 Rcvd: "250-AUTH LOGIN CRAM-MD5\r\n"
210  64:16.49 Rcvd: "250-AUTH=LOGIN\r\n"
210  64:16.49 Rcvd: "250 EXPN\r\n"
210  32:16.49 Sent: "AUTH CRAM-MD5\r\n"
210  64:16.49 Rcvd: "334 PDE0NOTA4QG1zMT4=\r\n"
210  32:16.49 Sent: "bGNvbnJhZCVHbzJGcmFWVhNmJhNDA2NzFmYTg0NDcxMjUz\r\n"
210  64:16.49 Rcvd: "235 authenticated\r\n"
210  32:16.49 Sent: "RSET\r\n"
210  64:16.49 Rcvd: "250 ok its reset\r\n"
210  32:16.49 Sent: "MAIL FROM:<[EMAIL PROTECTED]>\r\n"
210  64:16.49 Rcvd: "250 ok\r\n"
210  32:16.49 Sent: "RCPT TO:<[EMAIL PROTECTED]>\r\n"
210  64:16.49 Rcvd: "250 ok its for <[EMAIL PROTECTED]>\r\n"
210  32:16.49 Sent: "DATA\r\n"
210  64:16.49 Rcvd: "354 ok, send it; end with <CRLF>.<CRLF>\r\n"

1. When the SMTPD process that doesn SMTP AUTH is not responding, 
then after the mail client sends this line:

210 32:16.49 Sent: "AUTH CRAM-MD5\r\n"

there is no response.

2. the other failure is the SMTPD AUTH is working, but refusing logins.

Len


http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 & 8.2.3 T6B for NT4 & W2K
http://IMGate.MEIway.com:  Build free, hi-perf, anti-spam mail gateways

Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/

Reply via email to