[exim-cvs] rework userforward local_part_suffix documentatio…

Top Page
Delete this message
Reply to this message
Author: Exim Git Commits Mailing List
Date:  
To: exim-cvs
Subject: [exim-cvs] rework userforward local_part_suffix documentation
Gitweb: http://git.exim.org/exim.git/commitdiff/d91082979d7b34eb32d676110a3b44417ae43551
Commit:     d91082979d7b34eb32d676110a3b44417ae43551
Parent:     3399bb60b83537c54021e5d0553612fe2f2cde39
Author:     Phil Pennock <pdp@???>
AuthorDate: Thu Oct 6 23:40:01 2011 -0400
Committer:  Phil Pennock <pdp@???>
CommitDate: Thu Oct 6 23:40:01 2011 -0400


    rework userforward local_part_suffix documentation


    Loosely based on suggestion from Julian Gilbey.
    fixes bug 1139.
---
 src/src/configure.default |   14 ++++++++------
 1 files changed, 8 insertions(+), 6 deletions(-)


diff --git a/src/src/configure.default b/src/src/configure.default
index d6aaa5e..a527b41 100644
--- a/src/src/configure.default
+++ b/src/src/configure.default
@@ -574,16 +574,18 @@ system_aliases:
# file starts with the string "# Exim filter" or "# Sieve filter", uncomment
# the "allow_filter" option.

-# If you want this router to treat local parts with suffixes introduced by "-"
-# or "+" characters as if the suffixes did not exist, uncomment the two local_
-# part_suffix options. Then, for example, xxxx-foo@??? will be treated
-# in the same way as xxxx@??? by this router. You probably want to make
-# the same change to the localuser router.
-
# The no_verify setting means that this router is skipped when Exim is
# verifying addresses. Similarly, no_expn means that this router is skipped if
# Exim is processing an EXPN command.

+# If you want this router to treat local parts with suffixes introduced by "-"
+# or "+" characters as if the suffixes did not exist, uncomment the two local_
+# part_suffix options. Then, for example, xxxx-foo@??? will be treated
+# in the same way as xxxx@??? by this router. Because this router is
+# not used for verification, if you choose to uncomment those options, then you
+# will *need* to make the same change to the localuser router. (There are
+# other approaches, if this is undesirable, but they add complexity).
+
# The check_ancestor option means that if the forward file generates an
# address that is an ancestor of the current one, the current one gets
# passed on instead. This covers the case where A is aliased to B and B