Ben Kamen wrote:
Ooo, sounds like Keyword filtering...
bad.. very bad...
You may want to consider adding them to a scoring list in mimedefang's
spamassassin config file instead.
I NEVER reject message because they might have words that are legit or
possibly mispelled.
Not to mention
I was performing an upgrade on 2.51. to 2.58.
Today I have restarted the mimedefang filter only to be greeted with the
following:
md-mx-ctrl status
ERROR MXCommand: connect: No such file or directory: Is multiplexor running?
Hmmm, what did I miss?
Also, how strict are the version numbers
-Original Message-
From: Kelson
I NEVER reject message because they might have words that
are legit or
possibly mispelled.
Not to mention legit words that contain blacklisted words.
Looking for cialis will trigger on specialist, for instance.
Or words that have different
I have recompiled the 2.56 branch of mimedefang, as the upgrade to 2.58
created an unstable result. Now, even the 2.56 branch is an unstable
beast. The problem is exhibited on startup of mimedefang. Without a
load the 4 children (configured minimum) grow their RSS to 1.0G+ and
consume 25%
Albert E. Whale wrote:
I have recompiled the 2.56 branch of mimedefang, as the upgrade to
2.58 created an unstable result. Now, even the 2.56 branch is an
unstable beast. The problem is exhibited on startup of mimedefang.
Without a load the 4 children (configured minimum) grow their RSS to
Albert E. Whale wrote:
I have recompiled the 2.56 branch of mimedefang, as the upgrade to 2.58
created an unstable result. Now, even the 2.56 branch is an unstable
beast. The problem is exhibited on startup of mimedefang. Without a
load the 4 children (configured minimum) grow their RSS to
Locally (and for users on the road) we use port 465 (SMTPS).
Since we trust email on this port, it seems a waste of time to scan
it for Spam.
I figure this is fairly common. Anyone have an issue with the patch:
***
*** 263,269
return if message_rejected();
# Spam
7 matches
Mail list logo
