Login Failed - Resource id #25
rabel1 at austin.rr.com
Sun Oct 23 16:31:26 CEST 2005
Thank you for the response.
Turns out that the "auto_create_user" config option doesn't really mean
what I thought it meant. I suppose there's a certain argument to be had
to say that the config file description for this parameter isn't quite
clear, but I'm happy to admit that I'm not clever enough for this.
In any event, if one sets the auto_create_user parameter to "false",
which is what I did when I was first configuring RoundCube, that means
that RoundCube will not auto create users in the RoundCube DATABASE. I
had assumed this meant something like, "Gee, if someone tries to login
with a completely random user id and password, go ahead and let them
in! This is the people's e-mail server, man! Anyone can use it!"
Of course, that did seem a little strange to me at the time, so I set
this value to "FALSE" meaning, "I only want the users that are already
authorized in my IMAP server to be able to log in."
So, my confusion. Set the auto_create_user to TRUE and now everything
is working great.
Robert Landes wrote:
>I am using dovecot 0.99.14-1 (Debian sarge). I did not run into similar errors. Are you using SSL? WHat login mechanism are you using? Please post some more information about your system and configuration.
>On Sat, 22 Oct 2005 08:38:18 -0500, Randy Abel <rabel1 at austin.rr.com> wrote:
>>I saw in the archives that others where having this same problem. Was
>>there a solution posted?
>>Using Roundcube 20051021 build, dovecot .99
>>I'm able to telnet into dovecot and login without issue.
>>When I attempt to login through RoundCube I get:
>>* CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT
>>LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE AUTH=PLAIN cp01
>>OK Capability completed. Tried PLAIN: Resource id #25
>>My dovecot log shows a successful login when I am receiving this error
>>from RoundCube. On the other hand, this is a brand new DoveCot install
>>and I have never used IMAP with my mail server. I wonder if the other
>>people who were receiving this error where able to resolve it?
>>Any help is appreciated. Thank you!
More information about the Dev