Re: [Declude.JunkMail] Line Issues
Are you aware of any issues related to filter files in which the log reports and weights against a line in the filter, however, it was the line below or above it that should have got triggered? For example, lets stay that line 39 states: BODY 5 contains @123example.com Line 40 states BODY 20 contains @domain.com If I look in the log, it shows that my filter got tripped at line 40, however if I search for line 40 in the email, it is not there, however, line 39 clearly was. The weight was assigned for line 40. It is as if from time to time, it picks the wrong line (in my case just 1 off). I am running 1.77beta. Hope this makes sense, thanks for the aid. Yes, that is possible under some circumstances. There was a previous version of Declude that could have the line numbers pretty far off, but they should be much more accurate now. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask for a free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
RE: [Declude.JunkMail] Line Issues
Scott, Should I run the latest interim release to fix this issue? Just had a few upset customers, thanks, Keith -Original Message- From: [EMAIL PROTECTED] on behalf of R. Scott Perry Sent: Wed 2/11/2004 8:11 PM To: [EMAIL PROTECTED] Cc: Subject: Re: [Declude.JunkMail] Line Issues Are you aware of any issues related to filter files in which the log reports and weights against a line in the filter, however, it was the line below or above it that should have got triggered? For example, lets stay that line 39 states: BODY 5 contains @123example.com Line 40 states BODY 20 contains @domain.com If I look in the log, it shows that my filter got tripped at line 40, however if I search for line 40 in the email, it is not there, however, line 39 clearly was. The weight was assigned for line 40. It is as if from time to time, it picks the wrong line (in my case just 1 off). I am running 1.77beta. Hope this makes sense, thanks for the aid. Yes, that is possible under some circumstances. There was a previous version of Declude that could have the line numbers pretty far off, but they should be much more accurate now. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask for a free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. winmail.dat
RE: [Declude.JunkMail] Line Issues
Should I run the latest interim release to fix this issue? Just had a few upset customers, thanks, Declude JunkMail won't handle the situation incorrectly, except for reporting a line number that is different than the one you might expect. Declude JunkMail won't use the wrong line in the filter file. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask for a free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
