Date: Wed, 1 Aug 2001 01:30:52 -0400 From: Klaus Steden <klaus@compt.com> To: parv <parv_@yahoo.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: weird interaction between procmail and perl on 4.x ? Message-ID: <20010801013052.R95706@cthulu.compt.com> In-Reply-To: <20010801005030.D27358@moo.holy.cow>; from parv_@yahoo.com on Wed, Aug 01, 2001 at 12:50:30AM -0400 References: <20010731223739.G95706@cthulu.compt.com> <20010731231059.A26373@moo.holy.cow> <20010731231021.I95706@cthulu.compt.com> <20010801005030.D27358@moo.holy.cow>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > It's a pretty lengthy script, so I'll include the URL for his homepage and > > hopefully avoid angry replies about hefty attachments. > > > > ftp://ftp.rubyriver.com/pub/jhardin/antispam/procmail-security.html > > > > wow! that's long alright! i didn't get thru' the whole script, but from > the looks of... > > ftp://ftp.rubyriver.com/pub/jhardin/antispam/html-trap.procmail > > if i were using the script, i would put long perl scripts in their own > files... > yeah, that's what i did, and to great success. although you'd never know that anyone else had encountered this. this bug has actually been around for a while ... searching through the archives for the sanitizer scripts found me this ... http://www.spconnect.com/pipermail/esa-l/2001q3/000603.html and i followed the guy's advice. i guess perl on freebsd doesn't like command lines that immense. the mime one is almost 500 lines (as a separate perl script, but with no extra line padding), and the other two long perl segments didn't do any better. cutting them into individual files was much more effective. :> peace, Klaus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010801013052.R95706>