On Wed, 4 Dec 2002, Marc MERLIN wrote:
> Ok, let me see if I understand.
> - If you return 4xx or 5xx, *return_text is already used to print the
> error message back to the sender, and the value is always made
> available to exim.conf in $local_scan_data
No. The value is used only for the error message. It is not put in
$local_scan_data. There is no point - the message is being rejected, so
it is about to be thrown away.
> - In the case of 2xx, *return_text also gets sent back to
> $local_scan_data,
Yes. (But "only" rather than "also".)
There are two mutually exclusive cases:
(1) Accept the message - text goes to $local_scan_data.
(2) Reject the message - text sent to the client host.
> If I did summarize this correctly, then I understand now. Honestly, I'd
> be very surprized if someone is actually doing the above and relying on
> return_text not being printed in the SMTP ack.
Well, I don't know what people do, but I can imagine people setting text
such as
checked=yes spam-level=4 cookie=xxxxx copy_to_postmaster=no ....
for $local_scan_data which they wouldn't want sent outside.
> I don't think anyone actually replied that making return_text visible in
> the SMTP ok would break anything for them,
I didn't ask that question! Let's ask it now.
If anybody reading this is using the feature for setting
$local_scan_data, would it embarrass you if the text were returned to
the sending client?
But whatever the answers to that are, I don't think it should be
automatically returned. These are texts with entirely different uses;
they should be kept separate.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
