Jul 14 00:00:43 lonestar spamc[73960]: connect() to spamd at 207.135.127.67 failed, retrying (2/3): Invalid argument
Jul 14 00:00:44 lonestar spamc[73960]: connect() to spamd at 207.135.64.67 failed, retrying (3/3): Invalid argument
Jul 14 00:00:45 lonestar spamc[73960]: connection attempt to spamd aborted after 3 retries
Spamc is being called like so from procmailrc files: | /usr/bin/spamc -d spamd.alink.net -f the result is that the messages come thru unscanned, unaltered.
What's particularly puzzling here is that the second try attempted to use the mail spamd server, which *does* succeed in scanning if it isn't attempted in this manner. That is, the scan succeeds if the first attempt goes to it. Functionality is perfect if I modify DNS to only resolve to the primary server address.
Also interesting is that the first error message is "Connection refused", and the rest are "Invalid argument".
spamd itself is started like so on the primary and secondary servers respectively:
/usr/bin/spamd -m 60 -c --listen-ip=207.135.127.67 --allowed-ips=127.0.0.1,216.39.0.226,207.135.64.226,207.135.64.42,207.135.127.67 -d -r /var/run/spamd.pid -s mail -L -x -q -u nobody
/usr/bin/spamd --sql-config --nouser-config --listen-ip=207.135.64.67 --allowed-ips=127.0.0.1,216.39.0.226,207.135.64.226,207.135.64.42 -d -r /var/run/spamd.pid -s mail --syslog-socket=inet --username=nobody --local
Is there something I'm missing? I've previously reported this same issue, and things were modified.. I haven't retested until now, with version 2.55, and stuff still appears to be the same.
Please let me know if I've just done something whack.
Thanks
--Tomki
------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
