Re: [AMaViS-user] another x-original-to question...

> --- amavisd~ Fri Sep 29 21:12:49 2006
> +++ amavisd Wed Aug 29 23:43:37 2007
> @@ -8363,4 +8363,10 @@
> # $Mail::SpamAssassin::SUB_VERSION, c('myhostname')));
> }
> +
> + # BREAKS SENDER'S PRIVACY!!! DO NOT USE!!!
> + $hdr_edits->add_header('X-Original-To',
> + join(', ', map { scalar(qquote_rfc2821_local($_->recip_addr)) }
> + @{$msginfo->per_recip_data}));
> +
> if ($mail_defanged ne '') {
> # prepend Resent-* header fields, they must precede corresponding
> Received
>
>
>> I tried putting this part of the code in the
>> add_forwarding_header_edits_common function (looks like thats what the
>> patch is doing) and then adding a declaration for recip_addr_smtp above,
>> but the X-Original-To is empty. Looks like I need to find the place of
>> where recip_addr_smtp can get a value... ?
>
> The recip_addr_smtp is a later invention.
> You will have to do with recip_addr, re-encoded into a rfc2822 form.
> There shouldn't be any difference with normal addresses, there may
> be a difference with weird and incorrectly encoded addresses
> by the original sender (like containing special characters
> in the local part of the address).

Hmm.. it's still putting the rewritten address into this field and not the
alias that is originally sent to (rcpt to). Just to reiterate, I am doing
address rewriting in Postfix before the content-filter (amavisd-new)...

Thanks,
Zivago

--
Zivago Lee
z@ziff.net

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/...fo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/