And since this is new code in a CVS, not too surprising that it might have a bug.... However, taking a casual look at the libspamc.c from the latest CVS snapshot on http://spamassassin.sourceforge.net/dist/spamd/libspamc.c I don't see why it wouldn't work.
In theory the EINVAL error here is telling us that mysock is in an invalid state to attempt connect() again. I can't see how the sockaddr isn't valid the second time but is valid the first.
Perhaps there's an issue with re-using the same socket object on connect() after a connection refused... I'd venture to guess a close() and setup of a new socket may be in order to correct it, but I'm hardly a sockets expert.
At 12:01 PM 12/10/2002 -0800, Tomki wrote:
At least, not as advertised
I have set up 2 spamd servers, and I have spamc being used from my .procmailrc like so:
spamc -d spamd.alink.net -f
However... when I shut down the spamd on one, there are failures connecting to both.. is this a known bug, or have I overlooked something somewhere in the configuration for this?
Dec 10 11:44:21 lonestar spamc[11342]: connect() to spamd at 207.135.127.67 fail
ed, retrying (1/3): Connection refused
Dec 10 11:44:22 lonestar spamc[11342]: connect() to spamd at 207.135.64.67 faile
d, retrying (2/3): Invalid argument
Dec 10 11:44:23 lonestar spamc[11342]: connect() to spamd at 207.135.127.67 fail
ed, retrying (3/3): Invalid argument
Dec 10 11:44:24 lonestar spamc[11342]: connection attempt to spamd aborted after
3 retries
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
