I was also reading the logs when the first time I am install QMT
but after a year pass, and I get the big picture how QMT working and no
more tweaking needed,
the server stable enough, I leave it alone, never upgrade the SA,
clamav, and other packages
never check the logs, SA bayes, clamav ext dat
until my boss complain, he said
"it seems now I have more spam, can you please check it"
Now I need to refresh a little bit, by using Jake QMT Video and manual I
made
things do get rusty if you not using them :D
David Milholen wrote:
I thought I was the only one who read the logs before breakfast:)
Man, I need a vacation..
Jake Vickers wrote:
Phil Leinhauser wrote:
Just curiously Jake, how often do you really find yourself reading
that 1M log file you get every day?
I've been there and found they get auto sorted into a "Logs" folder
only to be deleted (still unread) when Outlook slows down.
Depends on the server. For servers that I run for other clients I at
least scroll down past the HTML log entries and look for "serious
entries" daily. For my non-client servers (like the qmailtoaster.com
server, or other servers that do not directly generate me revenue) I
scan them for major errors about once a week, maybe once every 2
weeks if "things are happening".
This nets me about 30 minutes of log file scanning a day with the
occasional investigation thrown in to make sure there's not a major
issue brewing. That's an average though, including those that I only
look at once a week.
I find that log files go good with the first couple cups of coffee.
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
