Yes. Jamie wrote a very clever bit of code to implement virus and spam filtering on a per-domain basis. Both SpamAssassin and ClamAV are installed during the installation process and are pre-configured for use by Virtualmin. As stated in the FAQ, this should Just Work.
We are also hoping to get some other AV and Spam products into the mix–the code is designed to be extensible in just this way–so as our third party developer program ramps up, we hope some AV and anti-Spam vendors will step in with some enhanced products in this space that integrate cleanly into the Virtualmin bundle. It’s also not unlikely that we’ll mix in some other OSS products in this space as we get feedback about what folks find useful in a large-scale hosting environment.
I mentioned it in another thread, but I’ll reiterate here: I’m releasing the installer to our sponsors tonight for some beta testing, and I expect to have Virtualmin Professional up for sale before the end of the week, so you’ll be able to give it a try yourself.
I’ve only configured AV and Spam filtering on either a “Global” or a “single user” basis, so far.
Virtualmin Professional supporting “per-domain” will greater improve the flexiblity of the solutions that we can offer to clients.
Joe, Thanks for your quick and very helpful reply!
Yes. Jamie wrote a very clever bit of code to implement virus and spam filtering on a per-domain basis. Both SpamAssassin and ClamAV are installed during the installation process and are pre-configured for use by Virtualmin. As stated in the FAQ, this should Just Work.
We are also hoping to get some other AV and Spam products into the mix–the code is designed to be extensible in just this way–so as our third party developer program ramps up, we hope some AV and anti-Spam vendors will step in with some enhanced products in this space that integrate cleanly into the Virtualmin bundle. It’s also not unlikely that we’ll mix in some other OSS products in this space as we get feedback about what folks find useful in a large-scale hosting environment.
I mentioned it in another thread, but I’ll reiterate here: I’m releasing the installer to our sponsors tonight for some beta testing, and I expect to have Virtualmin Professional up for sale before the end of the week, so you’ll be able to give it a try yourself.
Yes. Jamie wrote a very clever bit of code to implement virus and spam filtering on a per-domain basis. Both SpamAssassin and ClamAV are installed during the installation process and are pre-configured for use by Virtualmin. As stated in the FAQ, this should Just Work.
We are also hoping to get some other AV and Spam products into the mix–the code is designed to be extensible in just this way–so as our third party developer program ramps up, we hope some AV and anti-Spam vendors will step in with some enhanced products in this space that integrate cleanly into the Virtualmin bundle. It’s also not unlikely that we’ll mix in some other OSS products in this space as we get feedback about what folks find useful in a large-scale hosting environment.
I mentioned it in another thread, but I’ll reiterate here: I’m releasing the installer to our sponsors tonight for some beta testing, and I expect to have Virtualmin Professional up for sale before the end of the week, so you’ll be able to give it a try yourself.
Without seeing this feature (which I really look forward to seeing once it becomes available), I would like to ask what will happen to existing users of the very popular[A HRef="http://www.MailScanner.info/">MailScanner</A> package. [A HRef="http://www.MailScanner.info/">MailScanner</A> is an excellent free anti-virus and anti-spam filter, written by[A HRef="http://www.ecs.soton.ac.uk/people/jkf">Julian Field</A>. Similar to Webmin/Usermin/Virtualmin, it is also a set of perl scripts, and it integrates very nicely with both SpamAssassin and ClamAV (as well as almost every other anti-virus product).
I am currently using this configuration with the GPL Virtualmin and have been very happy with it. Will it be supported in Virtualmin Professional, or will it be necessary to migrate to the new internal filtering code?