April 2012 - dovecot - dovecot.org

[Dovecot] Howto reindex with solr?
by Jean-Daniel Beaubien 17 Apr '12

17 Apr '12

Hi, I am currently testing a 2.1 dovecot setup with fts-solr. Search speed is simply amazing. I decided to try to delete and rebuild the solr indexes, but i can't seem to rebuild them thru dovecot. At first, when telnetting to the imap server, the search initially built the index, and then subsequent searches are blazingly fast. 1- I deleted all the solr indexes with the following query: <delete><query>*:*</query></delete> 2- Flag the mailbox to be re-indexed: doveadm force-resync INBOX At this point, it doesn't work. When I telnet into the imap server, the searches always come back empty 3- I also tried a few other commands: doveadm fts rescan, doveadm index INBOX. Still no search results. Nothing seems to be appearing in the logs when I issue all the doveadm commands. What did I miss? Thanks, -JD

1 0

[Dovecot] problems upgrade 2.0 - 2.1 virtual inbox broken / special use namespace
by Robert Schetterer 16 Apr '12

16 Apr '12

Hi Timo the virtual setup got broke after update to 2.1 ( its still working under 2.0 ) on other loadbalanced server namespace default { separator = / prefix = "" list = yes subscriptions = yes hidden = no } namespace virtual { prefix = "virtual/" separator = / location = virtual:/etc/dovecot/virtual:LAYOUT=maildir++:INDEX=~/virtual hidden = yes list = no subscriptions= no } namespace real { prefix = "RealMails/" separator = / list = no hidden = yes } after upgrade i have Error: Couldn't open INBOX: Virtual mailbox open failed because of mailbox <hidden>/RealMails/: Invalid mailbox name --------------------- also i wanted to include namespace inbox { #mailbox name { # auto=create will automatically create this mailbox. # auto=subscribe will both create and subscribe to the mailbox. #auto = no # Space separated list of IMAP SPECIAL-USE attributes as specified by # RFC 6154: \All \Archive \Drafts \Flagged \Junk \Sent \Trash #special_use = #} # These mailboxes are widely used and could perhaps be created automatically: mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Trash { special_use = \Trash } # For \Sent mailboxes there are two widely used names. We'll mark both of # them as \Sent. User typically deletes one of them if duplicates are created. mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } # If you have a virtual "All messages" mailbox: mailbox virtual/All { special_use = \All } # If you have a virtual "Flagged" mailbox: mailbox virtual/Flagged { special_use = \Flagged } } but i found no working namespace combination with virtual -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 2

[Dovecot] POP3 Dovecot Auth CPU usage 75%+
by Root Kev 16 Apr '12

16 Apr '12

Hello all, I hope someone can help me, I have been testing out Dovecot to switch from popa3d which I use at the moment. When I get several users connecting and disconnection multiple times, the Dovecot process with command Auth uses 50-90% of the CPU for the period which they are connecting. I am wondering if there is something that I may have misconfigured, or if there is something that I can change so that this spike doesn't occur. If anyone could shed some light on the issue, I would appreciate it, Kevin /var/mail# dovecot -n # 2.1.4: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-33-generic-pae i686 Ubuntu 10.04.4 LTS ext4 auth_cache_size = 10 M auth_verbose = yes disable_plaintext_auth = no instance_name = Mail Popper 1 listen = 172.20.20.222 login_greeting = Mail Popper 1 Ready mail_location = mbox:/var/empty:INBOX=/var/mail/%u:INDEX=MEMORY mail_privileged_group = mail 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 { driver = shadow } protocols = pop3 service pop3-login { service_count = 0 } ssl = no userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xu%08Xv }

2 5

[Dovecot] Better to use a single large storage server or multiple smaller for mdbox?
by Emmanuel Noobadmin 15 Apr '12

15 Apr '12

