January 2017 - dovecot

Unable to access apt.dovecot.fi
by Alexandre Ellert 12 Jan '17

12 Jan '17

Hi, I bought a Dovecot Enterprise repository acces in 2013 and since several months, I can't access it anymore. It seem that my credential are broken. When doing an apt-get update : W: Failed to fetch http://apt.dovecot.fi/3rdparty/debian/wheezy/dists/wheezy/main/binary-amd64… 401 Unauthorized W: Failed to fetch http://apt.dovecot.fi/stable-2.2/debian/wheezy/dists/wheezy/main/binary-amd… 401 Unauthorized And here is my sources.list : # cat /etc/apt/sources.list.d/dovecot.list deb http://USER:PASSWORD@apt.dovecot.fi/stable-2.2/debian/wheezy wheezy main # cat /etc/apt/sources.list.d/dovecot-3rdparty.list deb http://USER:PASSWORD@apt.dovecot.fi/3rdparty/debian/wheezy wheezy main Thank you for help. Alexandre

2 1

Broken OS after upgrade
by Odhiambo Washington 11 Jan '17

11 Jan '17

Hi, I have broken my OS (FreeBSD) after upgrade, making me unable to compile dovecot the usual way so I am seeking a 3rd eye. The config.log is at : http://bit.ly/2jE5djl Hoping someone can help me figure out what is broken. During configure, it fails with: checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... unknown checking for _LARGE_FILES value needed for large files... unknown checking for _Bool... yes checking for uoff_t... no checking type of off_t... unknown configure: error: Unsupported off_t type -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft."

2 2

multiple shared/mail format namespaces
by Michal Soltys 11 Jan '17

11 Jan '17

