On Mon, 2009-06-15 at 13:27 -0700, Jeremy Doran wrote: > It certainly seems to be the 'verbose debug' information that DSpam > prints to stderr that triggers this. > > After testing with the patches from Marcin Rzepecki and Harlan Stenn, I > managed completely disabled these kind of lines from being sent: > > > 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 > > > I then put in the unaltered FreeBSD ports version of the plugin, and no > longer got the "Failed to call dspam" messages.
Ok. > Since these messages - even though non-zero and stating that they aren't > an error - are just informational, I'd think that it might be an idea to > have the plugin detect and ignore that. > > Turning on DSpam debugging should not (I should think) break the plugin > from working. Well, that's not trivial. I guess if dspam has now been fixed to always exit with a non-zero exit code we could remove the stderr checking code, or make it depend on a configuration option. But as it was when I wrote the code, dspam was broken enough for this to be absolutely necessary. johannes
signature.asc
Description: This is a digitally signed message part
