On Sat, Dec 10, 2005 at 06:30:34PM -0800, Patrick R. Wade wrote:
> >Now, I can trivially identify the AOL client through its msgid, or through
> >its X-Mailer being a retarded string like "8.0 for Windows", but I have no
> >idea how to do the two-line match to determine that one of the parts is a
> >mislabelled Q-P part with windows-1252 charset. I've managed to determine
> >that AOL's software sends a proper charset for anything BUT windows-1252,
> >which makes this just really annoying.
> >
> >So the question is, how do I match on the condition of that two-line
> >breakage and, having done so, how do I fix the broken charset before
> >writing the message to the destination folder?
>
> I have a feeling this is going to involve an egrep pattern that
> incorporates a newline, and then use of formail to munge the
> Content-Type line, but i'm groping.
Yeah, I don't think formail is smart enough. I've seen people do stuff
with munpack and other people do stuff with perl scripts, but I think I am
running smack into the limitations of procmail/formail here. It is then
rather unfortunate that all of the things that lack procmail's limitations
also lack its "ease" (relatively) of configuration.
The last person to call procmail "puny" used some massive bit of perl
grossness which required writing a new function every time he wanted to
add a new mailing list. On the other hand, it would deal with the
crosspost issue that my little procmail recipe can't and make sure that
the message is delivered to all of the lists he's on, but won't cause a
new folder to be created automatically for ones he's not.
Middle ground should exist. ;)
--
"We are what we repeatedly do. Excellence, therefore, is not an act,
but a habit."
-- Aristotle
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
