home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!swrinde!elroy.jpl.nasa.gov!decwrl!decwrl!infopiz!mccall!ipmdf-newsgate!list
- From: ned@sigurd.innosoft.com (Ned Freed)
- Newsgroups: vmsnet.mail.pmdf
- Subject: RE: Mail-11 delivery and soft-vs-hard failures
- Message-ID: <01GO8IVWWXWS9S3OWV@SIGURD.INNOSOFT.COM>
- Date: 31 Aug 92 22:40:38 GMT
- Organization: The Internet
- Lines: 18
- Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
- Resent-Date: 31 Aug 1992 15:40:38 -0700 (PDT)
- Resent-From: epmdf@YMIR.CLAREMONT.EDU
- Errors-To: epmdf@YMIR.CLAREMONT.EDU
- Resent-Message-ID: <01GO8J1MUO9E95O4DJ@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
-
- The code to determine whether or not a given error is temporary or
- permanent is deeply buried in the internals of the VMS mail foreign
- protocol interface. This code is not shipped with PMDF as a rule (it is
- available under nondisclosure). The code is extremely complex since these
- are not simple numbers -- they are strings and have to be parsed to obtain
- their content.
-
- This error in particular is also produced when a forwarding address is
- broken on receiving system's side of things. This can in fact be a
- consequence of the system not being fully initialized, so it does happen
- at completely transient times. It is therefore inappropriate to reclassify
- this particular error as permanent. Classification of errors is very tricky
- because you have to know all the circumstances that can produce the error.
- (My personal favorite is the "no such device" error, which you might think
- would be permanent, but turns out to be what you get when some network
- software is temporarily shut down!)
-
- Ned
-