Re: [Mimedefang] MIMEDefang 2.68 panic: top_env problems

2010-02-25 Thread Matt Smith
Thanks for all that replied. David - I had forgotten to included that I had googled, I just didn't like the response I got (perl bug). I don't believe the bug is in my filter (or only in my filter), as replacing the filter with the stock "suggested minimum for windows.." included filter gave the sa

Re: [Mimedefang] check for "null SPF entries" only

2010-02-25 Thread Steffen Kaiser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 24 Feb 2010, - wrote: Why are you using Mail::SPF::Query? That package was depreciated 3 years ago in favor of the newer Mail:SPF, the latter which handles other cases such as IPv6 entries that ::Query didn't understand. Because it looke

Re: [Mimedefang] MIMEDefang 2.68 panic: top_env problems

2010-02-25 Thread WBrown
DFS wrote on 02/25/2010 09:06:56 AM: > Oh, dear. It's probably a Perl bug that's triggered by some peculiarity > of your filter or one of your Perl modules. > > Googling for "panic: top_env" yields little enlightenment other than > "It's probably a Perl bug." :( Mastering Regular Expressions (O

Re: [Mimedefang] MIMEDefang 2.68 panic: top_env problems

2010-02-25 Thread David F. Skoll
Matt Smith wrote: > However, after installing and firing it up, I kept receiving the error: > "all slaves are busy", and then; > Slave 5 stderr: panic: top_env > Slave 5 died prematurely -- check your filter rules Oh, dear. It's probably a Perl bug that's triggered by some peculiarity of your fi

Re: [Mimedefang] MIMEDefang 2.68 panic: top_env problems

2010-02-25 Thread Tilman Schmidt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 2010-02-25 10:55 schrieb -: > Even if you choose not to upgrade perl itself (to version 5.10.1), you should > really run: > >perl -MCPAN -e upgrade Don't do that if Perl was installed as an RPM package. (Which I suspect in the case of the OP,

Re: [Mimedefang] MIMEDefang 2.68 panic: top_env problems

2010-02-25 Thread -
--- On Thu, 2/25/10, Matt Smith wrote: > I upgraded to MD 2.68 (from 2.61, I missed a few!). > After checking the Changelog for incompatibilities, I thought it should > be a smooth upgrade. > > However, after installing and firing it up, I kept receiving the error: > "all slaves are busy", ... >

[Mimedefang] MIMEDefang 2.68 panic: top_env problems

2010-02-25 Thread Matt Smith
Hi List, I upgraded to MD 2.68 (from 2.61, I missed a few!). After checking the Changelog for incompatibilities, I thought it should be a smooth upgrade. However, after installing and firing it up, I kept receiving the error: "all slaves are busy", and then; Slave 5 stderr: panic: top_env Slave 5