January 2003 - dovecot

[dovecot] Plain auth broken
by Timo Sirainen 03 Feb '03

03 Feb '03

On Fri, 2003-01-17 at 14:15, Timo Sirainen wrote: > On Thu, 2003-01-16 at 03:31, james broermann wrote: > > pine still doesn't want to work. It does detect that the server is using > > plain text passwords. I'll try the sniffer and see what turns up. > > Whops, you're right. I've tested pine only with digest-md5 > authentication before. Looks like my PLAIN authentication isn't working > properly. Normally other clients just use LOGIN command which is > different. Patch is now available at http://dovecot.procontrol.fi/

2 7

[dovecot] cvs down?
by Jesse Peterson 24 Jan '03

24 Jan '03

(Logging in to anonymous(a)dovecot.procontrol.fi) CVS password: cvs [login aborted]: connect to dovecot.procontrol.fi:2401 failed: Connection refused cvs [checkout aborted]: connect to dovecot.procontrol.fi:2401 failed: Connection refused Was the CVS server taken down? -- Jesse Peterson / jesse(a)pixeltechs.com

2 1

[dovecot] Unable to Log in on FreeBSD server?
by Mark 21 Jan '03

21 Jan '03

Hello! I recently compiled dovecot 0.99.7 on a FreeBSD 4.3 server, and have been having problems with logging in and password authentication. a. I can't seem to get it to compile MD5 support -- it only seems to support plain, plain-file, and pam. b. Whenever I try to log in, I always get something along the following lines in /var/log/messages .... Jan 16 17:52:15 akira imap-login: close(master) failed: Bad file descriptor Jan 16 17:55:33 akira imap-auth: Userinfo pam doesn't support DIGEST-MD5 method Jan 16 18:08:28 akira imap-master: Login process died too early - shutting down (I also included one about MD5 in there too! :-)) Basically, the imap-login process is dying every time I try to do a login from a remote machine (I've tried Evolution and Outlook Express ....) I've tried telling it to use port 143 and port 993 (where it correctly generates a warning about a certificate that it can't verify, since i created that certificate with mkcert.sh ) Is there something I haven't configured correctly? The only things I've changed in dovecot.conf are: Any suggestions? Thanks, Marc.

2 5

[dovecot] mbox & Maildir
by james broermann 18 Jan '03

18 Jan '03

Hi, Is it possible for a client to read both mbox and Maildir formats from one server running dovecot? Without changing default_mail_env in dovecot.conf, Maildir folders are working ... they're located in ~/Maildir. No /var/mail/username exists. I have mbox format folders in ~/mail and have been trying to get pine to find them by adding pine folder collections. I always end up back in ~/Maildir, though. Thanks, Jim

2 1

[dovecot] 0.99.7 out
by Timo Sirainen 17 Jan '03

17 Jan '03

This one seems to be actually working. Also rewrote doc/index.txt in case someone is interested.

3 7

[dovecot] 0.99.6 buggy
by Timo Sirainen 14 Jan '03

14 Jan '03

Just a note, the hash table code in it was still buggy. Especially with maildir it could leave the processes to infinite loop. Have to think a bit more how to fix this properly..

1 0

[dovecot] security audit of the code
by seth vidal 14 Jan '03

14 Jan '03

Timo, I know that you're taking an effort to make sure that dovecot is written securely, but I was wondering if you've asked any third party to audit the code yet. I don't have the skills necessary to do this but I bet there is someone out there who does and might be willing to do so. -sv

5 7

[dovecot] 0.99.6 released
by Timo Sirainen 14 Jan '03

14 Jan '03

Several bugfixes since 0.99.6rc3. Here's again the change summary since 0.99.5: v0.99.6 2003-01-13 Timo Sirainen <tss(a)iki.fi> + THREAD=REFERENCES extension support. ORDEREDSUBJECT would be easy to add, but I think it's pretty useless. + SORT is much faster now. + mbox: If ~/mail directory isn't found, create it. + Log login usernames * Some coding style changes (less typedefs) - Mails with nested MIME parts might have caused incorrect BODY and BODYSTRUCTURE fetches and sometimes might have crashed dovecot (assert at imap-bodystructure.c). If client had already successfully done the BODY fetching a couple of times, the bug couldn't happen anymore since Dovecot then began caching the BODY data. So, this mostly happened with new users. - non-UID SEARCH might gave wrong replies in certain conditions. - SORT replied always with UIDs instead of sequences. - If authentication was aborted by client ("*" reply to AUTHENTICATE), the login process crashed later. - STATUS command gave invalid reply for mailboxes with spaces in name - Timezones were parsed wrong with message dates - Digest-MD5: We used "qop-options" instead of "qop", which was incompatible with at least Cyrus SASL. - Realms in passwd-file were buggy - Literals didn't work when logging in - Crashed if it had to wait for mbox lock - With invalid configuration auth and login processes were just dying and master filling log files infinitely. - We didn't work with some 64bit systems

1 0

[dovecot] dovecot-0.99.6rc3 compilation problems on (Open|Free)BSD
by Johan Fredin 13 Jan '03

13 Jan '03

Hi there! Dovecot-0.99.6rc3 barfs at me when I try to compile it on OpenBSD 3.2 or FreeBSD 4.7, both with the same error: [ ..snip.. ] gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c charset-iconv.c gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c charset-utf8.c charset-utf8.c:42: storage size of `ascii_translation' isn't known charset-utf8.c:42: storage size of `utf8_translation' isn't known *** Error code 1 Stop in /usr/home/griffin/dovecot-0.99.6rc3/src/lib-charset. *** Error code 1 Stop in /usr/home/griffin/dovecot-0.99.6rc3/src (line 134 of Makefile). *** Error code 1 Stop in /usr/home/griffin/dovecot-0.99.6rc3 (line 202 of Makefile). *** Error code 1 Stop in /usr/home/griffin/dovecot-0.99.6rc3 (line 330 of Makefile). I didn't use any fancy parameters for ./configure. Any config.* files I can post to help? /Regards, Johan

2 3

[dovecot] 0.99.6rc3
by Timo Sirainen 13 Jan '03

13 Jan '03

Well, "release candidate" wasn't really right name for last two versions. Maybe not for this one either, it has a few changes that could potentially break things badly (new hash table code especially). Anyway, seems to work with me. If I don't see any problems with it for a few days it'll be the final. The really great news is that we support threading. A lot of people have not used Dovecot simply because it couldn't be used for webmails. Hmm. What's the next most important feature? .. Better mbox support? Shared folders? Quota? LDAP/MySQL/etc. authentication? Here's the change summary: v0.99.6 2003-01-xx Timo Sirainen <tss(a)iki.fi> + THREAD=REFERENCES extension support. ORDEREDSUBJECT would be easy to add, but I think it's pretty useless. + SORT is much faster now. + mbox: If ~/mail directory isn't found, create it. + Log login usernames * Some coding style changes (less typedefs) - Mails with nested MIME parts might have caused incorrect BODY and BODYSTRUCTURE fetches and sometimes might have crashed dovecot (assert at imap-bodystructure.c). If client had already successfully done the BODY fetching a couple of times, the bug couldn't happen anymore since Dovecot then began caching the BODY data. So, this mostly happened with new users. - non-UID SEARCH might gave wrong replies in certain conditions. - SORT replied always with UIDs instead of sequences. - If authentication was aborted by client ("*" reply to AUTHENTICATE), the login process crashed later. - STATUS command gave invalid reply for mailboxes with spaces in name - Timezones were parsed wrong with message dates - Digest-MD5: We used "qop-options" instead of "qop", which was incompatible with at least Cyrus SASL. - Realms in passwd-file were buggy - Literals didn't work when logging in - Crashed if it had to wait for mbox lock - With invalid configuration auth and login processes were just dying and master filling log files infinitely. - We didn't work with some 64bit systems

2 4