Scott-
I think this is a great idea.
Once we know a message has passed the delete limit, why would we want to
keep testing it in routine operations? Of course, we'd need to be able to
turn it off when needed for debugging or whatever, but it would save a lot
of processing time under normal condit
I may seem small, but the SKIPIFWEIGHT functionality seems overly
cumbersome to use. I don't like defining the same lines repeatedly for
each test. I would like to place the HOLDIFWEIGHT and/or DELETEIFWEIGHT
lines in the $default$.junkmail file. Or in any per domain/per user
.junkmail file. Th
Any progress on the fix for the syntax
a:host.domain.name/nn
Yes, it was fixed in the first interim release that was released on or
after January 13.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude
Here is a case where a message was NOT DELIVERED to either user because
one user had it blocked (weight10=HOLD). Even though the second
recipient has only IGNORE for all tests and the log file has "L2 Message
OK," the message was not delivered but moved to the spam folder instead.
Correct. That
> I'm thinking this could be accomplished by Declude passing in a
> current score and having the individual external tests handle what
> they do on their own. I'm thinking that this might already be
> possible though, but I'm not sure about what order they are
> processed in
Hi Scott:
Any progress on the fix for the syntax
a:host.domain.name/nn
?
---
[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 "unsub
To:
[EMAIL PROTECTED] [EMAIL PROTECTED] IP: 63.252.12.191 ID:
01/21/2004 18:25:50 Q188610910132b08a Tests failed [weight=94]:
WAMCHECK=IGNORE MYFILTERPASS=IGNORE SPFFAIL=IGNORE WEIGHT10=IGNORE
WEIGHT15=IGNORE WEIGHT20=IGNORE
This is the Imail log (no reference to this message after the 4th line)
So if a message comes in for 50 users from say, [EMAIL PROTECTED], and any
one of those users has it whitelisted, everybody gets it regardless of
its failed tests?
That is correct. That's how SMTP was designed.
We did add a "bypasswhitelisting" option to help with this (where if the
total weigh
>
>
> >If a message comes in and is whitelisted by any of the recipients
> >(using WHITELISTFILE in a user.junkmail file), the message gets
> >whitelisted for all recipients!
>
> That is correct. That is by the design of SMTP, where a
> single E-mail can
> have multiple recipients -- but it
I think that ordering the grouping would be great, but group all of the
text based filters together and let their order of appearance dictate
when they get run. Right now custom filters do work like that, and I
did work carefully with my ordering and SKIPIFWEIGHT settings in order
to improve p
I'm not sure how much of an impact the RBL lookups have in terms of
processing, but I'm thinking this is very small compared to the rest. If
Declude doesn't yet do this, performance here could be improved by only
querying an RBL once regardless of the code that you are looking for, so
for ins
Title: Message
I had
a similar problem last month being caused by a beta release of SNIFFER.
There is a new final release version of SNIFFER available. You also may
want to just turn off SNIFFER (in your global.cfg file) to see if that is
causing the problem
Bill
-Original Mess
BADHEADERS caught the following E-mail for the Message ID. I'm not sure
if this is an RFC issue or not though, thinking that it might be due to
the fact that the ID starts with a period, or maybe because it includes a
comma??? Could you clarify that this is definitely a valid BADHEADERS hit?
If a message comes in and is whitelisted by any of the recipients (using
WHITELISTFILE in a user.junkmail file), the message gets whitelisted for
all recipients!
That is correct. That is by the design of SMTP, where a single E-mail can
have multiple recipients -- but it is expected that the E-ma
I can’t speak as to the internal
organization of Junkmail. It might be very difficult to separate
the similar tests from each other. Perhaps the similar tests could be
grouped and the group could be placed in an order with other tests.
As to the tests we would like to see run
first,
Imail v8
Declude v1.77i22
I have found what I am assuming is unintended actions with whitelisting
and multiple recipients:
If a message comes in and is whitelisted by any of the recipients (using
WHITELISTFILE in a user.junkmail file), the message gets whitelisted for
all recipients!
Another thi
Scott,
BADHEADERS caught the following E-mail for the Message ID. I'm not sure
if this is an RFC issue or not though, thinking that it might be due to
the fact that the ID starts with a period, or maybe because it includes
a comma??? Could you clarify that this is definitely a valid BADHEADER
Ok thanks Scott, that makes sense.to confirm, but the only global.cfg
file that will be used under any condition is the top level global.cfg file
within the Imail/declude directory
thanks again for all your support
gb
At 03:04 PM 1/21/2004 -0500, you wrote:
My understanding, that once you
I can't get this whitelisted any suggestions? The path to the filter file
is valid.
HEADERS WHITELIST CONTAINSnewtonwall.com
The "WHITELIST" option in filters requires the latest interim release (from
http://www.declude.com/interim ).
I was going to ask about this. If filters support this, only the most
recent interim release could be used. I think this might have been
Scott's way of announcing new functionality :)
Matt
Kris McElroy wrote:
I can't get this whitelisted any suggestions? The path to the filter file
is val
I can't get this whitelisted any suggestions? The path to the filter file
is valid.
GLOBAL.CFG
FILTER_GoodHEADERS filter D:\IMail\Declude\goodheaders.txt
x 0 0
GOODHEADERS.TXT
HEADERS WHITELIST CONTAINSnewtonwall.com
Received: fr
Todd,
The RBL's and the built in Declude tests are very efficient. The RBL's
also go off all at once essentially, so there is no good way to stagger
them one by one.
I think it would be great though if Declude allowed us to set a
SKIPIFWEIGHT value for FROMFILE's, IPFILE's, SPAMDOMAIN's and
Thanks Guys,
After Scott looked the logs, Declude is performing as it should be. It was
using the default.junkmail per the individual domain directory.
I was just expecting that I could have individual global.cfg files per each
domain and in turn could have different log files and filters, etc.
Can I whitelist something like this:
WHITELIST HEADERS Containsnewtonwall.com
No, "WHITELIST HEADERS" is not defined, and "Contains" isn't used in
whitelists.
If you want to use a whitelist, you can use "WHITELIST ANYWHERE
newtonwall.com" in the \IMail\Declude\global.cfg file.
I
Can I whitelist something like this:
WHITELIST HEADERS Containsnewtonwall.com
Thanks,
Kris
---
[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 t
My understanding, that once you have a directory for a domain, you must have
a $default$.junkmail file in there, otherwise no action will be taken at
all.
The per-domain config file (\IMail\Declude\example.com\$default$.JunkMail
file) is actually not required.
If a per-user config file exists, D
> Once that is right, you just need to put in the folders your user.junkmail
> files for each user that needs different settings than whats in the the
> root
> $default$.junkmail (i.e. you don't need a $default$.junkmail in each
> domains
> folder UNLESS you want different defaults specifically for
The per-domain folders need to be the official host name as in IMail, so if
your setup is like this in Imail:
Official host name: mail.domain1.com, alias: domain1.com
Official host name: mail.domain2.com, alias: domain2.com
... then your folders for declude need to be:
mail.domain1.com
mail.domai
Scott? Do you have an estimated timeframe for the newest "official"
release?
I'm seeing lots of betas go by with some cool features but I prefer to
wait until they are all packaged into one.
It is very hard to say. We do plan to have a new beta shortly (hopefully
within 1-2 weeks), but can't say
Scott? Do you have an estimated timeframe for the newest "official"
release?
I'm seeing lots of betas go by with some cool features but I prefer to
wait until they are all packaged into one.
Sharyn
We are the worldwide producer and marketer of the award winning Cruzan
Single Barrel Rum, judged
The following has been suggested before and is similar:
- Allow the Declude admin to set the order of test processing and stop
processing if the weight reaches a specified limit.
Your concern at the time was:
- If the admin places the tests in the wrong order it would be possible
to exceed maximum
Is there a test, in the works, that will end all processing of
any further filters. Basically, exit all Declude processing, or is it
best to use the SKIPWEIGHT, thanks,
There isn't anything like that in the works now, but it is something that
we may end up adding.
First, try using $default$.junkmail as the file name.
John Tolmachoff
Engineer/Consultant/Owner
eServices For You
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
> [EMAIL PROTECTED] On Behalf Of Glenn Brooks
> Sent: Wednesday, January 21, 2004 7:05 AM
> To: [EMAI
My spool directory just started filling up recently and Imail
is not delivering any messages to local mailboxes. It appears to be sending
messages outbound. I am using Imail v 7.07 with declude junkmail and virus
1.77 i12. I have moved all the Q*, D* files from the spool directory
Scott,
Is there a test, in the works, that will end all processing of
any further filters. Basically, exit all Declude processing, or is it
best to use the SKIPWEIGHT, thanks,
Keith
-Original Message-
From: R. Scott Perry [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 21, 2
That is all correct (just one note to clarify, though: END will stop
processing that one filter, but other tests will run).
-Scott
At 10:35 AM 1/21/2004, Keith Johnson wrote:
We are giving our Declude filters an overhaul this week, adding in all
the functionality
We are giving our Declude filters an overhaul this week, adding in all
the functionality of the new 'beta' tests and I wanted to ensure I am
good on the following:
Using Examples SKIPWEIGHT 70
MAXWEIGHT 60
MINWEIGHT 20
MAXWEIGHT: If during the run of the fi
I have $default.junkmail$ files in each of the directories for each domain
as well as global.cfg files.
Any other suggestions, one client especially is running out of patience on
this problem.
Anyone at Declude have any ideas why the per-domain feature would not be
working?
The best way to det
I have $default.junkmail$ files in each of the directories for each domain
as well as global.cfg files.
Any other suggestions, one client especially is running out of patience on
this problem.
Anyone at Declude have any ideas why the per-domain feature would not be
working?
gb
At 11:54 PM 1/2
You meed to put a default.junkmail file in the directories. The
golbal.config is just that global and can not be modified to work for just
one domain.
Kevin Bilbee
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Glenn Brooks
> Sent: Tuesday, January 2
I am not able to get the per domain feature of pro to work.
Imail running about 60 domains
About 5 of them need to have custom settings.
domain1.com is the top level primary domain and all config files are in the
declude directory
E:\imail\declude\
inside the declude directory are directories
41 matches
Mail list logo
