Harlan Stenn wrote:
It is probably a good idea to figure out the underlying problem instead of ignoring it.
I use the following patch...
Oh, I agree.
The extra logging only produced these extra lines in the logs:
Jun 13 15:35:18 stelleri imap: antispam: mailbox_is_unsure(SPAM): 0 Jun 13 15:35:18 stelleri imap: antispam: mailbox_is_trash(INBOX): 0 Jun 13 15:35:18 stelleri imap: antispam: mailbox_is_trash(SPAM): 0 Jun 13 15:35:18 stelleri imap: antispam: mail copy: from trash: 0, to trash: 0 Jun 13 15:35:18 stelleri imap: antispam: mailbox_is_spam(INBOX): 0 Jun 13 15:35:18 stelleri imap: antispam: mailbox_is_spam(SPAM): 1 Jun 13 15:35:18 stelleri imap: antispam: mailbox_is_unsure(INBOX): 0 Jun 13 15:35:18 stelleri imap: antispam: mail copy: src spam: 0, dst spam: 1, src unsure: 0 Jun 13 15:35:18 stelleri imap: antispam: /usr/local/bin/dspam --source=error --class=spam --signature=4a339984859385209328925 --deliver= --user frysco Jun 13 15:35:18 stelleri imap: antispam: error: dspam returned <57397: [06/13/2009 15:35:18] query error: VERBOSE DEBUG (INFO ONLY - NOT AN ERROR): see sql.errors for more details > Jun 13 15:35:18 stelleri imap: antispam: error: dspam returned <57397: [06/13/2009 15:35:18] query error: VERBOSE DEBUG (INFO ONLY - NOT AN ERROR): see sql.errors for more details >
Could the plugin be getting hung up on the 'verbose debug' messages that dspam seems to be insistent upon producing? (I'm not sure how to disable the writing to sql.errors)
Thanks, -jcd