- dovecot - dovecot.org

[Dovecot] in a major jam...
by Tom Allison 16 Jan '06

16 Jan '06

I upgraded my dovecot installation from something <<1.0 to 0.99.14 today. I wasn't exactly planning to but it just came along for the ride when I upgraded the rest of my system. I was using postgresql for the authentication. Nothing works. the debug logs show that I'm able to make a connection to the database table well enough: auth(default): pgsql: Connected to dbmail (that's my database name) When I attempt to login I get (briefly) password mismatch. I haven't changed the password in well over a year. My old configuration file for dovecot.conf went to the tune of: login = imap auth_mechanisms = plain auth_passdb = pgsql:/etc/dovecot/dovecot-pgsql.conf auth_user = root (probably not the best, but it worked) I now have a config file something like this: dovecot-pgsql.conf -- added the 'driver = pgsql' statement. Because it's able to connect to the database I don't think this is much of a problem here. dovecot.conf (these are all the non-empty lines, except for some logging stuff) protocols = imap disable_plaintext_auth = no protocol imap { } protocol pop3 { } auth_verbose = yes auth_debug = yes auth default { mechanisms = plain passdb pam { } passdb sql { args = /etc/dovecot/dovecot-pgsql.conf } userdb passwd { } user = root } It's fairly obvious that there has been a lot of work done on getting more authentication mechanisms in place for dovecot. That's great, and some day I want to play with it, but this is not the day for it. help.... help.... oh help!

2 2

[Re: [Dovecot] in a major jam...]
by Tom Allison 16 Jan '06

16 Jan '06

Marcus Rueckert wrote: > On 2006-01-16 14:46:36 -0500, Tom Allison wrote: > >>I upgraded my dovecot installation from something <<1.0 to 0.99.14 >>today. I wasn't exactly planning to but it just came along for the ride >>when I upgraded the rest of my system. > > > do you mind to upgrade to the release mentioned in this mail > http://www.dovecot.org/list/dovecot/2006-January/010832.html ? > > the 0.99.14 code base is 2y old and no longer actively maintained. > I upgraded from 0.99.14. It reports 1.0alpha5 now. This is the transistion that broke me. And I just realized I posted this twice to the mailing list. My rather hastily set up connection to another mail server wasn't telling me I actually sent anything.

1 0

[Dovecot] Plain password not authenticating
by Anne Wilson 16 Jan '06

16 Jan '06

I'm trying to set up a temporary mailserver using Debian Sarge and Dovecot 1.0 with maildir format. My only previous experience has been on a simple imap server. I have read the wiki documentation and searched the archives, but can't tie down my problem. The log tells me Info: passwd-file(anne) : unknown user. I have set auth_userdb = passwd-file /etc/imap.passwd auth_passdb = passwd-file /etc/imap.passwd and created the /etc/imap.passwd file as anne:{plain}mypassword:1000:1000::/home/anne What have I missed? Anne -- Registered Linux User No.293302 (http://counter.li.org/)

4 23

[Dovecot] Re: Dovecot memory use and settings
by Roger Weeks 16 Jan '06

16 Jan '06

We're continuing to have dovecot auth-worker failures once or more times per day. The symptoms are these in the log: pop1 dovecot: auth-worker(default): Out of memory (Needed 8164 bytes) or auth-worker(default): sql(lewis1,12.43.59.134): Password query failed: MySQL client ran out of memory Timo suggested that we need to up the auth_process_size = 256 However, we've tried increasing this to 512 and then 768. The comment on the entry says # Set max. process size in megabytes. These changes don't seem to make any difference. On both of our servers (RH ES4, 1MB RAM), we never seem to have more than 300MB of RAM used. However, the auth-worker process continues to fail occasionally. It does respawn itself after a couple of minutes, but in that time all authentication for dovecot fails. Am I missing something else in the config? -- Roger J. Weeks Systems & Network Administrator Mendocino Community Network On Jan 11, 2006, at 12:51 PM, Timo Sirainen wrote: > On Wed, 2006-01-11 at 12:40 -0800, Roger Weeks wrote: >> pop1 dovecot: auth-worker(default): Out of memory (Needed 8164 bytes) >> >> or >> >> auth-worker(default): sql(lewis1,12.43.59.134): Password query >> failed: MySQL client ran out of memory > > These are different from the system running out of memory. It's about > authentication process size hitting its configured limit. Default is: > > # Set max. process size in megabytes. > #auth_process_size = 256 > > So it appears that it's trying to grow above 256MB at which point it > gets killed. This could mean that something is leaking memory, but I > don't remember other people having this problem, so it might be > somehow > specific to your configuration. > > In any case those auth-workers are restarted automatically whenever > they > die so it shouldn't be that big of a problem? > > There are also ways to debug this if you want to.. >

3 5

[Dovecot] Imap working, but not Pop3
by Cyril Spiro 16 Jan '06

16 Jan '06

I'm running Redhat Linux 4.1 and I have dovecot loaded and imap is working. Users can get their mail via squirrelmail. But everytime I try to 'chkconfig ipop3 on' I get the error 'error reading information on service pop3: no such file or directory'. Any ideas?

2 1

[Dovecot] passdb-pam: PAM_RHOST on FreeBSD >= 5.0 (where PAM != Linux-PAM)
by Tom Alsberg 16 Jan '06

16 Jan '06

This is actually something I had on my mind to write about in the past few -stable and alpha releases, but did not get to and instead always patched myself. Now having updated to the latest snapshot (which may be released as beta1), I stumbled on it again: In src/auth/passdb-pam.c, where the client host is passed to PAM, the code looks like this: #ifdef PAM_RHOST const char *host = net_ip2addr(&request->remote_ip); if (host != NULL) pam_set_item(pamh, PAM_RHOST, host); #endif For some reason there is a preprocessor/compile-time check whethere there exists such a preprocessor symbol as the PAM item PAM_RHOST (why check that? IIRC PAM_RHOST is standard and in all PAM implementations). However, PAM_RHOST (or other PAM items, for that matter), are not preprocessor symbols in all PAM implementations. For example, in OpenPAM (the PAM implementation used on FreeBSD >= 5.0, among others; FreeBSD 4 used Linux-PAM), PAM items are elements of an enum, and thus this check fails, and the client host is not passed to PAM. Since it can be defined in several ways, I do not see how to check for it other than using a compilation test (in autoconf) and then defining something like HAVE_PAM_RHOST in config.h. However I do not see why check for it at all, so I propose to remove that #ifdef. Tiny patch attached for that. Cheers, -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

1 0

[Dovecot] Looking to upgrade from .99.14 to 1.0alpha5
by Erik Dasque 15 Jan '06

15 Jan '06

Hi all, I was looking to upgrade my dovecot .99.14 installation to 1.0alpha5 today and bumped into an issue. My setup is on Mac OS X 10.4 and I am using After reading http://wiki.dovecot.org/UpgradingDovecot , I created a default dovecot.conf file with the following information grabbed from my prior installation: Snow:~ ed$ grep -v '^ *#' /usr/local/etc/dovecot.conf|grep -v ^$ ssl_disable = yes login = imap login = pop3 auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam login auth_user = root auth_verbose = yes So as you can see, I use passwd and pam as my authentication db. So I copied over the dovecot-example.conf and as far as I know the only modifications I needed to make to the default file were to disable ssl and set the verbose and debug auth. Keep in mind that passwd/pam db methods work with .99.14 but with 1.0alpha5, I get the following: Jan 14 15:55:16 Snow dovecot: Dovecot v1.0.alpha5 starting up Jan 14 15:58:15 Snow dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AGVkAGFic2ludGhlMzM= Jan 14 15:58:15 Snow dovecot: auth(default): pam(ed,127.0.0.1): pam_authenticate() failed: Authentication failure Jan 14 15:58:15 Snow dovecot: auth(default): client out: FAIL 1 user=ed Jan 14 15:58:21 Snow dovecot: auth(default): client in: AUTH 2 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AGVkAGFic2ludGhlMzM= Jan 14 15:58:21 Snow dovecot: auth(default): pam(ed,127.0.0.1): pam_authenticate() failed: Authentication failure Jan 14 15:58:21 Snow dovecot: auth(default): client out: FAIL 2 user=ed and so on and so forth. Any idea what could be causing this or how to debug this further ? Thanks in advance, Erik PS: my pam setup for dovecot is: Snow:~ ed$ more /etc/pam.d/dovecot auth required pam_unix.so nullok account required pam_unix.so

3 2

[Dovecot] Occasional errors opening email folder in SquirrelMail
by Jonathan 15 Jan '06

15 Jan '06

Every once in a while I get this [1] error when trying to open a mail folder in SquirrelMail. I don't know enough about IMAP to tell if it is a SquirrelMail or a Dovecot issue. I also get this [2] error message every time I try to send an email. The email goes through but there is no copy in the Sent folder. If there is some kind of logging I can enable that would help with this please let me know. [1] ERROR: Bad or malformed request. Query: FETCH (FLAGS UID RFC822.SIZE BODY.PEEK[HEADER.FIELDS (Date To Cc >From Subject X-Priority Importance Priority Content-Type)]) Server responded: Error in IMAP command UID: Invalid arguments. [2] ERROR: Bad or malformed request. Server responded: Error in IMAP command APPEND: Thank you, Jonathan

2 2

[Dovecot] How long to 1.0?
by Fredrik Tolf 15 Jan '06

15 Jan '06

Hi! I'm wondering how close Dovecot can be said to be to 1.0 "Final". How stable can the alpha branch be said to be? I was browsing around the Dovecot homepage, but I couldn't find any answer to this question. I hope it hasn't been asked (too many times) before. Fredrik Tolf

15 29

[Dovecot] Corrupted index files
by Andy Cravens 15 Jan '06

15 Jan '06

I'm using alpha 5 and I'm getting "Corrupted index cache files" errors on one user's account. I found several posts in the mail archives on this subject and concluded from the responses that it's not a serious problem because Dovecot can deal with it. I deleted the index files and they were recreated but the error persists. The end user did not notice any problem but it makes me nervous. Is this something I should be concerned about? dovecot: Jan 12 10:22:06 Error: imap(username): Corrupted index cache file /export/home/username/mail/dovecot.index.cache: Duplicated field in header: hdr.CONTENT-TYPE dovecot: Jan 12 14:31:08 Error: imap(username): Corrupted index cache file /export/home/username/mail/.syslog_analyzer/dovecot.index.cache: Duplicated field in header: hdr.CONTENT-TYPE dovecot: Jan 12 14:43:56 Error: imap(username): Corrupted index cache file /export/home/username/mail/.gl3_ip_allocation/dovecot.index.cache: Duplicated field in header: hdr.CONTENT-TYPE By the way... is there a search function somewhere for searching the mailing list archives? I ended up selecting one month at a time and searching through the thread titles with my browser's "find" button. -- Andy

3 3