Hello Bill,
Tuesday, September 17, 2024, 7:15:49 PM, you wrote:
BC> You should upgrade to 4.0.1. That error on that line indicates that you are
running an obsolete 3.4.x version.
As far as that goes I'm just waiting to hear what the host of our VM says about
updating it, as CentOS7 went EOL
Hello Bill,
Tuesday, September 17, 2024, 7:15:49 PM, you wrote:
BC> The likely root cause there is the lack of any reply from the Pyzor server,
which is unlikely to be a per-user
BC> condition.
But another user logs this-
procmail: Match on "< 512000"
procmail: Locking "spamassassin.lock"
pr
On 2024-09-17 at 13:10:13 UTC-0400 (Tue, 17 Sep 2024 18:10:13 +0100)
Niamh Holding
is rumored to have said:
> Hello
>
> I'm seeing the following logged by Procmail in one and only one mailbox and
> as far as I can see there is no difference in the Procmail recipe calling
> Spamassassin in all t
On Fri, 2020-01-10 at 00:56 -0500, Bill Cole wrote:
> On 9 Jan 2020, at 17:32, Chris wrote:
>
> > Since upgrading my Ubuntu 18.04.3 to ClamAV version 0.102.1
> > yesterday
> > I've been seeing this in my syslog:
> >
> > spamd[2455]: Use of uninitialized value $r in scalar chomp at
> > /usr/local/
On Fri, Jan 10, 2020 at 12:56:30AM -0500, Bill Cole wrote:
>
> SA is designed to aggregate a lot of independent imperfect criteria for
> judging mail as spam or ham into a single numeric score, while AV is
> designed to make a highly accurate binary judgment.
That's a bit binary way to look at it
On 9 Jan 2020, at 17:32, Chris wrote:
Since upgrading my Ubuntu 18.04.3 to ClamAV version 0.102.1 yesterday
I've been seeing this in my syslog:
spamd[2455]: Use of uninitialized value $r in scalar chomp at
/usr/local/share/perl/5.26.1/File/Scan/ClamAV.pm line 224
spamd[2455]: Use of uninitiali
n 4/24/2015 1:26 PM, Bertrand Caplet wrote:
Does your Spamd run with -D?
What parameters is it running with?
I don't know why there's so much verbosity...
What's an example spamc call?
> Does your Spamd run with -D?
>
> What parameters is it running with?
Nope, it doesn't :
spamd --create-prefs --max-children 5 --help-home-dir -d --pidfile=/example/
and my local.cf is really short :
rewrite_header Subject *SPAM*
whitelist_from *@genesis.ninja
dns_server 127.0.0.1
ifpl
On 4/23/2015 4:09 PM, Bertrand Caplet wrote:
you don't privide *any* information like version auf spamassassin, perl,
operating system and so my only hint is "man rsyslog"
Yes, sorry about that.
My versions are :
SpamAssassin version 3.4.0
running on Perl version 5.18.2
I just checked again
> you don't privide *any* information like version auf spamassassin, perl,
> operating system and so my only hint is "man rsyslog"
Yes, sorry about that.
My versions are :
SpamAssassin version 3.4.0
running on Perl version 5.18.2
I just checked again my logs and I got lot of info and errors on
Am 23.04.2015 um 21:55 schrieb Bertrand Caplet:
Hey guys,
I have long since errors in my spamassassin logs like this :
Use of uninitialized value $2 in concatenation (.) or string at
/usr/share/perl5/Mail/SpamAssassin/Plugin/URIDNSBL.pm line 1043,
line 400.
From $2 to $4. How can I don't show
On 4/23/2015 3:55 PM, Bertrand Caplet wrote:
Hey guys,
I have long since errors in my spamassassin logs like this :
Use of uninitialized value $2 in concatenation (.) or string at
/usr/share/perl5/Mail/SpamAssassin/Plugin/URIDNSBL.pm line 1043,
line 400.
From $2 to $4. How can I don't show thi
alexus wrote:
> On Thu, Apr 23, 2009 at 4:08 PM, alexus wrote:
>
>> On Wed, Apr 8, 2009 at 12:50 AM, Matt Kettler
>> wrote:
>>
>>> alexus wrote:
>>>
I keep getting this line in my logs everytime there is a spamd calles
Apr 8 03:55:15 mx1 spamd[36109]: Use of uniniti
On Thu, Apr 23, 2009 at 4:08 PM, alexus wrote:
> On Wed, Apr 8, 2009 at 12:50 AM, Matt Kettler wrote:
>> alexus wrote:
>>> I keep getting this line in my logs everytime there is a spamd calles
>>>
>>> Apr 8 03:55:15 mx1 spamd[36109]: Use of uninitialized value $dir in
>>> scalar chomp at /usr/loc
On Wed, Apr 8, 2009 at 12:50 AM, Matt Kettler wrote:
> alexus wrote:
>> I keep getting this line in my logs everytime there is a spamd calles
>>
>> Apr 8 03:55:15 mx1 spamd[36109]: Use of uninitialized value $dir in
>> scalar chomp at /usr/local/bin/spamd line 2118, line 2.
>>
>> i dont suppose
I do run spamd as a spamd user with a flag --vpopmail
$ ~vpopmail/bin/vuserinfo postmas...@xxx.xxx
Error: unable to setuid
$
I even tried with following, still same thing
$ chmod u+s vuserinfo
$ ls -ld ~vpopmail/bin/vuserinfo
-rws--x--x 1 vpopmail vchkpw 225377 Mar 25 01:15 /home/vpopmail
alexus wrote:
> I keep getting this line in my logs everytime there is a spamd calles
>
> Apr 8 03:55:15 mx1 spamd[36109]: Use of uninitialized value $dir in
> scalar chomp at /usr/local/bin/spamd line 2118, line 2.
>
> i dont suppose this is normal
>
Are you using the -v parameter when you st
Andy Millar-2 wrote:
>
> I get the following error when trying to use sa-learn.
>
> SA Learn: Use of uninitialized value in hash element at
> /usr/share/perl5/Mail/SpamAssassin/Message/Metadata/Received.pm line 357.,
> Use of uninitialized value in hash element at
> /usr/share/perl5/Mail/Spam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 08 January 2006 2:04 am, Loren Wilton wrote:
> Since its in sys/hostname/long and you just installed the guts of a new
> machine, I'd be slightly suspicious that you may have a hostname or some
> such mosconfigure on the system.
>
> L
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 08 January 2006 2:04 am, Loren Wilton wrote:
> Since its in sys/hostname/long and you just installed the guts of a new
> machine, I'd be slightly suspicious that you may have a hostname or some
> such mosconfigure on the system.
>
> L
Since its in sys/hostname/long and you just installed the guts of a new
machine, I'd be slightly suspicious that you may have a hostname or some
such mosconfigure on the system.
Loren
On Mon, Nov 28, 2005 at 06:02:11PM -0500, Bob wrote:
> Use of uninitialized value in string eq at
> /usr/local/lib/perl5/site_perl/5.8.4/Mail/SpamAssassin/EvalTests.pm line
> 2671, line 323.
>
> Is there some way to fix this or is it really anything I should concern
> myself with? Thanks in advan
Because of the following part of /usr/bin/spamd... It tries to set the $dir
variable to the virtual homedir, but it can't, so it sets $dir to an
undefined value. Then comp and '.' (string concatenation) complain when they
try to operate on an undefined value. You'll see these warnings since the
Hello Simon,
Monday, May 9, 2005, 2:46:15 AM, you wrote:
SB> Hi Everyone,
SB> Upgraded from 2.64 to 3.0.3 today + a few of the SARE rulesets, and I'm
SB> noticing a spamd warning message in the log files occasionally that was
SB> not occuring on the test server I evaluated 3.0.3 on:
SB> May 9
On Tue, 18 Jan 2005 14:33:55 +, Martin Hepworth
<[EMAIL PROTECTED]> wrote:
Hi
probably means you sa 2.x rules don't parse in the SA 3.x world
have you "spamassassin --lint" checked to if it gives you any more info
ot does it die here as well.??
It's a clean installation, I dont't have a
Hi
probably means you sa 2.x rules don't parse in the SA 3.x world
have you "spamassassin --lint" checked to if it gives you any more info
ot does it die here as well.??
--
Martin Hepworth
Snr Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300
German Staltari wrote:
Hi list, I've up
26 matches
Mail list logo