Re: ISPDirector. A rewrite of ISPMan
"Atif Ghaffar" <[email protected]> Sat, 12 Jan 2008 00:14:45 +0100
| Newsgroups | gmane.comp.isp.ispman.user |
|---|---|
| Message-ID | <[email protected]> |
--===============1666146992== Content-Type: multipart/alternative; boundary="----=_Part_3543_24499975.1200093285825" ------=_Part_3543_24499975.1200093285825 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello Ignacio, Sorry for the late reply. I have been awfully busy lately. On Jan 9, 2008 11:57 AM, Ignacio Garcia <[email protected]> wrote: > > Well, it looks interesting. I have several servers with ISPMan for which > I had the impression that they would eventually die of old age in the > near future since there has not been too much activity for the project > in recent times. It's great to see that good projects never die (or if > they do, they reincarnate to new ones :) > Well the thing about not so much activity is that if its working, why tinker with it :-) But yes, ISPMan is showing its age and its time for a re-injection. > > Talking about ISPMan and ISPdirector, I must say I'm quite happy with > ISPMan (I've been using it for almost 4 years now). For ISPdirector, may > I offer some suggestions? Ofcoarse, that was the goal of the early news. > > > - - Improve the isp's customer interface (this is where ISPMan lacks > behind so much) > Yes. I plan to do that. I am going with the one-interface for all aproach so we dont have to manage many different interfaces. At the same time, I am making everything accessible programatically so if someone want to put another interface GTK/QT/Windows, whatever, it should be possible. > > - - Keep installation/deployment simple, as ISPMan Again, yes, I want it to just run out of the box (or perhaps in the box, I might make vmware images, hardware appliance and perhaps a hosted version) I want to do think by keeping the provisioning part separate. For example the provisioning interface just tells a server (You must make a mailbox). How the server does that can be up-to-the server. Ofcoarse I will provide a reference implementation but the users are free to ignore it or replace it. ISPMan was basically just that. A central place which gives orders to other servers. Imagine this. There is an ispdirector implementation at xyz.ispdirector.net. You configure it to define what servers you have and what they do. Now you can manage every thing from the web-interface (create mailboxes, create users, create domains, etc). The real servers just have to connect from time to time to the ispdirector and ask Server: "Hi my name is dns01. Can I do something now?" and ispdirector might say ISPDirector: "Yes, here are the new domains, please add them to your zonefiles" or Server: "Hi. my name is mailhost0304. Can I do something now?" ISPDirector: "Yes, create user [email protected]" > (other solutions, i.e. > ISPconfig, require locked settings, like installation of their > own/modified apache, spamassassin, etc). What I like of ISPMan is that I > use the services that come with my choice of OS/Distribution and ISPMan > only interoperates with them. As I said, I will provide with a reference implementation (use this smtp server, this mailserver, this webserver, etc. The rest is all changeable) > > > - - Make customer interface modifiable by isp settings or checkboxes (i.e. > ~ I don't want customer x to be able to view/change any antispam or > vhosts settings, so I disable them) Ok. Will keep that in mind. Perhaps an ACL system should be in place. > > If it's as solid as ISPMan has been for me, I will certainly wait for > ISPdirector before considering any other options. It should be as solid or more. And definitively more easier. > > > One question , will it be possible to upgrade from ISPMan to ISPDirector > in any way? > Yes. 95% sure. With a script. best regards. ------=_Part_3543_24499975.1200093285825 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello Ignacio,<br><br>Sorry for the late reply. I have been awfully busy lately.<br><br><div class="gmail_quote">On Jan 9, 2008 11:57 AM, Ignacio Garcia <<a href="mailto:[email protected]">[email protected]</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br>Well, it looks interesting. I have several servers with ISPMan for which<br>I had the impression that they would eventually die of old age in the<br>near future since there has not been too much activity for the project <br>in recent times. It's great to see that good projects never die (or if<br>they do, they reincarnate to new ones :)<br></blockquote><div><br>Well the thing about not so much activity is that if its working, why tinker with it :-) <br>But yes, ISPMan is showing its age and its time for a re-injection.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Talking about ISPMan and ISPdirector, I must say I'm quite happy with <br>ISPMan (I've been using it for almost 4 years now). For ISPdirector, may<br>I offer some suggestions?</blockquote><div><br>Ofcoarse, that was the goal of the early news.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br><br>- - Improve the isp's customer interface (this is where ISPMan lacks<br>behind so much)<br></blockquote><div><br>Yes. I plan to do that. I am going with the one-interface for all aproach so we dont have to manage many different interfaces. At the same time, I am making everything accessible programatically so if someone want to put another interface GTK/QT/Windows, whatever, it should be possible. <br><br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>- - Keep installation/deployment simple, as ISPMan</blockquote><div><br> Again, yes, I want it to just run out of the box (or perhaps in the box, I might make vmware images, hardware appliance and perhaps a hosted version)<br><br>I want to do think by keeping the provisioning part separate. For example the provisioning interface just tells a server (You must make a mailbox). <br><br>How the server does that can be up-to-the server. <br>Ofcoarse I will provide a reference implementation but the users are free to ignore it or replace it.<br><br>ISPMan was basically just that. A central place which gives orders to other servers. <br>Imagine this.<br><br>There is an ispdirector implementation at <br><a href="http://xyz.ispdirector.net">xyz.ispdirector.net</a>. You configure it to define what servers you have and what they do.<br>Now you can manage every thing from the web-interface (create mailboxes, create users, create domains, etc). <br><br>The real servers just have to connect from time to time to the ispdirector and ask<br>Server: "Hi my name is dns01. Can I do something now?"<br>and ispdirector might say<br>ISPDirector: "Yes, here are the new domains, please add them to your zonefiles" <br><br>or<br>Server: "Hi. my name is mailhost0304. Can I do something now?"<br>ISPDirector: "Yes, create user <a href="mailto:[email protected]">[email protected]</a>"<br><br><br><br><br> </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> (other solutions, i.e.<br>ISPconfig, require locked settings, like installation of their<br> own/modified apache, spamassassin, etc). What I like of ISPMan is that I<br>use the services that come with my choice of OS/Distribution and ISPMan<br>only interoperates with them.</blockquote><div><br>As I said, I will provide with a reference implementation (use this smtp server, this mailserver, this webserver, etc. The rest is all changeable) <br><br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>- - Make customer interface modifiable by isp settings or checkboxes ( i.e.<br>~ I don't want customer x to be able to view/change any antispam or<br>vhosts settings, so I disable them)</blockquote><div><br>Ok. Will keep that in mind. <br>Perhaps an ACL system should be in place.<br><br> <br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>If it's as solid as ISPMan has been for me, I will certainly wait for <br>ISPdirector before considering any other options.</blockquote><div><br>It should be as solid or more. And definitively more easier.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br><br>One question , will it be possible to upgrade from ISPMan to ISPDirector<br>in any way?<br></blockquote><div><br>Yes. 95% sure. With a script.<br><br>best regards.<br><br></div></div> ------=_Part_3543_24499975.1200093285825-- --===============1666146992== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace --===============1666146992== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ispman-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ispman-users --===============1666146992==--