On 2009-06-30, at 7:47 PM, Jake Vickers wrote:
Eric Shubert wrote:
Jake Vickers wrote:
Eric Shubert wrote:
John Hansen wrote:
Hi,
We currently authenticate our users with an LDAP server for
different systems
such as email and thin clients (LTSP). I would like to keep this
same set up
and not use a separate user database for QmailToaster, if
possible. Most of
our users use webmail, but there are around 20 that use an email
client with POP3.
Does anyone have a recommendation, one way or another, on using
QmailToaster
with LDAP?
Pro's and cons?
Tuturial?
Thanks,
John
I'm sure Jake will chime in on this with authority.
I'd like to say, though, that I think this is a big weakness in
the toaster presently, and I'd love to see us develop LDAP
capability for QMT. I don't believe that it's a simple thing to
do though, and I'd be thrilled to work with a sponsor to get it
implemented.
Not a weakness, a different path.
Vpopmail does not work with LDAP, and some of the other patches we
use will not work with qmail-ldap either.
There is a project that helps you set up a qmail-ldap server over
at qmail-ldap.org
Since they're completely different approaches, I don't think you
can really give any pros/cons besides what you get from LDAP
anyway (both pros and cons).
I beg to differ. QMT offers no common authentication mechanism that
can be shared with other applications in an organization. Seems
like most applications can authenticate with LDAP. Does anything
besides certain implementations of qmail use vpopmail
authentication? I don't know of any. With vpopmail, user and
password definitions are (un)necessarily separate from 'the rest of
the world'. I'd call that a weakness if I wanted to integrate it
with other applications in an organization. Let's face it, QMT is
weak in this area. Now, how important that might can vary with
depending on the circumstances.
As I stated before, they're separate paths, not "weakness".
Qmailtoaster is a Qmail path that utilizes vpopmail and mysql. If
you want to use LDAP, use qmail-ldap. If you want to use vpopmail
but not mysql, use either LWQ or qmailrocks, etc.
Qmail is only the backend. There are many paths you can take to
achieve your goals. If you want vpopmail and mysql in an easy to
install package, then Qmailtoaster is a good path for you.
As far as sharing common authentication mechanisms, that is a matter
of viewpoint. I've written PHP apps that used the vpopmail database
for authentication to tie the application to the email system. With
vpopmail being in mysql, you can use any mashup that can communicate
with mysql for authentication. If this does not work for a specific
app, then a different approach may be in order for your configuration.
I myself have written things to authenticate to my toaster, using the
PHP imap functions, however if I was trying to integrate with
something else premade, I am not so sure. I am not really adding
anything of value here, just pointing out another way to have an app
auth against the existing toaster systems.
Dustin
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
