- dovecot - dovecot.org

[Dovecot] Problem copying e-mails to IMAP - Dovecot 2.1.2
by Odhiambo Washington 16 Mar '12

16 Mar '12

I have a situation where I need to migrate e-mails from Outlook 2011 (Mac) to Apple Mail. Having looked at all options, I have resorted to the, perhaps, most difficult way: Create folders on the IMAP server, copy e-mails into them from Outlook, connect Apple Mail and do the reverse. However, I have hit a wall. I am running Dovecot 2.1.2 on FreeBSD, with mdbox storage. In my first attempt, I have 1792 messages in the "Sent Items" folder for Outlook. I have tried (3 times) to copy the messages to the IMAP/Sent Items folder, but the process dies at some point. When that happens, Outlook pops a screen saying "IMAP session state is inconsistent, please relogin". Dovecot says: Mar 16 13:30:26 jaribu dovecot: master: Warning: Killed with signal 15 (by pid=72242 uid=0 code=kill) Mar 16 13:30:29 master: Info: Dovecot v2.1.2 starting up Mar 16 13:31:15 auth-worker(72594): Info: mysql(localhost): Connected to database exim4u Mar 16 13:31:15 imap-login: Info: Login: user=<wash(a)kictanet.or.ke>, method=PLAIN, rip=192.168.40.194, lip=192.168.40.252, mpid=72595 Mar 16 13:31:15 imap: Debug: Loading modules from directory: /opt/dovecot2.1/lib/dovecot Mar 16 13:31:15 imap: Debug: Module loaded: /opt/dovecot2.1/lib/dovecot/lib10_quota_plugin.so Mar 16 13:31:15 imap(wash(a)kictanet.or.ke): Debug: Effective uid=26, gid=26, home=/var/spool/virtual/kictanet.or.ke/wash Mar 16 13:31:15 imap(wash(a)kictanet.or.ke): Debug: quota: No quota setting - plugin disabled Mar 16 13:31:15 imap(wash(a)kictanet.or.ke): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mdbox:~/mdbox Mar 16 13:31:15 imap(wash(a)kictanet.or.ke): Debug: fs: root=/var/spool/virtual/kictanet.or.ke/wash/mdbox, index=, control=, inbox=, alt= Mar 16 13:31:15 imap(wash(a)kictanet.or.ke): Debug: Namespace : Using permissions from /var/spool/virtual/kictanet.or.ke/wash/mdbox: mode=0700 gid= -1 Mar 16 13:31:30 imap-login: Info: Login: user=<wash(a)kictanet.or.ke>, method=PLAIN, rip=192.168.40.194, lip=192.168.40.252, mpid=72646 Mar 16 13:31:30 imap: Debug: Loading modules from directory: /opt/dovecot2.1/lib/dovecot Mar 16 13:31:30 imap: Debug: Module loaded: /opt/dovecot2.1/lib/dovecot/lib10_quota_plugin.so Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: Effective uid=26, gid=26, home=/var/spool/virtual/kictanet.or.ke/wash Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: quota: No quota setting - plugin disabled Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mdbox:~/mdbox Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: fs: root=/var/spool/virtual/kictanet.or.ke/wash/mdbox, index=, control=, inbox=, alt= Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: Namespace : Using permissions from /var/spool/virtual/kictanet.or.ke/wash/mdbox: mode=0700 gid= -1 Mar 16 13:31:30 imap: Debug: Loading modules from directory: /opt/dovecot2.1/lib/dovecot Mar 16 13:31:30 imap: Debug: Module loaded: /opt/dovecot2.1/lib/dovecot/lib10_quota_plugin.so Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: Effective uid=26, gid=26, home=/var/spool/virtual/kictanet.or.ke/wash Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: quota: No quota setting - plugin disabled Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mdbox:~/mdbox Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: fs: root=/var/spool/virtual/kictanet.or.ke/wash/mdbox, index=, control=, inbox=, alt= Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: Namespace : Using permissions from /var/spool/virtual/kictanet.or.ke/wash/mdbox: mode=0700 gid=-1 Mar 16 13:31:30 imap-login: Info: Login: user=<wash(a)kictanet.or.ke>, method=PLAIN, rip=192.168.40.194, lip=192.168.40.252, mpid=72647 Mar 16 13:33:23 jaribu dovecot: imap(wash(a)kictanet.or.ke): Error: Corrupted dbox file /var/spool/virtual/kictanet.or.ke/wash/mdbox/storage/m.4 (around offset=894): msg header has bad magic value Mar 16 13:33:23 jaribu dovecot: imap(wash(a)kictanet.or.ke): Warning: mdbox /var/spool/virtual/kictanet.or.ke/wash/mdbox/storage: rebuilding indexes Mar 16 13:33:23 jaribu dovecot: imap(wash(a)kictanet.or.ke): Error: /var/spool/virtual/kictanet.or.ke/wash/mdbox/mailboxes/SentItems/dbox-Mails/dovecot.index reset, view is now inconsistent Mar 16 13:33:23 imap(wash(a)kictanet.or.ke): Info: Disconnected: IMAP session state is inconsistent, please relogin. bytes=13816863/907529 My doveconf output is here -> http://pastebin.com/6yNP5ygt -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email.

