[exim-dev] [Bug 1317] New: DCC logging & debug tidyup

Top Page
Delete this message
Reply to this message
Author: Graeme Fowler
Date:  
To: exim-dev
Subject: [exim-dev] [Bug 1317] New: DCC logging & debug tidyup
------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1317
           Summary: DCC logging & debug tidyup
           Product: Exim
           Version: N/A
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: ACLs
        AssignedTo: graeme@???
        ReportedBy: graeme@???
                CC: exim-dev@???



Created an attachment (id=596)
--> (http://bugs.exim.org/attachment.cgi?id=596)
dcc log & debug cleanup

A couple of days ago I noticed that the DCC code logged to the rejectlog if
Exim couldn't make a socket connection to the DCC daemon. For a short while I
thought we were dropping mail until I realised that (a) it returns an ACL defer
under those circumstances, and (b) we had /defer_ok on the call to DCC.

However, it struck me that this should either be in the mainlog or the
paniclog. Additionally, the log string didn't actually say this was from a DCC
lookup, so I went digging in the code to find it.

Patch sets the log messages to go into PANIC rather than REJECT log (which is
what the malware calls do when they fail to connect).
It also prefixes each log line and debug print line with "DCC - " to make it
clear where they're coming from.

Sanity check required!


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email