- dovecot - dovecot.org

[Dovecot] wish now I'd not upgraded...
by Stan Hoeppner 19 Feb '10

19 Feb '10

Upgraded from Debian Dovecot 1.0.15 to Debian Dovecot 1.2.10-1~bpo50+1. I use Postfix local delivery to and Dovecot mbox. As per upgrade directions, I stopped dovecot processes and deleted all dovecot.index.cache files in /home/%user/mail/.imap. Performed upgrade to 1.2.10-1~bpo50+1. Modified new dovecot.conf for my environment. Started dovecot. Problem: Instantly noticed in TB 3.0.1 Win32 that all emails in all folders were marked as unread. Stopped TB, stopped dovecot, deleted *all* files in /home/%user/mail/imap/ so indexes and caches could be rebuilt from scratch. Started dovecot, started TB. Same problem. Then I got ugly, stopped TB and dovecot, deleted all ~.imap/ files *and* deleted *all* TB cache and index files with a time stamp of today. Restarted dovecot, restarted TB. Same damn problem. I sit hit right clicking folder after folder and selecting "mark as read", only to see all the emails in the folder go "read" and then within seconds go back to marked as unread (bold). Opening messages one at a time and moving to the next doesn't even keep them marked as read. WTF is going on? Why won't they stay marked as read? I've got over 25,000 emails in these folders and I get a few hundred list mails a day. I really need to get this read/unread business straightened out. What the heck am I missing? Is this a bug in the Debian backport? Good thing I have no hair or I'd have pulled half of it out by now... -- Stan

7 16

[Dovecot] quota plugin + setting in "protocol" or "lda"
by maximatt 19 Feb '10

19 Feb '10

hi... which are the diference to configure quota plugin when LDA is dovecot: these setting: protocol imap { : mail_plugins = quota imap_quota : } protocol pop3 { : mail_plugins = quota : } .vs. these setting: protocol lda { : mail_plugins = quota : } Note: - dovecot version is 1.2.0 thanks in advance!! -- Salu2 ;)

2 1

[Dovecot] quota problem
by Andre Hübner 19 Feb '10

19 Feb '10

dovecot 1.0.15 Hello, i try to set quota settings for my users. currentyl i use a mysql table for auth process and now i want to add quotasettings for each individual user. at the moment i have the problem that only global quota is effective and no userquota which is stored in usertable. This is my mysql-usertable: login varchar(255) password varchar(64) home varchar(128) uid int(11) gid int(11) quota_kb varchar(10) active char(1) In my main-dovecot.conf i have quota/imap_quota activated for pop/imap and protocol lda This is the auth-section which contains passdb/userdb auth default { mechanisms = plain login passdb sql { args = /etc/dovecot-sql.conf } userdb sql { args = /etc/dovecot-sql.conf } user = root socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } socket listen { client { path = /var/run/dovecot/auth-master mode = 0755 user = nobody } } } SQL-queries in /etc/dovecot-sql.conf (connection itselfs is ok, auth per mysql is working already) password_query = SELECT login as user, password, home as userdb_home, uid as userdb_uid, gid as userdb_gid FROM mail_users WHERE login = '%u' AND active='Y' user_query = SELECT login as user, home, uid, gid, concat('dirsize:storage=', quota_kb) AS quota FROM mail_users WHERE login = '%u' I think there is something missing in my conf but have no idea what it could be. I need a little hint please. Thanks, Andre

4 11

[Dovecot] auth processes
by Stan Hoeppner 19 Feb '10

19 Feb '10

With 1.0.15 my configuration I a single dovecot-auth process, which is what I want now. Since upgrading to 1.2.10 I have two such processes: root 16992 16990 0 Feb15 ? 00:00:00 dovecot-auth root 16997 16990 0 Feb15 ? 00:00:00 dovecot-auth -w I can't seem to tweak dovecot.conf to get this down to one auth process again. I've tried setting each of these below to 0, which resulted in either none, or one auth process. In the case of the one auth process, T-Bird wasn't working correctly, although it presented no pop up or other errors. When I'd click an IMAP folder it would just show whitespace and never pull up the emails. auth_worker_max_count = # Number of authentication processes to create count = This is an extremely low volume host, and I'm an efficiency freak. I don't like having "unnecessary" processes running if it is at all possible to avoid it. Given my IMAP user load, I know for a fact that I should only need one auth process, and for that matter, given my load, running all the dovecot processes from inetd is even a valid option, although I've not yet attempted that. Any ideas? Thanks. -- Stan

3 7

[Dovecot] dovecot and firstname.initial.lastname mbox format archive
by Wilko Bulte 19 Feb '10

19 Feb '10

