There are a few errors in the text you posted.
This is not a valid multiplayer meme. Check out the wikipedia link , which, although not normative, is still correct.
Mimic border is not defined. From the wikipedia example: Content-Type: multipart/mixed; boundary="frontier" Content-Type: multipart/mixed; boundary="frontier" indicates that the border is a "border". In your example, "---- = _ NextPart_000_005D_01CC73D5.3BA43FB0" is the border, but this can only be determined by scanning text ( ie ). You need to instruct goofball, which gives you mime content, which you also need to know the mime border value that is not defined in the message header. If you get all the text of the message, which you will have enough, because the body of the message starts with MIME-Version: 1.0 , followed by Content-Type: multipart/mixed; boundary=" frontier " Content-Type: multipart/mixed; boundary=" frontier " , where the frontier will be replaced by the border value for the encoded mime.
If the person sending the body is goofball (changed from a monkey because the monkey is too subjective - my bad DwB) and will not (rather know how) send the full body, you can get borders by scanning the text for the line that starts and ends with the symbol "-" ( ie --boundary--). Please note that I mentioned the "line". The terminal border is actually "- borderline - \ n".
Finally, the material you published is in two parts. The first part seems to determine the replacements to be made in the second part. If this is the case, the Content-Type: of the first part should probably be something other than "text / plain". Maybe "companyname / substitution-definition" or something like that. This will allow the use of multiple (as in future improvements) replacement formats.
source share