|Subject:||Problem with SMTP Server|
|Posted by:||Thomas Zangl (usen…@tzis.net)|
|Date:||Tue, 24 Aug 2004|
it seems my ISP upgraded its mailserver and this has broken Indy´s SMTP
Look at this conversation:
Connected to badmailserver
Escape character is '^]'.
220 badmailserver Microsoft ESMTP MAIL Service, Version: 5.0.2195.5329
ready at Tue, 24 Aug 2004 20:36:07 +0200
250 badmailserver Hello [xxx.xxx.xxx.xxx]
mail from: thom…@tzi.xxx
250 2.1.0 thom…@tzi.xxx....Sender OK
rcpt to: thom…@tzi.xxx
250 2.1.5 thom…@tzi.xxx
354 Start mail input; end with <CRLF>.<CRLF>
250 2.6.0 <MsgID> Queued mail for delivery
221 2.0.0 badmailserver Service closing transmission channel
it seems after the "rcpt to: " command sent to the server Indy waits for
an response different from the one the server sents back.
Here is what the RFC says about the response to the RCPT TO command:
The second step in the procedure is the RCPT command.
RCPT TO:<forward-path> [ SP <rcpt-parameters> ] <CRLF>
The first or only argument to this command includes a forward-path
(normally a mailbox and domain, always surrounded by "<" and ">"
brackets) identifying one recipient. If accepted, the SMTP server
returns a 250 OK reply and stores the forward-path. If the recipient
is known not to be a deliverable address, the SMTP server returns a
550 reply, typically with a string such as "no such user - " and the
mailbox name (other circumstances and reply codes are possible).
This step of the procedure can be repeated any number of times.
So we can expect "250 OK" or "550 go away" message instead of "250
<somebullshit>". Is it M$ fault? Can we fix it?