Email Content Encoding with pop3-Socket


I fetch E-Mail with pop3-Secure-Socket.
I get an email with base64 Content-Parts. When looking in emailMessage.rawSource, I get:

[code]Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64


Looking in emailMessage.Source, I get:

[code]Content-type: text/plain;
Content-transfer-encoding: 7bit


But, as you can see, this isn’t 7bit, it is the same base64 as before.
Even emailMessage.BodyPlainText is this base64-string without any way to check if it is base64.
For me, this doesn’t seems to be wanted !?


btw. It is the same with things like “quoted-printable”…

if you query source of an EmailMessage object, the source is created for you on the fly.
So it’s not the same as the raw source you got before.

Hi Christian,

thanks for your answer. Maybe, it is created this way.
But it is not important. First of all I get incorrect data here. This is a problem for me.

Second is the workaround. I have emailMessage.BodyPlainText with the encoded Data in it. But there is no Information about the encoding. So this is not useable.

Now, I need to know which encoding is used. Guessing is no way for me.
Is there a way to get the correct Information for “Content-transfer-encoding” of the part-header?
It would be better if Xojo decode it and put decoded data to emailMessage.BodyPlainText etc.

So I think, I have to parse the emailMessage.rawSource myself. That is nothing I wanted to do :wink: