Also, when Mercury is restarted, the session log target filename index is reset and any existing files for the corresponding session index are appended to rather than being overwritten, hence the large files if this has been session logging continuously for some time.

I have a scheduled script that cleans out old session logs, so if I want to have the logging running for a while (or forget it is on) it doesn't fill the disk.

The Mercury mail server has a folder named SESSIONS that contains MERCURYB, MERCURYC, etc folders corresponding to the different modules you can use.

On our server the MERCURYE and MERCUYS folders use over 14GB of drive space (some of the files are almost a gigabyte). With a short peak into the content of these files I've noticed that most of it is quite old, with just a few that actually were updated with new information recently. And as far as I can tell these files look like they just contain logging.

Am I correct in assuming this is just logging and not anything that is crucial to the working of Mercury? We want to clean up these folders to reclaim some drive space.

Hi,

as far as I know the SESSIONS folders are for logging only. Mercury creates a separate file for any session, that is, any mail that passes through Mercury. The files contain the server commands and also the mail contents in some cases. But how can a single file be ~1 GB large (unless you send mails that big?)

You can delete these; Mercury will continue creating new ones. You may also uncheck the "enable session logging" option in your respective Mercury modules to disable logging completely.

Bernward

Some of those files are so big thanks to binary data (attachments) in the sent emails.

We'll leave on the logging just in case we ever need it. But with this information we can clean these folders now and then to keep them manageable.

Session logging is meant to be used for debugging under a shorter time, and it's recommended to switch it off when there is no specific issue to investigate.

/Rolf