John Peacock wrote: > Robin Bowes wrote: > >>I was expecting to get little or no output in the detailed log for a >>message that was delivered successfully. > > > No, the detailed log is exactly like running the standard logging with > LOGDEBUG. > My initial attempt at this collected up log lines and only output them when > the > message was ACCEPTED or REJECTED. The problem with this was that the log > lines > would not be spooled at all if the remote server hung for a while, the log > lines > would not get timestamps contemporaneous from when they were actually > generated, > and there is the added memory to spool these lines. > > The way I am using this, I have detailed logs going back no more than a day > and > accepted logs going back two weeks. I typically find that if there is a > problem, I find out right away (and can check the detailed logs), but I > sometimes need to demonstrate that something went out OK last week. So I am > covered both ways...
John, This does indeed help. I now understand what's happening! It's not quite what I'd like to see. Ideally, I'd like to have three logs: 1. detailed - everything in here. Level of detail controlled by loglevel 2. accepted - sender/recipient details for accepted mail 3. rejected - sender/recipient/host/reason for rejected mail Any ideas how to achieve this? Michael Holtz's denylog plugin may be of some use. Perhaps I can modify that to write a leading character to each line logged and filter into a separate log file using multilog? Thanks for any suggestions. R.
