You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Daniel Ziltener <dz...@lyrion.ch> on 2013/11/27 11:19:50 UTC

spamc can't connect to spamd

Hi!
First my system details.
I'm running FreeBSD 9.2 in a BSD Jail, and am using the most recent stable 
versions of the software involved. The System  has 256 MB of RAM.

I have a Dovecot/Postfix/SpamAssassin installation.

In Postfix' master.cf I've added the following:
# SpamAssassin
spamchk    unix  -       n       n       -       -       pipe
  flags=Rq user=spamd argv=/usr/local/bin/spamc -f -e /usr/sbin/sendmail -oi -f 
${sender} ${recipient}

Then in main.cf I have the entry content_filter = spamchk .

sa-spamd is running, I've done no additional configuration for SpamAssassin on 
FreeBSD since the defaults seem sane for trying to get  it to work. It's 
started with "service sa-spamd start". According to ps it's running as root 
with "/usr/local/bin/spamd -c -u spamd -H /var/spool/spamd -d -r 
/var/run/spamd/spamd.pid" and the child processes as user spamd.

Now I always get
spamc[11047]: connect to spamd on 127.0.0.1 failed, retrying (#1 of 3): 
Operation timed out
And then, after three attempts, of course also
spamc[10982]: connection attempt to spamd aborted after 3 retries

I have no idea how to solve this problem.

regards,
Daniel Ziltener

Re: spamc can't connect to spamd

Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 11/27/2013 7:23 AM, Daniel Ziltener wrote:
> Oh. Now this is embarassing. I've set up the firewall to allow all loopback
> connections from <trusted>, but I've set <trusted> to my public IP instead of
> 127.0.0.1... Hmm. Now it works perfectly. I spent hours on this yesterday! Oh
> well. Thanks again.
My theory was a firewall so glad it's fixed for you!
> By the way, I've seen that on the sa wiki it is shown to use a separate shell
> script to pipe the message (as is on most other websites). Is there a specific
> downside to this:
>
> spamchk    unix  -       n       n       -       -       pipe
>    flags=Rq user=spamd argv=/usr/local/bin/spamc -f -e /usr/sbin/sendmail -oi -f
> ${sender} ${recipient}
>
> or is that something that could be added to the wiki?
I'm afraid I have no comment beyond saying that more documentation is 
rarely a bad thing.  If you create a user on the wiki, let me know and 
I'll add you to the approved list to edit things.

Regards,
KAM

Re: spamc can't connect to spamd

Posted by Daniel Ziltener <dz...@lyrion.ch>.
Am Mittwoch, 27. November 2013, 06:53:06 schrieb Kevin A. McGrail:
> On 11/27/2013 5:19 AM, Daniel Ziltener wrote:
> > I have no idea how to solve this problem.
> 
> Daniel, if you do something like the following, what occurs:
> 
> telnet localhost 783,
> type "PING SPAMC/1.1"
> 
> You should get something like the following back:
> 
> SPAMD/1.5 0 PONG
> Connection closed by foreign host.
> 
> Regards,
> KAM
Oh. Now this is embarassing. I've set up the firewall to allow all loopback 
connections from <trusted>, but I've set <trusted> to my public IP instead of 
127.0.0.1... Hmm. Now it works perfectly. I spent hours on this yesterday! Oh 
well. Thanks again.

By the way, I've seen that on the sa wiki it is shown to use a separate shell 
script to pipe the message (as is on most other websites). Is there a specific 
downside to this:

spamchk    unix  -       n       n       -       -       pipe
  flags=Rq user=spamd argv=/usr/local/bin/spamc -f -e /usr/sbin/sendmail -oi -f 
${sender} ${recipient}

or is that something that could be added to the wiki?

Regards,
Daniel Ziltener

Re: spamc can't connect to spamd

Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 11/27/2013 5:19 AM, Daniel Ziltener wrote:
> I have no idea how to solve this problem.
>
Daniel, if you do something like the following, what occurs:

telnet localhost 783,
type "PING SPAMC/1.1"

You should get something like the following back:

SPAMD/1.5 0 PONG
Connection closed by foreign host.

Regards,
KAM