- dovecot - dovecot.org

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

02 Jan '14

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

2 1

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

02 Jan '14

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

1 0

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

01 Jan '14

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

1 0

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

31 Dec '13

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

2 1

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

30 Dec '13

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

6 10

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

30 Dec '13

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

1 0

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

30 Dec '13

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

2 2

[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