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
Thanks, but there are two issues there: 1) I don't plan on keeping Plesk for more than a few months, and don't want to spend the effort/money just to undo/redo it later. 2) I want to manage it manually 100% from the start That said, are there any suggestions as to how to accomplish what I've requested? Regards, Michael On Jul 18, 2007, at 11:28 AM, Daniel Anson wrote:> 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 > 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"
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 > >
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 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"
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
On Wed, 18 Jul 2007 11:05:25 -0400 Michael Williams <gberz3@gmail.com> wrote:> Hi All, > > I'm looking for a way to properly manage SpamAssassin after Plesk has > wreaked havoc on the server.Hi Michael, i think this thread doesnt belong in stable@, but questions@ - i dont see how this refers to one particular version of freebsd in particular. > 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?Caveat : I only suffer plesk in Linux, but the issues are very similar. I dont know of any way to bypass the licensing limitations... i strongly suggest if you walked into those you simply get rid of plesk now. I am not sure for SA, but there is a version of qscan that supports passing the email to Clamav: http://www.hostbird.com/beta/index.php?loc=0602-0602 Maybe there is something out there to support SA? Or simply configure qmail to support SA - you wont get an interface to manage SA from plesk, but you aren't missing much, IMHO - most of our users dont care about custom spam/ham , but rely on the system wide bayes list. (qmail is another reason to move away from plesk, imho... :( ) _________________________ {Beto|Norberto|Numard} Meijome "Liberty is not a means to a higher political end. It is itself the highest political end... liberty is the only object which benefits all alike, and provokes no sincere opposition... The danger is not that a particular class is unfit to to govern. Every class is unfit to govern... Power tends to corrupt, and absolute power corrupts absolutely." Lord Acton I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.