- dovecot - dovecot.org

Can't get shared public folders working
by Randall Gellens 12 Dec '14

12 Dec '14

I'm trying to use a shared public namespace. Clients say it exists, but sieve scripts can't write to it. The configuration in /etc/dovecot/conf.d/10-mail.conf: # Shared namespace for Foo stuff namespace { type = public separator = '/' prefix = "#Foo/" location = maildir:/local/mnt/mail/shared:INDEXPVT=/local/mnt/mail/%n/shared:LAYOUT=fs # Use the default namespace for saving subscriptions. #subscriptions = no # List the shared/ namespace only if there are visible shared mailboxes. #list = children } I created the location, owned by the vmail user: $ ls -ld /local/mnt/mail/shared drwxr-xr-x 4 vmail vmail 4096 Dec 11 12:38 /local/mnt/mail/shared I created the subfolders, verified that they are there. Also, I see that Dovecot created a dovecot.mailbox.log file: $ ls -l /local/mnt/mail/shared total 12 -rw-r--r-- 1 vmail vmail 96 Dec 11 12:38 dovecot.mailbox.log drwxr-xr-x 3 vmail vmail 4096 Dec 11 12:37 Foo-Bugs drwxr-xr-x 3 vmail vmail 4096 Dec 11 12:38 Foo-Patches The dovecot.mailbox.log file is empty: $ more /local/mnt/mail/shared/dovecot.mailbox.log The intermediate folder is empty: $ ls -l /local/mnt/mail/shared/Foo-Bugs/ total 4 drwxr-xr-x 5 vmail vmail 4096 Dec 11 12:36 Foo-Bugs-New The mailbox has some folders in it: $ ls -l /local/mnt/mail/shared/Foo-Bugs/Foo-Bugs-New/ total 12 drwxr-xr-x 2 vmail vmail 4096 Dec 11 12:36 cur drwxr-xr-x 2 vmail vmail 4096 Dec 11 12:36 new drwxr-xr-x 2 vmail vmail 4096 Dec 11 12:36 tmp They seem to be empty: $ ls -l /local/mnt/mail/shared/Foo-Bugs/Foo-Bugs-New/* /local/mnt/mail/shared/Foo-Bugs/Foo-Bugs-New/cur: The Sieve log insists the mailbox doesn't exist: $ more /local/mnt/home/Foo-bugs/.dovecot.sieve.log sieve: info: started log at Dec 11 15:35:20. error: msgid=<p06240614d0afdab4a086(a)[99.111.97.136]>: failed to store into mailbox '#Foo/Q popper-Bugs/Foo-Bugs-New': Mailbox doesn't exist: #Foo/Foo-Bugs/Foo-Bugs-New. info: msgid=<p06240614d0afdab4a086(a)[99.111.97.136]>: stored mail into mailbox 'INBOX'. But if I telnet into the server, the mailbox shows up: a1 list "" * * LIST (\HasNoChildren \Junk) "/" Junk * LIST (\Noselect \HasChildren) "/" #Foo * LIST (\Noselect \HasChildren) "/" #Foo/Foo-Patches * LIST (\HasNoChildren) "/" #Foo/Foo-Patches/Foo-Patches-New * LIST (\Noselect \HasChildren) "/" #Foo/Foo-Bugs * LIST (\HasNoChildren) "/" #Foo/Foo-Bugs/Foo-Bugs-New * LIST (\HasNoChildren) "/" INBOX a1 OK List completed. And I can SELECT it: a2 select "#Foo/Foo-Bugs/Foo-Bugs-New" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1418343553] UIDs valid * OK [UIDNEXT 1] Predicted next UID * OK [NOMODSEQ] No permanent modsequences a2 OK [READ-WRITE] Select completed (0.006 secs). So why can't the Sieve script store into it? -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly selected tag: --------------- Broad-mindedness: The result of flattening high-mindedness out.

1 0

mdbox backup strategy
by Jiří František 11 Dec '14

11 Dec '14

