I originally wanted to implement the logic at the data (or any) ACL but the issue I ran into was that I can't seem to specify a custom log file, only main/reject/panic. If this is not the case then it changes everything (for the better!)
I want to have the events written to a separate log because of the way the logs are picked up for processing. We are using flume to pick up these events, which doesn't like tailing live logs so we rotate every 5 minutes and place the event log into a folder where it is picked up. There is a logstash agent tailing the live mainlog and sending events to elasticsearch (but not the events generated by the system filter). As for why we have both flume and logstash... different projects, different history. I can't change the past ;) -----Original Message----- From: Exim-users [mailto:[email protected]] On Behalf Of Ted Cooper Sent: Thursday, February 04, 2016 5:53 AM To: [email protected] Subject: Re: [exim] can I suppress the "message frozen by system filter" log line? On 04/02/16 20:46, Heiko Schlittermann wrote: > 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.) The other ACL is called in this instance: acl_smtp_notquit - ACL for non-QUIT terminations http://www.exim.org/exim-html-current/doc/html/spec_html/ch-access_control_lists.html#SECTNOTQUITACL -- ## 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/ -- ## 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/
