OK, that's embarassing... I though we tried that earlier. Evidently not!
 
As for the reliability, let me pass a few million messages through the system and I'll let you know. As of today, we are still testing. I should be able to answer this by next week.

>>> Ross Vandegrift <[EMAIL PROTECTED]> 5/3/2002 4:17:43 PM >>>
On Fri, May 03, 2002 at 04:08:09PM -0400, Dave Strickler wrote:
> A friend I just set up SA and it was working fine with the deamons.
> After rebooting, the spamass-milter wouldn't load, even by hand. The
> error it give is (from the log):

> May  3 15:47:58 scrubber su(pam_unix)[1030]: session opened for user
> root by awaltman(uid=501)
> May  3 15:48:08 scrubber spamass-milter: SpamAssassin: Unable to bind
> to port /var/local/spamass-sock: Address already in use
> May  3 15:48:08 scrubber spamass-milter: SpamAssassin: Unable to create
> listening socket on conn /var/local/spamass-sock

> We checked to make sure its not already loaded, so we're confused as to
> what port is in use already. Since it doesn't list a port, I don't want
> to start guessing ;-)

> Anyone have an idea as to why this is happening?

The socket you've told it to open (/var/local/spamass-sock, in this
case) already exists.  It won't start until you delete this file.

On a related note, is spamass-milter at all reliable for you?  I have
huge amounts of problems with it spinning off a ridiculous number of
sub-processess (spamass-milter and spamc) that never return.  I'm
considering figuring out why this seems so broken, if I can verify it's
not just my setup.

Ross Vandegrift
[EMAIL PROTECTED]

Reply via email to