home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!agate!spool.mu.edu!uwm.edu!zaphod.mps.ohio-state.edu!howland.reston.ans.net!usc!news.service.uci.edu!unogate!mvb.saic.com!info-multinet
- From: RSCHOFIELD@LUCY.WELLESLEY.EDU (Dick Schofield)
- Newsgroups: vmsnet.networks.tcp-ip.multinet
- Subject: Re: mail problem
- Message-ID: <34B3B6E58040EB28@LUCY.WELLESLEY.EDU>
- Date: Tue, 26 Jan 1993 19:01 EST
- Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
- X-Gateway-Source-Info: Mailing List
- Lines: 21
-
- In a previous article, NED@SIGURD.INNOSOFT.COM (Ned Freed) wrote:
-
- > Counterexamples taken from real-world cases and uses of email and FAX:
- > ...
- > Now, you can make a case for not sending this sort of stuff via email, and you
- > can make a case for using explicit expiration dates instead of nondelivery
- > notifications, but the fact remains that people do use email for this sort of
- > stuff and rightly or wrongly they depend on temporary nondelivery notifications
- > to tell them when things are messed up. You may not use mail this way, I may
- > not use mail this way, but believe me there are lots of people who do, and
- > they're probably the majority.
-
- We have used Ned's PMDF at Wellesley College for years and depend on it
- providing periodic notification of undeliverable mail.
-
- We did, however, make one minor change. Out of the box, PMDF sends these
- warning messages after 3, 6, 9, and 12 days -- retaining the mail in its
- outbound queue until it gives up after the 12th day. We modified it to
- begin warning the user after 24 hours.
-
- Dick Schofield
-