search for: authspecials

Hi, I'm testing/using dovecot as imap proxy, passdb/userdb as passwd-like-file. It seems to function as expected (1). This setup is described in the wiki in AuthSpecials. But I also noticed in the documentation (ImapProxy / FeatLoginProxy pages) that the proxy feature only works with a sql passdb. Maybe I did something strange, but passwd-like-passdb does work..... So I have some questions: Is the documentation wrong? Is the documentation right? ;-) Are there...

Updated from ports collection from ver. dovecot-1.0.a3 to 1.0.a4_1. And it wan't work. Here's the log Nov 8 10:51:07 ot-group dovecot: Dovecot v1.0.alpha4 starting up Nov 8 10:51:08 ot-group dovecot: Auth process died too early - shutting down Nov 8 10:51:08 ot-group dovecot: auth(default): Unknown userdb driver 'passdb' Nov 8 10:51:08 ot-group dovecot: child 17872 (auth)

I've been having problems setting up my proxy using dovecot. I'm using the passwd-file for authentication as well as the regular unix passwd file. Can someone provide me with a complete example of how this should be done, I'm finding that the documentation on http://wiki.dovecot.org/AuthSpecials is sparse on the details. Please do not assume anything as I am new to both Dovecot as well as Linux (FC5).

.... The most important bugfixes were also done to dovecot-stable. The tarball is already updated. Looking at changelog, there seems to be: - Don't crash if client disconnects in the middle of APPEND - LDAP and static passdbs can return "extra parameters" (http://wiki.dovecot.org/AuthSpecials) now. Only SQL did before. - Added "nice" extra parameter for userdb to set imap/pop3 process's priority - RPA/SQL passdb patches from Andrey - Major rearrangements (again) to auth code: - Blocking passdbs (SQL) now create auth worker processes to do the actual blocki...

I upgraded to 1.0a3 - i have everything in the config migrated over, but I'm unsure about the way i should be querying postgres my db handles virtual accounts only, and is set as such: CREATE TABLE accounts ( local_part VARCHAR(64) NOT NULL, domain VARCHAR(64) NOT NULL, password VARCHAR(64) NULL, home_dir VARCHAR(256) NOT NULL, uid INTEGER DEFAULT

...user database means that the passdb already provided the # needed information and there's no need to do a separate userdb lookup. # This can be made to work with SQL and LDAP databases, see their example # configuration files for more information how to do it. # http://wiki.dovecot.org/AuthSpecials #userdb prefetch { #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shado...

...user database means that the passdb already provided the # needed information and there's no need to do a separate userdb lookup. # This can be made to work with SQL and LDAP databases, see their example # configuration files for more information how to do it. # http://wiki.dovecot.org/AuthSpecials #userdb prefetch { #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shado...

So I just upgraded from Dovecot 0.99 to the latest 1.0 RC2 because I was having all sorts of Authentication problems and crashes in 0.99. The upgrade did not solve the problem apparently. Dovecot still crashes periodically and always needs to be manually rebooted. The log file errors at the time of the crash: dovecot: Jul 12 14:30:59 Error: imap-login: Can't connect to auth server at