- dovecot - dovecot.org

[Dovecot] Enforcing server cipher list order
by Phillip Odam 29 Aug '13

29 Aug '13

I noticed a similar/same discussion back on Aug 14th titled force ciphers order for clients. However from that thread I can't find quite what I'm after. From my testing of dovecot 2.1.6, by default it appears to honor the clients cipher list order for SSL/TLS connections. I can't find any documentation on dovecot providing a setting like Apache HTTPDs to either honor the client or server cipher list i.e. SSLHonorCipherOrder. Do newer versions (> 2.1.6) of dovecot either make this configurable or force honoring of the servers cipher list order? Or is the cipher selection a function that openssl performs? The version of openssl in use is 1.0.1e-fips. Thanks Phillip

1 0

Re: [Dovecot] Log successful login plain text password
by Joseph Tam 29 Aug '13

29 Aug '13

Marco Fretz writes: > Maybe you can find a way in this direction > > http://wiki2.dovecot.org/HowTo/ConvertPasswordSchemes I've sync'd a separate password system by process tracing dovecot's auth process and dumping out the arguments of read() calls for some fixed set of descriptors and piping it into password synching script. A bit of a hack, but it works without having to touch dovecot. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Bug in dovecot 2.2.5: segfault due to bad alignment
by Andreas F. Borchert 29 Aug '13

29 Aug '13

Take a look at the sources, hmac.h declares struct hmac_context: struct hmac_context { char ctx[HMAC_MAX_CONTEXT_SIZE]; char ctxo[HMAC_MAX_CONTEXT_SIZE]; const struct hash_method *hash; }; If compiled for a 32 bit virtual address space, this has an alignment requirement of 4 due to the hash pointer. In line 171 of auth-token.c, we have following declaration of ctx as a local variable in auth_token_get(): struct hmac_context ctx; This is put on an address with an alignment requirement of 4. In lines 174 and 175 hmac_init is invoked with hash_method_sha1: hmac_init(&ctx, (const unsigned char*)username, strlen(username), &hash_method_sha1); In hmac.c, lines 43 and following, ctx->ctx with an alignment of 4 is passed to meth->init and meth->loop where meth refers to hash_method_sha1: meth->init(ctx->ctx); meth->loop(ctx->ctx, k_ipad, 64); These functions refer now to sha1_init and sha1_loop where the first parameter is expected to be a pointer to struct sha1_ctxt, a data structure which is declared in sha1.h: struct sha1_ctxt { union { uint8_t b8[20]; uint32_t b32[5]; } h; union { uint8_t b8[8]; uint64_t b64[1]; } c; union { uint8_t b8[64]; uint32_t b32[16]; } m; uint8_t count; }; Here we have with b64 one uint64_t which has on a SPARC platform an alignment requirement of 8. In consequence, struct sha1_ctxt has an alignment requirement of 8. With the invocations of meth->init and meth->loop above we pass a pointer to a data structure of alignment 4 to a function expecting a pointer to a data structure of alignment 8. Chances are that the alignment requirement is not met, causing a segmentation violation. This must be solved by declaring struct hmac_context such that is not just big enough but respects also the highest alignment required for one of the hashing data structures. There are several options to do this: * Beginning with C11, you are free to use an alignment specifier, i.e. add _Alignas ( uint64_t ) (see section 6.7.5 in ISO 9899-2011) * GCC supports alignment attributes, i.e. add __attribute__ ((aligned (8))) or whatever is required instead of 8, see http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html * Do not use a local variable for it, allocate the data structure using malloc instead. If you want to see a live crash, here is the relevant output of gdb that debugs ${prefix}/libexec/dovecot/auth. Program received signal SIGSEGV, Segmentation fault. sha1_loop (ctxt=0xffbff63c, input=0xffbff548, len=64) at sha1.c:224 224 sha1.c: No such file or directory. (gdb) where #0 sha1_loop (ctxt=0xffbff63c, input=0xffbff548, len=64) at sha1.c:224 #1 0xff2e218c in hmac_init (ctx=ctx@entry=0xffbff63c, key=key@entry=0x6a698 "borchert", key_len=8, meth=0x555d0 <hash_method_sha1>) at hmac.c:44 #2 0x00023310 in auth_token_get (service=service@entry=0x6a648 "imap", session_pid=0x56071 "26272", username=0x6a698 "borchert", session_id=0x6a650 "AErv6nbk6gB/AAAB") at auth-token.c:174 #3 0x00021708 in userdb_callback (result=USERDB_RESULT_OK, request=0x6a530) at auth-request-handler.c:668 #4 0x0001f144 in auth_request_userdb_callback (result=<optimized out>, result@entry=USERDB_RESULT_OK, request=request@entry=0x6a530) at auth-request.c:1039 #5 0x000312c8 in prefetch_lookup (auth_request=0x6a530, callback=0x1f058 <auth_request_userdb_callback>) at userdb-prefetch.c:40 #6 0x0001f37c in auth_request_lookup_user (request=0x6a530, callback=callback@entry=0x2150c <userdb_callback>) at auth-request.c:1072 #7 0x00022034 in auth_request_handler_master_request ( handler=<optimized out>, master=master@entry=0x6b120, id=1292369921, client_id=1, params=0x55bfc) at auth-request-handler.c:758 #8 0x0001be98 in master_input_request (args=<optimized out>, conn=0x6b120) at auth-master-connection.c:127 #9 auth_master_input_line (line=<optimized out>, conn=0x6b120) at auth-master-connection.c:598 #10 master_input (conn=0x6b120) at auth-master-connection.c:653 #11 0xff2ecca4 in io_loop_call_io (io=io@entry=0x6b398) at ioloop.c:387 #12 0xff2ed604 in io_loop_handler_run (ioloop=ioloop@entry=0x5e5e8) at ioloop-poll.c:211 #13 0xff2ec7a8 in io_loop_run (ioloop=0x5e5e8) at ioloop.c:406 #14 0xff29ad7c in master_service_run (service=0x5e128, callback=0x27b40 <client_connected>) at master-service.c:566 #15 0x0001852c in main (argc=1, argv=0xffbffd54) at main.c:393 (gdb) print ctxt $1 = (struct sha1_ctxt *) 0xffbff63c As you can see, ctxt is on a 4-byte boundary, not on an 8-byte boundary. The crash happens at sha1.c:224 where the 8-byte-alignment is indeed mandatory on a SPARC architecture: ctxt->c.b64[0] += copysiz * 8; The environment is Solaris 10 on SPARCv9. The sources have been compiled using gcc 4.8.0 for 32 bit. Andreas.

