SCOUG-HELP Mailing List Archives
Return to [ 12 | 
September | 
2003 ]
<< Previous Message << 
 >> Next Message >>
 
 
 
Content Type:   text/plain 
=====================================================  
If you are responding to someone asking for help who  
may not be a member of this list, be sure to use the  
REPLY TO ALL feature of your email program.  
=====================================================  
 
On Fri, 12 Sep 2003 10:42:57 PDT7, Peter Skye wrote:  
 
>sending to webmaster@ but have never heard of postmaster@ -- who  
 
 
			II. postmaster@domain   
 
which RFC requires the  address be implemented?  
-RFC 2821 (new) (see below)  
 
-RFC 1173 <http://sunsite.cnlab-switch.ch/ftp/doc/standard/rfc/11xx/1173>,   
Responsibilities of Host and Network Managers.  
 
-RFC 2142 <http://sunsite.cnlab-switch.ch/ftp/doc/standard/rfc/21xx/2142>,   
Mailbox names for common services, roles and functions.  
 
  [JR Note: RFC822 is in \archive.zip  
 
  Note: RFC822 requires all domains exchanging e-mail to have a  
   address which is to be read by a person.  RFC2142   
  states they SHOULD have an  address.  
-RFC822:  
 
   6.3.  RESERVED ADDRESS  
 
          It often is necessary to send mail to a site, without  know-  
     ing  any  of its valid addresses.  For example, there may be mail  
     system dysfunctions, or a user may wish to find  out  a  person's  
     correct address, at that site.  
 
          This standard specifies a single, reserved  mailbox  address  
     (local-part)  which  is  to  be valid at each site.  Mail sent to  
     that address is to be routed to  a  person  responsible  for  the  
     site's mail system or to a person with responsibility for general  
     site operation.  The name of the reserved local-part address is:  
 
                                Postmaster  
 
     so that "Postmaster@domain" is required to be valid.  
 
     Note:  This reserved local-part must be  matched  without  sensi-  
            tivity to alphabetic case, so that "POSTMASTER", "postmas-  
            ter", and even "poStmASteR" is to be accepted.  
 
 
     This standard specifies a single, reserved mailbox address (local-part)  
     which is to be valid at each site.  Mail sent to that address is to be  
     routed to a person responsible for the site's mail system or to a person   
     with responsibility for general site operation.  
 
 
Date: Thu, 21 Sep 2000 19:10:30 -0700  
From: Steve Lamb   
To: "Dr. Jeffrey Race"   
Subject: Re: Postmaster  
On Thu, Sep 21, 2000 at 09:29:01PM +0700, Dr. Jeffrey Race wrote:  
> I thought it was 2142 that required .    Is this so and  
> if so how does 822 relate to it?  
    How it relates are stated in the rational in RFC2142.  Other documents  
require certain addresses for services, 2142 is taking thoes addresses and  
aggrigating them into a single location.  The requirement still comes from  
822. ;)  
         Steve C. Lamb           
-------------------------------+---------------------------------------------  
 
 
RFC-2821 says:  
 
   Any system that includes an SMTP server supporting mail relaying or  
   delivery MUST support the reserved mailbox "postmaster" as a case-  
   insensitive local name.  This postmaster address is not strictly  
   necessary if the server always returns 554 on connection opening (as  
   described in section 3.1).  The requirement to accept mail for  
   postmaster implies that RCPT commands which specify a mailbox for  
   postmaster at any of the domains for which the SMTP server provides  
   mail service, as well as the special case of "RCPT TO:"  
   (with no domain specification), MUST be supported.  
   SMTP systems are expected to make every reasonable effort to accept  
   mail directed to Postmaster from any other system on the Internet.  
   In extreme cases --such as to contain a denial of service attack or  
   other breach of security-- an SMTP server may block mail directed to  
   Postmaster.  However, such arrangements SHOULD be narrowly tailored  
   so as to avoid blocking messages which are not part of such attacks.  
 
 
 
 
 
 
 
 
RFCs  
 Complete index				http://www.cis.ohio-state.edu/htbin/rfc/  
 Searchable (by number or keyword)      http://www.tohuku.ac.jp/RFC.html   
 
http://sunsite.cnlab-switch.ch/ftp/doc/standard/rfc             
 
 
 
=====================================================  
 
To unsubscribe from this list, send an email message  
to "steward@scoug.com". In the body of the message,  
put the command "unsubscribe scoug-help".  
 
For problems, contact the list owner at  
"rollin@scoug.com".  
 
=====================================================  
 
  
<< Previous Message << 
 >> Next Message >>
Return to [ 12 | 
September | 
2003 ] 
  
  
The Southern California OS/2 User Group
 P.O. Box 26904
 Santa Ana, CA  92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group.  ALL RIGHTS 
RESERVED. 
 
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International 
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
 
      |