- dovecot - dovecot.org

[Dovecot] ssl enabled, but ssl_cert not set ( 2.0.7 freebsd 8.1 )
by Frank Bonnet 16 Dec '10

16 Dec '10

hello trying to install dovecot 2 on a fresh installed machine I get this error message : doveconf -n > dovecot-new.conf doveconf: Error: ssl enabled, but ssl_cert not set doveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/dovecot.conf: ssl enabled, but ssl_cert not set the ssl config file look like the following : Thanks for any info. ## ## SSL settings ## # SSL/TLS support: yes, no, required. <doc/wiki/SSL.txt> ssl = yes # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem # If key file is password protected, give the password here. Alternatively # give it when starting dovecot with -p parameter. Since this file is often # world-readable, you may want to place this setting instead to a different # root owned 0600 file by using ssl_key_password = <path. #ssl_key_password = # PEM encoded trusted certificate authority. Set this only if you intend to use # ssl_verify_client_cert=yes. The file should contain the CA certificate(s) # followed by the matching CRL(s). (e.g. ssl_ca = </etc/ssl/certs/ca.pem) #ssl_ca = # Request client to send a certificate. If you also want to require it, set # auth_ssl_require_client_cert=yes in auth section. #ssl_verify_client_cert = no # Which field from certificate to use for username. commonName and # x500UniqueIdentifier are the usual choices. You'll also need to set # auth_ssl_username_from_cert=yes. #ssl_cert_username_field = commonName # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 168 # SSL ciphers to use #ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL -- Frank BONNET 01.45.92.66.17 Service des Moyens Informatique Generaux ESIEE PARIS Cité Descartes / BP 99 93162 NOISY-LE-GRAND Cedex http://www.esiee.fr <http://www.esiee.fr/>

5 6

[Dovecot] problem with ~/mail/ namespace
by Tom Lieuallen 16 Dec '10

16 Dec '10

We just changed from UW imap last night and one of our bigger problems right now is that the ~/mail/ compatibility namespace doesn't seem to work. dovecot 2.0.8 Dec 15 12:01:52 zen.engr.oregonstate.edu dovecot: [ID 583609 mail.warning] imap(tom2): Warning: Subscriptions file /nfs/rack/u4/t/tom2/mail/.subscriptions: Ignoring invalid entry: ~/mail/foo1/folder1 Dec 15 12:01:52 zen.engr.oregonstate.edu dovecot: [ID 583609 mail.warning] imap(tom2): Warning: Subscriptions file /nfs/rack/u4/t/tom2/mail/.subscriptions: Ignoring invalid entry: ~tom2/mail/foo1/folder1 from .subscriptions: ~/mail/foo1/folder1 ~tom2/mail/foo1/folder1 in 10-mail.conf namespace { type = private separator = / prefix = inbox = yes } # for backwards compatibility: namespace { type = private separator = / prefix = mail/ hidden = yes list = no } namespace { type = private separator = / prefix = ~/mail/ hidden = yes list = no } namespace { type = private separator = / prefix = ~%u/mail/ hidden = yes list = no } What's funny is that it appears to work with a preauthenticated session or by using openssl to connect to port 993. 1 list "~/mail/" * * LIST (\NoInferiors \UnMarked) "/" "~/mail/testfolder" * LIST (\NoInferiors \UnMarked) "/" "~/mail/Trash" * LIST (\NoInferiors \UnMarked) "/" "~/mail/Sent" * LIST (\Noselect \HasChildren) "/" "~/mail/foo1" * LIST (\NoInferiors \UnMarked) "/" "~/mail/foo1/folder1" * LIST (\Noselect \HasChildren) "/" "~/mail/foo2" * LIST (\NoInferiors \UnMarked) "/" "~/mail/foo2/folder1" 1 OK List completed. 1 select ~/mail/foo2/folder1 * OK [CLOSED] Previous mailbox closed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 0 RECENT * OK [UIDVALIDITY 1274985137] UIDs valid * OK [UIDNEXT 2] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest 1 OK [READ-WRITE] Select completed. We're seeing this with at least thunderbird and outlook. thank you Tom Lieuallen Oregon State University

3 4

[Dovecot] Dovecot 2.0.8 don´t recognize auth user format
by Wilberth Perez 15 Dec '10

15 Dec '10

My configuration file have this lines: # doveconf | grep user auth_anonymous_username = anonymous auth_master_user_separator = auth_socket_path = auth-userdb auth_ssl_username_from_cert = no auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_username_format = %Lu <-----(in version 1.2.10 this work fine) auth_username_translation = default_internal_user = dovecot default_login_user = dovenull director_user_expire = 15 mins login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_max_userip_connections = 10 in this new version, my user authentication fails: Debug: shadow(wperez(a)mydomain,1.2.3.4): lookup Info: shadow(wperez(a)mydomain,1.2.3.4): unknown user auth: Debug: client out: FAIL 2 user=wperez@mydomain in my server only exists the user wperez, but dovecot uses the user "wperez@mydomain" in this new version auth format changes? Thank you.

