- dovecot - dovecot.org

[Dovecot] did the conversion and something broke
by Eric S. Johansson 26 Nov '03

26 Nov '03

figures. Converted over to maildir today. Procmail is a piece of cake once I managed to pride out of its cold dead fingers the essential tiny bit of documentation I needed. But I'm having a problem with my nested directories. I have a directory called incoming sort my incoming mail. The conversion utility created a bunch of files called incoming.<stuff> and 1 file is visible incoming/pound. However, if I try to subscribe to anything else I get: the current command did not succeed. The mail server responded: Invalid mailbox name: incoming/ATMoB and this is how it set up. [esj@harvee Maildir]$ ls -ld .incomming.ATMoB/ drwx------ 5 esj esj 4096 Nov 25 13:45 .incomming.ATMoB/ [esj@harvee Maildir]$ ideas? ---eric -- Speech recognition in use. Incorrect endings, words, and case is closer than it appears

2 2

[Dovecot] IMAP subscribe/unsubscribe broken in 0.99.10.2
by Matthew Reimer 25 Nov '03

25 Nov '03

IMAP subscribe/unsubscribe is broken in 0.99.10.2 (and earlier releases), specifically subsfile_set_subscribed(), where the logic is all wrong. I tried just copying over the latest subscription-file.c but it has dependencies on some file locking/dotlocking stuff that 0.99.10.2 doesn't have. Timo, would it be possible to incorporate the latest subscription-file.c into 0.99.10.3 (whenever that will be)? Matt

2 2

[Dovecot] The latest dovecot fixes the problems with most mail clients
by Brook Humphrey 25 Nov '03

25 Nov '03

.99.10.4 fixes most the issues with kmail. For some reason if I look at an email and then go to another one and then try to go back to one I've already viewed sometimes it shows the mail as an atacment. This version does fix the problem with squrrelmail not being able to subscribe to folders. Thanks for the fixes. -- -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~- Brook Humphrey Mobile PC Medic, 420 1st, Cheney, WA 99004, 509-235-9107 http://www.webmedic.net, bah(a)webmedic.net, bah(a)linux-mandrake.com Holiness unto the Lord -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-

1 0

Re: [Dovecot] SSL and certificate authorities.
by Matthew Reimer 25 Nov '03

25 Nov '03

Zach Bagnall wrote: > On Thu, 20 Nov 2003 18:28:51 +0200, Timo Sirainen <tss(a)iki.fi> wrote: > >>What exactly does this patch do? Gives client a list of accepted CAs, >>but it doesn't look like it actually requires client to provide a >>valid certificate? > > > On Tue, 18 Nov 2003 11:03:08 +1300, James Tyson <james(a)giantrobot.co.nz> > wrote: > >>Also, is there a configuration directive for dovecot to add the >>issuers ca bundle similar to apache's SSLCACertificateFile? > > > I'm no SSL expert, but I took the requested feature to be a way to "make > additional certificates available in order to complete a certificate > chain". I had trouble with an instantssl cert, and found that what I needed to do was to also include all the certs up the chain in the .pem file, in a certain order, to keep the client from complaining about an invalid certificate. The first certificate in the pem file should be the the server certificate, followed by its chain starting from the root certificate down. Works for me without the need for patches (though something like SSLCACertificateFile would be nice). Matt

1 0

[Dovecot] mbox format
by DINH Viet Hoa 25 Nov '03

25 Nov '03

I wish to know some implementation details about mbox. When you you mbox format in IMAP, are you doing to keep the same message UID across IMAP session if you know that any other program can modify the mailbox as it wants, for example, two messages can be exchanged. In this case, will the UID kept the same ? If they keep their UID, how do you identify the messages ? Thanks, -- DINH V. Hoa, etPan! - newsreader, mail user agent -- http://libetpan.sf.net/etpan

2 1

[Dovecot] New index / mailbox API
by Timo Sirainen 25 Nov '03

25 Nov '03

