Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: exim: dev
[Bug 859] New: Invalid syntax in log_message is not detected
 

Index | Next | Previous | View Flat


john.horne at plymouth

Jun 29, 2009, 8:22 AM


Views: 456
Permalink
[Bug 859] New: Invalid syntax in log_message is not detected

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=859
Summary: Invalid syntax in log_message is not detected
Product: Exim
Version: 4.69
Platform: Other
OS/Version: Linux
Status: NEW
Severity: bug
Priority: medium
Component: ACLs
AssignedTo: nigel[at]exim.org
ReportedBy: john.horne[at]plymouth.ac.uk
CC: exim-dev[at]exim.org


Hello,

Using exim 4.69 on CentOS 5.3.

In the ACL for the 'DATA' command I had the following:

warn condition = ${if >= {$spam_score_int} {80} }
log_message: LOGGING: Spam message seen: $spam_score_int

Note that the keyword 'log_message' is followed by a colon rather than an '='.
Exim ran okay with this. I only noticed it because our logs were not showing
any spam being received. Once I changed the ':' to an '=', then I started to
get the log entries.

I would have expected a panic log entry, or 'exim -bV' to pick something up,
but neither occurred.

(Sorry, but I'm right in the middle of reconfiguring a mailhub, so I haven't
tested this any further. I thought I should report it before I forget.)



John.


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

--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##

Subject User Time
[Bug 859] New: Invalid syntax in log_message is not detected john.horne at plymouth Jun 29, 2009, 8:22 AM

  Index | Next | Previous | View Flat
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.