On Tue, Feb 10, 2015 at 10:17 PM, Kevin A. McGrail wrote:
> On 2/10/2015 9:13 AM, Kevin A. McGrail wrote:
>>
>> I would guess I missed the cutoff for yesterday's masscheck and tomorrow's
>> will include it.
>
> Rule gen just finished and the update does include the fix if you want to
> confirm.
L
On 2/10/2015 9:13 AM, Kevin A. McGrail wrote:
I would guess I missed the cutoff for yesterday's masscheck and
tomorrow's will include it.
Rule gen just finished and the update does include the fix if you want
to confirm.
Regards,
KAM
Uh,ohsorry my bad. I did it try the modifed ruleset on
a test installation without the Rule2XSBody plugin enabled.
With the plugin enabled (and after restarting Amavis) it looks
like those warning messages are not there anymore.
Thanks a lot for the fix!
Regards,
Matteo
On 10.02.2015 16:
On 2/10/2015 9:54 AM, Matteo Dessalvi wrote:
Hello KAM.
Unfortuntately I am still getting the same "warning messages"
with the new 25_spf.cf.
It looks like that the check part:
if can(Mail::SpamAssassin::Plugin::SPF::has_check_for_spf_errors)
(...)
endif
is ignored. Could it be an effect intr
Hello KAM.
Unfortuntately I am still getting the same "warning messages"
with the new 25_spf.cf.
It looks like that the check part:
if can(Mail::SpamAssassin::Plugin::SPF::has_check_for_spf_errors)
(...)
endif
is ignored. Could it be an effect introduced by the sa-compile step?
The output of t
On Tue, Feb 10, 2015 at 9:13 AM, Kevin A. McGrail wrote:
> On 2/10/2015 9:00 AM, Jim Popovitch wrote:
>>
>> On Mon, Feb 9, 2015 at 6:30 AM, Kevin A. McGrail
>> wrote:
>>>
>>> On 2/9/2015 4:12 AM, Reindl Harald wrote:
what is that below introduced with tonights update and get triggered n
On 2/10/2015 9:27 AM, Jim Popovitch wrote:
Then I'll hope the rule update hits tomorrow. There is some vagueness to my
>understanding of exactly how long rules take from start to finish to go
>outbound. There are some emergency rule generation procedures if someone
>wants to help the project.
On 2/10/2015 9:00 AM, Jim Popovitch wrote:
On Mon, Feb 9, 2015 at 6:30 AM, Kevin A. McGrail wrote:
On 2/9/2015 4:12 AM, Reindl Harald wrote:
what is that below introduced with tonights update and get triggered now
for every single mail and why does such things not automatically get caught
befo
On Mon, Feb 9, 2015 at 6:30 AM, Kevin A. McGrail wrote:
> On 2/9/2015 4:12 AM, Reindl Harald wrote:
>>
>> what is that below introduced with tonights update and get triggered now
>> for every single mail and why does such things not automatically get caught
>> before push?
>
> It was part of a com
On 2/9/2015 6:33 AM, Reindl Harald wrote:
Am 09.02.2015 um 12:30 schrieb Kevin A. McGrail:
On 2/9/2015 4:12 AM, Reindl Harald wrote:
what is that below introduced with tonights update and get triggered
now for every single mail and why does such things not automatically
get caught before push?
Am 09.02.2015 um 12:30 schrieb Kevin A. McGrail:
On 2/9/2015 4:12 AM, Reindl Harald wrote:
what is that below introduced with tonights update and get triggered
now for every single mail and why does such things not automatically
get caught before push?
It was part of a commit on Jan 30,
http:/
On 2/9/2015 4:12 AM, Reindl Harald wrote:
what is that below introduced with tonights update and get triggered
now for every single mail and why does such things not automatically
get caught before push?
It was part of a commit on Jan 30,
http://www.gossamer-threads.com/lists/spamassassin/commi
Hi all.
I am getting the same errors. I am running SA through Amavis but I guess
it does not matter in this case. Is there a way of fixing those errors,
apart from disabling the rules from 25_spf.cf?
SA version: 3.4.0 - Perl 5.14.2 (Debian Wheezy - 64 bit)
Log snapshot:
Feb 9 10:
> Help. sa-update is jammed.
> What should I do?
>
> rules: failed to run __KAM_BODY_LENGTH_LT_256 test, skipping:
> (Can't locate object method "check_body_length" via package
> "Mail::SpamAssassin::PerMsgStatus" at (eval 1114) line 419.
>
> etc. etc.
Just got a report from another source
On 6/28/2012 8:43 PM, Michael Scheidell wrote:
> On 6/28/12 9:08 PM, Richard B. Pyne wrote:
>> SpamAssassin version 3.3.2 running as spamd called from maiad called
>> form postfix on CentOS 6.2 64bit linux.
>>
>>
>> I am trying to get a new installation of SpamAssassin working am
>> getting this e
On 6/28/12 9:08 PM, Richard B. Pyne wrote:
SpamAssassin version 3.3.2 running as spamd called from maiad called form
postfix on CentOS 6.2 64bit linux.
I am trying to get a new installation of SpamAssassin working am getting this
error:
spam_scan FAILED: Can't locate object method "get_tag"
ackup fixed the
issue.
HTH
Cheers,
Michael Hutchinson
-Original Message-
From: mouss [mailto:mo...@ml.netoyen.net]
Sent: Thursday, 22 January 2009 9:40 a.m.
To: users@spamassassin.apache.org
Subject: Re: Can't locate object method "new" via package "Net::DNS::RR::TXT&qu
Brian J. Murrell a écrit :
> I seem to be getting a lot of these in the last 36h:
>
>
> 12:02:26 spamd Can't locate object method "new" via package
> "Net::DNS::RR::TXT" at /usr/lib/perl5/Net/DNS/RR.pm line 305.
> 12:02:26 spamd caught at /usr/share/perl5/Mail/SpamAssassin/DnsResolver.pm
> line
At 08:13 AM 10/21/2006, you wrote:
Getting the below error in my mail.log repeatedly:
Oct 21 08:09:22 espphotography spamd[301]: Can't locate object
method "tokenize" via package "Mail::SpamAssassin::Bayes" at
/usr/bin/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Bayes.pm line
1185, line 391
On Sunday 20 August 2006 23:50, Loren Wilton wrote:
> Old version of Net::DNS?
>
> Loren
Not according to cpan. That was the first thing I checked.
I wonder what low-level stuff Net::DNS is trying to use?
Its running on an older SuSE Distro, and the newer boxes
don't seem to show this mes
Old version of Net::DNS?
Loren
Jeffrey Duncan wrote:
> Thanks! Do I need to remove the 5.8.5 and 5.8.6 perl libraries too?
The Mail/SpamAssassin ones, yes.. everything else, no.
Thanks! Do I need to remove the 5.8.5 and 5.8.6
perl libraries too?
Matt Kettler wrote:
Jeffrey Duncan wrote:
Thanks,
>From my mail headers I think I am running 3.0.2 - also,
spamc -V
SpamAssassin Client version 3.0.2
I think what happened is that I did a yum update and it bro
Jeffrey Duncan wrote:
> Thanks,
>
>>From my mail headers I think I am running 3.0.2 - also,
>
> spamc -V
> SpamAssassin Client version 3.0.2
>
> I think what happened is that I did a yum update and it broke things. I
> tried to rename the 5.8.5 PerMsgStatus and spamd didn't load. I thinik
> I
Thanks,
>From my mail headers I think I am running 3.0.2 - also,
spamc -V
SpamAssassin Client version 3.0.2
I think what happened is that I did a yum update and it broke things.
I tried to rename the 5.8.5 PerMsgStatus and spamd didn't load. I
thinik I have some mix ups here. Should I uni
Jeffrey Duncan wrote:
> Okay, so I see that I have two versions of PerMsgStatus.pm (below)
>
> How do I remove one of them to get rid of the issues?
>
> Jeffrey Duncan wrote:
>
>> Thanks,
>>
>> What do you mean resolve? Here is the output ...
>>
>>
>> [EMAIL PROTECTED] log]# locate PerMsgSta
Thanks,
What do you mean resolve? Here is the output ...
/home/spamd
/home/spamd/.spamassassin
/home/spamd/.spamassassin/auto-whitelist
/home/spamd/.spamassassin/bayes_toks
/home/spamd/.spamassassin/bayes_seen
/home/spamd/.bash_profile
/home/spamd/.bash_logout
/home/spamd/.bashrc
/home/s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey Duncan writes:
> Hello. I am getting the following in my logs and wonder if anyone can
> help with the problem:
>
> Nov 9 12:56:01 server spamd[1845]: Failed to run
> __ENV_AND_HDR_FROM_MATCH SpamAssassin test, skipping:__(Can't locate
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp Snizek wrote:
> Hi
>
> when starting SA 3.1.0 I'm getting this in my logs:
[snip]
> Nov 6 14:46:53 mail spamd[20449]: rules: failed to run
> INVALID_HOSTNAME test, skipping:
> Nov 6 14:46:53 mail spamd[20449]: _(Can't locate object method
>
> > when starting SA 3.1.0 I'm getting this in my logs:
>
> > Nov 6 14:46:53 mail spamd[20449]: Can't locate object
> method "check_hostname" via package
"Mail::SpamAssassin::PerMsgStatus"
> > at
> /usr/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/PerMsgStatus.
> pm line 2581, line 45.
>
>
* Philipp Snizek <[EMAIL PROTECTED]>:
> Hi
>
> when starting SA 3.1.0 I'm getting this in my logs:
> Nov 6 14:46:53 mail spamd[20449]: Can't locate object method
> "check_hostname" via package "Mail::SpamAssassin::PerMsgStatus"
> at /usr/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/PerMsgStatus.
Robert Menschel wrote:
> I just installed SA 3.0.4 on my Cygwin machine. I used the tarball,
> extracted it into a new directory of its own making, and installed via
> "perl Makefile.pl", "make", "make test", and "make install".
> "make test" seemed to run OK.
> But when I attempt to use SA, whethe
On Fri, Jun 10, 2005 at 07:50:52PM -0700, Robert Menschel wrote:
> But when I attempt to use SA, whether on an email or --lint,
> I get:
>
> failed to create instance of plugin Mail::SpamAssassin::Plugin::Pyzor:
> Can't locate object method "register_commands" via package
> "Mail::SpamAssassin::Co
33 matches
Mail list logo