Hi, now we backup maildir with rdiff-backup every single day. Backup takes almost 20hours. I would like to switch to mdbox, but how to acomplish possibility of restore emails from any date what I want? Now if I need to restore mails from the day before yesterday I put the right date to parametrs of rdiff-backup restore command and I get what I want. But if I use doveadm backup I have backup only from last run. Because we have tens of TB email I couldn't do full backup every single day. Is it possible to restore state of mailbox from backup run before the last run if I use doveadm? I don't want do full backup every day, because backup storage is not unlimited. Thank you Jiri

1 0

dovecot.index.log files: what are they?
by Thomas Klausner 11 Dec '14

11 Dec '14

Hi! I have lots of these files: /home/wiz/Mail/my-folder-name/cur/.imap/1238738125.13533_23713.danbala:2,S/dovecot.index.log What are they for? Why are they here? Can I remove them? Thomas

2 4

dovecot & Apple Mail & maildir & lots of Mail
by Thomas Klausner 11 Dec '14

11 Dec '14

Hi! I have dovecot 2.1.12 running on a mail server, and recently configured Apple Mail to connect to it using secure IMAP, for the first time. At the beginning it just showed the inbox and everything was fine, but then I wanted to look at some of my folders and found the 'subscribe' menu. When I opened it, Apple Mail went to discover what mailboxes there are, and that's where my trouble began. It seemed to make good progress for some time (though slow -- over days), and now lists the mailboxes from starting with letters a to d on the left hand side (filling all the visible space, so there might be more). However, whenever Apple Mail gets focus, the cursor becomes a spinning rainbow circle and I can't interact with it. I tried deleting the mail account and setting it up again. The inbox was shown again immediately and Apple Mail was usable, but the first time the cursor moved over the mailboxes on the left hand side, it froze again. There were two imap processes on the server, one rather idle, the other eating CPU for about two minutes, then idling, and some time later it disappeared too. My Mail directory is 31G with about 180 directories, each containing mails in maildir format. Has anyone had similar issues? Is my maildir too big for dovecot too handle? How can I debug this? Thanks, Thomas

5 6

Quota issue with mailbox.
by Grant Pasley 11 Dec '14

11 Dec '14

good morning, i am experiencing an issue with a quot limits with a new install of dovecot with mysql integration. quotas are set to 0 (unlimited) and show as such in the mysql database as well as via the postfixadmin frontend. i use imapsync to transfer mail from another imap server to this one, the total user mailbox size is 18gb. dovecot lda tells me mailbox is full even though i have set mailbox to unlimited. *the the error is:* Dec 9 19:17:01 sentinel dovecot: lda(grant(a)xxxxxxx.com): msgid=<e8b2c897c11cafda2c2ab93a92beb681(a)localhost.localdomain>: rejected: Quota exceeded (mailbox for user is full) *[root@sentinel dovecot]# grep -v '^ *$#.*$\?$' dovecot-mysql.conf* driver = mysql connect = host=localhost dbname=postfix user=postfix password=xxxxxxxx default_pass_scheme = MD5-CRYPT password_query = SELECT username as user, password, concat('/home/vmail/', maildir) as userdb_home, concat('maildir:/home/vmail/', maildir) as userdb_mail, 101 as userdb_uid, 12 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' user_query = SELECT concat('/home/vmail/', maildir) as home, concat('maildir:/home/vmail/', maildir) as mail, 101 AS uid, 12 AS gid, CONCAT('*:messages=10000:bytes=', quota) as quota_rule FROM mailbox WHERE username = '%u' AND active = '1' *[root@sentinel dovecot]# dovecot -n* *# 2.0.9: /etc/dovecot/dovecot.conf* *# OS: Linux 2.6.32-504.1.3.el6.x86_64 x86_64 CentOS release 6.6 (Final) ext4* auth_mechanisms = plain login dict { quotadict = mysql:/etc/dovecot/dovecot-dict-quota.conf } first_valid_gid = 12 first_valid_uid = 101 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_save_to_detail_mailbox = yes mail_location = maildir:/home/vmail/%d/%n 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 passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { acl = vfile:/etc/dovecot/acls quota = dict:user::proxy::quotadict sieve = ~/dovecot.sieve sieve_before = /home/sieve/globalfilter.sieve sieve_dir = ~/sieve sieve_max_script_size = 1M trash = /etc/dovecot/trash.conf } protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = mail mode = 0666 user = vmail } } service dict { unix_listener dict { group = mail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service imap { vsz_limit = 256 M } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = </etc/pki/tls/certs/xxxxxxxxxxxxxxxx.crt ssl_key = </etc/pki/tls/private/xxxxxxxxxxxxxxxxx.key userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol lda { mail_plugins = quota sieve postmaster_address = postmaster@xxxxxxxxxxxxxx } protocol imap { imap_client_workarounds = delay-newmail mail_plugins = quota imap_quota trash } protocol lmtp { mail_plugins = sieve } protocol pop3 { mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol sieve { managesieve_implementation_string = Dovecot Pigeonhole managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 } --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com

