- dovecot - dovecot.org

[Dovecot] listescape und sieve
by Heiko Schlittermann 27 May '10

27 May '10

Hello, bug or feature? I'm using Dovecot 1.2.11. And because of a migration projekt I'm tempted to use the listescape plugin. If I understood well, it plugin { escape_char = "%" } should change the escape character to %. But it doesnt. Bug or feature? But more important: # sieve fileinto "a.b"; does not work as expected - the folder is visible as "a.b" in a normal imap client - because of the listescape plugin. # sieve fileinto "a\\2eb"; works. But the user won't understand this. Any ideas? Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann HS12-RIPE ----------------------------------------- gnupg encrypted messages are welcome - key ID: 48D0359B --------------- gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B -

2 2

[Dovecot] Dovecot 2.0beta4: Managesieve example config
by Thomas Leuxner 26 May '10

26 May '10

Hi, the 'example-config' holds an incorrect value for the listener socket: $ head -10 20-managesieve.conf ## ## ManageSieve specific settings ## # Service definitions service managesieve-login { #inet_listener sieve { # port = 4190 #} inet_listener sieve <> inet_listener managesieve Regards Thomas

5 6

[Dovecot] dovecot-sieve and managesieve for 2.0bX vanished ?
by Leon Meßner 26 May '10

26 May '10

Hi, im trying to build 2.0b5 with dovecot-sieve and possibly maangesieve. Does anyone know where i can get those for 2.0b5 ? There is no repo listed for these at http://hg.rename-it.nl/ cheers and TIA, Leon

3 3

[Dovecot] mdbox: Is there any more info on the "cleanup" step? (Dovecot 2.0beta5)
by William Blunn 26 May '10

26 May '10

The wiki page which mentions mdbox talks about a "cleanup" step for mdbox: : The space is later freed in "cleanup" step. This may be done : automatically within the session or later in a nightly cronjob when : there's less disk I/O. The cleanup first finds all files that have : refcount=0 mails. Then it goes through each file and copies the : refcount>0 mails to other dbox files (to the same files as where newly : saved messages would also go), updates the map index and finally : deletes the original file. So there is never any overwriting or file : truncation. I was wondering if there was any code to actually do this, or any command-line tools (and if either of those where they might be), or whether it was just design musings at the minute. Regards, Bill

2 1

[Dovecot] mdbox: What format is the file "storage/dovecot.map.index" in? (Dovecot 2.0beta5)
by William Blunn 26 May '10

26 May '10

I am looking at "mdbox" under Dovecot 2.0beta5. Looking at the documentation for "mdbox" I saw that we had a directory "storage" containing files "m.#" where "#" is an integer and a map file ("dovecot.map.index"). I think I expected the map file to be a plain text file with one record per line, but in fact it appears to contain binary data. According to the wiki ( http://wiki.dovecot.org/MailboxFormat/dbox ) the records go as: - map_uid: Unique growing 32 bit number for the message. - refcount: 16 bit reference counter for this message. Each time the message is copied the refcount is increased. - file_id: File number containing the message. For example if file_id=5, the message is in file m.5. - offset: Offset to message within the file. - size: Space used by the message in the file, including all metadata. The map file I have here is 1688 bytes in size (and I think there are 64 messages stored). Prime factors of 1688 are 2^3 x 211, so I think it is something other than just a straight array of fixed-size structures. Still, I can always look at the source if I really want to know :-) Regards, Bill

2 1

Re: [Dovecot] quota dict mysql not working (2.0.beta4)
by Timo Sirainen 26 May '10

26 May '10

On Mon, 2010-05-24 at 00:47 +0400, Andrey Melnikov wrote: > after mysql_query() - mysql return right data (affected rows = 1), but > there is no result to store (this is UPDATE/DELETE query), > next unconditional call to mysql_store_result() return nothing (right, > there no result) and reset affected_rows to -1ULL. > > You should modify driver_mysql_query_s() to call mysql_field_count() > first, to ensure - there is any data to read or no. But the whole point of the code is to get number of affected rows for previous UPDATE, so that if there is no quota row for user, the quota gets recalculated. This fixed it for my tests: http://hg.dovecot.org/dovecot-2.0/rev/0c15a760dab8

2 1

[Dovecot] newbie question about shared folders
by Tom Lieuallen 26 May '10

26 May '10

I'm preparing to move our site to dovecot 1.2.11 and have a question about shared folders. We're currently using UW imap's mbx mailboxes for shared folders. We accomplish the sharing by use of file system permissions and ACLs. I notice that dovecot's method of sharing is more based on IMAP ACLs and apparently file system permissions are useful, but not necessary. On the main dovecot page, it says: "Dovecot allows mailboxes and their indexes to be modified by multiple computers at the same time..." So, my question is whether I need to use the dovecot imap sharing namespace in order to safely share imap folders, or whether I can just use file system permissions as we have been using? My biggest concern is safe concurrent access to the shared folders, which I'm planning to implent with mbox files for now. thank you Tom Lieuallen Oregon State University College of Engineering

2 1

[Dovecot] Busy looping of 2.0Beta4 on NetBSD-current
by Scott Ellis 26 May '10

26 May '10

I built and install Dovecot 2.0Beta4 on my NetBSD/amd64-current system, and am seeing the user-owned imap processes busy-looping. In Dovecot 1.2.x (and 1.x and 0.x..) I force ionotify and ioloop to kqueue, so I suspected that was the problem. Turns out it's not: Using poll or none also causes the same problem. This did not happen in 1.2.8 (didn't try anything later than that). After a quick visit to gdb, I added some i_debug() statements in ioloop-kqueue.c (when I had that as the notify and loop method) which showed that the loop was in io_loop_handler_run() . I haven't done any similar debugging for the other ioloop methods, but a quick look at the 2.0 changelog for those files doesn't raise any immediate alarms. Any ideas what to look for here? Timo, any ideas? 1.2.x worked perfectly so it's something "new" in 2.0. ScottE

