I have had James v3B5 running for several years on a WinServer16 box.
In the last couple of weeks, the service has failed to start. I can
open a command prompt and run James with the 'run' bat file from there
without any problem. I've tried rebooting. I uninstalled the service
and reinstall
Hey Jason,
I thought again about the database sync and ID conflicts: I don't know if james
generates the id or if the database does, but no matter where the id is
generated it should be possible to modify it to be a unix timestamp instead of
a counter. Reason: it's very unlikely that two instan