Jason Finch

I believe this is the origin of Thread.ResetAbort() being obsolete https://docs.microsoft.com/en-us/dotnet/api/system.threading.thread.resetabort?view=net-6.0 MS suggest using CancellationToken as a alternative. https://docs.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/5.0/thread-abort-obsolete

Have you considered persisting your cache to something like a REDIS store? It should afford you the speed of maintaining a cache and not be affected by which node runs...

@zlepper , There is a unit test `ReschedulingTriggerShouldKeepOriginalNextFireTime` , which if I understand your issue, means that when you trigger `scheduler.RescheduleJob()` it will still keep the original nextFireTime for the...

@zlepper , What I've noticed: trigger.GetNextFireTimeUtc has the expected future trigger time. When the triggerBuild.Build() completes, the result trigger has a null `nextFireTime()` and a historic `startTimeUtc`. The docs say...

@lahma I found the logic for all this deep to investigate. It may benefit if there was a clue (log) to the above scenario occuring? Something like a debug/warn log...

@olivier65 Where are you seeing `--service` used as a parameter? In the docs, it talks about using `sc.exe` or powershell with a `--service` argument but the smtp4dev executable doesn't appear...

I don't have a Linux env running, according to this page; https://developers.redhat.com/blog/2018/11/07/dotnet-special-folder-api-linux# `AppData` maps to: 

@craigs100 The default configuration will have the website interface running on `http://localhost:5000` https://github.com/rnwood/smtp4dev/wiki/Installation ` Open your browser at http://localhost:5000. To run the web server on a different port or make...

@craigs100 apologies, as mentioned I'm not in a position to assist with linux configs. From what you posted, it appears the SMTP port failed to bind, possibly because you already...

@thecliguy, the more recent CI builds have serilog logging, but the official release (at time 3.1.3.2) is using net logging. The interesting challenge here is maintaining the documentation for both...