Email logs

Both the CollabNet TeamForge email and search backends are managed from a parent daemon known as Phoenix. If the mail backend is not operating properly, the first troubleshooting step is to check the phoenix.log to see if it encountered difficulties starting up.


The Phoenix daemon logs its activities to the phoenix.log file, which is stored under SOURCEFORGE_INSTALL_DIR/james/james-2.2.0/logs. This log is overwritten each time Phoenix is (re)started. Phoenix is run as part of the CollabNet TeamForge standalone server init script.

CollabNet TeamForge email is handled by the JAMES server. JAMES logs all of its activities under SOURCEFORGE_INSTALL_DIR/james/james-2.2.0/apps/james/logs. A new log is created for each date when there is activity, and additional logs are created if james is restarted on a date when there is activity. The date is embedded in the log name (such as james-2005-04-28-01-00.log).

Active logs

Sixteen different logs are created by james for different components of its functionality. This topic describes only the ones that are used actively by CollabNet TeamForge .

The James log records the overall mail handling behavior of the James server.
The mailet log records how each piece of email is handled. If there is a mail delivery problem, this log is the best place to begin investigation.
The mailstore log records the behavior of mail spools, and the storage of mail. This log should normally not contain errors unless James is unable to write or read mail to or from the file system.
The smtpserver log records all inbound mail handling results. If email to discussion forums is not posting, or is getting rejected, this log would be the best place to begin investigation.
The spoolmanager log records the processing of mail spools. This log could be of value in troubleshooting mail delivery or handling problems.