Well, I successfully sent a message to an invalid address to eagle.co.nz.
I'd guess it was a wierd patch, too.
921720265.618007 delivery 147849: failure: 202.36.45.1_does_not_like_recipient.
/Remote_host_said:_550_<[EMAIL PROTECTED]>_user_unknown/Giving_up_on_202.36.45.1./
Aaron
Quoting Harald Hanche-Olsen ([EMAIL PROTECTED]):
> | At Mon Mar 15 18:22:27 1999
> | call from renaissance.co.nz/203.97.88.2
> | 220-relay ESMTP SMTP/smap Ready.
> | 220 ESMTP tried here
> | HELO renaissance.co.nz
> | 250 (renaissance.co.nz) pleased to meet you.
> | QUIT
> | 221 Closing connection
> |
> | It looks as if the Qmail machine is connecting, passing a HELO
> | command and then just QUITing. Can anyone explain to me what is
> | going on here?
>
> As far as I can tell, this falls into the ``this cannot happen''
> category. I contacted the SMTP port on relay.eagle.co.nz myself, it
> responds exactly as shown above, with each line CRLF terminated and no
> fuzz about it. It looks like qmail-remote has stopped reading the
> response after the first line (the one with the hyphen), leaving the
> second line to be interpreted as the response to the HELO command.
> But, as far as I can read the source in qmail-remote.c (the first few
> lines in smtp() and all of smtpcode(), only ~20 lines in all) there is
> no way this can happen. So unless this is a patched version of qmail,
> I can see no rational explanation for this.
