testing clearly shows that without the explicit set_tag
>>> _LASTEXTERNALRDNS_ and _LASTEXTERNALHELO_ won't be set.
>>> I'm testing this using spamassassin in debug mode to scan a testmessage.
>>> As soon as I re-add the set_tag to PerMsgStatus.pm the tags are set
t; >
> > > But my current testing clearly shows that without the explicit set_tag
> > > _LASTEXTERNALRDNS_ and _LASTEXTERNALHELO_ won't be set.
> > > I'm testing this using spamassassin in debug mode to scan a
> testmessage.
> > > As soon as I re-a
debug mode to scan a testmessage.
> > As soon as I re-add the set_tag to PerMsgStatus.pm the tags are set and
> > tests based on that tags are run. Removing the lines from pm and debug
> > shows that the tests are **not** run anymore.
> >
> > So I somewhat doubt th
t set_tag
> _LASTEXTERNALRDNS_ and _LASTEXTERNALHELO_ won't be set.
> I'm testing this using spamassassin in debug mode to scan a testmessage.
> As soon as I re-add the set_tag to PerMsgStatus.pm the tags are set and
> tests based on that tags are run. Removing the lines from pm and d
Henrik
But my current testing clearly shows that without the explicit set_tag
_LASTEXTERNALRDNS_ and _LASTEXTERNALHELO_ won't be set.
I'm testing this using spamassassin in debug mode to scan a testmessage.
As soon as I re-add the set_tag to PerMsgStatus.pm the tags are set and
test
son why the two tags mentioned in subject are
> > not set in SA? It took me a while to find out why an askdns test was not
> > running. The test relies on _LASTEXTERNALRDNS_ but after running with
> > --debug I found that those tags are not set by SA. Although
> > _LASTEXT
On Wed, 27 Nov 2019 12:59:47 +0100
Tobi wrote:
> Hi,
>
> is there any specific reason why the two tags mentioned in subject are
> not set in SA? It took me a while to find out why an askdns test was
> not running. The test relies on _LASTEXTERNALRDNS_ but after running
> with --debug I found tha
On Wed, 27 Nov 2019 17:00:26 +0100
Tobi wrote:
>
> Issue could occur if trusted/internal networks is not set properly and
> the message contains a non-smtp received header with a public IP. Like
> for example could occur if the message is sent via lmtp. Then the
> received header does not contai
ubject are
>> not set in SA? It took me a while to find out why an askdns test was not
>> running. The test relies on _LASTEXTERNALRDNS_ but after running with
>> --debug I found that those tags are not set by SA. Although
>> _LASTEXTERNALIP_ is set. Also the man page states t
not set by SA. Although
> _LASTEXTERNALIP_ is set. Also the man page states that the two tags
> should exist.
>
> In PerMsgStatus.pm I saw that everything is prepared for the two tags
> but they finally not set (around line 1721). So I changed to
>
>> if ($lasthop) {
>&g
set. Also the man page states that the two tags
should exist.
In PerMsgStatus.pm I saw that everything is prepared for the two tags
but they finally not set (around line 1721). So I changed to
> if ($lasthop) {
>$self->set_tag('LASTEXTERNALIP', $lasthop->{ip}
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/07/09 03:05, quoth Mark Martinec:
> Steven,
>
>> Jul 6 22:38:08 saturn spamd[32217]: Argument "2.long" isn't \
>> numeric in numeric lt (<) at \
>> /usr/lib/perl5/vendor_perl/5.10.0/Mail
Steven,
> Jul 6 22:38:08 saturn spamd[32217]: Argument "2.long" isn't \
> numeric in numeric lt (<) at \
> /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PerMsgStatus.pm line
> 1004.
>
> Should I be concerned?
>
> 595 > spamassassin -V
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jul 6 22:38:08 saturn spamd[32217]: Argument "2.long" isn't \
numeric in numeric lt (<) at \
/usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PerMsgStatus.pm line 1004.
Should I be concerned?
595 > spamassassin -V
> [32179] warn: config: could not find site rules directory
>>> check: no loaded plugin implements 'check_main': cannot scan!
>>> at
>>> /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm
>>> line 164.
>>>
>>> mes
gt; check: no loaded plugin implements 'check_main': cannot scan!
>> at
>> /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm
>> line 164.
>>
>> message can be found at
>>
>> http://real-world-systems.com/mail/lottery.msg
> D
gt; /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm
> line 164.
>
> message can be found at
>
> http://real-world-systems.com/mail/lottery.msg
Does your spamassassin work properly when you run spamassassin --lint?
Just from the look of the error you got, it
gt; /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm
> line 164.
>
> message can be found at
>
> http://real-world-systems.com/mail/lottery.msg
Don't forget to add the "-t" flag if you want to see how SA will score a
message. I tested the
/SpamAssassin/PerMsgStatus.pm
line 164.
message can be found at
http://real-world-systems.com/mail/lottery.msg
On Fri, 2008-07-04 at 16:47 +0200, Alex Woick wrote:
> Richard Johnson schrieb am 04.07.2008 06:35:
> > I then reinstall:
> > apt-get install spamassassin
> [...]
> > Suggested packages:
> > razor libnet-ident-perl libio-socket-ssl-perl pyzor libmail-dkim-perl
> > Recommended packages:
> > spa
illed.
spamd.
and as before the spamassassin -D --lint gives:
[27161] dbg: bayes: no dbs present, cannot tie DB
R/O: /user1/.spamassassin/bayes_toks
check: no loaded plugin implements 'check_main': cannot scan!
at /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 164.
This is driving me crazy now. This has to be a bust install?
Richard Johnson schrieb am 04.07.2008 06:35:
I then reinstall:
apt-get install spamassassin
[...]
Suggested packages:
razor libnet-ident-perl libio-socket-ssl-perl pyzor libmail-dkim-perl
Recommended packages:
spamc re2c libsys-syslog-perl
The following NEW packages will be installed
spam
cannot scan!
at /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 164.
Would that look 'seriously broke'?
For a just installed and never modified SpamAssassin package that
do look broken. Unless the package came with some information
about additional setup instructions the
On Fri, 2008-07-04 at 12:39 +0200, Alex Woick wrote:
> Richard Johnson schrieb am 03.07.2008 10:58:
>
> > check: no loaded plugin implements 'check_main': cannot scan! at
> > /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 164.
>
> > [9086] dbg:
Richard Johnson schrieb am 03.07.2008 10:58:
check: no loaded plugin implements 'check_main': cannot scan! at
/usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 164.
[9086] dbg: ignore: using a test message to lint rules
[9086] dbg: config: using "/etc/spamassassin"
With this in mind it started to look like a perl issue:
> I have just spotted the line: "No /usr/bin/perl found"
So I checked:
-rwxr-xr-x 2 root root 1.1M 2007-12-04 09:18 perl
-rwxr-xr-x 2 root root 1.1M 2007-12-04 09:18 perl5.8.8
-rwxr-xr-x 1 root root 37K 2007-12-04 09:
Richard Johnson <[EMAIL PROTECTED]> wrote:
[...]
> Stopping SpamAssassin Mail Filter Daemon: No /usr/bin/perl found
This is odd, try to fix it.
[...]
> check: no loaded plugin implements 'check_main': cannot scan!
> at /usr/share/perl5/Mail/Spa
esent, cannot tie DB
R/O: /root/.spamassassin/bayes_toks
[6727] dbg: config: score set 0 chosen.
[6727] dbg: message: main message type: text/plain
[6727] dbg: message: MIME PARSER START
[6727] dbg: message: parsing normal part
[6727] dbg: message: MIME PARSER END
[6727] dbg: bayes: no dbs present, cannot tie DB
R/O: /root/.spamassassin/bayes_toks
check: no loaded plugin implements 'check_main': cannot scan!
at /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 164.
Would that look 'seriously broke'?
On Thu, 2008-07-03 at 20:38 +0100, Richard Johnson wrote:
> On Thu, 2008-07-03 at 13:34 -0400, Theo Van Dinter wrote:
> > If you're missing pre files, I would suggest reinstalling SA. A normal
> > installation will include the content you need, and who knows what else you
> > are missing.
>
> I
On Thu, 2008-07-03 at 13:34 -0400, Theo Van Dinter wrote:
> On Thu, Jul 03, 2008 at 06:01:21PM +0100, Richard Johnson wrote:
> > As the .pre files are missing, what would I do to rectify it? What
> > should they contain?
>
> If you're missing pre files, I would suggest reinstalling SA. A normal
On Thu, 2008-07-03 at 18:01 +0100, Richard Johnson wrote:
> Thank you, Karsten. I've learned the [ctrl] + [l] now. My apologies, I
> did not want to start a war.
Nah, you didn't, don't worry. :)
guenther
--
char *t="[EMAIL PROTECTED]";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=
On Thu, Jul 03, 2008 at 06:01:21PM +0100, Richard Johnson wrote:
> As the .pre files are missing, what would I do to rectify it? What
> should they contain?
If you're missing pre files, I would suggest reinstalling SA. A normal
installation will include the content you need, and who knows what el
On Thu, 2008-07-03 at 16:34 +0200, Karsten Bräckelmann wrote:
> > Leaving the evolution plugin thing to one side for now.
> >
> > I don't have any .pre files. /etc/spamassassin is empty.
>
> See, there's your problem.
>
Thank you, Karsten. I've learned the [ctrl] + [l] now. My apologies, I
di
> >
> > > So, I ran this:
> > > spamassassin --lint
> > >
> > > and ended up with:
> > >
> > > [9086] dbg: bayes: untie-ing
> > > check: no loaded plugin implements 'check_main': cannot scan!
> > > at /usr/share/pe
ran this:
> spamassassin --lint
>
> and ended up with:
>
> [9086] dbg: bayes: untie-ing
> check: no loaded plugin implements 'check_main': cannot scan!
> at /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 164.
Last time I've seen this (chatter on
in headers. My thinking was, let me test
spamassassin is working at all before I get into MTA's, MUA's etc.
So, I ran this:
spamassassin --lint
and ended up with:
[9086] dbg: bayes: untie-ing
check: no loaded plugin implements 'check_main': cannot scan!
at /usr/share/p
's, MUA's etc.
So, I ran this:
spamassassin --lint
and ended up with:
[9086] dbg: bayes: untie-ing
check: no loaded plugin implements 'check_main': cannot scan!
at /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 164.
I then ran:
spamassassin -D --lint
and got:
[9086] dbg:
spamd[29634]: Use of uninitialized value in
concatenation (.) or string at
/usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 2669, line
60.
Jun 26 16:55:37 MY-SERVER last message repeated 2 times
Jun 26 16:55:37 MY-SERVER spamd[29634]: Number found where operator expected
at (eval 277) line 10
likely the result of a misconfiguration on my part or is
> it more likely a bug in spamassassin that I should report to -dev?
>
>
> Sep 14 12:51:28 moose spamd[29477]: Use of uninitialized value in
> concatenation (.) or string at
> /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line
my part or is
it more likely a bug in spamassassin that I should report to -dev?
Sep 14 12:51:28 moose spamd[29477]: Use of uninitialized value in
concatenation (.) or string at
/usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 2669.
Sep 14 12:51:28 moose spamd[29477]: Number found wher
> perl install Mail::SpamAssassin
>
>
> Does anyone know a way to fix this?
>
> Thanks
>
> Nightduke
>
> Sep 4 23:54:50 bck00654 spamd[5745]: Use of uninitialized value in
> concatenation (.) or string at
> /usr/share/perl5/Mail/SpamA
not running 3.2.3.. or at
least not completely.. The PerMsgStatus.pm for 3.2.3 isn't even 2669
lines long, so having an error at that line isn't possible, unless
you've got a PerMsgStatus.pm from some different, presumably older, version.
Is there any chance you've got two cop
uninitialized value in
concatenation (.) or string at
/usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 2669, line 37.
Sep 4 23:54:50 bck00654 last message repeated 2 times
Sep 4 23:54:50 bck00654 spamd[5745]: Number found where operator expected at
(eval 2497) line 10, near "}
Sep 4 23:
:
>>
>>Use of uninitialized value in concatenation (.) or string at
> /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm
> line 1628, line 323
>>
>>Line 1628 is the 3rd line in this subroutine--
>>
>>sub hash_line_for_rule {
>> my (
SpamAssassin/PerMsgStatus.pm line
>1628, line 323
>
>Line 1628 is the 3rd line in this subroutine--
>
>sub hash_line_for_rule {
> my ($self, $rulename) = @_;
> return "\n".'#line 1 "'.
>$self->{conf}->{source_file}->{$rulename}.
I see this warning (error?) hundreds of thousands of times in my logs:
Use of uninitialized value in concatenation (.) or string at
/usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line
1628, line 323
Line 1628 is the 3rd line in this subroutine--
sub hash_line_for_rule
Thanks for the immediate answer!It seems that the old SA was under /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/while the new one under /usr/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/rpm reported two packages spamassassin and perl-spamassassin.
I have deinstalled these using YAST (rpm repor
Thomas Schlosser <[EMAIL PROTECTED]> [10-06-2006 15:38]:
[...]
> I updated it via perl -MCPAN - e shell -> force install Mail::SpamAssassin
> The output was too long to have a chance to see if any problems have been
> reportet.
New SA should have been installed somewhere around /usr/local (if your
Hi,I have updated my SA installation yesterday. Most but not all seems to run well.In my mail.log I constantly find these errors all referring on some methods called from PerMsgStatus.pm:snip
Jun 10 12:21:54 homesrv spamd[6367]: Failed to run __ENV_AND_HDR_FROM_MATCH SpamAssassin test
Geez I hate Bugzilla and its searches that do not work. SO I don't know
if this was a duplicate or not. It now has number 4445. It is a particularly
annoying bug.
(A search for "SpamAssassin/PerMsgStatus.pm line 2119" returned a bazillion
hits the first dozen of which did not match
ssage -
From: "jdow" <[EMAIL PROTECTED]>
> error: Insecure dependency in eval while running setuid at
> /usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line
2119._
> , continuing
>
>
> Ayup - another one of those horrid problems.
>
> I am run
te_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line 2119._
, continuing
> error: Insecure dependency in eval while running setuid at
> /usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line
2119._
> , continuing
>
>
> Ayup - another one of those horrid problems.
>
>
error: Insecure dependency in eval while running setuid at
/usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line 2119._
, continuing
Ayup - another one of those horrid problems.
I am running 3.04 with spamd and spamc. I get this on "full" rules.
However, I do not get
r/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line 2091._
>No such file or directory, continuing
>===8<---
>
I'd be looking closely at all your "full" type rules. The offending line
is the execution of a regex for a "full" rule.
Clearly a normal ru
sin/PerMsgStatus.pm line 2091._
No such file or directory, continuing
===8<---
Alas, there is no indication of WHAT file or directory is needed here.
Sometimes the bug repeats with "spamc
running setuid at
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/PerMsgStatus.pm line
1669, line 216._ , continuing
and some spam was slipping through untagged.
When I disabled the rbl checks, the error went away and so did the spam
misses.
Any suggestions?
david
/5.8.0/Mail/SpamAssassin/PerMsgStatus.pm line
1669, line 216._ , continuing
and some spam was slipping through untagged.
When I disabled the rbl checks, the error went away and so did the spam
misses.
Any suggestions?
david
57 matches
Mail list logo
