Wietse Venema:
> Viktor Dukhovni:
> > On Sat, Nov 24, 2012 at 03:09:59PM -0500, Wietse Venema wrote:
> >
> > > > > Any help greatly appreciated! Patrick
> > > >
> > > > Postfix built-in mechanisms to add recipients are "reliable" in the
> > > > sense that the sender will be informed of delivery errors.
> > > >
> > > > To add a recipient without notification, use an smtpd_proxy_filter
> > > > that copies command and replies without modification, and that adds
> > > > the additional recipients as
> > > >
> > > > RCPT TO:<additional-recipient> NOTIFY=NONE
> > > >
> > > > (this requires Postfix 2.3 or later).
> > >
> > > Plus, it requires that all systems down-stream from Postfix correctly
> > > implement RFC 3461 (the SMTP DSN extension).
> >
> > 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.
I've been fixing documentation bugs as I run into them, time
permitting.
Wietse
