Feature Idea: MailScanner process name

[Lewis Bergman]

    [ The following text is in the "ISO-8859-1" character set. ]
    [ Your display is set for the "US-ASCII" character set.  ]
    [ Some characters may be displayed incorrectly. ]

Jeff A. Earickson wrote:
> I take the contrary point of view -- I log everything for all processes
> (sendmail, MailScanner, popper, etc) into one file.  All facilities
> and loglevels from syslogd.conf point to the same file.  Yes the
> file is gigantic on my mail server (about 100 MB/day, rotated daily),
> but everything is in one place waiting for grep to reveal what I want.  
> What happened to a mail message?  Grep for the msgid and see
> both sendmail and MailScanner actions.  Want to know about a user?
> Grep for userid to see sendmail, MailScanner, and POP actions.  Easy.
> Behold the power of grep.
> 
Yea, I use remote syslogging to do the same thing but from all my 
servers. I log everything to individual files on the server and then all 
logs are sent to the remote syslog. That way, I can track that userid 
across several MX's, into the mailhub, down into his account, and back 
out via dovecot.

I just like to see them broken down on the server so if I am looking for 
trends on a program they are easier to spot. Sometimes grep hides things 
that you asked it to but didn't really mean to.

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the Wiki (http://wiki.mailscanner.info/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).

Support MailScanner development - buy the book off the website!