[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] JS_KAKWORM.A virus [LONG]
- Subject: RE: [cobalt-users] JS_KAKWORM.A virus [LONG]
- From: "Colin J. Raven" <cjraven@xxxxxxxxxxx>
- Date: Thu Aug 23 19:26:02 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> On Thu, 23 Aug 2001 18:14:29 -0400, Colin J. Raven mumbled something
> like:
> >>VERBOSE=ON #turn this to VERBOSE=OFF only when you are satisfied
> >>that stuff
> >>is being flushed properly
>
> Even with verbose=off in my procmailrc, I'm still getting a log of
> every email that gets checked (which is every email that goes through
> the machine). Is it the logabstract line that is doing this? Should I
> comment it out?
> SHELL=/bin/sh
> LOGFILE=/home/log/procmaillog
> #changed to /home/log/procmaillog to avoid filling up /var partition
> LOGABSTRACT=ALL
> VERBOSE=OFF
Well yes, there will be an "abstract" or "abbreviated" log of all incoming
mail if LOGABSTACT is set to "ALL". The exception is outgoing mail of
course, which isn't logged at all.
Another approach could be to LOGABSTRACT only those recipes you are
interested in seeing, or define a per-recipe log which is inefficient in
CPU's and downright uggerly to look at in the .procmailrc or
/etc/procmailrc.
Comment it out and you'll get a silent logfile when verbose is off.
Unfortunately you'll have no record of *anything* that happened (good OR
bad)
Personally unless I'm debugging something, I leave logabstract set and and
rotate the logfile. Unless you have ***thousands*** of users on one box, an
abstract log isn't that big. Nowhere near httpd logs for example.
Groetjes,
-Colin
--
Colin J. Raven