Re: Retrieving mail from read-only mdbox

> On June 1, 2017 at 4:05 AM Joseph Tam wrote: > > > > > I've tried using IMAP with mail_location pointed at the snapshot, but, > > though I can get a listing of emails in the mailbox, the fetch fails when > > dovecot can't write-lock dovecot.index.log. > > I've thought

Re: Retrieving mail from read-only mdbox

I've tried using IMAP with mail_location pointed at the snapshot, but, though I can get a listing of emails in the mailbox, the fetch fails when dovecot can't write-lock dovecot.index.log. I've thought about doing this someday (adding snapshots to a user's namespace) but never got around to

Re: sieve folders in maildir with imap: not a directory not fixed with maildir_stat_dirs = yes

Yes, understood. I was hoping for an easier fix than migration. In particular: Home vs. mail directory Home directory shouldn't be the same as mail directory with mbox or Maildir formats (but with dbox/obox it's fine). It's possible to do that, but you might run into trouble with it sooner

Re: Retrieving mail from read-only mdbox

Quoting Mark Moseley : > I've tried using IMAP with mail_location pointed at the snapshot, but, > though I can get a listing of emails in the mailbox, the fetch fails when > dovecot can't write-lock dovecot.index.log. I'm surprised that dovecot would even try to write-lock

Re: v2.2.30.1 released

Built on CentOS 7 without a hitch. On 5/31/2017 7:24 AM, Timo Sirainen wrote: https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig Due to some release process changes I didn't notice that one important bugfix wasn't included in

Retrieving mail from read-only mdbox

This is a 'has anyone run into this and solved it' post. And yes, I've been reading and re-reading TFM but without luck. The background is that I'm working on tooling before we start a mass maildir->mdbox conversion. One of those tools is recovering mail from backups (easy as pie with maildir).

Re: v2.2.30 released

On 31 May 2017, at 22.56, Joseph Tam wrote: > > Timo wrote: > + If dovecot.index.cache corruption is detected, reset only the one corrupted mail instead of the whole file. >>> >>> Is this a big performance win? I still have users with jumbo mailboxes >>> who

Re: sieve folders in maildir with imap: not a directory not fixed with maildir_stat_dirs = yes

On 2017-05-31 15:09, David Gessel wrote: As my logs fill up with "imap(u...@domain.com): Error: stat(/mail/doman.com/user//.dovecot.sieve/tmp) failed: Not a directory" errors, I followed the advice at https://wiki2.dovecot.org/VirtualUsers/Home and

Re: v2.2.30 released

Timo wrote: + If dovecot.index.cache corruption is detected, reset only the one corrupted mail instead of the whole file. Is this a big performance win? I still have users with jumbo mailboxes who insist on direct mailbox file access using procmail or mail readers, which trigger index

Re: [Dovecot-news] v2.2.30.1 released

Am 31.05.2017 um 16:35 schrieb Timo Sirainen: On 31 May 2017, at 16.53, Reindl Harald > wrote: LTO build is as broken as 2.2.30 libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s "../lib10_quota_plugin.la"

Re: [Dovecot-news] v2.2.30.1 released

Am 31.05.2017 um 17:19 schrieb Timo Sirainen: On 31 May 2017, at 18.03, Reindl Harald wrote: libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s "../lib10_quota_plugin.la" "lib10_quota_plugin.la" ) /tmp/ccGO7JSw.ltrans4.ltrans.o::function

Re: v2.2.30 released

On 31 May 2017, at 16.32, FUSTE Emmanuel wrote: > >> + auth: Add passdb { mechanisms=none } to match separate passdb lookup >> + auth: Add passdb { username_filter } to use passdb only if user >>matches the filter. See

Re: Bug with 2.2.29-1~auto+25 back to haunt me

> On May 31, 2017 at 6:10 PM Ralf Hildebrandt > wrote: > > > * Ralf Hildebrandt : > > > So I added > > ssl_ca_file = /etc/ssl/certs/ca-certificates.crt > > > > But alas: > > May 31 16:50:24 mproxy dovecot: config: Warning: Obsolete

Re: [Dovecot-news] v2.2.30.1 released

On 31 May 2017, at 18.03, Reindl Harald wrote: > >>> libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s >>> "../lib10_quota_plugin.la" "lib10_quota_plugin.la" ) >>> /tmp/ccGO7JSw.ltrans4.ltrans.o::function >>> imapc_quota_refresh.lto_priv.22: error:

