On Mon, 23 Dec 1996, Philip Hazel wrote:
ph10 >We had a discussion about this on the list a few weeks ago. (I know you
ph10 >are new to the list since then.) The RFC mandates that if any resent-
ph10 >headers are present, these should be treated as the working set of
ph10 >headers, and then there has to be at least one of To, Cc or Bcc. Exim's
ph10 >rules for a missing To, Cc, or Bcc header (at least one is required)
ph10 >cause it to add a To header if (and only if) the envelope is coming in
ph10 >from a list of addresses on the command line. In other circumstances it
ph10 >adds an empty Bcc header. In the next version of Exim there will be an
ph10 >option requesting that it always add an empty Bcc header in all cases.
I read up on the list and found a good solution. I think the
way exim handles the situation is ok. Just add a hint somewhere in the
documentation that this is a known issue with smartlist.
--- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---
PGP Public Key = FB 9B 31 21 04 1E 3A 33 C7 62 2F C0 CD 81 CA B5
