[syslog-ng]Reciving data from non RFC compliant devices

I just got another syslog-generating machine to monitor, and it seems it doesn't follow the syslog RFC as it sends out messages with ^I (tabs). I was thinking about hacking syslog-ng in such way it will enforce RFC compliance of the "message" part for the data. Basically I am thinking about replacing char <= 31 and char >= 127 with a space. Question: - Any reason why _not_ to do this? - Which function is the best place to hack the code in? Best regards Michael Boman -- Michael Boman Security Architect, SecureCiRT Pte Ltd http://www.securecirt.com