Date: Wed, 09 Dec 2009 23:45:47 +0200 From: Joel Jans <joel.jans@eenet.ee> To: "Kahlil Erwin S. Talledo" <kstalledo@binarysalad.com> Cc: Bob Martin <bob@buckhorn.net>, "Michael W. Lucas" <mwlucas@blackhelicopters.org>, isp@freebsd.org Subject: Re: ispCP or alternative? Message-ID: <4B201A8B.2000507@eenet.ee> In-Reply-To: <05F5E6D8-CCA7-4CD1-BCA5-EA99FBE0D01B@binarysalad.com> References: <20091209144510.GA89359@bewilderbeast.blackhelicopters.org> <c32604580912090918ib3b4247t3c2141a29cdd9e49@mail.gmail.com> <05F5E6D8-CCA7-4CD1-BCA5-EA99FBE0D01B@binarysalad.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >> ucas >> <mwlucas@blackhelicopters.org> wrote: >> >>> Hi, >>> >>> I'm in need of a general "control panel" solution for an ISP. I'm >>> considering ispCP, but there appear to be several minor annoyances >>> with getting it to run on FreeBSD. Other options include dtc >>> (/usr/ports/sysutils/dtc), CPanel, etc. It appears that there's many >>> pieces of software that work only on very specific FreeBSD revs, some >>> that don't seem to have been used for several years, etc. >>> >>> Ideally, I'd have a piece of software with three levels of access: >>> admin level where our support staff could provision new domains, a >>> customer admin who could add and remove customer email accounts and >>> Web server access, and end-user access to their own email, forwarding, >>> etc. >>> >>> What are you folks using successfully? Or, what have you tried to use >>> and wish you hadn't? >>> Try Syscp, /usr/ports/sysutils/syscp, http://www.syscp.org/ JJ
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B201A8B.2000507>