Re: [AMaViS-user] OT? trying to get lock
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 few hits. If that does not help, your only choice is to switch AWL database to SQL. thank you, flock seems to solve it... Mark - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
[AMaViS-user] Spam tag found in body of message
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
use strict;
$MYHOME = '/var/amavisd';
$mydomain = 'mydomain.com';
$myhostname = 'mymta.mydomain.com';
$daemon_user = 'amavisd';
$daemon_group = 'amavisd';
#$daemon_chroot_dir = $MYHOME;
$QUARANTINEDIR = $MYHOME/quarantine;
$TEMPBASE = $MYHOME/tmp;
$ENV{TMPDIR} = $TEMPBASE;
$helpers_home = $MYHOME;
$max_servers=4;
$child_timeout=20*60; # we need to adjust the timeout since it is not a
localhost transfer
$forward_method = 'smtp:127.0.0.1:10025';
$notify_method = $forward_method;
$inet_socket_port = 10024;
$inet_socket_bind = '127.0.0.1';
[EMAIL PROTECTED] = (read_hash(/var/amavisd/badheader));
@bypass_virus_checks_acl = (1);
#read_hash(\%local_domains, '/etc/postfix/relay_domains');
@local_domains_maps = ([ .$mydomain, '.xyz.co.in']);
$DO_SYSLOG = 0; # (1 = syslog, 0 = logfile)
$LOGFILE = /var/amavisd/amavis.log;
$log_level = 0; # (0-5)
$final_spam_destiny = D_PASS; # Set to D_REJECT, D_PASS to pass through
$final_bad_header_destiny = D_PASS;# D_REJECT, D_BOUNCE, D_DISCARD,
D_PASS
read_hash(\%whitelist_sender, '/var/amavisd/whitelist');
read_hash(\%blacklist_sender, '/var/amavisd/blacklist');
read_hash(\%spam_lovers, '/var/amavisd/spam_lovers');
#defending against mail bombs
$MAXLEVELS = 14;
$MAXFILES = 1500;
$MIN_EXPANSION_QUOTA = 100*1024;
$MAX_EXPANSION_QUOTA = 300*1024*1024;
$path = '/usr/bin:/bin';
$file = 'file';
$gzip = '/usr/bin/gzip'; # location of gzip on your system -
Important!
$enable_db = 1;# enable use of BerkeleyDB/libdb (SNMP
and nanny)
$enable_global_cache = 1;# enable use of libdb-based cache if
$enable_db=1
#If you want to adhere to the principle that postmaster should be able
to receive all mail (except viruses), find and uncomment the following
$spam_lovers{lc([EMAIL PROTECTED])} = 1;
# SpamAssassin settings
$sa_local_tests_only = 0;
$sa_auto_whitelist = 1; # comment this line out to turn off auto
whitelist
$sa_mail_body_size_limit = 64*1024; # 64KB
$sa_tag_level_deflt = 3.0; # controls adding the X-Spam-Status and
X-Spam-Level headers,
$sa_tag2_level_deflt = 6.3; # controls adding 'X-Spam-Flag: YES', and
editing Subject,
$sa_kill_level_deflt = $sa_tag2_level_deflt; # triggers spam evasive
actions:
$sa_spam_subject_tag = '***SPAM*** ';
$sa_spam_modifies_subj = 1;
$sa_debug = 1; # comment this line out to turn off debugging
1; # insure a defined return
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] change in $forward_method from amavisd-new-2.4.2_3, 1 to amavisd-new-2.4.3 trying to understand
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 = 'smtp:[192.168.1.1]:25'; Either form doesn't get me where I wanted to go. Both forms are correct (brackets become useful with IPv6 addresses, which contain colons). But this is irrelevant for a milter setup. The $forward_method should be left at undef in a milter setup - mail is forwarded by MTA itself after it gets a go from a milter, the milter should not forward a message on its own. To make all mail pass, set: $final_virus_destiny = D_PASS; $final_banned_destiny = D_PASS; $final_spam_destiny = D_PASS; $final_bad_header_destiny = D_PASS; Mark - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] amavis 2.4.4, spamassassin 3.1.7 Problem on report format of the X-Spam-Report header
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 Spamassassin's local.cf defines a report template: ... clear_report_template report speciala report _SUMMARY_ report specialb ... Running spamassassin -t -x testmailfile outputs the X-Spam-Report header with the expected format. - SA config seems to be okay! Running amavis/spamassassin outputs the X-Spam-Report header(*), but it is not in the format given in local.cf / got when running spamassassin directly: 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 (IAI_x) in this local.cf file it is for sure that it is read by amavis/spamassassin. - amavis overwrites the report template ? I'm no perl user but I have checked the amavis script and the config file to no avail. I'm not able to find a line supporting the theory about overwriting local.cf's report config definition. If anyone is using amavis 2.4.4 (or 2.4.3) and spamassassin 3.1.7 with a special report template I would be happy to get to know if it is working or not. I would be even more happy if someone could indicate what might be the problem.,-) Thanks in advance, ws All mail (header) editing is done by amavisd-new and not by SA. Even though SA does observe options in its configuration file to rewrite mail body and modify mail header, the result is purposely not used by amavisd-new. http://www.ijs.si/software/amavisd/#faq-spam Gary V - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
[AMaViS-user] amavis 2.4.4, spamassassin 3.1.7 Problem on report format of the X-Spam-Report header
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 local.cf defines a report template: ... clear_report_template report speciala report _SUMMARY_ report specialb ... Running spamassassin -t -x testmailfile outputs the X-Spam-Report header with the expected format. - SA config seems to be okay! Running amavis/spamassassin outputs the X-Spam-Report header(*), but it is not in the format given in local.cf / got when running spamassassin directly: 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 (IAI_x) in this local.cf file it is for sure that it is read by amavis/spamassassin. - amavis overwrites the report template ? I'm no perl user but I have checked the amavis script and the config file to no avail. I'm not able to find a line supporting the theory about overwriting local.cf's report config definition. If anyone is using amavis 2.4.4 (or 2.4.3) and spamassassin 3.1.7 with a special report template I would be happy to get to know if it is working or not. I would be even more happy if someone could indicate what might be the problem.,-) Thanks in advance, ws - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] amavis 2.4.4, spamassassin 3.1.7 Problem on report format of the X-Spam-Report header
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 (IAI_x) in this local.cf file it is for sure that it is read by amavis/spamassassin. I'm no perl user but I have checked the amavis script and the config file to no avail. I'm not able to find a line supporting the theory about overwriting local.cf's report config definition. If anyone is using amavis 2.4.4 (or 2.4.3) and spamassassin 3.1.7 with a special report template I would be happy to get to know if it is working or not. I would be even more happy if someone could indicate what might be the problem.,-) Thanks in advance, ws Do you or do you not have this set?: $sa_spam_report_header = 1; Is it possibly mail is passing through both amavisd-new and spamassassin? It would be interesting to see all the X-Spam headers for this message. Gary V - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] Duplicate mails: archive retained andclamavtimeout [TIMEOUT RESOLVED]
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 message in time, yet MTA gives up earlier, telling the client it hit a temporary failure and that it should re-try later. Fix MTA timeout, it should not give up sooner than $child_timeout time, customarily MTA timeout is set to 20 minutes. Don't know how to set this timeout value\ on qmail. Mark Hi Mark, 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 www.qmail.org page http://www.ehuss.org/qmail/qmqpc-timeout.tar.gz which would be great if you could mention somewere in the amavisd docs. clamav still times out though on zero byte members in compressed (zip) archives. Thanks, Nicklas - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] Duplicate mails: archive retained andclamavtimeout [TIMEOUT RESOLVED]
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 www.qmail.org page http://www.ehuss.org/qmail/qmqpc-timeout.tar.gz which would be great if you could mention somewere in the amavisd docs. That's great news, I'm glad you found the culprit! I'll see that it gets mentioned somewhere, at least in RELEASE_NOTES and in the qmqpqq patch. clamav still times out though on zero byte members in compressed (zip) archives. The 2.4.5-pre1 is delayed somewhat, but I'll ask you to test your sample when I prepare the promised pre-release which will include updated timeouts code for virus scanners. Mark - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] external plugins in SA (WAS: Custom CRM114 plugin in Spamassassin gives allways same score)
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 gets CRM114 score -7.1548, which evals CRM114_SPAM_00 and every other email allways gets this score to tests summary. After some trying I noticed, that amavisd-new calls SA via Mail::SpamAssassin perl module, that seems like problem part -- is it possible to use external plugins in SA, and if yes, could you please tell me how? -- Ondřej Čečák - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] amavis 2.4.4, spamassassin 3.1.7 Problem on report format of the X-Spam-Report header
[ 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 understand the amavisd-new perl code:
amavisd-new calls check_mail() which calls spam_scan() which calls
a function named check() which calls SA routines.
sub check...
...
$which_section = 'SA collect';
{ local($1,$2,$3,$4); # avoid Perl 5.8.0..5.8.3...? taint bug
if ($sa_version=~/^(\d+(?:\.\d+)?)/ $1 = 3) {
$spam_level = $per_msg_status-get_score;
$sa_tests = $per_msg_status-get_tag('TESTSSCORES',',');
$autolearn_status = $per_msg_status-get_autolearn_status;
} else {
$spam_level = $per_msg_status-get_hits;
$sa_tests = $per_msg_status-get_names_of_tests_hit; # only names
}
$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');
I'm using a do_log() function right after the last line to log
$spam_report. I'm getting the same (wrong) values which are later
added to the mail headers in add_forwarding_header_edits_per_recip().
(no big surprise I assume)
I've logged $spam-report in my older amavisd-new / SA combo which
shows the value / format as configured in local.cf.
I don't know what is the difference between the two configurations.
local.cf is the same and the two amavisd.conf are basically the same
in all relevant parts afaik.
And yes, $sa_spam_report_header is set to 1;
Not that I have noticed any difference according to the value of
$spam_report. I think it is just a trigger for adding the header
to the mail message. ... and the header is added!
Is it possibly mail is passing through both amavisd-new and
spamassassin?
I don't know if I understand your last question. Sorry, my english
is poor... isn't it that what I want?
Do you wanted to know, if there is another instance of spamassassin
running on the message besides amavisd-new (seperate SA process)?
I don't believe this is the case. In fact, if I don't let amavisd-new
add the X-Spam-Report header there is no such header in the message.
The X-Spam headers you wanted to see:
X-Spam-Score: 0.5
X-Spam-Level:
X-Spam-Status: No, score=0.5 tagged_above=- required=
X-Spam-Report: * 0.3 IAI_00055 BODY: about.the.company
* 0.2 IAI_00138 BODY: indicative of future resu|ts
The reason why we see an X-Spam-Report header here is that I changed
the code a little bit to alsways get this header. As said before,
the values of $spam_report differ for the running and the new instal-
lation before (- in check())
Maybe this problem is solved in 2007 - now it's holiday time,-)
Thanks for your time and a Merry Christmas! ws
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] amavis 2.4.4, spamassassin 3.1.7 Problem on report format of the X-Spam-Report header
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 !
# $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') which is
apparently not using the report template as configured in local.cf.
In my production version of amavisd-new $spam_report is set to the
output of $per_msg_status-get_report.
In this version of amavisd-new this output is assigned to $spam_summary
as one can see from the piece of code above.
I've changed the amavisd-new code to use $spam_summary instead of
$spam_report and I see my configured report template again.
The output is somewhat broken (wrong line feed in one of the lines
but I'm feeling that I can see the light at the other side of the
tunnel.
I don't know what 'taints $1 and $2' implies bu maybe I'll find some
references to this source change. I haven't found anything useful
before but 'summary' seems to be a good keyword to search for (next
year,-)
Thanks and good night. ws
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] amavis 2.4.4, spamassassin 3.1.7 Problem on report format of the X-Spam-Report header
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') which is
apparently not using the report template as configured in local.cf.
Right. SA is preparing two types of reports: the more baroque one is
appropriate for inclusion in mail body, the leaner one is appropriate
for inclusion in mail header. The change was made to better go along
with SA terminology and target application.
In my production version of amavisd-new $spam_report is set to the
output of $per_msg_status-get_report.
In this version of amavisd-new this output is assigned to $spam_summary
as one can see from the piece of code above.
I've changed the amavisd-new code to use $spam_summary instead of
$spam_report and I see my configured report template again.
That's ok, use whichever fits your purpose best.
The output is somewhat broken (wrong line feed in one of the lines
but I'm feeling that I can see the light at the other side of the
tunnel.
Indeed this is a reason why it is no longer used in later versions.
I don't know what 'taints $1 and $2' implies but maybe I'll find some
references to this source change. I haven't found anything useful
before but 'summary' seems to be a good keyword to search for (next
year,-)
It is mostly a note to myself, pointing to another potential source of
Perl taint problems. The local($1,$2,$3,$4) statement above should take
care of the Perl bug, so I don't expect further problems in that area.
Mark
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] external plugins in SA (WAS: Custom CRM114 plugin in Spamassassin gives allways same score)
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 CRM114_SPAM_00 and every other email allways gets this score to tests summary. After some trying I noticed, that amavisd-new calls SA via Mail::SpamAssassin perl module, that seems like problem part -- is it possible to use external plugins in SA, and if yes, could you please tell me how? SA plugins are handled and loaded entirely by SA mechanisms - *.cf files and/or .pre files in the usual SA directory. The mechanism should behave the same, regardless of SA being invoked through amavisd-new or directly, just make sure to do command-line tests as user amavis/vscan. If the code behaves differently, compare SA debug produced by: # amavisd debug-sa to the one produced by: # su vscan -c 'spamassassin -t -D test.msg' Could you give me please some hits to debug this problem or hopefuly to solve it? I'm using Debian 3.1, = amavisd-new 20030616, spamassassin 3.0.3. Isn't it a waste of time to deal with such old versions? Look at the calendar. Happy New Year! Mark - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
