> i.e. nothing in the DATA section whatsoever. This isn't "legitimate 
> mail" in any sense whatsoever (since there's no mail there, only an 
> envelope). It's completely illegitimate. It violates RFC 2822. 

I think we all agreed on that. However: As i already pointed out, 
i believe that RFC 2821 does not require the message to be of any
particular format, because it explicitely says "_When_ using 822 
...". Therefore i believe that any breaking of RFC 822/2822 is 
completely unrelated to the purpose of mail transport known as
SMTP which is the job of qpsmtpd.

qmail-smtpd and qmail-remote will receive/send happily "messages" 
in  totally weird formats, even complete binary data (as long as 
not CRLF.CRLF is contained in the data). I believe the same is 
true for other MTAs. For the purpose of SMTP all one need is
a.) a data object of some kind and b.) envelope sender and 
recipient. 

(Of course later stages in the MTA which process the message and 
add Received-Lines etc. will have problems with non RFC2822 
"messages", but this is not related to SMTP and can be solved by 
adding appropiate handling code)

I'm all with you that i also do currently do not see any usage
for 0 byte messages (although they might very well trigger an
action, e.g. when sent to an recipient which is piped into a
script), but i prefer to be as compliant as possible in 
implementation of SMTP.

-kju

-- 
      It's an insane world, but i'm proud to be a part of it. -- Bill Hicks

Reply via email to