----- Цитат от 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 not
change any other behavior.
I don't understand this.
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?
I would expect that such things either before or after the
filter but not on both sides.
Wietse
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).
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.
Best regards
Luben