3 5

[Dovecot] warning: pipe flag `D' requires dovecot_destination_recipient_limit = 1
by Phil Howard 26 May '10

26 May '10

I'm getting this message, which looks like Postfix is the one logging it, but I don't know where it comes from or which configuration it needs to be placed in. Anyone know what this means? May 26 13:13:28 eth0 postfix/pipe[13821]: warning: pipe flag `D' requires dovecot_destination_recipient_limit = 1

2 2

[Dovecot] quota and lazy_expunge plugins both used: quotas go wrong with lazy_expunge'd mails
by Baptiste Malguy 26 May '10

26 May '10

Hello, I may have missed a point, but I could have found an issue between plugins quota and lazy_expunge. I have noticed that the "lazy_expunge"d mails are counted as part of the quota, while the documentation says it should not be. I have first tried to find out if this was a configuration mistake somewhere. Notably, you can notice that the expunged mails are in directory ~/expunged while the usual mail is in ~/Maildir : expunged mails are not in a subdirectory of ~/Maildir (this was just to make sure there were no side effect with this). I have deleted some expunged mails to be sure : at its next cycle, the file ~/Maildir/maildirsize contained expected value. So yes, I do know expunged mails in the expunged directory are counted (size, number of mails). So I've taken a look at the source code, adding some i_info(...) at different places of the quota and lazy_expunge plugins. >From the source code reading session, I understand that : 1. In src/lazy-expunge/lazy-expunge-plugin.c 1.1. lazy_expunge_mail_storage_init() sets the expunged mails namespace flag with NAMESPACE_FLAG_NOQUOTA 1.2. lazy_expunge_mail_storage_init() is called by lazy_expunge_mail_storage_created() 1.3. lazy_expunge_mail_storage_created() is part of the callback list hook_mail_storage_create 2. In src/plugins/quota/quota-storage.c: 2.1. The only place in the whole dovecot source code where NAMESPACE_FLAG_NOQUOTA is checked is in function quota_mailbox_list_created() 3. In src/plugins/quota/quota-plugin.c: 3.1 quota_plugin_init() add quota_mailbox_list_created() to the callback list hook_mailbox_list_created. >From my observations : - Callback functions in quota_mailbox_list_created are called _before_ callback functions in hook_mail_storage_create. - This observation led me to move the piece of code that sets NAMESPACE_FLAG_NOQUOTA from lazy_expunge_mail_storage_init() to lazy_expunge_mail_storage_created(). - But there, lazy_expunge_mail_storage_created() is called after quota_mail_storage_created() because names of the library files are lib10_quota_plugin.so and lib02_lazy_expunge_plugin.so. - There I have also learnt that callback functions of the same list are called in the reverse order compared to the library filenames. So see if my observations were right, I have renamed lib10_quota_plugin.so to lib01_quota_plugin.so, then it worked. But I doubt this is the right way to fix it. This also reverses the order other callbacks between the two plugins are called, which migh not be expected at all. I'm not event sure moving some code from lazy_expunge_mail_storage_init() to lazy_expunge_mail_storage_created() was right : I've improvized the reading the source code and do not understand the whole logic, so I suppose this could break something else. Timo, what do you propose ? Thanks for your great software. -- Baptiste MALGUY PGP fingerprint: 49B0 4F6E 4AA8 B149 B2DF 9267 0F65 6C1C C473 6EC2

2 2