From owner-freebsd-stable@FreeBSD.ORG Wed Jul 18 15:38:40 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 454DD16A404 for ; Wed, 18 Jul 2007 15:38:40 +0000 (UTC) (envelope-from gberz3@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.237]) by mx1.freebsd.org (Postfix) with ESMTP id F1F4813C47E for ; Wed, 18 Jul 2007 15:38:39 +0000 (UTC) (envelope-from gberz3@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so204102wxd for ; Wed, 18 Jul 2007 08:38:39 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=sSaolJBSeni4KgJPi158K3PXruweuIqZDxZt+bDSyjXtmTaSCxVwHQEDMSz7GRWscQXFB3tjbmFPax61ZqyI0LwzKM1sgdSoT/djb/jAs5aeezxTzlvFi9+8DXdZiTHqQLLBqqGr43mfTgv+Vn4cyfBy++ngy99JksnRngnfcdg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=D1BWNyhm/oypE5JwVd6skwr1Xu6jQAJRyD2WH/cl/v9jyiXTJVaEohiKRnLdPLhM/cI41EBkLfVknuA9s67lRWGVx+7fSmJsqeYraEOHsJ2bxaLrXmEO5m7n6SUNh4J0dp955uaHwGb41+J0n8QtBVnSmZ4LTeL5UjYgSiXFqzQ= Received: by 10.90.51.17 with SMTP id y17mr1632380agy.1184773118959; Wed, 18 Jul 2007 08:38:38 -0700 (PDT) Received: from ?192.168.1.115? ( [74.140.142.75]) by mx.google.com with ESMTPS id r15sm463415nza.2007.07.18.08.38.35 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 18 Jul 2007 08:38:35 -0700 (PDT) In-Reply-To: <001b01c7c951$14217760$3c646620$@ca> References: <20070718120014.4F48916A418@hub.freebsd.org> <001b01c7c951$14217760$3c646620$@ca> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Michael Williams Date: Wed, 18 Jul 2007 11:38:34 -0400 To: "Kevin K." X-Mailer: Apple Mail (2.752.2) Cc: freebsd-stable@freebsd.org Subject: Re: Properly managing SpamAssassin. . . X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jul 2007 15:38:40 -0000 Kevin, Thanks. I have no problem with that at all. Can you recommend any quality, modular (redundant I know) jailing techniques (e.g. directory structures, user levels, permissions, etc)? Regards, Michael On Jul 18, 2007, at 11:34 AM, Kevin K. wrote: > 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 > >