Recommend Exim fast-track delivery rule for Tamarind aliases.

1 files changed, 26 insertions, 1 deletions

diff --git a/README b/README
index aee1b1e..fe82840 100644
--- a/README
+++ b/README
@@ -197,7 +197,7 @@ www-data group in the /etc/groups file.
 
    www-data:x:33:list,Debian-exim
 
-3.4.3 Exim Configuration
+3.4.3 Exim Aliases Configuration
 
 Early versions of Tamarind worked directly with /etc/aliases.  Later, it was
 changed to use an alternative aliases file, /etc/tamarind/aliases.
@@ -225,3 +225,28 @@ tamarind_aliases:
 
 In a "separate files" configuration style for Exim, this would be placed in its
 own file: router/450_exim4_config_tamarind_aliases.
+
+3.4.5 Exim Delivery Configuration
+
+Optionally, configure Exim to allow Tamarind addresses to bypass spam
+filtering.  Under the  acl_check_rcpt: section in your Exim configuration, add
+the following.
+
+  accept
+    recipients = ^\\d\\d\\d-\\d\\d\\d-\\d\\d\\d\\d@YOUR_DOMAIN\$
+
+Substitute the mail domain for YOUR_DOMAIN!
+
+Note: when Tamarind generates aliases, the domain part of these
+aliases is taken from /etc/mailname.
+
+The above rule should be among the first rules processed, before any "deny"
+rules for spam filtering.
+
+Rationale---why this is a good idea: Tamarind addresses are an anti-spam
+measure; they do not need to be combined with other anti-spam checks, and doing
+so is counter-productive in some ways. It is useful for Tamarind addresses to
+enjoy certain delivery.  They can then be used for online transactions in which
+it is inconvenient or impossible to have an e-mail repeated.   If a Tamarind
+address starts being abused by spammers, the user can stop the spam by deleting
+it. That is the only anti-spam measure required.