- dovecot - dovecot.org

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