4 11

[Dovecot] v2.1.3 released
by Timo Sirainen 16 Mar '12

16 Mar '12

http://dovecot.org/releases/2.1/dovecot-2.1.3.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.3.tar.gz.sig Do not use v2.1.2 with multi-dbox format, it's broken. I didn't notice that a small optimization I did a few days ago broke mdbox in some situations (when mdbox first created a new m.X file, and later in same session saved another message to it). It's quite a high priority for me to run some automated testing before releasing new versions, for example a small imaptest run with mdbox would have caught this. Perhaps the next release will already have the automated testing.

1 0

[Dovecot] Another hint from the clue box 8-) imapc/imap proxy user mailbox server location
by Terry Carmen 16 Mar '12

16 Mar '12

I'm running imapproxy as shown at http://wiki2.dovecot.org/HowTo/ImapcProxy. In fact, that's my config in the wiki. 8-) It's been working, but has performance issues when the Exchange server that's hard-coded as imapc_host=xxx.xxx.xxx.xxx doesn't happen to be the user's home exchange server. I'd like to point dovecot at the correct Exchange server based on an LDAP query, and in fact, have an LDAP search that works: DC=example,DC=com (&(objectCategory=person)(objectClass=user)(!(userAccountcontrol:1.2.840.113556.1.4.803:=2))(sAMAccountName=username)) With the exchange server being returned in the msExchHomeServerName property as: /O=example/OU=INT/cn=Configuration/cn=Servers/cn=exchangeservername I believe this should somehow end up in the userdb section, which currently contains "driver = prefetch", but can't seem to figure out specifically what should be there. The only important part is "cn=exchangeservername", which is the machine name and would need to be prepended to example.com to get the fqdn. Can anybody toss me a clue? Once I get it working, I'll update the wiki. Thanks! Terry

4 14

[Dovecot] ldapi support
by Nikolaos Milas 16 Mar '12

16 Mar '12

Hi, Quick question: Does Dovecot support ldapi (i.e. via Unix Sockets) connections for LDAP lookups (user, password, auth etc.) or only ldap/ldaps (over TCP)? If yes, how do we specify ldapi://localhost in Dovecot configuration files? Thanks, Nick

2 1

[Dovecot] imaptest: performance testing
by Nick Urbanik 16 Mar '12

16 Mar '12

