Hi guys,
I've got this task to set up a Postfix based mail gateway that will act as primary MX and filter the email for spam (with amavisd-new/spamassassin) before transporting it to the backend Microsoft Exchange environment. So far nothing odd. But the thing is that I even need to set up a Cyrus IMAP instance, locally on the Postfix gateway that will recieve a copy of every incoming e-mail as well. The logic behind this setup is to have some kind of "disaster solution", if Exchange environment would be down, an email would still be avaiable in Cyrus IMAP so users can authenticate themseleves and reach it. I have no clue how to do this, I've been searching the net, looking through manuals, not a single clue how I can have these both transports at the same time. Could some kind of BCC be solution? Please note that this Cyrus IMAP should be entirely "autonomous". It should not be in any kind of synch with Exchange except for reception of a copy of every single incoming e-mail on the domain.

What I need, to start with, is the clues which parameters in Postfix I need to look into to point the email transport to both of these directions at the same time. By following documentation I can only see picture how to either send mail to Cyrus or forward to Exchange, but not both at the same time. As for the authentication / accounts and other specific things regarding the environment - I'll figure that out myself. I just need to know now how I can use transport_maps to forward the e-mail to Exchange and at the same time send a copy to local IMAP on the server.

Thanks in advance for any tip!

Try always_bcc

Hi, and thanks for the reply.
I was suspecting, like written before, some of the bcc-options should do the trick. My intention is not to bcc to an optional address. Cyrus will have identical e-mail addresses to those that will exist in Exchange environment as well. So only a single bcc-option in Postfix won't do the trick, I assume (or am I missing something?). As soon as transport_maps directive is set pointing smtp to Exchange for that domain, Cyrus (listening localy on lmtp socket) is being ignored by Postfix, nothing will get there. Therefore, I assume something else needs to be done so the transport goes both ways.

Thanks in advance.

Ah I see .. sorry, I'm not aware of any easy way to do that

Thanks anyway.
PS.
If you happend to know a _complicated_ way of solving this, that one will do too :=)

I was thinking of a policy daemon, postfix supports policy daemons which can inspect mail during the connection and before it's submitted to the queue, but then you wouldn't have the actual content. Maybe a custom filter that fits in where amavis or spamassassin would ... ?