I don t know if it is feasible (or maybe it is already in place) to have
separate junk mail files in the Imail\Declude directory like
$low$.junkmail, $mid$.junkmail, $high$.junkmail so that separate filtering
levels could be set for different individuals more easily.
I think the REDIRECT
Dan,
Unfortunately we don't currently have a demo/trial version of LogTool available.
However, we will be adding additional screenshots to the website
(http://www.netcomm.com/products/logtool) later today, which should give you a better
idea of how the application works. If you have additional
Title: Message
Hi;
Just thought to
share this finding with the group.
We made BASE64 a
test with ROUTETO to admin. We also added a filter
with:
HEADERS
1 CONTAINS
Content-Transfer-Encoding: base64
The high weight
was simply to allow us to put a filter in the mail client to move the
Hey scott, ever thought about adding a special action keyword like
FORCE, to force an action in the odd situation where you want to
override the the severity scale? It would only need to be handled in the
.junkmail files.
Thanks,
Chuck Frolick
ArgoNet, Inc.
-Original Message-
From:
Hey scott, ever thought about adding a special action keyword like
FORCE, to force an action in the odd situation where you want to
override the the severity scale? It would only need to be handled in the
.junkmail files.
That does sound like it could be useful. It might be a bit difficult for
his in the entry in my GLOBAL.CFG file:
WHITELIST FROM @info.weightwatchers.com
This is a snippet from the e-mail that was held. I have a hold weight of
20.
X-Declude-Sender: [EMAIL PROTECTED] [216.73.90.161]
X-Declude-Spoolname: D51ea12ef00562fee.SMD
X-Note: This E-mail was scanned by Declude
his in the entry in my GLOBAL.CFG file:
WHITELIST FROM @info.weightwatchers.com
This is a snippet from the e-mail that was held. I have a hold weight of 20.
X-Declude-Sender: [EMAIL PROTECTED] [216.73.90.161]
X-Declude-Spoolname: D51ea12ef00562fee.SMD
X-Note: This E-mail was scanned by
It is my understanding from the docs that Declude Pro does not have per USER
whitelisting. Is this correct?
Whitelisting in its current form only works in the global.cfg file, so it
can't be used on a per-user or per-domain basis.
However, the next release will allow for per-user and
However, the next release will allow for per-user and per-domain
whitelisting.
Great. Any idea on release date?
David
---
[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
However, the next release will allow for per-user and per-domain
whitelisting.
Great. Any idea on release date?
No clue yet, sorry.
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the
10 matches
Mail list logo
