recipient_bcc_maps
in [Postfix]
|
From: Stan Hoeppner on 29 Apr 2010 09:02 I'm current using recipient_bcc_maps to forward spam trap emails to a dnsbl. I've been asked by another dnsbl to provide them the same trap data. According to recipient_bcc_maps, I can't bcc to more than one address. I thought of creating a local alias that expands to both addresses and bcc'ing that local alias address, but my further reading of recipient_bcc_maps says I can't do that either. How can I accomplish this "simple" task? I'm using 2.5.5. Thanks. -- Stan
From: Wietse Venema on 29 Apr 2010 10:05 Stan Hoeppner: > I'm current using recipient_bcc_maps to forward spam trap emails to a dnsbl. > I've been asked by another dnsbl to provide them the same trap data. > According to recipient_bcc_maps, I can't bcc to more than one address. As documented. > I > thought of creating a local alias that expands to both addresses and bcc'ing > that local alias address, but my further reading of recipient_bcc_maps says > I can't do that either. I don't see any text that _bcc_maps recipient are given other treatment than non-BCC recipients. Wietse
From: Stan Hoeppner on 29 Apr 2010 13:49 Wietse Venema put forth on 4/29/2010 9:05 AM: > Stan Hoeppner: >> I'm current using recipient_bcc_maps to forward spam trap emails to a dnsbl. >> I've been asked by another dnsbl to provide them the same trap data. >> According to recipient_bcc_maps, I can't bcc to more than one address. > > As documented. > >> I >> thought of creating a local alias that expands to both addresses and bcc'ing >> that local alias address, but my further reading of recipient_bcc_maps says >> I can't do that either. > > I don't see any text that _bcc_maps recipient are given other > treatment than non-BCC recipients. > > Wietse Thanks Wietse. I was misreading this Note: automatic BCC recipients are produced only for new mail. To avoid mailer loops, automatic BCC recipients are not generated for mail that Postfix forwards internally, nor for mail that Postfix generates itself. to mean that bcc'ing to a local virtual_alias_maps address that expands to multiple remote addresses fell under "internal forwarding". I assume now that my example would be "internal processing" not "internal forwarding". -- Stan
From: Wietse Venema on 29 Apr 2010 14:31 Wietse: > I don't see any text that _bcc_maps recipient are given other > treatment than non-BCC recipients. Stan Hoeppner: > Thanks Wietse. I was misreading this > > Note: automatic BCC recipients are produced only for new > mail. To avoid mailer loops, automatic BCC recipients > are not generated for mail that Postfix forwards internally, > nor for mail that Postfix generates itself. > > to mean that bcc'ing to a local virtual_alias_maps address that expands to > multiple remote addresses fell under "internal forwarding". I assume now > that my example would be "internal processing" not "internal forwarding". I can clarify this text by changing it to: automatic BCC recipients are not generated after Postfix forwards mail internally, or after Postfix generates mail itself. It's just one more item for the documentation checklist: - Instead of "Postfix", "server" or "client" write "Postfix SMTP server", "remote SMTP client", and so on. We're pretty good on that one. - Instead of "when", make the dependency clear with words like "before", "after", etc. There is some work left here. Wietse
|
Pages: 1 Prev: relayhost and transport_maps Next: smtpd ldap query causes session to hang with postfix 2.6.2 |