Re: Could not create inet socket

2014-06-20 Thread Buzz
> Buzz, > > > When I try to run spamassassin I get the following error: > > > > Starting SpamAssassin Mail Filter Daemon: Jun 18 05:08:09.140 [21543] > > warn: > > server socket setup failed, retry 1: spamd: could not create INET > > socket on > >

Re: Could not create inet socket

2014-06-20 Thread Cristian Filipescu
socket setup failed, retry 1: spamd: could not create INET socket on > 127.0.0.1:783: Cannot assign requested address > Jun 18 05:08:10.141 [21543] warn: server socket setup failed, retry 2: > spamd: > could not create INET socket on 127.0.0.1:783: Cannot assign requested > address

Re: Could not create inet socket

2014-06-20 Thread Kevin A. McGrail
Check if your loopback interface really has address 127.0.0.1 assigned. Running in a jail? SELinux? Try and experiment with the following one-liner, it is pretty much equivalent to what spamd in 3.3.2 does: $ perl -MIO::Socket::INET -le ' print IO::Socket::INET->new(LocalAddr=>"127.0.0.1",

Re: Could not create inet socket

2014-06-20 Thread Mark Martinec
Buzz, When I try to run spamassassin I get the following error: Starting SpamAssassin Mail Filter Daemon: Jun 18 05:08:09.140 [21543] warn: server socket setup failed, retry 1: spamd: could not create INET socket on 127.0.0.1:783: Cannot assign requested address Looks like SpamAssassin

Could not create inet socket

2014-06-19 Thread Buzz
Hi, When I try to run spamassassin I get the following error: Starting SpamAssassin Mail Filter Daemon: Jun 18 05:08:09.140 [21543] warn: server socket setup failed, retry 1: spamd: could not create INET socket on 127.0.0.1:783: Cannot assign requested address Jun 18 05:08:10.141 [21543] warn

Re: server socket setup failed, retry 1: spamd: could not create INET socket on 127.0.0.1:783: Address already in use

2010-08-04 Thread Randy Ramsdell
Suhag P Desai wrote: No even when I try to do spamd at very first time after reboot the server, I get the same message,... huh? See below. Below are the output of [r...@spd ~]# ps -ef | grep spamd root 3519 3516 0 12:44 ?00:00:00 supervise spamd root 3544 3519 0 12:4

RE: server socket setup failed, retry 1: spamd: could not create INET socket on 127.0.0.1:783: Address already in use

2010-08-04 Thread Suhag P Desai
No even when I try to do spamd at very first time after reboot the server, I get the same message,... r...@spd ~]# spamd [4581] warn: server socket setup failed, retry 1: spamd: could not create INET socket on 127.0.0.1:783: Address already in use [4581] warn: server socket setup failed, retry 2

Re: server socket setup failed, retry 1: spamd: could not create INET socket on 127.0.0.1:783: Address already in use

2010-08-03 Thread Daniel Lemke
Suhag P Desai wrote: > > spamd: could not create INET socket on 127.0.0.1:783: Address already in > use > Spamd default port on your machine is already in use. Did you start a spamd instance before? -- View this message in context: http://old.nabble.com/server-socket-setup-faile

server socket setup failed, retry 1: spamd: could not create INET socket on 127.0.0.1:783: Address already in use

2010-08-03 Thread Suhag P Desai
I have installed qmail toaster plus latest version. When I run the spamd it appears with below output. [r...@spd ~]# spamd [25502] warn: server socket setup failed, retry 1: spamd: could not create INET socket on 127.0.0.1:783: Address already in use [25502] warn: server socket setup

Re: procmail: Could not create INET socket on 127.0.0.1:783: Permission denied

2005-07-11 Thread jdow
From: <[EMAIL PROTECTED]> > Hello, > > I set up spamassassin to work with procmail according to instructions. > Here is what is in ~/.procmailrc: > > #SPAM ASSASSIN SECTION > > :0fw: spamd.lock > * < 256000 > | /usr/sbin/spamd ^ The spamd tool is run as

procmail: Could not create INET socket on 127.0.0.1:783: P ermission denied

2005-07-11 Thread prosolutions
g "/home/user/.lockmail" procmail: [19772] Mon Jul 11 11:18:53 2005 procmail: Match on "< 256000" procmail: Locking "spamd.lock" procmail: Executing "/usr/sbin/spamd" Could not create INET socket on 127.0.0.1:783: Permission denied (IO::Socket::INET: Perm

Re: Could not create INET Socket

2004-12-12 Thread Matt Kettler
not create INET socket on 127.0.0.1:783: Permission denied (IO::Socket::INET: Permission denied) maildrop: error writing to filter. the call to SA is xfilter "spamd" You really should not be calling spamd in your mail chain, as it does not accept email as input. You should be calling spa

Could not create INET Socket

2004-12-11 Thread Rob Blomquist
I am trying to get fetchmail, maildrop and spamassassin happily running together, and most things are working except between maildrop and SA. I am getting this message: fetchmail: reading message [EMAIL PROTECTED]:1 of 1 (1122 octets) #Could not create INET socket on 127.0.0.1:783