3 2

[Dovecot] Trying to populate dovecot with outlook contacts
by Spyros Tsiolis 15 Dec '10

15 Dec '10

Hello, What the subject says. I am trying, that is. OK, here's the story. Users very lazy. Don't want to write down their contact details from scratch. Here's what I thought : migrate (export?) contacts from outlook to mozilla thunderbird. Then find a way to make thunderbird "talk" to dovecot, so that the latter can import the contact details from mozilla tb. Any ideas ? Will it work ? Am I ranting ? :-) Thank you all, s. ---- "I merely function as a channel that filters music through the chaos of noise" - Vangelis

2 2

[Dovecot] Problem after upgrade dovecot v2.0.8
by Wilberth Perez 15 Dec '10

15 Dec '10

Hello, upgrade Dovecot from v1.2.10 to v2.0.8, after build a new configuration file following instructions of http://wiki2.dovecot.org/Upgrading/2.0 run dovecot I get this: auth: Error: Fatal: Dovecot version mismatch: Master is v2.0.8, dovecot-auth is v1.2.10 (if you don't care, set version_ignore=yes) log: Error: service(auth): child 3389 returned error 89 (Fatal failure) master: Error: service(auth): command startup failed, throttling Did any SSL configuration is missing? I am currently authenticating with dovecot and postfix. Any knows , how could i solved this problem? Thanks.

3 2

Re: [Dovecot] Question about "slow" storage but fast cpus, plenty of ram and dovecot
by Stan Hoeppner 15 Dec '10

15 Dec '10

Patrick Westenberg put forth on 12/11/2010 5:12 AM: > Stan Hoeppner schrieb: > >> So, either: >> >> 2. Move indexes to memory > > What steps have to be done and what will the configuration look like > to have your indexes in memory? Regarding Dovecot 1.2.x, for maildir, I believe it would be something like this: mail_location = maildir:~/Maildir:INDEX=MEMORY The ":INDEX=MEMORY" disables writing the index files to disk, and as the name implies, I believe, simply keeps indexes in memory. The docs say: "If you really want to, you can also disable the index files completely by appending :INDEX=MEMORY." My read of that is that indexing isn't disabled completely, merely storing the indexes to disk is disables. The indexes are still built and maintained in memory. Timo, is that correct? Also, due to the potential size of the index files (mine alone are 276 MB on an 877 MB mbox), you'll need to do some additional research to see if this is a possibility for you. If using a ramdisk, 100 mail boxen like mine would require ~ 27.6 GB or RAM just for the index files. This would not be logical to do or feasible given the amount of RAM required. I don't know if, or how much, storing them in RAM via :INDEX=MEMORY consumes, as compared to using a ramdisk. The memory consumption may be less or it may be more. Timo should be able to answer this, and give a recommendation as to whether this is even a sane thing to do. -- Stan

7 18

[Dovecot] Connection queue full on 2.0.8
by Patrick McLean 15 Dec '10

15 Dec '10

Hi, I can't find any references to this problem on 2.x. I upgraded to 2.0.8 last night, and now I am getting these errors in the logs (along with the server refusing new connections): > Dec 8 09:46:52 orford dovecot: imap-login: Disconnected: Connection queue full (no auth attempts): rip=x.x.x.x, lip=x.x.x.x, TLS > Dec 8 09:47:16 orford dovecot: imap-login: Disconnected: Connection queue full (no auth attempts): rip=x.x.x.x, lip=x.x.x.x, TLS handshaking I have unsuccessfully tried to tweak my settings to prevent this problem, and any help would be appreciated. The server has plenty of power for increasing process limits, etc. Below is the output of "dovecot -n". We have users with some _very_ large mailboxes (~400 000 messages) so some of the limits might appear excessive.: > # 2.0.8: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.35-gentoo-r5+ x86_64 Gentoo Base System release 2.0.1 > auth_cache_size = 10 M > auth_mechanisms = plain login > auth_worker_max_count = 80 > default_client_limit = 2048 > default_process_limit = 256 > default_vsz_limit = 512 M > first_valid_uid = 125 > last_valid_uid = 20000 > listen = 127.0.0.1 x.x.x.x > login_greeting = IMAP ready. > mail_location = maildir:~/Maildir > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date > mdbox_rotate_size = 10 M > namespace { > hidden = no > inbox = yes > list = yes > location = > prefix = > subscriptions = yes > type = private > } > namespace { > hidden = yes > list = no > location = > prefix = INBOX. > subscriptions = yes > type = private > } > namespace { > hidden = no > list = yes > location = maildir:/home/shared/Maildir:CONTROL=~/Maildir/control/shared:INDEX=~/Maildir/index/shared > prefix = shared. > subscriptions = no > type = public > } > passdb { > args = failure_show_msg=yes > driver = pam > } > plugin { > quota = fs:User quota:user > quota_warning2 = storage=80%% quota-warning 80 %u > sieve = ~/dovecot.sieve > sieve_dir = ~/sieve > } > protocols = imap pop3 > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0666 > user = postfix > } > } > service imap-login { > process_min_avail = 5 > } > service imap { > process_limit = 2048 > } > service managesieve-login { > inet_listener sieve_deprecated { > port = 2000 > } > } > service pop3 { > process_limit = 128 > } > ssl_cert = </etc/ssl/dovecot/imap.crt > ssl_key = </etc/ssl/dovecot/imap.key > userdb { > driver = passwd > } > verbose_proctitle = yes > protocol lda { > mail_plugins = sieve quota > } > protocol imap { > mail_max_userip_connections = 10 > mail_plugins = " quota imap_quota acl" > } > protocol sieve { > mail_max_userip_connections = 10 > } > protocol pop3 { > mail_max_userip_connections = 3 > pop3_uidl_format = %u-%v > ssl_cert = </etc/dovecot/certs/pop3.pem > ssl_key = </etc/dovecot/certs/pop3.key > }