Dear Folks, Using head of imaptest with dovecot 2.1, I am attempting to put a heavy load on the server, with insufficient success. I made 15000 user accounts, put them in to a file, one per line. Then I ran imaptest with ./imaptest userfile=../../imap-test-userlist-15001.txt clients=15001 pass=SECRETPASSWORD But CPU load is only reaching 20. I put an mbox containing 67 messages into ~/mail/dovecot-crlf So what is the best way to put a really heavy load on an imap server? The documentation describes testing correctness of the server without really emphasising performance. I would like to do something like dnsperf, which adds a linearly increasing load until the server is unable to cope. This machine has 24G RAM and 8 cores. I'll be grateful for any constructive suggestions. -- Nick Urbanik http://nicku.org nicku(a)nicku.org GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24

3 2

[Dovecot] Upgrading from 2.0.x to 2.1.x
by Nikolaos Milas 16 Mar '12

16 Mar '12

Hi, A quick question: Are there any incompatibilities in config settings among versions 2.0.x and 2.1.x (and subsequently v2.2.x)? That is, upgrading Dovecot 2.0.x to 2.1.x software, will also require changes of any config settings (as upgrading from v1.x to 2.0.x did)? Thanks, Nick

2 2

[Dovecot] Lack of external documentation?
by Steve Campbell 16 Mar '12

16 Mar '12

Firstly, this isn't meant to be critical, and I realize the subject line probably suggest criticism, so... I was sort of forced into using dovecot as my imap/pop server due to upgrading 3 versions of OS on my mail servers. So far, that's not bad. What surprises me is that one of the first things I usually do whenever I start using different software is to purchase a book that seems to suit me. Searching all of the common places like amazon, ebay, etc for manuals turned up little to nothing on dovecot. I'm wondering why and is this so new that people just haven't written books about it yet? The one thing I'm a little critical of, though, is that trying to make heads or tails of dovecot by following the online documentation is a little problematic. I'm constantly jumping to another page and then back to the original page, and for the most part, I just don't know enough about it all yet to know what I'm looking for. Does anyone know of any manuals/books that have been written that might introduce me to most of the stuff in dovecot? So far, the list has been great, but once the "dsync" threads started popping up, I find there's even more I don't know about. Thanks for all the help I've received so far and I think I'm really going to like dovecot. Once I get the hang of it, I'll probably reduce the amount of noise on the list by half. steve campbell

8 8

[Dovecot] v2.1.2 released
by Timo Sirainen 16 Mar '12

16 Mar '12

http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz.sig There are a ton of proxying related improvements in this release. You should now be able to do pretty much anything you want with Dovecot proxy/director. This release also includes the initial version of dsync-based replication. I'm already successfully using it for @dovecot.fi mails, but it still has some problems. See http://dovecot.org/list/dovecot/2012-March/064243.html for some details how to configure it. + Initial implementation of dsync-based replication. For now this should be used only on non-critical systems. + Proxying: POP3 now supports sending remote IP+port from proxy to backend server via Dovecot-specific XCLIENT extension. + Proxying: proxy_maybe=yes with host=<hostname> (instead of IP) works now properly. + Proxying: Added auth_proxy_self setting + Proxying: Added proxy_always extra field (see wiki docs) + Added director_username_hash setting to specify what part of the username is hashed. This can be used to implement per-domain backends (which allows safely accessing shared mailboxes within domain). + Added a "session ID" string for imap/pop3 connections, available in %{session} variable. The session ID passes through Dovecot IMAP/POP3 proxying to backend server. The same session ID is can be reused after a long time (currently a bit under 9 years). + passdb checkpassword: Support "credentials lookups" (for non-plaintext auth and for lmtp_proxy lookups) + fts: Added fts_index_timeout setting to abort search if indexing hasn't finished by then (default is to wait forever). - doveadm sync: If mailbox was expunged empty, messages may have become back instead of also being expunged in the other side. - director: If user logged into two directors while near user expiration, the directors might have redirected the user to two different backends. - imap_id_* settings were ignored before login. - Several fixes to mailbox_list_index=yes - Previous v2.1.x didn't log all messages at shutdown. - mbox: Fixed accessing Dovecot v1.x mbox index files without errors.

