Today, it offers services similar to those of Microsoft and Google with WorkMail being its managed email application. Moreover, you have to do an ugly line before calling send like so: its humble beginnings as a small e-commerce platform, Amazon has become a massive behemoth with physical products ranging from books, apparel and consumer electronics to high-end services including digital content streaming, cloud services and even artificial intelligence and machine learning offerings. That's dope and no interface also makes it unmockable which might blow your integration tests. There are some issues with the library though, first, before sending you have to call Connect which takes host and port as parameter, that means you cannot just inject premade smtpclient as singleton and have to instantiate it within the place of usage. NET Standard so I ended up using Mailkit. NET Core and I didn't want to spend time porting not my own library to. Sadly, most of them are paid, there is AIM but it doesn't work with. You can either try tunneling or better just use one of the available libraries. If you are trying this, you will not get this to work using standard SmtpClient and as usually the case with Microsoft, they don't recognize it as an issue. You see, WorkMail allows only connections that start from SSL and the SmtpClient first starts from unencrypted and then switches over to encrypted if it cannot connect.
NET Core SmtpClient does not support StartSSL (implicit SSL) which is the only accepted option by WorkMail. A quick guide to getting up and running is here : Just in my personal experience, I think Mailkit is great and super easy to use. Much to some developers chargrin who don't want to use a third party library for such a "simple" and common feature.
#Shortcut bar in amazon workmail full#
MailKit is actually being pushed by Microsoft full stop for people to use when it comes to Email. It's kinda deprecated, but not being marked so in some official docs. It would instantly make any project that is using SmtpClient with Warnings as Errors turned on suddenly stop building. NET Core team wanted to mark it as obsolete, but some developers have existing projects with "Warnings as Errors" turned on. See comments here ( )Įssentially it boils down to SmtpClient hasn't been updated in years and is missing many features. SMTPClient is actually obsolete/deprecated but is not being marked as so. Although this would not be a relevant solution, I also increased the timeout to 10 seconds (even though this would not be a solution).Īny idea what could be wrong? I am tearing my hair already. We tried switching for 587 for STARTTLS and providing the Username without the domain The server sending has proper SSL certificate installed and the mailserver is exactly the one we have our smtp on. Sadly, the sending always fails with a gateway timeout. Mail.To.Add(new MailAddress(sendToEmail)) The settings are injected and the SmtpClient gets properly instantiated and the sending of the email is just: var mail = new MailMessageįrom = new MailAddress(_smtpSettings.FromAddress, _smtpSettings.SenderName), The configuration is very standard according to Amazon Documentation: I am trying to send a standard email message through AWS WorkMail using the SmtpClient in.
0 kommentar(er)
