I'd like to think it's my fault, for altering smtpd.c to have cute
messages, but this has never happened before, so it could mean that
MDaemon got confused by the non-standard 250 code, saying more
than "250 ok" like others do, and returned the buffer in a
rcpt to: command.
I'm looking at these headers:
Received:
(qmail 501888 invoked by alias); 10 Apr 2000
20:55:05 -0000
Delivered-To:
250 ok yes [EMAIL PROTECTED]
Received:
(qmail 501889 invoked from network); 10 Apr 2000
20:54:54 -0000
Received:
from asub.arknet.edu (HELO
asubserver1.asub.arknet.edu) (150.208.48.1) by
tesla.umkc.edu with SMTP; 10 Apr 2000 20:54:54
-0000
Received:
from guest.asub.arknet.edu [150.208.48.186] by
asubserver1.asub.arknet.edu [127.0.0.1]
with SMTP (MDaemon.v2.7.SP4.R) for
<[EMAIL PROTECTED]>; Mon, 10 Apr 2000
15:46:50 -0500
Apparently qmail on tesla delivered this to "250 ok yes
[EMAIL PROTECTED]" which fell through to
me, instead of queueing it and re-sending it to [EMAIL PROTECTED] like
was supposed to happen.
I have forwarded the message to the correct recipient, but I would like
to
prevent this from happening again.
I am guessing that I need to include a dash after the OK in the replies,
like microsoft exchange has, to fix this. Reviewing the relevant
documentation, that is, http://cr.yp.to/smtp/request.html, I am
led to understand that a SMTP response of "250 ok yes sir" is every
bit as valid as exchange's "250 OK - Recipient <[EMAIL PROTECTED]>"
so I am not changing my server.
Thoughts?
_____________________________________________________________________
David Nicol 816.235.1187 [EMAIL PROTECTED]
"Nobody wants a hammer with racing stripes and a horn." - Greg Knauss
