On 24 nov. 2012, at 23:40, Wietse Venema wrote: >>> I believe the same properties hold with recipients added via >>> recipient_bcc_maps (automatic NOTIFY=NEVER up to the last forward-path >>> MTA that supports DSN). Therefore, it may be simpler to use bcc maps, >>> rather than implement a proxy filter or similar. >> >> This is not well documented. I have done another documentation bugfix. > > I have updated the postconf(5) text for always_bcc, recipient_bcc_maps > and sender_bcc_maps. These three primitives use the same code to add > an envelope recipient address. > > Old: > Note: if mail to the BCC address bounces it will be returned to > the sender. > > New: > Note: with Postfix 2.3 and later the BCC address is added as if it > was specified with NOTIFY=NONE. The sender will not be notified > when the BCC address is undeliverable, as long as all down-stream > software implements RFC 3461. > > Note: with Postfix 2.2 and earlier the sender will be notified > when the BCC address is undeliverable.
Ok, that looks great. I'll go with bcc maps then. I'm running Postfix 2.9.x on MX and training servers, so it should be ok. Thank you very much for your help. Patrick
