On 01/10/2013 02:05 AM, Jean-Luc Wasmer wrote:
Hi,
I've searched the mailing lists but every time the proposed solution
involves using sender_bcc_maps (or other form of bcc'ing).
The problem with adding a BCC to the incoming email is that other BCC
headers will be dropped to the recipient of my server-side BCC rule.
What "other BCC headers" ?
You may be confused about RFC822: there is no BCC header, and never has
been.
I want the equivalent of what Mutt calls Fcc, so an actual copy of the
incoming mail, not a new recipient added to it.
That is what always_bcc and its derivatives do.
The idea is to avoid having MUAs send each outgoing email twice (SMTP
submission + IMAP copy).
How is that related to the workings of the MTA ?
If you don't want to store your Sent mail in IMAP, tell your MUA not to
do that.
--
J.