Nicholas Blumhardt

Hi all! Awaiting the logger's `flush()` method should now work, and no synchronous APIs should be needed: ```js await logger.flush(); ``` If you still run into any problems or incompatibilities...

Thanks for the heads-up, @Jaben. I'm assuming that trusting the self-signed cert on the Seq server isn't an option for you? That's generally the ideal approach, but understandably not always...

In case it helps in the meantime: https://serverfault.com/questions/1102376/error-sending-email-with-office-365 has some configuration suggestions on the O365 end.

That's great, thank you, @vmandic 👍

Hi Damiaan, thanks for giving this a nudge! 👍 Your timing is great, we're rewriting the email app with a view to addressing some of these longstanding issues. Because a...

Thanks for dropping by, @jods4! Time has been a little short lately, but I'm looking forward to circling back and finishing this up for the (I guess impending) NLog 4.5...

Thanks for your replies. I can see on the surface how separate settings seem to make sense, but as soon as you've selected the "ignore certificate errors" option, the other...

Howdy! We've pushed forward with Seq.App.Mail.Smtp, it might not perfectly line up with what you had in mind but if I've understood everything correctly it should be usable in the...

Thanks for that, @vmandic! Just thinking - since `-` is not a valid identifier char in Seq's query language, it's inconsistent to allow it while disallowing other invalid identifiers. Perhaps...

Thank you - looks great! I'll loop back to this in the next few days, I'll need to quickly run over history and make sure I'm not overlooking anything important...