For example, if you do not run
UUCP (as few do), you may safely ignore mail to uucp. If you later add UUCP services,
you should add an alias for uucp.
RFC2142, then, suggests that a well-formed aliases file might contain the following
entries:
info: recipient
marketing: recipient
sales: recipient
support: recipient
abuse: recipient
noc: recipient
security: recipient
postmaster: recipient
hostmaster: recipient
usenet: recipient
news: recipient
webmaster: recipient
www: recipient
uucp: recipient
ftp: recipient
Note that recipient will be a person in some instances, and in others it will be a program
or a file.
In addition to requiring specific recipient addresses, RFC2142 also requires that
mailing lists always have a mailbox that can be reached using the literal suffix
-request. That is, if a mailing list is named bobs, the administrative address must be
bobs-request.
This behavior is easy to maintain using sendmail and could be implemented in an
aliases file entry that looks like this:
bobs: :include:/mail/lists/bobs.list
owner-bobs: postmaster
bobs-request: bob
Here, the first line defines the actual mailing list as a list of addresses read from the
file /mail/lists/bobs.list. The second line defines the address that should process
bounced email generated by this list. The third line defines the -request address that
will receive administrative email concerning the list.
Pages:
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854