John Zheng wrote:
I'm not sure what the version is, as the installer was packaged with
another piece of software. Is there an easy way to find out the version?

You should see version information when you start James, or maybe in a stdout/stderr log file.


The repository is just the file system.  I don't believe these messages
receive any special processing, although certain types of messages doe
receive special processing.   Perhaps sending you the configuration file
will help?

Yeah perhaps, but don't think it's necessary yet.


My examination of log files didn't point out anything obvious.  Can you
point me to what log files I should examine to determine where delays
may be occurring?  There seems to be several log files generated by
James, and I'm not sure which log file or files are the most relevant.

In <james-dir>/apps/james/SAR-INF/environment.xml, you can change the log level for James.Mailet and spoolmanager to DEBUG to give you more information on what messages are doing.


To clarify what I'm doing, I'm basically sending an email to a local
user.  Then trying to immediately retrieve that same message.  I notice
the message seems to sit in the spool directory for exactly 60 seconds,
at which point it disappears from the spool folder, and I'm able to
retrieve it using pop.

Yeah, it does seem to be sitting in the spool once received for a bit before getting processed. Not sure what is the issue yet though.


--
Serge Knystautas
President
Lokitech >>> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. [EMAIL PROTECTED]


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to