Bug#396003: 396003: exim4 paniclog reports

[Ross Boylan]

I also think it would be better if the cron job only reported when new
material was in the paniclog. tiger, for example, takes this approach to
its warnings.

Arguably the continued nagging is a feature.  However, there are 3
possible responses
1) ignore the messages.  This is  what I was doing, but it's dangerous
if something new goes wrong.
2) check the log each time.  tedious, and likely to turn into 1.
3) follow the recommended (by README.Debian) practice and rename the
file.  tedious, and also possibly leading to the accumulation of such
files (I ended up appending the contents of paniclog to paniclog.1 and
deleting the former).

If the cron job just reported on new stuff, I think everything would
"just work" (tm).
-- 
Ross Boylan                                      wk:  (415) 514-8146
185 Berry St #5700                               ross at biostat.ucsf.edu
Dept of Epidemiology and Biostatistics           fax: (415) 514-8150
University of California, San Francisco
San Francisco, CA 94107-1739                     hm:  (415) 550-1062