mirror of
https://github.com/mailscope/kumomta.git
synced 2026-09-03 17:38:17 +00:00
Wez Furlong
6359820d3d
We had a user report that launching kumod post-7fbec8758720dad465d711458f6bf7923b778773 produced a panic about the spool not being configured. My supposition is that they were bringing the system up under load (incoming traffic) and that a new message was being injected before we had started the spool. So what we do here is restore the spool_started check, but have it be satisfied once the startup has been triggered, rather than on completion of enumeration. The result is that there is still a small window where we might turn away a message during startup, but it should be very very small.