- dovecot - dovecot.org

[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

[Dovecot] dsync-local crashes due to assertion failures
by Fabian Groffen 30 Dec '13

30 Dec '13

Hi, I have two servers that share nothing, running dovecot version 2.2.9. The first server hosts the original mail base, which I want to sync using dovecot to the second server. With some trial and error I managed to get synchronisation running using tcp sockets. Now for some accounts I see dsync-local crashing on the server that has the original mail base (which is still the only of the two that receives new mail). The log shows: Dec 8 03:13:14 zeus dovecot: dsync-local(someuser): Panic: file mail-index-tr ansaction-export.c: line 203 (log_append_ext_hdr_update): assertion failed: (u32 .offset + u32.size <= ext_hdr_size) Dec 8 03:13:14 zeus dovecot: dsync-local(someuser): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x70ea0) [0x7f3ee4137ea0] -> /usr/lib64/dovecot/libdovecot.so.0(+0x70efe) [0x7f3ee4137efe] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f3ee40ebd2c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_transaction_export+0xbed) [0x7f3ee442e89d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x89104) [0x7f3ee442d104] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_transaction_commit_full+0xb2) [0x7f3ee442d592] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_transaction_commit+0xc) [0x7f3ee442d63c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0xb6) [0x7f3ee44372b6] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x335d6) [0x7f3ee43d75d6] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x328bc) [0x7f3ee43d68bc] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x32d83) [0x7f3ee43d6d83] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xd9) [0x7f3ee43d7199] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x2e) [0x7f3ee43e7f2e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7f3ee43e8047] -> dovecot/doveadm-server(dsync_brain_master_send_mailbox+0xcf) [0x41f17f] -> dovecot/doveadm-server(dsync_brain_run+0x2c8) [0x41d738] -> dovecot/doveadm-server() [0x41dd70] -> dovecot/doveadm-server() [0x42eda0] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f3ee41495a6] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0xbd) [0x7f3ee414a62d] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f3ee4149008] -> dovecot/doveadm-server() [0x41bb6c] -> dovecot/doveadm-server() [0x40ee3b] -> dovecot/doveadm-server() [0x419581] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f3ee41495a6] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0xbd) [0x7f3ee414a62d] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f3ee4149008] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f3ee40f1643] Dec 8 03:13:14 zeus dovecot: dsync-local(someuser): Fatal: master: service(doveadm): child 14116 killed with signal 6 (core dumps disabled) It seems that despite these crashes, some data is being transferred. Newer accounts seem not to have problems, this happens with older accounts only, for as far as I can see. I tried removing the index files, but that didn't seem to help. Any ideas on what I can do here? Both servers are configured to use maildir storage. Thanks, Fabian -- Fabian Groffen Gentoo on a different level

1 1

[Dovecot] pop3 rate limit
by Christian Rößner 30 Dec '13

30 Dec '13

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 -- [*] 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, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

2 1

[Dovecot] Sieve's spamtest always returns 0
by martin f krafft 28 Dec '13

28 Dec '13

I am a bit at a loss here with Sieve (pigeonhole) and the spamtest extension. I am using Dovecot 2.1.7 (backported to Debian squeeze), which comes with Pigeonhole 0.3.0. Messages are scanned with SpamAssassin, which adds a header like X-Spam-Status: Yes, score=84.6 required=5.0 tests=… and so I configured spamtest in conf.d/90-plugin.conf like so: sieve_spamtest_status_type = score sieve_spamtest_status_header = X-Spam-Status: [^,]*, score=(-?[[:digit:]]+\.[[:digit:]]).* sieve_spamtest_max_header = X-Spam-Status: [^,]*, score=[^[:space:]]+ required=(-?[[:digit:]]+\.[[:digit:]]).* I tested those regular expressions with sed -r, e.g. % sed -rne "s@^X-Spam-Status: [^,]*, score=-?[[:digit:]]+\.[[:digit:]] required=(-?[[:digit:]]+\.[[:digit:]]).*@\1@p" mailfile 5.0 and they work. Unfortunately, in sieve scripts, the spamtest value is always 0, which is indicative of the spamtest "not having run", which in this case I assume means that the regular expression didn't match. Am I right in assuming that the matching happens at the time of evaluation, and so adding the headers using vnd.dovecot.filter just before works? Or does the spamtest matching happen before the sieve scripts are executed? Can you see any other reason why spamtest always yields a value of 0? Thanks, -- martin | http://madduck.net/ | http://two.sentenc.es/ "those who are faithful know only the trivial side of love: it is the faithless who know love's tragedies." -- oscar wilde spamtraps: madduck.bogus(a)madduck.net

3 4

[Dovecot] Dovecot 'Submission' service?
by Charles Marcus 27 Dec '13

27 Dec '13

I do recall this being discussed, but I can't remember if it is actually in a working state now or not. According to the wiki, it is a work in progress: http://wiki2.dovecot.org/Roadmap?highlight=%28submission%29 So - is it in a functional state yet? Thanks, -- Best regards, */Charless/***

2 2

[Dovecot] Using DSync to convert from maildir to m/sdbox during migration of mail to new server
by Charles Marcus 27 Dec '13

27 Dec '13

Ok, now to work out the precise method (config for the target server and dsync command) to use to perform the migration from the old server to the new one, converting to dbox (s or m, depending on how the other thread discussing this turns out). I'll update the old server to 2.2.10 tomorrow morning so they're both at the same version. So, assuming both servers are running 2.2.10, with OldServer: mail_location = maildir:~/:INDEX=MEMORY and NewServer: mail_location = sdbox:~/sdbox or mail_location = mdbox:~/mdbox After reading and re-reading: http://wiki2.dovecot.org/Tools/Dsync I'm not so sure... First problem - apparently it can only be used one user at a time? And - do you have to actually know the users password too? If so, then this probably isn't going to be easier, and maybe even harder than just rsyncing everything, then slowly converting each user one at a time. -- Best regards, */Charles/*

1 0

[Dovecot] Migrating from Maildir to dbox+SIS... sdbox or mdbox?
by Charles Marcus 27 Dec '13

27 Dec '13

