W dniu 30.01.2018 o 14:51, Kevin A. McGrail pisze:
> On 1/30/2018 4:11 AM, Marcin Mirosław wrote:
>> Can error pasted below be related to this commit?
>
> Yes, without a doubt the same bug.
Hi!
I'm answering with one email, thanks for your anwsers and now sa-update
works fine.
Have a nice day
On 1/30/2018 4:11 AM, Marcin Mirosław wrote:
Can error pasted below be related to this commit?
Yes, without a doubt the same bug.
>>>
>> Committed yesterday by davej@
>> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7534
>
>
> Hi!
> Can error pasted below be related to this commit?
> # sa-update -vD
> [...]
> sty 30 10:10:00.540 [3276] dbg: FreeMail: RULE (
ted below be related to this commit?
# sa-update -vD
[...]
sty 30 10:10:00.540 [3276] dbg: FreeMail: RULE (__freemail_reply)
check_freemail_replyto
sty 30 10:10:00.540 [3276] dbg: FreeMail: From address:
ign...@compiling.spamassassin.taint.org
sty 30 10:10:00.540 [3276] dbg: FreeMail: No Reply-To an
On Fri, 26 Jan 2018, Ian Zimmerman wrote:
What is this ***UNCHECKED*** goo in the subjects? Has someone played
with the list manager configuration?
That was probably a side effect of the ClamAV problem, that has been
fixed.
--
John Hardin KA7OHZhttp://www.impsec.org/~j
What is this ***UNCHECKED*** goo in the subjects? Has someone played
with the list manager configuration?
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain
m44s LEFTUse of
> uninitialized value in lc at
> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/RegistryBoundaries.pm line 205.
> plugin: eval failed: Can't locate object method "trim_domain" via package
> "elo...@netvisio.com" (perhaps you forgot to load "
/vendor_perl/Mail/SpamAssassin/RegistryBoundaries.pm
line 205.
plugin: eval failed: Can't locate object method "trim_domain" via
package "elo...@netvisio.com" (perhaps you forgot to load
"elo...@netvisio.com"?) at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/R
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
o the rules.
Hi KAM,
Still seeing these, even after today's update,
Feb 10 13:57:25 svr5 spamd[3922]: rules: failed to run
T_SPF_HELO_PERMERROR test, skipping:
Feb 10 13:57:25 svr5 spamd[3922]: (Can't locate object method
"check_for_spf_helo_permerror" via package "Mail:
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
:42:13 lxmtin2 amavis[6411]: (06411-09) _WARN: rules: failed to
run T_SPF_HELO_PERMERROR test, skipping:\n\t(Can't locate object method
"check_for_spf_helo_permerror" via package
"Mail::SpamAssassin::PerMsgStatus" at (eval 1329) line 19, line
4061.\n)
Feb 9 10:
[9786]: rules: failed to run
T_SPF_HELO_PERMERROR test, skipping:
Feb 9 10:02:58 mail-gw spamd[9786]: (Can't locate object method
"check_for_spf_helo_permerror" via package "Mail:
[...]:SpamAssassin::PerMsgStatus" at (eval 1217) line 357.
Feb 9 10:02:58 mail-gw spamd
On Thu, 2014-05-29 at 03:21 +0200, Karsten Bräckelmann wrote:
> spamassassin --lint -D debug output will show weather that cf file and
Whether. *sigh* When did I unlearn that?
> the plugin are loaded. Running --lint without debug might be worthwhile
> on its own already.
--
char *t="\10pse\0r
On Wed, 2014-05-28 at 20:54 -0400, Art Werschulz wrote:
> > Your SA installation seems to be broken. That's stock code:
> >
> > $ grep -rl check_https_http_mismatch .
> > Mail/SpamAssassin/Plugin/HTTPSMismatch.pm
>
> I have the same thing:
>
> $ pwd
> /usr/share/perl5/vendor_perl/Mail/Sp
On 2/13/2013 11:03 PM, Anirudha Patil wrote:
On Tue, Feb 12, 2013 at 6:16 PM, Mark Martinec
mailto:mark.martinec...@ijs.si>> wrote:
Anirudha,
> I have a stable running setup of postfix after-queue using
amavis-new
> [currently using for content inspection and antivirus only] an
On Tue, Feb 12, 2013 at 6:16 PM, Mark Martinec wrote:
> Anirudha,
>
> > I have a stable running setup of postfix after-queue using amavis-new
> > [currently using for content inspection and antivirus only] and would
> like
> > to use this for additional spam protection.
> >
> > As i understand fro
Anirudha,
> I have a stable running setup of postfix after-queue using amavis-new
> [currently using for content inspection and antivirus only] and would like
> to use this for additional spam protection.
>
> As i understand from the above comments to my query, i dont need to run the
> 'spamd' as
On Tue, Feb 12, 2013 at 5:00 PM, Mark Martinec wrote:
> Anirudha,
>
> > So what should be the ideal setup of running binaries. I want Amavis
> > running both Spamprotection and ANtivirus protection, hence i have below
> > process running in current production
> > 1. Postfix MTA
> > 2. Amavisd
> >
Anirudha,
> So what should be the ideal setup of running binaries. I want Amavis
> running both Spamprotection and ANtivirus protection, hence i have below
> process running in current production
> 1. Postfix MTA
> 2. Amavisd
> 3. Clamd
> Should the spamd be running for spamprotection via amavis-n
On Mon, Feb 11, 2013 at 8:16 PM, Bowie Bailey wrote:
> On 2/11/2013 3:23 AM, Anirudha Patil wrote:
>
>>
>> I have a MTA setup of [Postfix + Amavis-new + ClamAV + Spamassasin] of
>> which only the spamassasin part is disabled. Now i wish to enable the
>> Spamcontrol part.
>>
>
>
> [root@host spa
On 2/11/2013 3:23 AM, Anirudha Patil wrote:
I have a MTA setup of [Postfix + Amavis-new + ClamAV + Spamassasin] of
which only the spamassasin part is disabled. Now i wish to enable the
Spamcontrol part.
[root@host spamassassin]# cat /etc/sysconfig/spamassassin
# Options to spamd
SPAMDOPTION
Anirudha,
> Thank you Mark for the nice explanation. Just one question, can i upgrade
> my spamassasin to latest and still use it with amavis-new 2.6.4 version or
> does it also needs to be upgraded. Just that amavis required lots of
> depencies.
Yes, I believe amavis-new 2.6.4 should be able to
On Mon, Feb 11, 2013 at 6:10 PM, Mark Martinec wrote:
> Anirudha,
>
> > > > My Setup details:
> > > > Postfix version: 2.7.3
> > > > Amavis-new version : 2.6.4-4
> > > > Spamassasin version : SpamAssassin version 3.0.1
> > > > running on Perl version 5.8.5
> > >
> > > The get_tag method was only m
Anirudha,
> > > My Setup details:
> > > Postfix version: 2.7.3
> > > Amavis-new version : 2.6.4-4
> > > Spamassasin version : SpamAssassin version 3.0.1
> > > running on Perl version 5.8.5
> >
> > The get_tag method was only made public with version of SpamAssassin
> > 3.0.3, which was about 8 ye
; But after enabling the spamassasin option in amavis-new, it shows the
> below
> > mentioned error.
> >
> > *(!!)SA failed: Can't locate object method "get_tag" via package
> > "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425, line 29.
&g
t; mentioned error.
>
> *(!!)SA failed: Can't locate object method "get_tag" via package
> "Mail::SpamAssassin::PerMsgStatus" at (eval 86) line 425, line 29.
> at (eval 86) line 467, line 29*.
>
> Also the above line number, does is refer to "spamd&
itelist_sender] => undef,
"anirudha@myhostname" does not match
Feb 11 09:09:10 myhostname amavis[29615]: (29615-01) lookup
[score_recip,score_sender], 1 matches for "myuser@mydomain",
results: "."=>[Amavis::Lookup::RE=ARRAY(0xa33a0e8),HASH(0xa33a154)]
Feb 1
> 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.
>
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.
sassin working am
>> getting this error:
>>
>> spam_scan FAILED: Can't locate object method "get_tag" via package
>> "Mail::SpamAssassin::PerMsgStatus" at (eval 69) line 366.
>>
>> Any help will be greatly appreciated.
>>
> review
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 &qu
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" via package
&quo
8] warn: rules: failed to run
> FAKE_HELO_EXCITE test, skipping:
> Wed Feb 17 10:42:46 2010 [4988] warn: (Can't locate object method
> "check_for_rdns_helo_mismatch" via package "Mail:
> [...]:SpamAssassin::PerMsgStatus" at (eval 1950) line 517.
> Wed Feb 17 10:42:4
Feb 17 10:42:46 2010 [4988] warn: (Can't locate object method
> "check_for_rdns_helo_mismatch" via package "Mail:
> [...]:SpamAssassin::PerMsgStatus" at (eval 1950) line 517.
> Wed Feb 17 10:42:46 2010 [4988] warn: rules: failed to run
> ROUND_THE_WORLD_LO
I've got several warnings during execution of spamd on win32. For every
incoming mail the same warning pops up, saying:
Wed Feb 17 10:42:46 2010 [4988] warn: rules: failed to run FAKE_HELO_EXCITE
test, skipping:
Wed Feb 17 10:42:46 2010 [4988] warn: (Can't locate obj
of problems like the "can't
locate object method" error.
Investigating the Perl modules afterwards, it was clear that some were a new
version, while others were the old version - God only knows how that happened
(probably misuse of CPAN). Restoring the old perl modules from b
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/s
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
419
Any ideas why?
b.
Help...
I'm giving up for the weekend. I'll get back at in Monday.
Starting spamd: Can't locate object method "register_domain" via package
"IO::Socket::INET" at
/usr/local/lib/perl5/5.8.8/i686-linux/IO/Socket/INET.pm line 22.
Compilation failed in require at /
Can anyone tell me why, when I run sa-update on Spamassassin 3.1.8
(installed on Gentoo from portage) I get this message:
Can't locate object method "finish" via package
"Mail::SpamAssassin::Timeout" at
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PluginHandler.pm line
187.
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/B
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.\n
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
On one of my machines, my logs are getting a fair amount of the following
message: Any clue would be welcome.
Aug 20 21:55:26 norcomix spamd[12046]: Can't locate object method "type" via
package "Net::DNS::RR::MX"
at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/D
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
M_MATCH SpamAssassin test, skipping:__(Can't locate
object method "check_for_matching_env_and_hdr_from" via package
"Mail::SpamAssassin::PerMsgStatus" at
/usr/lib/perl5/site_perl/5.8.5/Mail/SpamAss
assin/PerMsgStatus.pm line 2312, line 144._)
Nov 9 12:56:01 se
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
object method "check_for_matching_env_an
:56:01 server spamd[1845]: Failed to run
__ENV_AND_HDR_FROM_MATCH SpamAssassin test, skipping:__(Can't locate
object method "check_for_matching_env_and_hdr_from" via package
"Mail::SpamAssassin::PerMsgStatus" at
/usr/lib/perl5/site_perl/5.8.5/Mail/SpamAss
assin/PerMsgS
45]: Failed to run USER_IN_DEF_SPF_WL
> SpamAssassin test, skipping:__(Can't locate object method "chec
> k_for_def_spf_whitelist_from" via package
> "Mail::SpamAssassin::PerMsgStatus" at
> /usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/Per
> MsgStatus.pm li
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
object method "check_for_matching_env_and_hdr_from" via
-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
> > 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
* 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"
&g
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.pm
line 2581, line
Hello Matt,
Friday, June 10, 2005, 8:01:08 PM, you wrote:
MK> 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".
>>
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
pt to use SA, whether on an email or --lint,
I get:
/* begin output */
failed to create instance of plugin Mail::SpamAssassin::Plugin::Pyzor:
Can't locate object method "register_commands" via package
"Mail::SpamAssassin::Conf::Parser" at
/usr/lib/perl5/site_perl/5.8.5/M
73 matches
Mail list logo
