Suresh Ramasubramanian wrote:
>
..[snip]...
>
> And if
>
> > #Turn Off duplicate syslog logging of messages
> > syslog_duplication = false
>
> was the case, you'd be seeing double logging of everything, not just
> rejects.
>
--
No, No, No, and NO, please read Section 45.4...
http://www.exim.org/exim-html-4.30/doc/html/spec_toc.html#TOC361
And here are a few excerpts from the manual...
The use of syslog does not change what Exim logs or the format of its
messages
..[snip]...
mainlog is mapped to LOG_INFO
rejectlog is mapped to LOG_NOTICE
paniclog is mapped to LOG_ALERT
Many log lines are written to both mainlog and rejectlog, and some are
written to both mainlog and paniclog, so there will be duplicates if these
are routed by syslog to the same place. You can suppress this duplication
by setting syslog_duplication false.
..[snip]...
the following would be the result of a typical rejection message to mainlog
(LOG_INFO), each line in addition being preceded by the time, host name,
and pid as added by syslog:
[1/3] 2002-09-16 16:09:43 16RdAL-0006pc-00 rejected from [127.0.0.1](ph10):
..[snip]...
The same error might cause the following lines to be written to
"rejectlog" (LOG_NOTICE):
..[snip]...
[1/14] 2002-09-16 16:09:43 16RdAL-0006pc-00 rejected from [127.0.0.1(ph10):
And from Section 14.23
http://www.exim.org/exim-html-4.30/doc/html/spec_toc.html#TOC162
..[snip]...
syslog_duplication
Type: boolean
Default: true
When Exim is logging to syslog, it writes the log lines for its three
separate logs at different syslog priorities so that they can in principle
be separated on the logging hosts. Some installations do not require this
separation, and in those cases, the duplication of certain log lines is a
nuisance. If syslog_duplication is set false, only one copy of any
particular log line is written to syslog. For lines that normally go to
both the main log and the reject log, the reject log version (possibly
containing message header lines) is written, at LOG_NOTICE priority. Lines
that normally go to both the main and the panic log are written at the
LOG_ALERT priority.
--EAL--
