Victor Duchovni put forth on 3/6/2011 3:05 PM: > On Sun, Mar 06, 2011 at 03:48:34PM -0500, Charles Marcus wrote: > >> On 2011-03-05 9:29 PM, Stan Hoeppner wrote: >>> always_bcc is exactly what I would do >> >> But isn't there a problem with the loss of all of the headers when using >> always_bcc and if so, isn't that a problem with respect to most of the >> laws mandating email archival? > > Not headers, envelope. You lose the envelope recipient list. That's > why recipient_bcc_maps is better, since one can encode the original > recipients into the bcc recipient list.
I was unaware of this envelop loss issue with always_bcc. Thanks Viktor. So in the OP's case, would he want to use something like /etc/postfix/recipient_bcc @hisdomain.tld [email protected] to send a copy of every inbound mail, with envelop info, to his downstream archiving host MTA? Also, probably of interest to the OP, is there a way around sending bounces back to the sender? I would think in the OP's scenario he wouldn't want this. It would be very confusing to the remote sender, as the actual recipient probably did receive such mail, but a problem with archive server caused the bcc copy to be bounced. Thus the sender may think the email didn't get through to the recipient. There are probably many others reasons one wouldn't want such bounced bcc mail going back to original senders. -- Stan
