* Note that this can also be done with the nobodyreturn keyword (?§24.9.86.3 on page 1066) withth e
PrivacyOptions option.
?? Although RFC2142 requires that they all be treated in a case-insensitive manner.
Table 12-1. RFC2142-defined email addresses and aliases
Address RFCs Description
abuse RFC2142 Accepts reports of unacceptable behavior
ftp RFC959 Accepts mail reporting FTP needs or problems
hostmaster RFC1033
through
RFC1035
Accepts mail reporting needs or problems with DNS
info RFC2142 Replies to requests for information about the business, its products, and its services
marketing RFC2142 Handles marketing communications
news RFC977 A synonym for Usenet
noc RFC2142 Accepts mail for the network operations center, which deals with network infrastructure
problems and requests
postmaster RFC2821 and
RFC2822
Accepts mail describing email problems
sales RFC2142 Replies with product or service information
security RFC2142 Sends or receives security notices, answers security concerns
support RFC2142 Accepts mail describing problems with products or services
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
12.4 Special Aliases | 475
Note that each of these ???required??? addresses is actually required only if you offer the
service indicated in the description (in Table 12-1).
Pages:
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853