Dear Scott Heisler,
I found that the mailscanner-mrtg was very easy to install and I was incorrect. It is showing stats now and does appear to be working fine. It was well documented and pre-configured for RH Linux so I had to change almost nothing. From a stats point of view, the mailscanner-mrtg does seem to provide most of what I need to know. I just liked the graphs in mailwatch better.
a small howto post on mailscanner mrtg will enlighten all of us :). actually mailwatch has some good features apart from graphs in it like the quarantine management and retraining spam/ham misclassification.
Since I use Webmin for 95% of the day-to-day admin of my Linux servers, I
think that Webmin is the way to go for configuration. I'm never afraid to
work from the command line (and often DO). However, Webmin is a consistent
administration interface with support for hundreds of applications on Linux.
Having a Webmin module will also put you on their (webmin's) website, which
will further promote the use of Openprotect.
we will go with what people want then :).
Which brings me to another issue. Since OpenProtect uses spamassassin for ratings, is it ok to make changes to SpamAssassin using the Webmin interface for SpamAssassin?
I am going to repeat some of the clarifications about spamassassin:
MailScanner calls the function library Mail::Spamassassin directly from Perl, gives the message directly to the function library, and gets the results straight back from it.
SA user_prefs files in individual people's home directories are not consulted by MailScanner, as it doesn't know where the mail is going or how to map an email address onto a user's home dir. You can only do that for local email accounts and even then only at the delivery stage, which means MailScanner would have to be involved in mail delivery.
~/.spamassassin is consulted only for restricted values of ~. Specifically, ~ here refers to the home directory of the mail user (users like root, mail, smmsp, postfix, qmailq ...etc). ~ does not refer to each user on the machine.
SpamAssassin User State Dir
This is the directory where SpamAssassin should store its state information for things like the Bayes database. It avoids having them pile up somewhere unhelpful such as /root or /home/smmsp. Note that only one directory can be specified, therefore it does not apply for each user on the system; there is only one setting.
So what all the above means is that whatever changes you do to spamassassin config via webmin have no effect on the calling config of Mail::Spamassassin by openprotect.
cheers, Ganesh, KM. PS: itz 02:30 in the morning and i lost my flair for english grammar :) -- K.M.Ganesh | Mobile: +91 (0) 9444080290 Opencomputing Technologies | http://opencompt.com Server Side E-Mail Protection.
