Sounds like the problem is in 2.x
I went from 1.79 to 2.05, where can I download 1.82, or can someone send it
to me?
Thanks
Chuck
- Original Message -
From: Erik [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, March 07, 2005 12:16 PM
Subject: RE: [Declude.JunkMail]Log
There is an issue with 2.0+ and the DELETE action when there's a certain
type of configuration used. Declude seems to be aware of it, but no
official notice or known issues have been posted; other then from user's
of DECLUDE.
We've elected to revert back to 1.82 (with the subject fix) for the
Below is a line from my declude log file. I was able to get the message
ID from my syslog and then went to my declude log file and found this.
Could someone explain to me why this was caught?
It was not caught:
03/25/2004 08:44:52 Qe2520a28017a22f2 Tests failed [weight=0]:
IPNOTINMX=IGNORE
I've noticed the tests HOUR and IPNOTINMX are preceded by an n in mylogs,
such as nHOUR and nIPNOTINMX.
That means that the a weight was applied because an E-mail did *not* fail
the test.
HOURhour6 20 0 1
IPNOTINMX ipnotinmx x x
Has anyone else noticed bad log lines in the JM log? I will get a short
spurt of partial log entries, usually without a newline to separate
them, occasionally just the end of an entry on a line by itself. Never
seems to last more than a minute. It can really mess with log analysis.
Yes, I
