a) I think the "LASTACTION' log entry is rendering the "Deleting Spam from/to" log entry obsolete. It contains the action, the from and to to - all information that is redundant with other log lines (see "red" sample below)
This will be changed in the next release.
b) Once an email is "bypassing whitelisting" then all other "bypassing" tests are mood. The "mid" log might just as well not report the outcome of the other "bypassing" tests (or even skip over them). See "green" sample below.
This would be more difficult to accomplish, as the logging is currently done as the test is run -- and while we could easily stop further bypasswhitelist tests from being run (which would prevent the extra log file entries), there is a chance that someone may count on those other bypasswhitelist tests being run for some obscure reason. There are other ways that we could get around this, but they would require more work.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000.
Declude Virus: Ultra reliable virus detection and 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.
