spamassassin-dev April 2011 archive
Main Archive Page > Month Archives  > spamassassin-dev archives
spamassassin-dev: [Bug 6571] New: FH_DATE_PAST_20XX alive and we

[Bug 6571] New: FH_DATE_PAST_20XX alive and well in CentOS 5.6 build

From: <bugzilla-daemon_at_nospam>
Date: Wed Apr 13 2011 - 04:40:33 GMT
To: dev@spamassassin.apache.org

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

           Summary: FH_DATE_PAST_20XX alive and well in CentOS 5.6 build
           Product: Spamassassin
           Version: 3.2.5
          Platform: PC
        OS/Version: other
            Status: NEW
          Severity: major
          Priority: P2
         Component: spamassassin
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: dan@jlazyh.com

I have read the posts regarding BUG 6269, but have not been able to resolve
this.

This is a fresh, clean install of CentOS 5.6 which included SpamAssasin 3.2.5
- and this bug. Running sa-update returned warnings about permissions on the
directory, but no errors - and was done to restart spamassassin - but it
persists. Running sa-update returns no further warnings or errors - and yes,
the problem persists.

I am currently running with the default rule set - which save for this
annoyance seems far better then the old version of Spamassassin I use to run.

But this is a problem, and very surprising to see that the thread of comments
was believed closed in June 2010.

I would very much appreciate an updated response as to how I can actually
remedy this issue.

I see the note from Justin Mason on 1-14-2010 saying anyone with more than "I
ran sa-update but the rule still exists" problems should mail the users@
mailing list, but I fail to see in the notes above how or where I was to find
the clue to solving this issue. And again it's a fresh build from a fresh
Final version - so something is off.

If there is any additional information that would be helpful, please don't
hesitate to ask and I will try and provide it. To that end, if you would help
by clearly stating what I should execute to generate an intended response, that
would be appreciated.

Truly appreciate the help.

-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.