gmane.mail.spam.spamassassin.devel

Rule updates are too old

2012-05-25T16:00:03

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 6798] New: WIFEXITED not supported in windows from Util.pm

2012-05-25T15:54:21

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6798

          Priority: P2
            Bug ID: 6798
          Assignee: dev< at >spamassassin.apache.org
           Summary: WIFEXITED not supported in windows from Util.pm
          Severity: normal
    Classification: Unclassified
                OS: Windows XP
          Reporter: jkozee< at >bowser-morner.com
          Hardware: PC
            Status: NEW
           Version: 3.3.2
         Component: Libraries
           Product: Spamassassin

I found this error when enabling the DCC plugin on Windows.  I was able to work
around it by redefining the offending commands in Util.pm:

# These are not implemented on windows
if (RUNNING_ON_WINDOWS) {
  *WIFEXITED   = sub { not $_[0] & 0xff };
  *WEXITSTATUS = sub { $_[0] >> 8  };
  *WIFSIGNALED = sub { $_[0] & 127 };
  *WTERMSIG    = sub { $_[0] & 127 };
}

Re: sa-update DNS TXT record not being updated?

Kevin A. McGrail — 2012-05-25T01:57:01

Once I get past a few of the hurdles I have in getting my chair work 
caught up, approving masscheck is a definite goal.  I think Warren's 
worry is legitimate but I think we have to choose candidates well and 
move forward.

Regards,
KAM

Re: sa-update DNS TXT record not being updated?

2012-05-25T00:48:50

Rule updates are supposed to be generated daily, but it hasn't happened
since 2012-02-25 due to insufficient masscheck corpora, which is partially
due to a security bug which is preventing new masscheck contributors (bug
6694, but you can't see it due to being a security bug).

It's enough of a problem that an alert about it is automatically posted to
this list every day.

It's my opinion that it should not be considered a bug and new masscheck
accounts should be created.

You could sign up for a masscheck account for when they start being created
again if you want to contribute:
https://wiki.apache.org/spamassassin/NightlyMassCheck

sa-update DNS TXT record not being updated?

Paul Scott — 2012-05-25T00:14:33

I have not seen any new rules via sa-update for a long time. Looking at the source repository it looks like there may have been changes, but they are not getting out to users.

Is someone forgetting to update the DNS TXT record at 2.3.3.updates.spamassassin.org with the correct version number? Or are there just no updates?

--
Paul Scott
pscott< at >skycoast.us

Rule updates are too old

2012-05-24T16:00:01

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.

Rule updates are too old

2012-05-23T16:00:02

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.

[auto] bad sandbox rules report

Rules Report Cron — 2012-05-23T08:32:42

HTTP get: http://ruleqa.spamassassin.org/1-days-ago?xml=1
HTTP get: http://ruleqa.spamassassin.org/2-days-ago?xml=1
HTTP get: http://ruleqa.spamassassin.org/3-days-ago?xml=1

Bad performing rules, from the past 3 night's mass-checks.

(Note: 'net' rules will be listed as 'no hits' unless you set 'tflags net'.
This also applies for meta rules which use 'net' rules.)


rulesrc/sandbox/wtogami/20_url_shortener.cf (10 rules, 10 bad):

  URL_SHORTENER:  bad, avg S/O=0.49 avg Spam%=1.12 avg Ham%=1.16
      # used in: SHORT_URL SPOOFED_URL SPOOFED_URL_HOST
  __URL_SHORTENER_ABC:  bad, avg S/O=0.31 avg Spam%=0.16 avg Ham%=0.36
      # used in: SHORT_URL SPOOFED_URL SPOOFED_URL_HOST URL_SHORTENER
  __URL_SHORTENER_DEFGHI:  bad, avg S/O=0.07 avg Spam%=0.02 avg Ham%=0.20
      # used in: SHORT_URL SPOOFED_URL SPOOFED_URL_HOST URL_SHORTENER
  __URL_SHORTENER_JKLM:  bad, avg S/O=0.55 avg Spam%=0.01 avg Ham%=0.01
      # used in: SHORT_URL SPOOFED_URL SPOOFED_URL_HOST URL_SHORTENER
  __URL_SHORTENER_NOPQ:  bad, avg S/O=0.

Rule updates are too old

2012-05-22T16:00:02

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 6781] multiple emails in From

2012-05-21T19:34:37

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6781

--- Comment #10 from D. Stussy <software+spamassassin< at >kd6lvw.ampr.org> ---
RE: Comment #9 - I must disagree:

A message with multiple from entries, no sender header, and non-spammy content
is not a "false positive" as it is an RFC violation and therefore not a valid
message.

Although spam is generally about content, I cannot accept that a malformed
message is a legitimate message.  Such malformations are precisely the target
of the rule(set) that we are developing as a result of this bug report.

