- dovecot - dovecot.org

[Dovecot] virtual mailboxes folder structure
by Marco Cusano 06 Jan '14

06 Jan '14

Hi, I am trying to find a way to list my virtual mailboxes hiding the namespace prefix into my imap client. Fore example now my “All” mailbox is listed under virtual/ as: Inbox Sent Drafts Spam Trash virtual All I would like to list as this: Inbox Sent Drafts Spam Trash All This is my 10-mail.conf: http://pastebin.com/DumEbbmy and this is my 15-mailboxes.conf: http://pastebin.com/QFzWGzyC I thought that the list = children paramenter would do but it did not. Thank you

1 0

[Dovecot] virtual mailboxes folder structure
by Marco Cusano 06 Jan '14

06 Jan '14

Hi, I am trying to find a way to list my virtual mailboxes hiding the namespace prefix into my imap client. Fore example now my “All” mailbox is listed under virtual/ as: Inbox Sent Drafts Spam Trash virtual All I would like to list as this: Inbox Sent Drafts Spam Trash All This is my 10-mail.conf: http://pastebin.com/DumEbbmy and this is my 15-mailboxes.conf: http://pastebin.com/QFzWGzyC I thought that the list = children paramenter would do but it did not. Thank you

1 0

[Dovecot] [SIEVE] Locking Errors with vnd.dovecot.duplicate Extension
by Daniel Parthey 06 Jan '14

06 Jan '14

Hi, we are running a 4 host setup which each hosts a director+mailbox which is mounted via NFSv4 from a DRBD cluster. * Dovecot upstream release 2.1.16 * Doveadm batch subcommand fix - http://hg.dovecot.org/dovecot-2.1/raw-rev/850b5d8bbcc9 * Pigeonhole release 0.3.4 Now we would like to remove duplicate Mails using the vnd.dovecot.duplicate extension using a SIEVE script like this: require ["vnd.dovecot.duplicate", "fileinto", "mailbox", "regex", "vacation", "variables"]; if duplicate { fileinto :create "Trash"; } But as soon as we start delivering duplicate mails, we're sometimes getting locking errors from the mailbox (which is responsible for the user) according to the director: Dec 27 16:36:30 10.129.3.213 dovecot: lmtp(27975, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:33 10.129.3.213 dovecot: lmtp(27987, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:35 10.129.3.213 dovecot: lmtp(27994, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:36 10.129.3.213 dovecot: lmtp(28011, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:36 10.129.3.213 dovecot: lmtp(28013, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:38 10.129.3.213 dovecot: lmtp(28017, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:39 10.129.3.213 dovecot: lmtp(28025, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:42 10.129.3.213 dovecot: lmtp(28037, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Dec 27 16:36:43 10.129.3.213 dovecot: lmtp(27973, user001(a)example.org) Error: Creating lock file for /mail/dovecot/example.org/user001/.dovecot.lda-dupes timed out in 20 secs Configs and Error log is attached. Any idea how to mitigate these locking issues? Regards Daniel

1 0

[Dovecot] disable_plaintext_auth = yes not showing in doveconf -n output?
by Charles Marcus 04 Jan '14

04 Jan '14

I have it set, but it doesn't show up. However, I noticed that it does show as enabled by default in doveconf -a output. Is this why it doesn't show up in doveconf -n output? -- Best regards, Charles

4 5

[Dovecot] RFE: IMAP LIST Extension for Special-Use Mailboxes
by Patrick Ben Koetter 03 Jan '14

03 Jan '14

Timo, would you consider adding support for "IMAP LIST Extension for Special-Use Mailboxes" <http://www.rfc-editor.org/rfc/rfc6154.txt> any time near in the future? I would really love to get rid of all those folders created by all those different mail clients just because they can't agree to use the same folder for special purpose. Obviously clients need to support it too. Having Dovecot support it certainly would make them adopt the standard sooner. p@rick -- state of mind Digitale Kommunikation http://www.state-of-mind.de Franziskanerstraße 15 Telefon +49 89 3090 4664 81669 München Telefax +49 89 3090 4666 Amtsgericht München Partnerschaftsregister PR 563

10 17

[Dovecot] Allow both SSL/993 and STARTTLS/143 connections (secure only)
by Charles Marcus 03 Jan '14

