> amavis[12119]: (12119-01) spam_scan: score=0 tests=[none]
> Sorry, I missed it. Not good. And puzzling.\
Make sure we hit at least one test. In local.cf set:
header TEST100 Subject =~ /./
score TEST100 .001
reload amavisd-new then test again and see if you at least get:
spam_scan: score=
amavis[12119]: (12119-01) spam_scan: score=0 tests=[none]
Sorry, I missed it. Not good. And puzzling.
---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make
Frank wrote:
> Gary,
>> > It seems that Amavis or SpamAssassin are ignoring the $sa_* settings in the
>> > configuration files, no matter what I change.
The files are read in order, make sure you are not making changes that
are replaced by settings in one of the other files. They recommend you
p
Gary,
Gary V johnmecham.com> writes:
> > It seems that Amavis or SpamAssassin are ignoring the $sa_* settings in the
> > configuration files, no matter what I change.
> Then I suspect you have a procmail recipe or other program calling
> spamassassin after it leaves amavisd-new.
> grep 'SPAM FRO
The Debian 2.3 and 2.4 versions of amavisd-new ignore amavisd.conf. If
you are in fact using the Debian version (and have not replaced
amavisd-new with the original amavisd) then you would edit the files
in /etc/amavis/conf.d/ to configure amavisd-new. I assume you have been
doing this, is this cor
> @debug_sender_maps = ( ['[EMAIL PROTECTED]'] );
Oops. The SENDER'S address should go here, not the recipient's.
Gary V
---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated
Frank wrote:
> There are no errors in the 0.log file and some hits:
> pts rule name description
> -- --
> 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines
> 0.2 MISSING_HEADERS
Hi Gary,
Gary V johnmecham.com> writes:
> > Amavis always has Hits: 0., expect the test spam mail I've sent. Is that
> > normal?
> No. Could be wrong but it appears SpamAssassin is broken. Get a sample
> mail (something other than the gtube), feed it to spamassassin in debug
> mode as the amavis
Frank wrote:
> Amavis always has Hits: 0., expect the test spam mail I've sent. Is that
> normal?
> May 11 00:19:03 asterix amavis[20852]: (20852-01) Passed CLEAN,
> [213.165.64.20]
> [84.158.46.189] <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>, Message-ID:
> <[EMAIL PROTECTED]>, mail_id: ay+4oblm
Gary,
Gary V johnmecham.com> writes:
> > X-Spam-Status: Yes, score=1000 tag=-999 tag2=5 kill=10 tests=[GTUBE=1000]
> Everything looks OK. You dug this one out of the local quarantine.
> Is there another MTA or MUA that may be removing the headers as the
> non-spam mail makes its way to your mail
Frank wrote:
> Return-Path: <[EMAIL PROTECTED]>
> Delivered-To: spam-quarantine
> X-Envelope-From: <[EMAIL PROTECTED]>
> X-Envelope-To: <[EMAIL PROTECTED]>
> X-Quarantine-ID:
> X-Spam-Flag: YES
> X-Spam-Score: 1000
> X-Spam-Level:
>
Gary V johnmecham.com> writes:
> > Do you know how to configure Amavis to add X-Spam headers to every mail
> > no matter how high the spam results are?
> You mean no matter how low.
Yes :)
> What domain was the mail addressed to? It's possible $mydomain has a
> bad value. You may want to set it
Frank wrote:
> But I still don't see any headers added from SpamAssassin to the
> incoming mails. $sa_tag_level_deflt is set to -999.0 so I expect every
> mail to have some X-Spam headers but these are only inserted if a mail
> is really spam.
> Do you know how to configure Amavis to add X-Spam h
Gary V wrote:
> As I said, either comment out these 2 lines, or uncomment the 4 lines
> in 15-content_filter_mode. Given this choice, I would comment these 2
> out.
If I read this thread correctly, you are suggesting commenting out the
lines in /usr/share/amavis/conf.d/20-package. I would strongly
Gary,
Gary V johnmecham.com> writes:
> >> > All is commented out so everything is enabled - right?
> >> Not on Debian.
> As I said, either comment out these 2 lines, or uncomment the 4 lines
> in 15-content_filter_mode. Given this choice, I would comment these 2
> out.
That did the trick, Amavis
Gary wrote:
> It's the double negatives and the perverse method of undoing one
> setting by enabling another setting that is confusing. It would have
> been better if they had left it alone and simply had:
> # @bypass_virus_checks_maps = (1); # uncomment to DISABLE anti-virus code
> # @bypass_sp
Frank wrote:
> Gary,
> Gary V johnmecham.com> writes:
>> > All is commented out so everything is enabled - right?
>> Not on Debian.
>> They have this perverse method of enabling/disabling these checks.
>> Either uncomment these or look in one of the files in
>> /usr/share/amavis/conf.d/ and comm
Gary,
Gary V johnmecham.com> writes:
> > All is commented out so everything is enabled - right?
> Not on Debian.
> They have this perverse method of enabling/disabling these checks.
> Either uncomment these or look in one of the files in
> /usr/share/amavis/conf.d/ and comment out the lines that
Frank,
> I don't think that it's disabled as every line is a comment on
> 15-content_filter_mode. I did not change/create black/whitelists
> and the mail was very small (body contained only one word).
It must be specific to Debian as Gary notes. Check port documentation.
It is not disabled in the
Frank wrote:
> Hi Gary,
> Gary V johnmecham.com> writes:
>> On a stock Debian install spam and virus checks are disabled by
>> default. Have you enabled them? If I recall, look in
>> 15-content_filter_mode.
> I have not enabled them but I think they were enabled by default:
> use strict;
> #
Mark,
Mark Martinec ijs.si> writes:
> > > Still no headers from Amavis:
> "Hits: -" indicates that SA was not even called.
> Either it is disabled/bypassed, or sender is black/whitelisted,
> or mail size was over the $sa_mail_body_size_limit.
I don't think that it's disabled as every line is a c
Hi Gary,
Gary V johnmecham.com> writes:
> On a stock Debian install spam and virus checks are disabled by
> default. Have you enabled them? If I recall, look in
> 15-content_filter_mode.
I have not enabled them but I think they were enabled by default:
use strict;
# You can modify this file to
Frank,
> > I have the same result for incoming mail:
> >
> > May 10 15:56:17 asterix amavis[13446]: (13446-04) Passed CLEAN,
> > [213.165.64.20] [84.158.46.189] <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>,
> > Message-ID: <[EMAIL PROTECTED]>, mail_id: Kj637E1PMotj,
> > Hits: -, 139 ms
> > Still no
Frank wrote:
> Mark,
>> > What can I do to get Amavis adding headers into the mails?
>> *Recipient* domains must be in local_domains_acl (or related lookups).
>> In your example the recipient domain is list.ee.ethz.ch, which is
>> not local. Outbound mail does not get spam headers inserted inte
Mark,
> > What can I do to get Amavis adding headers into the mails?
> *Recipient* domains must be in local_domains_acl (or related lookups).
> In your example the recipient domain is list.ee.ethz.ch, which is
> not local. Outbound mail does not get spam headers inserted intentionally.
I have t
25 matches
Mail list logo