Re: Bug with 2.2.29-1~auto+25 back to haunt me

* Ralf Hildebrandt : > So I added > ssl_ca_file = /etc/ssl/certs/ca-certificates.crt > > But alas: > May 31 16:50:24 mproxy dovecot: config: Warning: Obsolete setting in > /etc/dovecot/conf.d/10-ssl.conf:36: ssl_ca_file has been replaced by ssl_ca = > > Gnarf!

Bug with 2.2.29-1~auto+25 back to haunt me

After upgrading from 2.2.28-1~auto+45 to 2.2.29-1~auto+25 I'm gettings this: May 31 16:44:31 mproxy dovecot: auth: Fatal: passdb imap: Cannot verify certificate without ssl_ca_dir or ssl_ca_file setting May 31 16:44:31 mproxy dovecot: master: Error: service(auth): command startup failed,

Re: [Dovecot-news] v2.2.30.1 released

On 31 May 2017, at 16.53, Reindl Harald wrote: > > LTO build is as broken as 2.2.30 > > libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s > "../lib10_quota_plugin.la" "lib10_quota_plugin.la" ) > /tmp/ccGO7JSw.ltrans4.ltrans.o::function >

shared folder and private index file problems

Hello, I'm using Dovecot 2.2.30 with Pideonhole 0.4.18 and I'm having some problems, perhaps someone can give an hint on how to solve them. When I try to create a folder in the toplevel directory of a shared mailbox, i get a "permission denied" although I have the rights, example: 1.doveadm -f

Re: v2.2.30.1 released

On 31 May 2017, at 16.47, Tom Sommer wrote: > > > On 2017-05-31 15:24, Timo Sirainen wrote: >> https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz >> https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig >> Due to some release process changes I didn't notice that

Re: v2.2.30.1 released

On 2017-05-31 15:24, Timo Sirainen wrote: https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I

v2.2.30.1 released

https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with

Re: v2.2.30 released

Le 30/05/2017 à 20:16, Timo Sirainen a écrit : > https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig > > * auth: Use timing safe comparisons for everything related to > passwords. It's unlikely that these could have been used

[Dovecot-news] v2.2.30.1 released

https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with

Re: v2.2.30 released

On 31/05/2017 12:04, A.L.E.C wrote: Recently Timo said "Don't use --with-storages=maildir. The benefits are very close to zero. I think I'll just remove that configure option entirely". So, it's been removed, I suppose. Suppose nothing, it's there (v2.2.30). $ grep with-storages configure

sieve folders in maildir with imap: not a directory not fixed with maildir_stat_dirs = yes

As my logs fill up with "imap(u...@domain.com): Error: stat(/mail/doman.com/user//.dovecot.sieve/tmp) failed: Not a directory" errors, I followed the advice at https://wiki2.dovecot.org/VirtualUsers/Home and https://dovecot.org/list/dovecot/2016-June/104403.html and set in

Re: v2.2.30 released

On 31/05/2017 12:06, Reuben Farrelly wrote: There is a build problem in the configure/make/libtool process when using "./configure ... --with-storages=maildir ...". This was deliberate - see the mailing list archives dated around 9 May 2017 My apologies, I missed that. I've stopped using

Re: v2.2.30 released

On 05/31/2017 12:54 PM, James wrote: > This can be avoided if "--with-storages=maildir,imapc" is used to build. > I could not find a proper solution in the time I had. Recently Timo said "Don't use --with-storages=maildir. The benefits are very close to zero. I think I'll just remove that

Re: v2.2.30 released

On 31/05/2017 8:54 PM, James wrote: On 30/05/2017 19:16, Timo Sirainen wrote: https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz There is a build problem in the configure/make/libtool process when using "./configure ... --with-storages=maildir ...". This was deliberate - see the

Re: v2.2.30 released

On 30/05/2017 19:16, Timo Sirainen wrote: https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz There is a build problem in the configure/make/libtool process when using "./configure ... --with-storages=maildir ...". libtool: link: cc -G -h lib10_quota_plugin.so -o

Re: Still trouble with vpopmail

On 30.05.2017 22:33, Bobber wrote: > Getting this error: > >> In file included from ../../src/lib/lib.h:6:0, >> from auth-common.h:4, >> from userdb-vpopmail.c:5: >> ../../config.h:791:0: note: this is the location of the previous >> definition >> #define