I'm trying to improve the setup of our Dovecot/Exim mail servers to handle the increasingly huge accounts (everybody thinks it's like infinitely growing storage like gmail and stores everything forever in their email accounts) by changing from Maildir to mdbox, and to take advantage of offloading older emails to alternative networked storage nodes. The question now is whether having a single large server or will a number of 1U servers with the same total capacity be better? Will be using RAID 1 pairs, likely XFS based on reading Hoeppner's recommendation on this and the mdadm list. Currently, I'm leaning towards multiple small servers because I think it should be better in terms of performance. At the very least even if one node gets jammed up, the rest should still be able serve up the emails for other accounts that is unless Dovecot will get locked up by that jammed transaction. Also, I could possibly arrange them in a sort of network raid 1 to gain redundancy over single machine failure. Would I be correct in these or do actual experiences say otherwise?

11 41

[Dovecot] Sieve pipe extension - can it retur something?
by kjonca＠o2.pl 15 Apr '12

15 Apr '12

I have a question about sieve pipe: can it return something to further processing? For example in procmail I can do: --8<---------------cut here---------------start------------->8--- :0 VIRUS=`$CLAMSCAN --mbox --disable-summary --stdout -` --8<---------------cut here---------------end--------------->8--- and then test VIRUS variable. Maybe I missing something, when read http://hg.rename-it.nl/pigeonhole-0.2-sieve-pipe/raw-file/tip/doc/rfc/spec-… KJ -- http://sporothrix.wordpress.com/2011/01/16/usa-sie-krztusza-kto-nastepny/ Gloffing is a state of mine.

2 1

[Dovecot] Dovecot 2.1.4 and client certificates
by Бранко Мајић 14 Apr '12

14 Apr '12

Version: 2.1.4 OS: Gentoo stable/amd64 OpenSSL version: 1.0.0h I'm having a slight problem with the client certificates in Dovecot 2.1.4. I've set-up the client certificate verification/authentication, and it seems that Dovecot is choking on the trustchain with CRL's that I'm providing to it (attached to this mail). When I enable the client authentication using certificates, and pick the certificate from my client (I've also tried it out with gnutls-cli as well), I get the following errors in Dovecot's log: imap-login: Info: Invalid certificate: Different CRL scope: /CN=Example Root CA/O=Example Inc./C=RS As per the wiki2 configuration page, I've set up the truststore in the following order (everything PEM-encoded): Example Person CA Certificate Example Person CA CRL Example Root CA Certificate Example Root CA CRL Person CA is the one issuing the end-entity certificates, of course. I'm also attaching the certificate I've used for testing. On additional note, the imap-login process also got stuck writing out the error message to the log file, refusing to die when receiving the SIGTERM (had to send SIGKILL). A similar set-up used to work under Dovecot in Debian Squeeze (version 1.2.15). The same file copied over to Dovecot 2.1.4's configuration won't work. I've compiled Dovecot by hand, and I'm not running it in any kind of chroot (this is a developer set-up so I could add support for rfc822Name username extraction I mentioned a week or so ago without messing around as root). Best regards -- Branko Majic Jabber: branko(a)majic.rs Please use only Free formats when sending attachments to me. Бранко Мајић Џабер: branko(a)majic.rs Молим вас да додатке шаљете искључиво у слободним форматима.

1 0

[Dovecot] Compressed mbox - patch
by kjonca＠o2.pl 14 Apr '12

14 Apr '12

Some time ago I complained about very slow access to compressed mboxes. Unfortunately it looks like that it is very little interest in it, so I have to investigate some things by myself. Firstly: some rationale. Why do I prefer use mbox/maildir over mdbox. Short answer "bus factor" for support mdbox (not only dovecot) Longer answer: if something goes wrong withm maildir/mbox i can use other tools (mutt, or formail or even text editor) and with mdbox ... I am not ISP, I use dovecot as a "gateway" to my (rather huge) mail archive. Most of these mails are rather valuable for me, so I prefer use something "well-known-and-tested". (I can't do like most ISP's do: write in "Terms of Service" that mail can be lost or damaged and we give no warranty :) ) So then: Below my patch. It contains 2 changes: 1. when buffer is compressed, we try to save last marked offset. 2. Increase temporary buffer for decompression. without these changes 1.5 GB of bzip compressed mbox with ~20K messages can't be open in 1.5 day After applying 1. change it can be open in ~1.5 h With both changes it was a few minutes. Maybe it is a good idea to add config parameter to specify size of decompress buffer? Patch is against v2.0.18 -- Gdyby ktoś miał zbędny Toshiba G450 - to chętnie przejmę ;) < asuffield> a workstation is anything you can stick on somebodies desk and con them into using -- in #debian-devel