Ok... Now that I've got the niggling issues resolved, on to bigger and better things. I want to convert everyone from Maildir to dbox and enable SIS (our users use a lot of large attachments), and after some reading/googling, I think it may be better to use dsync instead of rsync for the actual migration after all since it will do this at the same time as the syncing. If I'm not mistaken, once I've figured out the correct syntax for the command, I should be able to do the conversion and migration at the same time. So, that is what I want to do, but I still have to choose between sdbox and mdbox. I tend to feel a little safer with sdbox, just because it seems more stable - and I like the idea that if a file gets corrupted somehow, then it is only that one mail that may potentially be lost, but if mdbox indexes get corrupted, you are guaranteed to lose messages (maybe a lot)... But I also really like the idea of an order of magnitude fewer actual files (would make rsync based backups much faster, etc). Timo - the last comments I was able to find from you were back in 2011... would you mind commenting on the current stated of dbox - especially mdbox, as far as reliability goes? The 'scary warnings' about how important the index files are ... well ... scares me... ;) I know there were definitely some issues with mdbox a few years ago - I found the old thread from 2011, but nothing substantial since, so... So... are there any people here, especially larger installs, using mdbox? sdbox? I'd especially be interested in hearing from anyone who has used both, and picked one over the other, and their reasons for doing so. Thanks, -- Best regards, */Charles/*

1 0

[Dovecot] Enabling SIS (single instance storage)
by Charles Marcus 27 Dec '13

27 Dec '13

Ok, didn't find much on this... The bottom of /etc/dovecot/conf.d/10-mail.conf has the following settings: #mail_attachment_dir = #mail_attachment_min_size = 128k #mail_attachment_fs = sis posix #mail_attachment_hash = %{sha1} all of which are apparently the defaults according to doveconf -d output - so no need to set them explicitly, unless I want to change them, right? So, enable the first one - but - the comments don't say anything about supporting variables. I'm assuming you can, otherwise all attachments for all domains would be in a single directory, which some admins might not like (I wouldn't)... so hopefully I can just set it to this: mail_attachment_dir = /var/vmail/%d/.attachments So how does this work during conversion? Users still on maildir simply don't engage it? But as users are converted to dbox, all attachments are de-duped, and then new mails coming in with attachments (for converted users) are de-duped at delivery? The wiki could do with a bit more on enabling and implementing it, especially what to expect when enabling it for the first time on a production system and what to expect along the way when converting existing users... -- Best regards, */Charles/*

1 0

[Dovecot] mail_location, user 'home', questions
by Charles Marcus 27 Dec '13

27 Dec '13

Hi all, Ok, another question... I always like changes to the default settings whenever possible (KISS principle)... So, according to the dovecot wiki, the default location for a maildir setup is: mail_location = maildir:~/Maildir However, when I first tried to access mail on the new box, something wasn't right, and I ended up having to change this to: mail_location = maildir:~ to get mail to display correctly. The filesystem for a users maildir currently has everything (cur/new/tmp, and the individual folders) inside that users directory, ie: /var/vmail/example.com/user/ Do I need to change this so that everything is under a 'Maildir' subdirectroy inside the users directory, like: /var/vmail/example.com/user/Maildir/ ? Also, I'm aware that it is important that even virtual users have valid 'homes', but I'm confused as to where these are (or are supposed to be) by default. My sql query currently contains: user_query = \ SELECT CONCAT('/var/vmail/', maildir) AS home \ FROM mailbox WHERE username = '%u' iterate_query = SELECT username AS user FROM mailbox So... what exactly is this saying? That the users 'home' is '/var/vmail'? Or does it automatically append %d/%u? I'm specifically wondering if the intention for the defaults is for the users home to be: /var/vmail/example.com/user and the users maildirs to be in: /var/vmail/example.com/user/Maildir Would appreciate some clarification... It wouldn't be hard to mv all of the users maildirs to a Maildir subfolder after the sync, but I want to know for sure that that is what I should/need to do... Thanks, -- Best regards, */Charles/*

1 1

[Dovecot] dovecot-postfix stack imap_client_workarounds
by thufir 27 Dec '13

27 Dec '13

To use dovecot-postfix stack with thunderbird, do I put the configuration into /usr/share/dovecot/protocols.d/impad.protocol? That would seem to be how the stack is configured. "Thunderbird To use with Thunderbird, edit the file /etc/dovecot/dovecot.conf: protocol imap { ... login_greeting_capability = yes imap_client_workarounds = tb-extra-mailbox-sep }" https://help.ubuntu.com/community/Dovecot thufir@dur:~$ thufir@dur:~$ cat /usr/share/dovecot/protocols.d/imapd.protocol protocols = $protocols imap thufir@dur:~$ thufir@dur:~$ dovecot -n # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.5.0-44-generic i686 Ubuntu 12.04.3 LTS mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } thufir@dur:~$ thufir@dur:~$ thanks, Thufir

2 1

[Dovecot] Thunderbird message cache out of sync after repetitive rsyncs...
by Charles Marcus 27 Dec '13

27 Dec '13

Ok, hopefully there is a solution to this. I've been experimenting with multiple rsyncs in preparation for pulling the trigger on the mail server switch, but have a problem that I really want to fox before doing so. Apparently something causes Thunderbirds local message cache to get out of sync with dovecot after a sync. Here is the series of commands I'm running: 1. stop postfix, stop dovecot on new server 2. rsync -rltgovDHP --delete --exclude-from 'excludes.txt' /path/to/vmail/example.com/ /var/vmail/example.com/ 3. chown vmail:vmail /var/vmail 4. start dovecot, start postfix ls -al /var/vmail/example.com/user/cur shows all of the messages that should be there, and all perms are correct. Go to my account that is pointed to this mail server/account, and none of the new messages show up. Also, some messages are still showing up that shouldn't. I've tried compacting the folders, closing/relaunching Thunderbird, but nothing helps. The only way to get them to show up is to go to the local Thunderbird cache for the account, and delete the files associated with the folder having the problem. The problem is, ALL folders will have this problem, which means that everyone will need to delete ALL of their local cahced folders. This will be a major support problem. Anyone have any ideas? -- Best regards, */Charles/*

5 16

[Dovecot] Server Migration Attempt - new messages DELETED after secondary rsyncs
by Charles Marcus 27 Dec '13

27 Dec '13

Starting a new thread, as I've got a lot more details now... First, I know this may be (or is even likely) something weird happening with Thunderbird, but the bottom line is, I have to find a resolution or a workaround or something, or I will be unable to pull the trigger on the server migration. It is simply unacceptable to lose ANY mails doing this. Goal: migrate mailstore from old server to new server using rsync Thunderbird (24.2) is set up to access the new account for testing Problem: after rsync, ls shows new messages (11 for the 27th), but when Thunderbird accesses the maildir again after another rsync, MOST (but not all) of the new messages are deleted (only one for the 27th remains) Timo - I'd be happy to do anything necessary to track this down if you'll just tell me what you need... Note: if you are pretty confident that upgrading dovecot on the old server and using dsync to do the migration will solve the problem, obviously I'm willing to do that if there is no other choice, but... I hope you'll want to get to the bottom of this regardless, as, according to you and everything I've read, it should work without losing any emails... Ok, as to details... Source (ol/active server): dovecot 2.1.17, postfix virtual for delivery, vmail owned by postfix:postfix Note: using prefix=INBOX. courier compatibility namespace Target: dovecot 2.2.10, dovecot LDA, vmail owned by vmail:vmail, nothing being actively delivered (yet) Note: NOT using prefix=INBOX. courier compatiblity namespace Both doveconf -n outputs at end of this message *** Could the different namespaces, or differing dovecot versions cause this? Current /snapshot/ being used was taken at about 3:48am this morning rsync command (dovecot is STOPPED before performing, source is the latest snapshot of the active server): rsync -rltgovDHP --delete --delete-excluded --exclude-from '/path/to/excludes.txt' /snapshot/.../vmail/example.com/user/ /.../vmail/example.com/user/ I'm only syncing the one user until I get this problem resolved as it is faster. excludes.txt contains only (just to eliminate these which are still on the source): courierimap* Right after the rsync: ls -al /.../user (changes depending on what is in includes.txt) -rw------- 1 vmail vmail 51 Dec 18 10:13 dovecot-keywords -rw------- 1 vmail vmail 221638 Dec 27 02:42 dovecot-uidlist -rw------- 1 vmail vmail 8 Dec 18 09:56 dovecot-uidvalidity -r--r--r-- 1 vmail vmail 0 Jun 9 2012 dovecot-uidvalidity.4fd32805 ls -al /.../user/cur (copy/pasted newest thru 12/25 - this list is always the same after a sync) -rw------- 1 vmail vmail 24904 Dec 25 15:47 1388004452.Vfe02Ic72976M281736.oldhost.example.com:2, -rw------- 1 vmail vmail 5825360 Dec 25 22:52 1388029948.Vfe02Ic7306fM556006.oldhost.example.com:2, -rw------- 1 vmail vmail 27718 Dec 26 02:19 1388042391.Vfe02Ic33b40M543019.oldhost.example.com:2, -rw------- 1 vmail vmail 28083 Dec 26 07:11 1388059893.Vfe02Ic76388M193423.oldhost.example.com:2,S -rw------- 1 vmail vmail 100651 Dec 26 08:02 1388062961.Vfe02Ic763c2M415005.oldhost.example.com:2, -rw------- 1 vmail vmail 5286 Dec 26 09:41 1388068882.Vfe02Ic7642dM83715.oldhost.example.com:2,S -rw------- 1 vmail vmail 53203 Dec 26 09:55 1388069721.Vfe02Ic7646fM716189.oldhost.example.com:2,S -rw------- 1 vmail vmail 12039 Dec 26 12:48 1388080111.Vfe02Ic76742M972942.oldhost.example.com:2,RS -rw------- 1 vmail vmail 13531 Dec 26 13:14 1388081648.Vfe02Ic7674cM68343.oldhost.example.com:2,S -rw------- 1 vmail vmail 25161 Dec 26 15:47 1388090846.Vfe02Ic768acM489505.oldhost.example.com:2, -rw------- 1 vmail vmail 5037 Dec 26 16:27 1388093257.Vfe02Ic76918M766778.oldhost.example.com:2, -rw------- 1 vmail vmail 3157 Dec 26 17:01 1388095312.Vfe02Ic76997M703744.oldhost.example.com:2, -rw------- 1 vmail vmail 22480 Dec 26 17:50 1388098239.Vfe02Ic769deM225078.oldhost.example.com:2, -rw------- 1 vmail vmail 10043 Dec 26 19:59 1388105984.Vfe02Ic76a25M12505.oldhost.example.com:2, -rw------- 1 vmail vmail 10635 Dec 26 21:11 1388110298.Vfe02Ic76a65M649895.oldhost.example.com:2, -rw------- 1 vmail vmail 8695 Dec 26 21:11 1388110319.Vfe02Ic76a6fM696948.oldhost.example.com:2, -rw------- 1 vmail vmail 11045 Dec 26 21:56 1388112965.Vfe02Ic76a57M185504.oldhost.example.com:2, -rw------- 1 vmail vmail 823 Dec 26 22:40 1388115600.Vfe02Ib61cf5M913598.oldhost.example.com:2,ST -rw------- 1 vmail vmail 815 Dec 26 22:40 1388115627.Vfe02Ib63443M811945.oldhost.example.com:2,ST -rw------- 1 vmail vmail 785 Dec 26 22:40 1388115628.Vfe02Ib659c9M617314.oldhost.example.com:2,ST -rw------- 1 vmail vmail 6156 Dec 27 00:05 1388120705.Vfe02Ib7aa31M58188.oldhost.example.com:2,ST -rw------- 1 vmail vmail 869 Dec 27 00:05 1388120713.Vfe02Ib8506aM185504.oldhost.example.com:2,ST -rw------- 1 vmail vmail 925 Dec 27 00:29 1388122155.Vfe02Ibb2a1fM764275.oldhost.example.com:2,ST -rw------- 1 vmail vmail 823 Dec 27 00:38 1388122687.Vfe02Ic2f69aM168075.oldhost.example.com:2,ST -rw------- 1 vmail vmail 801 Dec 27 00:38 1388122696.Vfe02Ic31befM507147.oldhost.example.com:2,ST -rw------- 1 vmail vmail 801 Dec 27 00:38 1388122709.Vfe02Ic3ac2bM981625.oldhost.example.com:2,ST -rw------- 1 vmail vmail 4576 Dec 27 00:57 1388123820.Vfe02Ic769e8M270744.oldhost.example.com:2,ST -rw------- 1 vmail vmail 8379 Dec 27 01:33 1388126003.Vfe02Ib7fd87M510118.oldhost.example.com:2,ST -rw------- 1 vmail vmail 27647 Dec 27 02:20 1388128838.Vfe02Ic7610fM483481.oldhost.example.com:2, -rw------- 1 vmail vmail 6373 Dec 27 02:42 1388130144.Vfe02Ic76a99M631316.oldhost.example.com:2,ST -rw------- 1 vmail vmail 3906 Dec 27 03:01 1388131281.Vfe02Ic76a9cM599830.oldhost.example.com:2,ST Start dovecot, select INBOX in Thunderbird for this account, it only displays these (I got this ls output from AFTER the messages in the cur directory are deleted per below - before doing any of the 3 aqctions below, ALL of the messages show in the ls output): ls -al /.../user/cur -rw------- 1 vmail vmail 24904 Dec 25 15:47 1388004452.Vfe02Ic72976M281736.oldhost.example.com:2, -rw------- 1 vmail vmail 5825360 Dec 25 22:52 1388029948.Vfe02Ic7306fM556006.oldhost.example.com:2, -rw------- 1 vmail vmail 27718 Dec 26 02:19 1388042391.Vfe02Ic33b40M543019.oldhost.example.com:2, -rw------- 1 vmail vmail 28083 Dec 26 07:11 1388059893.Vfe02Ic76388M193423.oldhost.example.com:2,S -rw------- 1 vmail vmail 100651 Dec 26 08:02 1388062961.Vfe02Ic763c2M415005.oldhost.example.com:2, -rw------- 1 vmail vmail 5286 Dec 26 09:41 1388068882.Vfe02Ic7642dM83715.oldhost.example.com:2,S -rw------- 1 vmail vmail 53203 Dec 26 09:55 1388069721.Vfe02Ic7646fM716189.oldhost.example.com:2,S -rw------- 1 vmail vmail 12039 Dec 26 12:48 1388080111.Vfe02Ic76742M972942.oldhost.example.com:2,RS -rw------- 1 vmail vmail 13531 Dec 26 13:14 1388081648.Vfe02Ic7674cM68343.oldhost.example.com:2,S -rw------- 1 vmail vmail 25161 Dec 26 15:47 1388090846.Vfe02Ic768acM489505.oldhost.example.com:2, -rw------- 1 vmail vmail 5037 Dec 26 16:27 1388093257.Vfe02Ic76918M766778.oldhost.example.com:2, -rw------- 1 vmail vmail 3157 Dec 26 17:01 1388095312.Vfe02Ic76997M703744.oldhost.example.com:2, -rw------- 1 vmail vmail 22480 Dec 26 17:50 1388098239.Vfe02Ic769deM225078.oldhost.example.com:2, -rw------- 1 vmail vmail 10043 Dec 26 19:59 1388105984.Vfe02Ic76a25M12505.oldhost.example.com:2, -rw------- 1 vmail vmail 10635 Dec 26 21:11 1388110298.Vfe02Ic76a65M649895.oldhost.example.com:2, -rw------- 1 vmail vmail 8695 Dec 26 21:11 1388110319.Vfe02Ic76a6fM696948.oldhost.example.com:2, -rw------- 1 vmail vmail 11045 Dec 26 21:56 1388112965.Vfe02Ic76a57M185504.oldhost.example.com:2, -rw------- 1 vmail vmail 27647 Dec 27 02:20 1388128838.Vfe02Ic7610fM483481.oldhost.example.com:2, This is weird, because it does show ONE new message from the 27th. And again, ls -al on the cur dir at this point still shows ALL of the messages (11 for the 27th, and 18 for the 26th) shown in the FIRST ls output, ABOVE this second listing (which is shown only to show you what Thunderbird is seeing, and what shows in the ls output AFTER doing any of the 3 actions below). Now... Doing ANY of the following results in MOST (BUT NOT ALL) OF THE NEW MESSAGES BEING DELETED ON THE SERVER - ie, ls -al output changes to the match what is immediately above (what was showing in Thunderbird right after selecting the Inbox right after the rsync). 1. Right-click on the Inbox > Properties > Repair Folder (in Thunderbird) 2. Right-click on INBOX > Compact (in Thunderbird) 3. Manually deleting the .msf file for the INBOX Obviously, I must find a resolution for this before I can pull the trigger on this migration. ************************************************************************ old server dovecon -n: oldhost : Fri Dec 27, 05:59:12 : ~ # doveconf -n # 2.1.17: /etc/dovecot/dovecot.conf # OS: Linux 3.10.7-gentoo-r1 x86_64 Gentoo Base System release 2.2 auth_default_realm = example.com auth_mechanisms = plain login first_valid_uid = 207 last_valid_uid = 207 listen = * login_log_format_elements = user=<%u> method=%m rip=%r lport=%{lport} mpid=%e %c session=<%{session}> mail_gid = 207 mail_location = maildir:~/:INDEX=MEMORY mail_uid = 207 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = INBOX. separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap lmtp service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = postfix mode = 0600 user = postfix } } service imap-login { service_count = 0 } service imap { process_limit = 2048 } ssl = required ssl_cert = </etc/ssl/myCerts/imap.pem ssl_key = </etc/ssl/myCerts/imap_key.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol smtp { auth_verbose = yes } protocol lda { mail_plugins = sieve } protocol imap { mail_max_userip_connections = 20 } oldhost : Fri Dec 27, 08:22:04 : ~ ********************************************************** new server dovecot -n: host : Fri Dec 27, 08:13:34 : ~ # doveconf -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.17-gentoo x86_64 Gentoo Base System release 2.2 auth_default_realm = example.com auth_mechanisms = plain login first_valid_uid = 200 last_valid_uid = 200 listen = * login_log_format_elements = user=<%u> method=%m %c rip=%r lport=%{lport} mail_gid = vmail mail_location = maildir:~ mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap lmtp service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service imap-login { service_count = 0 } service imap { process_limit = 2048 } ssl = required ssl_cert = </etc/ssl/myCerts/imap.pem ssl_key = </etc/ssl/myCerts/imap_key.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol smtp { auth_verbose = yes } protocol lda { auth_verbose = yes mail_plugins = sieve } protocol imap { mail_max_userip_connections = 20 } host : Fri Dec 27, 08:19:59 : ~ -- Best regards, */Charles/*

3 4

[Dovecot] v2.2.10 released
by Timo Sirainen 27 Dec '13

27 Dec '13

http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz.sig I've been really busy the last few months, as I guess people in Dovecot mailing list have seen since I haven't been very responsive. There are at least some dsync bugs I haven't had time to look into yet. The busyness probably continues for a while more, but the next year is looking much better for me and for Dovecot in general. We're planning to hire a few more Dovecot coders at some point, so if you're interested send me an email. :) + auth: passdb/userdb dict rewrite to support much more complex setups. See doc/example-config/dovecot-dict-auth.conf.ext. The old settings will continue to work. + auth: Added userdb result_success/failure/tempfail and skip settings, similar to passdb's. See http://wiki2.dovecot.org/UserDatabase + imap: Implemented SETQUOTA command for admin user when quota_set is configured. See http://master.wiki2.dovecot.org/Quota/Configuration + quota: Support "*" and "?" wildcards in mailbox names in quota_rules + mysql: Added ssl_verify_server_cert=no|yes parameter. This currently defaults to "no" to make sure nothing breaks, but likely will become "yes" in Dovecot v2.3. + ldap: Added blocking=yes setting to use auth worker processes for ldap lookups. This is a workaround for now to be able to use multiple simultaneous LDAP connections. + pop3c+dsync performance improvements - quota-status: quota_grace was ignored - ldap: Fixed memory leak with auth_bind=yes and without auth_bind_userdn. - imap: Don't send HIGHESTMODSEQ anymore on SELECT/EXAMINE when CONDSTORE/QRESYNC has never before been enabled for the mailbox. - imap: Fixes to handling mailboxes without permanent modseqs. (When [NOMODSEQ] is returned by SELECT, mainly with in-memory indexes.) - imap: Various fixes to METADATA support. - stats plugin: Processes that only temporarily dropped privileges (e.g. indexer-worker) may have been logging errors about not being able to open /proc/self/io.

3 2

[Dovecot] Question about mailformat migration
by Davide 27 Dec '13

27 Dec '13

Hi to all, my question is if it's possible to retrive only mail location and mailformat with user_query and for authentication to use vpopmail plugins for dovecot version 2.2.5 i want to put a column in my mysql tables that inherit to user (vpopmail db) like "maildir format" -- *Davide Marchi* *T*eorema *F*errara *Srl* Via Spronello, 7 - Ferrara - 44121 Tel. *0532783161* Fax. *0532783368* E-m@il: *davide.marchi(a)mail.cgilfe.it* Skype: *davide.marchi73* Web: *http://www.cgilfe.it* *CONFIDENZIALITA'* *Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario/dei destinatari. Qualora il messaggio in parola Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo e a non inoltrarlo a terzi, dandocene gentilmente comunicazione.* *Per favore, pensa all'ambiente. Stampa questa email solo se necessario.*

1 0

[Dovecot] obox_fs and Dropbox, someone uses it?
by Alessio Cecchi 27 Dec '13

27 Dec '13

I purchased the license for the Dovecot Object Storage for Dropbox to test this functionality on a personal domain. Unfortunately I can not make it work, I create the token for my Dropbox account from here https://dropbox.dovecot.fi/ and setup in dovecot configuration. When I try to login with an user I found these errors in log file: ============ Dec 27 10:52:16 mail dovecot: imap-login: Login: user=<dovecot1(a)test.it>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=8844, secured, session=<xxCXDIHuTQB/AAAB> Dec 27 10:52:16 mail dovecot: metacache-worker(8839): Error: fs-dropbox: GET 1/metadata/sandbox/dovecot1(a)test.it/idx/?file_limit=25000 failed: 401 Unauthorized Dec 27 10:52:16 archiviomail dovecot: metacache-worker(8839): Error: Failed to iterate dovecot1(a)test.it/idx/: GET 1/metadata/sandbox/dovecot1(a)test.it/idx/?file_limit=25000 failed: 401 Unauthorized Dec 27 10:52:16 mail dovecot: imap(dovecot1(a)test.it): Error: user dovecot1(a)test.it: Initialization failed: Namespace '': obox: USER-REF: /var/run/dovecot/metacache returned failure Dec 27 10:52:16 mail dovecot: imap(dovecot1(a)test.it): Error: Invalid user settings. Refer to server log for more information. Dec 27 10:52:16 mail dovecot: imap-login: Login: user=<dovecot1(a)test.it>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=8846, secured, session=<NTSaDIHuTgB/AAAB> ============= I do not think it's a problem of my configuration, if instead of Dropbox use AWS S3 works fine, seems to be a token problem (401 Unauthorized). The plugin configuration is this: ### Dropbox plugin { obox_fs = fscache 10G:/var/lib/dovecot/cache:dropbox:https://XXXX:YYYY@dropbox/ } Anyone successfully used this setup?

1 0

[Dovecot] German Umlauts in folder name and sieve
by Christian Rößner 27 Dec '13

27 Dec '13

Hi, I had created an imap folder that has German Umlauts in it: „RA Rößner - Merle“ When finished, the result looks like this on filesystem: drwx------ 3 vmail vmail 4096 Dec 27 11:02 RA Ro&AwgA3w-ner - Merle/ I wrote this sieve script (with SOGo): if anyof (address :regex "from" "@.*\\.ra-roessner-merle\\.de") { fileinto "RA Ro&AwgA3w-ner - Merle"; stop; } That creates a new IMAP folder with exactly this strange name. Can I change this somehow? # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.11.2-hardened x86_64 Gentoo Base System release 2.2 auth_master_user_separator = * auth_mechanisms = plain login cram-md5 digest-md5 ntlm auth_verbose = yes default_vsz_limit = 512 M hostname = mail.roessner-net.de imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_access_groups = vmail mail_attachment_dir = /var/mail/virtual/copymail/attachments mail_gid = vmail mail_location = mdbox:~/mdbox mail_plugins = quota acl fts fts_lucene zlib mail_log notify mail_privileged_group = mail mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mdbox_rotate_size = 128 M namespace { list = children location = mdbox:%%h/mdbox prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox "Deleted Messages" { special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk-E-Mail { auto = subscribe special_use = \Junk } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } mailbox junkmail { special_use = \Junk } prefix = separator = / type = private } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/mail/virtual/shared-mailboxes.db fts = lucene fts_autoindex = yes fts_lucene = whitespace_chars=@. quota = dict:User quota::file:%h/mdbox/dovecot-quota quota_grace = 10%% quota_rule = *:storage=300M:messages=20000 quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = -storage=100%% quota-warning below %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve zlib_save = gz zlib_save_level = 6 } protocols = imap pop3 lmtp sieve service auth-worker { extra_groups = ssl-cert unix_listener auth-worker { mode = 0600 user = vmail } user = vmail } service auth { extra_groups = ssl-cert unix_listener auth-userdb { mode = 0600 user = vmail } user = vmail } service config { unix_listener config { mode = 0600 user = vmail } } service dict { unix_listener dict { mode = 0600 user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/lmtp-dovecot { group = postfix mode = 0666 user = postfix } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = vmail } ssl_cert = </etc/ssl/certs/mail.roessner-net.de.pem ssl_key = </etc/ssl/private/mail.roessner-net.de.key.pem userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_proctitle = yes protocol lmtp { mail_plugins = quota acl fts fts_lucene zlib mail_log notify sieve } protocol lda { mail_plugins = quota acl fts fts_lucene zlib mail_log notify sieve } protocol imap { mail_max_userip_connections = 50 mail_plugins = quota acl fts fts_lucene zlib mail_log notify imap_quota imap_acl imap_zlib } Thanks in advance -Christian Rößner -- [*] 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, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

2 2

[Dovecot] Question re: indexes
by Charles Marcus 26 Dec '13

26 Dec '13

Hi all, On the old/current dovecot server, I have disabled on disk indexes: mail_location = maildir:~/:INDEX=MEMORY On the new server, I removed the 'INDEX=MEMORY' part, and I now see some new index related files, but what I don't see is the main dovecot.index file... I only have: dovecot.index.cache and dovecot.index.log So... where is the main dovecot.index file? -- Best regards, */Charles/*

1 1

[Dovecot] SHA512-CRYPT scheme fails password verification
by Jouko Nikula 25 Dec '13

25 Dec '13

Hello, If I try to use the crypt schemes provided by libc. I fail as follows: jnikula@jlaptop:~/$ doveadm pw -s SHA512-CRYPT -p 123456 {SHA512-CRYPT}$6$to2umWLDtqvzS8SV$ZGpBeGNKuUN/2HKG6I2BEAt.Gzrz/y.SZDkos2GT2ik8obnp3XCFWfVsKVriJa6jjHULmLIqCSSyaF5YrTH7u. jnikula@jlaptop:~/$ doveadm pw -t {SHA512-CRYPT}$6$to2umWLDtqvzS8SV$ZGpBeGNKuUN/2HKG6I2BEAt.Gzrz/y.SZDkos2GT2ik8obnp3XCFWfVsKVriJa6jjHULmLIqCSSyaF5YrTH7u. -p 123456 doveadm(jnikula): Fatal: reverse password verification check failed: Password mismatch Using SHA512 sum scheme (-s SHA512) works ok in the same manner. I have dovecot version 2.2.9 on Linux 3.11.0-14-generic x86_64 Ubuntu 13.10 and I get the same results on 32-bit Debian as well. Does anyone have idea what's wrong? Thanks in advance, Jouko Nikula

2 2

[Dovecot] Patch for Dovecot's quota policy daemon
by Peer Heinlein 24 Dec '13

24 Dec '13

Hi Timo, we wrote a simple Patch for the Dovecot quota policy daemon. If a user is over quota, I prefer blocking the user sending e-mails, so I need a policy daemon, that's able to use the envelope or sasl sender as lookup key. I'd be happy if that patch can become part of the normale Dovecot releases. Peer -------- Original-Nachricht -------- Betreff: Re: Fwd: Quota-Patch Datum: Wed, 11 Dec 2013 17:33:45 +0100 Von: Stephan Seitz <s.seitz(a)heinlein-support.de> Organisation: Heinlein Support GmbH An: Peer Heinlein <p.heinlein(a)heinlein-support.de> Parameter r Code ENUM QUOTA_MATCH_RECIPIENT Stringmatch recipient= ${recipient} This macro expands to the complete recipient address. A command-line argument that contains ${recipient} expands to as many command-line arguments as there are recipients. This information is modified by the hqu flags for quoting and case folding. Parameter S Code ENUM QUOTA_MATCH_SASLSENDER Stringmatch sasl_sender= ${sasl_sender} This macro expands to the SASL sender name (i.e. the original submitter as per RFC 4954) in the MAIL FROM command when the Postfix SMTP server received the message. This feature is available as of Postfix 2.2. Parameter U Code ENUM QUOTA_MATCH_SASLUSER Stringmatch sasl_username= ${sasl_username} This macro expands to the SASL user name in the AUTH command when the Postfix SMTP server received the message. This feature is available as of Postfix 2.2. Parameter s Code ENUM QUOTA_MATCH_SENDER Stringmatch sender= ${sender} This macro expands to the envelope sender address. By default, the null sender address expands to MAILER-DAEMON; this can be changed with the null_sender attribute, as described above. This information is modified by the q flag for quoting. -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

1 0

[Dovecot] Eliminate legacy INBOX namespace - how?
by Charles Marcus 24 Dec '13

24 Dec '13

Hi all, Our mailstore was converted from a Courier-IMAP system last year, but I am planning a migration to a shiny new VM, and would really like to clean things up and do away with the legacy INBOX namespace. My goal is to simplify IMAP client setup - no special 'INBOX' namespace needed, they just enter the server info and credentials. Also important because I will be rolling out SOGo, which has a nice web interface, and I want the mailstore to be as close to default dovecot settings as possible - although I do plan on converting from maildir to mdbox when I do the conversion I also don't want other folders to show up as subfolders of the Inbox in IMAP clients, they should all show up on the same level as the Inbox. I've read http://wiki2.dovecot.org/Migration/Courier, but I don't see anything about how to eliminate this stupid legacy INBOX. namespace, so that new IMAP clients won't show all folders as subfolders of the INBOX unless/until they add the INBOX namespace prefix in the advanced settings. I've also been reading http://wiki2.dovecot.org/Namespaces, but I'm still confused as to how to go about this. Currently I have: namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = INBOX. separator = . } The wiki recommends avoiding the 'alternative' of having two different namespaces, so I don't want to do that. Also - it would be ok if existing clients had temporary issues displaying folders properly until the INBOX prefix was removed (I would give everyone plenty of advance warning). Anyone ever done this before? Any suggestions Timo? Note: I am planning a migration to a new mail server (VM), so could make any filesystem layout changes when I do this if necessary. Thanks, -- Best regards, */Charles/*

5 6

[Dovecot] Sieve Addon in thunderbird is not showing Vacation in action list
by Anant 23 Dec '13

23 Dec '13

Hello guys, I am using "dovecot-2.2-pigeonhole-0.4.2" ( Sieve <http://www.sieve.info/> Support for Dovecot <http://www.dovecot.org/> ) , Now I can set Vacation mail using Roundcube and it is working fine. now i want to set Vacation/outofoffice mail from thunderbird 24.0 , I have installed pluginsieve-0.2.3d.xpi <https://github.com/thsmi/sieve/blob/master/nightly/0.2.3/sieve-0.2.3d.xpi?r…> for thunderbird from "https://github.com/thsmi/sieve/tree/master/nightly" But I am not able to set vacation as it is not giving me an option with reply option. *Even if i will create a vacation mail in Roundcube , my thunderbird plugin was unable to understand that filter. getting an error / //Error while parsing script.// // } expected but found: vacation :subject "not available" "not here"; } .../ and my source code for sieve filter is look like ///require ["vacation"];// //# rule:[vacation]// //if true// //{// // vacation :subject "not available" "not here";// //}/ *I am only able to Enable one filter at a time in thunderbird. And I am not sure it is the right place to post that stuff.. So please guide me as well if I am wrong. Regards, Anant Saraswat

1 0

[Dovecot] Is the users password available from a mail_filter?
by martijn.list 23 Dec '13

23 Dec '13

Hi, I'm working on a Dovecot encryption module which uses the mail filter plugin to encrypt/decrypt the message "on the fly". I was wondering whether it is possible to access the password (or a hashed password) of the user. It seems that only the user (using the %u parameter) is available to the mail_filter plugin. Any idea how to get hold of the (possibly hashed) password? Kind regards, Martijn Brinkers

1 0

[Dovecot] search gives variable/different results
by W. de Hoog 23 Dec '13

23 Dec '13

Hi, When I perform a search using doveadm every time it returns different results. For example: $ doveadm search mailbox shared/\* TO stromvers 938ff10527d6be515f5900007b46f991 6 938ff10527d6be515f5900007b46f991 7 938ff10527d6be515f5900007b46f991 8 $ doveadm search mailbox shared/\* TO stromvers 6a8ff10527d6be515f5900007b46f991 1 6a8ff10527d6be515f5900007b46f991 3 6a8ff10527d6be515f5900007b46f991 4 938ff10527d6be515f5900007b46f991 1 938ff10527d6be515f5900007b46f991 2 938ff10527d6be515f5900007b46f991 3 938ff10527d6be515f5900007b46f991 6 938ff10527d6be515f5900007b46f991 7 938ff10527d6be515f5900007b46f991 8 $ doveadm search mailbox shared/\* TO stromvers 938ff10527d6be515f5900007b46f991 6 938ff10527d6be515f5900007b46f991 7 938ff10527d6be515f5900007b46f991 8 $ doveadm search mailbox shared/\* TO stromvers 938ff10527d6be515f5900007b46f991 7 938ff10527d6be515f5900007b46f991 8 $ doveadm search mailbox shared/\* TO stromvers 6a8ff10527d6be515f5900007b46f991 1 6a8ff10527d6be515f5900007b46f991 3 6a8ff10527d6be515f5900007b46f991 4 $ dovecot -n # 2.2.9 (5c170e0786f3): /etc/dovecot/dovecot.conf # OS: Linux 3.12.0-031200-generic x86_64 Ubuntu 13.10 auth_verbose = yes disable_plaintext_auth = no log_path = /var/log/dovecot.log mail_debug = yes mail_plugins = fts fts_squat mail_privileged_group = mail namespace { hidden = yes inbox = yes list = no location = mbox:~/mail:INBOX=/var/mail/%u prefix = "#mbox/" separator = / } namespace { list = yes location = sdbox:/home/imapshared-sdbox prefix = shared/ separator = / subscriptions = no type = public } namespace inbox { location = sdbox:~/sdboxmail mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / } passdb { driver = pam } plugin { fts = squat fts_autoindex = yes fts_squat = partial=4 full=10 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap" ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } verbose_ssl = yes protocol imap { imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags } -- Willem-Jan de Hoog

1 2

[Dovecot] [help]how to config the dovecot authentication by the other servers
by wuwei 23 Dec '13

23 Dec '13

hi i am the postfix+dovecot.for example,there are three servers: server 1 for postfix server 2 for dovecot server 3 for auth server how could i let the dovecot(2.29) authenticated by the other servers? i config the postfix auth-type to dovecot.how could i config the dovecot authenticated by the server 3 with tcp/ip socket?or is there are any samples?i have found in http://wiki2.dovecot.org/. *at first i try to use memcached ,these are the configure:* *./dovecot-dict-auth.conf.ext* uri = memcached:host=172.24.140.252:port=12000 password_key = dovecot/passdb/%u user_key = dovecot/userdb/%u value_format = json iterate_disable = yes default_pass_scheme = plain * ./10-auth.conf* auth_mechanisms = plain login !include auth-dict.conf.ext *./auth-dict.conf.ext* passdb { driver = dict args = /usr/local/dovecot/etc/dovecot/dovecot-dict-auth.conf.ext } userdb { driver = prefetch #args = /etc/dovecot/dovecot-dict-auth.conf.ext } *in memcached i put some data in：* set dovecot/passdb/test(a)test.com 0 0 103 {'uid':'123','gid':'123','home':'/home/username','username':'test(a)test.com','password':'test(a)test.com'} STORED set dovecot/passdb/test 0 0 103 {'uid':'123','gid':'123','home':'/home/username','username':'test(a)test.com','password':'test(a)test.com'} STORED set test 0 0 103 {'uid':'123','gid':'123','home':'/home/username','username':'test(a)test.com','password':'test(a)test.com'} STORED set test(a)test.com 0 0 103 {'uid':'123','gid':'123','home':'/home/username','username':'test(a)test.com','password':'test(a)test.com'} STORED i reload dovecot and postfix.postfix connect to dovect is ok!i open the debug log .the memcached tell that it has received a connection.and the dovecot also said has connect to the memcached ,but after 30s,the connect to the memcached auto broken by out of time.here some logs: * dovcot logs:* Dec 23 16:45:57 auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth Dec 23 16:45:57 auth: Debug: Read auth token secret from /usr/local/dovecot/var/run/dovecot/auth-token-secret.dat Dec 23 16:45:57 auth: Debug: auth client connected (pid=0) Dec 23 16:46:08 auth: Debug: client in: AUTH 1 login service=smtp nologin lip=172.24.140.228 rip=192.168.3.29 Dec 23 16:46:08 auth: Debug: client passdb out: CONT 1 VXNlcm5hbWU6 Dec 23 16:46:22 auth: Debug: client in: CONT 1 OTY1ZWI3MmM5MmE1NDlkZA== (previous base64 data may contain sensitive data) Dec 23 16:46:22 auth: Debug: client passdb out: CONT 1 UGFzc3dvcmQ6 Dec 23 16:46:39 auth: Debug: client in: CONT 1 OTY1ZWI3MmM5MmE1NDlkZA== (previous base64 data may contain sensitive data) Dec 23 16:46:39 auth-worker(27884): Debug: Loading modules from directory: /usr/local/lib/dovecot/auth Dec 23 16:46:39 auth-worker(27884): Debug: dict(965eb72c92a549dd,192.168.3.29): lookup shared/dovecot/passdb/965eb72c92a549dd Dec 23 16:47:11 auth: Debug: client passdb out: FAIL 1 user=965eb72c92a549dd temp Dec 23 16:47:09 debian228 dovecot: auth-worker(27884): Error: memcached: Lookup timed out in 30.000 secs Dec 23 16:47:09 debian228 dovecot: auth-worker(27884): Error: dict(965eb72c92a549dd,192.168.3.29): Lookup failed i don't know why it happened.and why it look up key with prefix "shared/".until now i found that the key is password "965eb72c92a549dd"(password is the same as username before).what will happened if there two people with the same password.it seams that i should use the userdb! is someone could give me a sample?what could i do if there has two or more memcached servers?so ,i think of that if there has some config to connect to the tcp socket server.and the server implement by java or any other language by the developer itself. thank you for you help! -- View this message in context: http://dovecot.2317879.n4.nabble.com/help-how-to-config-the-dovecot-authent… Sent from the Dovecot mailing list archive at Nabble.com.

1 0

[Dovecot] [dovecot-2.2.5] Duplicates in mdbox
by radek 23 Dec '13

23 Dec '13

Hi I have strange situation with one of mailboxes in mdbox format. Some messages are duplicated, not all. I am sure that is not sieve or another mail client issue, because access is via roundcube without sieve plugin. In maillog I have not found any suspicious information about this problem and i can see that from postfix do dovecot-lda was piped only one copy of message. Radek

2 1

[Dovecot] Horde + dovecot metadata support
by Andreas Schulze 23 Dec '13

23 Dec '13

Hello, Horde (http://horde.org) has the ability to store its preferences direct into a users imap mailbox using imap metadata extension. There are two implementations of the imap extension. 1. a dovecot plugin: http://hg.dovecot.org/dovecot-metadata-plugin 2. dovecot itself: http://www.dovecot.org/list/dovecot/2013-November/093243.html I setup Horde and dovecot-2.2.5 to use this extension and it works well using 1.) Now, with dovecot-2.2.9, the plugin fail to compile (unrelated problem on my side). So I tried 2.) But here I get a Horde-Error "Error in IMAP command GETMETADATA: Invalid arguments." I enables mail_debug but saw no helpfull logging. mail_attribute_dict = file:/tmp/%Lu/dovecot-attributes remote horde.testserver.ip/32 { imap_metadata = yes mail_debug = yes } Also I created directory /tmp/$my_login_id (mode 777) but dovecot also created no files. neither it logs anything about it. This is a sample imap session generated by horde: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready. 1 AUTHENTICATE PLAIN *** 1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE METADATA QUOTA] Logged in 2 NAMESPACE * NAMESPACE (("" ".")) NIL NIL 2 OK Namespace completed. 3 LIST () "" (*) * LIST () "." INBOX 3 OK List completed. 4 GETMETADATA "*" (/shared/vendor/kolab/folder-type) 4 BAD Error in IMAP command GETMETADATA: Invalid arguments. 5 LOGOUT * BYE Logging out 5 OK Logout completed. Are there any hints or is the metadata extension just not fully implemented in dovecot? Thanks, Andreas -- Andreas Schulze Internetdienste | P252 DATEV eG 90329 Nürnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196 E-Mail info @datev.de | Internet www.datev.de Sitz: 90429 Nürnberg, Paumgartnerstr. 6-14 | Registergericht Nürnberg, GenReg Nr.70 Vorstand Prof. Dieter Kempf (Vorsitzender) Dipl.-Kfm. Wolfgang Stegmann (stellvertretender Vorsitzender) Dipl.-Kfm. Michael Leistenschneider Dipl.-Kfm. Dr. Robert Mayr Jörg Rabe v. Pappenheim Dipl.-Vw. Eckhard Schwarzer Vorsitzender des Aufsichtsrates: Reinhard Verholen

3 3

[Dovecot] auth: Error: net_accept() failed: Too many open files
by boyd yang 23 Dec '13

23 Dec '13

Hi All, I got below errors when I do some 2000 users concurrency test against dovecot 2.1.7. Dec 23 10:18:52 auth: Error: net_accept() failed: Too many open files Dec 23 10:18:52 auth: Error: net_accept() failed: Too many open files Dec 23 10:18:52 auth: Error: net_accept() failed: Too many open files Dec 23 10:18:52 auth: Error: net_accept() failed: Too many open files Dec 23 10:18:52 auth: Error: net_accept() failed: Too many open files Dec 23 10:18:52 auth: Error: net_accept() failed: Too many open files Dec 23 10:18:52 auth: Error: net_accept() failed: Too many open files Dec 23 10:18:52 auth: Error: net_accept() failed: Too many open files Dec 23 10:18:52 auth: Error: net_accept() failed: Too many open files Dec 23 10:18:52 auth: Error: net_accept() failed: Too many open files Dec 23 10:18:52 auth: Error: net_accept() failed: Too many open files I seems the auth process become the bottleneck as there is only one auth process. service auth-worker { process_limit = 1000 } service imap-login { process_min_avail = 48 service_count = 0 } service imap { process_limit = 10240 process_min_avail = 8 } I find that the auth process does not open too many files with lsof, and my limit is very big(1000000). How to fix this? Thanks!

1 0

[Dovecot] move mailbox to LAYOUT=fs
by Andreas Schulze 23 Dec '13

23 Dec '13

Hello, I think about migrating small servers storage to LAYOUT=fs (http://wiki2.dovecot.org/MailLocation/Maildir#Directory_layout) Is there a smooth way to adjust the existing folders? Andreas

1 0

[Dovecot] TLS SNI with Dovecot
by Michael Neurohr 23 Dec '13

23 Dec '13

Hi! I've been using Dovecot for one single Domain with SSL certificates. Now I would like to use Dovecot with several Domains and proper SSL certificates. I tried to setup TLS SNI but it does not work. What I basically did was just adding local_name imap.samsoft.at { ssl_cert = </etc/ssl/private/mailserver/imap.samsoft.at.crt ssl_key = </etc/ssl/private/mailserver/imap.samsoft.at.key } for the additional domain. When trying to login via IMAP, I see the following lines in the log file: =================================================================== Dec 22 21:01:05 mx0 dovecot: imap-login: Warning: SSL alert: where=0x4004, ret=554: fatal bad certificate [151.236.5.22] Dec 22 21:01:05 mx0 dovecot: imap-login: Warning: SSL failed: where=0x2002: SSLv3 read client certificate A [151.236.5.22] Dec 22 21:01:05 mx0 dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=151.236.5.22, lip=151.38.7.25, TLS handshaking: SSL_accept() failed: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate: SSL alert number 42, session=<Rg5EzyXutgCX7AaF> =================================================================== The actual Dovecot config is pasted below. How can I solve that and server different certificates on the same IP Address? Thanks, Michael doveconf -n # 2.2.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab076.8 i686 CentOS release 6.5 (Final) simfs auth_mechanisms = plain login mail_location = maildir:/var/mail/vhosts/%d/%n mail_plugins = notify mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave imapflags namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { antispam_backend = dspam antispam_dspam_args = --source=error;--signature=%%s;--user;%u antispam_dspam_binary = /usr/bin/dspam antispam_signature = X-DSPAM-Signature antispam_signature_missing = move antispam_spam = Spam antispam_trash = trash;Trash;Deleted Items;Deleted Messages sieve = /var/mail/vhosts/sieve-scripts/%d/%n/.dovecot.sieve sieve_before = /var/mail/vhosts/sieve-scripts/before sieve_dir = /var/mail/vhosts/sieve-scripts/%d/%n/sieve sieve_extensions = +imapflags } postmaster_address = postmaster(a)changed.at protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service dict { unix_listener dict { user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl = required ssl_ca = </etc/ssl/private/mailserver/ca-bundle.crt ssl_cert = </etc/ssl/private/mailserver/mx0.domain1.at.pem ssl_key = </etc/ssl/private/mailserver/mx0.domain1.at.key userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol lmtp { mail_plugins = sieve } protocol lda { mail_plugins = sieve } protocol imap { mail_plugins = antispam } local_name imap.samsoft.at { ssl_cert = </etc/ssl/private/mailserver/imap.samsoft.at.crt ssl_key = </etc/ssl/private/mailserver/imap.samsoft.at.key }

3 3

[Dovecot] Duplicated (but only for unread) messages after second rsync pass...
by Charles Marcus 22 Dec '13

22 Dec '13

Ok, I know I should probably be using dsync for this, but I'm more familiar with rsync, and didn't think this would be a problem. Here is what I am doing, and what is apparently happening (only done this once, but I'm guessing it will happen each time): rsync -avHP /mnt/vmail/example.com/user1/ /var/vmail/example.com/user1/ chown -R vmail:vmail /var/vmail/example.com Ok, so far so good, everything works fine accessing the mails (I'm using Thunderbird). Now I do another rsync, but this time I did the entire mailstore: rsync -avHP /mnt/vmail/example.com/ /var/vmail/example.com/ chown -R vmail:vmail /var/vmail/example.com Right after I started up dovecot again, I hot a bunch of these in the logs: 2013-12-22T09:52:51-05:00 newhost dovecot: imap(user1(a)example.com): Warning: Maildir /var/vmail/example.com/user1/: Expunged message reappeared, giving a new UID (old uid=45516, file=1387468268.Vfe02Ic1343fM845754.oldhost.sub.example.com:2,ST) 2013-12-22T09:52:51-05:00 newhost dovecot: imap(user1(a)example.com): Warning: Maildir /var/vmail/example.com/user1/: Expunged message reappeared, giving a new UID (old uid=45518, file=1387468645.Vfe02Ic73e0eM530539.oldhost.sub.example.com:2,ST) The problem is, it looks like every single message that was flagged as unread is now duplicated on the new system. Also - not that this is a problem, but all of the old messages have the fqdn of the old server in the individual email file names - oldhost.sub.example.com - while the new ones only have the local hostname (newhost) Did I do something wrong? Or is this going to be an unavoidable problem if I want to use rsync to do the final migration that using dsync would avoid? Thanks, -- Best regards, */Charles /*

3 4

[Dovecot] Dovecot proxying with LDAP - an example?
by Graham Leggett 22 Dec '13

22 Dec '13

Hi all, I have been struggling trying to understand the syntax to configure dovecot as a proxy against an LDAP server. As a single server dovecot works great. Now I want to add the "mailHost" attribute which, if present, should indicate the DNS name of the host that contains the person's mailbox. If the mailHost matches the local hostname, the mailbox should be served locally as it already does now. If the mailHost is not the local hostname, dovecot should proxy the request to the given server using SSL on port 993. The docs at http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy suggest that proxy_always is what I am looking for, but I cannot find any worked examples of how this might work. Has anyone attempted this before? What I have so far is this, but no proxying seems to take place: pass_attrs = mail=user,userPassword=password,\ mailMessageStore=userdb_mail,=proxy_always=y,mailHost=host,=ssl=yes Can anyone confirm? I am using dovecot v2.0.9 as provided out the box by RHEL6. Regards, Graham --

1 0

[Dovecot] 'unknown user' using dovecot LDA
by Charles Marcus 22 Dec '13

22 Dec '13

Ok, one more issue to resolve. The old server was still using the postfix/virtual for delivery, but the new one is using the dovecot LDA. Now, when an email generated locally by a cron job is delivered, this shows in the log: 2013-12-22T10:29:55-05:00 host postfix/pickup[31400]: C67FD90F676B2: uid=0 from=<newsrv+rkhunter(a)example.com> 2013-12-22T10:29:55-05:00 host postfix/cleanup[22349]: C67FD90F676B2: message-id=<20131222152955.C67FD90F676B2(a)smtp2.example.com> 2013-12-22T10:29:55-05:00 host postfix/qmgr[31401]: C67FD90F676B2: from=<newsrv+rkhunter(a)example.com>, size=1555, nrcpt=1 (queue active) 2013-12-22T10:29:55-05:00 host dovecot: auth-worker(22365): passwd(user1(a)example.com): unknown user 2013-12-22T10:29:55-05:00 host dovecot: lda(user1(a)example.com): msgid=<20131222152955.C67FD90F676B2(a)smtp2.example.com>: saved mail to INBOX 2013-12-22T10:29:55-05:00 host postfix/pipe[22361]: C67FD90F676B2: to=<user1+rkhunter-report(a)example.com>, relay=dovecot, delay=0.06, delays=0.02/0/0/0.04, dsn=2.0.0, status=sent (delivered via dovecot service) 2013-12-22T10:29:55-05:00 host postfix/qmgr[31401]: C67FD90F676B2: removed The mail was delivered (as the log also clearly shows), but what is with the 'unknown user'? I'm not sure how I can test my maps with dovecot, but testing with postfix shows: # postmap -q user1(a)example.com mysql:/etc/postfix/maps/mysql/vmm.cf example.com/user1/ Which is correct. And my dovecot-sql-conf.ext contains: driver = mysql connect = "host=localhost dbname=db_name user=dbuser password=password" default_pass_scheme = CRYPT password_query = \ SELECT username AS user, password \ FROM mailbox WHERE username = '%u' user_query = \ SELECT CONCAT('/var/vmail/', maildir) AS home \ FROM mailbox WHERE username = '%u' iterate_query = SELECT username AS user FROM mailbox I confirmed the db info is identical to what postfix is using. Oh - and in order to make sure that all usernames are lowercased, shouldn't I change '%u' above to '%Lu'? Appreciate any suggestions on where to go next... thanks -- Best regards, */Charles/*

3 4

[Dovecot] New server missing auth-worker entries in logs
by Charles Marcus 22 Dec '13

22 Dec '13

Hi all, Ok, I'm making progress on my new server, but there is an entry in the logs on the old/current server that is not showing p on the new one... lines like: dovecot: auth-worker(20284): mysql(localhost): Connected to database my_auth_db I've looked everywhere, compared settings, etc, and can't seem to find why I get this line on the old server and odn't on the new one. Anyone have a clue stick? Thanks

2 2

[Dovecot] File descriptor leak in sieve-extprograms
by Kirill A. Shutemov 21 Dec '13

21 Dec '13

I've tried to use sieve-filter for my inbox (~6000 messages). It failed after some work with this backtrace: sieve-filter(kas): Error: socketpair() failed: Too many open files sieve-filter(kas): Panic: file script-client-local.c: line 155 (script_client_local_disconnect): assertion failed: (pid >= 0) sieve-filter(kas): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x66a71) [0x7f020e717a71] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f020e717ada] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f020e6d32ee] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(+0x4baf) [0x7f020dae0baf] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(+0x58ca) [0x7f020dae18ca] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(script_client_fail+0x2f) [0x7f020dae199f] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(script_client_run+0xc4) [0x7f020dae1fd4] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(+0x6134) [0x7f020dae2134] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x3ac) [0x7f020ecd1adc] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x4a) [0x7f020ece05aa] -> /usr/bin/sieve-filter(main+0x6a9) [0x403b49] -> /usr/lib/libc.so.6(__libc_start_ma in+0xf5) [0x7f020e327bc5] -> /usr/bin/sieve-filter() [0x404111] The reason is file descriptor leak in "script client local". script_client_local_close_output() shutdowns write side of descriptor and sets sclient->fd_out to -1, but never closes the descriptor. I've tried to fix this by the patch below. Tests works fine, but sieve-filter crashed in other way: sieve-filter(kas): Panic: epoll_ctl(del, 13) failed: Bad file descriptor sieve-filter(kas): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x66a71) [0x7f0ed406fa71] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f0ed406fada] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f0ed402b2ee] -> /usr/lib/dovecot/libdovecot.so.0(+0x776f5) [0x7f0ed40806f5] -> /usr/lib/dovecot/libdovecot.so.0(+0x8009a) [0x7f0ed408909a] -> /usr/lib/dovecot/libdovecot.so.0(io_stream_unref+0x25) [0x7f0ed40764c5] -> /usr/lib/dovecot/libdovecot.so.0(o_stream_unref+0x26) [0x7f0ed4088136] -> /usr/lib/dovecot/libdovecot.so.0(+0x80e48) [0x7f0ed4089e48] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x27) [0x7f0ed407fa47] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7) [0x7f0ed40807d7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f0ed407f5e8] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(script_client_run+0x9c) [0x7f0ed343af8c] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(+0x6114) [0x 7f0ed343b114] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x3ac) [0x7f0ed4629adc] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x4a) [0x7f0ed46385aa] -> /usr/bin/sieve-filter(main+0x6a9) [0x403b49] -> /usr/lib/libc.so.6(__libc_start_main+0xf5) [0x7f0ed3c7fbc5] -> /usr/bin/sieve-filter() [0x404111] I failed to unfold this in a reasonable time. Any ideas? diff --git a/src/plugins/sieve-extprograms/script-client-local.c b/src/plugins/sieve-extprograms/script-client-local.c index 56d32f707c09..f54ef82132cf 100644 --- a/src/plugins/sieve-extprograms/script-client-local.c +++ b/src/plugins/sieve-extprograms/script-client-local.c @@ -139,7 +139,6 @@ static int script_client_local_close_output(struct script_client *sclient) i_error("shutdown(%s, SHUT_WR) failed: %m", sclient->path); return -1; } - sclient->fd_out = -1; return 1; } diff --git a/src/plugins/sieve-extprograms/script-client.c b/src/plugins/sieve-extprograms/script-client.c index 06a5d5d54ba9..6fefca4c9f26 100644 --- a/src/plugins/sieve-extprograms/script-client.c +++ b/src/plugins/sieve-extprograms/script-client.c @@ -68,7 +68,8 @@ static void script_client_disconnect if (sclient->fd_in != -1 && close(sclient->fd_in) < 0) i_error("close(%s) failed: %m", sclient->path); - if (sclient->fd_out != -1 && sclient->fd_out != sclient->fd_out) + if (sclient->fd_out != -1 && sclient->fd_out != sclient->fd_in + && close(sclient->fd_out) < 0) i_error("close(%s/out) failed: %m", sclient->path); sclient->fd_in = sclient->fd_out = -1; -- Kirill A. Shutemov

3 6

[Dovecot] Errors in log file
by Christian Rößner 21 Dec '13

21 Dec '13

Hi, just wonder about some errors I found with: doveadm log errors: … Dec 16 17:21:55 imap(roessner@****): Error: stat(/srv/mail/virtual/*****/roessner/.dovecot.sieve/tmp) failed: Not a directory … And this is correct, it is a link: .dovecot.sieve -> sieve/default.sieve I do not see, where I have an error in my config ;) root@mx ~ # doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.11.2-hardened x86_64 Gentoo Base System release 2.2 ext4 auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes default_vsz_limit = 512 M disable_plaintext_auth = no imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_access_groups = mail mail_attachment_dir = /srv/mail/copymail/attachments mail_gid = mail mail_location = maildir:/srv/mail/virtual/%d/%n mail_plugins = quota acl fts fts_lucene zlib mail_log notify listescape mail_privileged_group = mail mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace { list = children location = maildir:%%h prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk-E-Mail { auto = subscribe special_use = \Junk } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /usr/local/sbin/ispcp-decrypt.py driver = checkpassword } plugin { acl = vfile acl_shared_dict = file:/srv/mail/virtual/shared-mailboxes.db fts = lucene fts_autoindex = yes fts_lucene = whitespace_chars=@. quota = dict:User quota::file:/srv/mail/virtual/%d/%n/dovecot-quota quota_grace = 10%% quota_rule = *:storage=2G:messages=20000 quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = -storage=100%% quota-warning below %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve zlib_save = gz zlib_save_level = 6 } postmaster_address = postmaster(a)deltaweb.de protocols = imap pop3 lmtp sieve service auth-worker { extra_groups = ssl-cert unix_listener auth-worker { mode = 0600 user = vmail } user = vmail } service auth { extra_groups = ssl-cert unix_listener /var/spool/postfix.relay/private/auth { group = postfix mode = 0660 user = postfix } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0660 user = vmail } user = vmail } service config { unix_listener config { mode = 0600 user = vmail } } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap-login { inet_listener imaps { port = 993 ssl = yes } } service lmtp { inet_listener lmtp { address = ::1 port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = vmail } ssl_cert = </etc/ssl/certs/mx_deltaweb_de.crt ssl_key = </etc/ssl/private/mx_deltaweb_de.key userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota acl fts fts_lucene zlib mail_log notify listescape sieve } protocol lda { mail_plugins = quota acl fts fts_lucene zlib mail_log notify listescape sieve } protocol imap { mail_max_userip_connections = 50 mail_plugins = quota acl fts fts_lucene zlib mail_log notify listescape imap_quota imap_acl imap_zlib } Any ideas? Thanks in advance :) Kind regards -Christian Rößner -- [*] 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, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

