Thanks all Sounds link I need to update to SA 3.2.0 or later. Normally I just wait for updates to come through Centos update system (Up2date) - but perhaps I should give it a hurry on.
I tried running sa-update from my root login - but got errors. I'm afraid I'm a bit clueless with all this command line stuff... Just a recently reformed windows user. Can anyone tell me what is wrong here?: [EMAIL PROTECTED] ~]# sa-update Can't locate Archive/Tar.pm in @INC (@INC contains: /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.8.5 /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /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.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /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.4/i386-linux-thread-multi /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.4 /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/bin/sa-update line 94. BEGIN failed--compilation aborted at /usr/bin/sa-update line 94. [EMAIL PROTECTED] ~]# Will using sa-update interfere with the centos Up2Date system? Thanks Richard. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 March 2007 12:04 AM To: John Rudd Cc: Duane Hill; Robert Swan; Richard; users@spamassassin.apache.org Subject: Re: Spamassassin doesn't seem to obey my whitelist John Rudd writes: > Duane Hill wrote: > > On Tue, 13 Mar 2007, Robert Swan wrote: > > > >> Richard the whitelist_from you are specifying as [EMAIL PROTECTED] but > >> if you look at the headers below, the email comes from : > >> > > > > > According to documentation: > > > > The headers checked for whitelist addresses are as follows: if > > Resent-From is set, use that; otherwise check all addresses taken from > > the following set of headers: > > > > Envelope-Sender > > Resent-Sender > > X-Envelope-From > > From > > > > http://spamassassin.apache.org/full/3.1.x/doc/Mail_SpamAssassin_Conf.html#wh itelist_and_blacklist_options > > > > > > > It doesn't check Return-Path as well? > > That seems rather inappropriate, since that's where the Envelope From is > _supposed_ to be recorded. "We'll check a header that isn't standard > (X-Envelope-From) for the envelope sender, but we wont check the > _standard_ header for that information". > > That's just silly. And not in an entertaining way. It does -- however the documentation forgot to mention it. fixed in 3.2.0. --j.
