At 13:42 2009-10-30 -0500, Harry Putnam wrote:
But like you said, its at the end so it appears those kind of changes
don't really effect the first part of the non-decoded subject lines.
Correct - though the text following "Retrospect" can have an effect on the
trailing encoding:
$ echo "Retrospect" | mimencode
UmV0cm9zcGVjdAo=
$ echo "Retrospect " | mimencode
UmV0cm9zcGVjdCAK
Note that the mere addition of a space causes the final 3 characters of the
encoded text to change. This was an oversight even in my own reply to you,
where I suggested you could use mimencode to create a string to match
against (but then, that wasn't really my preferred solution anyway <g>).
While in your particilar case, you can manage to match against some fixed
portion of the known encoding from the subject because you're just using a
portion of a known static string, you really are better off considering a
mime decoding and then matching the string, per the recipe I posted.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)de
http://mailman.rwth-aachen.de/mailman/listinfo/procmail