On Tue, 23 Aug 2005, Marco Herrn wrote:
> Jakob Hirsch <jh@???> wrote:
> >
> > It would expand to
> > data = forwarded_address@???, original_address@???
> > but only if there's a mailbox original_address@???, otherwise
> > data = forwarded_address@???
>
> Well, that shouldn't work, since for original_address@??? a new
> message would be created, which itself is handled by the same router.
check_ancestor Use: redirect Type: boolean Default: false
This option is concerned with handling generated addresses that are the
same as some address in the list of redirection ancestors of the current
address. Although it is turned off by default in the code, it is set in
the default configuration file for handling users' .forward files. It is
recommended for this use of the redirect router.
When "check_ancestor" is set, if a generated address (including the
domain) is the same as any ancestor of the current address, it is replaced
by a copy of the current address. This helps in the case where local part
A is aliased to B, and B has a .forward file pointing back to A. For
example, within a single domain, the local part 'Joe.Bloggs' is aliased to
'jb' and ~jb/.forward contains:
\Joe.Bloggs, <other item(s)>
Without the "check_ancestor" setting, either local part ('jb' or
'joe.bloggs') gets processed once by each router and so ends up as it was
originally. If 'jb' is the real mailbox name, mail to 'jb' gets delivered
(having been turned into 'joe.bloggs' by the .forward file and back to
'jb' by the alias), but mail to 'joe.bloggs' fails. Setting
"check_ancestor" on the redirect router that handles the .forward file
prevents it from turning 'jb' back into 'joe.bloggs' when that was the
original address. See also the "repeat_use" option below.
Tony.
--
<fanf@???> <dot@???>
http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}
