Hi
Ive got two servers running amavisd-new using spamassassin both with
equal MX preference, now im using bayes with mysql DB and my one box
has a higher hit rate than the other ,
1st = %35.6: BAYES_99=4.3
2nd = %87.7: BAYES_99=4.3
and obvisouly the server with the lower his rate is letting
The first public pre-release of amavisd-new 2.4.3 is available at:
http://www.ijs.si/software/amavisd/amavisd-new-2.4.3-pre2.tar.gz
It is primarily a maintenance release over 2.4.2 with fixes for
known problems, although a couple of more straightforward features
were added as well, mostly as
I know this is OT, but I do have to ask...
I've tried to get amavis-stats 0.1.21 up and running, but with no big
success. I can't get it to show tabs and buttons.
Anyone? If you feel it's too OT for the list, please respond privately.
--
Anders Norrbring
Norrbring Consulting
R.Smits,
Difficult problem. I want to apply a different spamassassin rule to the
outgoing mail stream. I know about the policy bank MYNETS.
I want to block all the mail to the internet with a specific string in
the subject. But I do not want to apply this rule to the incoming stream.
You
# sa-learn -L --spam and spamassassin -L -r learn the same spam differently.
SA version 3.13, using db or sql database, doesn't seem to matter,
--sync or not --sync, doesn't matter.
Also, it doesn't matter if I run sa-learn --spam or spamassassin -r first.
Further, spamassassin -r and sa-learn
amavis wrote:
Hi,
My settings are as follows in amavisd.conf
$sa_tag2_level_deflt = 3.1;
$sa_kill_level_deflt = 9.0;
So suppose I want the mails which have a score of equal to or greater
than 3.1 and less than 9.0 to go to a separate spam box for that
domain . Above 9.0 the mail
One possibility is to add a SA test which checks on a particular
Received header field (like some specific internal IP address),
and conditionalize the other test (using meta rules).
P.S. here is another possibility: let SA know through a header field
about which policy banks were loaded at
Ilo wrote:
Hi
Ive got two servers running amavisd-new using spamassassin both with
equal MX preference, now im using bayes with mysql DB and my one box
has a higher hit rate than the other ,
1st = %35.6: BAYES_99=4.3
2nd = %87.7: BAYES_99=4.3
and obvisouly the server with the lower
Sysadmin,
My settings are as follows in amavisd.conf
$sa_tag2_level_deflt = 3.1;
$sa_kill_level_deflt = 9.0;
So suppose I want the mails which have a score of equal to or greater
than 3.1 and less than 9.0 to go to a separate spam box for that
domain . Above 9.0 the mail is discarded.
Ilo,
Ive got two servers running amavisd-new using spamassassin both with
equal MX preference, now im using bayes with mysql DB and my one box
has a higher hit rate than the other ...
Gary V wrote:
you could have them both use one database (possibly on another
machine)
That is probably
Philipp,
We are using amavisd to scan incoming mails for viruses.
While we are manageing our imap with courier imap and virtual users,
we can't use procmail ...
what's the most simple way to scan all incoming mails for viruses but
only mails to maildomain.de additionally for spam?
Hi
I've been using SQL lookups on amavisd-new 2.4.2 for a couple weeks
with relative success.
Today I was looking at amavisd-new logfile (debuglevel 4) and I got
surprised when I noticed that '$sql_select_policy' query was being
performed twice for each email
At 13:10 05.09.2006, you wrote:
I know this is OT, but I do have to ask...
I've tried to get amavis-stats 0.1.21 up and running, but with no big
success. I can't get it to show tabs and buttons.
the rest is working?
Anyone? If you feel it's too OT for the list, please respond privately.
if the
MK [ [EMAIL PROTECTED] ] skrev:
At 13:10 05.09.2006, you wrote:
I know this is OT, but I do have to ask...
I've tried to get amavis-stats 0.1.21 up and running, but with no big
success. I can't get it to show tabs and buttons.
the rest is working?
Anyone? If you feel it's too OT for the
On 05/09/06 11:39, Mark Martinec wrote:
The first public pre-release of amavisd-new 2.4.3 is available at:
http://www.ijs.si/software/amavisd/amavisd-new-2.4.3-pre2.tar.gz
The use IO::Select line in the Courier patch has got misplaced again. In
fact it is no longer necessary, because now
Hello,
Another way to beat my problem is the next.
In the subject of a mail , 2 strings has to excist.
Like : greetings and dear friend
Greetings in the beginning
Dear friend case insensitive
I use a meta rule.
header __OFFICE_1 Subject =~ /^greetings/
header __OFFICE_2 Subject =~ /dear
I also tried,
meta SOLUTION __OFFICE_1 + __OFFICE2
and
meta SOLUTION __OFFICE_1 __OFFICE2
instead of
meta SOLUTION (__OFFICE_1 + __OFFICE2)
Also no luck
Greetings..
-
Using Tomcat but need to do more?
17 matches
Mail list logo