1 #use wml::db.d.o title="User Settable Mail Configuration"
6 Debian developers have a wide variety of loud and conflicting opinions
7 about what constitutes correct handling of their mail, making it impossible for
8 an admin to choose a single setup that fits all use cases.
12 Instead, we invite you to configure your own spam handling.
16 Some options available to you are:
19 <li><b>bATVToken</b> (to be enabled before 1/1/2010, with any luck) BATV
20 private token for address rewriting. Useful in combatting bounce forgery, but
21 requires configuration on your own mail relay(s).
22 <li><b>emailForward</b> Address to forward your mail to. Setting this and
23 then rejecting mail from d.o machines is less than helpful.
24 <li><b>mailCallout</b> Whether or not to use Sender Address Verification.
25 <li><b>mailContentInspectionAction</b> One of reject, markup, or blackhole.
26 Applies to checks done on the content of message bodies, such as spam and
27 virus checks. Reject is default, and will reject the mail if a match occurs.
28 Markup will add a header and then forward the mail to you anyway. Blackhole
29 will accept the mail and silently discard it.
30 <li><b>mailDefaultOptions</b> (to be enabled before 1/1/2010, with any
31 luck) Whether to enable the 'normal' set of (fairly
32 minimal) SMTP time checks that DSA decide are appropriate. Defaults to true.
33 <li><b>mailGreylisting</b> Whether to enable greylisting.
34 <li><b>mailRBL</b> Set of RBLs to use.
35 <li><b>mailRHSBL</b> Set of RHSBLs to use.
36 <li><b>mailWhitelist</b> Sender envelopes to whitelist.
37 <li><b>mailDisableMessage</b> Absolute last resort measure - will disable
38 incoming mail from all machines not part of the Debian host list (see
39 /var/lib/misc/thishost/debianhosts on any d.o machine). This makes it very
40 difficult for things like automated pings and mass mailings to all concerned
41 DDs about changes to happen, and is strongly discouraged.