2 2

Re: dovecot.index.log files: what are they?
by Joseph Tam 10 Dec '14

10 Dec '14

Thomas Klausner writes: >> RTFM: http://wiki2.dovecot.org/IndexFiles > > Thanks, but I had read this. > > I still don't know what they are good for, why they stay there for > days and if I can remove them. After all, they are not the caches, but > some "transaction logs" (I don't know what this is). Re-read the page, all the way to the bottom. Interpreting the last section: The transaction log records recent changes to a mailbox, and together with the index, gives the current state of the mailbox. This is an I/O optimization so that mailbox states changes are quickly updated without having to compare an entire index file with the last (in-memory?) index. For large mailboxes, this can save a lot of I/O. It may persist because updates to the indices are not done immediately (again, possibly to reduce I/O), so the current mailbox state is reflected by the index file *and* deltas in the transaction log. I suspect that you could remove the transaction logs (if you do not use dbox) and dovecot should rebuild them (or more likely, rebuild the indices). Joseph Tam <jtam.home(a)gmail.com>

1 0

devoid mailbox status for mail reloaded from a tape backup
by Stephen Lidie 10 Dec '14

10 Dec '14

dovecot --version 2.2.10 I've only be able to status a mailbox for currently existing users, is it possible to status a mailbox reloaded from tape to an alternate location? The user may or may not exist at this time, but I still need to inspect the mailbox ... thank you, Steve

3 9

Renaming directories with subdirectories over IMAP
by Зинин Дмитрий Андреевич 10 Dec '14

10 Dec '14

Hi, I¹ve a problem with renaming directories with subdirectories. In root directory I create directory named ³lvl1² with subdirectory ³lvl2² When I rename directory lvl1 to lvl1-new I get: 1. /lvl1-new with subdir lvl2 but I can use only /lvl1-new and not /lvl1-new/lvl2 2. /lvl1 with subdir lvl2 but I can use only /lvl1/lvl2 and not /lvl1 Is it a feature or a bug? If bug is there a fix? PS: CentOS 6.6 and Dovecot 2.0.9-7 from official repository with all updates. Best regards, Dmitriy

2 1

Panic: file mail-index-sync-update.c: line 250 (sync_expunge_range): assertion failed: (count > 0)
by Ralf Hildebrandt 10 Dec '14

10 Dec '14

