Re: question about recipient/sender_bcc_maps limitation

2008-07-31 Thread kyoku cocinillas
mouss escribió: kyoku cocinillas wrote: Hi, i am also interested in this feature, with the aliases i can figure out where to route all the incoming email without having to use the recipient_bcc_maps, but i cant find a workaround for the sender_bcc_maps, i can only configure one email accoun

Re: question about recipient/sender_bcc_maps limitation

2008-07-31 Thread kyoku cocinillas
mouss escribió: kyoku cocinillas wrote: Hi, i am also interested in this feature, with the aliases i can figure out where to route all the incoming email without having to use the recipient_bcc_maps, but i cant find a workaround for the sender_bcc_maps, i can only configure one email accoun

Re: question about recipient/sender_bcc_maps limitation

2008-07-30 Thread mouss
kyoku cocinillas wrote: Hi, i am also interested in this feature, with the aliases i can figure out where to route all the incoming email without having to use the recipient_bcc_maps, but i cant find a workaround for the sender_bcc_maps, i can only configure one email account, and i would lik

Re: question about recipient/sender_bcc_maps limitation

2008-07-30 Thread Victor Duchovni
On Wed, Jul 30, 2008 at 05:24:31PM +0200, kyoku cocinillas wrote: > >The BCC address is subject to virtual alias expansion (and aliases(5) > >expansion for any resulting local recipients). > > Hi, i am also interested in this feature, with the aliases i can figure > out where to route all the inc

Re: question about recipient/sender_bcc_maps limitation

2008-07-30 Thread kyoku cocinillas
Victor Duchovni escribió: On Thu, Jul 10, 2008 at 08:04:25PM -0300, Leonardo Rodrigues Magalh?es wrote: Hello Guys, From http://www.postfix.org/postconf.5.html i have: sender_bcc_maps (default: empty) Optional BCC (blind carbon-copy) address lookup tables, indexed by sender a