Bug 2928 - spamd syslog to system log (not maillog) on message with control chars in ID
Summary: spamd syslog to system log (not maillog) on message with control chars in ID
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 2.61
Hardware: PC Linux
: P5 normal
Target Milestone: 2.70
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-15 09:39 UTC by Mick Szucs
Modified: 2004-01-15 02:27 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Message with control characters in ID text/plain None Mick Szucs [NoCLA]
patch against spamd.raw patch None Malte S. Stretz [HasCLA]
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mick Szucs 2004-01-15 09:39:48 UTC 
Posted about this on the satalk list and Malte E. Stretz suggested that I open 
a bug report on it, so here goes. 
 
Using spamd/spamc under Redhat 9, spamassassin 2.61.  Got a message the other 
day that resulted in a spamd message being logged to /var/log/messages, as 
opposed to /var/log/maillog where it belongs, with control characters making 
things pretty ugly. 
 
The resulting line in /var/log/messages was: 
 
Jan 9 14:39:23 tachi xïc\202^A^_0Â`\202^A^[\204/ for onramp:10010. 
 
A little concerned that these control chars have allowed this message to jump 
log files. 
 
I'm attaching the message that was responsible for this to this ticket, per 
Malte's request. 
 
Regards, 
 
Mick
Comment 1 Mick Szucs 2004-01-15 09:42:50 UTC 
Created attachment 1695 [details]
Message with control characters in ID
Comment 2 Malte S. Stretz 2004-01-15 09:59:40 UTC 
Thanks. What a message. I think I've rarely seens such broken trace headers. 
Let's see what it gives...
Comment 3 Malte S. Stretz 2004-01-15 10:54:46 UTC 
Created attachment 1696 [details]
patch against spamd.raw

ok, I'll apply a patch similar to this to HEAD. it will be in 2.70.
Comment 4 Malte S. Stretz 2004-01-15 11:27:36 UTC 
Will be fixed in 2.70.