http://bugzilla.spamassassin.org/show_bug.cgi?id=2838
------- Additional Comments From [EMAIL PROTECTED] 2005-03-17 12:53 ------- (In reply to comment #8) > Does this still happen with 3.0? > I'm closing as WORKSFORME, please reopen if it is still happening. > We really need more direct communication with the reporter than what we have > here. > I'm wondering if the issue is that the unix domain socket kernel module > isn't loaded when spamd is started? Or maybe a directory isn't mounted? > Is the location of the unix domain socket located on a separate filesystem? I have experienced the syslog issue cited here. I have traced it back to the system's hostname having been changed to an unresolveable value. Have run into this hostname issue twice now, the first time after upgrading SpamAssassin on a production server (SA 2.63 to 3.0.1, under PERL 5.8.4), the second after a fresh install of PERL/SA on a dev server (SA 3.0.2, PERL 5.8.6): [EMAIL PROTECTED]:/etc> hostname --fqdn The dang hostname gets trampled into "--fqdn" by some portion of the installation! Once the hostname is corrected, the syslog problems cease. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
