On 10/01/2011 09:48 PM, Casey wrote:
I know that qmailtoaster comes with mrtg integrated in to allow for
graphs and stats of various aspects of server monitoring...
The thing is, on my Debian server I setup awhile back before I began
using CentOS and Qmailtoaster, I have mailgraph setup. It uses RRD and
creates a set of graphs like MRTG, but its simple and basically
displays
2 sets of graphs - one that shows sent/received messages & and another
that shows bounced, viruses, spam, and rejected on a separate
graph. It
then breaks it down by day, week, month, and year like MRTG does. Has
anyone tried using mailgraph with qmail/qmailtoaster?
Not me. You might want to search the list archives for mailgraph to
see if it has come up.
Does anyone know of any other available open-source monitoring tools?
I've used Cacti and MRTG quite a bit, and my true goal here is to set
something up on my gateway servers so I can track the kinda of mail
traffic that is reaching the servers, how much is getting passed from
the gateways into the main mail servers, and then a breakdown of spam,
virus, clean mail. Any recommendations?
I'd like to see you take a little bit different approach to this, if
you don't mind.
Having just converted, I'm wondering if you've installed spamdyke yet
or not. Spamdyke will be stock with QMTv2, but you need to install it
yourself for QMTv1.3. Everything you need to get going with spamdyke
is found at http://qtp.qmailtoaster.com/. You _will_ want to run
spamdyke.
Now, there are a few scripts floating around which report various
filtering statistics (see this and spamdyke list archives), none of
which that I know of has (yet) been incorporated into QMT's graphical
display of statistics (which would be nice). In any case, I think
you'll perhaps want a few more than the 4 categories that your
mailgraph shows, based off various spamdyke filter counts.
Are you thinking of using mailgraph and rrdtool in place of mrtg, or
running them both? Is this an enhancement that could just as well be
made to qmailmrtg-toaster?
Also, I think you'll probably want to reconsider your gateway/mail
server roles, in light of spamdyke. You see, spamdyke is only
effective when it's running at the perimeter, connected directly
(conducting the smtp session) with the sending server. Having a
gateway which processes the smtp session destroys spamdyke's
effectiveness. Given though that spamdyke is more effective at
blocking spam than most email gateways (commercial or otherwise),
having your email bypass any email gateway processing makes sense.
Plus, spamdyke rejects spam (80+% of it I'd say) without having to
even receive it, which means much less mail to scan. Spamdyke
significantly reduces the load on your email server.
I know it sounds like spamdyke is too good to be true, but it is
truely magical. To be honest, if I had to pick between running only
spamdyke or only spamassassin, I'd choose spamdyke, hands down. No
need to choose though, as they do well together. :)
Here is a link to the setup on my personal server at home:
http://www.caseyjprice.com/cgi-bin/mailgraph.cgi
Thanks,
--
Casey
Smile Global Technical Support
Submit or check trouble tickets http://billing.smileglobal.com
www.smileglobal.com <http://www.smileglobal.com>