03 Jan '14

Hi all, Ok, up until now, I've only always allowed IMAPS connections to dovecot on port 993. I want to also start allowing clients to user port143+STARTTLS, but I walso want to make sure both ports are locked down to ONLY allow secure connections. So... is disable_plaintext_auth = yes in the main config enough to accomplish this? http://wiki2.dovecot.org/SSL/DovecotConfiguration says: There are a couple of different ways to specify when SSL/TLS is required: * disable_plaintext_auth=yes allows plaintext authentication <http://wiki2.dovecot.org/Authentication/Mechanisms> only when SSL/TLS is used first. * ssl = required requires SSL/TLS also for non-plaintext authentication <http://wiki2.dovecot.org/Authentication/Mechanisms>. * If you have only plaintext mechanisms enabled (auth { mechanisms = plain login } ), you can use either (or both) of the above settings. They behave exactly the same way then and the comments in 10-auth.conf say: # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that if the remote IP # matches the local IP (ie. you're connecting from the same computer), the # connection is considered secure and plaintext authentication is allowed. # See also ssl=required setting. #disable_plaintext_auth = yes These seem to be saying that all I need to do is set either or both (ssl-required and/or disable_plaintext_auth=yes). I'm looking for the simplest, and don't like redundant/unnecessary settings, so... which is the best/preferred way? And what is the difference between ssl=required and disable_plaintext_auth=yes? Thanks, -- Best regards, */Charles/***

2 3

[Dovecot] How to remove Dovecot (LMTP) information from Email header
by Anant 02 Jan '14

02 Jan '14

Hello All, I want to remove Dovecot (LMTP) information from Email Header, Please help me. I am using Dovecot 2.0.9 with Exim. Received: from XX.XXblue.co.uk by XX.XXblue.co.uk*(Dovecot) with LMTP id* XIuTJkJFxVLKTwAAG2fxGQ for <anant.saraswat(a)techblue.co.uk>; Thu, 02 Jan 2014 10:59:28 +0000 Received: from [210.7.64.2] (helo=[192.168.100.71]) by solo.techblue.co.uk with esmtp (Exim 4.72) (envelope-from <sysadmin(a)techblue.co.uk>) id 1Vyfzr-0005Oy-7H for anant.saraswat(a)techblue.co.uk; Thu, 02 Jan 2014 10:59:28 +0000 Thanks & Regards, Anant Saraswat

2 2

[Dovecot] Problem building dovecot 2.2.10 with pigeonhole 0.4.2
by Nikolaos Milas 02 Jan '14

02 Jan '14

Hi, I am on CentOS 5.10 x86_64 and I am trying to build RPMs for Dovecot 2.2.10 with pigeonhole 0.4.2. I am getting an error that autogen.sh is missing from pigeonhole 0.4.2 source (as available from: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.2.tar…) /var/tmp/rpm-tmp.89185: line 92: /home/mockbuild/rpmbuild/BUILD/dovecot-2.2.10/dovecot-2.2-pigeonhole-0.4.2/autogen.sh: No such file or directory Indeed, the file is missing, as: tar --list -f dovecot-2.2-pigeonhole-0.4.2.tar.gz | grep autogen ...produces no output. However, I managed to use the latest source code: http://hg.rename-it.nl/dovecot-2.2-pigeonhole/shortlog/32beba3bfd8d which does contain an autogen.sh, and this package worked fine. I guess the released source tar pack should be updated? Thanks and regards, Nick

2 1

[Dovecot] Dovecot doesn't seem to read userdb for the first delivery
by phuhimself＠phunehehe.net 02 Jan '14