We're seeing this: % doveadm force-resync -u USERNAME INBOX doveadm(USERNAME): Panic: file mail-index-sync-update.c: line 250 (sync_expunge_range): assertion failed: (count > 0) doveadm(USERNAME): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x817ad) [0x33ab08317ad] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x3a) [0x33ab08318ba] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x33ab07d7570] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xced79) [0x33ab0b7ad79] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xc67) [0x33ab0b7ba07] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x1a4) [0x33ab0b7bdf4] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_map+0x15c) [0x33ab0b6b70c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xba44a) [0x33ab0b6644a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xba5e8) [0x33ab0b665e8] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_open+0x88) [0x33ab0b666f8] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x45762) [0x33ab0af1762] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_map_open_or_create+0x42) [0x33ab0af1a92] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_storage_rebuild_in_context+0x10b) [0x33ab0af839b] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_sync_begin+0x222) [0x33ab0af61f2] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_sync+0x45) [0x33ab0af67d5] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_storage_sync_init+0xa8) [0x33ab0af68e8] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x3d) [0x33ab0b2490d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x33ab0b24a87] -> doveadm(+0x1c0dc) [0x5a1f7f90dc] -> doveadm(+0x1bd1b) [0x5a1f7f8d1b] -> doveadm(doveadm_mail_try_run+0x267) [0x5a1f7f9d37] -> doveadm(main+0x404) [0x5a1f7f5a64] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x33ab042cd55] -> doveadm(+0x18cb9) [0x5a1f7f5cb9] # doveadm quota get -u USERNAME Quota name Type Value Limit % user STORAGE 4587 3145728 0 user MESSAGE 3 - 0 The user has an EMPTY mailbox with 3 folders (when connecting via IMAP) But looking in $HOME, I'm seeing: # du -sh . 1.6G. The user cannot receive mail: Dec 10 14:09:57 lmtp(86133, USERNAME): Fatal: master: service(lmtp): child 86133 killed with signal 6 (core dumps disabled) Dec 10 14:09:57 lmtp(106153, USERNAME): Fatal: master: service(lmtp): child 106153 killed with signal 6 (core dumps disabled) -- [*] 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, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

2 1

doveadm -A operations failing due to broken mdbox
by Ralf Hildebrandt 10 Dec '14

10 Dec '14

I'm using "/usr/bin/doveadm purge -A" to purge the mdboxes of my users. Unfortunately this command terminates prematurely once it reaches a defective mdbox! Is there a workaround for this? Like using doveadm to get a list of valid users and then run "doveadm purge -u" on each of those? -- [*] 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, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

3 3

Re: Required SSL with exceptions
by dovecot＠outputservices.com 09 Dec '14

09 Dec '14

On 12/08/14 23:50, SATOH Fumiyasu wrote: > Hi, > > At Mon, 08 Dec 2014 16:01:43 -0600, > List wrote: >> Essentially we would like to host IMAP with SSL enforced for any connections coming from anywhere except the subnet where our other mail servers reside. The idea is to not install a local instance of dovecot on the webmail/carddav/caldav servers to reduce the number of instances that need to be managed. Is it possible to have two imap listeners, where ssl is enforced on one port, and not on another? > > Use login_trusted_networks parameter. > What is the syntax for login_trusted_networks? The docs and WIKI do not show it.

2 1

Dovecot Pre-Login Scripting
by Jeremy Hayden 09 Dec '14

09 Dec '14

Hello, We are in the process of migrating users from one system that is currently not hosted by our company, to our dovecot 2.2.10 installation. We are planning on doing the dovecot dsync command for copying users mail over to the new installation, but the one snag we are running into is ensuring we are able to get the users credentials stored in our system. We are migrating the email from a Gmail ISP account to our installation as they are discontinuing their support next year. The setup is a multistep process we are hoping to accomplish. When a connection is started to our cluster, it will first check the database to see if the credentials match, if not it will verify against Gmail's servers. If the Gmail test is successful, it would pass the credentials to a script to store them for future login attempts. Once the authentication is verified and stored locally, we would run a post-login script to run dsync to copy the mail down to the new system. The problem we are running into is efficiently and appropriately hooking into the dovecot authentication process. We are unable to find anything regarding PreLogin Scripting to contrast the PostLoginScripting we are currently using, and the only other thing we are currently seeing as a possible option is running a custom authentication socket or password imap-login to a script. This seems like it would be a resource nightmare depending on the server load and are hoping for a more elegant option to be unveiled. Any other options or suggestions are welcome. We are also wondering, if we have to go with the custom authentication setup, if there are any examples out there to base our scripts off in setting it up. Thank you, Jeremy

1 0

Required SSL with exceptions
by List 09 Dec '14

09 Dec '14

I have a Dovecot cluster which is on separate machines from my webmail/caldav/cardav cluster, and I currently have the system setup with ssl = required. Unfortunately the caldav/cardav server I am running doesn't support STARTTLS so I was wondering if there is a way to still enforce ssl for every connection with the exception of a certain subnet, or if there is a better way to accomplish this without install a local install of Dovecot on each of my caldav/cardav servers.