Hi, Are configurations (with separate formats per namespace) - such as ... namespace { type = shared list = children inbox = no separator = / subscriptions = no prefix = shared1/%%n/ location = maildir:/var/mail1/%%n/ } namespace { type = shared list = children inbox = no separator = / subscriptions = no prefix = shared2/%%n/ location = mdbox:/var/mail2/%%n/ } With separate userdbs serving part of the users with maildirs in /var/mail1/ and the other part with mdboxes in /var/mail2 ... valid in dovecot ? To be more precise: 1) Is current version dovecot expected to work with configuration as above ? E.g. if some user's mail location returned from userdb doesn't match location/format from one of the above namespaces - would it be ignored for it ? A very old version of dovecot I could check quickly (2.1.7) was segfaulting (imap processes) all the time with this kind of config. While I'll be upgrading it and the whole system to modern versions, I'm wondering if this kind of thing is formally allowed at all. An interesting variation of the above setup I tested - with the second namespace "un-variabled" and pointing to single user (with matching passwd-file returning that user) managed to work somehow - but the user itself was still created on the fly for the 1st namespace - having just a directory with empty dovecot-acl-list file. This essentially seemed to have worked like a typical public profile (shared acl db didn't seem to be used either) 2) For shared namespace with variables, would overriding shared namespace location in userdb query work ? For example if we had single namespace such as the first one (maildir) above with explicit share1 name, and then in userdb for some users: userdb_namespace/share1/location=mdbox:/var/mail2/some_user_name Would that override a shared namespace pattern on per user basis correctly ? 3) Is there perhaps a way to constraint which userdbs are considered per which shared namespace ? 4) Not strictly related to the above, but in LDAP part of documentation - namely http://wiki2.dovecot.org/AuthDatabase/LDAP/Userdb - why user_attrs = \ =home=%{ldap:homeDirectory}, \ =uid=%{ldap:uidNumber}, \ =gid=%{ldap:gidNumber} instead of user_attrs = \ homeDirectory=home, \ uidNumber=uid, \ gidNumber=gid Do both are equivalent with differet syntax (opening the way for templates for %{} based syntax), or are there some subtle differences between those ? (aside later example with 'attr=' instead of just '='). Would this kind of syntax also be correct for pass_attrs, such as: pass_attrs = \ =password=%{ldap:uid}, \ =userdb_home=%{ldap:homeDirectory}

3 6

Ban dots in folder names
by Marek Grondecki 11 Jan '17

11 Jan '17

Hello Dovecot Community, I am using Dovecot 2.2.13-12~deb8u1 (Debian Jessie). separator = / listescape plugin is NOT active LAYOUT=fs is NOT active I would like to prohibit/ban the creation of folders with dot "." in the names - so creation of a folder "foo.bar" should NOT be possible. Currently, when I create "foo.bar" in Outlook 2013 it will be created but won't be synchronised with the mail server - Outlook shows it as "foo.bar (Only this computer)". Ideally the user should receive an error message informing that "the folder foo.bar could not be created." Thank you for your help. Regards, Marek Grondecki

2 1

pigeonhole + spamprobe
by Mark Constable 11 Jan '17

11 Jan '17

Would anyone have an example of how to use dovecot-pigeonhole to call spamprobe as an external program in the current 2.2.25?

1 0

Dovecot and MariaDB/MySQL
by Michael A. Peters 11 Jan '17

11 Jan '17

Howdy - For most of my dovecot servers, they are small and I just use unix accounts. However I am going to be running a new server for more general users, webmail (probably roundcube but I'm hacking roundcube quite a bit, enough that I'm calling it squarepeg instead so users familiar with roundcube will know it is quite different) and it will use MariaDB for account management. I already have it working, following the instructions at https://www.linode.com/docs/email/postfix/email-with-postfix-dovecot-and-my… - those instructions also work in CentOS 7 with the latest Dovecot - but there is something that really bothers me. It makes no provision for salting the password before the crypt function. What I would like to do is when creating a new account, use /dev/urandom to generate a random salt for the account that is stuck in the database along with the account and used when validating the password. That way in the event of a SQL injection attack that dumps the database - yes it is still bad, but 20 accounts that have the same password will have radically different hashes and thus won't be a clue that they are the same, the blackhat that gets the database dump would have to generate a rainbow table for each unique salt. I've looked at at least a dozen different Dovecot / MariaDB howto guides and none of the ones I have looked at supported any kind of individual salting of the user passwords. Can someone point me to a guide that does? I don't mind keeping the salt in the database, I just want to be able to have a different salt for each account. Thank you

2 2

GMail-like user labels in IMAP/dovecot, situation in 2017?
by Gioele Barabucci 11 Jan '17

11 Jan '17

Hello, I am in the process of updating my IMAP dovecot installation and I was wondering what is the current state of the art for GMail-like user-defined labels. Are GMail-like user-defined labels now somehow achievable with dovecot? If now, what is missing? Standardized metadata formats? Support in clients? I searched the web a bit but I could not find any activity in the relevant IETF working groups. That seems strange to me, because the user-defined labels looks like a feature many users would like to have. I suppose I haven't found the relevant discussion group. Is this kind of enhancement to IMAP being discussed somewhere? Regards, -- Gioele Barabucci <gioele(a)svario.it>

2 2

Poolmon: Problem with index-locking
by Tom Sommer 11 Jan '17

11 Jan '17

I have Poolmon (https://github.com/brandond/poolmon) set up. When it does all the checks concurrently, obviously there are locking issues on each mailserver it tests: "Warning: Locking transaction log file xxxx/indexes/dovecot.list.index.log took 60 seconds (syncing)" It's just an empty mailbox. Is there any way to do a login test, without locking the index files? Hence avoiding these warnings/errors? Thanks. -- Tom

2 2

doveadm output format changes
by Benoit Branciard 10 Jan '17

10 Jan '17

It appears that doveadm output format changes every now and then, without particular notice. For example, the following command: doveadm -f pager mailbox status 'messages recent' '*' did output something like this until v2.2.24 : mailbox: Mailbox1 messages: 58 recent: 12 ^L mailbox: Mailbox2 messages: 128 recent: 0 but switched to that in v2.2.26 : Mailbox1 messages: 58 recent: 12 ^L Mailbox2 messages: 128 recent: 0 This seems related to the following changelog entry: 2016-10-25 20:51:36 +0300 Timo Sirainen <timo.sirainen(a)dovecot.fi> (5baa99e) doveadm: "pager" formatter supports now DOVEADM_PRINT_HEADER_FLAG_HIDE_TITLE M src/doveadm/doveadm-print-pager.c Some other format changes did also occur in the past. For example, "doveadm user" had a specific format in v2.0.19 (and ignored the "-f format" option), and obviously defaulted to the "-f tab" format (which has different rendering) somewhere in the v2.2.x or 2.1.x. Such changes render maintenance of wrapping scripts particularly tedious. Could it be possible to avoid such breaking changes in the future ? -- Benoit BRANCIARD Service InfraStructures (SIS) Direction du Système d'Information et des Usages Numériques (DSIUN) Université Paris 1 Panthéon-Sorbonne Centre Pierre Mendès France 90 rue de Tolbiac - 75634 Paris cedex 13 - France Bur. B406 - Tél +33 1 44 07 89 68 - Fax +33 1 44 07 89 66 Accueil: +33 1 44 07 89 65 - Assistance-DSIUN(a)univ-paris1.fr http://dsi.univ-paris1.fr

1 1

Re: dovecot-pigeonhole running external script ends with signal 11
by Stephan Bosch 10 Jan '17

10 Jan '17

Op 1/8/2017 om 10:00 AM schreef Tobi: > Hi Stephan > > according to ps aux the process that segfaults is (pid 18261) > > vmail 18261 0.0 0.0 0 0 pts/0 Z 09:39 0:00 [lmtp] > <defunct> > > the gdb backtrace I attached to my mail was the deepest one I got That looks like it happens in Dovecot still. > @Steffen > the script does not chroot, at least not that I'm aware of. I checked my > dovecot configs and could not find any active chroot config. All > occurences of mail_chroot are commented out and have no path values. What about the version information I asked about? Regards, Stephan. > Am 06.01.2017 um 00:04 schrieb Stephan Bosch: >> Op 1/4/2017 om 9:37 AM schreef Tobi: >>> Hi Aki >>> >>> yes I built dovecot and pigeonhole rpms in the same rpmbuild. pigeonhole >>> rpm is based on 0.4.14 >>> Do you think that the error might come from self building the rpms? >> But what version of Pigeonhole are you actually using? Version 0.4.16 is >> released for Dovecot v2.2.26. >> >> Also: >> >> - Can you find out which process is getting the segfault? GDB shows the >> pid and you should lookup what process that is while GDB is still active. >> - Isn't that GDB backtrace you provided deeper? It shows only two >> levels, but that makes no sense (i.e. main() is not listed). >> >> Regards, >> >> Stephan. >>

4 4