- dovecot - dovecot.org

[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

[Dovecot] How to add dovecot plugin?
by Timothy Murphy 31 Dec '13

31 Dec '13

I'm running dovecot version 2.0.9 under CentOS-6.5 . I want to add the following plugin: ==================== require "fileinto"; if header :contains "X-Spam-Flag" "YES" { fileinto "Spam"; } ==================== Could some kind soul tell me where exactly I should place this script (eg "anywhere in /etc/dovecot/dovecot.conf" or "anywhere in /etc/dovecot/conf.d/90-plugin.conf"), and do I need to take any other action? Actually, the folder I should like spam to go to is ~/Maildir/.Spam/cur/ - should I modify the above script? If these queries are anwered clearly in some dovecot documentation, please point me to that. -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

2 1

Re: [Dovecot] pop3 rate limit
by michael 30 Dec '13

30 Dec '13

On 2013-12-29 02:05, Christian Rößner wrote: > Hi, > > we have customers with Exchange servers that are polling for new mail > every minute with dozens of pop3 accounts. I am looking for a > mechanism to rate limit this per user. So what I am looking for is a > way to block users from polling, if a user asks for new mail more > than > every 5 minutes (for example). > > Is this possible? Can this be achieved within Dovecot or does it need > external scripting? (I thought about fail2ban, but also want IPv6 > support) > > Thanks in advance > > -Christian Rößner See: www.policyd.org You'll need to use v2.1 to get IPV6 support. Michael Hallager

6 10

[Dovecot] Warning: fscking index file /.../dovecot.index
by Alex Vitola 30 Dec '13

30 Dec '13

We have often found the below error in VPS servers using OpenVZ, and some cases using OpenStack, in neither case is used for storage or sharing ISCSI or NFS Client can not receive messages via POP3 or IMAP In /var/log/maillog the message below is seen Oct 31 15:28:26 vps dovecot: pop3(user(a)domain.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718e07400] -> /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718e07456] -> /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718e06df3] -> /usr/lib64/dovecot/libdovecot-storage.so.0 [0x2b3718b6566b] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x89) [0x2b3718b5ced9] -> /usr/lib64/dovecot/libdovecot-storage.so.0 [0x2b3718aeae4d] -> /usr/lib64/dovecot/libdovecot-storage.so.0 [0x2b3718aea357] -> /usr/lib64/dovecot/libdovecot-storage.so.0 [0x2b3718aea698] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xbb) [0x2b3718aea83b] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x2b3718b15e31] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x2b3718b18537] -> dovecot/pop3(client_create+0x332) [0x405702] -> dovecot/pop3 [0x40414b] -> dovecot/pop3 [0x404708] -> /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718dc9a52] -> /usr/lib Both POP3 as IMAP Oct 31 15:24:42 vps dovecot: imap(user(a)domain.com): Warning: fscking index file /home/user/mail/domain.com/user/dovecot.index Oct 31 15:28:26 vps dovecot: pop3(user(a)domain.com): Warning: fscking index file /home/user/mail/domain.com/user/dovecot.index Today I do to solve this the procedure below - Access the directory mailbox - Remove files dovecot.index * - Run the command doveadm index-u $ user @ $ domain-q INBOX The question is for what reason this only occurs with VPS servers, I do not find this error on any single physical server to virtual and dovecot settings are the same. att Alex Vitola

1 0

[Dovecot] dovecot 2.2.10 - imap: Error: Can't load plugin imap_stats_plugin:
by giovanni＠neweden.uk.to 30 Dec '13

30 Dec '13

dovecot 2.2.10 is raising this error on my installation. Dec 30 13:57:59 imap: Error: Can't load plugin imap_stats_plugin: Plugin stats must be loaded also (you must set: mail_plugins=$mail_plugins stats) Dec 30 13:57:59 imap: Fatal: Couldn't load required plugins This error occurs at logging phase. The dovecot configuration looks correct to me, here below an excerpt of it: ... ... mail_plugins=$mail_plugins stats protocol imap { mail_plugins = $mail_plugins imap_stats } plugin { # how often to session statistics stats_refresh = 30 secs # track per-IMAP command statistics stats_track_cmds = yes } ... ... I was already using this configuration but only now I am getting this error. From STRACE I see that the stat plugin is correctly localed . Is anybody else getting this error? or am I missing something? Here below an except of the strace message. [pid 17112] open("/usr/local/lib/dovecot/lib95_imap_stats_plugin.so", O_RDONLY) = 14 [pid 17112] read(14, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\t\0\0004\0\0\0"..., 512) = 512 [pid 17112] fstat64(14, {st_mode=S_IFREG|0755, st_size=53122, ...}) = 0 [pid 17112] mmap2(NULL, 8908, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 14, 0) = 0xf7609000 [pid 17112] mmap2(0xf760b000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 14, 0x1) = 0xf760b000 [pid 17112] close(14) = 0 [pid 17112] open("/usr/local/lib/dovecot/lib90_stats_plugin.so", O_RDONLY) = 14 [pid 17112] read(14, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0@\24\0\0004\0\0\0"..., 512) = 512 [pid 17112] fstat64(14, {st_mode=S_IFREG|0755, st_size=100054, ...}) = 0 [pid 17112] mmap2(NULL, 20320, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 14, 0) = 0xf7604000 [pid 17112] mmap2(0xf7608000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 14, 0x3) = 0xf7608000 [pid 17112] close(14) = 0 [pid 17112] write(2, "\1\01017112 prefix=imap: \n", 22) = 22 [pid 17112] write(2, "\1\00417112 Can't load plugin imap_s"..., 127) = 127 [pid 17112] munmap(0xf7609000, 8908) = 0 [pid 17112] munmap(0xf7604000, 20320) = 0 [pid 17112] write(2, "\1\00517112 Couldn't load required p"..., 39) = 39 [pid 17112] exit_group(89) = ? Process 17112 detached

2 2