Date: Wed, 18 Jul 2007 10:28:12 -0500 From: "Daniel Anson" <danson@rackspace.com> To: "Michael Williams" <gberz3@gmail.com>, <freebsd-stable@freebsd.org> Subject: RE: Properly managing SpamAssassin. . . Message-ID: <96AF20FDF4301D419B33CCE8E3A0132B01CA7456@SAT4MX07.RACKSPACE.CORP> In-Reply-To: <AFC412B5-2BA3-4ABA-A9F9-F30F4F83BF23@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
You can buy a spamassasin liscense from plesk. I would suggest that. Daniel -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Michael Williams Sent: Wednesday, July 18, 2007 10: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 =20 wreaked havoc on the server. In the short term, we need to keep =20 Plesk around for those that need the "ease of use". However, it =20 wants to keep resetting values, etc; meaning that since the Plesk =20 license doesn't support "SpamAssassin" it won't allow us to use it =20 and wants it to remain that way. If push comes to shove, I *will* =20 blast Plesk. That said, I need to figure out the proper way to =20 enable SpamAssassin and have Qscan work properly, circumventing the =20 Plesk activites and licensing limitations. Does anyone have any =20 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?96AF20FDF4301D419B33CCE8E3A0132B01CA7456>