02 Jan '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello List, First of all, this is my first post so please bear with me if I miss something. I'm using Postfix with Dovecot 2.0.19 as the LDA. The home directory is of the form `/var/mail/virtual/<domain>/<username>`. The mail directory is under the home directory and named `mail`. `mail_location` is left empty, and userdb is specified using SQL: user_query = SELECT uid AS uid, \ gid AS gid, \ homedir AS home, \ maildir AS mail \ FROM users WHERE email = '%u' Everything had been fine, until I added a new user. In the log, Dovecot complains that it doesn't have permission to create the mail directory (email address replaced): > Jan 2 05:46:19 mail1 dovecot: lda(test(a)test.com): Error: user > test(a)test.com: > Initialization failed: Initializing mail storage from mail_location > setting > failed: mkdir(mail) in directory /var/spool/postfix failed: Permission > denied > (euid=5000(virtual) egid=5000(virtual) missing +w perm: > /var/spool/postfix, > dir owned by 0:0 mode=0755) Sometimes it complains about /run/dovecot instead of /var/spool/postfix, but I think that doesn't really matter. I think not specifying `mail_location` confused Dovecot, as explained in [MailLocation][1]. When I put in the right value for `mail_location` the error went away. What I don't understand is, it is said in the [same document][1] that the userdb field `mail` will override `mail_location` anyway. I would think that I can skip `mail_location` if I specify userdb `mail` for all users. Is the document wrong? Thanks, Phu [1]: http://wiki2.dovecot.org/MailLocation -----BEGIN PGP SIGNATURE----- Version: OpenPGP.js v.1.20131017 Comment: http://openpgpjs.org wsFcBAEBCAAQBQJSxRknCRD8UQvv5Zm+EAAAj68P/iidn6jYSNlhLY2640Qg vPC9xg0lhH/LJLEMMK+oSDnOmF+Hjtm/IMctOVDiTnPfdbvoC9oE4RWnKlL0 /couQQHQKjh2L2mqN50buROjUQyR+pQXGNfVGS+jq74S30299/VnH+gWPUSV xYRb1i6wuKVGCCNRF3vJHZs1eCiEFKpvC4LUiI5yarclCUE4mCtRO97Iadu/ GTaXn3euy5/5dyZEiPvld5IcGJ0BMC5RJiHb89EpN7A5J+4MvlMNUdcPYgcF j+ilwsOCpchj1AfjLnosnpCJRysin8aYj9mxGC+gR2/fAIm242qBNrVpnLQM IjP8G1pKhxKzQx2jFnENvhTKaxDSIWva0u/CSxSiCE3Kepj1b39qsjFlM8k7 0/EzoWf1rxzy0kQQ1qNeoz1Ta93D2cWQkTj6AK6kVmtmt9iaqzjGU+n7w3ae n+hoYs19r8LnhqSrlAX/N10h7/B++SRJG81EUB4tJF+LtRknFJa1qyr7Guh/ mOieUupr9Ks5WlPYaZ77t61FZauI0bK716p+J5C/f75EdWMrUInVumGletk/ FIaILS6nhq+D6SvrqiVseKvhjc+6p4HoeNVotceus+yssNmkniey5j3Hs0H5 EPmmkAT+hNN5R0wcbj2LaErG3VQ6SGMdY/suIJQb1Aq08nymtVaA2mS8Tcnm Z+O+ =pqon -----END PGP SIGNATURE-----

1 0

[Dovecot] Wrong file accessed after file was renamed because of wrong size
by Rolf Eike Beer 01 Jan '14

01 Jan '14

I'm migrating from Courier-IMAP. On first access of folders I get this log (slightly anonymized): Jan 1 18:38:27 mail dovecot: imap(username): Error: Cached message size smaller than expected (1452 < 1668) Jan 1 18:38:27 mail dovecot: imap(username): Error: Maildir filename has wrong S value, renamed the file from /var/vpopmail/domains/domain/username/.maildir/cur/1206559119.14350.mail,S=1452:2,RS to /var/vpopmail/domains/domain/username/.maildir/cur/1206559119.14350.mail,S=1668:2,RS Jan 1 18:38:27 mail dovecot: imap(username): Error: Corrupted index cache file /var/vpopmail/domains/domain/username/.maildir/dovecot.index.cache: Broken physical size for mail UID 161 Jan 1 18:38:27 mail dovecot: imap(username): Error: read(/var/vpopmail/domains/domain/username/.maildir/cur/1206559119.14350.mail,S=1452:2,RS) failed: Invalid argument Jan 1 18:38:27 mail dovecot: imap(username): Disconnected: Internal error occurred. Refer to server log for more information. [2014-01-01 18:38:27] in=135 out=63515 This is the same in 2.2.6 and 2.2.10. Greetings, Eike

1 0