Re: ispman-HEAD tasks cleanup

Paul Wolstenholme <[email protected]>
Newsgroups gmane.comp.isp.ispman.devel
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Jan 5, 2005, at 10:48 AM, Wim Kerkhoff wrote:

> Paul Wolstenholme wrote:
>
>> I'm quite new to ispman. I've only been using it for a few months. 
>> The  one major change I've made to my installation revolves around 
>> using  cyrus virtual domains. With this setup, the uid is the same as 
>> their  email address. The changes were not difficult to implement -- 
>> most of  the changes were to ldap templates, control panel, and the 
>> creation of  user directories. If people are interested, I do not 
>> believe it would  be difficult to implement this feature in a way 
>> which would be  compatible with the old model.
>
> Any idea what would be involved in migrating from uid's of the format 
> user_domain_told to [email protected]? Currently I have both in LDAP so 
> that users can authenticate either way through 
> PAM/Perdition/SMTP/SSH/etc, except for Sieve - which is requiring 
> user_domain_tld as per the mailboxes.

Most of the changes can be made to the templates in ispman/templates. 
The domain control panel one example where the scripts need to be 
changed a bit. Basically, I just looked for cases where the uid is 
merged with the domain.

>
>>
>> There are a couple other ideas I have been thinking of lately as 
>> well.  I have been contemplating setting up a box that uses DAV 
>> instead of FTP  for file transfers. Has anyone done this with ispman? 
>> I don't think it  would be too hard to implement:
>>
> Sounds interesting... I haven't seen too many webmasters looking for 
> DAV yet though - most people are stuck in the 'old' way of doing 
> things.

Most operating systems have support along with the big web dev suites. 
I think it should cut down on tech support (eg firewall problems). It 
may be a bit more secure (especially if used over ssl).


>
>>
>> I'm also running both apache 1.3 and 2.0 boxes. I'm only using ispman 
>>  with the 2.0 boxes now because they require a different module for 
>> ldap  authentication. It would be great if ispman could handle a 
>> mixed  environment (or maybe it can and I'm just to thick to figure 
>> it out).
>
> I have HTTP authentication against LDAP working fine with Apache 1.3. 
> The relevant portion from vhosts.conf.template:
>
>    <Directory /ispman/analog/$servername>
>        $ispmanVhostDocumentRootOption
>        AuthName "Analog WebStats for $servername"
>        AuthType Basic
>        AuthLDAPURL ldap://$ldapHost/$ldapBaseDN?uid
>        require valid-user 
> ou=users,ispmanDomain=$ispmanDomain,$ldapBaseDN
>    </Directory>
>

The block is slightly different for the module I'm using for apache2. I 
guess I'm just thinking that it would be good to be able to specify a 
different template depending on the authentication module installed on 
that box.


> Wim
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Ispman-developers mailing list
> Ispman-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/ispman-developers
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFB3yt14vygjarL2QkRAhoRAJ0a7JOHMWFo9YyDWN5otLUuS0lkXQCdFNNV
4dB8RVk0Sp6oGesqCyA8ofY=
=uM8T
-----END PGP SIGNATURE-----



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.