Since we house mulitple domains (using spam filtering) and this
filter test is used in the Global file it seems it would fail every other
domain email (i.e. 1000 weight) that we house on the same box?! Is there
a way to only define it for use in the default config file for that
03, 2003 7:55 AM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] Need aid on Declude Header rule
Since we house mulitple domains (using spam
filtering) and this
filter test is used in the Global file it seems it would
fail every other
domain email (i.e. 1000 weight
I have a customer who only wants to get email to a list of valid
employees, no one else (i.e. ex-employees). However, the list of
ex-employees is too long for him to come up with, thus he gave me the
list of valids. I looked, but I don't think Declude has a HEADER tag
called DOESNOT CONTAIN,
I have a customer who only wants to get email to a list of valid
employees, no one else (i.e. ex-employees). However, the list of
ex-employees is too long for him to come up with, thus he gave me the
list of valids. I looked, but I don't think Declude has a HEADER tag
called DOESNOT CONTAIN,
Scott,
The problem with using the CONTAINS is that I would have to have
a list of the ex-employees and the only list he can put together is the
good employees. Thus if I used the CONTAINS I would be hitting good
employee email. Any other suggestions, thanks for your time.
Keith
What
Karen,
My bad, I failed to mention this is a Store and Forward
domain...
Keith
-Original Message-
From: Karen D. Oland [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 02, 2003 12:07 PM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] Need aid on Declude Header rule
Delete the nobody alias. Then, only valid email in his domain will be
accepted. Delete all old employees not on the list of valid names you just
received from the domain.
-Original Message-
From: Keith Johnson
The problem with using the CONTAINS is that I would have to have
a
Keith,
What about at the client end? Could he not filter at his mail server to
refuse mail for non-local users?
It sounds like you need a to version of MAILFROM -- then you could delete
all those that failed the test. Perhaps a domain rule that tests for each
of his vlalid user names and adds
CONTAINS *would* work in this way. For example:
HEADERS -1000 CONTAINS [EMAIL PROTECTED]
HEADERS -1000 CONTAINS [EMAIL PROTECTED]
...
In this case, an E-mail with [EMAIL PROTECTED] in the headers
would always receive a weight less than 0. You can then create a
Scott,
SWEET, that is a great idea, I'll give it a go, you are the man.
Keith Johnson
CONTAINS *would* work in this way. For example:
HEADERS -1000 CONTAINS [EMAIL PROTECTED]
HEADERS -1000 CONTAINS [EMAIL PROTECTED]
...
In this case, an E-mail with
]
Cc:
Subject: RE: [Declude.JunkMail] Need aid on Declude Header rule
Scott,
SWEET, that is a great idea, I'll give it a go, you are the man.
Keith Johnson
CONTAINS *would* work in this way
I spoke to soon. If I use the weighting method, it hurts my
ability to use the Weight system to guard them against Spam. Your thoughts...
Ah, I see.
In that case, you can have the same filter, but instead of having it
defined as MYFILTER filter C:\IMail\Declude\myfilter.txt x -1000
: [Declude.JunkMail] Need aid on Declude Header rule
I spoke to soon. If I use the weighting method, it hurts my
ability to use the Weight system to guard them against Spam. Your
thoughts...
Ah, I see.
In that case
13 matches
Mail list logo
