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 (we send a copy to the
> "Sent" folder) so we enable BCC mapping by default (in main.cf)
> and disable it on default smtpd that handles incoming mail (we
> obviously need the other mappings there but do not need bcc mappings).
I see. What about using this instead?
/etc/postfix/master.cf
smtp inet n - n - - smtpd
-o sender_bcc_maps=
submission inet n - n - - smtpd
/etc/postfix/main.cf:
sender_bcc_maps = maptype:mapname
Or this?
/etc/postfix/master.cf
smtp inet n - n - - smtpd
submission inet n - n - - smtpd
-o sender_bcc_maps=maptype:mapname
I am reluctant to add no_bcc_mappings, because that would make BCC
mappings be a special case, and special cases make systems more
difficult to understand.
To avoid the special case, I'd have to also implement support for
no_canonical_mappings, no_virtual_alias_mappings, and for
no_address_masquerade. Otherwise, people would be wondering why
they can turn off one feature and not the other.
> The setup is somewhat unusual but it was decision made a long time
> ago. I would not argue if this is a good idea but the reason is
> every client (even clients with POP3 setup) to have copy of the
> sent mail. Until now it was working with separate instance of
> Postfix just for this (and separate instance for SPAM filtering
> etc). I find easier to care for one postfix config (instance) than
> a number of them. So I am in a process of consolidating them.
Beware, as you add -o options in master.cf you have, it becomes
harder to change one thing without breaking another thing.
Wietse
