Re: Spamassassin fails to start

From: Dan Mahoney <>
Date: Sat, 01 Oct 2022 19:55:18 UTC
This is either a disconnect between sa and the init script, or something broken in spamassassin.

Please post any relevant config snippets for spamassassin from your rc.conf.local -- it was previously the case but may have been fixed that the rc.d files would start it, but if you were running in debug mode, the rc.d files could not stop it or status it.

What does spamassassin --lint reveal?

What do you get if you try to start spamd manually with the stock args specified in /usr/local/etc/rc.d/sa-spamd


> On Oct 1, 2022, at 12:43, George Mitchell <> wrote:
> On 10/1/22 15:12, Robert Huff wrote:
>> Hello:
>> 	On a system running:
>> FreeBSD 14.0-CURRENT #0 main-dfddfe29d8:
>> Thu Jul 28 11:36:59 EDT 2022
>> amd64
>> 	with all involved ports up to date, spamassassin fails to start
>> and reports:
>> Starting spamd.
>> child process [90570] exited or timed out without signaling production of a PID file: exit 255 at /usr/local/bin/spamd line 3034.
>> /usr/local/etc/rc.d/sa-spamd: WARNING: failed to start spamd
>> 	Way above my pay grade.  Any idea what's going wrong?
>> 			Respectfully,
>> 				Robert Huff
>> [...]
> The first thing I'd recommend is looking in the log (/var/log/messages)
> to see if it mentions anything.  If this was a fresh installation, have
> you run sa-update yet?                                     -- George