I'll happily accept patches. In the meantime, killing spamd won't cause any loss of mail, only loss of identification of spam messages for that fraction of a second when it's not listening, or for those messages already in process. spamc will just dump the unprocessed message back out if processing fails for whatever reason.
C On Sat, 2002-02-16 at 17:51, Tom Lipkis wrote: > Modifying the site-wide config requires killing and restarting spamd, which > risks missing some mail or killing a running scan. It would be handy if > sending SIGHUP to the parent spamd process would cause it to reload the > rules cleanly. It should leave the listen up, and ideally it would > continue to accept connections but defer processing them until it's done > (else the listen() backlog might fill and new connections be refused). _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
