Luca Bertoncello <lucabert@???> (Mi 18 Mär 2015 07:28:48 CET):
> Hello list!
>
> Is it possibile to have more exim_mainlog (and exim_rejectlog, exim_paniclog)
> for more IPs?
Read the spec.
+-------------+---------+------------------+----------------------------+
|log_file_path|Use: main|Type: string list*|Default: set at compile time|
+-------------+---------+------------------+----------------------------+
This option sets the path which is used to determine the names of Exim's log
files, or indicates that logging is to be to syslog, or both. It is expanded
when Exim is entered, so it can, for example, contain a reference to the host
name. If no specific path is set for the log files at compile or run time, they
are written in a sub-directory called log in Exim's spool directory. Chapter 51
contains further details about Exim's logging, and section 51.1 describes how
the contents of log_file_path are used. If this string is fixed at your
installation (contains no expansion variables) it is recommended that you do
not set this option in the configuration file, but instead supply the path
using LOG_FILE_PATH in Local/Makefile so that it is available to Exim for
logging errors detected early on - in particular, failure to read the
configuration file.
You may use expansion there. Take care to use an expansion item that's
available at the time when the log gets opened. ($hostname might be a
good choice, $received_ip_address might be a bad choice when the
delivery process want's to log something…)
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --------------- key ID: F69376CE -
! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -
