I grabbed 2.5.4, and your patch (rather, applied it to my file) and I 
can confirm we are seeing the correct To: address.

The boys here are happy, thank you for your assistance.

Lund


Mark Martinec wrote:
> Lund,
> 
>> Still need to hack source to get the "To:" that was actually used
>> in the email?
> 
> The following patch achieves what you want.
> You need 2.5.0-pre2 or later (preferebly the latest: -pre4)
> to pull this trick.
> 
> --- amavisd~  Thu Apr  5 20:57:28 2007  
> +++ amavisd   Thu Apr 12 17:18:15 2007
> @@ -19193,6 +19193,6 @@
>  BANNED contents (%F) in mail|VIRUS (%V) in mail]\
>   TO YOU from [?%s|<>|[?%o|(?)|%s]]
> -To: [? %#T |undisclosed-recipients: ;|[<%T>|, ]]
> -[? %#C |#|Cc: [<%C>|, ]]
> +[? [:header_field|To] |To: undisclosed-recipients:;|To: [:header_field|To]]
> +[? [:header_field|Cc] |#|Cc: [:header_field|Cc]]
>  Message-ID: <[EMAIL PROTECTED]>
> 
> 
>> I'm a little confused then. Using my latest example, I send EICAR test
>> string to "[EMAIL PROTECTED]", which is accepted by the host that handles
>> email for "sony" and "microsoft". The email is forwarded to the host
>> running postfix+amavisd.
> 
> Ok. So the envelope recipient address should contain @microsoft,
> assuming you did not rewrite recipient addresses through a virtual
> mapping _before_ content filtering. Even if you did, the envelope
> recipient address should preferably be distinguished from other
> domains handled by this MTA, e.g. our-host.handling-mail-for-ms.example
> 
>> (The headers will show it came from host "sony" 
>> due to reverse DNS picking the first entry only).
> 
> The sender address is irrelevant to recipient notifications.
> 
>> The email TO: addess IS [EMAIL PROTECTED]
>> The quarantine email has "[EMAIL PROTECTED]"
> 
> Ok.
> 
>> The notify recipient email sent by Amavisd has "To: [EMAIL PROTECTED]".
> 
> Only if your MTA rewrote it to @sony by its virtual mapping.
> That is certainly possible, although somewhat counterproductive.
> 
>> At no point did we specify "sony" in the original email.
>> To the user, this is not really acceptable.
> 
> If MTA would have the following in its setup (assuming Postfix):
> 
>   mydestination = sony, microsoft, etc
> 
> there would be no need to rewrite recipient addresses,
> it would be accepted as local by this MTA for any
> of its listed domains.
> 
>   Mark
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> AMaViS-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/amavis-user
> AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
> AMaViS-HowTos:http://www.amavis.org/howto/
> 

-- 
Jorgen Lundman       | <[EMAIL PROTECTED]>
Unix Administrator   | +81 (0)3 -5456-2687 ext 1017 (work)
Shibuya-ku, Tokyo    | +81 (0)90-5578-8500          (cell)
Japan                | +81 (0)3 -3375-1767          (home)

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
AMaViS-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to