- dovecot - dovecot.org

[Dovecot] mbox, hierarchical folders/folders and IMAP
by Alexander Chekalin 30 Dec '11

30 Dec '11

Hello, I'm now dealing with funny problem. I try to use Dovecot (2.1.rc1, actually) and mbox format to store old mailing, to keep logic of "one folder = one file". If I'd choose Maildir, I'd be able to create hierarchical folders (like "OldMail -> Maillists -> Dovecot"), and in fact on disk such a folders would be stored as real folders with dots in their names. In PHP it is easy to create with "imap_createmailbox()" function, I'd simple fire it 3 times (for "OldMail", for "OldMail.Maillists" and for "OldMail.Maillists.Dovecot"). But when I do the same with mbox, in fact it creates separate files (indeed, named "OldMail", "OldMail.Maillists" and "OldMail.Maillists.Dovecot") instead of creating filesystem folders ("OldMail/Maillists/Dovecot"). PHP is not guilty, Thunderbird won't create such folders as well. I can only create folders myself (say, with mkdir in the shell), chown it, and the it perfectly works in IMAP. Now I just wanted to know, are there any way to create IMAP-folders and subfolders using standard IMAP functionality? Thank you, Alexander

4 8

[Dovecot] Using Amazon S3 storage for Maildir ?
by Forrest Aldrich 30 Dec '11

30 Dec '11

I wonder if anyone has tried using an IMAP server with Amazon S3 as a backend. There would be many factors to consider (speed, etc). However, moreso, I don't know that Maildir(++) would support multiple folders that might be linked into the cloud. For example, higher-I/O local incoming mail is on disk, some folders archived on S3. Could be easily done by simply creating another account and storing its Maildir in S3 -- Curious....

3 2

[Dovecot] How to serve a subset of IMAP folders for hand held devices.
by David Pottage 29 Dec '11

29 Dec '11

Hello I am currently running dovecot 1.2.15 on my home server. I have over 200 folders in personal email account, and I have found that my smart-phone does not work well trying to display that many folders. I solved the problem by creating a second instance of dovecot running on a non standard port, and configured it to serve only a subset my email folders, so that way the email client on my smartphone works well and I can read the emails I am interested in on the move. The process of configuring two instances of dovecot on the same machine serving different views of the same mailbox was faily complex, so I think it would be worth documenting the process in an FAQ or suchlike for other users. I thought a good place to write up my method would be in the HowTo section of the Dovecot Wiki. Is that a good idea? Can I request an account to edit the Wiki, or should I send a draft text to an editor? Are there any Dovecot experts here who can review my methods and suggest improvements? -- David Pottage

8 10

[Dovecot] /usr/lib/dovecot/imap ignores log settings?
by Asheesh Laroia 29 Dec '11

29 Dec '11

Hi Dovecot peeps, I'm enjoying running /usr/lib/dovecot/imap directly as a PREAUTH IMAP pipe. I find that it outputs log messages whose severity is INFO to stdout. I'm running it as follows: /usr/lib/dovecot/imap -c /tmp/dovecot.conf and I see the following messages output to stdout: * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS] Logged in as paulproteus imap(paulproteus): Info: Connection closed bytes=0/305 Naturally, the first line is great. My /tmp/dovecot.conf is: <cut here> # single-dbox mail_location = sdbox:~/Maildir/dbox log_path = syslog info_log_path = /dev/null </cut> I'm also attaching strace output, created by running this command: echo | strace /usr/lib/dovecot/imap -c /tmp/dovecot.conf > /tmp/straced 2>&1 (The point of the "echo | " is to provide a newline and then EOF to /usr/lib/dovecot/imap.) You can see in the strace output that /usr/lib/dovecot/imap outputs the "Connection closed" message to file descriptor 2. I'd like that message to actually not be printed, which is why I set log_path to syslog. -- Asheesh.

2 2

[Dovecot] Dsync Error Can't Delete Mailbox
by Asai 29 Dec '11

29 Dec '11

Greetings, I'm getting this error in the dsync logs: Warning: Destination mailbox INBOX has been modified, need to recreate it before we can continue syncing dsync(foo(a)bar.org): Error: Can't delete mailbox INBOX: INBOX can't be deleted. In this situation, what should I do to remedy the problem? Just delete the backup and rebuild? -- --asai

