Hi David,
Are you aware of any bugs with the CONTAINS filter statement?
Thanks!
-Nick
David Barker wrote:
Kevin,
After reviewing your files you had sent me this is the problem you are
having:
1. The email you received was encoded in BASE64 (Msg failed BASE64)
2. In your global.cfg you
Kevin,
After reviewing your files you had sent me this is the problem you are
having:
1. The email you received was encoded in BASE64 (Msg failed BASE64)
2. In your global.cfg you have the following directive:
DECODE OFF
Therefore your STOCKFILTER did not trigger - as nowhere in the
I am talking about :)
David B
www.declude.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nick Hayer
Sent: Tuesday, July 26, 2005 1:19 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Filter not triggering
Hi David,
Are you aware
: RE: [Declude.JunkMail] Filter not triggering
Nick,
I am not aware of any bugs with the CONTAINS filter statement.
However there are some items on our wish list, currently CONTAINS searches
for a string eg. ABC
So this will trigger XXXABCXXX
Currently there is not a way to use CONTAINS
@declude.com
Sent: Tuesday, July 26, 2005 12:26 PM
Subject: RE: [Declude.JunkMail] Filter not triggering
Nick,
I am not aware of any bugs with the CONTAINS filter statement.
However there are some items on our wish list, currently CONTAINS
searches
for a string eg. ABC
So this will trigger XXXABCXXX
No. I used to get nabbed by that, it is the first thing I check when having
problems.
Kevin Bilbee
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Guhl, Markus
(LDS)
Sent: Monday, July 25, 2005 7:22 AM
To: Declude.JunkMail@declude.com
Subject: AW:
I have reported to Declude a problem with the "CONTAINS"
statement. Prior to 2.0.6 (or somewhere around there)it worked
oncharacter match, but after an upgrade to Declude it only works on a word
match. (In other words you could not longer match on a string of characters
within a word.) This
Declude support -
Would you comment on this? Is there a problem with 'CONTAINS' ? Would
you kindly share what other issues are being addresses in 'one they are
testing now' ?
Thanks!
-Nick
John Carter wrote:
I have reported to Declude a
problem with the "CONTAINS" statement.
25, 2005 8:05 AMTo:
Declude.JunkMail@declude.comSubject: RE: [Declude.JunkMail] Filter
not triggering
I have reported to Declude a problem with the "CONTAINS"
statement. Prior to 2.0.6 (or somewhere around there)it worked
oncharacter match, but after an upgrade to Declude it
: [Declude.JunkMail] Filter not triggering
I have reported to Declude a
problem with the "CONTAINS" statement. Prior to 2.0.6 (or somewhere
around there)it worked oncharacter match, but after an upgrade to
Declude it only works on a word match. (In other words you could not
lo
do - we do.
Declude, could you please work on this?
Don
- Original Message -
From:
Matt
To: Declude.JunkMail@declude.com
Sent: Monday, July 25, 2005 1:47 PM
Subject: Re: [Declude.JunkMail] Filter
not triggering
Kevin,Just a thought if you wanted to confirm this a
@declude.com
Sent: Monday, July 25, 2005 11:16
AM
Subject: RE: [Declude.JunkMail] Filter
not triggering
Well
that would explain why many of my filters are not as effective as they used to
be. Has Declude announced when the fix will be
available
Kevin Bilbee
12 matches
Mail list logo
