For that directive to be recognized as
special, any address that begins with :include: must select the local delivery agent
and, beginning with V8.7, must have the F=: delivery-agent flag set (?§20.8.11 on page
765). This is automatic with most configuration files, but if your configuration file
does not automatically recognize the :include: directive, you will need to add a new
rule near the end of your parse rule set 0 (?§19.5 on page 696). For example:
R :include: $* $@ $#local $: :include:$1
Beginning withV8.7 sendmail, any delivery agent for which the F=: flag (?§20.8.11 on
page 765) is set can also process :include: files. (Note that eliminating the F=: flag for
all delivery agent definitions in your configuration file will disable this feature
entirely.)
The :include: directive is used in aliases(5) files like this:
localname: :include:/path
* Only root should be permitted to write to the aliases file. If you keep mailing lists inside that file, it might
need to be writable by others. This can create a security breach (?§4.5.4 on page 167).
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
13.2 :include: Mailing Lists | 487
The expression :include: is literal. It must appear exactly as shown, colons and all,
with no space between the colons and the ???include.
Pages:
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872