2 2

[Dovecot] Received date no longer email date?
by Brian L. Matthews 29 Dec '11

29 Dec '11

I just upgrade from dovecot 1.2 to dovecot 2.0.16. I use dovecot as a local IMAP server to archive email from my corporate email account (on Exchange). I don't have any automated archiving, I just periodically move messages from my Exchange inbox to the IMAP inbox. I'm on Mac OS X 10.6.8 using Entourage as my mail client. In the previous version of dovecot, the Received date of the email was preserved when I moved a message, but it's not in 2.0.16, it's set to the date and time I move the message. If I open a message, the date displayed is the date on the message as expected. I converted my config from 1.2 with $ doveconf -n -c dovecot.conf > dovecot-2.conf It spit out various warnings but, once I'd created a dovenull user, seemed to work fine. Here's my configuration info: $ dovecot --version 2.0.16 $ dovecot -n # 2.0.16: /usr/local/etc/dovecot/dovecot.conf # OS: Darwin 10.8.0 i386 disable_plaintext_auth = no listen = 127.0.0.1 log_path = /var/log/dovecot.log mail_location = maildir:~/Maildir passdb { args = login driver = pam } service auth { user = root } service imap-login { process_limit = 16 } service imap { process_limit = 64 } ssl = no userdb { driver = passwd } I'd like to get it back to preserving the Received date, any help you can provide will be appreciated. Brian

2 1

[Dovecot] proxying, SSL, and client certificate
by Mike Abbott 29 Dec '11

29 Dec '11

How do I configure dovecot-2.0.x to present a client SSL certificate when proxying? If dovecot on server1.example.com has: passdb { driver = static args = proxy=y host=server2.example.com nopassword=y ssl=yes } and dovecot on server2.example.com has: ssl_verify_client_cert = yes auth_ssl_require_client_cert = yes then when a client connects to server1 and authenticates, a connection is established to server2 but the SSL handshake fails because server1 doesn't present a client certificate. I don't see where ssl_client_ctx is tied to a client certificate in ssl-proxy-openssl.c. Thanks.

2 1

[Dovecot] Lucene vs Solr with 2.1 single server
by Daniel L. Miller 29 Dec '11

29 Dec '11

For a single server, is the Lucene backend now "better" than running a Solr server? -- Daniel

2 1

[Dovecot] Dovecot imap proxy to nginx, incompatible
by David Jonas 29 Dec '11

29 Dec '11

It appears that using dovecot to proxy to nginx imap proxy doesn't work. >From tcpdump and browsing the source it appears dovecot sends, C CAPABILITY\r\nL LOGIN <user> <pass>\r\n and nginx only responds to the CAPABILITY command. Is this a problem with dovecot sending the two commands without waiting for the first to complete or is it nginx's trouble with not handling it correctly? A quick test with a perl script confirms: #!/usr/bin/perl -w $|++; use IO::Socket; use strict; my ($host, $user, $pass) = @ARGV; my $s = new IO::Socket::INET(Proto => 'tcp', PeerAddr => $host, PeerPort => 143); die "Could not create socket $!\n" unless $s; while(<$s>) { print $_; last if /OK/; } print $s "C CAPABILITY\r\nL LOGIN $user $pass\r\n"; while(<$s>) { print $_; last if /OK/; } print $s "Q logout\r\n"; while(<$s>) { print $_; last if /OK/; } close($s); ## Output: * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1 QUOTA AUTH=PLAIN C OK completed * BYE Q OK completed

2 1

[Dovecot] UIDL format
by sottilette＠rfx.it 29 Dec '11

29 Dec '11

How can be sure of the current POP3 UIDL? Below my current config (to be migrated to 2.0.x ASAP). Thanks, P. # dovecot -n # 1.0.2: /etc/dovecot.conf log_path: /var/log/mail/dovecot.log info_log_path: /var/log/mail/dovecot.info.log protocols: pop3 pop3s imap imaps listen: * login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login first_valid_uid: 100 mail_location: mbox:~/:INBOX=/var/mail/%u mail_full_filesystem_access: yes mbox_read_locks: dotlock fcntl mbox_write_locks: dotlock fcntl mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: passdb: driver: pam userdb: driver: passwd

2 1