- dovecot - dovecot.org

[Dovecot] IMAP and POP3 per SSL
by Lamprecht, Andreas 20 Mar '12

20 Mar '12

Hi! I'm new to this list and i could not find a way to search through the already posted articles, so please forgive me if this subject has been discussed before. Our security scanner stumbled over the IMAPs server i've set up recently using dovecot on a RedHat Enterprise 64bit Server. The security scanner found an error regarding a new SSL security leak named "BEAST". The exact error number is CVE-2011-3389. Details can be found here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-3389 "The internet" has some workarounds for this problem. For example, in Apache webserver, you need to set SSLHonorCipherOrder On in apache config. This results in the following C-Code being executed: SSL_CTX_set_options(ctx, SSL_OP_CIPHER_SERVER_PREFERENCE); This setting tells OpenSSL not to honor the Ciper Order sent from the client, but prefer it's own configured set of CipherSuites. According to Qualis SSL Labs ( https://www.ssllabs.com/ssldb/index.html ), a webserver configured with this setting is not affected by that BEAST security leak. Is there a way to implement such a setting into Dovecot, too? I have created a very quick and dirty solution to avoid being listed on our internal security problem's list. This patch is for dovecot 2.0.9 which is included in Redhat Enterprise Linux 6.2: *** src/login-common/ssl-proxy-openssl.c 2010-12-30 10:42:54.000000000 +0100 --- src/login-common/ssl-proxy-openssl.c_1 2012-03-20 09:48:28.359508087 +0100 *************** *** 924,930 **** X509_STORE *store; STACK_OF(X509_NAME) *xnames = NULL; ! SSL_CTX_set_options(ssl_ctx, SSL_OP_ALL | SSL_OP_NO_SSLv2); if (*set->ssl_ca != '\0') { /* set trusted CA certs */ store = SSL_CTX_get_cert_store(ssl_ctx); --- 924,930 ---- X509_STORE *store; STACK_OF(X509_NAME) *xnames = NULL; ! SSL_CTX_set_options(ssl_ctx, SSL_OP_ALL | SSL_OP_NO_SSLv2 | SSL_OP_CIPHER_SERVER_PREFERENCE ); if (*set->ssl_ca != '\0') { /* set trusted CA certs */ store = SSL_CTX_get_cert_store(ssl_ctx); Of course there should be a way to switch this setting on or off, but my C programming skills are rather basic ... So, maybe you have the time to look over it and implement a final solution for the BEAST problem. Greetings Andreas lamprecht

2 2

[Dovecot] INBOX cant be created
by Radim Kolar 20 Mar '12

20 Mar '12

Inbox does not exists on disk, but following command sequence will not create it. 2 select INBOX 2 NO Mailbox doesn't exist: INBOX 3 create INBOX 3 NO [ALREADYEXISTS] Mailbox already exists: INBOX i think its bug

4 5

[Dovecot] Problem with sieve
by Cédric Jeanneret 20 Mar '12

20 Mar '12

Hello List! I have a tiny-teeny problem with dovecot + sieve: it seems that the LDA doesn't run sieve, and thus doesn't filter my emails. Here's the sieve configuration: plugin { # Used by both the Sieve plugin and the ManageSieve protocol sieve=/var/local/vmail/%n/dovecot.sieve sieve_dir=/var/local/vmail/%n/sieve sieve_extensions = +notify +imapflags } The managesiege: protocol managesieve { # Specify an alternative address:port the daemon must listen on # (default: *:2000) listen = localhost:2000 managesieve_logout_format = bytes ( in=%i : out=%o ) } (this one is working fine, I can edit the filters through roundcube webmail, and the correct file (/var/local/vmail/%n/dovecot.sieve) is edited) the lda part: protocol lda { postmaster_address = foo(a)bar.com mail_plugins = sieve } I think all is in place to allow dovecot to use sieve... ? One more thing: dovecot --version 1.2.15 Any help will be welcomed :). Thanks in advance ! Cheers, C.

5 12

[Dovecot] Per-user IMAP enable - is it possible?
by Alexander Chekalin 20 Mar '12

20 Mar '12

Just wonder if it is possible to enable/disable IMAP4 on Dovecot (2.0.x as far) on per-user basis? The deal is simple: our policy is not to store a lot of mailing on mailserver (the user should store it locally), thus the 'use POP3' approach, but for a vary few users it is permitted to use IMAP4. But users sometimes simple miss the point that some mail clients (e.g. TB) 'prefer' to use IMAP4 first, and afterward I see mailbox full of mailings and no local store of it on user's workstation. Sound too complicated, but setting up two Dovecots is not something I'd love to do as well. Thank you for any ideas, Alexander

3 4

[Dovecot] Dsync Dovecot
by Jitendra Bhaskar 20 Mar '12

20 Mar '12

Hi guys, I am using dovecot-2.1.0 in centos 5.7, I configured dovecot with postfix in 2 system both system is having same configuration and os. I want to use dsync in mirror mode via ssh but I am not able to do it. When I followed the dsync wiki then I an unable to find the username : *dsync -u username mirror ssh -i id_dsa.dovecot mailuser(a)example.com dsync -u username* In the above command what will b user name and id_dsa.dovecot I am unable to understand. -- * Thanks & Regards * *Jitendra Kumar Bhaskar* Cell:- +91 7306311531 +91 8102997821

2 1

Re: [Dovecot] Using plaintext auth and SSL
by Jeff Simmons 20 Mar '12

20 Mar '12

On Monday, March 19, 2012 04:16:46 pm you wrote: > On 3/19/2012 4:04 PM, Jeff Simmons wrote: > > I'm working with a company that presently has a Linux mailserver which > > all users have (no shell) accounts on. Mail is accessed via pop3 with > > plaintext authentication. They want to move to a system using imap with > > SSL. I'm building them a new server. I'd like to offer both for a while > > so we can work the bugs out and migrate users over to SSL imap over > > time. It appears that in order to limit the imap connections to SSL I > > will need to run two separate instances of Dovecot. Is this correct? > > I only have SSL or TLS connections enabled and I only have one copy of > Dovecot running. Let me rephrase that. I want to run plaintext authentication pop3 and ssl/tls only authentication imap. The 'allow plaintext authentication' configuration directive appears to be global, meaning I will need to run two instances of dovecot for a while. Is that correct, or can this be done on a single instance of dovecot? -- Jeff Simmons jsimmons(a)goblin.punk.net Simmons Consulting - Network Engineering, Administration, Security "You guys, I don't hear any noise. Are you sure you're doing it right?" -- My Life With The Thrill Kill Kult

5 6

[Dovecot] Using plaintext auth and SSL
by Jeff Simmons 20 Mar '12

20 Mar '12

I'm working with a company that presently has a Linux mailserver which all users have (no shell) accounts on. Mail is accessed via pop3 with plaintext authentication. They want to move to a system using imap with SSL. I'm building them a new server. I'd like to offer both for a while so we can work the bugs out and migrate users over to SSL imap over time. It appears that in order to limit the imap connections to SSL I will need to run two separate instances of Dovecot. Is this correct? -- Jeff Simmons jsimmons(a)goblin.punk.net Simmons Consulting - Network Engineering, Administration, Security "You guys, I don't hear any noise. Are you sure you're doing it right?" -- My Life With The Thrill Kill Kult

1 0

[Dovecot] Creating an IMAP repo for ~100 users need some advice
by Kaya Saman 19 Mar '12

19 Mar '12

Hi, I am currently in the process of setting up an IMAP repository for round 100 users.... Currently the user authentication method is being handled via a Windows Domain Controller. The host OS for Dovecot will either be FreeBSD or CentOS. Would Dovecot be able to authenticate to either the DC directly or would we need to go through LDAP?? Additionally what would be the best method to store the **mail** information? - as in MySQL database or Maildir format; coinciding with this what is the best backup method in order to be able to do 'dump' backups or restore single emails?? Can anyone give me a hand with this? Regards, Kaya

8 21

[Dovecot] Accessing maildir snapshots through dovecot
by Laurent CARON 19 Mar '12

19 Mar '12

Hi, I'm currently having a fairly simple setup: - users (real, not virtual) - Maildir storage (over NFS) - 1 namespace I'm currently trying to render the storage snapshots available through dovecot (to allow my users to browse their mail history). dovecot.conf: namespace { inbox = yes location = prefix = INBOX. type = private } I did the following modifications: dovecot.conf: namespace snaps-h0 { prefix = INBOX.EmailBackup.h0. hidden = no list = yes inbox = no location = maildir:/home/.snapshot/hourly.0/%u/Maildir:INDEX=/var/tmp/dovecot/indexes/hourly.0/%u:CONTROL=/var/dovecot/control/hourly.0/%u type = private } Problem: I don't see the content of the inbox folder contained in the snapshots (subfolders are perfectly viewed). Do any of you have a clue on how to render it visible ? Thanks Laurent

3 3

[Dovecot] Building Dovecot RHEL RPMs with custom LDAP packages
by Nikolaos Milas 19 Mar '12

19 Mar '12

Hi, We are (still) mainly using CentOS 5 (5.8 x86_64). As CentOS / RHEL 5 standard OpenLDAP packages are rather old (2.3.x), we've been using LTB OpenLDAP packages (http://ltb-project.org/wiki/download#openldap) which get installed in non-standard file system locations. So, I would like to re-build Dovecot packages based on these OpenLDAP libraries, esp. because I see that dovecot RPM packages are built using OpenLDAP v2.3 libraries. I am not much experienced in building RPMs and preparing spec files. In http://dl.atrpms.net/all/dovecot.spec I see: ------------------------------------------------ BuildRequires: openldap-devel, cyrus-sasl-devel ... Obsoletes: %{name}-pgsql < %{epoch}:%{version}-%{release}, %{name}-mysql < %{epoch}:%{version}-%{release}, %{name}-sqlite < %{epoch}:%{version}-%{release}, %{name}-ldap < %{epoch}:%{version}-%{release}, $ Conflicts: %{name}-pgsql > %{epoch}:%{version}-%{release}, %{name}-mysql > %{epoch}:%{version}-%{release}, %{name}-sqlite > %{epoch}:%{version}-%{release}, %{name}-ldap > %{epoch}:%{version}-%{release}, $ ------------------------------------------------ So, I can change the former reference (openldap-devel) to: openldap-ltb-debuginfo, cyrus-sasl-devel Question 1: What other changes should we make in order to specify that we will be using LDAP libraries from: /usr/local/openldap/lib64 and include files from: /usr/local/openldap/include (rather than from /usr/lib64 and /usr/include, respectively, which are the standard file paths used in openldap-devel) Question 2: How the Obsoletes and Conflicts lines should be changed? Question 3: It seems to me (by reading the spec file) that the final Dovecot RPM (and the included executables) does not need any LDAP dynamic library in order to run with LDAP support (because I don't see any dependencies on openldap package). Can somebody please confirm? Any other associated info would be appreciated. Thanks, Nick

2 4