On Wed, 9 Aug 2006, Jakob Hirsch wrote:
> Quoting Nico Erfurth:
>
> > "${if def:received_for{X-Envelope-To: <${received_for}>\n}}");
> >
> > If I'm not wrong, received_for can't be set while the mime/content ACLs
> > are running, but I wasn't sure.
>
> I don't know that, but according to the spec, it is only set if there is
> exactly one recipient, which is bad. I sent a small patch to this list a
> while ago, replacing it with $recipients. Nobody seemed to care about
> it, though.
The whole point of $received_for is that it is included in the default
definition of Received:. Therefore, it cannot be set if there is more
than one recipient, because otherwise you may reveal bcc: recipients to
the other recipients, who are not supposed to know about them.
The *only* reason for the existence of $received_for is so that it can
be used in the value of received_header_text.
There is already a variable called $recipients, but it is set only in
situations (documented) where it is OK for all the recipients to be
know. Expansion of received_header_text is not one of those situations.
--
Philip Hazel University of Cambridge Computing Service
Get the Exim 4 book: http://www.uit.co.uk/exim-book
--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details
at http://www.exim.org/ ##