3 4

Using dovecot with existing mbox hieararchy - possible?
by Chris Green 08 Dec '14

08 Dec '14

I currently use mutt to read my E-Mail on a machine which runs a postfix server to receive mail by SMTP. Mail is actually delivered to the final mbox mailboxes by a custom filtering script writtin in Python. Will dovecot happily serve mail from the existing hierarchy (obviously if I configure it right) so that I can connect using IMAP to my server machine to read mail? The mbox files are all under ~/Mail with several levels of directories in some trees. Does dovecot need any sort of notification from postfix (or my Python script) to indicate that new mail has been delivered or does it just re-scan the mbox files at intervals to see changes? -- Chris Green

1 0

sdbox and IMAP folders
by Jeff Larsen 08 Dec '14

08 Dec '14

We have just migrated from cyrus-imap to dovecot 2.2.9 on Ubuntu. By default, all our user's manually created folders appear at the same folder level as INBOX (i.e., they are next to INBOX, and not inside INBOX in a typical tree view of the folders). But on Dovecot, users are able to create new folders either parallel to INBOX or as subfolders within INBOX, which I think is going to lead to confusion for our users, especially when working from the limited UI of a smartphone client where folder hierarchy is not as easy to visualize. With cyrus, this behavior depended on the client setting for "IMAP server directory" as it is called in Thunderbird. If the setting was given the value "INBOX", then all folders were parallel to INBOX and you could not create any folder that would appear in the tree inside INBOX. With the setting empty, then all folders appeared as subfolders of INBOX. It was all or nothing. When the mail accounts were migrated to dovecot, the existing top-level user folders were created in dovecot at the same level as INBOX. We did nothing intentional to get this result. We just used cyrus2dovecot to export to maildir, then doveadm sync to convert to the final sdbox. With dovecot, when "IMAP server directory" is empty, we get the original folder tree with all folders parallel to inbox, but users are also able to create subfolders inside INBOX . We are using sdbox storage and the folder heirarchy as seen in the client tree (parallel folders and subfolders) is also reflected in the server's local file system. If we change the "IMAP server directory" setting on the client while using dovecot, then all the folders that were previously at the same level as INBOX become inaccessible, so that's not a viable option. So, my question is this: Can I replicate the cyrus behavior where INBOX subfolders are an all-or-nothing option? Or are we stuck with users (having questionable file management skills in the first place) getting lost between INBOX subfolders and top-level folders. Thanks, Jeff root:~# doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-40-generic x86_64 Ubuntu 14.04.1 LTS auth_mechanisms = plain login auth_verbose = yes listen = * mail_location = sdbox:%h:LAYOUT=fs:ALT=/var/alt-vmail/%n mail_plugins = " quota" 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-ldap.conf.ext driver = ldap } plugin { quota = dict:%n::file:%h/dovecot-quota quota_grace = 10%% quota_rule = *:storage=100M quota_rule2 = Trash:storage=+20M sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0666 } } service imap-login { inet_listener imap { address = localhost port = 143 } inet_listener imaps { port = 0 } } service managesieve-login { inet_listener sieve { address = localhost port = 4190 } } ssl = required ssl_cert = </etc/ssl/certs/mail.XXXX.com.crt ssl_key = </etc/ssl/private/mail.XXXX.com.key userdb { args = username_format=%n /etc/dovecot/qec-quota-override default_fields = uid=vmail gid=vmail home=/var/vmail/%n driver = passwd-file } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext default_fields = uid=vmail gid=vmail home=/var/vmail/%n driver = ldap } protocol lda { mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota" }

1 0

Missing hits when performing full-text searches
by Frerich Raabe 08 Dec '14

08 Dec '14

