Well ok so if nobody else is going to explain this, let me try...
You probably started 'spamd' earlier and now you are trying to start it again. My guess is you ran 'spamd' and it returned like nothing happened (now it's running in the background as a daemon). Then you ran it again and got this error. Or maybe you installed it and your system started it already and when you run it.
What's happening is spamd is a daemon, it runs in the background and it listens for connections on port 783. If you try to run it again and there's already another instance of it running and listening on port 783, you get the below message.
spamd sits there on port 783 and waits for something to send it an email to scan, it then pumps the message to spamassassin and returns it and whether it's spam or not. (I am simplifying things).
You can send spamd messages on the command line using the spamc command. spamc connects to the waiting spamd on port 783. But typically your mail system would have a milter or some sort of plugin that would send messages to spamd, get the response back, and then reject or pass the message or perhaps stick it in a spam folder (again, I am simplifying).
spamd does not do the actual scanning, it's just something that feeds messages to the thing that does: spamassassin.
You can run spamassassin on the command line directly, it reads a message and tells you whether it thinks it's spam or not. spamc does essentially the same thing except it sends the message to spamd and spamd runs spamassassin. In a mail system setup, for efficiency and other reasons, you would use spamd and let it run spamassassin and not have it run spamassassin directly.
I have left out many details but hopefully this will get you started. "FalconChristopher" <[email protected]> wrote:
spamd: could not create IO::Socket::IP socket on [::1]:783: Address already in use server socket setup failed, retry 9: spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
