Re: [Dovecot] SASL using different auth database?

2007-05-12 Thread Dave McGuire
On May 11, 2007, at 11:50 AM, Timo Sirainen wrote: If you can assign two IPs to the server, one for SMTP, and one for POP/IMAP, and you can use a SQL backend, you could craft your db schema and queries to pull the appropriate password based on the local IP of the connection. I know this isn't

Re: [Dovecot] SASL using different auth database?

2007-05-11 Thread Timo Sirainen
On Thu, 2007-05-10 at 20:57 -0400, Dave McGuire wrote: The goal here is to allow users to have different passwords for SMTP authentication and POP/IMAP connections. I am converting an existing installation to Dovecot...this installation currently has quite a few users who are

Re: [Dovecot] SASL using different auth database?

2007-05-11 Thread Timo Sirainen
On Fri, 2007-05-11 at 11:39 -0400, Justin McAleer wrote: If you can assign two IPs to the server, one for SMTP, and one for POP/IMAP, and you can use a SQL backend, you could craft your db schema and queries to pull the appropriate password based on the local IP of the connection. I know

Re: [Dovecot] SASL using different auth database?

2007-05-11 Thread Justin McAleer
Timo Sirainen wrote: On Fri, 2007-05-11 at 11:39 -0400, Justin McAleer wrote: If you can assign two IPs to the server, one for SMTP, and one for POP/IMAP, and you can use a SQL backend, you could craft your db schema and queries to pull the appropriate password based on the local IP of the

Re: [Dovecot] SASL using different auth database?

2007-05-11 Thread Justin McAleer
Timo Sirainen wrote: On Thu, 2007-05-10 at 20:57 -0400, Dave McGuire wrote: The goal here is to allow users to have different passwords for SMTP authentication and POP/IMAP connections. I am converting an existing installation to Dovecot...this installation currently has quite a few

[Dovecot] SASL using different auth database?

2007-05-10 Thread Dave McGuire
Hi folks. Is it possible to configure Dovecot to authenticate against one mechanism (i.e., /etc/passwd) for POP/IMAP connections, while providing a SASL authentication socket that satisfies authentication requests against a different mechanism, say MySQL? The goal here is to allow