On Thu, 24 Apr 2003, Oliver Eikemeier wrote:
> The following router/transport combination does not log a delivery as local:
>
> localuser:
> driver = accept
> transport = lmtp_delivery
> log_as_local
>
> lmtp_delivery:
> driver = smtp
> protocol = lmtp
Well, it *isn't* "local" in the Exim sense, is it? "Local" to Exim means
"on this host", and SMTP deliveries are to other hosts...
> but this one does:
>
> localuser:
> driver = accept
> transport = lmtp_delivery
> log_as_local
>
> lmtp_delivery:
> driver = lmtp
The lmtp transport does indeed delivery on the local host.
> /* We start with just the local part for pipe, file, and reply
> deliveries, and for successful local deliveries from routers that have
> the log_as_local flag set. */
My idea was that people would only want this "local" kind of logging for
truly local deliveries.
> Does it make sense not to check for addr->transport->info->local?
I would not like to do this without making it optional because I suspect
there are cases where people use "accept" routers (where log_as_local is
true by default) to send messages to other (usually internal) hosts, and
they expect the "non-local" style of logging. The default for "accept"
was chosen so that Exim 4 by default was more or less compatible with
Exim 3 in this regard. I think one would have to add
"log_remote_as_local" or something to do what you want. Or possibly
invent log_as_local for the transport.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
