Good point!  I hadn't thought of that :-)  I wondered why the reports had stopped!  So, I will have to reduce the reporting period, if I do a daily restart.  I have now set it to 23 hours, which will lose some of the count.  I wonder if it will handle reporting periods that include fractional hours.

Gordon

I have started to use Mercury's mail statistics reporting function, using the 24-hour e-mail option.  I have not found any way to control when this message is sent.  I would like to align this with a complete day (midnight-midnight) if possible.  I have checked MERCURY.INI, but the statistics controls there don't seem to include anything about the reporting time.

The last two-days' reports came at close to the same time (3:12 pm), but previous ones seemed to be at quite random times.

I am not clear whether the reporting period finishes when the reporting e-mail is sent, though I suspect that it would be.

The timezone variable in MERCURY.INI is not currently set correctly (+0000, rather than -0400, currently for EDT), but this doesn.t explain the timing of the statistics message.

 Thank you

Gordon

The time is calculated from program start.

Thank you, DLN.  It seems that, if I set things up to exit and re-start after daily maintenance at (say) 2359 each day, that should do the trick.  The random times will be because I restarted Mecrury from time to time.

Gordon

Not quite :)

It will never reach 24 hours of uptime so will never generate the 24 hour report [:(]

DLN - Can you clarify this?  Why wouldn't it achieve24 hours uptime?

I am, in fact, counting categories of mail (particularly Spam) with external scripts, which do honour the 0000 to 2359 period, but the Mercury statistics would be a good complement.

Thank you

Gordon

[quote user="GordonM"]

DLN - Can you clarify this?  Why wouldn't it achieve24 hours uptime?[/quote]

Because if you "set things up to exit and re-start after daily maintenance at (say) 2359 each day" it will exit & re-start just before 24 hours is up. Same thing will happen next day...

So the down time is very minimal .... basically the time that it takes to do the daily maintenance and restart.  I should, maybe, set the maintenance time to be 0000, but I will still lose a few seconds, depending on how long these two processes take, regardless of what time this is set to.  I suppose that the worst result (which is insignificant) is that some messages could be available before midnight but not be processed until the next day, just after midnight.

Gordon

The point being, that when the program is restarted, so is the countdown to report generation.

So setting a 24 hourly report with a daily restart will NEVER generate a report.