- dovecot - dovecot.org

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