[Bug 6784] New: meta refresh in HTML-mail should cause a relativly high spamvalue.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6784 Bug #: 6784 Summary: meta refresh in HTML-mail should cause a relativly high spamvalue. Product: Spamassassin Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Rules AssignedTo: dev@spamassassin.apache.org ReportedBy: mybugrepo...@monkz.de Classification: Unclassified Hi I registered a new wave (towards my server) of HTML mails with meta refresh content (see below). (bd-infinity is not my server, but yahoo seems to be the used relay) meta refresh should cause a relativly high spamvalue. Regards X-Amavis-Alert: BAD HEADER SECTION, Non-encoded 8-bit data (char E1 hex): Subject: o \341\271\210\304\273\304\256n-\320\200 \341\271\227\341[...] X-Spam-Flag: NO X-Spam-Score: 1.999 X-Spam-Level: * X-Spam-Status: No, score=1.999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HEADER_CTYPE_ONLY=1.996, RCVD_IN_DNSWL_NONE=-0.0001, SUBJECT_NEEDS_ENCODING=0.1, T_RP_MATCHES_RCVD=-0.01, T_TO_NO_BRKTS_FREEMAIL=0.01, UNPARSEABLE_RELAY=0.001] autolearn=no [...] X-Yahoo-SMTP: yW16IQOswBC9dieJeZLPk5rzni61jTXAEPijtdQC Received: from txjh.netscape.net (sathyannanaviddbd@123.18.64.140 with login) by smtp104.mail.in.yahoo.com with SMTP; 31 Mar 2012 17:37:34 +0530 IST From: sathyannanavid...@yahoo.com To: br...@bd-infinity.org.uk Subject: o ṈĻĮn-Ѐ ṗḣäÈṀᾋḉẎ ĉἪеĈK ȂʈŢåḉᾞMẼŋẗ Date: Sat, 31 Mar 2012 20:06:53 +0800 Content-Type: multipart/mixed; boundary==_NextPart_000_EDA1_EDA05DF6.937F8650 --=_NextPart_000_EDA1_EDA05DF6.937F8650 Content-Type: multipart/alternative; boundary==_NextPart_001_EDA1_EDA05DF6.937F8650 --=_NextPart_001_EDA1_EDA05DF6.937F8650 Content-Type: text/plain o ṈĻĮn-Ѐ ṗḣäÈṀᾋḉẎ ĉἪеĈK ȂʈŢåḉᾞMẼŋẗ 0499be9e744ad77e --=_NextPart_001_EDA1_EDA05DF6.937F8650-- --=_NextPart_000_EDA1_EDA05DF6.937F8650 Content-Type: text/html; name=101609 Content-Disposition: attachment meta http-equiv=refresh content=0; url=http://xbpvuk.gfedone.ru/?llcpu.cr; --=_NextPart_000_EDA1_EDA05DF6.937F8650-- -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Rule updates are too old
SpamAssassin version 3.3.0 has not had a rule update since 2012-02-25. SpamAssassin version 3.3.1 has not had a rule update since 2012-02-25. SpamAssassin version 3.3.2 has not had a rule update since 2012-02-25.
[Bug 6785] New: Add option to display current config values of SA
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6785 Bug #: 6785 Summary: Add option to display current config values of SA Product: Spamassassin Version: 3.3.1 Platform: PC OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: spamassassin AssignedTo: dev@spamassassin.apache.org ReportedBy: nao...@gmail.com Classification: Unclassified Is it possible to have an option that can display the current config values of spamassassin, please? Something like postconf -d (prints default parameter settings instead of actual settings) + postconf -n (prints parameter settings that are not left at their built-in default value). Thank you! -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 6780] Existing but empty From: and To:
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6780 Lemat le...@lemat.priv.pl changed: What|Removed |Added CC||le...@lemat.priv.pl --- Comment #3 from Lemat le...@lemat.priv.pl 2012-04-03 23:57:11 UTC --- Kevin, your rules do match the spamrun I see. Meanwhile I was also testing something different: header __HAS_FROM exists:From header __EMPTY_FROM From =~ /^\s*$/ meta EMPTY_FROM __HAS_FROM __EMPTY_FROM describe EMPTY_FROM empty from score EMPTY_FROM 1 header __HAS_TO exists:To header __EMPTY_TO To =~ /^\s*$/ meta EMPTY_TO __HAS_TO __EMPTY_TO describe EMPTY_TO empty to score EMPTY_TO 1 and it also did the job. But (I believe) your rule is faster. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 6780] Existing but empty From: and To:
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6780
--- Comment #4 from Lemat le...@lemat.priv.pl 2012-04-04 00:16:34 UTC ---
hmm... MISSING_HEADERS is operating only on To: header:
header MISSING_HEADERS eval:check_for_missing_to_header()
sub check_for_missing_to_header {
my ($self, $pms) = @_;
my $hdr = $pms-get('To');
$hdr = $pms-get('Apparently-To') if $hdr eq '';
return 1 if $hdr eq '';
return 0;
}
which is not exactly identical to what I have been thinking about. And I have
been thinking not about AND but OR, something like that:
header __EMPTY_FROM From =~ /^\s*$/
header __EMPTY_TO To =~ /^\s*$/
header __EMPTY_CC Cc =~ /^\s*$/
header __HAS_FROM exists:From
header __HAS_TO exists:To
header __HAS_CC exists:CC
meta EMPTY_TO_OR_FROM_OR_CC (__HAS_TO __EMPTY_TO) || (__HAS_FROM
__EMPTY_FROM) || (__HAS_CC __EMPTY_CC)
describe EMPTY_TO_OR_FROM_OR_CC Mail contains headers that are blank and
shouldn't be.
score EMPTY_TO_OR_FROM_OR_CC 1.0
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
[Bug 6786] New: near zero score for TO_EQ_FM*
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6786 Bug #: 6786 Summary: near zero score for TO_EQ_FM* Product: Spamassassin Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Rules AssignedTo: dev@spamassassin.apache.org ReportedBy: le...@lemat.priv.pl Classification: Unclassified few days ago sa-update greatly lowered the scores for TO_EQ_FM* tests: 72_scores.cf: previous: score TO_EQ_FM_DIRECT_MX1.650 0.659 1.650 0.659 score TO_EQ_FM_HTML_DIRECT 3.134 3.950 3.134 3.950 score TO_EQ_FM_HTML_ONLY2.374 3.008 2.374 3.008 current: score TO_EQ_FM_DIRECT_MX0.001 0.001 0.001 0.001 score TO_EQ_FM_DOM_HTML_IMG 0.001 0.001 0.001 0.001 score TO_EQ_FM_DOM_HTML_ONLY0.001 0.001 0.001 0.001 score TO_EQ_FM_DOM_SPF_FAIL 0.001 2.638 0.001 2.638 score TO_EQ_FM_HTML_DIRECT 0.001 0.001 0.001 0.001 score TO_EQ_FM_HTML_ONLY0.001 0.001 0.001 0.001 score TO_EQ_FM_SPF_FAIL 0.001 2.367 0.001 2.367 and I believe something is wrong with that since TO_EQ_FM* are nice enough to mark the spam I receive -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 6786] near zero score for TO_EQ_FM*
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6786 Darxus dar...@chaosreigns.com changed: What|Removed |Added CC||dar...@chaosreigns.com --- Comment #1 from Darxus dar...@chaosreigns.com 2012-04-04 04:23:29 UTC --- A new sa-update hasn't been generated since 2012-02-25, how did your scores change a few days ago? Those rules are ranked pretty terribly. Best rules are ranked 1, worst are ranked 0: MSECSSPAM% HAM% S/ORANK SCORE NAME WHO/AGE 0 0.5257 0.0050 0.9910.540.00 TO_EQ_FM_HTML_ONLY 0 0.3420 0.0017 0.9950.520.00 TO_EQ_FM_DIRECT_MX 0 0.2501 0.0011 0.9960.510.00 TO_EQ_FM_HTML_DIRECT - http://ruleqa.spamassassin.org/?daterev=20120403-r1308758-nrule=%2FTO_EQ_FMsrcpath=g=Change Looks like all the hams hitting those three rules are in llanga's corpus. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
