- dovecot - dovecot.org

dovecot.index.pvt view is inconsistent: error messages for public mailbox folder
by Andreas Ntaflos 04 Jan '17

04 Jan '17

Hi list, running Dovecot 2.2.27 on Ubuntu 14.04. A public mailbox "Public/Spam-Learning" in a public namespace with per-user "Seen" flags is configured like this: namespace pub { hidden = no inbox = no list = children location = maildir:/var/vmail/public:INDEXPVT=~/Maildir/public prefix = Public/ separator = / subscriptions = no type = public mailbox "Spam-Learning" { auto = subscribe } } The log files are full of error messages like these (got about 15000 in the last three days): 2017-01-03T11:19:28.242386+01:00 mailserver01 dovecot: imap(foo.bar(a)example.org): Error: /var/vmail/example.org/foo.bar/Maildir/public/.Spam-Learning/dovecot.index.pvt reset, view is now inconsistent 2017-01-03T11:19:28.248524+01:00 mailserver01 dovecot: imap(foo.bar(a)example.org): Error: /var/vmail/example.org/foo.bar/Maildir/public/.Spam-Learning/dovecot.index.pvt view is inconsistent 2017-01-03T11:23:50.209732+01:00 mailserver01 dovecot: imap(baz.quux(a)example.org): Error: /var/vmail/example.org/baz.quux/Maildir/public/.Spam-Learning/dovecot.index.pvt reset, view is now inconsistent 2017-01-03T11:23:50.775940+01:00 mailserver01 dovecot: imap(some.user(a)example.org): Error: /var/vmail/example.org/some.user/Maildir/public/.Spam-Learning/dovecot.index.pvt reset, view is now inconsistent 2017-01-03T11:25:38.419536+01:00 mailserver01 dovecot: imap(other.user(a)example.org): Error: /var/vmail/example.org/other.user/Maildir/public/.Spam-Learning/dovecot.index.pvt reset, view is now inconsistent 2017-01-03T11:34:14.351346+01:00 mailserver01 dovecot: imap(more.user(a)example.org): Error: /var/vmail/example.org/more.user/Maildir/public/.Spam-Learning/dovecot.index.pvt reset, view is now inconsistent 2017-01-03T11:41:37.488916+01:00 mailserver01 dovecot: imap(support.user(a)example.org): Error: /var/vmail/example.org/support.user/Maildir/public/.Spam-Learning/dovecot.index.pvt reset, view is now inconsistent This problem did not seem to manifest itself in Dovecot 2.2.25, we see it only after upgrading to 2.2.27. I am not sure what the effects are. It seems that messages moved to the Public/Spam-Learning folder are deleted after a short while (not by the sa-learn cron job, which runs every morning) but I currently cannot say if this is because a user deletes them explicitly or because Dovecot does something it shouldn't. So this observation is possibly not relevant. It also doesn't seem to matter what kind of IMAP client access the Spam-Learning folder. Our users use Thunderbird, Apple Mail, Outlook, Roundcube, Horde and various mobile clients as well. I have attached the output of doveconf -n for reference. What could be the issue here? Are we doing something wrong or is this a bug in Dovecot? Thanks! Andreas

1 0

expunging all mailboxes
by Michael Fox 03 Jan '17

03 Jan '17

Evidently, the 'doveadm expunge' command requires a "mailbox" to be defined in the search string. But is there a way tell it all mailboxes for a user? For example, something like: doveadm expunge -u user@domain mailbox ALL savedbefore 30d Thanks, Michael

4 10

two listeners with different "driver = " configs
by mj 03 Jan '17

03 Jan '17

Hi, I would like to have two seperate imap listeners, with different authentication settings, but the mailstore and userbase etc will be identical. I know I can do this: > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imap2 { > port = 144 > } > } But I'm unsure how to configure imap/143 with "driver = ldap" and imap2/144 with "driver = pam" Just to explain why i would like this: I am using pam-script-saml (https://github.com/ck-ws/pam-script-saml) to enable saml-based access to dovecot. I would like to have one listener 144 to only serve this saml authentication listener, and the regular 143 listener with driver = ldap. Is that config possible? Best regards, MJ

5 10

differential SETACL silently fails if no vfile exists
by Vincent Breitmoser 02 Jan '17

02 Jan '17

In version 2.2.13, with `acl = vfile`, setting a differential ACL permission doesn't work if there are no permissions set yet. Example IMAP log: b1 GETACL test * ACL test valodim lrwstipekxacd b1 OK Getacl completed. b2 SETACL test valodim -l b2 OK Setacl complete. b3 GETACL test * ACL test valodim lrwstipekxacd b3 OK Getacl completed. My expectation was that the file would be created with default permissions, and the requested change then applied. However, no acl permission is set and no vfile is created for this mailbox in the process. This does work as expected (and a file is created) if I set a non-differential ACL first: b4 SETACL test valodim lrwstipekxacd b4 OK Setacl complete. b5 GETACL test * ACL test valodim akxeilprwtscd b5 OK Getacl completed. b6 SETACL test valodim -l b6 OK Setacl complete. b7 GETACL test * ACL test valodim akxeiprwtscd b7 OK Getacl completed. - V

1 0

dovecot and sssd
by Günther J. Niederwimmer 02 Jan '17

02 Jan '17