3 7

[Dovecot] question about snarf plugin in dovecot 2
by Tom Lieuallen 15 Dec '10

15 Dec '10

I'm trying to get the snarf plugin working with dovecot 2.0.7. Specifically, I want to use the UW-IMAP style optional snarfing. I'm looking at the wiki2 documentation. The first question is whether the UW-IMAP optional snarfing will require any changes to the mail_location. The first section suggests (but doesn't specifically state, which I'd propose be clarified) that mail_location be updated to point at ~/mbox for INBOX. However, with the optional snarfing, sometimes inbox will be at /var/mail and for some users, it'll be ~/mbox. What, if anything, do I do to mail_location? Does it matter where (in which config file) the plugin block is placed? I put all of my snarf configuration in 10-mail.conf. It's not working; not snarfing and not reading mail from ~/mbox (how would it, I have yet to tell it to). The following are excerpts from 10-mail.conf mail_location = mbox:~/mail:INBOX=/var/mail/%u:INDEX=/a2/imap-index/%u .... namespace { type = private separator = / prefix = inbox = yes } .... namespace snarf { prefix = /snarf separator = / location = mbox:/private/dovecot/var/run/dovecot/empty:INBOX=/var/mail/%u:INDEX=MEMORY list = no hidden = yes } plugin { snarf = /snarf/INBOX mbox_snarf = ~/mbox } Thank you BTW, the dovecot-2.0.7/docs/wiki appear to be from wiki1, not wiki2... :-) Tom Lieuallen Oregon State University

3 5

[Dovecot] After-delivery sieve processing
by Daniel L. Miller 14 Dec '10

14 Dec '10

Is it possible to run sieve against an existing mailbox? My application: I've got a mailbox that stores status messages from multiple sites. It's easier to check up on recent events by having them all in one folder. However, after I've read them, I'd like to have them archived to individual folders per site. I currently have a sieve script that uses "fileinto" to sort the mails - but I'm thinking of removing it from deliver if I can run it as a manual job later. I suppose another method would be to duplicate the mails on delivery into both the main folder and the per site folders, then delete after I've read them - but for whatever reason that strikes me as inelegant. -- Daniel

1 0

[Dovecot] Migration from UW-IMAP
by Daniel Senie 14 Dec '10

14 Dec '10

I am attempting to test out dovecot on a server on a separate IP address from the live, functioning UW-IMAP. I am having mixed results with dovecot. An entirely new account that's never been used with UW-IMAP seems to work fine, but that's really not the point of the exercise. If I try changing over an existing account to use dovecot, I get a variety of issues. Testing with Apple Mail.app, if I synchronize the account, the INBOX stops displaying. So off to plan B, and debug via command line commands. I tried connecting to Dovecot. It was able to list the mailboxes for me. I asked for status on INBOX. Sometimes I get an error back in the IMAP stream, sometimes not. Either way, the log shows complaints about creating mail/.imap and below (we use mbox format, plus /var/mail/%u for inbox). I have active namespace compatibility recommended by the Wiki so that clients specifying "mail/" and clients not specifying an imap path both work. With the test account, I proved this functionality is working. At this point I clearly have some issues, and could use some help figuring out what to ask for help with, i.e. how to proceed to debug this without damaging the existing UW-IMAP setup in the process. The goal is to cut over to dovecot once I can be sure it really is working compatibly, but until then I have a large user base and can't blow everything up. And yes, I really, truly have RTFM (i.e. read the Wiki, the troubleshooting pages, the migration pages).

2 2