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

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-failed%2C-retry-1%

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

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 fail

OT: godaddy emails

at the bottom of an email that was NOT DKIM signed the ironic thing, the headers,godaddy publishes SPF records, but this came 'from: mmboun...@returns.secureserver.net So, no SPF signature, no DKIM signatures. just wonder about what they were thinking: Go Daddy is always looking out for your

Re: sa-compile has no effect (under Windows.......)

Daniel McDonald-3 wrote: > > The question is not how processing one mail compares, but how 10 per > second > compare in each scenario. That's where the win is - lower total cpu > utilization to accomplish the same work. > Yes, that makes sense to me. Daniel McDonald-3 wrote: > > But your nu