On Tue, 24 Jun 2008, Phil Pennock wrote:
| just checked and the rewrite code doesn't appear to adjust
| $parent_local_part or $original_local_part. How useful those are depend
| upon what redirection has already happened. If you're not already using
| address_data, then one workaround is to preserve $local_part or
| [EMAIL PROTECTED] in the address_data option on the Routers and
| pull it back out again via $address_data (or ${local_part:$address_data}
| ) in the Transport.
|
| $parent_/$original_ have the downside of being potentially fragile
| depending upon other Routers.
|
| $address_data has the downside of needing to be set on every Router
| using this transport and preventing you from using it otherwise.
Thanks, that gives me plenty to go on. I have a test environment and will
play with the above.
I also wonder about forgetting rewrites and just replacing From: outright
with a headers_remove then headers_add. Given that the config elements in
question are only serving one person, this may suffice...
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
