Steve / Eric,
Here are the ouputs of the commands on our server "mail.etisbew.com" [r...@mail ~]# rpm -V perl-Mail-DomainKeys [r...@mail ~]# rpm -ql perl-Mail-DomainKeys /usr/lib/perl5/vendor_perl/5.8.8/Mail /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys.pm /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Header.pm /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Key /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Key.pm /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Key/Private.pm /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Key/Public.pm /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Message.pm /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Policy.pm /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Signature.pm /usr/share/doc/perl-Mail-DomainKeys-1.0 /usr/share/doc/perl-Mail-DomainKeys-1.0/Changes /usr/share/doc/perl-Mail-DomainKeys-1.0/MANIFEST /usr/share/doc/perl-Mail-DomainKeys-1.0/META.yml /usr/share/doc/perl-Mail-DomainKeys-1.0/README /usr/share/doc/perl-Mail-DomainKeys-1.0/THANKS /usr/share/man/man3/Mail::DomainKeys.3pm.gz [r...@mail ~]# cat /etc/tcprules.d/tcp.smtp 127.:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private" :allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONG RCPTLIMIT="10",DKSIGN="/var/qmail/control/domainkeys/%/private" [r...@mail ~]# cat /var/qmail/control/simcontrol etisbew.com:clam=yes,spam=yes,spam_hits=12,attach=.mp3:.src:.bat:.pif :clam=yes,spam=yes,spam_hits=12,attach=.mp3:.src:.bat:.pif -----Original Message----- From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert Sent: Thursday, October 01, 2009 9:07 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] RE: Mails not being scanned / filtered by SA server Steve Huff wrote: > > On Oct 1, 2009, at 10:53 AM, Atul Paralikar wrote: > >> [r...@mail qmt]#qmlog spamd >> >> 09-14 11:38:14 [8862] error: Can't locate Mail/DomainKeys/Message.pm >> in @INC (@INC contains: /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib64/perl5 >> /site_perl/5.8.8/x86_64-linux-thread-multi >> /usr/lib64/perl5/site_perl/5.8.7/x86_64-linux-thread-multi >> /usr/lib64/perl5/site_perl/5.8.6/x86_64- >> linux-thread-multi >> /usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi >> >> [r...@mail qmt]#cpan >> Cpan> Trying with "/usr/bin/links -source" to get >> ftp://ftp.perl.org/pub/CPAN/modules/03modlist.data.gz >> Going to read /root/.cpan/sources/modules/03modlist.data.gz >> Going to write /root/.cpan/Metadata >> Mail::DomainKeys::Message is up to date. >> >> [r...@mail qmt]# rpm -qa|grep -i domainkeys >> perl-Mail-DomainKeys-1.0-1.el5.rf >> libdomainkeys-toaster-0.68-1.3.6 >> >> Why SA is not detecting the installed plugin of DomainKeys? How to >> rectify this? > > this is indeed the problem; A problem, not *the* problem. I believe that there are 2 (at least) problems here. > until you fix this issue, SA will continue > to not work. True. Although fixing this problem does not mean that SA will begin working. ;) (simscan isn't being invoked, so neither will SA be invoked) > first things first, don't install Perl modules from CPAN on a > RPM-managed system; you will assuredly break things at some point or > another, and the problem will be difficult to fix. Good advice, in general. > i can see that you have the perl-Mail-DomainKeys package from rpmforge > installed; this is good. please post the output of the following two > commands: > > $ rpm -V perl-Mail-DomainKeys > $ rpm -ql perl-Mail-DomainKeys > /usr/lib/perl5/vendor_perl/5.8.8/Mail > /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys > /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys.pm > /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Header.pm > /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Key > /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Key.pm > /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Key/Private.pm > /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Key/Public.pm > /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Message.pm > /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Policy.pm > /usr/lib/perl5/vendor_perl/5.8.8/Mail/DomainKeys/Signature.pm > /usr/share/doc/perl-Mail-DomainKeys-1.0 > /usr/share/doc/perl-Mail-DomainKeys-1.0/Changes > /usr/share/doc/perl-Mail-DomainKeys-1.0/MANIFEST > /usr/share/doc/perl-Mail-DomainKeys-1.0/META.yml > /usr/share/doc/perl-Mail-DomainKeys-1.0/README > /usr/share/doc/perl-Mail-DomainKeys-1.0/THANKS > /usr/share/man/man3/Mail::DomainKeys.3pm.gz > > `rpm -V` should give you no output at all; `rpm -qf` should give you the > output as shown above. if you get anything different, then your > installed package has been corrupted (perhaps by using CPAN to do a > manual install); the fix is to remove perl-Mail-DomainKeys (`sudo rpm -e > --nodeps perl-Mail-DomainKeys`) and reinstall it (`sudo yum install > perl-Mail-DomainKeys`). That's certainly worth a shot. -- -Eric 'shubes' ---------------------------------------------------------------------------- ----- Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! ---------------------------------------------------------------------------- ----- Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
