home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!decwrl!infopiz!mccall!ipmdf-newsgate!list
- From: ned@sigurd.innosoft.com (Ned Freed (Postmaster))
- Newsgroups: vmsnet.mail.pmdf
- Subject: RE: Postmaster notification for held msgs
- Message-ID: <01GMWZJKLZDM96VL5T@SIGURD.INNOSOFT.COM>
- Date: 28 Jul 92 22:01:18 GMT
- Organization: The Internet
- Lines: 19
- Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
- Resent-Date: 28 Jul 1992 15:01:18 -0700 (PDT)
- Resent-From: epmdf@YMIR.CLAREMONT.EDU
- Errors-To: epmdf@YMIR.CLAREMONT.EDU
- Resent-Message-ID: <01GMWZR46PNM9GVWP1@YMIR.CLAREMONT.EDU>
- X-Vms-To: IN%"bob@camb.com"
- X-Vms-Cc: IPMDF
- Mime-Version: 1.0
- Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-Transfer-Encoding: 7BIT
-
- When PMDF puts messages on hold because of detected loops no messages are
- sent to notify anyone about it. In addition, the message return job does not
- "see" these messages and does not act on them in any way.
-
- I think the reasons for not generating mail when mail loops have been detected
- are pretty obvious. If you want to do this yourself it is trivial to write
- a DCL procedure that runs once a day and does it. I would never recommend
- using such a scheme, however -- my experience has been that mail loops on
- postmaster addresses are far more common than on any other sort of address.
-
- The preferred approach is to write something that checks for held messages
- and notifies the appropriate people using something other than mail. This is
- axiomatically outside of the realm of PMDF to implement, so we don't
- provide any mechanism for doing it. Given the fact that a single line of
- DCL suffices to check to see if any messages are on hold, there doesn't seem
- to be much infrastructure outside of the notification process to provide in
- any case.
-
- Ned
-