(no subject)
Jeffrey Nikoletich
jeffrey at nikoletich.com
Thu Apr 8 22:25:33 IST 2010
Kai,
What proof do you need? I can see the clean messages in the quarantine folder. Config is a basic config with nothing special with only deliver for clean messages.
--
Jeffrey Nikoletich
-----Original Message-----
From: mailscanner-request at lists.mailscanner.info
Date: Thu, 8 Apr 2010 12:02:04
To: <mailscanner at lists.mailscanner.info>
Subject: MailScanner Digest, Vol 52, Issue 8
Send MailScanner mailing list submissions to
mailscanner at lists.mailscanner.info
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.mailscanner.info/mailman/listinfo/mailscanner
or, via email, send a message with subject or body 'help' to
mailscanner-request at lists.mailscanner.info
You can reach the person managing the list at
mailscanner-owner at lists.mailscanner.info
When replying, please edit your Subject line so it is more specific
than "Re: Contents of MailScanner digest..."
Today's Topics:
1. Re: CentOS perl issues (Lance Haig)
2. Re: CentOS perl issues (Lance Haig)
3. Re: bayes mysql performance (Lance Haig)
4. OT: Julian (John Wilcock)
5. Re: CentOS perl issues (Kai Schaetzl)
6. Re: OT: Julian (--[ UxBoD ]--)
7. RE: OT: Julian (Hostmaster)
8. Re: CentOS perl issues (Marc Lucke)
9. Re: CentOS perl issues (Phil Hale)
10. Re: CentOS perl issues (Kai Schaetzl)
11. Re: CentOS perl issues (Michael Mansour)
12. Issues with store and store-spam (jeffrey at nikoletich.com)
13. Re: Issues with store and store-spam (Kai Schaetzl)
14. Re: CentOS perl issues (Marc Lucke)
15. Re: CentOS perl issues (Alex Neuman van der Hans)
----------------------------------------------------------------------
Message: 1
Date: Wed, 07 Apr 2010 15:20:45 +0100
From: Lance Haig <lhaig at haigmail.com>
Subject: Re: CentOS perl issues
To: MailScanner discussion <mailscanner at lists.mailscanner.info>
Message-ID: <4BBC94BD.7000204 at haigmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Thanks Michael,
I will have a look
Lance
On 07/04/2010 04:17, Michael Mansour wrote:
> Hi,
>
> In your /etc/yum.repos.d/rpmforge.repo file change:
>
> enabled=1
>
> to:
>
> enabled=0
>
> so that RPMforge isn't automatically enabled. Be selective with your perl modules.
>
> Regards,
>
> Michael.
>
> --- On Tue, 6/4/10, Lance Haig<lhaig at haigmail.com> wrote:
>
>
>> From: Lance Haig<lhaig at haigmail.com>
>> Subject: CentOS perl issues
>> To: "MailScanner discussion"<mailscanner at lists.mailscanner.info>
>> Received: Tuesday, 6 April, 2010, 6:57 PM
>> Hi,
>>
>> I am running CentOS 5 with MailScanner 4.78.17
>>
>> I am trying to run yum update and I get the error below.
>> Does anyone have suggestions as to how I can get past this?
>>
>> Thanks
>>
>> Lance
>>
>> Transaction Check Error:
>> file /usr/share/man/man3/Math::BigRat.3pm.gz from
>> install of perl-Math-BigRat-0.24-1.el5.rf.noarch conflicts
>> with file from package perl-5.8.8-27.el5.i386
>> file /usr/share/man/man3/File::Temp.3pm.gz from
>> install of perl-File-Temp-0.22-1.el5.rf.noarch conflicts
>> with file from package perl-5.8.8-27.el5.i386
>> file /usr/bin/prove from install of
>> perl-Test-Harness-3.21-1.el5.rf.noarch conflicts with file
>> from package perl-5.8.8-27.el5.i386
>> file /usr/share/man/man1/prove.1.gz from install of
>> perl-Test-Harness-3.21-1.el5.rf.noarch conflicts with file
>> from package perl-5.8.8-27.el5.i386
>> file /usr/share/man/man3/Test::Harness.3pm.gz from
>> install of perl-Test-Harness-3.21-1.el5.rf.noarch conflicts
>> with file from package perl-5.8.8-27.el5.i386
>> file /usr/share/man/man3/Sys::Syslog.3pm.gz from
>> install of perl-Sys-Syslog-0.27-1.el5.rf.i386 conflicts with
>> file from package perl-5.8.8-27.el5.i386
>> file /usr/share/man/man3/Test::Builder.3pm.gz from
>> install of perl-Test-Simple-0.94-1.el5.rf.noarch conflicts
>> with file from package perl-5.8.8-27.el5.i386
>> file
>> /usr/share/man/man3/Test::Builder::Module.3pm.gz from
>> install of perl-Test-Simple-0.94-1.el5.rf.noarch conflicts
>> with file from package perl-5.8.8-27.el5.i386
>> file
>> /usr/share/man/man3/Test::Builder::Tester.3pm.gz from
>> install of perl-Test-Simple-0.94-1.el5.rf.noarch conflicts
>> with file from package perl-5.8.8-27.el5.i386
>> file
>> /usr/share/man/man3/Test::Builder::Tester::Color.3pm.gz from
>> install of perl-Test-Simple-0.94-1.el5.rf.noarch conflicts
>> with file from package perl-5.8.8-27.el5.i386
>> file /usr/share/man/man3/Test::More.3pm.gz from
>> install of perl-Test-Simple-0.94-1.el5.rf.noarch conflicts
>> with file from package perl-5.8.8-27.el5.i386
>> file /usr/share/man/man3/Test::Simple.3pm.gz from
>> install of perl-Test-Simple-0.94-1.el5.rf.noarch conflicts
>> with file from package perl-5.8.8-27.el5.i386
>> file /usr/share/man/man3/Test::Tutorial.3pm.gz from
>> install of perl-Test-Simple-0.94-1.el5.rf.noarch conflicts
>> with file from package perl-5.8.8-27.el5.i386
>> file /usr/share/man/man3/bigint.3pm.gz from install
>> of perl-bignum-0.23-1.el5.rf.noarch conflicts with file from
>> package perl-5.8.8-27.el5.i386
>> file /usr/share/man/man3/bignum.3pm.gz from install
>> of perl-bignum-0.23-1.el5.rf.noarch conflicts with file from
>> package perl-5.8.8-27.el5.i386
>> file /usr/share/man/man3/bigrat.3pm.gz from install
>> of perl-bignum-0.23-1.el5.rf.noarch conflicts with file from
>> package perl-5.8.8-27.el5.i386
>>
>>
>> --
>> This message was scanned by Better Hosted and is believed
>> to be clean.
>> http://www.betterhosted.com
>>
>> -- MailScanner mailing list
>> mailscanner at lists.mailscanner.info
>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>
>> Before posting, read http://wiki.mailscanner.info/posting
>>
>> Support MailScanner development - buy the book off the
>> website!
>>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!
>
> --
> This message was scanned by Better Hosted and is believed to be clean.
> Click here to report this message as spam.
> http://mx1.betterhosted.com/cgi-bin/learn-msg.cgi?id=972909F82E.A23B2
>
>
>
--
This message was scanned by Better Hosted and is believed to be clean.
http://www.betterhosted.com
------------------------------
Message: 2
Date: Wed, 07 Apr 2010 15:28:50 +0100
From: Lance Haig <lhaig at haigmail.com>
Subject: Re: CentOS perl issues
To: mailscanner at lists.mailscanner.info
Message-ID: <4BBC96A2.6030309 at haigmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
This is one of the key reason I love this list.
Thanks for all the informed help and suggestions
Lance
On 07/04/2010 06:07, Iulian L Dragomir wrote:
> For one time occurrence use
>
> yum --exclude=package* update
>
> In your case if you want to exclude only those 6 packages :
>
> yum --exclude=perl-bignum --exclude=perl-File-Temp
> --exclude=perl-Math-BigRat --exclude=perl-Sys-Syslog
> --exclude=perl-Test-Harness --exclude=perl-Test-Simple update
>
> This 6 packages are for now the only packages that have older versions
> in mailscanner installation comparing to the rpmforge repo. In the
> future this list will not remain constant.
>
> If you want to exclude all perl packages use for one time update
>
> yum --exclude=perl* update
>
> If you need a more permanent solution use Craig's solution or look in
> to yum-protect-packages plug-in or use a more drastic solution
> (Michael's solution will disable rpmforge all together ) Other
> solutions are documented in the archive.
>
> Fore MailScanner updates use "./install.sh reinstall". More info on
> this subject here
>
> http://lists.mailscanner.info/pipermail/mailscanner/2009-April/090861.html
>
>
> Iulian L.D.
>
--
This message was scanned by Better Hosted and is believed to be clean.
http://www.betterhosted.com
------------------------------
Message: 3
Date: Wed, 07 Apr 2010 15:29:46 +0100
From: Lance Haig <lhaig at haigmail.com>
Subject: Re: bayes mysql performance
To: mailscanner at lists.mailscanner.info
Message-ID: <4BBC96DA.7090601 at haigmail.com>
Content-Type: text/plain; charset="iso-8859-1"
And Just when I am about to cluster my DB backend
Thanks for the great tip.
Lance
On 07/04/2010 09:38, Jason Ede wrote:
>
> For information I finally tracked down the performance problems I was
> having with using bayes in mysql.
>
> It seems that the inserts were taking an age to run and with multiple
> parallel inserts (i.e. multiple MS children) then the locks were
> slowing it down further. Changing the table types of all of the bayes
> tables from MyISAM to InnoDB using
>
> ALTER TABLE bayes_seen ENGINE = innodb;
>
> and repeating for each table seem to make a massive performance
> difference.
>
> Jason
>
>
> --
> This message was scanned by Better Hosted and is believed to be clean.
> Click here to report this message as spam
> <http://mx1.betterhosted.com/cgi-bin/learn-msg.cgi?id=BB58E9F1A2.A12B6>
--
This message was scanned by Better Hosted and is believed to be clean.
http://www.betterhosted.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20100407/a69e8e38/attachment-0001.html
------------------------------
Message: 4
Date: Wed, 07 Apr 2010 16:39:25 +0200
From: John Wilcock <john at tradoc.fr>
Subject: OT: Julian
To: MailScanner discussion <mailscanner at lists.mailscanner.info>
Message-ID: <4BBC991D.2000300 at tradoc.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I see that Julian hasn't posted to this list since his 10th anniversary
message almost a month ago, nor has he replied to a couple of recent
offlist messages of mine.
Has anyone here heard from him recently? I do hope his health problems
haven't reared their ugly head again...
John.
--
-- Over 4000 webcams from ski resorts around the world - www.snoweye.com
-- Translate your technical documents and web pages - www.tradoc.fr
------------------------------
Message: 5
Date: Wed, 07 Apr 2010 16:44:35 +0200
From: Kai Schaetzl <maillists at conactive.com>
Subject: Re: CentOS perl issues
To: mailscanner at lists.mailscanner.info
Message-ID: <VA.00003ace.004263f8 at news.conactive.com>
Content-Type: text/plain; charset=iso-8859-1
Mark McIntosh Infowall wrote on Tue, 06 Apr 2010 23:31:18 -0400:
> There is a bug
> upstream that causes perl to act badly it is documented if you search on
> google.
If you overwrite Perl modules that other modules or Perl itself depend on
it is to be expected that you run into problems. This is not a bug. Use
modules that have been built for this Perl and all is well.
I later redid my perl via non rpm centos repositories and all
> went fine. I agree disable rpmforge and use a different repository
Nonsense. The mistake you and Lance and others make is that you install the
Perl packages that come with MailScanner. I've told it several times in the
past on this list that doing it that way asks for trouble (on any OS with a
package system for updates). You do not need a single Perl module from the
MS package. All these modules are available from rpmforge and these work
fine with MS. So, you simply install them and then you install only the
mailscanner*.rpm from within the MS tarball. That's all and also much
faster.
> I later redid my perl via non rpm centos repositories and all
> went fine.
I wish you good luck the next time you get a perl update. Doing it that way
also eliminates one of the advantages of CentOS. Maybe you should use a
different OS.
Kai
--
Get your web at Conactive Internet Services: http://www.conactive.com
------------------------------
Message: 6
Date: Wed, 7 Apr 2010 16:05:57 +0100 (BST)
From: "--[ UxBoD ]--" <uxbod at splatnix.net>
Subject: Re: OT: Julian
To: MailScanner discussion <mailscanner at lists.mailscanner.info>
Message-ID:
<33304282.128.1270652757989.JavaMail.root at office.splatnix.net>
Content-Type: text/plain; charset=utf-8
----- Original Message -----
> I see that Julian hasn't posted to this list since his 10th
> anniversary message almost a month ago, nor has he replied to a couple
> of recent
> offlist messages of mine.
>
> Has anyone here heard from him recently? I do hope his health problems
> haven't reared their ugly head again...
>
> John.
>
> --
> -- Over 4000 webcams from ski resorts around the world -
> www.snoweye.com
> -- Translate your technical documents and web pages - www.tradoc.fr
> -- MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!
25th March was his last blog update on his website; and by the sounds of it I reckon he is snowed under at work at present. (Though like you I do hope it is nothing else!)
--
Thanks, Phil
------------------------------
Message: 7
Date: Wed, 7 Apr 2010 16:17:51 +0100
From: "Hostmaster" <Hostmaster at computerservicecentre.com>
Subject: RE: OT: Julian
To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
Message-ID:
<3D9C92F3075F5144B46AA2C590F48E2AE69278 at commssrv01.computerservicecentre.com>
Content-Type: text/plain; charset="utf-8"
-----Original Message-----
25th March was his last blog update on his website; and by the sounds of it I
reckon he is snowed under at work at present. (Though like you I do hope it is
nothing else!)
--
Please bear in mind that most UK universities are currently on their Easter
break, so with a bit of luck he is spending some quality time with family and
friends.
--
Richard
All E-Mail communications are monitored in addition to being content checked for malicious codes or viruses. The success of scanning products is not guaranteed, therefore the recipient(s) should carry out any checks that they believe to be appropriate in this respect.
This message (including any attachments and/or related materials) is confidential to and is the property of Computer Service Centre, unless otherwise noted. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
Any views or opinions presented are solely those of the author and do not necessarily represent those of Computer Service Centre.
------------------------------
Message: 8
Date: Thu, 08 Apr 2010 04:08:40 +1000
From: Marc Lucke <marc at marcsnet.com>
Subject: Re: CentOS perl issues
To: MailScanner discussion <mailscanner at lists.mailscanner.info>
Message-ID: <4BBCCA28.6060008 at marcsnet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I like to use rpmforge because of updated (from CentOS5 repos)
spamassassin and clamav and am quite happy to update manually. With the
repo turned off this works:
yum --enablerepo=rpmforge -y install clamav spamassassin
Of course you need to update the perl module with something like
cpan Mail::SpamAssassin && sa-update
There's probably a way to tell yum to update only these packages from
rpmforge automatically but I have bothered with that. It does annoy me
that the rpmforge and centos repos clash on perl but meh - what can you
do and would you bother?
Marc
Lance Haig wrote:
> This is one of the key reason I love this list.
>
> Thanks for all the informed help and suggestions
>
> Lance
>
> On 07/04/2010 06:07, Iulian L Dragomir wrote:
>> For one time occurrence use
>>
>> yum --exclude=package* update
>>
>> In your case if you want to exclude only those 6 packages :
>>
>> yum --exclude=perl-bignum --exclude=perl-File-Temp
>> --exclude=perl-Math-BigRat --exclude=perl-Sys-Syslog
>> --exclude=perl-Test-Harness --exclude=perl-Test-Simple update
>>
>> This 6 packages are for now the only packages that have older versions
>> in mailscanner installation comparing to the rpmforge repo. In the
>> future this list will not remain constant.
>>
>> If you want to exclude all perl packages use for one time update
>>
>> yum --exclude=perl* update
>>
>> If you need a more permanent solution use Craig's solution or look in
>> to yum-protect-packages plug-in or use a more drastic solution
>> (Michael's solution will disable rpmforge all together ) Other
>> solutions are documented in the archive.
>>
>> Fore MailScanner updates use "./install.sh reinstall". More info on
>> this subject here
>>
>> http://lists.mailscanner.info/pipermail/mailscanner/2009-April/090861.html
>>
>>
>>
>> Iulian L.D.
>>
>
>
> --
> This message was scanned by Better Hosted and is believed to be clean.
> http://www.betterhosted.com
>
------------------------------
Message: 9
Date: Wed, 07 Apr 2010 14:00:45 -0500
From: Phil Hale <phaleintx at gmail.com>
Subject: Re: CentOS perl issues
To: MailScanner discussion <mailscanner at lists.mailscanner.info>
Message-ID: <1270666845.15782.30.camel at zues>
Content-Type: text/plain; charset="UTF-8"
Hello List,
I'd recommend looking at using the yum Priorities and ProtectBase
plugins as described here:
http://wiki.centos.org/PackageManagement/Yum/Priorities
http://wiki.centos.org/PackageManagement/Yum/ProtectBase
CentOS discusses their use with 3rd party repositories on the following
page under the heading "3rd Party Repositories"
http://wiki.centos.org/AdditionalResources/Repositories
Basically you set your CentOS repositories to be higher priority than
rpmforge or epel and then packages from those repositories will not
replace packages found in the base CentOS repositories.
Phil Hale
On Thu, 2010-04-08 at 04:08 +1000, Marc Lucke wrote:
> I like to use rpmforge because of updated (from CentOS5 repos)
> spamassassin and clamav and am quite happy to update manually. With the
> repo turned off this works:
>
> yum --enablerepo=rpmforge -y install clamav spamassassin
>
> Of course you need to update the perl module with something like
>
> cpan Mail::SpamAssassin && sa-update
>
> There's probably a way to tell yum to update only these packages from
> rpmforge automatically but I have bothered with that. It does annoy me
> that the rpmforge and centos repos clash on perl but meh - what can you
> do and would you bother?
>
>
> Marc
>
> Lance Haig wrote:
> > This is one of the key reason I love this list.
> >
> > Thanks for all the informed help and suggestions
> >
> > Lance
> >
> > On 07/04/2010 06:07, Iulian L Dragomir wrote:
> >> For one time occurrence use
> >>
> >> yum --exclude=package* update
> >>
> >> In your case if you want to exclude only those 6 packages :
> >>
> >> yum --exclude=perl-bignum --exclude=perl-File-Temp
> >> --exclude=perl-Math-BigRat --exclude=perl-Sys-Syslog
> >> --exclude=perl-Test-Harness --exclude=perl-Test-Simple update
> >>
> >> This 6 packages are for now the only packages that have older versions
> >> in mailscanner installation comparing to the rpmforge repo. In the
> >> future this list will not remain constant.
> >>
> >> If you want to exclude all perl packages use for one time update
> >>
> >> yum --exclude=perl* update
> >>
> >> If you need a more permanent solution use Craig's solution or look in
> >> to yum-protect-packages plug-in or use a more drastic solution
> >> (Michael's solution will disable rpmforge all together ) Other
> >> solutions are documented in the archive.
> >>
> >> Fore MailScanner updates use "./install.sh reinstall". More info on
> >> this subject here
> >>
> >> http://lists.mailscanner.info/pipermail/mailscanner/2009-April/090861.html
> >>
> >>
> >>
> >> Iulian L.D.
> >>
> >
> >
> > --
> > This message was scanned by Better Hosted and is believed to be clean.
> > http://www.betterhosted.com
> >
------------------------------
Message: 10
Date: Wed, 07 Apr 2010 21:31:34 +0200
From: Kai Schaetzl <maillists at conactive.com>
Subject: Re: CentOS perl issues
To: mailscanner at lists.mailscanner.info
Message-ID: <VA.00003ad1.01491d6b at news.conactive.com>
Content-Type: text/plain; charset=iso-8859-1
Marc Lucke wrote on Thu, 08 Apr 2010 04:08:40 +1000:
> Of course you need to update the perl module with something like
>
> cpan Mail::SpamAssassin
no, you don't.
> There's probably a way to tell yum to update only these packages from
> rpmforge
There are rumours that "yum update" is for this ...
> It does annoy me
> that the rpmforge and centos repos clash on perl but meh
There is no clash. I suggest you try to understand how rpm, how yum and
how RHEL/CentOS works.
Kai
--
Get your web at Conactive Internet Services: http://www.conactive.com
------------------------------
Message: 11
Date: Wed, 7 Apr 2010 22:31:47 -0700 (PDT)
From: Michael Mansour <micoots at yahoo.com>
Subject: Re: CentOS perl issues
To: MailScanner discussion <mailscanner at lists.mailscanner.info>
Message-ID: <828365.44461.qm at web33307.mail.mud.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1
Hi,
--- On Wed, 7/4/10, Iulian L Dragomir <iulianld at gmail.com> wrote:
> From: Iulian L Dragomir <iulianld at gmail.com>
> Subject: Re: CentOS perl issues
> To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
> Received: Wednesday, 7 April, 2010, 3:07 PM
> For one time occurrence use
>
> yum --exclude=package* update
>
> In your case if you want to exclude only those 6 packages
> :
>
> yum --exclude=perl-bignum --exclude=perl-File-Temp
> --exclude=perl-Math-BigRat --exclude=perl-Sys-Syslog
> --exclude=perl-Test-Harness --exclude=perl-Test-Simple
> update
>
> This 6 packages are for now the only packages that have
> older versions
> in mailscanner installation comparing to the rpmforge repo.
> In the
> future this list will not remain constant.
>
> If you want to exclude all perl packages use for one
> time update
>
> yum --exclude=perl* update
>
> If you need a more permanent solution use Craig's solution
> or look in
> to yum-protect-packages plug-in or use a more drastic
> solution
> (Michael's solution will disable rpmforge all together )
I typically disable all 3rd party repo's and pick and choose what I want from them. So if there's certain RPMforge packages I want I simply do:
# yum --enablerepo=rpmforge -y update blah.rpm
This also allows me to list updated packages per repo by enabling what I want and checking against a pre-defined installation list.
Been using this technique for years (before yum plugins were available) and it's worked well, so haven't bothered changing the way I do things.
Regards,
Michael.
> Other
> solutions are documented in the archive.
>
> Fore MailScanner updates use "./install.sh
> reinstall". More info on
> this subject here
>
> http://lists.mailscanner.info/pipermail/mailscanner/2009-April/090861.html
>
>
> Iulian L.D.
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the
> website!
>
------------------------------
Message: 12
Date: Thu, 8 Apr 2010 04:16:41 -0400
From: "jeffrey at nikoletich.com" <jeffrey at nikoletich.com>
Subject: Issues with store and store-spam
To: mailscanner at lists.mailscanner.info
Message-ID: <380-2201044881641807 at M2W111.mail2web.com>
Content-Type: text/plain; charset=iso-8859-1
Hello All,
I am having an issue with mailscanner an its quarantine. I currently have
mailscanner to store spam and high spam messages in the quarantine and to
deliver clean non spam messages to the user.
The issues I am having is that mailscanner seems to be storing clean non
spam messages as well. I have check my configuration and the conf is
correct.
It doesnt store every clean message, it seems to be random, so I am kinda
lost with is now.
Any help is appreciated.
Thanks and advance,
Jeff N.
--------------------------------------------------------------------
mail2web.com – Enhanced email for the mobile individual based on Microsoft®
Exchange - http://link.mail2web.com/Personal/EnhancedEmail
------------------------------
Message: 13
Date: Thu, 08 Apr 2010 11:31:17 +0200
From: Kai Schaetzl <maillists at conactive.com>
Subject: Re: Issues with store and store-spam
To: mailscanner at lists.mailscanner.info
Message-ID: <VA.00003ad3.008a25a9 at news.conactive.com>
Content-Type: text/plain; charset=iso-8859-1
Jeffrey at nikoletich.com wrote on Thu, 8 Apr 2010 04:16:41 -0400:
> The issues I am having is that mailscanner seems to be storing clean non
> spam messages as well. I have check my configuration and the conf is
> correct.
And the proof is where?
> It doesnt store every clean message, it seems to be random, so I am kinda
> lost with is now.
Again, where is the proof?
I mean, how do you know that and how do you know that the configuration is
correct? Obviously it *cannot* be correct.
Kai
--
Get your web at Conactive Internet Services: http://www.conactive.com
------------------------------
Message: 14
Date: Thu, 08 Apr 2010 20:09:56 +1000
From: Marc Lucke <marc at marcsnet.com>
Subject: Re: CentOS perl issues
To: MailScanner discussion <mailscanner at lists.mailscanner.info>
Message-ID: <4BBDAB74.4030106 at marcsnet.com>
Content-Type: text/plain; charset="iso-8859-1"
Thank you Kai for your abrasive and unhelpful response. Very productive.
Kai Schaetzl wrote:
> Marc Lucke wrote on Thu, 08 Apr 2010 04:08:40 +1000:
>
>
>> Of course you need to update the perl module with something like
>>
>> cpan Mail::SpamAssassin
>>
>
> no, you don't.
>
>
>> There's probably a way to tell yum to update only these packages from
>> rpmforge
>>
>
> There are rumours that "yum update" is for this ...
>
>
>> It does annoy me
>> that the rpmforge and centos repos clash on perl but meh
>>
>
> There is no clash. I suggest you try to understand how rpm, how yum and
> how RHEL/CentOS works.
>
>
> Kai
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20100408/909819e1/attachment-0001.html
------------------------------
Message: 15
Date: Thu, 8 Apr 2010 10:48:43 +0000
From: "Alex Neuman van der Hans" <alex at rtpty.com>
Subject: Re: CentOS perl issues
To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
Message-ID:
<1784902539-1270723748-cardhu_decombobulator_blackberry.rim.net-1657107426- at bda942.bisx.prod.on.blackberry>
Content-Type: text/plain
I don't mean to be rude but no evidence has been provided to support your statements.
One thing that might be happening might be that "clean" messages being stored might be whitelisted messages that really aren't "clean".
But, again, no evidence of a "correct" configuration is provided, so assuming a "correct" configuration is not very helpful or productive on anyone's part either.
I'm not defending or condoning Kai's tone, but simply trying to point out that saying "I believe my configuration is correct so the program is doing something wrong" might also be construed as abrasive, specially from the point of view of someone who might have contributed to the program.
Imagine a teacher saying "I know I told your child how to do this correctly, but he randomly does crazy things". Without proper evidence of the instructions and purported behaviour, the human mind can easily construe it as an ad-hominem attack on the child (which it isn't) instead of a legitimate (albeit incompletely documented) observation.
Please try using pastebin to provide samples of your configuration and samples of both "correctly stored", "correctly not stored", "incorrectly stored" and, if possible, "incorrectly not stored" messages so that by careful examination we might be able to shed some light on the situation. Reading http://bit.ly/howtogethelpwiththat will also save you - and the rest of the list members some time and energy.
--
Alex Neuman van der Hans
Reliant Technologies
+507 6781-9505
+507 832-6725
BB PIN: 20EA17C5
-----Original Message-----
From: Marc Lucke <marc at marcsnet.com>
Date: Thu, 08 Apr 2010 20:09:56
To: MailScanner discussion<mailscanner at lists.mailscanner.info>
Subject: Re: CentOS perl issues
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
------------------------------
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read the Wiki (http://wiki.mailscanner.info/).
Support MailScanner development - buy the book off the website!
End of MailScanner Digest, Vol 52, Issue 8
******************************************
More information about the MailScanner
mailing list