Lurgle.Alerting v1.2.0 released - Consistent attachment content types!

I've released a small update to Lurgle.Alerting which adds automatic determination of the attachment content type using the MimeMapping library. I've raised the version to v1.2.0 to align with Lurgle.Logging's current releases.

This specifically addresses an issue when sending attachments with MailKit as the SMTP sender. The FluentEmail implementation was essentially causing a System.ArgumentNullException exception in MimeKit.Utils.ParseUtils.ValidateArguments, because content type defaults to null. With the old SmtpClient, that was okay, but FluentEmail was explicitly trying to parse a null content type and receiving the error.

The aforementioned MimeMapping project on Nuget had an extensive set of mime types and provided a straightforward way to perform a 'best effort' match based on file name, with a sensible default of application/octet-stream. Perfect.

As a result - Lurgle.Alerting will always supply a valid mime type to the underlying SMTP sender if you don't pass one. If you do pass a content type and it's invalid, we don't attempt to validate that at this point - so you will likely get an exception.

As per normal, update from Nuget, or via the oh-so-fancy links below.


You may also like:

Event Timeout for Seq v1.4.2 released

A new release of Seq.App.EventTimeout is out. This was a little earlier than I planned to release v1.4.x, but there was a bug in the AbstractAPI deserialization as a result of some code refactoring which I'd missed. As usual, you can install Event Timeout for Seq using Seq.App.EventTimeout as the...

Lurgle.Logging v1.2.0 - Multi-threaded correlation ids are now a thing

Multi-threaded correlation ids were not a thing Following on from my work on Seq.Client.WindowsLogins and the subsequent realisation that EventLog's EntryWritten event handler is bad and should feel bad, I contemplated whether I could apply some of my efforts to solve another issue that had been bugging me. Lurgle.Logging was...

Lurgle.Alerting - a standardised FluentEmail implementation with extra goodies!

Another Lurgle Around the time that I tackled my original Serilog logging implementation, I also looked at our email alerting. Emails can be used for a variety of reasons, and it's not uncommon that they are sent as a simple string that concatenates or formats variables. In this scenario, the...