brent.w at infosynergy.com.au
Tue Jun 12 06:14:10 PDT 2001
A good place to look for a start is the man page for logrotate. Can only
assume yor OS is linux....you don't mention it.
You have not probably recieved any answer for this because it's beyond the
scope of the list....it's something that is part of being a sysadmin,
not something that is a flaw/function of the sanitiser.
There are a hundreds of tools available for log management, a good place
worth read thru for an answer is:
Sorry if this is blunt but that's the way it is.
----- Original Message -----
From: "Murray Crane" <mcrane at longbridge.com>
To: <esa-l at spconnect.com>
Sent: Tuesday, June 12, 2001 9:50 PM
Subject: Re: [Esa-l]procmail log
> John (et. al.),
> Further to this, anyone have any idea what facility name is used by
procmail to do the logging?
> I keep having to reboot our sanitizer box because [particularly] the
procmail log grows hugely quickly. I am now having to rotate the procmail
log daily, only keep a single
> previous log and am having to compress all the logs on this machine. It
would be nice to foist it off to another machine (like our central logging
server) where it can be dealt with
> Murray Crane
> Longbridge International Plc
> On Sat, 9 Jun 2001 12:33:29 +0200, Nedudgi wrote:
> >I set up one log file (/var/log/procmail) for all users, but it
> >would be even better to have ONLY the poisoned (or at least the
> >name-mangled) messages logged into this file.
> >Instead of that now it lists each and every mail processed through
> >my server - even the ones with no attachments.
> >Is it possible to set procmail work the way I'd like to have?
> >E-mail Security Announce list mailing list
> >E-mail Security Announce list at spconnect.com
> E-mail Security Announce list mailing list
> E-mail Security Announce list at spconnect.com
More information about the esd-l