naasking

Sorry, I just realized I never got back to you on this. I switched away from parsing into the System.Net.Mail.MailMessage data types back in 2018, so the code you're depending on is very out of date and I don't anticipate digging into that again to fix issues. I can only advise upgrading to the newer Sasa releases that depend on MailKit, or even better, to use MailKit directly.

I'm currently on vacation and probably won't get to this for another week or so. The Sasa mail parsing api is largely obsolete though, since there are better libraries available. Sasa internally uses MimeKit and MailKit, so I recommend using those directly if you can.

Sasa v1.0.0-RC2 Released

Thanks Andrew, your change has been merged. I didn't have to add those dependencies to Build\packages.config though. It also revealed a bug maybe indicative of a change in the System.Uri parsing behaviour. I'll push out a new RC soon.

Update target frameworks

Thanks Andrew! Sorry for the delayed reply, but I didn't receive any kind of notification of your merge request, I just happened to notice it when I visited the home page. I'll have to look into that. Managing the builds has always been the least interesting part which is why I just target .NET standard, but this looks pretty straightforward so I'll definitely look at it sometime this week. I agree that the huge dependency graph is irritating.

Sasa v1.0.0-RC1 Released

You'll be happy to hear that the latest Sasa release targets .NET standard 1.3, so it should be compatible with most .NET core runtimes.