1479
Comment:
|
1531
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
## page was renamed from DebianMailSetup | |
Line 17: | Line 18: |
User controlled forwarding, with different behavior depending on local_part_suffix (eg, user-foo@debian.org is handled differently than user@debian.org) | User controlled forwarding, with different behavior depending on local_part_suffix (eg, user-''foo''@debian.org is handled differently than ''user''@debian.org) |
Line 25: | Line 26: |
''$package''@packages.debian.org forwards to the maintainer of the package and ''$package_contact''@pts |
|
Line 30: | Line 33: |
---- ## You can add other _helpful_ links here. ##See also: ## If this page belongs to an existing Category, add it below. ## CategorySomething | CategoryAnother |
* Mail Admins Group * weight RBL lists, and set cut-off level |
An attempt to categorize what the current mail setup does for Debian, and a wishlist for new features.
Current infrastructure
Standard alias file/role account handling
Different handling for different subdomains (e.g., the PTS has a header check that no other domain has, popcon is much more lenient about accepting mail with bad envelope senders, etc)
User settable per-user greylisting, RBL lookups, etc
User controlled forwarding, with different behavior depending on local_part_suffix (eg, user-foo@debian.org is handled differently than user@debian.org)
Virtual domain support - per domain alias file/user/group/etc settings
bsmtp mail - should we keep this? Do people use it? It seems like this should be replaced by the more generic virtual domain handling.
Several anti-spam measures, but discussing the specifics here is probably not that useful.
$package@packages.debian.org forwards to the maintainer of the package and $package_contact@pts
Wishlist
- AUTH based relay?
- RSA sig based relay?
- mail hub/spoke architecture?
- Mail Admins Group
- weight RBL lists, and set cut-off level