1 0

Re: [Dovecot] Dovecot 2.1 with custom OpenSSL fails to build
by Andreas M. Kirchwitz 14 Apr '12

14 Apr '12

Timo Sirainen <tss(a)iki.fi> wrote: >> $ patch -p1 -s < ../dovecot-20120303-e540404debb7.patch >> $ env SSL_CFLAGS="-I/usr/local/ssl/include" SSL_LIBS="-L/usr/local/ssl/lib -Wl,-R/usr/local/ssl/lib -lcrypto -lssl" ./configure --prefix=/usr/local/Dovecot-20120303 --with-ssl=openssl --with-ssldir=/usr/local/Dovecot-20120303/etc/dovecot/certs && make && make install > > You would have needed to run autogen.sh again. It works with me now that > I tried in a test server with OpenSSL in non-standard dir. Sorry, I didn't know that with "autogen.sh". Just grabbed Dovecot 2.1.2 (which is all properly set up - so I couldn't do anything wrong ;-) and compiled it. Compilation works. Great! The binaries find all their libraries. But two libraries are not quite okay. They don't find their SSL libs: libdovecot-lda.so libdovecot-storage.so Since libdovecot-lda.so doesn't contain the words libssl or libcrypto, I guess that ldd just complains because it uses libdovecot-storage.so. Thus, libdovecot-storage.so is the (only) one left with an incomplete library search path. Luckily, all binaries use some additional libraries which come with a proper library path. So the whole things works, but it's more like some kind of magic. It would be great if libdovecot-storage.so could be fixed as well to make things finally perfect. Thanks for all your effort. (I know this isn't top priority as most people use precompiled stuff and never run into such kind of things.) Greetings, Andreas

2 2

[Dovecot] [OT] Outlook identities
by Michael Orlitzky 14 Apr '12

14 Apr '12

Nothing to do with Dovecot, but I figured this is the best place to ask. Do any of the newer versions of Outlook have proper identities support like Thunderbird, mutt, Roundcube, i.e. every other mail client on Earth? We have customers who set up ten different mailboxes for one person because otherwise Outlook won't Do the Right Thing. Is there some way to make it behave like the others? * When sending new mail, you can choose which address to use. * When replying to mail, it sends from the address that the message was sent to by default. * All mail winds up in one inbox. Outlook (2003, 2007) does do this if you set up different mail accounts, but we shouldn't have to do that.

5 6

[Dovecot] Unseen messages question
by Antoine Nguyen 14 Apr '12

14 Apr '12

Hi list, this question is related to the IMAP protocol itself, not really to Dovecot. I'm trying to understand what is the more efficient way to maintain the number of unseen messages of the currently selected mailbox. RFC3501 says a client must not issue a STATUS command to the selected mailbox and that information sent by a SELECT is enough. My current idea follows these steps : * Issue a STATUS before the mailbox is selected => I know how many unseen messages it contains * SELECT the mailbox => I got the eventual first unseen message in this mailbox but I don't understand how this info can be useful * Maintain the unseen counter (on client side) according to what the user do * Send a NOOP command every X minutes and look at the RECENT response to see if there are new messages I think it works pretty well when the mailbox is opened only once. Let's imagine this mailbox is opened twice, by different clients. If one client marks a message as \Seen, how can the second client know about this change? Thanks for your help, Antoine Nguyen http://modoboa.org/

1 0