How to set the MAIL FROM envelope when using SmtpDeliveryMethod.PickupDirectoryFromIis

Question

Hi,

When you send an email using System.Net.Mail you can set the SMTP MAIL FROM envelope by using the MailMessage.Sender Property.
If you set the smtp network deliveryMethod property to be "Network", the MAIL FROM envelope is set using the Sender value.
If you set the smtp network deliveryMethod property to be "PickupDirectoryFromIis", the MAIL FROM envelope uses the MailMessage.From property instead of the Sender one.

Any suggestion how to keep the value I need for the SMTP MAIL FROM envelope?

Thanks

Answer 1

This doesn't sound right. I'll do some research and come back to you. Can you post a code snippet? It will make it faster for me

Thanks
Mariya

Answer 2

Hi Mariya,

Thanks for the reply. Sorry for the delay in my answer, I've somehow missed the notification.

Here is the code snippet I use.
You will notice the different MailMessage.From and MailMessage.Sender

using (MailMessage mailMsg = new MailMessage())

{

mailMsg.Subject = "Subject";

mailMsg.Body = "Content";

mailMsg.To.Add(new MailAddress("[e-mail]"));

mailMsg.ReplyTo = new MailAddress(string.Format("\"{0}\" <{1}>", "exampleReply", " [e-mail]"));

mailMsg.From = new MailAddress(string.Format("\"{0}\" <{1}>", " exampleFrom", " [e-mail]"));

mailMsg.Sender = new MailAddress("[e-mail]");

SmtpClient client = new SmtpClient

{

Host = "localhost",

DeliveryMethod = SmtpDeliveryMethod.Network,

//DeliveryMethod = SmtpDeliveryMethod.PickupDirectoryFromIis,

};

client.Send(mailMsg);

}

if I use the first delivery method (SmtpDeliveryMethod.Network), and I analyze the packets using Wireshark, here is what I have
23049    109.881909    192.168.XX.XXX    66.XXX.XX.XXX    SMTP    C: MAIL FROM:<[e-mail]> SIZE=663

If I use SmtpDeliveryMethod.PickupDirectoryFromIis as my delivery method, here is what I see
32163    153.352097    192.168.XX.XXX    66.XXX.XX.XXX    SMTP    C: MAIL FROM:<[e-mail]> SIZE=601

Obviously the first result is the one I would like to keep.

Thanks

Answer 3

I've just run into the same problem; switching the delivery method to "network" fixed it.
I've reported this as a bug: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=483878

Answer 4

The bug report has just been updated:
"Fix will appear in a future release of the .Net framework."

There's no indication which release - I would hope it makes it into v4.

Answer 5

I know this thread has been dormant for quite awhile, but is this confirmed to be fixed in the latest .net 4 build (RTM)?

Answer 6

I've just tested on .NET 4.0 RTM, and it looks like it's fixed.