On Thu, Mar 09, 2006 at 02:30:18AM +0000, Tristan Miller wrote: > from the command line, spamc didn't wait any longer no matter what value of > x I used; it just waited for a second and then spit out some-email.txt > as-is. Ditto when using the -x option.
That makes sense. If the daemon isn't running connect() will fail quickly because nothing's listening on the port. spamc retries the connection a few times with a pause in between, but if spamd hasn't started by the end you'll get the raw message back unmarked up. > Am I doing anything wrong? Is there something besides fiddling with spamc > arguments I can use to make sure fetchmail doesn't start running until > spamd has started up? (I am running SuSE 9.3.) Sure, change the startup scripts to start spamd before fetchmail. -- Randomly Generated Tagline: "Wouldn't it be neat if there was a new Tom Hanks western/romance film called Sheepless in Laredo?" - unknown
pgpCQhjGqGWOy.pgp
Description: PGP signature
