Accented characters from UTF-8 attachments are converted to ?? about hpop HOT 5 CLOSED

I suspect that OpenPop assumes US-ASCII as encoding, since no encoding is specified in the Content-Type. OpenPop does not try to guess the encoding if not specifies, it defaults to US-ASCII. Not sure if this is specified in an RFC anywhere.

Most XML documents are UTF, and it also says so in the first line. However, OpenPop does not inspect the contents of an attachment, but only looks at the MIME headers. If this is general for your application, you could decode the bytes to a string yourself, using the correct encoding.

from hpop.

This can fixed by changing in MessagePrt.cs GetBodyAsText() method to

    public string GetBodyAsText()
    {
        return Encoding.UTF8.GetString(Body);
        // Original gets ?? characters instead of unicode ones
        //return BodyEncoding.GetString(Body);
    }

How to change OpenPop so this can used without changing source code ?

from hpop.

Your changes would destroy any attachment which does not use UTF-8. Instead, you should convert the raw bytes yourself:

MessagePart m = ...; // Get the message part somehow
string text = Encoding.UTF8.GetString(m.Body);

In that way, you do not have to change OpenPop.

from hpop.

Shoud line in sample code

                        var xml = ado.GetBodyAsText();

changed to
var xml = Encoding.UTF8.GetString(ado.Body);
?

from hpop.

Yes

from hpop.