3 5

[Dovecot] Ignoring mount points for secondary dovecot instance does not seem to work
by Jouko Nikula 21 Dec '13

21 Dec '13

Hello, I tried to ignore all mountpoints in Dovecot. I have two dovecot instances running: root@fileserver# doveadm instance list path name last used running /usr/local/var/run/dovecot dovecot 2013-12-21 08:09:34 yes /var/run/dovecot.smtp smtp-auth 2013-12-21 08:09:34 yes I give commands: root@fileserver# doveadm mount add '/*' ignore root@fileserver# doveadm -i smtp-auth mount add '/*' ignore And then restart dovecot. In the log I can see that the main instance is now ignoring my mountpoints, but the smtp-auth instance is still warning about my mountpoints. Is this a bug or am I missing something? My configurations are as follows: root@fileserver# doveconf -ni smtp-auth # 2.2.9: /usr/local/etc/dovecot/dovecot.conf.smtp # OS: Linux 3.2.0-4-686-pae i686 Debian 7.1 auth_mechanisms = plain login base_dir = /var/run/dovecot.smtp/ first_valid_uid = 123 instance_name = smtp-auth log_timestamp = "%Y-%m-%d %H:%M:%S " mail_gid = mail mail_location = maildir:~/mail mail_uid = vmail passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = dovecot driver = pam } protocols = service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/certs/imapd.pem ssl_key = </etc/ssl/private/imapd.pem userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } root@fileserver# doveconf -n # 2.2.9: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.1 auth_mechanisms = plain login first_valid_uid = 123 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_gid = mail mail_location = maildir:~/mail mail_uid = vmail passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = session=yes dovecot driver = pam } protocols = imap service auth-worker { user = vmail } ssl_cert = </etc/ssl/certs/imapd.pem ssl_key = </etc/ssl/private/imapd.pem userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } regards, - Jouko

