Hi, Erik Browning <[email protected]> (Mi 03 Feb 2016 22:42:22 CET): … > Lately our requirements have changed and I have implemented some custom logic > and log generation through an exim system filter. The problem I have is that > with "queue_only" set the messages don't generate the log event right away > because the system filter only runs on message delivery. I tested a setup > where the "queue_only" is disabled an the system filter freezes the message > for later delivery. This writes the log events in a timelier fashion but > produces a lot of "system frozen by message filter" warnings that I would > like to suppress. We process ~100,000,000 messages/day so that is a lot of > extra data to collect/process in our logging system and I am actively trying > to cut down all the extraneous log lines that I can (eg: retry time not > reached).
Can't you implement the new requirement in the DATA acl or even in the
QUIT acl? (About QUIT I'm not sure if it fires even on connection loss
after the final dot.)
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 ------------ -
signature.asc
Description: Digital signature
-- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