Now, as for the misfirings on a character-set-encoded string, that could be a
problem.  Maybe we need a "decoded" function, which for non-encoded strings
will be identical to "raw", but for strings starting with "=charset", it
obviously decodes them and performs comparisons thereafter.

[Bug 6781] multiple emails in From

2012-05-21T18:36:11

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6781

--- Comment #9 from Mark Martinec <Mark.Martinec< at >ijs.si> ---
Observed 3800 messages which hit MULTI_FROM_BAD during the last four days.

Among these there were three legitimate mail messages with two addresses
in a From, and a missing Sender (a conference registration confirmation
or paper submissions). These were genuine false positives (of which one
was quarantined for exceeding a spam threshold, while the other two
were rescued by other rules).

Besides the above three, there were three additional false positives, where
my version of MULTI_FROM_ADDR misfired. These three were a result of a
B64-encoded display name in the iso-2022-jp character set, which happened
to contain bytes '< at >' and ',' in the b64-decoded string.

The string that was matched looked like (somewhat obfuscated):
  _$B:#1xxf_(B _$B< at >5,_(B <xxx< at >example.com>

It is most unfortunate that the :addr modifier only returns the first
of multiple addresses (in a To, From, Cc, ...), which

Rule updates are too old

2012-05-21T16:00:02

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.

Re: New SpamAssassin Project Chair

Daniel McDonald — 2012-05-21T12:34:33


Thanks for stepping up, Kevin.  And thanks to Daryl for his service, too.

Re: New SpamAssassin Project Chair

Mark Martinec — 2012-05-20T23:29:55

Congratulations Kevin, and a big thanks for accepting the duty!

  Mark

New SpamAssassin Project Chair

Kevin A. McGrail — 2012-05-20T19:34:07

Good Afternoon Everyone,

I am both humbled and honored to report that I have accepted the 
nomination of the SpamAssassin PMC to serve as the new project chair.  
On April 18th, the Board of Directors for the Apache Software Foundation 
accepted the nomination and appointed me to the position.

Unfortunately and for very good reasons, our previous chair, Daryl C. W. 
O'Shea is no longer unavailable to help the project.  I hope all can 
join me in thanking Daryl for his service to the project.  And while he 
will be sorely missed, for privacy reasons, I can only tell you that he 
is urgently needed elsewhere.  But I'm certain he needs and would 
appreciate all the good karma we can send his way.

Over the past few weeks, I've been working to get up to speed on my 
duties.  Luckily, I attended the ASF BarCamp DC conference yesterday.  
Not only was it a great conference with great people that taught me a 
few things but several of the attendees were very helpful in helping me 
overcome a few hurdles.   Many t

[Bug 6703] sa-learn doesn't work with kmail 2 mbox format

2012-05-20T19:33:35

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6703

--- Comment #31 from Thomas Arend <thomas< at >arend-rhb.de> ---
(In reply to comment #29)

I never saw more than one whitespace after the "From" but one or two white
spaces after the "e-mail" address / before the weekday.

[Bug 6703] sa-learn doesn't work with kmail 2 mbox format

2012-05-20T17:09:42

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6703

--- Comment #30 from Kevin A. McGrail <kmcgrail< at >pccc.com> ---
(In reply to comment #29)

Well more importantly than specific kmail 2 mbox regexes , does the patch I
wrote that let's someone use /^Mickey Mouse$/ as their mbox separator regular
expression work?  

Regards,
KAM

[Bug 6703] sa-learn doesn't work with kmail 2 mbox format

2012-05-20T16:54:40

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6703

--- Comment #29 from John Hardin <jhardin< at >impsec.org> ---
(In reply to comment #26)

There is no reason to capture the results of the match for later use. (?:...)
is a non-capturing match, which is slightly more efficient.

To allow for variations in whitespace, perhaps:

/^From\s{1,5}\S+\s{1,5}[[:upper:]][[:lower:]]{2}(?:, \d\d
[[:upper:]][[:lower:]]{2} \d{4} [0-2]\d:\d\d:\d\d [+-]\d{4}|
[[:upper:]][[:lower:]]{2} [ 1-3]\d [ 0-2]\d:\d\d:\d\d \d{4})/

Rule updates are too old

2012-05-20T16:00:02

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 6703] sa-learn doesn't work with kmail 2 mbox format

2012-05-20T13:41:23

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6703

--- Comment #28 from Thomas Arend <thomas< at >arend-rhb.de> ---
(In reply to comment #27)

Just found that the corrupted From_ line was added when filtering through
formail. Don`t ask me why. Formail works on command line as expected.

[Bug 6703] sa-learn doesn't work with kmail 2 mbox format

2012-05-20T12:16:26

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6703

--- Comment #27 from Thomas Arend <thomas< at >arend-rhb.de> ---
Created attachment 5071
  --> https://issues.apache.org/SpamAssassin/attachment.cgi?id=5071&action=edit
Test mbox showing two From_ lines

This is an export of four messages which show two from lines.