Bug#864810: spamassassin: fails to initialize on IPv6 and then breaks

2017-06-24 Thread Norbert Preining
Hi Noah, > It's worse than that. The spamassassin.service unit that we're shipping > doesn't even have a dependency on the network at all. The improvements Umpf, indeed, so my server was lucky that IPv4 was fast up and running. > Specifically, what's missing is "After=syslog.target

Bug#864810: spamassassin: fails to initialize on IPv6 and then breaks

2017-06-24 Thread Noah Meyerhans
Control: tags -1 + pending On Thu, Jun 15, 2017 at 04:23:22AM -0400, Norbert Preining wrote: > It seems that the systemctl service files do not require a working > ipv6 setup It's worse than that. The spamassassin.service unit that we're shipping doesn't even have a dependency on the network at

Bug#864810: spamassassin: fails to initialize on IPv6 and then breaks

2017-06-15 Thread Norbert Preining
Package: spamassassin Version: 3.4.1-6 Severity: important Dear Maintainer, * What led up to the situation? normal reboot * What exactly did you do (or not do) that was effective (or ineffective)? nothing, normal reboot * What was the outcome of this action? spamd cannot