Date: Wed, 18 Jul 2007 11:34:04 -0400 From: "Kevin K." <freebsd-stable@magma.ca> To: "'Michael Williams'" <gberz3@gmail.com>, <freebsd-stable@freebsd.org> Subject: RE: Properly managing SpamAssassin. . . Message-ID: <001b01c7c951$14217760$3c646620$@ca> In-Reply-To: <AFC412B5-2BA3-4ABA-A9F9-F30F4F83BF23@gmail.com> References: <20070718120014.4F48916A418@hub.freebsd.org> <AFC412B5-2BA3-4ABA-A9F9-F30F4F83BF23@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Managing plesk usually means that you really have to hand over your server (or the jail that plesk creates) to plesk itself. I've hacked and mangled plesk installations in order to merge other technologies and custom solutions that I personally preferred -- and in the end I concluded that it caused more headaches than it was worth. As of plesk 8.1 I believe it creates its installation in a jailed environment, so perhaps adding another jail to handle all the services you don't want to purchase through plesk (i.e. spamassassin, clamav, or whatever elese there is) may be the best way. That's my 0.2, perhaps someone else has a better solution though. Again, changing or hacking a plesk installation is not a good idea, considering their "windows update" style of submitting upgrades and patches. Hope it helps. -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Michael Williams Sent: Wednesday, July 18, 2007 11:05 AM To: freebsd-stable@freebsd.org Subject: Properly managing SpamAssassin. . . Hi All, I'm looking for a way to properly manage SpamAssassin after Plesk has wreaked havoc on the server. In the short term, we need to keep Plesk around for those that need the "ease of use". However, it wants to keep resetting values, etc; meaning that since the Plesk license doesn't support "SpamAssassin" it won't allow us to use it and wants it to remain that way. If push comes to shove, I *will* blast Plesk. That said, I need to figure out the proper way to enable SpamAssassin and have Qscan work properly, circumventing the Plesk activites and licensing limitations. Does anyone have any quality insight into the most up-to-date means for accomplishing this? Regards, Michael _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" __________ NOD32 2404 (20070717) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001b01c7c951$14217760$3c646620$>