- dovecot - dovecot.org

[dovecot] rpm and srpm for dovecot
by seth vidal 27 Nov '02

27 Nov '02

hi, I put an rpm and srpm for dovecot on: http://www.dulug.duke.edu/~skvidal/RPMS/ They are made under rhl 7.3 - should build on 8.x I'd bet. I added an init script to start up imap-master I've done exactly ZERO testing on these and I'd welcome some feedback, thanks. -sv

1 0

[dovecot] 0.99.3 released
by Timo Sirainen 27 Nov '02

27 Nov '02

OK, this one will be the final release for a while, I promise (or hope). Fixes mbox corruption when expunging mails from the middle of mailbox with mail_read_mmaped=no which is the default. This bug was already in 0.99.0 release. I had been using Dovecot like that for 5 days or so without noticing the bug.. Wonder if I lost any mails.

1 0

[dovecot] mbox problems
by Timo Sirainen 26 Nov '02

26 Nov '02

Strange .. I didn't think I had done anything that could break things too badly. Anyway, at least with Solaris EXPUNGE may corrupt part of the mbox file, so don't do that for now.

1 0

[dovecot] 0.99.2 released
by Timo Sirainen 26 Nov '02

26 Nov '02

Mostly compiling cleanups but also one bugfix when index wasn't exclusively locked while it was being fsck'ed - that doesn't normally happen without crashing/whatever. v0.99.2 2002-11-26 Timo Sirainen <tss(a)iki.fi> + If we have to wait for a lock longer, the client is now notified about it every 30 seconds. - Default settings still pointed to lib directory instead of the libexec directory where the binaries were actually installed - vpopmail support had to be kludged to fix a bug in vpopmail library which sometimes left extra character after the user name. - Login process crashed if master process didn't let some user login. Normally this couldn't happen without error in configuration. - select() based I/O loop wasn't working so Dovecot didn't work in eg. OSX. Also PAM authentication wasn't detected with OSX. - Didn't compile with NetBSD-current

1 0

[dovecot] 0.99.1 released
by Timo Sirainen 25 Nov '02

25 Nov '02

Nothing new, just a few compiling/configuration issues fixed. Dovecot should also be in NetBSD pkgsrc soon. Now who would want to get it into Debian? :) v0.99.1 2002-11-25 Timo Sirainen <tss(a)iki.fi> + Added doc/mkcert.sh script to easily generate yourself a self-signed certificate. Modify doc/dovecot-openssl.cnf before running it. + --with-ssldir configure option to specify default path for /etc/ssl + Added ssl_disable setting to config file - OpenSSL wasn't checked properly by configure - vpopmail authentication module didn't compile - We should install the binaries into libexec dir, not lib - doc/configuration.txt and doc/mail-storages.txt were missing

1 0

[dovecot] vpopmail support?
by Kyle Symonds 25 Nov '02

25 Nov '02

Well, I read that back in 0.98 or so vpopmail support should work so I assumed it would be enabled in 0.99 but here's what I get. gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -I/usr/local/vpopmail/include -g -O2 -Wall -W -g -O2 -Wall -W -c userinfo-vpopmail.c In file included from userinfo-vpopmail.c:12: /usr/local/vpopmail/include/vpopmail.h:133: syntax error before `*' *** Error code 1 Stop in /root/dovecot/src/auth. *** Error code 1 Stop in /root/dovecot/src. *** Error code 1 Stop in /root/dovecot. *** Error code 1 Stop in /root/dovecot. Someone want to throw a bone? =) --Weasel weasel(a)squeakyweasel.net http://squeakyweasel.net

2 1

[dovecot] Re: vpopmail support?
by Kyle Symonds 24 Nov '02

24 Nov '02