2 1

[Dovecot] Dovecot proxy to Microsoft Exchange 2013
by Ricardo Machini Barbosa 28 Aug '13

28 Aug '13

Hello, I am trying to do a proxy with dovecot to IMAP backend server that are using Microsoft Exchange 2013. I already did this with Microsoft Exchange 2007 and Microsoft Exchange 2010 and it works perfectly! But with Microsoft Exchange 2013 I can not perform LOGIN. The error log message is: /imap-login: Error: proxy(user(a)domain.com.br): Login for exchange2013.domain.com.br:143 timed out in state=4 (after 30 secs, local=x.x.x.x:59640)/ My troubleshoot was: - tcpdump on dovecot server side: I can see the commands sent/received by Microsoft Exchange. But no the "OK LOGIN" response. /* OK The Microsoft Exchange IMAP4 service in xxxx is ready.// //C CAPABILITY// //L LOGIN "user(a)domain.com.br" "123456"// //* CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN STARTTLS UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+// //C OK CAPABILITY completed./ - tcpdump with telnet login on dovecot server side: Works fine. /* OK The Microsoft Exchange IMAP4 service in xxxx is ready.// //a login "user(a)domain.com.br" "123456"// //a OK LOGIN completed.// //a logout// //* BYE Microsoft Exchange Server 2013 IMAP4 server signing off.// //a OK LOGOUT completed./ - Log verbose on Microsoft Exchange 2013. Look like that Microsoft Exchange did not receive the login command. Someone already tried do this with Microsoft Exchange 2013 ? See bellow some information about my dovecot configuration: /# 2.2.2: dovecot.conf// //# OS: Linux 2.6.32-358.2.1.el6.centos.plus.x86_64 x86_64 CentOS release 6.4 (Final)// // //base_dir = /var/run/dovecot/// //disable_plaintext_auth = no// //listen = x.x.x.x// //mbox_write_locks = fcntl// //passdb {// // args = /etc/dovecot/dovecot-ldap.conf.ext// // driver = ldap// //}// // //protocols = imap pop3// //service imap-login {// // inet_listener imap {// // port = 143// // }// // inet_listener imaps {// // port = 993// // ssl = yes// // }// // process_min_avail = 4// // service_count = 0// // vsz_limit = 512 M// //}// //service pop3-login {// // inet_listener pop3 {// // port = 110// // }// // inet_listener pop3s {// // port = 995// // ssl = yes// // }// // process_min_avail = 4// // service_count = 0// // vsz_limit = 512 M// //}// //ssl_cert = </etc/dovecot/certificate/chained.crt// //ssl_key = </etc/dovecot/certificate/cert.key// //userdb {// // driver = prefetch// //}// // ///etc/dovecot/dovecot-ldap.conf.ext// //hosts = x.x.x.x// //dn = cn=admin,o=email// //dnpass = xxxxxxx// //ldap_version = 3// //base = o=email// //scope=subtree// //pass_filter = mail=%u// //pass_attrs = uid=user,=password=,=proxy=y,mailHost=host,=nopassword=y/ Thanks, Ricardo Machini

4 7

[Dovecot] Disable PAM username change?
by George 28 Aug '13

28 Aug '13

Hi! I have a problem involving Samba4, exim4, fetchmail, Dovecot and PAM... I am using Dovecot 2.1.7 on Debian Wheezy. I have setup a "maildrop" machine, which fetches mail from an external POP3 server for multiple accounts using fetchmail, delivers to local users mailboxes through exim4 and then serves them on the intranet via IMAP with Dovecot. This works great with local unix users, but I am having some trouble to configure it to work with Samba4 AD users (Samba 4.0.9 running as a DC on the same machine). Basically, I have configured PAM with winbind and it works fine (AD users can SSH the machine for example). Dovecot also authenticates properly via PAM, but the problem is that the username gets changed in the process (PAM returrns the "username" as "DOMAIN\username"): Aug 21 22:50:22 dc2 dovecot: auth-worker(5179): Debug: auth(foo,127.0.0.1): username changed foo -> DOMAIN\foo Aug 21 22:50:22 dc2 dovecot: auth: Debug: auth(foo,127.0.0.1,<0bBfg3/kpQB/AAAB>): username changed foo -> DOMAIN\foo Aug 21 22:50:22 dc2 dovecot: auth: Debug: client out: OK#0111#011user=DOMAIN\foo So the actual problem is that exim4 is delivering the mail to, for example, "/var/mail/foo" but Dovecot is looking for the mailbox on "/var/mail/DOMAIN\foo", even if the username given in the IMAP session is just "foo". The wiki mentions<http://wiki2.dovecot.org/PasswordDatabase/PAM>that "a PAM module can change the username". Can this be avoided? I need either: * Exim to deliver the mail to the user mailbox, *including* the domain part (out of scope of this list, but information is welcome), or * Dovecot to fetch the mail *not* using the domain part as part of the username variable. As a quick and dirty workaround, I hardcoded the domain part in the exim delivery path (something like "/var/mail/DOMAIN\\$local_part"), but this is far from optimal since I cannot use both unix users and AD users, I cannot use dovecot_delivery LDA transport, etc. As a bottom line, I also posted this to the Samba list because I believe this could also be solved if winbind just always returned the username without the domain when queried (conf option not working, probable bug) Ideas are welcome!! Best regards, Jorge

1 1

[Dovecot] Install of Dovecot 2.2.5 on Solaris 10/Openssl version 0.9.7d 17 Mar 2004
by Haney, Donald 28 Aug '13

28 Aug '13

Greetings! I am attempting to install Dovecot 2.2.5 on Solaris 10 Sparc hardware with openssl version 0.9.7d 17 Mar 2004. I have created a dovecot user and a dove null user, assigned them their own login directories specifying the ksh shell and assigned them to their own groups. I have run the configure command successfully and am having trouble with the make. At first, I received the problem listed below: /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test -DMODULE_DIR=\""/usr/local/lib/dovecot"\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -I/usr/sfw/include -MT iostream-openssl-context.lo -MD -MP -MF .deps/iostream-openssl-context.Tpo -c -o iostream-openssl-context.lo iostream-openssl-context.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test -DMODULE_DIR=\"/usr/local/lib/dovecot\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -I/usr/sfw/include -MT iostream-openssl-context.lo -MD -MP -MF .deps/iostream-openssl-context.Tpo -c iostream-openssl-context.c -fPIC -DPIC -o .libs/iostream-openssl-context.o iostream-openssl-context.c: In function `ssl_proxy_ctx_set_crypto_params': iostream-openssl-context.c:451: error: `SSL_OP_SINGLE_ECDH_USE' undeclared (first use in this function) iostream-openssl-context.c:451: error: (Each undeclared identifier is reported only once iostream-openssl-context.c:451: error: for each function it appears in.) I followed directions found in http://hg.dovecot.org/dovecot-2.2/rev/27ebd9552471 to resolve this problem (I believe). I am now seeing the following error: test-http-server.c: In function `main': test-http-server.c:122: error: size of array `type name' is negative *** Error code 1 make: Fatal error: Command failed for target `test-http-server.o' Current working directory /export/home/hanedo00/dovecot-2.2.5/src/lib-http *** Error code 1 The following command caused the error: fail= failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ I have not had any luck thus far finding the solution for this error against test-http-server.o. Any assistance would be appreciated. Thanks, Don Haney This message and any attachments are solely for the use of intended recipients. The information contained herein may include trade secrets, protected health or personal information, privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you are not an intended recipient, you are hereby notified that you received this email in error, and that any review, dissemination, distribution or copying of this email and any attachment is strictly prohibited. If you have received this email in error, please contact the sender and delete the message and any attachment from your system. Thank you for your cooperation

2 1

[Dovecot] Trouble with case-sensitive LDAP user logins
by Jason Discount 28 Aug '13

28 Aug '13

Hi All, I have a client running Dovecot-Postfix on Debian Squeeze. I'm using Dovecot from the Squeeze repository. # dovecot --version 1.2.15 I've implemented a central mail_location and am using one vmail user, as I thought this would be be the best approach for when it came time to implement Shared and Public Mailboxes. # dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-686 i686 Debian 6.0.7 ext3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3s managesieve listen(default): 127.0.0.1:143 listen(imap): 127.0.0.1:143 listen(pop3): 127.0.0.1:110 listen(managesieve): * ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_listen(managesieve): ssl_ca_file: /etc/ssl/certs/RapidSSL_CA_bundle.pem ssl_cert_file: /etc/ssl/certs/mail.example.com.2013.chain.pem ssl_key_file: /etc/ssl/private/example.2013.key login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_max_userip_connections(default): 40 mail_max_userip_connections(imap): 40 mail_max_userip_connections(pop3): 10 mail_max_userip_connections(managesieve): 10 mail_privileged_group: mail mail_uid: vmail mail_gid: vmail mail_location: maildir:/var/spool/dovecot/%d/%u mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve namespace: type: private separator: / inbox: yes list: yes subscriptions: yes lda: postmaster_address: postmaster(a)example.com mail_plugins: sieve quota log_path: /var/log/dovecot-deliver.log info_log_path: /var/log/dovecot-deliver.log auth default: mechanisms: plain login passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap-userdb.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: maildir:User quota_rule: *:storage=1200M quota_rule2: Deleted Messages:storage=10%% quota_rule3: Deleted Items:storage=10%% quota_rule4: Trash:storage=10%% sieve: /var/spool/sieve/%d/%u/.dovecot.sieve sieve_dir: /var/spool/sieve/%d/%u All of the mail users are LDAP users only (not local UNIX users - not using nsswitch). dovecot-ldap-userdb.conf is a symbolic link to dovecot-ldap.conf # grep -v '^ *$#.*$\?$' /etc/dovecot/dovecot-ldap.conf uris = ldaps://mail.example.com/ dn = uid=mail,ou=Services,dc=example,dc=com dnpass = ****************** tls_require_cert = hard auth_bind = yes base = ou=People,dc=example,dc=com user_attrs = quota=quota_rule=*:storage=%$M user_filter = (&(objectClass=posixAccount)(mail=%u)) pass_attrs = uid=mail,userPassword=password pass_filter = (&(objectClass=posixAccount)(mail=%u)) Now, mail addressed to user(a)example.com and user(a)EXAMPLE.com correctly gets delivered to the correct mail location of /var/spool/dovecot/example.com/user, but the problem occurs when the user creates their account with uppercase characters in their username, e.g. user(a)exaMPLE.com. This creates a new directory at /var/spool/dovecot/exaMPLE.com/user, which ever receives any mail. Is it possible to ignore the case the user enters in their mail client and always land them at the lowercase mail directory? Where would this be done? Thank you, Jay

1 0

[Dovecot] How do I get CRAM-MD5 to work?
by LuKreme 28 Aug '13

28 Aug '13

I know how to ENABLE CRAM-MD5, but getting it to actually work? <http://wiki2.dovecot.org/HowTo/CRAM-MD5> It looks like I have to 1) manually create a CRAM-MD5 data file and, I suppose, 2) manually manage the file? Given I do not know user's passwords, this might be tricky. Currently I have users authenticate against MySQL (virtual users) or pam (local users). Or do i just ignore it all and stick with PLAIN since the connection is already encrypted? What is LOGIN? My MUA supports "Password" (which is PLAIN evidently), kerberos 5, MD5 Challenge-response (CRAM-MD5), and NTML (??) -- If you have any young friends who aspire to become writers, the second-greatest favor you can do them is to present them with copies of The Elements of Style. The first-greatest, of course, is to shoot them now, while they're happy. -Dorothy Parker

1 0

[Dovecot] Migrating from Maildir to Maildir:LAYOUT=fs
by Rainer M Krug 27 Aug '13

27 Aug '13

Hi I have use dovecot together with offlineimap to download my gmail account on a single user computer and I have only one maildir (~/Maildir). As I switched to Mac, I would like to use spotlight to index my mails, which apparently does not work as they are in hidden directories (.directories). So I would like to change to LAYOUT=fs. Is there an easy way to migrate my email structure? I have several folders and subfolders, but a manual solution would be fine with me as well. My questions: 1) can I simply restructure the mailboxes and rename the folders / move them into the folders where I want them after changing the configuration of dovecot? 2) Is there an easy tool I can use for this for one mailbox which is doing it automatically? Thanks, Rainer -- Rainer M. Krug email: RMKrug<at>gmail<dot>com

3 4

[Dovecot] Developer docs?
by C. Mills 27 Aug '13

27 Aug '13

Hi, I'm looking to modify Dovecot slightly to add support for a custom feature. I've spent some time reading the code, and I've been wondering if there are any contributor/developer documents I've missed that would make getting up to speed easier. I've read much of the code, and most of the wiki, including the Design/* and /*Process pages. They give a good summary of some of the design decisions, but I don't see much other than that. The docs included in the tarball are just dumps of the wiki pages. I've browsed some of the list archives as well, without finding much to help me. Are there other resources I've missed? What I'm trying to do requires passing some additional information/state from the imap-login process (presumably through the master) to the imap mail process. Any pointers much appreciated! Thanks, C. -- ----------------------------------------------------------------------- C. Mills -----------------------------------------------------------------------

2 4