Hi, we're running Dovecot 2.1.7 together with Solr for efficient fulltext search. A couple of days ago we reinstalled our Solr server on a new machine. After adjusting our Dovecot setup to use the new server, it took a few days to notice that something seems fishy about our full-text search: expected hits wouldn't be shown among the search results. For instance, one of the folders (a shared, read-only folder which is basically a mailinglist archive) with about 210k messages has a plaintext mail with the text 'Amman'. However, logging into the IMAP server and issueing a . SEARCH TEXT Amman In the folder doesn't yield any hits. It seems that this happens for older mails only -- trying other keywords, we did notice hits in recent mails but not in older ones. Some caching related to the old Solr server causing issues? Debugging this further, I noticed that the above IMAP command shows this in the Solr log files: INFO: [] webapp=/solr path=/select params={fl=uid,score&sort=uid+asc&q=(hdr:"Amman"+OR+body:"Amman")&fq=%2Bbox:b68ece09e22fb9502d34010017227a26+%2Buser:""&rows=209392} hits=0 status=0 QTime=229 And indeed, something like $ curl 'http://indexer:8080/solr/select?fl=uid,score&sort=uid+asc&q=(hdr:"Amman"+OR+body:"Amman")&fq=%2Bbox:b68ece09e22fb9502d34010017227a26+%2Buser:""&rows=209392' Yields no results. However, I noticed that if I remove the 'fq=' part from the query then I get a bunch of hits. Alas, I don't know whether those are to be expected or not. Does anybody have an idea what might cause this, or what the meaning of that 'box' checksum is? -- Frerich Raabe - raabe(a)froglogic.com www.froglogic.com - Multi-Platform GUI Testing

1 0

userdb lookup not possible with only userdb prefetch
by Yves Goergen 08 Dec '14

08 Dec '14

Hello, I am setting up a new server and migrating my Dovecot 1.2.9 config to the new 2.2.9 version. There wasn't much to keep from the old version so I had to recreate the config from scratch. Now I think I'm done but I can't login to IMAP. The log says this: > dovecot: auth: Error: prefetch(box@****.de,2001:****:7765,<bzAOP5QJXwAgAQpgEAXJAZyOMB1qBXdl>): userdb lookup not possible with only userdb prefetch > dovecot: auth: Error: userdb(box@****.de,2001:****:7765,<bzAOP5QJXwAgAQpgEAXJAZyOMB1qBXdl>): user not found from userdb prefetch > dovecot: imap: Error: Authenticated user not found from userdb, auth lookup id=178651137 (client-pid=13711 client-id=1) > dovecot: imap-login: Internal login failure (pid=13711 id=1) (internal failure, 1 successful auths): user=<box(a)****.de>, method=PLAIN, rip=2001:****:7765, lip=2a01:****:2, mpid=13717, TLS, session=<bzAOP5QJXwAgAQpgEAXJAZyOMB1qBXdl> That doesn't help me a lot. Here's parts of my configuration, dumped with 'dovecot -n': > # 2.2.9: /etc/dovecot/dovecot.conf > # OS: Linux 3.13.0-40-generic x86_64 Ubuntu 14.04.1 LTS > auth_mechanisms = plain login > disable_plaintext_auth = no > 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 = > } > passdb { > args = /etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > plugin { > quota = maildir > } > protocols = imap pop3 > userdb { > driver = prefetch > } > protocol imap { > mail_max_userip_connections = 100 > mail_plugins = quota imap_quota > } What's the problem here? How can I resolve this issue? -- Yves Goergen http://unclassified.de http://dev.unclassified.de

4 4

Missing metadata on Dovecot 2.2.14, on Kolab 3.3, Centos 6.6
by Max Raafat 08 Dec '14

08 Dec '14

