E-mail (SMTP) API for CoreCLR yet? If not, options??

[guardrex]

Back in January, @Eilon commented that CoreCLR didn't expose any E-mail capabilities (e.g., I don't see System.Net.Mail at MyGet)? Take home message: dnx50 can take on System.Net.Mail, but dnxcore50 can't.

Is there any way to coerce System.Net.Mail into a CoreCLR app?
If not, that also means that I couldn't do something like add in Interop.CDO, correct?
How about using TcpClient (or something like that) to an SMTP relay server?
Is there anything built-in to WS2012 that I can hook that would forward the mail to my relay server?
Could I hook into an install of hMailServer across an Azure VNET to send mail (i.e., the mail server would be on another VM)?
If these would all be dead ends, is the only option to consume some kind of external E-mail service?

[danieltharris]

Did you get your answer in the end?

[guardrex]

Not from the team, but after looking around the Net, it seems the way to do this is via TcpClient. It's in the System.Net.Sockets namespace and available in CoreCLR. There are a ton of references online about how to code SMTP communication directly with mail servers at a low, command level using TcpClient. For example, this one on SO.

I'm planning on asking the guys today on the Community Standup for any info on System.Net.Mail for CoreCLR. I just have a gut feeling that they don't know when they'll get around to it ... they seem very, very busy frying bigger fish right now.

When I get a working code sample, I'll add it to this issue. I hope to get into it this afternoon.

[Eilon]

Please file a bug on https://github.com/dotnet/corefx - that's where the CoreFX libraries are. This type of library API wouldn't be ASP.NET-specific anyway.

[guardrex]

Thanks @Eilon. I've posted a UserVoice request for this: Please vote for it here if you are in favor of having System.Net.Mail in CoreFX.

[guardrex]

I put a little sample SMTP port 25 code for talking to a mail server on the network over at https://github.com/dotnet/corefx/issues/1006.

[jstedfast]

Another option for those needing System.Net.Mail functionality is to use MailKit instead.

One thing that developers may be interested in is that because the MimeKit library that MailKit uses supports generating DKIM signatures, it's possible to start sending mail with DKIM-Signatures which is becoming more and more important for getting past spam filters.

If you run into any issues, feel free to report problems to the MimeKit and MailKit issue trackers and I will do my best to fix them as quickly as possible.