Cyborg <cyborg2@???> (Sa 29 Jun 2013 12:37:03 CEST):
> Hi,
>
> where is the right place to place the "no_message_logs" option ?
Just put it in the global part of your config. If you search for
/^|message_logs/ in the spec.txt, you'll find about the following:
+------------+---------+-------------+-------------+
|message_logs|Use: main|Type: boolean|Default: true|
+------------+---------+-------------+-------------+
If this option is turned off, per-message log files are not created in the
msglog spool sub-directory. This reduces the amount of disk I/O required by
Exim, by reducing the number of files involved in handling a message from a
...
The is "Use: main". It refers to the global part, before any
router, transport, …
> btw, i don't think this should be enabled by default. The Mainlog
> tells enough
The mainlog may rotate away. If you've a message, you're loosing
information about the message. And, w/o message_logs you loose the
exim -Mvl <message-id>
command, which is quite handy if you need fast access to the reasons,
why a message is not delivered yet.
On heavily loaded inbound systems we do not use the message logs,
because these systems forward the messages to outbound or storage
anyway. But on the outbound systems we use the message logs.
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: 7CBF764A -
gnupg fingerprint: 9288 F17D BBF9 9625 5ABC 285C 26A9 687E 7CBF 764A -
(gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B)-
