I've got cyrus-imapd 2.2.8 setup to authenticate via a MySQL database.
I've enabled logging on the database while I'm setting things up, and
I've noticed that when I login, Cyrus runs the same query twice:
47 Connect [EMAIL PROTECTED] on RETRIX_TRANSITION
47 Query START TRANSACTI
--
From: "Patrick Gibson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 28, 2004 11:28 AM
Subject: Redundant database query?
> I've got cyrus-imapd 2.2.8 setup to authenticate via a MySQL database.
> I've enabled logging on the database whi
Patrick Gibson wrote:
I've got cyrus-imapd 2.2.8 setup to authenticate via a MySQL database.
I've enabled logging on the database while I'm setting things up, and
I've noticed that when I login, Cyrus runs the same query twice:
47 Connect [EMAIL PROTECTED] on RETRIX_TRANSITION
47 Query
Hi Ken,
Here is my configuration in imapd.conf:
sasl_sql_hostnames: localhost
sasl_sql_user: cyrus
sasl_sql_passwd: ***
sasl_sql_database: RETRIX_TRANSITION
sasl_sql_statement: select PASSWORD from USER_ACCOUNTS where
USERNAME='%u'
This seems to be consistent with many of the examples I've fo
Patrick Gibson wrote:
Hi Ken,
Here is my configuration in imapd.conf:
sasl_sql_hostnames: localhost
sasl_sql_user: cyrus
sasl_sql_passwd: ***
sasl_sql_database: RETRIX_TRANSITION
sasl_sql_statement: select PASSWORD from USER_ACCOUNTS where USERNAME='%u'
This seems to be consistent with many of
On 28-Oct-04, at 4:59 PM, Ken Murchison wrote:
sasl_sql_statement: select PASSWORD from USER_ACCOUNTS where
USERNAME='%u'
You won't get rid of the second query for any of the SASL mechanisms.
The only thing you can do is keep it from selecting the *same* column
twice.
Hi Ken,
I'm not sure I get
Patrick Gibson wrote:
On 28-Oct-04, at 4:59 PM, Ken Murchison wrote:
sasl_sql_statement: select PASSWORD from USER_ACCOUNTS where
USERNAME='%u'
You won't get rid of the second query for any of the SASL mechanisms.
The only thing you can do is keep it from selecting the *same* column
twice.
Hi
On 29-Oct-04, at 11:44 AM, Ken Murchison wrote:
I'm not sure I get what you mean by selecting the same column twice
-- unless I'm mistaken, the query selects the PASSWORD column just
once.
From the log that you posted, it looks like its selecting PASSWORD
twice for user 'patrick'. Am I incorrec
Patrick Gibson wrote:
I'm pretty new to SASL, so this business of old and new secrets is a bit
foreign to me. Given that this is a fresh setup, is there a way for me
to force the server to assume that all old secrets have been upgraded to
the new? Is this what the "sasl_auto_transition" option i
On 29-Oct-04, at 5:50 PM, Ken Murchison wrote:
Patrick Gibson wrote:
I'm pretty new to SASL, so this business of old and new secrets is a
bit foreign to me. Given that this is a fresh setup, is there a way
for me to force the server to assume that all old secrets have been
upgraded to the new? I
Patrick Gibson wrote:
On 29-Oct-04, at 5:50 PM, Ken Murchison wrote:
Patrick Gibson wrote:
I'm pretty new to SASL, so this business of old and new secrets is a
bit foreign to me. Given that this is a fresh setup, is there a way
for me to force the server to assume that all old secrets have been
11 matches
Mail list logo
