Now tests can be triggered and there is NO trace for that ever having happened?
It has always worked this way. If you don't want the tests logged, they won't be logged.
That can't be good, specially now that filters can be used instead of weights to process "TESTSFAILED".
The filters work on all tests that an E-mail fails (at least ones that fail before the filter is run).
Again, I respectfully submit that at least the SUMMARY line (the last line in the medium log) must be complete, especially if the customer clearly specified "LOG".
As I've said several times, when the LOG action is used, it WILL appear in the "Tests Failed" line.
I don't see the benefit for omitting THOSE entries. I thought the purpose of the medium log was to get rid of all those DETAILED log lines - not to render the "summary" line (and thus the medium log) worthless.
Yes, but in all previous releases no log file entry would be made for these tests.
I know you consider them the same - but: I didn't specify "IGNORE", I specified "LOG" and the manual says: "LOG The LOG action places an entry into the log file (C:\IMail\spool\dec####.log by default)."
And again, that test WILL appear in the "Tests Failed" header.
In any case, for the next release, we will have the "Tests Failed" header include all tests that failed, as it seems to make more sense that way.
-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.
