At 21:23 21.12.2006, you wrote:
[18829] dbg: locker: safe_lock: trying to get lock on
/var/amavis/.spamassassin/auto-whitelist with 19 retries
lock_method flock
and see if that cures the problem.
If flock does not solve it, try rebuilding the awl database
while discarding entries with
Hi all,
I am sending test mail by doing SMTP manually try to send some spam
mail. But the subject doesn't get tagged, however the body the message
is getting spam tag (**SPAM**). Im running FC3 with postfix,
amavisd spamassassin.
Thanks
Gopinath.U
My amavisd.conf file
My setup is sendmail-milter and the desired effect was to have all the
incoming mail that passed forwarded to another less-able box.
What I used to have was this:
$forward_method = 'smtp:192.168.1.1:25'; # where to forward checked mail
The new config file has this form:
$forward_method =
Walter wrote:
I'm in the process of updating our amavis and spamassassin environ-
ment to 2.4.4 / 3.1.7. Unfortunately, I don't seem to be able to
cope with the following problem:
X-Spam-Report header is not in the format needed
- spamassassin's report template is not used
I'm in the process of updating our amavis and spamassassin environ-
ment to 2.4.4 / 3.1.7. Unfortunately, I don't seem to be able to
cope with the following problem:
X-Spam-Report header is not in the format needed
- spamassassin's report template is not used
Spamassassin's
Walter wrote:
Now it is always like...
X-Spam-Report: * 0.3 IAI_00055 BODY: about.the.company
* 0.2 IAI_00138 BODY: indicative of future resu|ts
... which might be the default format. The template lines
speciala and specialb are missing.
As I'm using those special rules
The 3.7 minutes is well below 8 minutes of $child_timeout, so
amavisd does not time out on this message.
If MTA times out with waiting earlier than in 3.7 minutes,
you end up with mail message being send, one copy at every
attempt: amavisd successfully processes and forwards the
Nicklas,
I finally found the root of the problem. The QMQP code in qmail have
hardcoded timeouts set. 10 seconds for connect and 60 seconds for
read/write. If amavisd processing takes longer than 60 secs you get the
early MTA connection drop.
I found the following patch by Eric Hess on the
Dne ct 21. prosince 2006 16:49 Ondrej Cecak napsal(a):
When is Spamassassin called from amavisd-new, allways give examined email
same score -- CRM114_SPAM_00; after some tries to debug I noticed that when
amavisd starts, loads crm114.pm as plugin, SA after registering glue method
for check_crm
[ I'm sorry to reply to my own message but I don't have the 2 replies
to my original message at hand ]
@Gary V:
Thank you for your replies and thanks for the faq-pointer. Yes, I'm
aware of that and I did not assume that spamassassin is adding headers
itself in this environment.
As far as I
On Fri, Dec 22, 2006 at 23:54:44 +0100, Walter Steiner wrote:
amavisd-new calls check_mail() which calls spam_scan() which calls
a function named check() which calls SA routines.
sub check...
...
...
$spam_summary = $per_msg_status-get_report; # taints $1 and $2 !
#
Walter,
$spam_summary = $per_msg_status-get_report; # taints $1 and $2
# $spam_summary = $per_msg_status-get_tag('SUMMARY');
$spam_report = $per_msg_status-get_tag('REPORT');
Okay... it's late and I haven't noticed before:
$spam_report is set to $per_msg_status-get_tag('REPORT')
Ondrej,
When is Spamassassin called from amavisd-new, allways give examined email
same score -- CRM114_SPAM_00; after some tries to debug I noticed that
when amavisd starts, loads crm114.pm as plugin, SA after registering glue
method for check_crm gets CRM114 score -7.1548, which evals
13 matches
Mail list logo
