----- Original Message ----- From: "Mike Carlson" <[EMAIL PROTECTED]>
> I have attached a snippet of the output of spamd -D that talks about URIDNSBL > > debug: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC > debug: plugin: registered Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) > debug: plugin: loading Mail::SpamAssassin::Plugin::Hashcash from @INC > debug: plugin: registered Mail::SpamAssassin::Plugin::Hashcash=HASH(0x8c35840) > debug: plugin: loading Mail::SpamAssassin::Plugin::SPF from @INC > debug: plugin: registered Mail::SpamAssassin::Plugin::SPF=HASH(0x8c36ef0) > debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) implements 'parse_config' > debug: plugin: Mail::SpamAssassin::Plugin::Hashcash=HASH(0x8c35840) implements 'parse_config' > debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks > > Does that look correct? I don't notice any errors, but I wasn't sure about "inhibited further callbacks". These can be ignored, and it looks like this output will be supressed in the next SA release, see: http://bugzilla.spamassassin.org/show_bug.cgi?id=3931. If you are impatient, you can comment out one line in your PluginHandler.pm file and these informational messages will no longer display in your debug output (see above reference bugzilla). Bill
