On 2021-12-29 at 19:07:06 UTC-0500 (Wed, 29 Dec 2021 18:07:06 -0600)
Robert Nicholson
is rumored to have said:
I just updated from 3.4.0 to 3.4.6 and the output in perl debugger
when I programmatically using SA is quite noisy.
Where can I find 3.4.1 etc so I can incrementally update from
I just updated from 3.4.0 to 3.4.6 and the output in perl debugger when I
programmatically using SA is quite noisy.
Where can I find 3.4.1 etc so I can incrementally update from 3.4.0 so I can
see where the dramatic change is coming from?
When I use my script in the debugger from 3.4.0 there
On Sat, 2017-10-14 at 14:45 +0100, RW wrote:
> spamkiller looks to have been been written for use with fetchmail;
>
Indeed it was, and ran that way until I got pissed off with the bugs in
fetchmail - especially the one that caused it to leave delivered mail
on the remote server, never to be automat
On Wed, 11 Oct 2017 20:45:10 -0700
Imam Toufique wrote:
> Hi Martin,
>
> I have not had a chance to work on the problem yet, I was busy with
> our stuff. I will test again with your suggestion later this week.
I would suggest you look at other ways of doing this. Filing spam files
into a dedica
Hi Martin,
I have not had a chance to work on the problem yet, I was busy with our
stuff. I will test again with your suggestion later this week.
Thank you so very much for your help!
On Wed, Oct 11, 2017 at 5:27 AM, Martin Gregorie
wrote:
> On Mon, 2017-10-09 at 17:24 -0700, Imam Toufique
On Mon, 2017-10-09 at 17:24 -0700, Imam Toufique wrote:
>
> So, I followed the example and created my command below:
>
> su fetchmail -s /bin/sh -c "/usr/bin/spamc |
> /usr/local/bin/spamkiller
> -c=/usr/bin/fetchmail -a -v -f /opt/RT/4.4.2/etc/fetchmailrc"
>
> when I run the above, nothing seems
On 9 Oct 2017, at 13:42, Benny Pedersen wrote:
more help ask on amavisd maillist
Benny: he already said he was using spamc/spamd, which means amavisd
isn't involved at all.
e
> > > to
> > > the sender when it discards a message.
> > >
> > > For example, if your mail volume is very low you could retrieve
> > > mail
> > > from your domain's mailbox at your ISP with 'getmail', run it past
> > > SA
>
> > > the sender when it discards a message.
> > >
> > > For example, if your mail volume is very low you could retrieve
> > > mail
> > > from your domain's mailbox at your ISP with 'getmail', run it past
> > > SA
> > > to
t; SA
> > to mark it as ham or spam and then through something that
> > quarantine
> > spam and passes ham to an internal MTA for delivery to recipients
> > on
> > your LAN.
> >
> >
> > Martin
> >
> >
> >
> > > thanks.
&
gt;
> > thanks.
> >
> > On Mon, Oct 9, 2017 at 7:47 AM, RW
> > wrote:
> >
> > > On Mon, 9 Oct 2017 00:49:33 -0700
> > > Imam Toufique wrote:
> > >
> > > > Hello everyone,
> > > >
> > > > I am runni
for delivery to recipients on
your LAN.
Martin
> thanks.
>
> On Mon, Oct 9, 2017 at 7:47 AM, RW
> wrote:
>
> > On Mon, 9 Oct 2017 00:49:33 -0700
> > Imam Toufique wrote:
> >
> > > Hello everyone,
> > >
> > > I am running SpamAssass
On Mon, 9 Oct 2017, Imam Toufique wrote:
Yes, I restarted spamd after changing blacklist entries. Actually, I think
it it working, as it is changing the e-mail subject lines to
"SPAM". But it is not deleting/discarding those mails.
SA does not, itself, perform *delivery* of messages.
RW <mailto:rwmailli...@googlemail.com>> wrote:
On Mon, 9 Oct 2017 00:49:33 -0700
Imam Toufique wrote:
> Hello everyone,
>
> I am running SpamAssassin 3.4.0 in centOS 7, and I can't get
> blacklist_from to work.
...
> an external op
Imam Toufique skrev den 2017-10-09 19:25:
not sure how to do that. Can you please tell me how to do that? I
want all e-mails (in this example... ) from gmail.com [2] to be
deleted/discarded as soon as SA scans them.
then add it to mta stage to reject *@gmail.com as sender, rejects is not
wh
ll
e-mails (in this example... ) from gmail.com to be deleted/discarded as
soon as SA scans them.
thanks.
On Mon, Oct 9, 2017 at 7:47 AM, RW wrote:
> On Mon, 9 Oct 2017 00:49:33 -0700
> Imam Toufique wrote:
>
> > Hello everyone,
> >
> > I am running SpamAssass
On Mon, 9 Oct 2017 00:49:33 -0700
Imam Toufique wrote:
> Hello everyone,
>
> I am running SpamAssassin 3.4.0 in centOS 7, and I can't get
> blacklist_from to work.
...
> an external option in getmail. when I send mail from my gmail
> account, spamc does not honor
Hello everyone,
I am running SpamAssassin 3.4.0 in centOS 7, and I can't get blacklist_from
to work. Here is my local.cf:
rewrite_header subject *SPAM*
required_hits 5
report_safe 0
#rewrite_header Subject [SPAM]
use_bayes 1
ok_languages en
#bayes_auto_le
Am 16.09.2016 um 13:41 schrieb Marcus Schopen:
> Hi Robert,
>
> Am Freitag, den 16.09.2016, 13:02 +0200 schrieb Robert Schetterer:
>> Am 16.09.2016 um 12:48 schrieb Marcus Schopen:
>>> Hi Patrick,
>>>
>>> Am Donnerstag, den 15.09.2016, 22:02 -0400 schrieb Patrick Domack:
Sounds like a lot of
I had no reason to backport it, xenial didn't exist when 3.4.1 was
released, and there is no need to backport a package just for a new
source code change, just apply the current package to the new source
code.
Quoting Marcus Schopen :
Hi Patrick,
Am Donnerstag, den 15.09.2016, 22:02 -04
Hi Robert,
Am Freitag, den 16.09.2016, 13:02 +0200 schrieb Robert Schetterer:
> Am 16.09.2016 um 12:48 schrieb Marcus Schopen:
> > Hi Patrick,
> >
> > Am Donnerstag, den 15.09.2016, 22:02 -0400 schrieb Patrick Domack:
> >> Sounds like a lot of work for an old spamassassin version.
> >>
> >> https
Am 16.09.2016 um 12:48 schrieb Marcus Schopen:
> Hi Patrick,
>
> Am Donnerstag, den 15.09.2016, 22:02 -0400 schrieb Patrick Domack:
>> Sounds like a lot of work for an old spamassassin version.
>>
>> https://launchpad.net/%7Epatrickdk/+archive/ubuntu/production/+sourcepub/5219815/+listing-archive-
Hi Patrick,
Am Donnerstag, den 15.09.2016, 22:02 -0400 schrieb Patrick Domack:
> Sounds like a lot of work for an old spamassassin version.
>
> https://launchpad.net/%7Epatrickdk/+archive/ubuntu/production/+sourcepub/5219815/+listing-archive-extra
H ... do you think better backporting 3.4.1
Sounds like a lot of work for an old spamassassin version.
https://launchpad.net/%7Epatrickdk/+archive/ubuntu/production/+sourcepub/5219815/+listing-archive-extra
Quoting Marcus Schopen :
Hi,
I've backported 3.4.0 from Ubuntu 14.04 TLS for Ubuntu 12.04 LTS (perl
5.14.2), which comes
Hi,
I've backported 3.4.0 from Ubuntu 14.04 TLS for Ubuntu 12.04 LTS (perl
5.14.2), which comes with very old version 3.3.2 (can't upgrade the
complete host right now). Before installing it: is there anything to be
aware of, beside better wiping bayes database and starting fresh? [1]
C
Just is case anyone else runs into this issue, the OmniOS build script was
calling "make pure install”
, when it should have just been calling “make install”
I changed it to “make install” and all is good.
> On Jan 27, 2015, at 4:17 PM, Alex McWhirter
> wrote:
>
> I’m
I’m building 3.4.0 on OmniOS , which is similar to Solaris. I am also using
PERL 5.20.1. Spam assassin compiles fine and seems to run fine, but the
configuration files are never installed. These are the options i am specifying
into “perl Makefiles.PL”
SYSCONFDIR=$PREFIX/etc
;>
>>> I have a CentOS release 5.5 (Final)
>>> SpamAssassin version 3.3.1
>>> running on Perl version 5.8.8
>>>
>>> I would like to upgrade it to 3.4.0 so I upgrade cpan module and install
>>> all the module on INSTALL document in the
2015-01-20 18:23 GMT+01:00 Mark Martinec :
> Carlo Filippetto wrote:
>
>> I have a CentOS release 5.5 (Final)
>> SpamAssassin version 3.3.1
>> running on Perl version 5.8.8
>>
>> I would like to upgrade it to 3.4.0 so I upgrade cpan module and install
>&g
Carlo Filippetto wrote:
I have a CentOS release 5.5 (Final)
SpamAssassin version 3.3.1
running on Perl version 5.8.8
I would like to upgrade it to 3.4.0 so I upgrade cpan module and
install
all the module on INSTALL document in the default root of the packages.
When I tried to install it
hi all,
I have a CentOS release 5.5 (Final)
I have
SpamAssassin version 3.3.1
running on Perl version 5.8.8
I would like to upgrade it to 3.4.0 so I upgrade cpan module and install
all the module on INSTALL document in the default root of the packages.
When I tried to install it with
perl
On Jan 8, 2015, at 11:52 AM, Benny Pedersen wrote:
> so you tested what happend if all plugins is disabled ?
Ah, no, I did not do that. I saw no need since I actually want to use the
plugins... =) So no, I guess I did not quite address you concern.
--- Amir
denpencyinfo says its needed, but sometimes its falls alarms for plugins
i discovered that problem as a gentoo maintainer for 3.4.0, still not a
big problem, but if it can be solved i like this to be in 3.4.2 atleast
bunch of updates into
the 5.8.8 packaged version. It's not purely "autopilot" nor "doing nothing."
> possible test:
> spamassassin 2>&1 -D --lint | less
As I mentioned, I run SA 3.4.0 on CentOS 5.11 with no problems. Running lint,
the only thing I see is a b
Eric Broch skrev den 2015-01-08 18:47:
Sorry, Benny I meant 5.8.8 is the latest version on RHEL 5 / COS 5. I
mistyped.
no need to sorry, its just me that hate to see more and more systems
runs on autopilot and just want to have it fixed by doing nothing on the
maintainer side of view, now yo
On 1/8/2015 10:28 AM, Benny Pedersen wrote:
> Kevin A. McGrail skrev den 2015-01-08 17:18:
>> On 1/8/2015 10:55 AM, Reindl Harald wrote:
>>>
>>> Am 08.01.2015 um 16:51 schrieb Eric Broch:
>>>> I read through the release announcements for Spamassassin 3.4.0
Am 08.01.2015 um 18:28 schrieb Benny Pedersen:
Kevin A. McGrail skrev den 2015-01-08 17:18:
On 1/8/2015 10:55 AM, Reindl Harald wrote:
Am 08.01.2015 um 16:51 schrieb Eric Broch:
I read through the release announcements for Spamassassin 3.4.0 (I'm
currently running 3.3.2) and noticed i
Kevin A. McGrail skrev den 2015-01-08 17:18:
On 1/8/2015 10:55 AM, Reindl Harald wrote:
Am 08.01.2015 um 16:51 schrieb Eric Broch:
I read through the release announcements for Spamassassin 3.4.0 (I'm
currently running 3.3.2) and noticed it was tested with perl 5.18.2.
Can
Spamassassin
On 1/8/2015 10:55 AM, Reindl Harald wrote:
Am 08.01.2015 um 16:51 schrieb Eric Broch:
I read through the release announcements for Spamassassin 3.4.0 (I'm
currently running 3.3.2) and noticed it was tested with perl 5.18.2. Can
Spamassassin 3.4.0 be run safely with perl 5.5.8 which i
I am running 3.4.0 on CentOS 5.11 with perl 5.8.8 with no issues whatsoever.
--- Amir
thumbed via iPhone
> On Jan 8, 2015, at 8:51 AM, Eric Broch wrote:
>
> List,
> I read through the release announcements for Spamassassin 3.4.0 (I'm
> currently running 3.3.2) and notice
Am 08.01.2015 um 16:51 schrieb Eric Broch:
I read through the release announcements for Spamassassin 3.4.0 (I'm
currently running 3.3.2) and noticed it was tested with perl 5.18.2. Can
Spamassassin 3.4.0 be run safely with perl 5.5.8 which is the latest for
RHEL 5 or with perl 5.10.1 whi
List,
I read through the release announcements for Spamassassin 3.4.0 (I'm
currently running 3.3.2) and noticed it was tested with perl 5.18.2. Can
Spamassassin 3.4.0 be run safely with perl 5.5.8 which is the latest for
RHEL 5 or with perl 5.10.1 which is the latest for RHEL 6?
Eric
On 10/16/2014 08:55 AM, Marc Perkel wrote:
Thanks - I'll try to install it.
On 10/15/14 12:38, Timo Schöler wrote:
Am 15. Oktober 2014 19:10:28 MESZ, schrieb Marc Perkel
:
I'm thinking about trying out SA 3.4.0 on Centos 6 or 7 if I have to.
Just wondering - is it worth it? An
Thanks - I'll try to install it.
On 10/15/14 12:38, Timo Schöler wrote:
Am 15. Oktober 2014 19:10:28 MESZ, schrieb Marc Perkel
:
I'm thinking about trying out SA 3.4.0 on Centos 6 or 7 if I have to.
Just wondering - is it worth it? And is Redis available and how hard is
it to act
Am 15. Oktober 2014 19:10:28 MESZ, schrieb Marc Perkel
:
>I'm thinking about trying out SA 3.4.0 on Centos 6 or 7 if I have to.
>Just wondering - is it worth it? And is Redis available and how hard is
>
>it to actually make it work?
Wrt redis, yes, it is and it's really e
I'm thinking about trying out SA 3.4.0 on Centos 6 or 7 if I have to.
Just wondering - is it worth it? And is Redis available and how hard is
it to actually make it work?
Thanks in advance
--
Marc Perkel - Sales/Support
supp...@junkemailfilter.com
http://www.junkemailfilter.com
Junk
(907) 586-0242, Fax: (907) 586-4500
Registered Linux User No: 307357
-Original Message-
From: Michael Schaap [mailto:spamassas...@mscha.org]
Sent: Monday, August 25, 2014 12:23 PM
To: users@spamassassin.apache.org
Subject: Upgrading to SA 3.4.0 on Ubuntu Precise (12.04)
Hi,
On my serv
Hi,
On my server, I'm running SpamAssassin 3.3.2 as provided as a package on
Ubuntu Precise (12.04 LTS).
I'd like to upgrade to SpamAssassin 3.4.0, but there is no upgrade
available for Precise (12.04). I could upgrade to Ubuntu Trusty
(14.04), but I'm afraid to...
Alterna
On 06/07/2014 01:47 PM, hospice admin wrote:
Date: Sat, 7 Jun 2014 13:43:37 +0200
From: axb.li...@gmail.com
To: users@spamassassin.apache.org
Subject: Re: Advice re- SA 3.4.0
On 06/07/2014 01:33 PM, hospice admin wrote:
Date: Sat, 7 Jun 2014 13:22:13 +0200 From: axb.li...@gmail.com To
> Date: Sat, 7 Jun 2014 13:43:37 +0200
> From: axb.li...@gmail.com
> To: users@spamassassin.apache.org
> Subject: Re: Advice re- SA 3.4.0
>
> On 06/07/2014 01:33 PM, hospice admin wrote:
> >
> >
> >
> >> Date: Sat, 7 Jun 2014 13:22:13 +
On 06/07/2014 01:33 PM, hospice admin wrote:
Date: Sat, 7 Jun 2014 13:22:13 +0200 From: axb.li...@gmail.com To:
users@spamassassin.apache.org Subject: Re: Advice re- SA 3.4.0
On 06/07/2014 01:09 PM, hospice admin wrote:
I was wondering about this one and had put it to one side until I
had
> Date: Sat, 7 Jun 2014 13:22:13 +0200
> From: axb.li...@gmail.com
> To: users@spamassassin.apache.org
> Subject: Re: Advice re- SA 3.4.0
>
> On 06/07/2014 01:09 PM, hospice admin wrote:
> > I was wondering about this one and had put it to one side until I had
>
On 06/07/2014 01:09 PM, hospice admin wrote:
I was wondering about this one and had put it to one side until I had
a chance to look at the memory implications in more detail. We run a
VM infrastructure here, so I'll load it up on one server and keep
throwing resources at it until I have something
> Date: Sat, 7 Jun 2014 12:49:32 +0200
> From: axb.li...@gmail.com
> To: users@spamassassin.apache.org
> Subject: Re: Advice re- SA 3.4.0
>
> On 06/07/2014 12:19 PM, hospice admin wrote:
> > Just wondering if anyone had any advice along the lines "you really
&g
On 06/07/2014 12:19 PM, hospice admin wrote:
Just wondering if anyone had any advice along the lines "you really
must do this", or "you'd be crazy to do that" re- all the new stuff,
etc?
I'm particularly 'interested' in things relating to Bayes, which has
bitten me in the rear so many times, b
Hi Team,
Ive finally completed the upgrade of all my mail servers from FC18 + SA 3.3.2 +
Perl 5.15.3 to FC20 + SA 3.4.0 + Perl 5.18.2. I run SA from within MineDefang
2.74 in both cases.
I've simply moved across all the rules and plug-ins I used 3.3.2 to 3.4.0, and
during our
Robert Nicholson wrote:
My first attempt an integrating 3.4.0 (hopefully to solve the
DnsResolver.pm Invalid Argument issue) ends up with
Subroutine NetAddr::IP::STORABLE_freeze redefined at
/usr/local/lib64/perl5/NetAddr/IP.pm line 362.
at /usr/local/lib64/perl5/NetAddr/IP.pm line 362
Robert Nicholson skrev den 2014-04-11 04:45:
Well I appear to have gotten it working..
all ?
For now everything works if I simply comment out the NetAddr::IP in
NetSet.pm
show "spamassassin 2>&1 -D --lint" here
i think you just need more updates
Well I appear to have gotten it working..
For now everything works if I simply comment out the NetAddr::IP in NetSet.pm
On Apr 10, 2014, at 8:11 PM, Robert Nicholson
wrote:
> My first attempt an integrating 3.4.0 (hopefully to solve the DnsResolver.pm
> Invalid Argument issue) ends u
My first attempt an integrating 3.4.0 (hopefully to solve the DnsResolver.pm
Invalid Argument issue) ends up with
Subroutine NetAddr::IP::STORABLE_freeze redefined at
/usr/local/lib64/perl5/NetAddr/IP.pm line 362.
at /usr/local/lib64/perl5/NetAddr/IP.pm line 362.
NetAddr::IP::import
Wolfgang Zeikat wrote:
> Bob Proulx wrote:
> > spamassassin -d -t -D < mail.file | less
>
> Note: in the above command you did _not_ redirect STDERR to STDOUT
Oops. My bad. I should have shown that. I was concentrating on the
options and neglected the right hand side.
> > spamassassin -d -t
In an older episode, on 2014-02-20 23:56, Bob Proulx wrote:
> spamassassin -d -t -D < mail.file | less
Note: in the above command you did _not_ redirect STDERR to STDOUT
In an older episode, on 2014-02-21 19:20, Bob Proulx wrote:
I picked a spam message and piped it into:
spamassassin -d -
Kevin A. McGrail wrote:
> Bob Proulx wrote:
> >It looks to me that -D now disables Bayes as a regression in 3.4.0.
>
> Can't recreate and can't see how that's possible. -D turns on debug
> output and I don't see any references to the config option in the
>
On 2/20/2014 5:56 PM, Bob Proulx wrote:
With the sa-update channel problems now behind us I have upgraded
again to 3.4.0 and am using it. It appears now that using -D turns
off Bayes?
spamassassin -d -t -D < mail.file | less
No BAYES_* anything is recorded. Versus using:
spamassas
With the sa-update channel problems now behind us I have upgraded
again to 3.4.0 and am using it. It appears now that using -D turns
off Bayes?
spamassassin -d -t -D < mail.file | less
No BAYES_* anything is recorded. Versus using:
spamassassin -d -t < mail.file | less
Where
On 18/02/14 15:49, Mark Martinec wrote:
> One server in each continent might be acceptable, but hasn't
> been tried.
Yeah, in fact I can separate into Europe and US (responsible for
different domains), so two Redis makes more sense.
> No corruption can happen due to network problems. Cases where
2014-02-18, Jason Haar wrote:
We have a geographically distributed edge mail relay network (some in
the US and some in Europe) and I'm wondering if the new REDIS support
could be used to centralize our Bayes?
If you have a fast and reliable connection between the two,
then in principle it could
Hi there
We have a geographically distributed edge mail relay network (some in
the US and some in Europe) and I'm wondering if the new REDIS support
could be used to centralize our Bayes?
Is anything special required to be done to get 4-6 spamd servers to use
the same REDIS backend? Will network
Hi,
I am a working on it although quite rusty on spec file study, comparison,
and editing etc.
Yet since I don't know everything about 3.4.0...
Would someone with a known good working spamassassin spec file that works
well with rhel4 - rhel6 machines please share?
I've been abl
Greetings
Thank you SpamAssassin team and other contrib people for all your hard work
in getting out 3.4.0 and more !
I have been playing with the spec file for spamassassin 3.3.1 and have been
able to get 3.4.0 to turn into the RPM's
Then I do a yum localinstall test and it looks like I
Thank you -- that is what I needed
On Wed, 12 Feb 2014, Mark Martinec wrote:
On 2/12/2014 11:53 AM, jpff wrote:
I got the same error installing via cpan. Trouble is I do not know
where the other system is or how to find it. There are a number of
Util.pm files ll over the place.
This is on
On 2/12/2014 11:53 AM, jpff wrote:
> I got the same error installing via cpan. Trouble is I do not know
> where the other system is or how to find it. There are a number of
> Util.pm files ll over the place.
> This is on a debian system but not really using their package
This should get rid of
On 2/12/2014 11:53 AM, jpff wrote:
I got the same error installing via cpan. Trouble is I do not know
where the other system is or how to find it. There are a number of
Util.pm files ll over the place.
This is on a debian system but not really using their package
==John ff
Please reopen th
I got the same error installing via cpan. Trouble is I do not know where
the other system is or how to find it. There are a number of Util.pm
files ll over the place.
This is on a debian system but not really using their package
==John ff
On 2/12/2014 11:02 AM, Mark Martinec wrote:
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7007#c1
For the archive: it was an installation error, having two versions
of SpamAssassin installed at the same time in different locations.
Mark
Good catch!
> > https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7007#c1
For the archive: it was an installation error, having two versions
of SpamAssassin installed at the same time in different locations.
Mark
am 12.02.14 03:50 schrieb Kevin A. McGrail :
Jim, what did you comment out more specifically?
Jim Knuth wrote:
am 12.02.14 02:50 schrieb Benny Pedersen :
On 2014-02-12 02:48, Jim Knuth wrote:
really? Thank you. :) For now I have deactivated the entry
in v
Jim, what did you comment out more specifically?
Jim Knuth wrote:
>am 12.02.14 02:50 schrieb Benny Pedersen :
>
>> On 2014-02-12 02:48, Jim Knuth wrote:
>>
>>> really? Thank you. :) For now I have deactivated the entry
>>> in v340.pre.
>>
>> if you have found workaround aswell post it to the tick
it you have found a bug, with i created a ticket for now
The Bug 7007 does not have a problem description.
now it is complete. , I overlooked, Sorry
Jim Knuth wrote:
I've had upgraded of version 3.4.0 and now I'm
getting that errors from cron
test -e /usr/sbin/amavisd-new-cron
ticket for now
The Bug 7007 does not have a problem description.
Jim Knuth wrote:
I've had upgraded of version 3.4.0 and now I'm
getting that errors from cron
test -e /usr/sbin/amavisd-new-cronjob && /usr/sbin/amavisd-new-cronjob
sa-clean
What is amavisd-new-cronjob and wh
am 12.02.14 02:50 schrieb Benny Pedersen :
On 2014-02-12 02:48, Jim Knuth wrote:
really? Thank you. :) For now I have deactivated the entry
in v340.pre.
if you have found workaround aswell post it to the ticket :)
i might be wroung
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=70
am 12.02.14 02:50 schrieb Benny Pedersen :
On 2014-02-12 02:48, Jim Knuth wrote:
really? Thank you. :) For now I have deactivated the entry
in v340.pre.
if you have found workaround aswell post it to the ticket :)
i might be wroung
yes, I'll do that.
--
Mit freundlichen Grüßen,
with kind
On 2014-02-12 02:48, Jim Knuth wrote:
really? Thank you. :) For now I have deactivated the entry
in v340.pre.
if you have found workaround aswell post it to the ticket :)
i might be wroung
am 12.02.14 02:39 schrieb Benny Pedersen :
On 2014-02-12 02:33, Jim Knuth wrote:
Util.pm ans AskDNS.pm both are available. What must
I do? Any ideas or solution greatly appreciated. Thanks.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7007
as i read it you have found a bug, with i
On 2014-02-12 02:33, Jim Knuth wrote:
Util.pm ans AskDNS.pm both are available. What must
I do? Any ideas or solution greatly appreciated. Thanks.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7007
as i read it you have found a bug, with i created a ticket for now
am 11.02.14 20:21 schrieb Kevin A. McGrail :
On behalf of the project, I am please to announce the availability of
Apache SpamAssassin version 3.4.0.
The Press Release is available on the ASF Blog at http://s.apache.org/G6b
& Release Notes follow. Downloads are available at
On behalf of the project, I am please to announce the availability of
Apache SpamAssassin version 3.4.0.
The Press Release is available on the ASF Blog at http://s.apache.org/G6b
& Release Notes follow. Downloads are available at
http://spamassassin.apache.org/downloads.cgi with some mi
Zitat von Mark Martinec :
Curl uses environment variable http_proxy (lowercase),
same as wget and LWP (libwww-perl) and similar tools.
Don't know where you got the uppercase variant.
Good point. The uppercase version simply did it's job.
I just tried the lowercase version and sa-update work a
2014-01-13 08:49, Andreas Schulze wrote:
thanks for that great software. The only problem I found is an issue
with sa-update:
My network require to use a http proxy incl. authentication. To load
updates
I currently (sa-3.3.2) set HTTP_PROXY="..." for sa-update.
That does not work anymore in 3.
Hello,
thanks for that great software. The only problem I found is an issue
with sa-update:
My network require to use a http proxy incl. authentication. To load updates
I currently (sa-3.3.2) set HTTP_PROXY="..." for sa-update.
That does not work anymore in 3.4
As I use curl I now have to c
Wolfgang writes:
what would be the minimum version of perl required to upgrade?
For features that already existed in 3.3 I believe the requirement
for version of perl has not changed, should work with 5.8.2 or later,
possibly even with 5.8.0 (perhaps with some Unicode-related problems).
If you
Hello Kevin,
what would be the minimum version of perl required to upgrade?
Regards
Wolfgang
On behalf of the PMC, the ASF SpamAssassin Project is pleased to
announce the availability of our fifth release candidate for 3.4.0. The
changes from rc4 are fairly minor and other than improved documentation,
only involve changes to the location of the TinyRedis.pm.
Files for this release
On behalf of the PMC, the ASF SpamAssassin Project is pleased to
announce the availability of our fourth release candidate for 3.4.0.
Files for this release candidate are available at
http://people.apache.org/~kmcgrail/devel/
The Proposed Announcement follows.
Regards,
KAM
To: users, dev
Thanks for the explanation. So I just forget about this new module, I
don't need it. Just thought it might hold other advantages as the make
output seems to suggest it does.
Kai
--
Get your web at Conactive Internet Services: http://www.conactive.com
Kevin A. McGrail wrote on Sun, 13 Oct 2013 14:14:02 -0400:
> I don't use MailScanner and have no input on this issue, sorry.
I've installed my 3.4.0 rpm on two systems with MailScanner now, one of
them in production. I've also tested compiling rules. It seems to be
working
That's much better, thanks! I wasn't sure about this also "Because LWP
does not support IPv6". It *could* mean that LWP generally does support
IPv6, but mine doesn't. As I understand it now it means that LWP in
general doesn't support it.
Kai
--
Get your web at Conactive Internet Services: ht
On 10/14/2013 12:44 PM, Mark Martinec wrote:
Andreas Schulze wrote:
thanks for that great software first!
I found two minor issues in perl documentation and attach a patch.
There is an other documentation issue in Conf.pm (found by debian lintian):
W: spamassassin: manpage-has-errors-from-man
us
Andreas Schulze wrote:
> thanks for that great software first!
> I found two minor issues in perl documentation and attach a patch.
> There is an other documentation issue in Conf.pm (found by debian lintian):
> W: spamassassin: manpage-has-errors-from-man
> usr/share/man/man3/Mail::SpamAssassin::C
On 10/14/2013 1:30 AM, Nicholas Chua wrote:
>
> I had rolled the tar into a rpm and installed into my CentOS 6.4 x64
> qmail + simscan + spamassassin + clamav devel machine
...
> Spamassassin works alright i guess but i think i will need to fix the
> getpwnam, dcc and pyzor
Sounds like you have con
1 - 100 of 145 matches
Mail list logo
