Re: Corrupted index cache after migrating from maildir to mdbox
all mails are stored on an xfs filesystem and only the local dovecot accesses it. Possible to fix the index.cache files? I havn't found anything suitable in the docs. The doveadm-index commands are only for the fts plugin I think. On 13.10.2014 02:37, Daniel Parthey wrote: > Maybe the index is corrupted too and the index.cache is a cached version of > the corrupted index? > > Are you using NFS with mdbox and accessing one nfs mailbox directory > concurrently from several dovecot hosts? >
Re: 2.2.14rc1 - dsync in backup mode still changes source permissions
On 2014-10-11 08:51, Peter Mogensen wrote: the docs says (or rather "said") explicitly: "No changes are ever done to the source location." ... Is the documentation intentionally changed to not make that promise anymore? I also notice that the "-o" for overriding userdb settings has been removed from the documentation. Is that intentionally? /Peter
Re: Corrupted index cache after migrating from maildir to mdbox
Maybe the index is corrupted too and the index.cache is a cached version of the corrupted index? Are you using NFS with mdbox and accessing one nfs mailbox directory concurrently from several dovecot hosts?
[Dovecot/VirtualUsers/VirtualMailBoxes] No mails into mua
Hi all, I've configured postfix with multiple host and virtual mailboxes (main.cf is here: http://pastebin.com/798VVxbv). So I can receive email to vu...@mydomain.tld into /var/mail/vhosts/mydomain.tld/vuser file. Now I'm configuring dovecot 2.2.13-r1; this is my dovecot -n and /etc/dovecot/passwddir/mydomain.tld/passwd: http://pastebin.com/b4xcjj7t - The auth and server subscribe from a mua is ok and in the vuser file there are some mails but I can't see them in my mua. mail.log doesn't report any error. Where I'm wrong? Aleskandro
Re: Dovecot domain quota
On 10/12/2014 01:28 PM, Filip Bartmann wrote: After running `doveadm quota recalc -A` I have in my db: --- +---++--+ | domain| bytes | messages | +---++--+ | debian.jd | 505758 | 81 | +---++--+ --- whith is from accountbartm...@debian.jd not both accounts at testing VPS domain debian.jd. The same is with quota enforcing - quota if enforced on the latter of the accounts in /etc/dovecot/users on testing machine or database in production machine. What I do wrong? As I remember from previous conversations here, this is a limitation of the current design. The comment in example-config/conf.d/90-quota.conf says: # Multiple quota roots are also possible, for example this gives each user # their own 100MB quota and one shared 1GB quota within the domain It doesn't really support accounting for the *sum* of *multiple storage quotas* within a domain. As a hack: you can just not run quota recalc ;-) or more realistically, separately track user quotas individually (you really should!), and post recalc immediately update the domain by running something like update domain_quota set bytes=(select sum(bytes) from user_quota where username like '%@debian.jd') where domain='debian.jd';
Re: Corrupted index cache after migrating from maildir to mdbox
Hi, I mv'ed all dovecot.index.cache files for one mailbox away but I still get error messages: Oct 12 22:47:12 mail01 dovecot: imap(foo...@example.com): Error: read(/home/vmail/example.com/foobar/mdbox/storage/m.1): FETCH BODY[] for mailbox INBOX UID 3 got too little data: 738 vs 1543 Oct 12 22:47:12 mail01 dovecot: imap(foo...@example.com): Error: Corrupted index cache file /home/vmail/example.com/foobar/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Broken virtual size for mail UID 3 So dovecot recreates the cache file but they are instant broken again? Any thoughts here? On 12.10.2014 14:54, Daniel Parthey wrote: > I think you could try to simply delete dovecot.index.cache file and have > dovecot automatically recreate it on the next delivery or login. And then see > if the error messages go away for this mailbox. > > With mdbox the dovecot.index file must not be deleted however, you would > otherwise lose "seen" flags. > > Anyway, better have a backup prepared, before deleting any files ;) > > Regards > Daniel >
Re: Dovecot domain quota
Am 12.10.2014 um 19:28 schrieb Filip Bartmann: > I have dovecot version 2.1.7 and I have quota configured as: > --- > dict { > quota_domain = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext > } > mail_plugins = quota > protocol imap { > mail_plugins = quota quota imap_quota > } > plugin { > quota = dict:domain:%d:proxy::quota_domain > quota_rule = *:storage=1M > quota_rule2 = Trash:storage=+100M > } > --- > /etc/dovecot/dovecot-dict-sql.conf.ext: > --- > map { > pattern = priv/quota/storage > table = quota_dict > username_field = domain > value_field = bytes > } > map { > pattern = priv/quota/messages > table = quota_dict > username_field = domain > value_field = messages > } > map { > pattern = shared/expire/$user/$mailbox > table = expires > value_field = expire_stamp > fields { > username = $user > mailbox = $mailbox > } > } > --- > But the problem is that quota table created as: > --- > CREATE TABLE `quota_dict` ( > `domain` varchar(255) NOT NULL, > `bytes` bigint(20) NOT NULL DEFAULT '0', > `messages` int(5) NOT NULL DEFAULT '0', > PRIMARY KEY (`domain`) > ) ENGINE=InnoDB DEFAULT CHARSET=latin1 > --- > counts quota only for last user as defined /etc/dovecot/users or in database > table. > So if I have in /etc/dovecot/users (the contents is from testing VPS): > --- > t...@debian.jd:{plain}radegast:8:8::/srv/mail/debian.jd/::userdb_quota_rule=*:storage=500k > bartm...@debian.jd:{plain}radegast:8:8::/srv/mail/debian.jd/::userdb_quota_rule=*:storage=500k > --- > After running `doveadm quota recalc -A` I have in my db: > --- > +---++--+ > | domain| bytes | messages | > +---++--+ > | debian.jd | 505758 | 81 | > +---++--+ > --- > whith is from account bartm...@debian.jd not both accounts at testing VPS > domain debian.jd. The same is with quota enforcing - quota if enforced on the > latter of the accounts in /etc/dovecot/users on testing machine or database > in production machine. > > What I do wrong? > Thanks > Filip Bartmann > domain quota may be tricky never tested but perhaps reread http://serverstutorial.wordpress.com/2012/12/28/configuring-domain-user-mailbox-quotas-in-dovecot-via-postfixadmin-on-ubuntu-12-04lts/ http://wiki2.dovecot.org/Quota/Configuration Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Dovecot domain quota
I have dovecot version 2.1.7 and I have quota configured as: --- dict { quota_domain = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } mail_plugins = quota protocol imap { mail_plugins = quota quota imap_quota } plugin { quota = dict:domain:%d:proxy::quota_domain quota_rule = *:storage=1M quota_rule2 = Trash:storage=+100M } --- /etc/dovecot/dovecot-dict-sql.conf.ext: --- map { pattern = priv/quota/storage table = quota_dict username_field = domain value_field = bytes } map { pattern = priv/quota/messages table = quota_dict username_field = domain value_field = messages } map { pattern = shared/expire/$user/$mailbox table = expires value_field = expire_stamp fields { username = $user mailbox = $mailbox } } --- But the problem is that quota table created as: --- CREATE TABLE `quota_dict` ( `domain` varchar(255) NOT NULL, `bytes` bigint(20) NOT NULL DEFAULT '0', `messages` int(5) NOT NULL DEFAULT '0', PRIMARY KEY (`domain`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 --- counts quota only for last user as defined /etc/dovecot/users or in database table. So if I have in /etc/dovecot/users (the contents is from testing VPS): --- t...@debian.jd:{plain}radegast:8:8::/srv/mail/debian.jd/::userdb_quota_rule=*:storage=500k bartm...@debian.jd:{plain}radegast:8:8::/srv/mail/debian.jd/::userdb_quota_rule=*:storage=500k --- After running `doveadm quota recalc -A` I have in my db: --- +---++--+ | domain| bytes | messages | +---++--+ | debian.jd | 505758 | 81 | +---++--+ --- whith is from account bartm...@debian.jd not both accounts at testing VPS domain debian.jd. The same is with quota enforcing - quota if enforced on the latter of the accounts in /etc/dovecot/users on testing machine or database in production machine. What I do wrong? Thanks Filip Bartmann
Re: Corrupted index cache after migrating from maildir to mdbox
I think you could try to simply delete dovecot.index.cache file and have dovecot automatically recreate it on the next delivery or login. And then see if the error messages go away for this mailbox. With mdbox the dovecot.index file must not be deleted however, you would otherwise lose "seen" flags. Anyway, better have a backup prepared, before deleting any files ;) Regards Daniel
CentOS x64 compilation fails.
Hello. I have problems to compile Dovecot2.2.13 with rpmbuild using options: ./configure \ --prefix=/usr \ --with-ssl=openssl \ --with-ssldir=/etc/ssl \ --sysconfdir=/etc \ --without-vpopmail \ --with-pam \ --without-bsdauth \ --without-sql \ --without-nss \ --without-ldap \ --without-pgsql \ --without-mysql \ --without-sqlite \ --with-rundir=/var/run/dovecot \ --without-deliver \ --without-gssapi make Using CentOS 5.11, option - rpmbuild -ba dovecot2.2.spec fails with error: /bin/mkdir -p '/var/tmp/dovecot-2.2.13-mp-root/usr/lib64/dovecot' /bin/sh ../../libtool --mode=install /usr/bin/install -c libdovecot-storage.la '/var/tmp/dovecot-2.2.13-mp-root/usr/lib64/dovecot' libtool: install: error: cannot install `libdovecot-storage.la' to a directory not ending in /usr/lib/dovecot make[4]: *** [install-pkglibLTLIBRARIES] Error 1 make[4]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.2.13/src/lib-storage' make[3]: *** [install-am] Error 2 make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.2.13/src/lib-storage' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.2.13/src/lib-storage' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.2.13/src' make: *** [install-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.14076 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.14076 (%install) But using CentOS 5.11with option- rpmbuild --target=i686 -ba dovecot2.2.spec works fine. However, using CentOS 6.5, with option - rpmbuild -ba dovecot2.2.spec fails with error: /bin/mkdir -p '/root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.x86_64/usr/lib64/dovecot' /bin/sh ../../libtool --mode=install /usr/bin/install -c libdovecot-storage.la '/root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.x86_64/usr/lib64/dovecot' libtool: install: error: cannot install `libdovecot-storage.la' to a directory not ending in /usr/lib/dovecot make[4]: *** [install-pkglibLTLIBRARIES] Error 1 make[4]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.13/src/lib-storage' make[3]: *** [install-am] Error 2 make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.13/src/lib-storage' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.13/src/lib-storage' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.13/src' make: *** [install-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.HP3meN (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.HP3meN (%install) But when CentOS 5.11with option rpmbuild --target=i686 -ba dovecot2.2.spec suceeds, CentOS 6.5still fails: cpio: dovecot-2.2.13/src/lib-compression/abspath.c: Cannot stat: No such file or directory cpio: dovecot-2.2.13/src/lib-compression/compat.h: Cannot stat: No such file or directory cpio: dovecot-2.2.13/src/lib-compression/lib.h: Cannot stat: No such file or directory 18096 blocks + /usr/lib/rpm/check-buildroot /root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.i386/usr/lib/dovecot/dovecot-config:LIBDOVECOT='-L/root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.i386/usr/lib/dovecot -ldovecot' /root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.i386/usr/lib/dovecot/dovecot-config:LIBDOVECOT_INCLUDE=-I/root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.i386/usr/include/dovecot Found '/root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.i386' in installed files; aborting error: Bad exit status from /var/tmp/rpm-tmp.69mGY0 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.69mGY0 (%install) How to fix these errors? -- Mart