At 17:14 2010-08-26, Michelle Konzack wrote:
Hmmm, the images are not always declared as "image/..."
Then amend the recipe to add whatever is necessary. What are you
seeing the files come across as anyway? content-aware email clients
aren't likely to display it if it isn't properly identified.
* 1^0 B ?? SkZJ RgAB # This hit nearly
* 1^0 B ?? RXhp ZgAA # 98% off all
* 1^0 B ?? R0lG ODlh # JPG/JFIF
* 1^0 B ?? R0lG ODdh # GIF
* 1^0 B ?? iVBO Rw0K # PNG
Looking to match specific sequences of BASE64 encoded values is
asking for trouble. I could for example send you an archive file
(ZIP, BZ, 7Z, etc) which contains files which didn't get compressed
as a result of them being too small or not particularly compressable,
and these sequences could be expected to match within the stream,
even though the actual attached file wasn't a GIF.
More than likely, the OP is trying to deal with image spam, where the
spammer is sending an image which contains their spam message. Seems
to me, there are a sufficient number of other characteristics on such
messages to identify them as spew without actually having to examine
the message body.
---
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