Undeliverable Mail


RDMAILER ($EMD000%SDSUMUS@CUNYVM.CUNY.EDU)
MON 26 SEP 1988 02:57:07 CDT


The following errors occurred while attempting to send this mail file.

Best guess - SENDER is: TCP-IP @SRI-NIC.ARPA

*02.57.05 FROM: Invalid user/address string

----------------------------- ORIGINAL MESSAGE -------------------------------

Received: from ADMIN.BYU.EDU by SDSUVM.BITNET (Mailer X1.25) with BSMTP id
 1231; Mon, 26 Sep 88 02:57:06 CST
Received: by BYUADMIN (Mailer X1.25) id 6590; Mon, 26 Sep 88 01:53:09 MDT
Date: Mon, 26 Sep 88 02:04:43 GMT
Reply-To: <TCP-IP@SRI-NIC.ARPA>
Sender: "(TCP-IP ARPA Discussions)" <Sender: "(TCP-IP ARPA Discussions)" <TCPIP-L@BYUADMIN>
Comments: Warning -- original Sender: tag was tcp-ip-request@SRI-NIC.ARPA
From: Ross Patterson
              <elbereth.rutgers.edu!hardees.rutgers.edu!patterso@RUTGERS.EDU>
Subject: re: Batch Processing -- via SMTP....
X-To: tcp-ip@sri-nic.arpa
To: jeff consoer <To: jeff consoer <CC57000@SDSUMUS>

Craig,

   The experience of the BITNET "LISTSERV" mail manager bears out your
observations from the Info server. Many's the time we've wished for an
explicitly defined address to direct errors towards, rather than
relying on the mail system's implementors to grasp the vagueries of
RFC822's From: and Sender:; RFC821's MAIL FROM:, and the interaction
between them all. We've even found some mailers that use Reply-to: as
an error target! LISTSERV has the unenviable status of both a mail
originator (for the discussion groups it manages), and a batch processor
(for the various commands it accepts (subscription requests, file
retrievals, database search, etc.), causing it even further grief.

One mail-based batch processor I'm aware of, which provides access to
an otherwise online computer conference, explicity codes a "Reply-to:
Garbage@Garbage (Don't REPLY to this message)" to avoid the problem.

Ross Patterson
Rutgers University



This archive was generated by hypermail 2.0b3 on Thu Mar 09 2000 - 14:43:31 GMT