O Luns 25/07/2005 ás 17:58, Michel Bouissou dicía...
This e-mail is a bit old, but I have a couple of comments about this:
> I ran into something exactly similar about 3-4 months ago. I could
> solve it only by deleting from system.log all entries older (and
> including) the day where the problem began (the first day with empty
> stats).
> It's quite probable that in some situations dspam generates
> system.log entries that the CGI cannot parse. I haven't investigated
> this in much depth, but it's well know that dspam doesn't escape
> some characters from messages subjects (i.e. bare LFs) when logging
> them to system.log, and this can cause unexpected line feeds to be
> found in the log file.
I've also found this problem in my installations (DSPAM 3.4.9). I
guess that dspam.cgi could be easily modified for it to parse
correctly the log file. I'll have a look if I find some time :)
Meanwhile, attached to this mail is a little perl script that fixes
the system.log so dspam.cgi shows the right stats.
Usage:
$ ./dspam-fix-logs.pl < system.log > new-system.log
Hope it helps.
-- Alberto García González Ingeniero en Informática mailto:agarcia@igalia.com Igalia, S.L. http://www.igalia.com Telf. +34 981 91 39 91 ext. 16 Fax. +34 981 91 39 49
This archive was generated by hypermail 2.1.8 : Thu Sep 29 2005 - 13:51:29 EDT