Jamin - 2008-07-09 17:25:16
We've had this problem show up recently, where our clients are scanning a document and emailing it to us - however, their scanner software is naming the file something like "07-07-2008 05;18;41PM.jpg".
The full part header of that particular file looks like this:
------=_NextPart_000_0001_01C8E055.ECCBCB80
Content-Type: image/jpeg;
name="07-07-2008 05;18;41PM.jpg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="07-07-2008 05;18;41PM.jpg"
In an older version of your class file (which is excellent, by the way!), several notice-level errors were thrown when it encountered these files (Uninitialized string offset: 0 in lines 745 and 370). I updated to the newest class file, and it's at least no longer throwing errors. However, it's still dropping everything after the first semicolon, so the filename after parsing is just "07-07-2008 05". This is causing problems with some other things I've got going on in the app, because it can't find the "jpg" at the end and is unsure how to handle the file.
I realize that semicolons are "special" in headers, and probably shouldn't be part of the filenames in the first place. But is there possibly a workaround to this, so that we can still get it to go through fine?
Thanks in advance!
Manuel Lemos - 2008-07-09 17:45:45 - In reply to 