hi Today I have been in a puzzling fight with 2 dovecot versions that I would like to ask some comments on. The situation is this: - I have a considerable mail archive in mbox format (yes, I know, but that is what I have..). - My mail reader is mutt 1.5.20 by the way. - Some of these mbox files have names like firstname.initial.lastname Note the . seperating the parts of the email-ers name. - On my old system I have dovecot v 1.1.7 which has always worked flawless - On my new system I have dovecot v 1.2.8 which refuses to handle these dot-seperated files. I get the somewhat familiar "Mailbox doesn't allow inferior mailboxes". On a not-previously-existing mbox dovecot 1.2.8 produces the directory hierarchy thing: firstname -> initial -> lastname - I am using the same dovecot.conf on v.1.1.7 and v.1.2.8 Can anyone tell me if v1.2.8 no longer is able to do what v1.1.7 did? And what I dearly would like to get working :-( And if it can, what should I put in dovecot.conf to make that happen? thanks, Wilko -- wilko(a)FreeBSD.org

2 8

[Dovecot] 2nd REPOST: mbox vs maildir
by Ashley M. Kirchner 18 Feb '10

18 Feb '10

I'm going to assume this is just not possible, or that no one has an answer, which would lead me back to uw-imap since it does work as-is. So I'll post it again, hoping that there is a solution for this setup and that folks have just been too busy to help think about it and/or help come up with a possible solution. ----- Ignoring my previous message just for a second, I realized that my config wasn't correct. First the layout: ~mail/ ~mail/Drafts ~mail/Ashley-Feb09 ~mail/Others-Feb09 ~mail-Archives/ ~mail-Archives/2009/ ~mail-Archives/2009/Ashley/ ~mail-Archives/2009/Ashley/Ashley-Dec09 ~mail-Archives/2009/Ashley/Ashley-Nov09 ~mail-Archives/2009/Ashley/Ashley-Oct09 So I (now) have this for namespaces: namespace private { separator = / prefix = "mail/" location = mbox:~/mail:INBOX=/var/mail/%u inbox = yes hidden = no list = yes # for v1.1+ } namespace private { separator = / prefix = "mail-Archives/" location = maildir:~/mail-Archives:LAYOUT=fs inbox = no hidden = no list = yes subscriptions = yes } But when I'm in Thunderbird and I try to subscribe to anything that falls inside of ~/mail-Archives/ it won't work. I can browser all the way down to the folder, but I can't see anything within that folder. For example, consider the full path to the following 'Ashley-Dec09' mailbox: ~mail-Archives/2009/Ashley/Ashley-Dec09 In Thunderbird, when I hit 'Subscribe' I can browse down to '2009' and I can see 'Ashley', but I can't drill down into it and subscribe to 'Ashley-Jan09'. What am I missing here?

3 13

[Dovecot] LDAP as password database - some problems / suggestions
by Stefan Palme 18 Feb '10

18 Feb '10

Hi all, Using dovecot-1.2.6, I use dovecot with an LDAP backend for user authentication. In general this works ok, but I have some issues with this... In LDAP, I have users like this: dn:cn=user1,ou=users,dc=kapott,dc=org dn:cn=user2,ou=users,dc=kapott,dc=org etc. When authenticating users, I explicitely want to use the AUTH_BIND feature (and NOT lookup passwords). My problem: not ALL users from the LDAP system should be allowed to use the IMAP server. Currently, I have defined an auth_bind_userdn of "cn=%u,ou=users,dc=kapott,dc=org" in dovecot-ldap.conf, but with this, user1 AND user2 could login (but I don't want user2 to be able to use dovecot). Because the LDAP system is used in a larger environment, it is NOT possible to re-arrange the users like this: cn=user1,ou=dovecot,ou=users,dc=kapott,dc=org cn=user2,ou=not_dovecot,ou=users,dc=kapott,dc=org So my question: are there any plans to support group-based LDAP authentication? For several other application, I have something like this: dn:cn=dovecot,ou=groups,dc=kapott,dc=org objectclass:groupOfNames member:cn=user1,ou=users,dc=kapott,dc=org So I can define groups of user accounts - one group per application. A nice solution for this in dovecot would be, if I could "mix" password lookup and authentication bind: First, a search query should be used to find a valid DN to bind as. In my case, the search query could look like this: base="ou=groups,dc=kapott.org" filter="(&(cn=dovecot)(member=cn=%u,ou=users,dc=kapott,dc=org))" result_attribute="member" After finding a DN this way (via attribute "member"), I want to use auth_bind to use this DN for password verification... Any hints how to solve this? Any plans to support this in the future? Thanks and regards -stefan-

4 7

[Dovecot] improved create dovecot certificate script
by Roger Oot 18 Feb '10

18 Feb '10

If anybody is interested, which they are probably not, here is an improved and more rigorous version of mkcert.sh #! /bin/sh #*****************************************************************************# #| #| file : /root/apps/share/sh/create_dovecot_certificate #| #*---------------------------------------------------------------------------*# BELL="\007" DOVECOT_DIR="${DOVECOT_DIR-/var/lib/dovecot}" OPENSSL="${OPENSSL-openssl}" OPENSSL_CONF="${OPENSSL_CONF-/etc/dovecot/dovecot-openssl.cnf}" #.............................................................................# certificates_dir="${DOVECOT_DIR}/certificates" echo="/bin/echo -e" error="${BELL}%ERROR -" #*---------------------------------------------------------------------------*# check_directory () { directory="${1}" #.............................................................................# if [ $ ! \( -d "${directory}" $ \) ] then mkdir -m 700 "${directory}" 2> /dev/null status=${?} if [ ${status} -ne 0 ] then ${echo} "${error} directory ${directory} cannot be created!" >&2 exit 2 fi chgrp dovecot "${directory}" fi #.............................................................................# return 0 } #*---------------------------------------------------------------------------*# check_executable () { executable="${1}" #.............................................................................# if [ $ ! \( -x "`which ${executable} 2> /dev/null`" $ \) ] then ${echo} "${error} executable ${executable} could not be found!" >&2 exit 1 fi #.............................................................................# return 0 } #*---------------------------------------------------------------------------*# check_exists () { file="${1}" description="${2}" #.............................................................................# if [ -e "${file}" ] then test "${description}" = "public certificate" && echo ${echo} \ "${error} ${description} file ${file} already exists!" >&2 test "${description}" = "public certificate" && \ show_certificate "${certificate}" exit 6 fi #.............................................................................# return 0 } #*---------------------------------------------------------------------------*# check_file () { file="${1}" description="${2}" #.............................................................................# if [ $ ! \( -e "${file}" $ \) ] then ${echo} "${error} ${description} file ${file} does not exist!" >&2 exit 3 fi if [ $ ! \( -f "${file}" $ \) ] then ${echo} "${error} ${description} ${file} is not a file!" >&2 exit 4 fi if [ $ ! \( -s "${file}" $ \) ] then ${echo} "${error} ${description} file ${file} is empty!" >&2 exit 5 fi #.............................................................................# return 0 } #*---------------------------------------------------------------------------*# create_certificate () { configuration="${1}" directory="${2}" #.............................................................................# name="`hostname -f | tr '[A-Z]' '[a-z]' | tr '.' '_'`-dovecot" certificate="${directory}/${name}.crt" check_exists "${certificate}" "public certificate" key="${directory}/${name}.pem" check_exists "${key}" "private key" #.............................................................................# ${echo} "\nCreating new X509 certificate\n\ with configuration ${configuration}\nfor ${name} ...\n" ${OPENSSL} req -new -x509 -nodes -config "${configuration}" \ -days 365 -out "${certificate}" -keyout "${key}" status=${?} if [ ${status} -ne 0 ] then ${echo} "${error} ${OPENSSL} failed with exit status ${status}!" >&2 exit 7 fi #.............................................................................# chmod 0400 "${key}" chmod 0444 "${certificate}" #.............................................................................# return 0 } #*---------------------------------------------------------------------------*# show_certificate () { certificate="${1}" #.............................................................................# echo ${OPENSSL} x509 -in "${certificate}" -noout -dates echo ${OPENSSL} x509 -in "${certificate}" -noout -serial echo ${OPENSSL} x509 -in "${certificate}" -noout -subject echo #.............................................................................# return 0 } #*---------------------------------------------------------------------------*# check_executable "${OPENSSL}" check_file "${OPENSSL_CONF}" "openssl configuration" check_directory "${DOVECOT_DIR}" check_directory "${certificates_dir}" create_certificate "${OPENSSL_CONF}" "${certificates_dir}" #.............................................................................# exit 0 #*****************************************************************************#

1 0

[Dovecot] dovecot-sieve and ldap user
by spamvoll＠googlemail.com 18 Feb '10

18 Feb '10

hi.. im running dovecor 1.2.10 and dovecot-sieve 0.1.15 protocol lda { .. mail_plugins = sieve } plugin { ... sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } cat .dovecot.sieve require "fileinto"; if header :contains "subject" ["VIRUS"] { fileinto "VIRUS"; } else { keep; } But mails dont get moved. I use the master.cf to get postfix to use deliver dovecot unix - n n - 10 pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -d ${recipient} dovecot -n # 1.2.10: /etc/dovecot.conf # OS: Linux 2.6.18-164.10.1.el5 i686 CentOS release 5.4 (Final) protocols: imaps ssl: required login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login first_valid_uid: 10000 last_valid_uid: 10000 first_valid_gid: 10000 last_valid_gid: 10000 mail_uid: vmail mail_gid: vmail lda: postmaster_address: postmaster(a)example.com mail_plugins: sieve auth_socket_path: /var/run/dovecot/auth-master auth default: passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: passwd userdb: driver: ldap args: /etc/dovecot-ldap.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve Does the sieve plugin use the home_dir returned from the ldap ? And is it ok to use the deliver in master.cf and or do i have to set mailbox_command = /usr/lib/dovecot/deliver ?

2 1

[Dovecot] Disabling Keywords
by Tony Rutherford 18 Feb '10

18 Feb '10

Is there a correct way to tell the client we don't want, and don't support Keywords via a configuration option? If there's no configuration option, would I override "allow_new_keywords" to just return FALSE? Thanks, Tony

2 3