Re: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-25 Thread Mark Martinec
Michael, > Problem with perl 5.8.7 in error processing. (or problem is in amavis, > fixed with 2.3.2) > > If problem fixed with a patch to amavisd-new, was it original problem > with amavis? Then why did it just NOW show up? It is a problem in Perl 5.8.7, which for some reason only surfaces on Fr

RE: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-12 Thread akpostfix
Clifton Royston: > > > > You're right, that may be the issue. But since mail server > shouldn't > > have much junk installed, it can be easy to just rebuild > ALL installed > > ports. > > My approach, FWIW, has been to use ports to build a > complete set of BSD binary packages on one system, us

Re: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-12 Thread Clifton Royston
On Tue, Jul 12, 2005 at 09:04:50AM +0200, [EMAIL PROTECTED] wrote: > Clifton Royston: > > > > No, but this time it's not perl port's fault. You have to > > upgrade all > > > dependent packages and it will work like a charm. > > > > Note that this method will not work correctly if some perl >

RE: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-12 Thread akpostfix
Clifton Royston: > > No, but this time it's not perl port's fault. You have to > upgrade all > > dependent packages and it will work like a charm. > > Note that this method will not work correctly if some perl > package has an error in its dependencies, because in that > case that package w

Re: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-11 Thread Clifton Royston
On Mon, Jul 11, 2005 at 04:41:44PM +0200, [EMAIL PROTECTED] wrote: > Michael Scheidell: > > No fud, and as I said, it doesn't work and I have the fix. > > > > Why would you deny people the right to speak the truth? > > Relax man. Go take a walk. I'm not denying you anything. You're just not > c

RE: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-11 Thread akpostfix
Michael Scheidell: > No fud, and as I said, it doesn't work and I have the fix. > > Why would you deny people the right to speak the truth? Relax man. Go take a walk. I'm not denying you anything. You're just not correct about the perl issue. > Are you trying to say that everything on FBSD por

Re: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-11 Thread Chris
[EMAIL PROTECTED] wrote: Michael Scheidell: The issue with deferred mail was that amavisd-new didn't really restart. You would see the missing modules if you start with debug. The rsync seemed to fix it. (again, don't ask don't tell) if you don't know what and why of the rsync, don't even t

RE: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-11 Thread Michael Scheidell
No fud, and as I said, it doesn't work and I have the fix. Why would you deny people the right to speak the truth? Are you trying to say that everything on FBSD ports is perfect and anyone who says anything bad abut it is evil? This has been reported several times, by several different people,

Re: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-11 Thread Ricardo Campos Passanezi
On Mon, Jul 11, 2005 at 10:26:46AM +0200, [EMAIL PROTECTED] wrote: > Michael Scheidell: > > > > The issue with deferred mail was that amavisd-new didn't > > really restart. > > > > You would see the missing modules if you start with debug. > > > > The rsync seemed to fix it. (again, don't ask d

RE: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-11 Thread akpostfix
Michael Scheidell: > > The issue with deferred mail was that amavisd-new didn't > really restart. > > You would see the missing modules if you start with debug. > > The rsync seemed to fix it. (again, don't ask don't tell) if > you don't know what and why of the rsync, don't even try it. > >

RE: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-10 Thread Michael Scheidell
The issue with deferred mail was that amavisd-new didn't really restart. You would see the missing modules if you start with debug. The rsync seemed to fix it. (again, don't ask don't tell) if you don't know what and why of the rsync, don't even try it. I actually had a similar problem when upgr

RE: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-10 Thread Michael Scheidell
Two problems: Problem with perl 5.8.7 in error processing. (or problem is in amavis, fixed with 2.3.2) If problem fixed with a patch to amavisd-new, was it original problem with amavis? Then why did it just NOW show up? Other problem seems to be upgrading from 5.8.6 to 5.8.7. Several reports of m

Re: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-10 Thread Chris
Thomas Vogt wrote: Hi What is the exact problem with amavis and perl 5.8.7? We have 4 FreeBSD Mailserver with amavis 2.3.2, perl 5.8.7 and Spamassassin 3.0.4. We don't have any problems with it. Every server is handling 700k avarage mails a day without any problem. Regards, Thomas As

Re: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-10 Thread Chris
Thomas Vogt wrote: Hi What is the exact problem with amavis and perl 5.8.7? We have 4 FreeBSD Mailserver with amavis 2.3.2, perl 5.8.7 and Spamassassin 3.0.4. We don't have any problems with it. Every server is handling 700k avarage mails a day without any problem. Regards, Thomas IIR

Re: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-10 Thread Thomas Vogt
Hi What is the exact problem with amavis and perl 5.8.7? We have 4 FreeBSD Mailserver with amavis 2.3.2, perl 5.8.7 and Spamassassin 3.0.4. We don't have any problems with it. Every server is handling 700k avarage mails a day without any problem. Regards, Thomas Am 10.07.2005 um 19:03

Re: [AMaViS-user] Followup on Perl 5.8.7 and Freebsd issues

2005-07-10 Thread Chris
Michael Scheidell wrote: I have not done any extensive diagnostic, nor have I bothered to send in an SPR to FreeBSD ports maintainers for the perl 5.8.7 yet, however, based on all the trauma experienced for everyone who tried perl 5.8.7/freebsd/amavisd-new combination, I would say 'just say no'.