Re: Sending mail to custom transport and second server
- Original Message - From: Jeroen Geilman jer...@adaptr.nl To: postfix-users@postfix.org Sent: Tuesday, 5 June, 2012 7:51:47 PM Subject: Re: Sending mail to custom transport and second server recipient_bcc_maps = hash:/etc/postfix/backup_domains, with the following content: @example.netcatch...@second.postfix.box Depending on your specific setup, there may be much better solutions, but this is what you asked for verbatim. Actually, this is not really what I meant. This BCCs everything to one e-mail address. What I would like, is to have a transport with two nexthops, so to speak. I need the primary server to deliver to its zarafa transport as well as relay to the secondary server. The secondary server then knows to which address it was sent and places the X-Original-To and Delivered-To.
Re: Sending mail to custom transport and second server
Jeroen Geilman: @example.netcatch...@second.postfix.box Depending on your specific setup, there may be much better solutions, but this is what you asked for verbatim. Wiebe Cazemier: Actually, this is not really what I meant. This BCCs everything to one e-mail address. What I would like, is to have a transport with two nexthops, so to speak. I need the primary server to deliver to its zarafa transport as well as relay to the secondary server. The secondary server then knows to which address it was sent and places the X-Original-To and Delivered-To. That functionality is provided by the pcre-based sender_bcc_maps solution - it makes one secondary delivery for each recipient. I guess by now we have covered all options available in existing Postfix releases. Wietse
Re: Sending mail to custom transport and second server
- Original Message - From: Jeroen Geilman jer...@adaptr.nl To: postfix-users@postfix.org Sent: Tuesday, 5 June, 2012 7:51:47 PM Subject: Re: Sending mail to custom transport and second server recipient_bcc_maps = hash:/etc/postfix/backup_domains, with the following content: @example.netcatch...@second.postfix.box Depending on your specific setup, there may be much better solutions, but this is what you asked for verbatim. I'll look into it when I'm back at work tomorrow. However, I'm all for better solutions. The way Postfix receives and delivers is basically made clear; it receives because example.net is mydestination, so it considers it to be local, and then it delivers using the zarafa transport. Any alternatives for setting up a machine that acts as real-time backup are welcome.
