Hello Peter, Tuesday, April 26, 2005, 5:42:07 AM, you wrote: > Hello Stuart,
> Tuesday, April 26, 2005, 11:40:28 AM, you wrote:
>>> This mostly happens with Googles GMail SMTP server.
>>> Maybe somebody using GMail can verify this?
SH>> Confirmed.
> Well, in that case Rit should enlighten us what this specific error message
> could mean and analyse it with an active GMail account. Everything else is
> pure speculation and not very helpful.
Okay, this could be interpreted two ways... But it could be read as
a bug on both sides.
[21:31:48] C: {476 bytes sent}
[21:31:48] S: 250 2.0.0 OK 1114569108
[21:31:48] C: RSET
[21:31:48] S: 250 2.1.0 Flushed
[21:31:48] C: QUIT
This little except is from the final communications of an SMTP
transaction. TB issues an RSET which gmail response with "250 2.1.0
Flushed". RFC2821 says that the SMTP server MUST return "250 OK" (see
section 4.1.1.5 of RFC2821). However, I think some if you read section
2.4 of the same RFC, it says that all replies must start with a 3
digit response code, and optional arguments. However I think reading
the RFC literally, the response MUST be "250 OK", and not what gmail
sent. It would be more friendly for TB to read the first 3 digits to
see if the command issues was in fact an error (4xx or 5xx) or an ok
command (1xx, 2xx, or 3xx).
--
Jonathan Angliss
<[EMAIL PROTECTED]>
pgp6iyJqbWTCw.pgp
Description: PGP signature
________________________________________________________ Current beta is 3.0.9.19 Return | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
