Re: [Mimedefang] MIMEDefang 2.68 panic: top_env problems
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 same results. If anyone else has similar perl module versions, I'd be interested in hearing about their upgrade success, in the hopes of tracking down the cause. I will look as kd6...@yahoo.com suggested and attempt some upgrades, however given the other excellent advice from Tilman (re: CPAN vs RPM upgrades) I'll be doing it carefully so I don't kill the system prior to being able to retire it. Thanks also to WBrown for the O'Reilly reference - I'm sure that was what David also encountered (as did I when i asked Google), I was just hoping it was more of a known fault, or one that could be tracked a little easier! Again, thanks all. I'll try upgrading some of my modules and report back if any progress is made, or the solution is found. Cheers, Matt ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] check for "null SPF entries" only
-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 looked easier than Mail::SPF, when I checked CPAN for SPF modules, and works for my needs. You need a "SPF server" object, query the result, but the record is in the original request. It also looks heavier in regards of ressources. http://search.cpan.org/~jmehnle/Mail-SPF-v2.007/lib/Mail/SPF.pm This is the fully RFC 4408 compliant version. This is actually a point to consider, because I'm also interested in "Does somebody know of a SPF implementation that only checks for "null SPF entries", aka "v=spf1 -all"? But does support, probably, TXT/SPF RRs and v=spf2.0 as well?" Anyway, can I simplify Mail::SPF's checks to just take a look after null entries? Probably the "max_*" settings, let's see, ... . Regards, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBS4adL0gddVksjRnHAQKfnAf5AfbL8pXfQmUxY0qSZpwjEKO8vy2KKr5A FEwnc3cWIhbza980MsdNhwEJLVRy5ud/Wp602szEqgQR4oNHW+j4ORKszs8wdeT4 XVxxf3IGR95vyX5ECXbYjNUbQARVLYJw6Hp5ydAEjvGt/bYagzX9MsnkItmllqkD aggwrgscrmbRSMgEZ/F183X+NkMSTNFup5HohGZ8zEP5Pz/yexKPe2HarmAkZzwi 8b/xvMh5feQp1mP12MnV29v6iJS0q9k41CMnVMkCBBnuDc9vkM1z/TAs4VYWydoM 0fFLAi9UBxSt2DpLV2k1um+4aNE8VIarq29b+r1hmsFoA14IT5Vo8A== =+T6V -END PGP SIGNATURE- ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] MIMEDefang 2.68 panic: top_env problems
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'Reilly) has this to say: "If you're working with embedded code or a dynamic regex, and your program suddenly ends with an unceremonial panic: top_env it is likely due to a syntax error in the code part of the regex. Perl currently doesn't handle certain kinds of broken syntax well, and the panic is the result. The solution, of course, is to correct the syntax." Confidentiality Notice: This electronic message and any attachments may contain confidential or privileged information, and is intended only for the individual or entity identified above as the addressee. If you are not the addressee (or the employee or agent responsible to deliver it to the addressee), or if this message has been addressed to you in error, you are hereby notified that you may not copy, forward, disclose or use any part of this message or any attachments. Please notify the sender immediately by return e-mail or telephone and delete this message from your system. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] MIMEDefang 2.68 panic: top_env problems
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 filter or one of your Perl modules. Googling for "panic: top_env" yields little enlightenment other than "It's probably a Perl bug." :( Regards, David. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] MIMEDefang 2.68 panic: top_env problems
-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, given his uname output.) Otherwise you risk ending up with a completely broken Perl after the next RPM update. HTH Tilman -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuGe7sACgkQ780oymN0g8MY5wCgnmXvQNIMisGZbGmHYP7q9a7x z+UAni0FCSoLhhb5xeFW8D7Aj9ntGn6A =DFJ2 -END PGP SIGNATURE- ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] MIMEDefang 2.68 panic: top_env problems
--- 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", ... > > I ended up downgrading to 2.67, and with my original filter, it worked > without fault or change. > I have noticed that the MD pre-requisites spec Perl 5.8.9, and I'm > running 5.8.8, but I wouldn't have thought such a minor revision would > have had an effect? > > I know this is an old system, due to be retired, but it's working for > now ;) > > ... > Anomy::HTMLCleaner : missing > Archive::Zip : Version 1.16 > Digest::SHA1 : Version 2.11 > HTML::Parser : Version 3.54 > HTML::TokeParser : Version 2.37 > IO::Socket : Version 1.29 > IO::Stringy : Version 2.110 * Current > MIME::Base64 : Version 3.07 > MIME::Tools : Version 5.420 > MIME::Words : Version 5.420 > Mail::Mailer : Version 1.74 > Mail::SpamAssassin : Version 3.002004 > Net::DNS : Version 0.57 > Unix::Syslog : missing Even if you choose not to upgrade perl itself (to version 5.10.1), you should really run: perl -MCPAN -e upgrade Current versions of the CPAN utilities mentioned: Anomy::HTMLCleaner: Version 1.26 Archive::Zip : Version 1.30 Digest::SHA1 : Version 2.12 HTML::Parser : Version 3.64 HTML::TokeParser : Version 3.57 IO::Socket: Version 1.31 IO::Stringy : Version 2.110 MIME::Base64 : Version 3.09 MIME::Tools : Version 5.427 MIME::Words : Version 5.427 Mail::Mailer : Version 2.06 Mail::SpamAssassin: Version 3.003000 Net::DNS : Version 0.66 Unix::Syslog : Version 1.1 The fact that you aren't using the most current modules could also be part of your problem. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] MIMEDefang 2.68 panic: top_env problems
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 died prematurely -- check your filter rules After going through my filter (and replacing with a clean one), removing SpamAssasin etc I had no luck in finding the cause. I tried running embedded perl and not (given the changelog entry relating to this on FreeBSD - I tried anyway ;) I ended up downgrading to 2.67, and with my original filter, it worked without fault or change. I have noticed that the MD pre-requisites spec Perl 5.8.9, and I'm running 5.8.8, but I wouldn't have thought such a minor revision would have had an effect? I know this is an old system, due to be retired, but it's working for now ;) Can anyone shed light? Cheers, Matt System details follow (MD features, Perl version, uname) My mimedefang.pl -features MIMEDefang version 2.67 Archive::Zip : yes HTML::Parser : yes HTML::TokeParser : yes Net::DNS : yes Path:CONFDIR : yes (/etc/mail) Path:QUARANTINEDIR: yes (/var/spool/MD-Quarantine) Path:SENDMAIL : yes (/usr/sbin/sendmail) Path:SPOOLDIR : yes (/var/spool/MIMEDefang) SpamAssassin : yes Virus:CLAMAV : yes (/usr/local/bin/clamscan) Virus:CLAMD : yes (/usr/local/sbin/clamd) HTMLCleaner : no Unix::Syslog : no Virus:AVP : no Virus:AVP5: no Virus:BDC : no Virus:CSAV: no Virus:FPROT : no Virus:FPROTD : no Virus:FPROTD6 : no Virus:FPSCAN : no Virus:FSAV: no Virus:HBEDV : no Virus:KAVSCANNER : no Virus:NAI : no Virus:NOD32 : no Virus:NVCC: no Virus:SAVSCAN : no Virus:SOPHIE : no Virus:SOPHOS : no Virus:SymantecCSS : no Virus:TREND : no Virus:TROPHIE : no Virus:VEXIRA : no Anomy::HTMLCleaner: missing Archive::Zip : Version 1.16 Digest::SHA1 : Version 2.11 HTML::Parser : Version 3.54 HTML::TokeParser : Version 2.37 IO::Socket: Version 1.29 IO::Stringy : Version 2.110 MIME::Base64 : Version 3.07 MIME::Tools : Version 5.420 MIME::Words : Version 5.420 Mail::Mailer : Version 1.74 Mail::SpamAssassin: Version 3.002004 Net::DNS : Version 0.57 Unix::Syslog : missing And perl -vi This is perl, v5.8.8 built for x86_64-linux-thread-multi And uname -a Linux 2.6.16-1.2122_FC5 #1 SMP Sun May 21 15:01:10 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
