- dovecot - dovecot.org

[Dovecot] Outlook 2010 very slow when using IMAP - are there any tweaks?
by Kaya Saman 03 Jul '12

03 Jul '12

Hi, though this is a bit of a side question, has anybody had an issue while running Outlook 2010 with Dovecot? The reason why I am asking is that I have setup a Dovecot 2.1.7 server on FreeBSD which works fantastically with Thunderbird but Outlook seems to be twice as slow in transferring information across?? # dovecot -n # 2.1.7: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.2-RELEASE amd64 auth_debug = yes auth_mechanisms = plain ntlm login auth_use_winbind = yes auth_username_format = %n auth_verbose = yes auth_winbind_helper_path = /usr/local/bin/ntlm_auth disable_plaintext_auth = no info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_gid = mail_user mail_home = /mail/AD_Mail/%Ld/%Ln mail_location = maildir:~/Maildir mail_uid = mail_user passdb { args = failure_show_msg=yes driver = pam } pop3_fast_size_lookups = yes pop3_lock_session = yes pop3_no_flag_updates = yes protocols = imap pop3 ssl = no userdb { driver = static } Since (like most corporate organizations out there) we solely run Outlook coupled to Exchange, this excersize was meant to be a way of getting rid of PST files. We don't run out own Exchange however, and don't have any control over it either. My workaround was to simply use the Outlook GUI space to transfer emails between Exchange and Dovecot running the IMAPv4 protocol. For whatever reason Outlook is being really garbage about dealing with stuff and since I don't know Outlook or MS products very well (being your typical average OpenSource guy) I was wondering if there were any tweaks that could be made within Outlook to speed it up or in Dovecot to work better with Outlook? I guess one could get sidetracked into the argument of mdbox vs. Maildir from my config however, Thunderbird is really fast and transfers large amounts of data really easily. Reaches round 130Mbps using nload performance grapher, while Outlook only manages ~50kbps but spikes at 2-3Mbps on occassion. Can anyone offer any guidence or assistance in this matter?? Actually wherever I run Dovecot, including my servers at home, it is fast and reliable. Yes I know MS is the polar opposite of anything worth using however, my company won't change and I'm stuck banging my head against the wall while trying to get MS to interface with ANYTHING..... Regards, Kaya

16 64

[Dovecot] Problem with 'doveadm mailbox status -t' reporting cumulative vsizes after upgrading from v2.0.16 to v2.1.7
by Jase Thew 03 Jul '12

03 Jul '12

Hi, I upgraded from Dovecot v2.0.16 to v2.1.7 over night and I noticed this morning that one of my daily reports which lists summarised mailbox sizes per user has started listing nonsense for vsizes. The reporting script at its core calls : doveadm -f flow mailbox status -A -t 'messages vsize' '*' It appears that Dovecot 2.1.7 is not resetting the vsize after collating the sum total of mailboxes sizes for each user, so that vsize just constantly increases as it iterates over each user. Eg: # doveadm -f flow mailbox status -A -t 'messages vsize' '*' accounts(a)example.com messages=1 vsize=759 adam(a)example.com messages=0 vsize=759 amy(a)example.com messages=24 vsize=51699697 andy(a)example.com messages=5446 vsize=3220940815 anna(a)example.com messages=50 vsize=3224035563 careers(a)example.com messages=1 vsize=3224036311 craig(a)example.com messages=2471 vsize=4421343199 creative(a)example.com messages=189 vsize=4426884182 david(a)example.com messages=8 vsize=4440729729 davidw(a)example.com messages=0 vsize=4440729729 enquiries(a)example.com messages=1 vsize=4440730491 gemma(a)example.com messages=4109 vsize=6349098844 gin(a)example.com messages=86 vsize=6392599904 holly(a)example.com messages=2000 vsize=7200342663 ian(a)example.com messages=0 vsize=7200342663 info(a)example.com messages=4 vsize=7200558689 jackie(a)example.com messages=2 vsize=7200721146 jade(a)example.com messages=137 vsize=7210548548 jake(a)example.com messages=16667 vsize=15260532446 katie(a)example.com messages=1 vsize=15260533375 mark(a)example.com messages=0 vsize=15260533375 mike.a(a)example.com messages=9 vsize=15261474205 mike.s(a)example.com messages=296 vsize=15314352543 mike(a)example.com messages=6357 vsize=20631446344 nick(a)example.com messages=1184 vsize=21038046728 social(a)example.com messages=65 vsize=21038935461 will(a)example.com messages=85 vsize=21057572390 [SNIP] The same occurs with -u '*(a)example.com' in place of -A, and also for 'all' in place of 'messages vsize'. Is this expected behaviour in 2.1.x compared to 2.0.x, or have I stumbled upon a bug? Regards, Jase Thew.

