On Sat, 31 Jan 2009, Melvyn Sopacua wrote: > On Friday 30 January 2009 21:12:30 Victor Duchovni wrote: > > On Fri, Jan 30, 2009 at 08:42:22PM -0900, Melvyn Sopacua wrote: > > > 1) Accept mail for example.com as primary MX (yes, possible) > > > 2) Relay to mx2.example.com (yes, possible) > > > 3) If mx2.example.com gives fatal error, reduce to transient and try > > > again later (not sure if relay -o soft_bounce=yes would cover it) > > > > This also will work. > > So to confirm, relay -o soft_bounce=yes in master.cf will reduce any 5xx > replies it receives from the exchange server to 4xx?
Yes, http://www.postfix.org/postconf.5.html#soft_bounce. > > > 4) Magically catch the accepted mail that bounces after completed > > > transaction (mailbox is full primarily. Spoof MAIL FROM: dialog?) > > > > This is getting too "creative". Probably easier to deliver a Bcc stream > > of the mail, and provide access to missed mail on demand. > > Yes, I'm thinking this too. But I'd like to have a log mailed to them (a > seperate account that's not touched by exchange) via cron, so they can see > subjects and senders, so I will probably create a 'backup' service in > master.cf that does all the stuff. It would be equivalent to an alias like > this: > > @example.com localmailbox, |logthis, relay:[mx2.example.com] Hm, and where is this access map syntax documented? -- Sahil Tandon <sa...@tandon.net>
