Raman,
Amavisd seems to skip spam scoring for some emails with BAD HEADER alerts:
X-Amavis-Alert: BAD HEADER SECTION, Missing required header field: Date
I'm not aware of spam tests being bypassed based on bad header, except when
a message is already known to be blocked for some other reason
Amavisd seems to skip spam scoring for some emails with BAD HEADER alerts:
X-Amavis-Alert: BAD HEADER SECTION, Missing required header field: Date
This is very similar to a problem previously reported on this list:
http://old.nabble.com/BAD-HEADER-not-being-Spam---scored-td26201700.html
I too
I take the opportunity of this thread to ask about one behaviour, that I
think is not uncommon. Has sense today to set defaults destiny values
for spam to D_BOUNCE? I mean this: today 99.9% of SPAM comes from
a faked email address, so bouncing it to the sender means to a faked
sender
Mark Martinec wrote:
Carlos,
how do I reject messages that have a high score of something like '5'?
X-Spam-Score: 11.543
$sa_kill_level_deflt = 6.31;
$final_spam_destiny = D_BOUNCE;
Yes, that should suffice. To block a message, $final_spam_destiny must
not be D_PASS,
Giuseppe Ghibò wrote:
Mark Martinec wrote:
Carlos,
how do I reject messages that have a high score of something like '5'?
You can't.
Spamassassin requires that your mail server actually accept the message
before it can be scanned because it needs to analyze the
On Sun, Mar 22, 2009 at 08:35:22PM +0100, Giuseppe Ghibò wrote:
I take the opportunity of this thread to ask about one behaviour, that I
think is not uncommon. Has sense today to set
defaults destiny values for spam to D_BOUNCE? I mean this: today 99.9%
of SPAM comes from
a faked email
I have Amavisd-new installed and configured however I am trying to
understand how it works. It appears to be scoring my incoming messages
like SpamAssassin would however it appears I have SA installed but not
running:
This is fine however when I get a message, I do see in the headers
that someone
$sa_spam_subject_tag = '***SPAM*** ';
$sa_tag_level_deflt = 2.0; # add spam info headers if at, or above that
level
$sa_tag2_level_deflt = 6.31; # add 'spam detected' headers at that level
$sa_kill_level_deflt = 6.31; # triggers spam evasive actions
$sa_dsn_cutoff_level = 10; # spam
On Fri, Mar 20, 2009 at 9:13 AM, Michael Scheidell scheid...@secnap.net wrote:
Final destination set for pass?
This does not make sense to me. Can you be more specific? Am I missing
this parameter in the config file I am looking at? Does that go
somewhere else in
the /etc/amavis/conf.d file?
On Fri, Mar 20, 2009 at 9:40 AM, Alexander Wirt formo...@formorer.de wrote:
See 20-debian_defaults
$final_virus_destiny = D_DISCARD; # (data not lost, see virus
quarantine)
$final_banned_destiny = D_BOUNCE; # D_REJECT when front-end MTA
$final_spam_destiny = D_BOUNCE;
Carlos Williams schrieb am Friday, den 20. March 2009:
On Fri, Mar 20, 2009 at 9:13 AM, Michael Scheidell scheid...@secnap.net
wrote:
Final destination set for pass?
This does not make sense to me. Can you be more specific? Am I missing
this parameter in the config file I am looking at?
Carlos,
how do I reject messages that have a high score of something like '5'?
X-Spam-Score: 11.543
$sa_kill_level_deflt = 6.31;
$final_spam_destiny = D_BOUNCE;
Yes, that should suffice. To block a message, $final_spam_destiny must
not be D_PASS, score must be above kill level, and
Jeff wrote:
Hi,
I'm trying to understand how the scoring is working through amavisd-new
and spamassassin. According to the spamassassin docs,
http://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_Conf.ht
ml#scoring_options
score set 3 is used when Bayes is enabled and
13 matches
Mail list logo
