Jump to content
Xtreme .Net Talk

content-transfer-encoding: base64 vs quoted-printable SMTP and .net framework 2.0


Recommended Posts

Posted

Howdy,

 

I'm hoping someone may know the answer to this.. I am using .net 2.0 frameworks smtpclient class object from System.Net.Mail namespace to send emails in a C# application.

 

It seems that when the email gets sent, it sends it with base64 encoding, though my body of the email is actually encoded using System.Text.Encoding.UTF8;

 

This works fine to read the body in Outlook or to use webdav commands, but when I try to use my pop3 class objects, which I found at: http://www.codeproject.com/csharp/despop3client.asp It fails to see the email as multipart and the body is actually just a string of characters like "DFDFKDJ343DFDF" etc.

 

Does anyone know of a workaround on .net 2.0 class object to make the content-transfer-encoding quoted?

 

Hopefully this is understandable as to what I'm asking and having trouble with, as I'm new to the .net c# arena when it comes to building custom email apps...

 

Thanks

  • 3 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...