Another. I’ve run Surgemail under several OSs (currently MacOS) and have never seen a clean shutdown. Always just chalked it up to a quirk that didn’t affect anything and ignored it. :)

> On Mar 9, 2018, at 1:10 PM, John Wilkes <john@wilkes.com> wrote:
> 
> If I shutdown SurgeMail from the browser admin interface, the swatch process is still running. If I then reboot the system, I do not see the error message.
> 
> Not sure what that implies, but it’s another data point.  ;-)
> 
> -- 
> John Wilkes
> john@wilkes.com
> 
> One of the advantages of being disorderly is that
> I am constantly making interesting discoveries.
> 
> 
> 
> 
> 
>> On Mar 9, 2018, at 12:52 PM, surgemail-support <surgemail-support@netwinsite.com> wrote:
>> 
>> 
>> Interesting,  I wasn't aware of this issue.  We'll look into it and sort it out.  
>>    ChrisP.
>> 
>> 
>> 
>>> On 10/03/2018 6:42 a.m., John Wilkes wrote:
>>> The default, standard system shutdown kills the main surgemail process but not the swatch process? That probably explains why I can find any obviously useful information about the error in the SurgeMail crash log file.
>>> 
>>> Question for SurgeMail support: Can this be fixed in a future SurgeMail release?
>>> 
>>> 
>> 
>> -- 
>> I'd really appreciate it if you could take a moment to like us on FaceBook, thanks heaps! ChrisP.
> 
>