Oh yeah, the system's FreeBSD 4.7-RELEASE. Trying to do a qmail+vpopmail+pop3+imap setup. --Weasel weasel(a)squeakyweasel.net http://squeakyweasel.net ======= At 2002-11-24, 12:25:00 you wrote: ======= >Well, I read that back in 0.98 or so vpopmail support should work so I assumed it would be enabled in 0.99 but here's what I get. > >gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -I/usr/local/vpopmail/include -g -O2 -Wall -W -g -O2 -Wall -W -c userinfo-vpopmail.c >In file included from userinfo-vpopmail.c:12: >/usr/local/vpopmail/include/vpopmail.h:133: syntax error before `*' >*** Error code 1 > >Stop in /root/dovecot/src/auth. >*** Error code 1 > >Stop in /root/dovecot/src. >*** Error code 1 > >Stop in /root/dovecot. >*** Error code 1 > >Stop in /root/dovecot. > >Someone want to throw a bone? =) > >--Weasel >weasel(a)squeakyweasel.net >http://squeakyweasel.net

1 0

[dovecot] 0.99.0 released
by Timo Sirainen 24 Nov '02

24 Nov '02

I figured now would be a good time for new release. All the major changes are pretty much done now. v0.99.0 2002-11-24 Timo Sirainen <tss(a)iki.fi> + Replaced hash file with binary tree file which makes Dovecot stay fast with large mailboxes after expunging multiple mails. + Several speed improvements with SEARCH + SEARCH CHARSET support using iconv(), although case-insensitive searching is currently supported only for ASCII characters. + OpenSSL support. + Support for regenerating Diffie Hellman and RSA parameters with specified intervals. NOTE: currently doesn't work with OpenSSL. + Support for each login connection being handled in it's own process. This is the default as it's more safe especially with SSL. + mbox locking is now safe, other processes can't modify the mbox file while we're reading it. + Notify clients with "EXISTS" almost immediately after new mail is received. + Rawlog: Support for saving user connections into files - useful for debugging. + Content-Language is finally parsed correctly + Lots of smaller speed optimizations - Partial BODY[] fetches weren't working properly - BODY[section] was buggy with message/rfc822 MIME parts - STARTTLS wasn't working - \* flag was missing from PERMANENTFLAGS. - Comments inside <> mail addresses crashed. - imap-login printed UTC timestamps to logfiles - passwd-file wasn't reread the the file changed - PAM authentication was implemented wrong, which caused it to break with some PAM plugins. - Lots of smaller fixes, mostly to do with reliability

1 0

[dovecot] Seen bug?
by Simon Lindgren 13 Nov '02

13 Nov '02

Hi, I'm using Kmail and dovecot for my IMAP pleasure, and have had some problems, which are evident from the following exchange with some kmail developers. My patch to the imap protocol in KDE fixed my problem, but should dovecot be changed instead? Thank you for any insight! I've included the discussion on kmail-devel so far: [ I wrote: ] -- I've recently switched to IMAP for email (using dovecot as the server, http://dovecot.procontrol.fi/) and have a small problem: Clicking a message brings it up, but doesn't seem to mark it read on the server. I need to select 'Message -> Mark Message -> Mark Message as Read' in order for it to "stay read" when I check for new mails on the server. Is anyone else seeing this behaviour? Is this a bug, or a feature? I've assigned a shortcut key for 'Mark Message as Read' so I get by, but with a large number of messages and folders, it quickly becomes annoying. -- [ Carsten Burghardt <burghardt(a)kde.org> wrote in reply: ] -- As your imap-server is not really common you should check with ethereal the communication between kmail and your server. -- [ I wrote in reply: ] -- Thanks for the replies... snooping with ethereal, I get the following: (quoting only the data sent from kmail) When viewing a mail in kmail: UID FETCH 203 (UID RFC822) When specifically flagging it as 'read' in kmail: UID STORE 203 -FLAGS.SILENT (\SEEN \ANSWERED \FLAGGED \DRAFT) UID STORE 203 +FLAGS.SILENT (\SEEN) It would seem that my problem would be solved if kmail also sent the +FLAGS stuff when viewing a message... but I don't know if this would be according to the IMAP specification - or if the server should flag the message as 'seen' when the client does the 'fetch' ? I do have 'Mark selected message as read after 0 sec' checked - and the message is flagged in kmail as read, but without specifically marking it as read in kmail, it's still 'unread' after the next 'check mail' run. I hope I'm being clear. If you still think this is a bug with my (non standard, I agree!) IMAP server I'll try another one. -- [ I wrote another reply: ] -- I made a change to imap4.cc, and it magically works for me - I've not tested this one very much, but it seems to do the trick so far. I would be very interested if someone knowledgeable would tell me just how wrong this piece of code is, as I'm working on learning these things. --- imap4.cc Tue Oct 15 21:52:43 2002 +++ imap4.cc Tue Nov 12 01:36:05 2002 @@ -289,6 +289,11 @@ } completeQueue.removeRef (cmd); + + if (aSection.find ("ENVELOPE", 0, false) == -1) { + doCommand (imapCommand:: + clientStore (aSequence, "+FLAGS.SILENT", "\\SEEN")); + } } } -- [ Carsten Burghardt <burghardt(a)kde.org> wrote: ] -- No, everything is alright here, you should check a different server. -- [ Bo Thorsen <bo(a)sonofthor.dk> wrote: ] -- It is definately a bug in the server. The IMAP RFC specifies that a server must only once serve a file flagged as new. So your server violates this principle.

2 1

[dovecot] Re: pam + radius
by Timo Sirainen 03 Nov '02

03 Nov '02

On Thu, 2002-10-31 at 21:32, Hielke Christian Braun wrote: > It helped a bit. Now the first login to dovecot works fine. The domainpart > of my username is not changed. But after the first login, dovecot > always sents the username from the first login to the radius server even when > i login from a different client with a complete different username. OK, fixed now in CVS. I implemented PAM support pretty wrong.

1 0