+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Development Area (/forum-1.html)
+--- Forum: General discussion (/forum-11.html)
+--- Thread: Spamasassin Issue with year 2010 (/thread-9041.html)
Spamasassin Issue with year 2010 - Lucan - 01-02-2010 01:35 AM
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6269
RE: Spamasassin Issue with year 2010 - Nuxwin - 01-02-2010 02:26 AM
Oh god, that suck. I'll check mind. Thank for the feedback
RE: Spamasassin Issue with year 2010 - dabvhcs - 01-02-2010 04:03 AM
Thanks Lucan, I think a lot of SA installation are concerned !
RE: Spamasassin Issue with year 2010 - kilburn - 01-02-2010 09:19 AM
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
RE: Spamasassin Issue with year 2010 - motokochan - 01-02-2010 11:06 AM
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?
RE: Spamasassin Issue with year 2010 - dabvhcs - 01-04-2010 02:19 AM
(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
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 ?).