we ran into a problem where a user receives an email message with multiple PDF attachments of which some are broken and instead of there being "filename with more than 64 characters.pdf" there are two files, "file6.part" and "filename with 64 characters" without extension (actually not sure if it had an extension or not, but if there was, it was .part or similar).

Now, if I forward (as an attachment) that mail to myself to another mail software (in this case KMail on Linux), all the attachments are fine and ok. Looking at the message source shows the possible problem where Groupwise hits a bug. The broken attachment is declared as follows:

Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"

Content-Disposition: inline; filename*0="a file with long filename, original filename
changed to protect";
filename*1=" the innocent.PDF"
Content-Type: application/pdf; x-unix-mode=0644; name="a file with long
filename, original filename changed to protect the innocent.PDF"
Content-Transfer-Encoding: base64

Apparently Groupwise doesn't handle that filename broken in two pieces that well. Filename has been changed but formatting is exactly the same.

I wonder if this is a known problem, should I report this as a bug somewhere?