I was looking at the wrong log file. The core module did not have log file turned on. I set this up for a test using ~D so I would get a daily log file. Since I most likely would not look back more than a week.

Thanks for your help, Ron

Do to a situation beyond our control I am taking over the IT support for our company. One of the things we use in mercury32 for part of our email.

How can I tell if a message was killed? For example someone says jsmtih@domain.com is trying to send me a message but I am not getting it. I do know how to add this address to the content control and spamhalter so future emails get through. What I would like to know is how to look to see if in the past this email was actually processed / killed by mercury32. We had one time when I saw an email showed as "killed" on the mercury core process window but later that day when I tried to find that in the one log file it was not listed.

I am new to using mercury32 and may have been looking in the wrong log file and may not have the right log file(s) to show this turned on.

Thanks for any help you can provide,

Ron

The Mercury Core can log all files passing thru.  The setting is for this logging can be found in the Files tab of the Mercury Core configuration.  It is the "System log file" option and contains the path followed by the parameters for the log filename (eg: ~Y~W.LOG)  The ~Y designates year and the ~W designates week.  The result is a weekly log file.  See the help file for additional special character options for the filename.