From: Julien Cristau
-Emails to @debian.org addresses now go through a LDAP distributed email system. +Emails to @debian.org addresses go through an LDAP distributed email system. This system uses the forwarding field in the LDAP directory to route mail -without passing it through a users .forward file on a single host. +without passing it through a user's .forward file on a single host. Multiple machines participate in the forwarding to provide redundancy.
-Each forwarders inspects the LDAP database -to see if foo@debian.org has forwarding set to an address, if so the envelope +Each forwarder inspects the LDAP database +to determine the forwarding address for foo@debian.org. The envelope to address is rewritten and the message redirected to the new address. -Otherwise the message is relayed to master.debian.org for processing by the -users .forward files. If email forwarding is setup then .forward files are -NOT considered. Extension addresses (foo-lists) are always routed -directly to master for processing. +As that redirection occurs on the mail relays, there is no opportunity for +the use of .forward files, procmail or other filtering. Extension addresses +(foo-lists) are supported, but the extension will not be preserved when +forwarding - i.e. if foo@debian.org redirects to foo@example.com, +then foo-lists@debian.org also redirects to foo@example.com. + +
+As a special-case, the forwarding address may be foo@master.debian.org, +in which case the message is relayed to that system for processing by the +user's .forward or .procmailrc files. Forwarding to master.debian.org preserves +the extension part of the original address.
All machines also use the forwarding attribute as a default destination for @@ -42,10 +49,10 @@ foo@debian.org
The correct way to invoke procmail for extension addresses is "|/usr/bin/procmail [options]" @@ -66,3 +73,40 @@ Exim.
Also, 'Exim Filter' files are deliberately turned off. + +
+Debian developers have a wide variety of loud and conflicting opinions +about what constitutes correct handling of their mail, making it impossible for +an admin to choose a single setup that fits all use cases. +
+ ++Instead, we invite you to configure your own spam handling. +
+ ++Some options available to you are: +
+