Bug#888837: Bug #888837: spamassassin: sa-update failed, spamd does not start anymore

2018-01-30 Thread Damir Islamov
tags 37 sid

Bug#888837: spamassassin: sa-update failed, spamd does not start anymore

2018-01-30 Thread Noah Meyerhans
Control: severity -1 normal Resetting severity to normal, since we don't ship with updates enabled at all by default. On Tue, Jan 30, 2018 at 09:07:26AM -0700, Will Aoki wrote: > forwarded 37 https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540 > thanks > > We hit this bug this morning wi

Bug#888837: spamassassin: sa-update failed, spamd does not start anymore

2018-01-30 Thread Will Aoki
forwarded 37 https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540 thanks We hit this bug this morning with an sa-update. I'd hazard a guess that it's the faulty ruleset described in upstream bug #7540 (fixed less than two hours ago) and will clear up soon, when upstream publishes new rules.

Bug#888837: spamassassin: sa-update failed, spamd does not start anymore

2018-01-30 Thread Niccolo Rigacci
Package: spamassassin Version: 3.4.1-6+deb9u1 Severity: grave Justification: renders package unusable Dear Maintainer, I enabled CRON=1 in /etc/default/spamassassin, to enable the cron job to automatically update spamassassin's rules. Then I run /etc/cron.daily/spamassassin, which failed with th