Today morning I had an idea how to make indexes more scalable with multiple concurrent writers. As a side effect it also made the locking issues much more simpler. So I thought I'd go and rewrite all the indexing code, it had gotten way too ugly and difficult to understand and maintain. I also thought to separate the index handling completely from mailbox handling. So there would be lib-index and lib-mailbox. lib-storage would then tie them together. Mailbox API still feels somewhat dirty though.. I didn't want it to depend on lib-index and I didn't want to duplicate any lib-index functionality in it to avoid uselessly allocating memory, so I can't reference to mails directly with their sequence number or UID. So I'm passing (void *id, size_t id_len) around - with maildir that would be the filename and with mbox it would be current offset in file. Suggestions welcome about both APIs. Some of the changes in indexes and it's API: - "modify log" -> "transaction log" which was the big change. All flag updates and expunges are first written to transaction log and only when committing it they will be moved into the main index. The transaction writes require the file locked for only very short time, so with lots of concurrent writers it means that several sessions could have written their wanted changes to log file, but they're all blocking on getting them moved into main index. When one session finally gets a lock in the main lock file, it writes everyone's changes into it. If lock can't be acquired in a second or so, the main index will be rewritten into temp file and rename()d over. This means that we can have tons of sessions reading and writing to same shared index file and no session can block others from reading or writing. Currently yoou could easily block changes for a very long time with eg. FETCH 1:* BODY.PEEK[] and reading it 1 bytes/sec. - mail_index will be a class interface, so it's implementation can be changed at runtime. In-memory indexing is going to be a totally different implementation this time with better memory usage. Could be useful for optimizing some special cases as well. - You'll get "views" into mailbox. A view will take care of keeping sequences synchronized according to what each client session thinks they are. Currently lib-storage does that in kind of ugly way. Hopefully this means that we can get rid of sequence parsing in lib-storage completely and move it into imap-only code. - You don't directly manipulate with locks and there's no rules of in which order you have to do something. You get views and transactions and use them. - You can have multiple views and transactions, so one opened index could be used to handle multiple client sessions. I'm not sure if that will ever be useful though :) - Error correction will be done automatically this time. Whenever some error is noticed, it will be fixed immediately and unless it changes syncing state, it doesn't force client to disconnect. Also it hopefully will be possible to change from disk-indexing to memory-indexing on the fly in case you run out of disk space. - I'm trying to get it NFS-safe.. - mail-cache that I recently rewrote doesn't change. The bad thing is that it seems to be broken in some way and probably needs rewriting anyway.. And I'm not sure if the problem is just in the code, or if the design itself is somehow broken with it. I'm fearing that memory doesn't somehow keep up with changes by other sessions, since we're not locking cache file for reading..

5 9

[Dovecot] 0.99.10.3 released
by Timo Sirainen 25 Nov '03

25 Nov '03

- SUBSCRIBE broke subscription lists - LIST code rewritten, children flags should be correct now - SORT and THREAD could have given invalid replies - Partial BODY[...] fetches might have returned wrong data or at least performed worse than was necessary Maybe Entourage was having problems with subscriptions?

3 6

[Dovecot] deliver mail with postfix to dovecot for mailinglists
by Sven Kirmess 25 Nov '03

25 Nov '03

This is a bit off topic on that list. But the question is required because of a limitation of dovecot. It cannot have shared mailboxes into which one would collect mailing list mails. I assume one has already solved that problem and therefore ask this question on that list. I try to do the following: I would like to setup an alias dovecot(a)kzone.ch and subscribe this alias to the dovecot mailing list. Then I would like to create an alias to run maildrop with the correct parameter to put it into the directory ~ski/Maildir/.dovecot/. Of course, there is no user dovecot on my system and if there would be one she couldn't write to a directory owned by me. Is there a trick to do the following: ski -> ~ski/Maildir dovecot -> ~ski/Maildir/.dovecot postfix -> ~ski/Maildir/.postfix Any other idea? Any good documentation on that? Sven

3 3

[Dovecot] Compiling dovecot
by Ted S. Garaventa 24 Nov '03

24 Nov '03

Still trying to compile dovecot to run on solaris8 x86. The program compiles without errors but does not run. The truss out put I get running the program is illegal system call by program: /usr/local/sbin/dovecot Any help is welcome.

4 3

[Dovecot] entourage + dovecot bug?
by Payton 24 Nov '03

24 Nov '03

I have dovecot set up to run IMAP services without SSL (I have tested many other configurations as well, but this reproduces the problem the simplest). When attempting to connect to the imap server using Entourage for OS X on a mac, I receive the following error: Mail could not be received at this time. The server returned the following error . Dovecot reports a successful login and nothing else in the mail log. All other email clients I have tried (mutt, Mail.app) work fine with the IMAP server. I have also tried this on multiple clients with the same results. All this leads me to believe a bug exists in Entourage, however: I also have a Red Hat 7.3 server running qmail and dovecot in nearly the same manner (except that it is using dovecot 0.99.10 and shadow for password authentication, instead of dovecot 0.99.10.2 and ldap password authentication). Entourage (and all other clients) works just fine with this setup. I'm not certain if the problem lies in some tweak between 0.99.10 and 0.99.10.2 or if it is something with the red hat system itself, but I can't find anything. I am using dovecot 0.99.10.2 on a Red Hat 9 system using qmail 1.04 (netqmail) and checking with the latest version (update 10.1.5) of Entourage on Mac OS 10.2.8. Thanks for any help! -Payton

6 8