Hello Nick!

 I cannot share your experience, as my systems all run on linux.
 There are however some sidenotes I would like to make.

 The problem you encounter could be caused by a memory leak and thus may
 depend on the ammount of available memory. A regular restart could
 circumvent a unsuspected shutdown and as a consequence demonstrate that
 there is indeed a memory leak.

 Why does this happen to ypu and apparently not to others. I have been
 experimenting with DBridge for some time and I was surprised at the way you
 trigger DBdrige for outgoing mail.

 Under common circumstances binkd scans the outgoing directory every minit,
 and initiates transfers for outgoing mail.
 To me it looks like you also refresh the config files, or its timestamp,
 to initiate a mail scan.

 There should be no harm in what you are doing, but on my system .e.g. the
 configfile timestamp is only triggerd, when I change a config parameter and
 once a day when a new nodelist is generated.

 So in general you may be refreshing the configfile more often as others.

 I hope that my suggestions can help to mitigate your problem and also help
 to pinpoint the cause of your problem.

16 Jun 18 18:33, you wrote to All:

 NA> For the second time now in a few months, BinkD 1.1a-95 just randomly
 NA> terminates with no error message, nothing in the log, no indication of any
 NA> problem whatsoever, after a good month or so of uptime.

 C:\DB>> binkdwin -vv

 NA> Binkd 1.1a-95 (Dec 10 2016 21:44:31/Win32)
 NA> Compilation flags: mingw32, zlib, perldl, https, ntlm, amiga_4d_outbound,
 NA> bwlim,
 NA>  ipv6.
 NA> Facilities: fts5004 ipv6

 NA> Nick

 NA> --- Renegade vY2Ka2

Kees

--- GoldED+/LNX 1.1.5