[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Zmailer RFC822 parser barfs on null (<>) addresses



Got a note from Eric Allman ponting out that one of our machines running
ZMailer was complaining about null return addresses.  According to RFC822 and 
RFC1123 this is not optional.  I have not had a chance to look at it yet,
and won't get a chance until after returning from USENIX.  Eris'c note
is attached below.

-- Dan Ehrlich

To:	postmaster@guardian.cse.psu.edu
From:	Eric Allman <eric@CS.Berkeley.EDU>
Subject: apparent bug in your mail system
Date:	Sat, 4 Jun 1994 10:30:30 -0400
Sender: eric@mastodon.CS.Berkeley.EDU

The error message shown below seems to indicate that your mail
system doesn't understand the null return address.  This syntax
is required by RFC 821 and 1123.  I suggest you forward this
bug to your vendor as a VERY HIGH priority item.

eric


------- Forwarded Message

Date: Thu, 2 Jun 1994 11:52:33 -0700
From: Mail Delivery Subsystem <MAILER-DAEMON@CS.Berkeley.EDU>
Subject: Returned mail: Remote protocol error
Message-Id: <199406021852.LAA14426@hofmann.CS.Berkeley.EDU>
To: postmaster@hofmann.CS.Berkeley.EDU
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="LAA14426.770583153/hofmann.CS.Berkeley
.EDU"

This is a MIME-encapsulated message

- --LAA14426.770583153/hofmann.CS.Berkeley.EDU

The original message was received at Thu, 2 Jun 1994 11:52:28 -0700
from localhost

   ----- The following addresses had delivery problems -----
<mji@guardian.cse.psu.edu>  (unrecoverable error)

   ----- Transcript of session follows -----
... while talking to guardian.cse.psu.edu.:
>>> MAIL From:<>
<<< 501 try without the junk at the end
554 <mji@guardian.cse.psu.edu>... Remote protocol error

	[ ... Stuff Deleted ... ]

-------- End Forwarded Message