1 0

[Dovecot] Thank you!
by Steve Litt 20 Dec '13

20 Dec '13

Hi all, I've been on this list for 18 months but almost completely as a lurker. You know why? Because Dovecot never, ever, ever screws up on me or displays unexpected behavior, so I never have technical questions. Thank you for producing such a rock solid piece of software! SteveT Steve Litt * http://www.troubleshooters.com/ Troubleshooting Training * Human Performance

1 0

Re: [Dovecot] configure lmtp to deliver to email addresses case insensitively
by Adrian Zaugg 20 Dec '13

20 Dec '13

Hi David > I believe RFC822 email addresses are case-insensitive, and (in some RFC 2821, Page 13, 1st paragraph: "The local-part of a mailbox MUST BE treated as case sensitive. Therefore, SMTP implementations MUST take care to preserve the case of mailbox local-parts. Mailbox domains are not case sensitive. In particular, for some hosts the user "smith" is different from the user "Smith". However, exploiting the case sensitivity of mailbox local-parts impedes interoperability and is discouraged." (http://tools.ietf.org/html/rfc2821#section-2.4) > cases, especially ones where there's just a mail server) it's entirely > possible that people remember their account names with some capital > letters that aren't in user db. (System knows you as > "mrsmithy(a)mail.domain", while the user may remember the account as > "MrSmithy(a)mail.domain" or "MrsMithy(a)mail.domain"...). Also, people with I just want login names to be case sensitive but not email addresses, and in spite of being treated as case insensitive email addresses should retain their case, just like defined and suggested in the RFC. This reduces support calls because it's con-formant and we have a clear policy: Usernames are always lower case, non-email addresses, the same simple and short name for all our services. There is nothing easier than this. We use this since 17 years and it works without confusion. If a user now spots that suddendly any capitalization of usernames is working when logging in to the webmail, how can I explain that this doesn't work with other services like FTP? > smartphones may not notice that the phone "helpfully" uppercased the > first letter of a lowercase user name. Forcing case reduces support > calls, which is always a good thing. That's why email addresses should be allowed containing capitalizations. On smartphone people tend to use MUAs and there the username is saved and not entered each and every time, so for the username this is less true, I think. Back to dovecot: Using LDA as a transport for the dovecot store, it used to work perfectly (with dovecot 1.x). It's just LMTP that spits, because it looks up the local part in the userdb, which is PAM in our case. I won't change PAM to act case insensitive: I'm not in the position to change a common sense in the computing world as it always was. It's enough Microsoft did that and probably just because of that we're having this discussion here... However, it's maybe best to lowercase the local part in the exim lmtp-transport and leave dovecot's LMTP in peace. Best regards, Adrian.

3 8

[Dovecot] Does quota-status respect quota_grace?
by Jiri Bourek 20 Dec '13

20 Dec '13

Hello, I have Dovecot 2.2.9 from Debian repository running on AMD64, ext4 filesystem for mail storage. Each mailbox has its own system user, quotas are enforced by file system. Quota settings in configuration are as follows (from doveconf -n): quota = fs:Domain quota:group:inode_per_mail quota2 = fs:Mailbox quota:user:inode_per_mail quota2_grace = 18%% quota_grace = 18%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO Quota rules are read from PostgreSQL (snippet) user_query = ... '*:bytes=' || domains.quota_size || 'M:messages=' || domains.quota_files as quota_rule, \ '*:bytes=' || mailboxes.quota_size || 'M:messages=' || mailboxes.quota_files as quota2_rule, \ ... As far as I can tell, quota enforcing in dovecot-lda works correctly. User is allowed one message which brings him over quota (provided the message fits into filesystem quota hard limit and quota_grace value), every other message after that is rejected. However policy service quota-status for Postfix seems to ignore the quota_grace value. When a message arrives which would make user go over quota (but which would not make him exceed the grace limit value), Postfix checks the policy service and is told to reject the message. I checked and dovecot itself is fine with the message - if I try to send it with the policy service check disabled, Postfix accepts it and so does dovecot-lda, the message is delivered into mailbox. My question is - is that intended behavior or bug in the quota-status? Appending some lines from debug log - as far as I can see there's not much in it though: dovecot: quota-status: Debug: Added userdb setting: mail=maildir:/home/mailboxes/t/e/test.info/test/:LAYOUT=fs:INDEX=/var/lib/dovecot-data/index/1010:CONTROL=/var/lib/dovecot-data/control/1010 dovecot: quota-status: Debug: Added userdb setting: plugin/quota2_rule=*:bytes=11M:messages=110 dovecot: quota-status: Debug: Added userdb setting: plugin/quota_rule=*:bytes=15M:messages=150 dovecot: quota-status(test(a)test.info): Debug: Effective uid=1010, gid=1007, home=/home/mailboxes/t/e/test.info/test/ dovecot: quota-status(test(a)test.info): Debug: Quota root: name=Domain quota backend=fs args=group:inode_per_mail dovecot: quota-status(test(a)test.info): Debug: Quota rule: root=Domain quota mailbox=* bytes=15728640 messages=150 dovecot: quota-status(test(a)test.info): Debug: Quota grace: root=Domain quota bytes=2831155 (18%) dovecot: quota-status(test(a)test.info): Debug: Quota root: name=Mailbox quota backend=fs args=user:inode_per_mail dovecot: quota-status(test(a)test.info): Debug: Quota rule: root=Mailbox quota mailbox=* bytes=11534336 messages=110 dovecot: quota-status(test(a)test.info): Debug: Quota grace: root=Mailbox quota bytes=2076180 (18%) dovecot: quota-status(test(a)test.info): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/home/mailboxes/t/e/test.info/test/:LAYOUT=fs:INDEX=/var/lib/dovecot-data/index/1010:CONTROL=/var/lib/dovecot-data/control/1010 dovecot: quota-status(test(a)test.info): Debug: fs: root=/home/mailboxes/t/e/test.info/test, index=/var/lib/dovecot-data/index/1010, indexpvt=, control=/var/lib/dovecot-data/control/1010, inbox=/home/mailboxes/t/e/test.info/test, alt= dovecot: quota-status(test(a)test.info): Debug: fs quota add mailbox dir = /home/mailboxes/t/e/test.info/test dovecot: quota-status(test(a)test.info): Debug: fs quota block device = /dev/sdc1 dovecot: quota-status(test(a)test.info): Debug: fs quota mount point = /home dovecot: quota-status(test(a)test.info): Debug: fs quota mount type = ext4

3 5

[Dovecot] mirror to download dovecot
by Edwardo Garcia 20 Dec '13

20 Dec '13

Halo, Is mirror to get 2.2.9? cannot get dovecot.org, this time out 4 xe-0-1-0-1-3664.r00.saplbr01.br.bb.gin.ntt.net (200.15.0.45) 6.946 ms 7.093 ms 6.899 ms 5 xe-4-1-3.r20.miamfl02.us.bb.gin.ntt.net (129.250.3.217) 118.130 ms 118.111 ms 118.117 ms 6 ae-1.r05.miamfl02.us.bb.gin.ntt.net (129.250.2.185) 118.592 ms 118.735 ms 118.628 ms 7 * * * 8 * * * 9 * * * I use to get from dovecot.ausics.org but fail connect too, seem has DNS 127.0.0.1 ????? is any others run mirror?

3 3

[Dovecot] reproducible dsync backup panic (dovecot 2.2.7)
by Peter Benko 20 Dec '13

20 Dec '13

Hi all, I'm receiving a reproducible dsync backup panic for some of my users. The error message is as follows: dsync-remote(user@<removed>): Panic: file dsync-brain-mailbox-tree-sync.c: line 111 (dsync_brain_mailbox_tree_sync_change): assertion failed: (brain->no_backup_overwrite) dsync-remote(user@<removed>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x69b70) [0x7f922dad9b70] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f922dad9c4a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f922da94725] -> /usr/bin/dsync(dsync_brain_mailbox_tree_sync_change+0x382) [0x42f912] -> /usr/bin/dsync(dsync_brain_recv_mailbox_tree_deletes+0x10b) [0x42f4db] -> /usr/bin/dsync(dsync_brain_run+0x305) [0x42c6f5] -> /usr/bin/dsync() [0x42cbe8] -> /usr/bin/dsync() [0x43e040] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f922daea066] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7) [0x7f922daeaf07] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f922dae9b78] -> /usr/bin/dsync() [0x4297f9] -> /usr/bin/dsync() [0x4133cd] -> /usr/bin/dsync(doveadm_mail_try_run+0x251) [0x414091] -> /usr/bin/dsync(main+0x3c8) [0x412f78] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f922d704ead] -> /usr/bin/dsync() [0x413191] dsync-local(user@<removed>): Error: read(<remote-mail-server>) failed: EOF dsync-local(user@<removed>): Error: Remote command returned error 134 The command I'm using to back up individual user's mail is something like: sudo -u vmail dsync -v -u user(a)server.com -R backup ssh -i sshid-file login(a)server.com sudo -u vmail dsync -v -u user(a)server.com I use the above command at the backup server. The error started to appear a few weeks after we started using the new mail system. First it appeared for a single user, now it appears for some more users as well. It is deterministic and reproducible. Any ideas? I included the relevant part of my config below. Best regards, Peter ------------------------------------------------------------------- # 2.2.7 (5c876ed0c3e0): /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.2 auth_master_user_separator = * auth_mechanisms = plain login hostname = <removed> listen = * login_greeting = $hostname IMAP server mail_attachment_dir = /mail/mailboxes/%d/_attachments_ mail_attachment_fs = sis-queue $mail_attachment_dir/queue:posix mail_attachment_min_size = 16 k mail_location = mdbox:~ mail_plugins = " zlib acl" mdbox_rotate_interval = 5 days mdbox_rotate_size = 5 M namespace { inbox = yes location = prefix = separator = / type = private } namespace { list = children location = mdbox:/mail/mailboxes/%%d/%%n:INDEX=/mail/mailboxes/%%d/%%n prefix = Accounts/%%n/ separator = / subscriptions = no type = shared } passdb { args = /mail/config/dovecot/passwd driver = passwd-file } passdb { args = /mail/config/dovecot/passwd-master driver = passwd-file master = yes pass = yes } plugin { acl = vfile acl_defaults_from_inbox = yes acl_shared_dict = file:/mail/mailboxes/%d/shared-mailboxes.db zlib_save = gz zlib_save_level = 6 } postmaster_address = postmaster@<removed> protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } syslog_facility = local6 userdb { args = uid=vmail gid=vmail master_user=%u home=/mail/mailboxes/%d/%n driver = static } protocol imap { mail_plugins = " zlib acl imap_acl" }

2 1

[Dovecot] auth failures
by Andreas Schulze 19 Dec '13

19 Dec '13

Hello, last week and today our dovecot pop3 server stopped responding. Without any other logentries dovecot start to log only this: Dec 12 09:14:12 mbox1 dovecot: auth: Error: ldap(testuser,192.0.2.110,<FBZH7lHtAQAK/FCj>): ldap_search(base=ou=accounts,dc=example,dc=de filter=(&(|(uid=testuser)(mail=testuser))(!(state=blocked)))) failed: Operations error For every pop3 Session, ~2000 per Minute ..., over 10 Minutes I send dovecot a SIGTERM. After dovecot was started again, all was fine again. # doveconf -n http://postmaster.datev.de/tmp/dovecot.conf The LDAP-Server itself did resond to queries in the same timeframe. I know this because the MTA on the same host was able to deliver messages into mailboxes. Any hints? Thanks Andreas -- Andreas Schulze Internetdienste | P252 DATEV eG 90329 Nürnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196 E-Mail info @datev.de | Internet www.datev.de Sitz: 90429 Nürnberg, Paumgartnerstr. 6-14 | Registergericht Nürnberg, GenReg Nr.70 Vorstand Prof. Dieter Kempf (Vorsitzender) Dipl.-Kfm. Wolfgang Stegmann (stellvertretender Vorsitzender) Dipl.-Kfm. Michael Leistenschneider Dipl.-Kfm. Dr. Robert Mayr Jörg Rabe v. Pappenheim Dipl.-Vw. Eckhard Schwarzer Vorsitzender des Aufsichtsrates: Reinhard Verholen

2 1

[Dovecot] External auth
by eechim enorniel 19 Dec '13

19 Dec '13

Hello, I saw a lot of tutorials about setting postfix with dovecot sasl but I would like more. I want to set a SSO system with roundcube on dovecot. I would like to know how to make dovecot work with sasl or saml, not as a provider but as a service plugging on an external provider. I saw there is an EXTERNAL auth mechanism but I didn't find any doc about it. Can you help me ? Thanks.

2 1

[Dovecot] Mailbox with .broken files
by Michael Smith (DF) 19 Dec '13

19 Dec '13

We're using Dovecot 2.2.4 and mdbox storage with compression. I noticed yesterday that at least one of the accounts has unusual files in it's mail/storage directory. This account has approximately 17.5G of compressed mail, across about 750 storage files (m.###) using 8G of storage. Starting on Dec 11, storage files m.409 through m.731 have not only their m.### file, but also a m.###.broken file. At the same time .temp.<unix time>.<unique id>.<hostname> files also started showing up... ... -rw--w---- 1 user123 mail 3225 Dec 12 04:38 m.708 -rw--w---- 1 user123 mail 167106 Dec 12 03:35 m.708.broken -rw--w---- 1 user123 mail 46155 Dec 12 04:38 m.709 -rw--w---- 1 user123 mail 177267 Dec 12 03:40 m.709.broken -rw--w---- 1 user123 mail 20965889 Nov 26 19:22 m.71 -rw--w---- 1 user123 mail 133248 Dec 12 04:38 m.710 -rw--w---- 1 user123 mail 264361 Dec 12 03:40 m.710.broken -rw--w---- 1 user123 mail 103407 Dec 12 04:38 m.711 -rw--w---- 1 user123 mail 627736 Dec 12 03:40 m.711.broken -rw--w---- 1 user123 mail 5132 Dec 12 04:38 m.712 -rw--w---- 1 user123 mail 136244 Dec 12 03:40 m.712.broken -rw--w---- 1 user123 mail 187224 Dec 12 04:38 m.713 -rw--w---- 1 user123 mail 351104 Dec 12 03:45 m.713.broken -rw--w---- 1 user123 mail 435793 Dec 12 04:38 m.714 -rw--w---- 1 user123 mail 566906 Dec 12 03:45 m.714.broken -rw--w---- 1 user123 mail 60916 Dec 12 04:38 m.715 -rw--w---- 1 user123 mail 192028 Dec 12 03:50 m.715.broken -rw--w---- 1 user123 mail 38051 Dec 12 04:38 m.716 -rw--w---- 1 user123 mail 169163 Dec 12 03:50 m.716.broken -rw--w---- 1 user123 mail 226067 Dec 12 04:38 m.717 -rw--w---- 1 user123 mail 389948 Dec 12 04:00 m.717.broken ... -rw--w---- 1 user123 mail 20967506 Dec 2 17:32 m.96 -rw--w---- 1 user123 mail 20967131 Dec 2 18:40 m.97 -rw--w---- 1 user123 mail 20969078 Dec 2 18:38 m.98 -rw--w---- 1 user123 mail 20963978 Dec 2 19:23 m.99 -rw--w---- 1 user123 mail 294968 Dec 11 20:05 .temp.1386813944.P9142Q0M123686.myhost -rw--w---- 1 user123 mail 294968 Dec 11 20:05 .temp.1386813967.P9213Q0M387733.myhost -rw--w---- 1 user123 mail 294968 Dec 11 20:05 .temp.1386813970.P9231Q0M371190.myhost -rw--w---- 1 user123 mail 327736 Dec 11 20:05 .temp.1386813972.P9173Q0M932070.myhost -rw--w---- 1 user123 mail 327736 Dec 11 20:05 .temp.1386813972.P9239Q0M114754.myhost -rw--w---- 1 user123 mail 327736 Dec 11 20:05 .temp.1386813983.P9261Q0M640646.myhost -rw--w---- 1 user123 mail 1048632 Dec 11 20:06 .temp.1386814038.P9515Q0M530600.myhost I'm not really seeing anything that stands out in the maillog during this time. What caused this problem? How concerned should I be about possible lost email? This is a production environment. Below is the dovecot -n output. -- Michael Smith # dovecot -n # 2.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.19.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) auth_debug = yes auth_debug_passwords = yes auth_default_realm = mydomain.com auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no dotlock_use_excl = no lda_mailbox_autocreate = yes lock_method = dotlock mail_access_groups = mail mail_debug = yes mail_fsync = always mail_location = mdbox:~/mail:INDEX=~/index mail_plugins = quota zlib mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mbox_read_locks = dotlock mbox_write_locks = dotlock mdbox_rotate_interval = 1 weeks mdbox_rotate_size = 20 M mmap_disable = yes namespace { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = type = private } passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { autosubscribe = Trash autosubscribe2 = Junk autosubscribe3 = Drafts autosubscribe4 = Sent autosubscribe5 = INBOX mail_max_userip_connections = 10 managesieve_max_line_length = 65536 quota = dict:User quota::file:%h/dovecot.quota quota2_rule = Trash:storage=+10%% quota3_rule = Junk:storage=+20%% quota_rule = *:storage=100M:messages=100000 recipient_delimiter = + sieve_before = /var/opt/mail/global.sieve/ zlib_save = gz zlib_save_level = 9 } pop3_reuse_xuidl = yes protocols = imap pop3 sieve lmtp service auth { inet_listener auth { port = 113 } unix_listener auth-userdb { user = nobody } } service lmtp { inet_listener lmtp { port = 24 } process_min_avail = 10 service_count = 1 } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = quota zlib sieve } protocol imap { mail_plugins = quota zlib imap_quota } protocol sieve { mail_max_userip_connections = 10 mail_plugins = quota zlib managesieve_max_line_length = 65536 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date } protocol lmtp { mail_plugins = quota zlib sieve }

2 1

Re: [Dovecot] Mailbox with .broken files
by Michael Smith (DF) 19 Dec '13

19 Dec '13

Anyone have any feedback, guidance or suggestions on this? Timo? -----Original Message----- From: Michael Smith (DF) [mailto:msmith@datafoundry.com] Sent: Friday, December 13, 2013 9:49 AM To: 'dovecot(a)dovecot.org' Subject: [Dovecot] Mailbox with .broken files We're using Dovecot 2.2.4 and mdbox storage with compression. I noticed yesterday that at least one of the accounts has unusual files in it's mail/storage directory. This account has approximately 17.5G of compressed mail, across about 750 storage files (m.###) using 8G of storage. Starting on Dec 11, storage files m.409 through m.731 have not only their m.### file, but also a m.###.broken file. At the same time .temp.<unix time>.<unique id>.<hostname> files also started showing up... ... -rw--w---- 1 user123 mail 3225 Dec 12 04:38 m.708 -rw--w---- 1 user123 mail 167106 Dec 12 03:35 m.708.broken -rw--w---- 1 user123 mail 46155 Dec 12 04:38 m.709 -rw--w---- 1 user123 mail 177267 Dec 12 03:40 m.709.broken -rw--w---- 1 user123 mail 20965889 Nov 26 19:22 m.71 -rw--w---- 1 user123 mail 133248 Dec 12 04:38 m.710 -rw--w---- 1 user123 mail 264361 Dec 12 03:40 m.710.broken -rw--w---- 1 user123 mail 103407 Dec 12 04:38 m.711 -rw--w---- 1 user123 mail 627736 Dec 12 03:40 m.711.broken -rw--w---- 1 user123 mail 5132 Dec 12 04:38 m.712 -rw--w---- 1 user123 mail 136244 Dec 12 03:40 m.712.broken -rw--w---- 1 user123 mail 187224 Dec 12 04:38 m.713 -rw--w---- 1 user123 mail 351104 Dec 12 03:45 m.713.broken -rw--w---- 1 user123 mail 435793 Dec 12 04:38 m.714 -rw--w---- 1 user123 mail 566906 Dec 12 03:45 m.714.broken -rw--w---- 1 user123 mail 60916 Dec 12 04:38 m.715 -rw--w---- 1 user123 mail 192028 Dec 12 03:50 m.715.broken -rw--w---- 1 user123 mail 38051 Dec 12 04:38 m.716 -rw--w---- 1 user123 mail 169163 Dec 12 03:50 m.716.broken -rw--w---- 1 user123 mail 226067 Dec 12 04:38 m.717 -rw--w---- 1 user123 mail 389948 Dec 12 04:00 m.717.broken ... -rw--w---- 1 user123 mail 20967506 Dec 2 17:32 m.96 -rw--w---- 1 user123 mail 20967131 Dec 2 18:40 m.97 -rw--w---- 1 user123 mail 20969078 Dec 2 18:38 m.98 -rw--w---- 1 user123 mail 20963978 Dec 2 19:23 m.99 -rw--w---- 1 user123 mail 294968 Dec 11 20:05 .temp.1386813944.P9142Q0M123686.myhost -rw--w---- 1 user123 mail 294968 Dec 11 20:05 .temp.1386813967.P9213Q0M387733.myhost -rw--w---- 1 user123 mail 294968 Dec 11 20:05 .temp.1386813970.P9231Q0M371190.myhost -rw--w---- 1 user123 mail 327736 Dec 11 20:05 .temp.1386813972.P9173Q0M932070.myhost -rw--w---- 1 user123 mail 327736 Dec 11 20:05 .temp.1386813972.P9239Q0M114754.myhost -rw--w---- 1 user123 mail 327736 Dec 11 20:05 .temp.1386813983.P9261Q0M640646.myhost -rw--w---- 1 user123 mail 1048632 Dec 11 20:06 .temp.1386814038.P9515Q0M530600.myhost I'm not really seeing anything that stands out in the maillog during this time. What caused this problem? How concerned should I be about possible lost email? This is a production environment. Below is the dovecot -n output. -- Michael Smith # dovecot -n # 2.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.19.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) auth_debug = yes auth_debug_passwords = yes auth_default_realm = mydomain.com auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no dotlock_use_excl = no lda_mailbox_autocreate = yes lock_method = dotlock mail_access_groups = mail mail_debug = yes mail_fsync = always mail_location = mdbox:~/mail:INDEX=~/index mail_plugins = quota zlib mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mbox_read_locks = dotlock mbox_write_locks = dotlock mdbox_rotate_interval = 1 weeks mdbox_rotate_size = 20 M mmap_disable = yes namespace { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = type = private } passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { autosubscribe = Trash autosubscribe2 = Junk autosubscribe3 = Drafts autosubscribe4 = Sent autosubscribe5 = INBOX mail_max_userip_connections = 10 managesieve_max_line_length = 65536 quota = dict:User quota::file:%h/dovecot.quota quota2_rule = Trash:storage=+10%% quota3_rule = Junk:storage=+20%% quota_rule = *:storage=100M:messages=100000 recipient_delimiter = + sieve_before = /var/opt/mail/global.sieve/ zlib_save = gz zlib_save_level = 9 } pop3_reuse_xuidl = yes protocols = imap pop3 sieve lmtp service auth { inet_listener auth { port = 113 } unix_listener auth-userdb { user = nobody } } service lmtp { inet_listener lmtp { port = 24 } process_min_avail = 10 service_count = 1 } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = quota zlib sieve } protocol imap { mail_plugins = quota zlib imap_quota } protocol sieve { mail_max_userip_connections = 10 mail_plugins = quota zlib managesieve_max_line_length = 65536 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date } protocol lmtp { mail_plugins = quota zlib sieve }

1 0

[Dovecot] v2.2.9 released
by Timo Sirainen 19 Dec '13

19 Dec '13

http://dovecot.org/releases/2.2/dovecot-2.2.9.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.9.tar.gz.sig + Full text search indexing can now be done automatically after saving/copying mails by setting plugin { fts_autoindex=yes } + replicator: Added replication_dsync_parameters setting to pass "doveadm sync" parameters (for controlling what to replicate). + Added mail-filter plugin + Added liblzma/xz support (zlib_save=xz) - v2.2.8's improved cache file handling exposed several old bugs related to fetching mail headers. - v2.2.7's iostream handling changes were causing some connections to be disconnected before flushing their output (e.g. POP3 logout message wasn't being sent)

7 9

[Dovecot] zlib plugin question
by Przemysław Orzechowski 19 Dec '13

19 Dec '13

Hi Is it possible to compress incoming mails delivered via dovecots LDA when using dovecot --version 1.2.9 or do i have to compress them via cron?

2 2

[Dovecot] problem with password in a changing scenario
by Angel Luis Mateo Martinez 19 Dec '13

19 Dec '13

Hello, I'm having a problem with with password changing. According to http://wiki2.dovecot.org/Authentication/Caching, I understand "normal scenario" and "Using old cached password scenario", but I'm having a problem with the "Early change scenario". I understand that in this case, if in step 4 user tries password Y, then this password is not tried again and login fails. But if the user tries another password Z, then is it test it? Or does it directly fail? I think that it is directly failing. And here is my problem... I am using dovecot with a ldap backend and another pam backend. The first one is users connecting with an email client. The other one applies when the ldap backend fails and it is use for connections from our webmail, which is integrated in our CAS SSO environment (it has running an imap proxy too). Sometimes (the only scenari we were able to reproduce is with users that for some reason has two SSO sessions opened) dovecot receives an invalid CAS ticket, then authentication fails, and no newer tickets are tried until cache is clean. That's why I think that in this scenario another Z password is even tried. Any idea? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

1 0

[Dovecot] letters local filter duplicated
by John Smith 18 Dec '13

18 Dec '13

two servers with replicated master/master. dovecot.conf = http://pastebin.com/jVnvyWZM with this setup letters processed local filter duplicated. ie when the mail client receives a letter begins processing using rules (filters) to move the letters in a different folder. summarized in this folder is two duplicate letters. if you disable the filter, the message is not duplicated. But does not move to another location. -- Best Regards, Evgeny Senior System Administrator OOO "Vaz Service Hurley"

3 4