I came across this same issue recently on Debian/Wheezy while trying to enable Evolution's built-in spamassassin checking.
As noted at some length in the upstream Spamassassin issue, it's not really a spamassassin issue at all (beyond quibbling over error message helpfulness) and seems more to do with a bad invokation of spamc by Evolution. As far as I was concerned, the fundamental issue was actually why wasn't Evolution using my perfectly good system spamd instead of creating per- user ones and trying to use some complicated socket mechanism to communicate with it. Anyway, I fixed that issue by a handful of mods to the sources to change upstream source's mentions of /usr/bin/spamd to the correct /usr/sbin/spamd (and also one mention of /usr/sbin/spamc to the correct /usr/bin/spamc but I'm not sure if that was important as Evolution seems to find spamc just fine anyway ) and now I have Evolution using my system spamd as expected just fine. More details at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724884 ** Bug watch added: Debian Bug tracker #724884 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724884 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1178826 Title: spamassassin broken error control on bad UNIX socket parameter To manage notifications about this bug go to: https://bugs.launchpad.net/spamassassin/+bug/1178826/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
