home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!usc!news.service.uci.edu!unogate!mvb.saic.com!info-multinet
- From: adelman@TGV.COM (Kenneth Adelman)
- Newsgroups: vmsnet.networks.tcp-ip.multinet
- Subject: RE: mail problem
- Message-ID: <930125181816.45000102@TGV.COM>
- Date: Mon, 25 Jan 93 18:18:16 PST
- Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
- X-Gateway-Source-Info: Mailing List
- Lines: 29
-
- > Some SMTP mailers issue nondelivery messages on a periodic basis. Thus after
- > the mail has been in queue for an hour, the sender would receive a message
- > similar to:
-
- > From: Mailer_Daemon
- > To: originating_user
- > Subject: RE: subject_line_of_original_message
-
- > This message has not been delivered after 1 hour.
-
- > The system will keep trying to deliver this message for 48 hours.
- > At that time, the message will be returned to you.
-
- > Thank you for your patience.
-
- > Using nondelivery times of 1/2, 1, 2, 4, 8, 12, 16, 24, 36, and 48 hours
- > (actually 1/2, 1, and 24 are probably sufficient) would ensure that the
- > originator was well aware of the delay in delivery yet allow sufficient
- > time for the message to get through a slow link.
-
- > Does anyone think a feature of this sort should be included in Multinet?
-
- I've always lobbied very strongly AGAINST this sort of thing. It
- can turn simple mail loops into something that explodes exponentially. I
- feel that unless specificically requested (eg, mailing list explosion)
- a mailer should never generate more than one message out for each message
- that arrives inbound.
-
- Ken
-