Hi, I've found a problem with parsing messages from some spammers. Thought their messages are parsed and displayed by popular E-Mail clients like TB or Outlook. The problem is that their content-type header is look like this: Content-Type: multipart/mixed; boundary=----=_NextPart_000_0004_01C5OEWG.X25IPK30 So gmime expects that boundary in message is ---- as '=' is special characters and must be enclosed in double quotes according to RFC. The problem is that decode_token function from gmime-param.c stops processing of value when it gets special character. So I'd like to ask is there any safe way to patch this code to "eat" some of special characters in detecting boundaries? Here is an example of message where gmime find no parts.
Attachment:
test1.eml.gz
Description: GNU Zip compressed data