From owner-freebsd-stable@FreeBSD.ORG Wed Jul 18 16:24:47 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 4644016A403 for ; Wed, 18 Jul 2007 16:24:47 +0000 (UTC) (envelope-from freebsd-stable@magma.ca) Received: from smtp-06.primus.ca (mail5.primus.ca [216.254.141.172]) by mx1.freebsd.org (Postfix) with ESMTP id E2C2F13C494 for ; Wed, 18 Jul 2007 16:24:46 +0000 (UTC) (envelope-from freebsd-stable@magma.ca) Received: from ottawa-hs-209-217-66-243.d-ip.magma.ca ([209.217.66.243] helo=kevin) by smtp-06.primus.ca with esmtpa (Exim 4.43) id 1IBCKT-0002CF-Lg; Wed, 18 Jul 2007 12:24:46 -0400 From: "Kevin K." To: "'Michael Williams'" References: <20070718120014.4F48916A418@hub.freebsd.org> <001b01c7c951$14217760$3c646620$@ca> In-Reply-To: Date: Wed, 18 Jul 2007 12:24:39 -0400 Message-ID: <000001c7c958$25077820$6f166860$@ca> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcfJUcsUAEy8+/y9TL2MsYMyok/EqAABhUWw Content-Language: en-us X-Authenticated: freebsd-stable - ottawa-hs-209-217-66-243.d-ip.magma.ca (kevin) [209.217.66.243] 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 16:24:47 -0000 Creating a jail isn't that hard. Unfortunately I haven't really tested it before, but im sure that through some simple redirection of the separate virtual localhost adapters between jails, you may be able to utilize spamassassin. I guess the real question is, is it worth it to do all that work if you are going to just scrap plesk in a few months anyways? In any case, the freebsd handbook's section on jails is a good place to start. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html -----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:39 AM To: Kevin K. Cc: freebsd-stable@freebsd.org Subject: Re: Properly managing SpamAssassin. . . 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 > > _______________________________________________ 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