Skip to main content

Sending Email with System.Net.Mail

Sending mails using the .NET’s SmtpClient API is very easy and straightforward. Alas the same doesn’t count for mocking the client in your unit test. So most of the time I create an extra layer of abstraction and wrap the SmtpClient in an IEmailService.  And this works fine for my unit tests.

But for my integration tests I follow a different strategy. By default, the SmtpClient takes mail server settings from your web.config or app.config file.

To configure it to send e-mail through a particular SMTP server, add the following to your web.config file:

   1:  <configuration>
   2:     <system.net>
   3:        <mailSettings>
   4:           <smtp deliveryMethod="Network">
   5:              <network host="smtp.example.com"/>
   6:           </smtp>
   7:        </mailSettings>
   8:     </system.net>
   9:  </configuration>

But this means that an actual mail server has to be configured to run my integration tests and even worse that some test mails will be send out to everyone.

Instead it would be better if you could write mails to a local directory, so you can see what’s happening without having to set up an actual mail server. This is done very easily, change your  config to use these settings:

   1:  <configuration>
   2:     <system.net>
   3:        <mailSettings>
   4:           <smtp deliveryMethod="SpecifiedPickupDirectory">
   5:              <specifiedPickupDirectory pickupDirectoryLocation="c:\emails" />
   6:           </smtp>
   7:        </mailSettings>
   8:     </system.net>
   9:  </configuration>
  10:   

This will write .eml files to the specified folder, which must already exist and be writable. If you double-click .eml files in Windows Explorer, they’ll open in Outlook Express or Windows Mail.

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more