On Fri, Aug 04, 2000 at 11:39:51AM +0200, Joaquin Ferrero wrote:
I have 200.000 users. The most part only have email service. The file
/etc/passwd es very, very long... but es necessary for IMAP server to
check the home directory for every user.
i'm surprised you get that many users in a
On Fri, Aug 04, 2000 at 11:39:51AM +0200, Joaquin Ferrero wrote:
I have 200.000 users. The most part only have email service. The file
/etc/passwd es very, very long... but es necessary for IMAP server to
check the home directory for every user.
i'm surprised you get that many users in a
-Mensaje original-
De: Jeremy C. Reed [mailto:[EMAIL PROTECTED]]
Enviado el: viernes, 04 de agosto de 2000 19:38
Para: Joaquin Ferrero
CC: [EMAIL PROTECTED]
Asunto: Re: very long passwd
On Fri, 4 Aug 2000, Joaquin Ferrero wrote:
I have 200.000 users. The most part only have
-Mensaje original-
De: Jeremy C. Reed [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 04 de agosto de 2000 19:38
Para: Joaquin Ferrero
CC: debian-isp@lists.debian.org
Asunto: Re: very long passwd
On Fri, 4 Aug 2000, Joaquin Ferrero wrote:
I have 200.000 users. The most part only
-Mensaje original-
De: Alberto [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 04 de agosto de 2000 22:22
Para: Joaquin Ferrero; debian-isp@lists.debian.org
Asunto: Re: very long passwd
Just add a wrapper before procesing any incoming mail which auth on mysql.
---
Antes de pasar el
What databases? What is the name of debian package?
libpam-pwdb
authentication is ok with pam_mysql. The problem is that IMAP server need
the home dir location.
thats what you need nss for. it can authenticate not only passwords
against varoius services
The file /etc/passwd es very, very long... but es necessary for IMAP server
to check the home directory for every user.
nss_mysql is the only solution?
nope.
Now, I have mysql to auth users for proftpd apache via PAM (pam_mysql)
there is also ldap, pg_sql and, probably what you want -
On Fri, 4 Aug 2000, Joaquin Ferrero wrote:
I have 200.000 users. The most part only have email service.
Are they for different domains? If so, you could use different password
files for each domain. (This is what I do.) And you can also use databases
(instead of flat-text) for the
Just add a wrapper before procesing any incoming mail which auth on mysql.
---
Antes de pasar el mail al delivery añade un nivel de chequeo via wrapper
(ahora que lo pienso puedes hacerlo tb añadiendolo como status de retorno
de una regla que definas) y que sea quien autentifique en el
On Fri, Aug 04, 2000 at 11:40:11AM +0200, Joaquin Ferrero wrote:
I have 200.000 users. The most part only have email service.
The file /etc/passwd es very, very long... but es necessary for IMAP server
to check the home directory for every user.
nss_mysql is the only solution?
Now, I
The file /etc/passwd es very, very long... but es necessary for IMAP server
to check the home directory for every user.
nss_mysql is the only solution?
nope.
Now, I have mysql to auth users for proftpd apache via PAM (pam_mysql)
there is also ldap, pg_sql and, probably what you want -
On Fri, 4 Aug 2000, Joaquin Ferrero wrote:
I have 200.000 users. The most part only have email service.
Are they for different domains? If so, you could use different password
files for each domain. (This is what I do.) And you can also use databases
(instead of flat-text) for the
Just add a wrapper before procesing any incoming mail which auth on mysql.
---
Antes de pasar el mail al delivery añade un nivel de chequeo via wrapper
(ahora que lo pienso puedes hacerlo tb añadiendolo como status de retorno
de una regla que definas) y que sea quien autentifique en el mysql.
On Fri, Aug 04, 2000 at 11:40:11AM +0200, Joaquin Ferrero wrote:
I have 200.000 users. The most part only have email service.
The file /etc/passwd es very, very long... but es necessary for IMAP server
to check the home directory for every user.
nss_mysql is the only solution?
Now, I have
14 matches
Mail list logo
