Timo Sirainen wrote:

...

On Sep 1, 2009, at 5:02 AM, Tom Sommer wrote:

...

I enabled all debug and see the following:

Sep 01 10:49:18 auth(default): Info: client in: AUTH 10 DIGEST-MD5 service=pop3 lip=195.41.131.35 rip=111.111.111.111 lport=110 rport=3730 Sep 01 10:49:18 auth(default): Info: digest-md5(?,111.111.111.111): Invalid realm: example.com

Do you have example.com in auth_realms?

no, auth_realms and auth_default_realm are both undefined.

How do I populate auth_realms, when all my users are pulled from SQL? Forget it, I'm just gonna remove digest-md5 from the mech list - I

Tom Sommer wrote: figure that might fix my problem.

Thanks // Tom

Timo Sirainen wrote:

On Tue, 2009-09-01 at 17:02 +0200, Tom Sommer wrote:

...

...

...

Do you have example.com in auth_realms?

no, auth_realms and auth_default_realm are both undefined.

How do I populate auth_realms, when all my users are pulled from SQL?

Forget it, I'm just gonna remove digest-md5 from the mech list - I figure that might fix my problem.

Well, I think the auth_realm checking is pointless anyway. Removed it: http://hg.dovecot.org/dovecot-1.2/rev/3c171f5eee8d

Of course, unless you have passwords saved as plaintext it wouldn't have worked anyway.

Alright, well removing digest-md5 fixed the problem. I wonder if the auth_realm check was the cause of the hang, or maybe it's something else in the digest-md5 code.

In any case, thanks for the change - I'll do a test when 1.2.5 comes out.

Keep up the good work. // Tom