home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!crcnis1.unl.edu!moe.ksu.ksu.edu!mccall!ipmdf-newsgate!list
- Newsgroups: vmsnet.mail.pmdf
- Subject: RE: mailserv `unauthorized' rejection msgs
- Message-ID: <01GSX95O4OXG8Y4XUK@SIGURD.INNOSOFT.COM>
- From: Ned Freed <ned@sigurd.innosoft.com>
- Date: 30 Dec 1992 10:24:02 -0700 (PDT)
- Organization: The Internet
- Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
- Resent-Date: 30 Dec 1992 10:24:02 -0700 (PDT)
- Resent-From: epmdf@YMIR.CLAREMONT.EDU
- Errors-To: epmdf@YMIR.CLAREMONT.EDU
- Resent-Message-ID: <01GT0OI1EHMO90OARS@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
- Lines: 9
-
- The proper choices of addresses for authorization checking are all
- described in RFC822. Specifically, the Sender: address is used if present,
- and failing that the From: address is used.
-
- The debug output for the channel shows what addresses are used in great
- detail as well. I'll consider adding this information to the response
- messages too.
-
- Ned
-