Current time: 11-24-2024, 01:19 AM Hello There, Guest! (LoginRegister)


Post Reply 
Spamasassin Issue with year 2010
Author Message
Lucan Offline
Member
*
Beta Team

Posts: 982
Joined: Jul 2008
Reputation: 12
Post: #1
Spamasassin Issue with year 2010
https://issues.apache.org/SpamAssassin/s...gi?id=6269


Wink
01-02-2010 01:35 AM
Find all posts by this user Quote this message in a reply
Nuxwin
Unregistered

 
Post: #2
RE: Spamasassin Issue with year 2010
Oh god, that suck. I'll check mind. Thank for the feedback
01-02-2010 02:26 AM
Quote this message in a reply
dabvhcs Offline
Junior Member
*

Posts: 26
Joined: Mar 2007
Reputation: 0
Post: #3
RE: Spamasassin Issue with year 2010
Thanks Lucan, I think a lot of SA installation are concerned !
01-02-2010 04:03 AM
Find all posts by this user Quote this message in a reply
kilburn Offline
Development Team
*****
Dev Team

Posts: 2,182
Joined: Feb 2007
Reputation: 34
Post: #4
RE: Spamasassin Issue with year 2010
sa-update is supposed to fix this feature. On my debian systems, it's scheduled to run each day (see the entry in /etc/cron.daily), so not that worrying Smile
01-02-2010 09:19 AM
Visit this user's website Find all posts by this user Quote this message in a reply
motokochan Offline
Member
***

Posts: 274
Joined: Jul 2008
Reputation: 1
Post: #5
RE: Spamasassin Issue with year 2010
Hopefully all those server admins using SpamAssassin are also using sa-update so this shouldn't be a concern for more than a day.

Maybe sa-update should be added to the cronjobs for ispCP?
01-02-2010 11:06 AM
Visit this user's website Find all posts by this user Quote this message in a reply
dabvhcs Offline
Junior Member
*

Posts: 26
Joined: Mar 2007
Reputation: 0
Post: #6
RE: Spamasassin Issue with year 2010
(01-02-2010 09:19 AM)kilburn Wrote:  sa-update is supposed to fix this feature. On my debian systems, it's scheduled to run each day (see the entry in /etc/cron.daily), so not that worrying Smile

Yes but at first it was not available via sa-update ;p

In fact I'm still not sure that just running sa-update is fine, as if using stable Ubuntu packages the bug has been fixed in distro-updates (as hardy-updates for example, but the changelog only seems to modify the concerned rule, so ?).
(This post was last modified: 01-04-2010 02:26 AM by dabvhcs.)
01-04-2010 02:19 AM
Find all posts by this user Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 2 Guest(s)