On 16.06.2011 16:13, Wietse Venema wrote:
karave...@mail.bg:
I thought that sender_bcc_maps/recipient_bcc_maps are options to
the cleanup process, not smtpd. Will smtpd pass this informations
somehow to the cleanup process? If it could be done in this way,
I could use it and the patch is not nee
As an example of how sender_bcc_maps might be specified only in a
single specific context, here is what I have been doing for some
time now.
I wanted to generate BCC copies for every message submitted by my
users (family members). In the "submission" stanza of my master.cf,
I include the followin
karave...@mail.bg:
>I thought that sender_bcc_maps/recipient_bcc_maps are options to
>the cleanup process, not smtpd. Will smtpd pass this informations
>somehow to the cleanup process? If it could be done in this way,
>I could use it and the patch is not needed.
Correct. this happens in cleanup no
- Цитат от Victor Duchovni (victor.ducho...@morganstanley.com),
на 16.06.2011 в 05:27 -
Or this?
/etc/postfix/master.cf
smtp inet n - n - - smtpd
submission inet n - n - - smtpd
-o sender_bcc_maps=maptype:mapname
As the OP observed, correctly, this won't work since bcc is don
On Wed, Jun 15, 2011 at 07:44:53PM -0400, Wietse Venema wrote:
> > We do not use it before/after filter. The setup is that BCC mapping
> > is only needed for sending outgoing mail (we send a copy to the
> > "Sent" folder) so we enable BCC mapping by default (in main.cf)
> > and disable it on defau
- Цитат от Wietse Venema (wie...@porcupine.org), на 16.06.2011
в 02:44 - Wietse:
Apparently you can't use receive_override_options=no_address_mappings
because you need virtual alias or canonical mapping on both sides
of the filter?
karave...@mail.bg:
We do not use it before/af
Wietse:
> Apparently you can't use receive_override_options=no_address_mappings
> because you need virtual alias or canonical mapping on both sides
> of the filter?
karave...@mail.bg:
> We do not use it before/after filter. The setup is that BCC mapping
> is only needed for sending outgoing mail (
- Цитат от Wietse Venema (wie...@porcupine.org), на 16.06.2011 в 01:18 -
karave...@mail.bg:
Hello,
For our setup here we needed to selectively disable BCC mappings
without disabling the other mappings. So attached is a patch that
adds this capability to receive_override_options . It does
karave...@mail.bg:
> Hello,
>
>For our setup here we needed to selectively disable BCC mappings
>without disabling the other mappings. So attached is a patch that
>adds this capability to receive_override_options . It does not
>change any other behavior.
I don't understand this.
Apparently you c
On Thu, Jun 16, 2011 at 12:44:36AM +0300, karave...@mail.bg wrote:
> For our setup here we needed to selectively disable BCC mappings without
> disabling the other mappings. So attached is a patch that adds this
> capability to receive_override_options . It does not change any other
> behavior.
Hello,
For our setup here we needed to selectively disable BCC mappings without
disabling the other mappings. So attached is a patch that adds this capability
to receive_override_options . It does not change any other behavior.
The patch is against v2.8.3. I hope that it will be integrated in
11 matches
Mail list logo