Hello, is there a way to configure dovecot over sssd ? like driver = sss Thanks for a answer, -- mit freundlichen Grüssen / best regards Günther J. Niederwimmer

2 1

Re: FreeBSD / dovecot 2.2.27 / libwrap
by Jim Pazarena 30 Dec '16

30 Dec '16

It works ! It was THAT easy ! Can you suggest how to replace the hair I pulled out ? :-) On 2016-12-29 5:27 PM, Larry Rosenman wrote: > login_access_sockets = tcpwrap > > service tcpwrap { > unix_listener login/tcpwrap { > group = $default_login_user > mode = 0600 > user = $default_login_user > } > } > > > > On Thu, Dec 29, 2016 at 7:21 PM, Jim Pazarena <dovecot(a)paz.bz> wrote: > >> I have compiled dovecot2 for FreeBSD with the tcpwrap option. >> >> A tcpwrap binary gets built and resides in the FreeBSD directory >> /usr/local/libexec/dovecot >> >> an examination of the compiled options (using the FreeBSD pkg install >> dovecot2) confirms: LIBWRAP : on >> >> yet, when I adjust dovecot.conf with: login_access_sockets = tcpwrap >> >> I get the following logged error message: >> >> 20161229 17:02:49 imap-login: Error: connect(tcpwrap) failed: No such file >> or directory >> >> Is there any way to turn up some super logging so that I can find just >> what dovecot feels is the failure ? >> >> Or, does anyone have an idea how to figure this out? What little hair I >> have is rapidly getting pulled out in frustration! >> >> Thank you. >> >> >> >> -- >> Jim Pazarena dovecot(a)paz.bz >> > > -- Jim Pazarena dovecot(a)paz.bz

2 1

FreeBSD / dovecot 2.2.27 / libwrap
by Jim Pazarena 30 Dec '16

30 Dec '16

I have compiled dovecot2 for FreeBSD with the tcpwrap option. A tcpwrap binary gets built and resides in the FreeBSD directory /usr/local/libexec/dovecot an examination of the compiled options (using the FreeBSD pkg install dovecot2) confirms: LIBWRAP : on yet, when I adjust dovecot.conf with: login_access_sockets = tcpwrap I get the following logged error message: 20161229 17:02:49 imap-login: Error: connect(tcpwrap) failed: No such file or directory Is there any way to turn up some super logging so that I can find just what dovecot feels is the failure ? Or, does anyone have an idea how to figure this out? What little hair I have is rapidly getting pulled out in frustration! Thank you. -- Jim Pazarena dovecot(a)paz.bz

2 1

doveadm expunge -A Error: Dictionary commit failed
by Alessio Cecchi 29 Dec '16

29 Dec '16

Hi, with the latest dovecot-ee version (dovecot-ee-2.2.26.1-10) if I run “doveadm expunge -A mailbox Spam savedbefore 30d” dovecot an error: doveadm: Error: dict-client: Commit failed: Dict server timeout: No input for 1916.209 secs (1 commands pending, oldest sent 0.000 secs ago: C1) (reply took 0.000 secs) doveadm: Error: expire: Dictionary commit failed Probably also "doveadm quota recalc -A" fail. Everything worked fine up to version 2.2.24 I hope can be fixed. Thanks -- Alessio Cecchi Postmaster AT http://www.qboxmail.it http://www.linkedin.com/in/alessice

3 6

dovecot-ldap.conf.ext for FreeIPA usage
by Matt . 29 Dec '16

29 Dec '16

Hello, I'm figuring out how to auth users against FreeIPA and I wonder if someone did this without GSAPI. My users are stored in a mysql DB where I wonder what I shall use as authname, the username or the mailaddress. As the mailaddress is always unique it could be best but if a user has multiple mailaddresses under seperate domains username might be better. Any clue here and maybe an example for dovecot-ldap.conf.ext when using FreeIPA ? Thanks! Matt

2 1

IPv4/IPv6 mismatches of doveadm: Fatal: connect(fd00:b::1:12345) failed: Connection refused
by Michael Grimm 28 Dec '16

28 Dec '16

Hi — I recently extendend my IPsec tunnel between two mail servers to deal with IPv4 addresses in addition to IPv6 ones. (No specific reason for that.) I ran into an issue worth reporting. This is Dovecot v2.2.27 (c0f36b0) at FreeBSD STABLE-11. Previously: dovecot.conf: plugin { mail_replica = tcp:remote.test } service doveadm { inet_listener { address = [::] } } | local> host remote.test: remote.test has IPv6 address fd00:b::1 working well. Currently: dovecot.conf: plugin { mail_replica = tcp:remote.test } service doveadm { inet_listener { address = * } } | local> host remote.test: remote.test has address 10.2.0.1 remote.test has IPv6 address fd00:b::1 Now, Replication stops and throws an error like: | <mail.crit> local.test dovecot: doveadm(user): Fatal: connect(fd00:b::1:12345) failed: Connection refused If I either #) remove IPv6 from my lokal DNS, #) use "mail_replica = tcp:10.2.0.1", or #) define the appropriate IPv4 address of remote.test in /etc/hosts, then replication works as usual. Hmm, shouldn't doveadm be more persistent in using every IP address of that entry of mail_replica *before* throwing a "Fatal:" error? Or do I miss something, and it's a feature, instead? Regards, Michael

1 0