Fernando Vilas wrote:
> On Friday 28 September 2007 14:09:58 Ronnie Gilkey wrote:
>
>> I'm not very good with procmail, but I know that procmail will allow you
>> to pass the input through a pipe, so you could set a filter that matches
>> all mails to pipe to perl.
>>
>>
> Yeah, that part is easy. It's getting the rules afterwards to work that's the
> trick. I may just add it as a nested rule to each of the main rules, but
> that becomes a maintenance nightmare. I'll play around with it.
>
>
>> With that the perl "one-liner" is handy (-n
>> for treating the code as being inside while (<>)):
>>
>> perl -ne "if ($_ =~ m/(=[0-9a-fA-F]{2})/) { $text = $1; $replace =
>> chr($text); $_ =~ s/$text/$replace/g; }
>>
>> It's not perfect, but I think you understand where I'm going with this.
>>
>>
> Thanks for the help. It's a great starting point, but right now, it's overly
> aggressive in its matching. When I get things settled in it, I'll post the
> final version. I haven't used Perl since the 2000/2001 school year, so I'm
> more than a little rusty.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> General mailing list
> General at brlug.net
> http://mail.brlug.net/mailman/listinfo/general_brlug.net
>
Heh. It's more than aggressive, there's also several typos :). But I'm
glad to help out.
Ronnie Gilkey
--
Puryear Information Technology, LLC
Baton Rouge, LA * 225-706-8414
http://www.puryear-it.com
Visit http://www.puryear-it.com/publications.htm to download your free
copies of:
"Best Practices for Managing Linux and UNIX Servers"
"Spam Fighting and Email Security in the 21st Century"
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mail.brlug.net/pipermail/general_brlug.net/attachments/20070929/778823fd/attachment.html
