Invalid Queue Files with Postfix
list-mailscanner at linguaphone.com
Mon Aug 20 15:06:43 IST 2007
On Mon, 2007-08-20 at 14:59, Brad Beckenhauer wrote:
> >>> On 8/18/2007 at 9:09 AM, in message <46C6FDA7.3080605 at ecs.soton.ac.uk>, Julian
> Field <MailScanner at ecs.soton.ac.uk> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > Brad Beckenhauer wrote:
> >> That would be a nice feature request for MailScanner, something to
> >> provide consistant volume benchmarks across all supported MailScanner
> >> platforms.
> >> Something like:
> >> MailScanner -stats
> >> or a configuration setting to enable benchmarking with the
> >> understanding that there would be system overhead associated with the
> >> additional process.
> > What stats would you like it to log that it doesn't already?
> > There's no communication between the child processes once they are
> > started, but I could add a signal trap so that a kill -USR or something
> > would make them dump some figures to some file or other, then restart
> > the batch they were on. They already catch kill -HUP to force them to
> > die. So exactly what do you want to do when it receives a SIGUSR?
> Several times on the list I've noticed questions like "What's your volume?".
> Is there already something in MailScanner that can generate an answer to that question?
> My first thought would be to have MailScanner calculate the daily volume of total daily messages processed. That way when the "What's your volume" question comes up, there is a standardized way to respond to the question. An hourly histogram would be an interesting stat.
> TIME Msgs processed
> 00:00-01:00 xxxx
> 01:00-02:00 xxxx
> 02:00-03:00 xxxx
> Mail Volume xxxxx
> Hourly Avg: xx%
> Anyway... That was the thought..... Feel free to toss the idea to the bit bucket. I'm not going to be arguing the idea.
> Thanks for listening.
I just use standard logwatch as it gives a good daily summary.
More information about the MailScanner