4 4

[Dovecot] problems with SSH-based clustering dovecot 2.1.1
by Michescu Andrei 16 Mar '12

16 Mar '12

Hello, I'm using dovecot 2.1.1 with vpopmail 5.4.30 with multiples domains and I have problems setting up synchronization in between multiple computers. All act like master (my clients can connect to any of the them and read their emails either via POP3 either via IMAP, inbound email gets on any of the machines). Each machine is on a different continent, there is no shared drive in between and the synchronization is supposed to be asynchronous via cron scripts. To simplify the case, let's consider 2 machines (mx1.a and mx2.a) with 3 virtual domains (a and b and c). On both machine domain a is the default domain (needs only username to connect to imap). Initially I synchronize mx1.a with mx2.a using rsync. I check that I can login using dovecot. I tried any of the following commands to synchronize the 2 machines: mx1.a$ doveadm -Dv sync -u user1@a -f ssh mx2.a doveadm dsync-server -u user1@a mx1.a$ doveadm -Dv sync -u user1@a ssh mx2.a doveadm -u user1@a mx1.a$ doveadm -Dv sync -u user1@a user1@a The only thing that happens is that the on each machine the folders get doubled with some random extension (eg. Inbox becomes Inbox_3e3ff3g3gb3bb3b22). Also, another bug, if there is a domain setup as default (auth_default_realm) dsync simply ignores the specified -u <user> and attempts to sync the first email in the default domain. Please advise. # 2.1.1: /etc/dovecot/dovecot/dovecot.conf # OS: Linux 2.6.38-b i686 Slackware 13.0.0.0.0 auth_debug = yes auth_debug_passwords = yes auth_default_realm = a first_valid_gid = 89 first_valid_uid = 89 last_valid_gid = 89 last_valid_uid = 89 listen = * log_path = /dev/stderr login_greeting = A login_trusted_networks = 192.168.20.64/26 mail_debug = yes mail_gid = vchkpw mail_location = maildir:~/Maildir mail_privileged_group = vchkpw mail_uid = vpopmail passdb { driver = vpopmail } protocols = imap pop3 service auth-worker { unix_listener auth-worker { user = vpopmail } user = vpopmail } service auth { user = vpopmail } service imap-login { user = vpopmail } service pop3-login { user = vpopmail } ssl = no userdb { driver = vpopmail }

5 24

[Dovecot] Compiler warnings in dovecot-2.1.2 and pigeonhole 0.3.0
by Tom Talpey 16 Mar '12

16 Mar '12

I'm seeing a few warnings emitted when building for x86. They're pretty obvious, but if you want the configure options etc, I can provide those. In Dovecot 2.1.2 (I also see some of these in 2.1.1): 1) src/lib-index/mail-cache-fields.c (comparison between two last_used fields) mail-cache-fields.c: In function 'mail_cache_header_fields_read': mail-cache-fields.c:406: warning: comparison between signed and unsigned 2) src/director/user-directory.c (comparison with ioloop_time) user-directory.c: In function 'user_directory_user_is_recently_updated': user-directory.c:147: warning: comparison between signed and unsigned 3) src/replication/replicator/replicator-brain.c (comparison with ioloop_time) replicator-brain.c: In function 'doveadm_replicate': replicator-brain.c:113: warning: comparison between signed and unsigned 4) src/replication/replicator/replicator-queue.c (comparison with ioloop_time) replicator-queue.c: In function 'replicator_queue_pop': replicator-queue.c:201: warning: comparison between signed and unsigned In Pigeonhole 0.3.0: 5) src/managesieve-login/client-authenticate.c (passing size_t * not uoff_t *) client-authenticate.c: In function 'managesieve_client_auth_read_response': client-authenticate.c:214: warning: passing argument 3 of 'i_stream_get_size' from incompatible pointer type

3 3