- dovecot - dovecot.org

[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