windows mail encoding order

[charlymz]

i detected a bug where a mail send from windows mail on windows 8 wasnt parsing ok
--739CC2DA-F094-4259-95D2-56B6A454FCFF
Content-Transfer-Encoding: base64
Content-Type: text/html; charset="utf-8"

this is part o fthe mail notice the order of Content-Transfer-Encoding first then Content-Type
changed function public function getBody($returnType=self::PLAINTEXT) between lines 213 - 248 to deal with this

    foreach ($this->rawBodyLines as $line) {

        if (!$detectedContentType || $waitingForContentStart || $contentTransferEncoding == null) {

            if (preg_match($contentTypeRegex, $line, $matches)) {
                $detectedContentType = true;
            }

            if(preg_match('/charset=(.*)/i', $line, $matches)) {
                $charset = strtoupper(trim($matches[1], '"')); 
            }                 

            if ($contentTransferEncoding == null && preg_match('/^Content-Transfer-Encoding: ?(.*)/i', $line, $matches)) {
                $contentTransferEncoding = $matches[1];
            }                

            if (self::isNewLine($line) && $detectedContentType && $contentTransferEncoding != null) {
                $waitingForContentStart = false;
            }
        } else {  // ($detectedContentType && !$waitingForContentStart)
            // collecting the actual content until we find the delimiter

            // if the delimited is AAAAA, the line will be --AAAAA  - that's why we use substr
            if (is_array($boundaries)) {
                if (in_array(substr($line, 2), $boundaries)) {  // found the delimiter
                    break;
                }
            }
            $body .= $line . "\n";
        }
    }

[appastair]

If you've tested your changes, commit them or (as it's a minor modification) in your browser then do a Pull Request.