[Pidgin] #11598: purple_mime_document_parsen() broken when '=' char included in boundary

[Pidgin]

#11598: purple_mime_document_parsen() broken when '=' char included in boundary
-------------------+--------------------------------------------------------
Reporter:  haakon  |        Type:  patch         
  Status:  new     |   Component:  libpurple     
 Version:          |    Keywords:  mime libpurple
-------------------+--------------------------------------------------------
 libpurple's purple_mime_document_parsen() in mime.c behaves incorrectly
 when MIME multipart message contains '=' in the boundary.

 For example I found that MS Office Communicator 2007 R2 sends messages
 like

 Content-Type:
 multipart/alternative;boundary="----=_NextPart_000_009D_01CACDCB.F5BB04D0"

 With current implementation, boundary gets parsed like

 _NextPart_000_009D_01CACDCB.F5BB04D0"

 so no message parts are found afterwards.

 I believe attached patch fixes this issue.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/11598>
Pidgin <http://pidgin.im>
Pidgin