I think I solved it :

127.0.0.1:10025 inet    n       -       n       -       -       smtpd
   -o content_filter=
   -o local_recipient_maps=
   -o smtpd_client_restrictions=permit_mynetworks,reject
   -o mynetworks=127.0.0.0/8
   -o receive_override_options=no_address_mappings
scache    unix  -       -       n       -       1       scache
discard   unix  -       -       n       -       -       discard
tlsmgr    unix  -       -       n       1000?   1       tlsmgr

Hopefully I did this the right way

now each user recieves only one mail, though I got one minor problem :) , the X-ORIGINAL says to either user2 or user3 and not the ORIGINAL user from where it was silently forwarded. Guesss this is lost due to address rewriting ?

Note : I've tried to disable address mappings in /etc/postfix/main.cf , that completely disables recipeient_maps

Sincerely
Robert B
----- Original Message ----- From: "mouss" <mo...@ml.netoyen.net>
To: <postfix-users@postfix.org>
Sent: Tuesday, June 30, 2009 00:29
Subject: Re: recipient_bcc to virtual alias


Robert Becskei a écrit :
Hello,

I have a virtual domain hosting posfix config here with amavisd-new. I
needed to silently bcc any recieved messages from one user to two other
users.
I've managed to do it with help like this

recipient_bcc original user to alias

u...@capriolobike.com -> silental...@capriolobike.com

sliental...@capriolobike.com is an alias for us...@capriolobike.com and
us...@capriolobike.com

The problem is both user2 and user3 recieve the e-mail sent to
u...@capriolobike.com twice, in one mail the X-OGIRIN-TO is
us...@capriolobike.com in the other e-mail
the X-ORIGIN-To is silental...@capriolobike.com

oh please, don't ignore the welcome message. it gives you a useful hint
on how to get help. in particular, the recommended URL will tell you to:
- show output of 'psotconf -n'
- logs (which you've shown. this is much appreciated)
- in your case, the copy of master.cf


If you use a content filter, make sure to disable rewrite before or
after the filter. see the FILTER README for more infos.


Reply via email to