SA Bugzilla – Bug 7473
SpamAssassin Installation - sa-compile error message
Last modified: 2017-09-18 13:58:15 UTC
Context: - Debian (Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.43-2+deb8u3 (2017-08-15) - Vmware Esxiv 6 , 3vCPU, 16Go RAM - Postfix + Mailman When I want to install SpamAssassin (apt-get intsall), both spamassassin and sa-compile are downloaded. But when trying to be installed, sa-compile says he is depending on Spamassassin ant that the package is not configured. But I can't configure SA without sa-compile functional. Manually executed, sa-compile returns a DNS error: unresolvable name: DNS at /usr/share/perl5/Mail/SpamAssassin/DnsResolver.pm line 128. I have no other issue about this DNS configuration. At the end of sa-compile execution, it says that spamassassin is compiled. When I check the service status, I have: ● spamassassin.service - Perl-based spam filter using text analysis Loaded: loaded (/lib/systemd/system/spamassassin.service; disabled) Active: failed (Result: timeout) since lun. 2017-09-18 15:41:22 CEST; 12min ago sept. 18 15:39:52 srvmailtst spamd[9739]: logger: removing stderr method sept. 18 15:41:22 srvmailtst systemd[1]: spamassassin.service start operation timed out. Terminating. sept. 18 15:41:22 srvmailtst spamd[9743]: spamd: server killed by SIGTERM, shutting down sept. 18 15:41:22 srvmailtst spamd[9743]: spamd: cannot unlink /var/run/spamassassin.pid: No such file or directory sept. 18 15:41:22 srvmailtst systemd[1]: Failed to start Perl-based spam filter using text analysis. sept. 18 15:41:22 srvmailtst systemd[1]: Unit spamassassin.service entered failed state. Would any of you have an idea to help me with this issue? I've searched for and tried a lot of experiments but I've been on this for weeks and my users get impatient. Thank you all. Cat.
That's going to be almost certainly an upstream or a DNS issue not a bug in the spamassassin product. Please join and email users@spamassassin.apache.org. It's the correct forum to discuss this before opening a bug report.