similar to: v1.1.12 and v1.2.beta2 released

Hi. Trying to upgrade from Dovecot 1.1.11 to 1.1.13 but having a problem with imap process segfaulting. Backtrace is below. I presume it's related to these MAILBOXDIR changes but the only documentation is the single line in the news for changing to ":MAILBOXDIR=mailboxes" when using dbox. Current configuration is "mail_location = dbox:~/Mail" so what exactly should be

Configurations with multiple shared namespaces can trigger a bug where the first argument of strcmp() invocation is NULL. This patch adds an explicit check, analogously to how the second argument is sanitized. --- src/lib-storage/mail-storage.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/lib-storage/mail-storage.c b/src/lib-storage/mail-storage.c index

http://dovecot.org/releases/1.1/dovecot-1.1.13.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.13.tar.gz.sig http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta3.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta3.tar.gz.sig Looks like Friday the 13th isn't the best day to make releases. :) These releases fix two bad bugs in v1.1.12. - v1.1.12's MAILBOXDIR changes broke

http://dovecot.org/releases/1.1/dovecot-1.1.13.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.13.tar.gz.sig http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta3.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta3.tar.gz.sig Looks like Friday the 13th isn't the best day to make releases. :) These releases fix two bad bugs in v1.1.12. - v1.1.12's MAILBOXDIR changes broke

I was unable to produce an IMAP core but have been successful with LMTP. Basically it crashes right upon login or delivery: Dec 20 08:55:23 nihlus dovecot: master: Dovecot v2.2.devel (9bc8d9b) starting up for imap, lmtp Dec 20 08:56:15 nihlus dovecot: imap(tlx at leuxner.net): Fatal: master: service(imap): child 5710 killed with signal 11 (core not dumped) Dec 20 08:57:23 nihlus dovecot:

http://dovecot.org/tmp/dovecot-1.1.12.rc.tar.gz I would have already released 1.1.12, but it needed the MAILBOXDIR change described below, and I'm slightly worried that it might have broken some special setup. So please test first and I'll release in v1.1.12 then in a few days. * Added :MAILBOXDIR= to mail_location to specify the root dir for mailboxes. dbox users should migrate to

I'm unclear about where and how this is to be used. I gather it is to be a new standard, but I didn't seem to find anything about it in the Dovecot Wiki Mail Location page. There are some words about it in the 1.1.12/3 release notes, but perhaps I'm thick, but they're meta-ambiguous to me. Is it meant to be used like this: mail_location =

Hi *, when a user A shares his INBOX with another user B, the user B can't access its content: User A: g getacl INBOX * ACL INBOX A at example.com lrswipkxtecda B at example.com lrswipkxtecd g OK Completed User B: l list "" "*" * LIST (\Noselect \HasChildren) "/" "user" * LIST (\Noselect \HasChildren) "/" "user/A at

Hi, I'm running dsync migrations using imapc and the source IMAP server is just too slow. It has taken 8 hours to migrate a mailbox with 47,000 messages. It seems most of the mailboxes are never accessed with IMAP, so it would be just as good to migrate them via POP3 which should work faster in my case. Is this actually meant to work? doveadm -D -o pop3c_user=xxxxxx at example.com -o

Hello Is it a bug in lazy expunge plugin or am I missing something? Dovecot v2.0.1 (c5111fb65b0b) home = /mail/%Ld/%Ln mail_location = mdbox:/mail/%Ld/%Ln/mdbox sources.list - debian (squeeze) .. deb http://xi.rename-it.nl/debian testing-auto/dovecot-2.0 main Config changes - - - plugin { lazy_expunge = .EXPUNGED/ } namespace { type = private separator = / prefix = inbox = yes

Hi Timo, make dies with an error: quota-fs.c: In function ?fs_quota_get_linux?: quota-fs.c:456: error: ?no? undeclared (first use in this function) quota-fs.c:456: error: (Each undeclared identifier is reported only once quota-fs.c:456: error: for each function it appears in.) make[4]: *** [quota-fs.lo] Error 1 One of the configure options was: --without-linux-quota Regards, Pascal -- The

Hi Timo, I'm playing with Dovecot v1.2.beta2 currently. When the dict process was started via deliver(?) and Dovecot is killed (kill $PID_OF_DOVECOT) after delivering only one message, it logs: Fatal: io_loop_handle_add: epoll_ctl(1, 10): Bad file descriptor If the dict process was not started or deliver has delivered more than one message, the error doesn't occur. I'm not using

Hello, I wanted to test the lazy expunge plugin together with mdbox. It seems to me that the folder subscriptions file in the mdbox directory was overwritten with only a few folder names every time I added or removed something in the list of subscribed folders, or even if I turned the imap folder subscription feature off and on. Here is my setup: # 2.0.16:

mail_location setting has started becoming a bit bloaty. I'm not actually even sure why I've kept adding more parameters to it rather than just adding new settings. It's also caused confusion, because people try things like: mail_location = mbox:/var/mail/%u mail_location = mbox:INBOX=/var/mail/%u Although the first one has been giving ok enough error message for a long time now and

So I decided to configure this plugin and take it for a test drive .. configured using mdbox (main namespace is Maildir) .. So as per Wiki have the following namespaces defined ... location is held within db ... but basically Maildir:~/Maildir for inbox namespace ==== 8< =============== namespace inbox { list = yes type = private inbox = yes prefix = INBOX/ separator = /

Hi What is the be practice regards setting the index path dynamically? My application needs to switch indexes based on the logged in user, I put the following before_filter into my controller (the Document.index_dir method calculates the user''s index path): before_filter { Document.ferret_configuration[:path] = Document.index_dir } It seems to work, the only rough edge is that the

==> /var/log/dovecot/dovecot.log <== Jun 9 09:58:26 spectre dovecot: lmtp: Fatal: master: service(lmtp): child 12635 killed with signal 11 (core dumped) This is another segmentation fault introduced in the current code. Please also look into fixing the other Core Dump I reported: http://www.dovecot.org/list/dovecot/2013-June/090795.html (gdb) bt full #0 0x00007f305d3df646 in

deeper still looks like culprit was fts_enforced = "no" which i removed given default anyway .. still get error [root at stargate dovecot.rawlog]# doveadm search -u matt at the-bryants.net mailbox .EXPUNGED/* from noreply at apress.com doveadm(matt at the-bryants.net): Error: fts: Failed to sync mailbox .EXPUNGED: Mailbox doesn't exist: .EXPUNGED 6156a416748c035b5c0b0000ef794dd1

Hey gang, A post on the Rails forum a while back had it sound like you pretty much had to use the Index Readers & Writers if you were going to be potentially accessing an index from more than one process. (i.e. multiple dispatch.fcgi''s, etc) Is this still the case, or does the main Index class do that black magic behind the scenes? =) I was having trouble implementing the

Hi, I think I found a bug in Dovecot 2.1.17 and 2.2.13. In our setup, sometimes ACLs stop working because "dovecot-acl-list" is replaced by an empty file. We found that lazy_expunge is connected to this. To reproduce, create ACLs for "user1" in a folder. Put a mail in that folder and expunge it, so that the folder will be created in the "expunged" namespace.