----- Original Message -----
From: "Charles Benett" <[EMAIL PROTECTED]>
> Stuart Roebuck wrote:
> >
> > Two thoughts / ideas / questions:
> >
> > 1. At the moment, when I change the configuration of JAMES I kill the
process and restart to load the new configuration. Is this the correct way
of doing things? What happens if email is being received at the time? Off
the top of my head it seems like it would be useful to have a feature of the
admin facility that allows you to reload the configuration. On the other
hand it may be that everything just works and my restarting is unnecessary.
Yes I agree james should be able to reload the conf file, but like Charles
said, we should be able to do this more gracefully with the new avalon.
You should be safe killing the server at most any point... even if it's
storing messages to the file system, james stores the message before it
responds to the remote SMTP agent that delivery was successful. If james
gets killed before giving that "Message received" command, the remote server
will retry later, and nothing should get lost. The only bad thing that
*might* happen is during internal message processing... as a message moves
through a processor, james doesn't store that it's partially through the
process or the message again if it were modified. Normally this means
nothing bad will happen... even if you're changing the message, as nothing
is saved until it's through the processor. However, if you spawn new
separate messages (like a notice that something has arrived) or external
events (like writing to a log file), you might get a second notice or log
entry after the server is restarted.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