Hello everyone, We were trying to provision a system with Dovecot instead of another working cyrus kolab system. I am stuck with a problem with the metadata, especially when it comes to the Special Folders in Kolab 3.3, like Calenders, Tasks, etc, as well as any user created Folders. Emails work perfectly, and all the types are correct. But for example, If I try to change the type of Calenders, or create a new folder from inside roundcube and set it to type "Calenders", it stays at the default which is "mail". Therefore it causes problems, when sharing events, since they are displayed as "mail" type and not "event" type. We've tracked the problem down to the metadata not existing for special folders. A simple search only shows the default "mail" metadata, but nothing for shared folders, or special folders, etc. Here is the doveconf -n ------------------------------------------------------------------------------------------------------------- [root@m3 ~]# doveconf -n # 2.2.14: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-504.el6.x86_64 x86_64 CentOS release 6.6 (Final) imap_metadata = yes mail_attribute_dict = file:Maildir/dovecot-metadata mail_gid = 5000 mail_location = maildir:~/Maildir mail_plugins = " acl" mail_uid = 5000 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 mbox_write_locks = fcntl namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / type = shared } 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/master-users driver = passwd-file master = yes pass = yes } passdb { driver = shadow } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = vmail user = vmail } } service dict { unix_listener dict { group = vmail mode = 0666 user = vmail } } service lmtp { executable = lmtp unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { address = 127.0.0.1 ::1 port = 4190 } } service managesieve { process_limit = 1024 } ssl = required ssl_cert = </etc/ssl/m3.company.includingchain.crt ssl_key = </etc/ssl/m3.company.de.key userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { mail_plugins = " acl sieve" } protocol lda { mail_plugins = " acl sieve" } protocol imap { mail_plugins = " acl imap_acl" } ------------------------------------------------------------------------------------------------------------ Would appreciate any help or ideas as to what I can do to fix this. Thanks Max

1 0

MD5-CRYPT/CRAM-MD5 vs SHA512-CRYPT/PLAIN
by ML mail 06 Dec '14

06 Dec '14

Hello, I am wondering which variant is more secure for user authentication and password scheme. Basically I am looking at both variants: 1) MD5-CRYPT password scheme storage with CRAM-MD5 auth mechanism 2) SHA512-CRYPT password scheme storage with PLAIN auth mechanism In my opinion the option 2) should be safer although it is using PLAIN auth mechanism. Of course I would always use STARTTLS and not allow unencrypted connection. What is your opinion? Best, ML

6 7

Size of array hosts, vhosts_count and modulo operation
by rub zorghy 05 Dec '14

05 Dec '14

Hi, Timo Sirainen wrote (May 19, 2010 1:50:34 am) : "When a connection from a newly seen user arrives, it gets assigned to a mail server according to a function: host = vhosts[ md5(username) mod vhosts_count ]" This hash function is it still used as it is without modification ? My another question sounds pretty innocent but I have doubts about vhosts_count. Taking two directors with three backend Dovecot as an example, the number of (v)hosts assigned for each host is "100" (default value of the vhost_count variable). I gather that the value for vhosts_count (to perform the modulo operation) and the size or length of the array (vhosts[]) in terms of number of elements are equal to 300. Thx so much. gdrub

1 0

doveadm backup gmail using imapc
by List 05 Dec '14

05 Dec '14

I am trying to sync a gmail inbox with dovecot 2.2.10 using the following config: imapc_host = 64.233.171.108 imapc_user = %u imapc_master_user = master imapc_password = secret imapc_features = rfc822.size imapc_features = $imapc_features fetch-headers mail_prefetch_count = 20 # If the old IMAP server uses INBOX. namespace prefix, set: #imapc_list_prefix = INBOX # for SSL: imapc_port = 993 imapc_ssl = imaps #imapc_ssl_ca_dir = /etc/ssl imapc_ssl_verify = no And the doveadm command: doveadm -D -o imapc_user=test(a)domain.tld -o imapc_password=password backup -R -x '\All' -x '\Flagged' -x '\Important' -u test(a)domain.tld imapc: I am getting the error: dsync(test(a)domain.tld: Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. What I really want to do is just sync Gmail's inbox, drafts, sent, trash/archive, and spam folders to my new system. Is this possible using imapc?

1 0

Dovecot Director and Dovecot proxy
by rub zorghy 05 Dec '14

05 Dec '14

Hi, Dovecot Director is used to keep a temporary user -> Dovecot backend server mapping. So, Director decides which backend handles each user and the user is always redirected to the same server. All user data is stored in shared storage (NFS). The Dovecot presentation featured during this webinar <http://knowledgebase.open-xchange.com/fileadmin/user_upload/open-xchange/mi…> mentions (slide 7) a Dovecot proxy cluster (doing credentials and user info lookup) behind the LB device (F5 Big-IP) Why Dovecot Director server isn't used to perform this without Dovecot proxy ? Thus, the load balancer (F5 Big-IP) can distribute requests based on IMAP protocol to Dovecot Director cluster. Thx so much. gdrub

