|
There has always been corruption of the logs. What seems to have
changed here is that there is a new log format and the programmed
exceptions in DLanalyzer are no longer able to handle the types of
corruption as seamlessly as in the past. I haven't seen the new log format, but I would imagine that if they built it in a column format and kept it to a single line, similar to Web logging standards, it should be even easier to parse the data and correct for issues. If they didn't keep to consistent columns, then this could be just as big of an issue to parse as before and a lot of the exception rules would have to be rewritten for the new format. Matt Goran Jovanovic wrote: Yesterday's report on my declude logfile showed =...................................1........0.01% 02/28/2005..........................1........0.01% FF156FB0094D05A.....................1........0.01% I005................................1........0.01% QCEA370970074D08A...................1........0.01% SET.................................1........0.01% SNIFFQCE053ABD0086D062..............1........0.01% -- ===================================================== MailPure custom filters for Declude JunkMail Pro. http://www.mailpure.com/software/ ===================================================== |
- RE: [Declude.JunkMail] Log Corruption Colbeck, Andrew
- RE: [Declude.JunkMail] Log Corruption Goran Jovanovic
- Re: [Declude.JunkMail] Log Corruptio... Matt
- Re: [Declude.JunkMail] Log Corru... Scott Fisher
- RE: [Declude.JunkMail] Log C... Andy Schmidt
- Re: [Declude.JunkMail] ... Darrell \([EMAIL PROTECTED])
- Re: [Declude.JunkMa... Scott Fisher
- Re[2]: [Declude.Jun... Pete McNeil
- [Declude.JunkMail] IMAI... Marc Catuogno
- RE: [Declude.JunkMa... Ralph Krausse
- [Declude.JunkMa... Imail Admin
- Re: [Declude.Ju... Darrell \([EMAIL PROTECTED])
- Re: [Declude.Ju... Imail Admin