2 2

[Dovecot] Dovecot shared library to replace libc-client
by Asheesh Laroia 03 Jul '12

03 Jul '12

Hi all Dovecotters, Lots of programs (e.g, PHP) link to a library called c-client, which is a derivative of the original IMAP implementation, UW IMAP. (For those new to UW IMAP, read here: http://www.washington.edu/imap/ ) UW IMAP is not in as much of active development as it used to be, so I am curious: I see there is a dovecot shared library. I haven't looked into the details, but here are things I'm interested in: 1. Replacing libc-client's use as a client library In Debian, for example, you can search for packages that depend on this library as a client. It looks like this: $ ~ apt-cache rdepends libc-client2007e libc-client2007e Reverse Depends: uw-mailutils uw-imapd libc-client2007e-dev ipopd prayer php5-imap mailsync libmail-cclient-perl asterisk aolserver4-nsimap uw-mailutils libc-client2007e-dev prayer php5-imap mailsync libmail-cclient-perl asterisk-voicemail-imapstorage Let's say, hypothetically, we wanted to switch php5-imap to using Dovecot where it currently uses libc-client. I envision creating libdovecot-c-client-alike that is a set of headers and a library that is API-compatible with (at least a subset of) c-client. You can call that a "compatibility shim." Then e.g. php5-imap could be given the path to those headers and the corresponding libdovecot-c-client-alike library, and when it thinks it is linking to c-client, it could instead link to the libdovecot-c-client-alike. This might be convenient if you want to limit how much of a public API is presented by the current "dovecot.so" that gets installed in e.g. /usr/lib/dovecot/. The compatiblity shim could have a small API, and if you don't want provide ABI guarantees within dovecot.so, the shim could dlopen() dovecot.so rather than link to it. 2. Use of Dovecot shared library within alpine, embedding the imapd Right now, the mail client "alpine" embeds a copy of the UW IMAP source. It uses this when accessing local mail spools, for example. If Dovecot's IMAPd were available as a shared library, perhaps with a c-client-like API, (although not necessarily -- it would be feasible to upgrade alpine to a different API), then alpine could use Dovecot's mail drivers directly. So, those two are the dream. Timo and others, what are your thoughts? Thanks for reading this far! -- Asheesh. P.S. The radical request #2 would be an excellent, decisive way to end a sad thread in the Debian bug tracker about Alpine + Maildir: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405762 .

2 3

[Dovecot] Authentication failed (migrate from 2.0.13 to 2.0.17)
by Dovecot user 03 Jul '12

03 Jul '12

Hi, I use OpenBSD 5.1, roundcube 0.7.2 and dovecot 2.0.17 (684381041dc4+), mysql. I get the following error when i try to connect to imap : roundcube: IMAP Error: Login failed for testing(a)mydomain.net from 192.168.0.92. AUTHENTICATE PLAIN: Authentication failed. in /var/www/webmail/roundcubemail-0.7.2/program/include/rcube_imap.php on line 205 (POST /webmail/?_task=login&_action=login) dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=, method=CRAM-MD5, rip=127.0.0.1, lip=127.0.0.1, TLS Jul 2 15:19:13 mx dovecot: auth-worker: mysql(localhost): Connected to database mail Jul 2 15:19:15 mx dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Can you help me please ? Here my config files : *dovecot-sql.conf driver = mysql connect = host=localhost dbname=mail user=postfix password=postfix default_pass_scheme = PLAIN password_query = SELECT email as user, password FROM users WHERE email = '%u' user_query = SELECT id as uid, id as gid, home, concat('*:storage=', quota, 'M') AS quota_rule FROM users WHERE email = '%u' *dovecot.conf #i use this on OpenBSD 5.0 and dovecot 2.0.13, works, but it doesn't seem to work with this version :-( # 2.0.13: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.0 i386 ffs auth_mechanisms = plain login digest-md5 cram-md5 apop auth_debug=yes base_dir = /var/dovecot/ first_valid_uid = 1000 mail_location = maildir:/var/mailserv/mail/%d/%n mmap_disable = yes passdb { args = /etc/dovecot-sql.conf driver = sql } plugin { antispam_mail_notspam = --ham antispam_mail_sendmail = /usr/local/bin/sa-learn antispam_mail_sendmail_args = --username=%u antispam_mail_spam = --spam antispam_mail_tmpdir = /tmp antispam_signature = X-Spam-Flag antispam_signature_missing = move antispam_spam = SPAM;Spam;spam;Junk;junk antispam_trash = trash;Trash;Deleted Items; Deleted Messages autocreate = Trash autocreate2 = Spam autocreate3 = Sent autocreate4 = Drafts autosubscribe = Trash autosubscribe2 = Spam autosubscribe3 = Sent autosubscribe4 = Drafts quota = maildir quota_rule = *:storage=5G quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2 = storage=80%% /usr/local/bin/quota-warning.sh 80 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap sieve pop3 service auth { unix_listener /var/run/dovecot-auth-master { group = _dovecot mode = 0666 user = _dovecot } unix_listener /var/spool/postfix/private/auth { group = _postfix mode = 0660 user = _postfix } } service imap-login { service_count = 0 #user = _dovecot vsz_limit = 64 M } service pop3-login { service_count = 0 #user = _dovecot vsz_limit = 64 M } ssl_cert =ssl_cipher_list = HIGH:MEDIUM:+TLSv1:!SSLv2:+SSLv3 ssl_key = userdb { args = /etc/dovecot-sql.conf driver = sql } #userdb { # driver = passwd #} protocol imap { imap_client_workarounds = delay-newmail mail_plugins = quota imap_quota autocreate } protocol pop3 { mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xv%08Xu } protocol lda { auth_socket_path = /var/run/dovecot-auth-master mail_plugins = $mail_plugins sieve postmaster_address = postmaster(a)mx.itdebug.net sendmail_path = /usr/sbin/sendmail } default_login_user = _dovenull default_internal_user = _dovecot ## ## ManageSieve specific settings ## # Service definitions service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service managesieve { #Max. number of ManageSieve processes (connections) #process_count = 1024 } # Service configuration protocol sieve { } Thank you very much. -- Wesley

2 7

[Dovecot] v2.1.8 released
by Timo Sirainen 03 Jul '12

03 Jul '12

http://dovecot.org/releases/2.1/dovecot-2.1.8.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.8.tar.gz.sig Most importantly fixes a pretty bad behavior of sending mailbox names as UTF-8 instead of mUTF-7 as required by IMAP RFC. I'm surprised nobody hadn't noticed this in v2.1.x tree before yesterday. I guess some clients might have translated the name to UTF-8 anyway and not noticed it, while others would have silently ignored the problem of not seeing STATUS updates. + pop3c: Added pop3c_master_user setting. - imap: Mailbox names were accidentally sent as UTF-8 instead of mUTF-7 in previous v2.1.x releases for STATUS, MYRIGHTS and GETQUOTAROOT commands. - lmtp proxy: Don't timeout connections too early when mail has a lot of RCPT TOs. - director: Don't crash if the director is working alone. - shared mailboxes: Avoid doing "@domain" userdb lookups. - doveadm: Fixed crash with proxying some commands. - fts-squat: Fixed handling multiple SEARCH parameters. - imapc: Fixed a crash when message had more than 8 keywords. - imapc: Don't crash on APPEND/COPY if server doesn't support UIDPLUS.

1 0

[Dovecot] Additional passdb result status
by Jürgen Pabel 03 Jul '12

03 Jul '12

Dear Dovecot-Team, I am implementing a plugin (for the pop3/imap process) that requires some data to provided from the authentication phase (a derivative of the password). For that, I have now implemented a passdb plugin that generates this data and I would like to "pass" this data down to the mail process (pop3/imap) via extra_fields in the reply of the authentication. The general idea is that my custom passdb plugin calculates the data, sets the extra_field and returns some error (authentication was not successful) so that the "real" passdb backend can be invoked to "really" validate the authentication data. However, in auth_request_handle_passdb_callback() the extra_fields are reseted unless the return code is PASSDB_RESULT_USER_DISABLED. But if that return code is used then any following passdb's aren't invoked any more - which makes sense with respect to user authenticiation. I would therefore like to propose that some IGNORE/CONTINUE-status to be introduced in auth/passdb.h, that would be handled in that extra_fields and possible other values are not reseted in order to allow such propagation of data from authentication process down to the mail process (which could be extracted from the reply string by parsing it). As a further implementation alternative (to the parsing of the reply string), I also propose that some new "environment" item be introduced (in auth_request) in order to allow such data passing in a generic manner. I hope you consider my proposal to be reasonable. If desired, I could implement this myself and provide a patch for merging (based on 2.0.x). If my proposal is generally unfavored, it would be great if any alternative approaches for my situation were suggested. Thanks. Regards, Jürgen PS: please reply to my e-mail (or CC me), as I have not subscribed to the dovecot list

3 3

[Dovecot] userdb errors after upgrading to 2.1
by André Rodier 03 Jul '12

03 Jul '12

Hello everybody, I am running debian wheezy for development and test, and I recently upgrade to dovecot 2.1.7 I am using LDAP lookups, and virtual users with the same UID/GID. Everything was working fine before, but now, I have this error when I try to send an email to a local account: -------------------------------------------------------- Jun 26 15:46:52 lapetus dovecot: lmtp(24518): Error: user user.test(a)indienet.com: Auth USER lookup failed Jun 26 15:46:52 lapetus dovecot: auth: Error: userdb(user.test(a)indienet.com,127.0.0.1): client doesn't have lookup permissions for this user: userdb reply doesn't contain uid (change userdb socket -------------------------------------------------------- However, even if I set the permissions to 0666, I still have the same error. Can you point me in the right direction to fix this, please? Kind regards, André Rodier

2 1

[Dovecot] Wrong headers in dovecot-crlf
by Matthieu RAKOTOJAONA 03 Jul '12

03 Jul '12

Hello everyone, I'm using the very good imaptest [0] tool to test my little imap server implementation. I've tried to use the dovecot-crlf [1] file, but it looks like there are some major issues : $ grep -n "In-Reply-To.*;" tests/data/dovecot-crlf 479:In-Reply-To: <20020806175441.GA7148(a)linux.taugt.net>; from rueckert(a)informatik.uni-rostock.de on Tue, Aug 06, 2002 at 07:54:41PM +0200 525:In-Reply-To: <20020806234054.GA30820(a)carpa.ciagri.usp.br>; from marcelo(a)carpa.ciagri.usp.br on Tue, Aug 06, 2002 at 08:40:54PM -0300 564:In-Reply-To: <20020806234054.GA30820(a)carpa.ciagri.usp.br>; from marcelo(a)carpa.ciagri.usp.br on Tue, Aug 06, 2002 at 08:40:54PM -0300 673:In-Reply-To: <20020807231956.GA11240(a)carpa.ciagri.usp.br>; from marcelo(a)carpa.ciagri.usp.br on Wed, Aug 07, 2002 at 08:19:56PM -0300 795:In-Reply-To: <20020808131329.GA30775(a)carpa.ciagri.usp.br>; from marcelo(a)carpa.ciagri.usp.br on Thu, Aug 08, 2002 at 10:13:30AM -0300 964:In-Reply-To: <20020808193533.GA28619(a)carpa.ciagri.usp.br>; from marcelo(a)carpa.ciagri.usp.br on Thu, Aug 08, 2002 at 04:35:33PM -0300 21545:In-Reply-To: <1046294808.30811.66.camel@hurina>; from tss(a)iki.fi on Wed, Feb 26, 2003 at 11:26:48PM +0200 22042:In-Reply-To: <1046373554.18310.4.camel@hurina>; from tss(a)iki.fi on Thu, Feb 27, 2003 at 09:19:14PM +0200 23712:In-Reply-To: <20030227212127.A10927(a)pcx3332.desy.de>; from Juergen.Kahnert(a)DESY.de on Thu, Feb 27, 2003 at 09:21:27PM +0100 25498:In-Reply-To: <OFF6D684CA.26838A7C-ON42256CE8.003A8EFC-42256CE8.003B49AC(a)icoc.org>; from Leslie_Viljoen(a)icoc.org on Thu, Mar 13, 2003 at 12:44:52PM +0200 30654:In-Reply-To: <1048667343.30187.100.camel@hurina>; from tss(a)iki.fi on Wed, Mar 26, 2003 at 10:29:03AM +0200 31126:In-Reply-To: <1048704303.31565.214.camel@hurina>; from tss(a)iki.fi on Wed, Mar 26, 2003 at 08:45:03PM +0200 31313:In-Reply-To: <1048928723.6856.21.camel@hurina>; from tss(a)iki.fi on Sat, Mar 29, 2003 at 11:05:23AM +0200 31820:In-Reply-To: <1049101161.884.126.camel@hurina>; from tss(a)iki.fi on Mon, Mar 31, 2003 at 11:59:21AM +0300 31890:In-Reply-To: <Pine.LNX.4.44.0303311009510.17234-100000(a)vegemite.nssg.mitel.com>; from charlieb-dovecot(a)e-smith.com on Mon, Mar 31, 2003 at 10:12:22AM -0500 32037:In-Reply-To: <Pine.LNX.4.44.0303311414410.17234-100000(a)vegemite.nssg.mitel.com>; from charlieb-dovecot(a)e-smith.com on Mon, Mar 31, 2003 at 02:19:27PM -0500 32463:In-Reply-To: <1049243642.11879.25.camel@hurina>; from tss(a)iki.fi on Wed, Apr 02, 2003 at 03:34:02AM +0300 As you can see, many of the "In-Reply-To" headers are polluted with some junk. The situation is the same for many "Message-ID" headers. I don't know why they are here, but I think it's a mistake. I thought I would let you know. [0] http://imapwiki.org/ImapTest [1] http://www.dovecot.org/tmp/dovecot-crlf Regards, -- Matthieu RAKOTOJAONA

2 1

[Dovecot] Setting up mixed mbox and maildir
by Jonathan Ryshpan 03 Jul '12

03 Jul '12

I'm trying to set up a dovecot server for which mail arrives in an mbox, and mail is stored in a maildir. The wiki (see http://wiki.dovecot.org/Namespaces) refers to this as "Mixed mbox and Maildir". It advises handling this situation by creating two namespaces: one for the mbox and the other for the maildir. Each of these namespaces starts with namespace private { On the other hand the sample configuration in the documentation puts inbox in a namespace starting with: namespace inbox { # Namespace type: private, shared or public #type = private It appears that there has been a change in the configuration syntax after the wiki was written, and that the word following namespace no longer gives a property of the namespace, but rather its name. Is this correct? In any case, how should the configuration be modified to handle mixed mailboxes? Thanks - jon

4 7

[Dovecot] indexer-worker
by Wojciech Puchar 03 Jul '12

03 Jul '12

why this process (which most probably do squat index/update) runs as root, not - like imap process - as user? 29413 root 1 76 0 22820K 9204K kqread 1 0:17 5.86% indexer-worker

2 3