2 2

speed up doveadm search
by Vu Ngoc VU 05 Dec '14

05 Dec '14

Hello, I have recently migrated our mail accounts from old setup with courier-imapd to Dovecot 2. I thought that I can search quicky messages in mailboxes with doveadm because of indexes. Our users are asking (sometimes) to remove messages that they have sent wrongly. Some of them are coming from Exchange, and there is a feature in Outlook to recall (to delete) a message. So basically, they give me some infos (date, sender, subject) of message to remove. And I planned to do "doveadm search", then "doveadm fetch" and at last "doveadm expunge" on the found results. But it appears that the first run of doveadm is very slow. I don't know if it is because some indexes/caches are missing at this time. But when I run again same commands it is fast. Could you tell me if I speed up search on our maildir storage? I have no idea if I must manually (or with cron) run "doveadm index" on all our accounts because index/cache is only generated when users access their mailboxes. Or do I have to tune some settings like : mail_always_cache_fields, mail_cache_fields, mail_cache_min_mail_count, mail_never_cache_fields Thanks

1 0

does lda_save_to_detail_mailbox exist?
by A. Schulze 04 Dec '14

04 Dec '14

Hello, there is a nice feature in lmtp to save messages to user+foo@domain in INBOX/foo Looks like that doesn't work as good if lda is used. I have dovecot-2.2.13 mail_location = maildir:%h/ lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes *lmtp*_save_to_detail_mailbox = yes messages to user+foo generate an error and are saved to INBOX not matter if INBOX/foo exist or not: Dec 4 09:40:59 mail dovecot: lda(user(a)example.org): Debug: Effective uid=10020, gid=10020, home=/var/mail/user(a)example.org/ Dec 4 09:40:59 mail dovecot: lda(user(a)example.org): Debug: Destination address: user(a)example.org (source: user@hostname) Dec 4 09:40:59 mail dovecot: lda(user(a)example.org): msgid=<3jtWlm3FCHz52KG@localhost>: save failed to open mailbox foo: Mailbox can't be created Dec 4 09:40:59 mail dovecot: lda(user(a)example.org): msgid=<3jtWlm3FCHz52KG@localhost>: saved mail to INBOX # doveadm user -u user(a)example.org userdb: user(a)example.org home : /var/mail/user(a)example.org/ quota_rule: *:bytes=1000000 master_user: user(a)example.org # doveadm mailbox list -u user(a)example.org INBOX INBOX/bar Possible, that *lda*_save_to_detail_mailbox is simply not implemented? Thanks, Andreas

2 2

"maildir_empty_new = yes" not working
by Nikola Derikonjic 04 Dec '14

04 Dec '14

I need for my dovecot-uidlist to be updated with next id when new email arrives (moved from new/ to cur/). This only happens now when I check for new email with my client. Setting maildir_empty_new = yes is not working. Do I have to uncomment something else as well maybe? I want to do some proemial pipe lets say for 10 emails. All of them will have same UID since dovecot-uidlist is not updated. I am suing 2.2.13 dovecot on Gentoo 64bit. This is my dovecot -n: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.5-gentoo x86_64 Gentoo Base System release 2.2 auth_mechanisms = plain login digest-md5 first_valid_gid = 500 last_valid_gid = 2000 last_valid_uid = 2000 login_greeting = Santa server is ready. mail_gid = vmail mail_location = /var/vmail/%d/%n/:INDEX=/var/vmail/%d/%n/indexes mail_uid = vmail maildir_empty_new = yes 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 duplicate 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 = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } ssl_ca = </etc/ssl/dovecot/server.in.crt ssl_cert = </etc/ssl/dovecot/server.csr.rapid ssl_key = </etc/ssl/dovecot/server.key.rapid ssl_key_password = notshown userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } -- Nikola Derikonjic Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

2 2