No, what I'm suggesting is make wrappers Mail::SpamAssassin::DCC.pm which just implements the functions that are now in Reporter.pm and Dns.pm, but just consolidate them to one location. And do the same for the similar razor-wrapper functions that are currently in Reporter and Dns too. You are correct that there is no current Perl DCC client implementation; I've been discussing it today on the DCC mailing list, and it sounds like it would non-trivial to implement. Might be worth looking at if there turn out to be performance issues with larger sites interested in having their own spam signature database but don't want to pay Cloudmark for the priviledge, but we can broach those when we come to them.
As for the debug info, just pass debug=>1 in the Mail::SpamAssassin constructor -- see spamassassin or spamd for an example C Rose, Bobby wrote: RB> Is there a DCC.pm? It appearred to me that dcc is a exec process and RB> not a perl module. I've come across something odd when using RB> Mailscanner and SA with DCC. If I pass a DCC reported message thru RB> dccproc or spamassassin then the report reflects the listing. But when RB> Mailscanner sends it to SA, there isn't a DCC test. Every other test is RB> reported back thru the object, just not DCC. RB> RB> Any ideas on how I can get some SA debug info when using RB> Mail::SpamAssassin calls? _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
