On Thursday 23 February 2006 23:20, Bob McClure Jr wrote:
>On Thu, Feb 23, 2006 at 10:59:02PM -0500, Gene Heskett wrote:
>> On Thursday 23 February 2006 22:45, Bob McClure Jr wrote:
>> >On Thu, Feb 23, 2006 at 10:36:19PM -0500, Gene Heskett wrote:
>> >> <snippage>
>> >>
>> >> Also, where would it put it if it did dl a new version of itself?
>> >
>> >Probably in /etc/mail/spamassassin/RulesDuJour/.
>>
>> And you are correct, its the same length anyway, as the one I dl'd
>> DBY and installed by hand.  Now to figure out why its not sending me
>> email.
>>
>> A snippet or 3 from a 'crontab -l' as root:
>> [EMAIL PROTECTED]
>> 06 22 * * *     /etc/init.d/asmb restart
>> 40 4 * * 0      /root/bin/fetchmail-restart
>> 37 6 * * *      /usr/local/sbin/rules_du_jour
>>
>> And I am getting email from the first 2 of those, but not the third.
>> The 2nd one is to allow logrotate to close the logfiles and reopen
>> them. However, I may have to delay that more than 4 minutes it
>> appears.
>
>You might check your maillog for clues timestamped around 0637 every
>morning.  There's probably a forehead slapper in there.  (Most of my
>trips to /var/log/maillog result in a slap to the forehead.)
>
>Check also your wrapper (I use my_rules_du_jour to call rules_du_jour)
>or config file (normally /etc/rulesdujour/config) for settings of
>MAIL_ADDRESS, SINGLE_EMAIL_ONLY, EMAIL_RDJ_UPDATE_ONLY, and MAILCMD.
>If those aren't set, and there's an alias for root in /etc/aliases
>that gets to you, it should work sensibly.

There is absolutely nothing in them back to maillog.4 that references 
rules_du_jour.

But a study did show me two problems, first although its running as the 
user, it was bitching about the existance of a procmailrc file 
in /etc/procmail, so I just renamed that which seems to have taken care 
of that bitch.  One less line in the logs per message per spamd client.

However, I'm also left with litterally megabytes of this below snippet 
since it occurs for every incoming message processed by spamd, and its 
something that I'd expect to see in procmail.log since its the spamd 
caller, but I am not.  I was not aware that spamd kept it mutterings in 
maillog.  My bad of course.

--------
Feb 24 00:09:27 coyote spamd[31012]: Can't locate IP/Country/Fast.pm in 
@INC (@INC 
contains: ../lib /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi 
/usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/5.8.3/i386-linux-thread-multi 
/usr/lib/perl5/5.8.3 /usr/lib/perl5/site_perl/5.8.2/i386-linux-thread-multi 
/usr/lib/perl5/site_perl/5.8.1/i386-linux-thread-multi 
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi 
/usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl/5.8.1 
/usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl 
/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi 
/usr/lib/perl5/vendor_perl/5.8.2/i386-linux-thread-multi 
/usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi 
/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi 
/usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl/5.8.2 
/usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl/5.8.0 
/usr/lib/perl5/vendor_perl) 
at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Plugin/RelayCountry.pm 
line 66, <GEN224> line 57.
--------

I'm reasonably sure all that stuff is installed *someplace* cause I got 
a whole wagonload of them from cpan at the time I installed 
spamassassin.  So where do I look to see whats mis-configured at lines 
66 and 57?  Probably a /usr vs /usr/local thing I'd guess.  I'd assume 
it would work better but even slower if the spamd children could find 
their stuff...

>> --
>> Cheers, Gene
>
>Cheers,

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.

Reply via email to