- dovecot - dovecot.org

[Dovecot] courier-imap to dovecot-imap migration: missing TLS_TRUSTCERTS feature
by Uffe Jakobsen 10 Feb '11

10 Feb '11

Hi, I'm attempting an one-to-one migration from courier-imap to dovecot-imap. current state: Imap-server has a self signed certificate Every client/user has a self signed client certificate that is used for SSL/TLS client authentication. All certificates are self signed "standalone" cerfificates - no CA hierarchy/structure is made. With courier-imap we could just put every client certificate into a trusted cert file (or hashed directory for a larger number of clients) and courier-imap would check that through TLS_TRUSTCERTS. I would like to keep the current appproach and avoid the whole mini CA setup - that way I can also avoid reissuing new certs to all existing users. Question: can a similar setup be achieved with dovecot-imap ? I've already made numerous attempts with no luck. As far as I can see dovecot-imap does not seem to implement the concept of checking trusted (self signed standalone client) certs - even though it is based on openssl like courier-imap is - but I may be wrong here. I'm using dovecot-2.0.7 (from ports) on FreeBSD Thanks in advance. Kind regards Uffe Jakobsen

2 1

[Dovecot] dovecot not delivering emails in the right folder
by paulino＠calderonpale.com 10 Feb '11

10 Feb '11

Hello everyone, I'm having trouble getting postfix + dovecot to work correctly. It seems like Postfix is receiving and delivering the emails correctly but dovecot is placing/looking for them in the wrong folder therefore the clients aren't receiving any new emails. I switched from courier and followed a tutorial found here: http://library.linode.com/email/postfix/dovecot-mysql-debian-5-lenny Dovecot's log: deliver(adomain.com/test/@adomain.com): 2011-02-04 21:48:04 Info: Module loaded: /usr/lib/dovecot/modules/lda/lib90_cmusieve_plugin.so deliver(adomain.com/test/@adomain.com): 2011-02-04 21:48:04 Info: auth input: adomain.com/test/@adomain.com deliver(adomain.com/test/@adomain.com): 2011-02-04 21:48:04 Info: auth input: uid=5000 deliver(adomain.com/test/@adomain.com): 2011-02-04 21:48:04 Info: auth input: gid=5000 deliver(adomain.com/test/@adomain.com): 2011-02-04 21:48:04 Info: auth input: home=/home/vmail/adomain.com/adomain.com/test/ deliver(adomain.com/test/@adomain.com): 2011-02-04 21:48:04 Info: maildir: data=/home/vmail/adomain.com/adomain.com/test/ deliver(adomain.com/test/@adomain.com): 2011-02-04 21:48:04 Info: maildir: root=/home/vmail/adomain.com/adomain.com/test, index=/home/vmail/adomain.com/adomain.com/test, control=, inbox= deliver(adomain.com/test/@adomain.com): 2011-02-04 21:48:04 Info: cmusieve: Using sieve path: /home/vmail/globalsieverc deliver(adomain.com/test/@adomain.com): 2011-02-04 21:48:04 Info: cmusieve: Executing script /home/vmail/globalsievercc deliver(adomain.com/test/@adomain.com): 2011-02-04 21:48:04 Info: msgid=<AANLkTimZi7pD2eSFNipHtmS5HZVstk9UF6kjWEyqynz-(a)mail.gmail.com>: saved mail to INBOX It seems like is using a wrong folder value since it should be using /home/vmail/adomain.com/test. Another odd thing is that postfix is replacing the email address with /folder/user(a)adomain.com. Postfix after receiving an email: 3:48:04 domain postfix/smtpd[29365]: 8FDC1A339: client=mail-yx0-f169.google.com[209.85.213.169] Feb 5 03:48:04 domain postfix/cleanup[29369]: 8FDC1A339: message-id=<AANLkTimZi7pD2eSFNipHtmS5HZVstk9UF6kjWEyqynz-(a)mail.gmail.com> Feb 5 03:48:04 domain postfix/qmgr[27253]: 8FDC1A339: from=<xxx(a)gmail.com>, size=1815, nrcpt=1 (queue active) Feb 5 03:48:04 domain postfix/pipe[29370]: 8FDC1A339: to=<adomain.com/test/@adomain.com>, orig_to=<test(a)adomain.com>, relay=dovecot, delay=0.21, delays=0.2/0.01/0/0.01, dsn=2.0.0, status=sent (delivered via dovecot service) Feb 5 03:48:04 domain postfix/qmgr[27253]: 8FDC1A339: removed My config files: main.cf ============================== alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no broken_sasl_auth_clients = yes config_directory = /etc/postfix inet_interfaces = all inet_protocols = all mailbox_size_limit = 0 message_size_limit = 30720000 mydestination = localhost, localhost.localdomain myhostname = adomain.com mynetworks = 127.0.0.0/8 myorigin = /etc/mailname proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $virtual_mailbox_limit_maps readme_directory = no recipient_delimiter = + relayhost = smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_tls_cert_file = /etc/postfix/cert.ca.crt smtpd_tls_key_file = /etc/postfix/cert.ca.key smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_use_tls = yes virtual_alias_domains = virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf virtual_gid_maps = static:5000 virtual_mailbox_base = /home/vmail virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf virtual_transport = dovecot virtual_uid_maps = static:5000 dovecot.conf: ====================== protocols = imap imaps log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%d/%n/Maildir mail_debug = yes disable_plaintext_auth = no ssl_cert_file = /etc/postfix/cert.crt ssl_key_file = /etc/postfix/cert.key namespace private { separator = . prefix = INBOX. inbox = yes } protocol lda { log_path = /home/vmail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master postmaster_address = postmaster(a)adomain.com mail_plugins = cmusieve global_script_path = /home/vmail/globalsieverc } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } auth default { user = root mechanisms = plain login passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb static { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } dovecot version: 1.0.15 # grep -v '^ *$#.*$\?$' dovecot-sql.conf driver = mysql connect = host=127.0.0.1 dbname=mail user=mail_admin password=xxx default_pass_scheme = CRYPT password_query = SELECT email as user, password FROM users WHERE email='%u'; Thanks, any help/pointers will be greatly appreciated.

2 1

[Dovecot] pop3 index virtual question
by Robert Schetterer 09 Feb '11

09 Feb '11

Hi @ll, Timo, on 2.0.9 i have a user reporting pop3 leaving mails on the server does not work as desired i have namespace default { # type = private separator = / prefix = "" list = yes # hidden = no subscriptions = yes } namespace virtual { # type = private prefix = "virtual/" separator = / location = virtual:/etc/dovecot/virtual:LAYOUT=maildir++ #location = virtual:/etc/dovecot/virtual hidden = yes list = no subscriptions= no } namespace real { # type = private prefix = "RealMails/" separator = / list = no hidden = yes } and pop3_uidl_format = %08Xu%08Xv before it was pop3_uidl_format = %g ( not sure what best ) # Permanently save UIDLs sent to POP3 clients, so pop3_uidl_format changes # won't change those UIDLs. Currently this works only with Maildir. #pop3_save_uidl = no my guess is that location = virtual:/etc/dovecot/virtual:LAYOUT=maildir++ isnt enough should be location = virtual:/etc/dovecot/virtual:LAYOUT=maildir++:INDEX=~/ to store/use indexes in the local maildir which is physical under /usr/local/virtual/domain/user@domain any meanings to this -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 6

[Dovecot] Using -s in "doveadm mailbox create"
by Christoph Pleger 09 Feb '11

09 Feb '11

Hello, it seems that "doveadm mailbox create" does not handle the mailbox parameters correctly if used with the "-s"-Parameter. I am using the following command in a script for adding new users: doveadm mailbox create -u "${ACCOUNT}" -s INBOX Drafts Sent Trash Spam Templates This creates mailboxes Drafts, Sent, Trash, Spam and Templates, but not INBOX. Likewise, when I omit INBOX in the command, only Sent, Trash, Spam and Templates are created, but not Drafts. With only one mailbox parameter, I get an error message about incorrect usage. When I enter the command without the "-s"-Parameter, all given mailboxes are created. As a workaround, I have to use the command without "-s" first and then call "doveadm mailbox subscribe". Regards Christoph

2 1

[Dovecot] Force STARTTLS on port 143 for !internalnetwork
by Ralf Hildebrandt 09 Feb '11

09 Feb '11

Hi! How can I force users which are connecting from OUTSIDE our newtworks to user STARTTLS on Port 143? Right now we resort to IMAPS on port 993, but an additional STARTTLS enabled login on the default port would make things easier! -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

3 5

[Dovecot] Dovecot + Solr does not index without break-imap-search?
by Jose Álvaro Domínguez Díaz 09 Feb '11

09 Feb '11

Hi folks, We are working with Dovecot 2.0.9 with Solr support and there is a thing, a little strange for us. Let me explain. We have this conf for Solr: plugin { ... fts = solr fts_solr = url=http:// solr.domain:8983/solr/ break-imap-search quota = maildir ... } With 'break-imap-search', Dovecot connects with solr, solr indexes all, searchs are fast and all works fine. BUT if we don't add 'break-imap-search', solr doesn't index anything. Logs don't report errors with debug/verbose options enabled. Somebody has any idea about this?. Thank you very much for all. Regards. -- Jose Álvaro Domínguez adominguez(a)yaco.es Yaco Sistemas S.L. http://www.yaco.es/ C/ Rioja 5, 41001 Sevilla Teléfono +34 954 50 00 57 Fax +34 954 50 09 29

2 1

[Dovecot] dsync problem
by Frank Bonnet 09 Feb '11

09 Feb '11

hello I try to convert from mbox to mdbox using dsync i get the followin error using the following command dsync mirror -u toto mbox:/user/toto:INBOX=/var/mail/toto I get this error message : mail3# dsync mirror -u toto mbox:/user/toto:INBOX=/var/mail/toto dsync(root): Fatal: execvp(-u) failed: No such file or directory dsync-local(root): Error: read() from worker server failed: EOF any infos welcome thanks

3 4

[Dovecot] Permissions in shared folders
by Lukas Haase 09 Feb '11

09 Feb '11

Hi, On my mail server I want to implement shared folders for each workgroup where there are many workgroups. One way would be to create a separate namespace for each workgroup. However, this does not scale well so I decided to use a single Shared mailbox and use ACLs: namespace public { separator = . prefix = Shared. location = maildir:/var/mail/shared:CONTROL=~/Maildir/shared } Each workgroup should get a subfolder in "Shared". Until now, this works, I create .Group1, .Group2 and assign correct group permissions and ACL files. However, now a user from group1 wants to create a subfolder in his IMAP folder. Since the permissions for /var/mail/shared/.Group1 are correct (writeable to group1 and the user is member of group1 and 'k' ACL permissions are active) I would expect it to work. However, for obvious reasons, the *sub*folder is created as /var/mail/shared/.Group1.Subfolder so it is actually not a subfolder in sense of the filesystem but rather a folder inside /var/mail/shared However, the user does (and should) not have write permissions to /var/mail/shared (only to /var/mail/shared/.Group1). Is there a way to overcome this problem? Why can't dovecot just use /var/mail/shared/.Group1/.Subfolder? Is there an option to do so? It would make everything a lot easier. The one option is to make /var/mail/shared world-writeable - which is not really a good option. A second option might be to use ACLs and give each group write permissions to /var/mail/shared. However, not even this seems very "clean" to me. What is the best way to handle this? Best regards, Luke

3 9

[Dovecot] ldap: LDAP attribute used multiple times. This is currently unsupported
by Lukas Haase 09 Feb '11

09 Feb '11

Hi, I have a problem when migrating from dovecot 1.0 to dovecot 1.2 (Debian lenny to Debian squeeze). In my dovecot-ldap.conf I have: user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,uid=system_groups_user I use the last parameter for the groups which I need for shared folders. If I only use this, everything works. However, I also use LDAP as passdb with prefetch: pass_attrs = uid=user,userPassword=password,homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid,uid=userdb_system_groups_user In this configuration I get the error in the subject line that uid is used multiple times. I know, but the message is somehow "weird" since it says it is *currently* unsupported. However, it seems to me that it is not supported any more. Is this true? Is there a reason for this? How can I fix this problem? Until now my shared folders do not works anymore because the group memberships are not assigned any more because of the missing system_groups_user parameter. Best regards, Luke

2 4

[Dovecot] critical feature from version 1 not migrated to version 2 = authentication configuration database per IP
by DaLiV＠apollo.lv 09 Feb '11

09 Feb '11

not possible make operation with dovecot version 2.x as was possible in version 1.x: requisites description: connect to dovecot service on IP1 - dovecot must serve users that related to domain1 located in database1 connect to dovecot service on IP2 - dovecot must serve users that related to domain2 located in database2 login must be with username that form not as "user@domain" but simple "user" databases may contain identical username, but they have different passwords existing version 1 config file, that allow such configuration: -------- /etc/dovecot.conf BEGIN ---------------- server mail.domain1.tld { protocols = imaps pop3s pop3 ssl_cert_file = /etc/pki/cert1.pem ssl_key_file = /etc/pki/cert1.key listen = 123.123.123.1 ssl_listen = 123.123.123.1 default_mail_env = mbox:/tmp:INBOX=/var/mail/domain1.tld/%n:INDEX=MEMORY pop3_uidl_format = %08Xu%08Xv auth default { mechanisms = plain passdb ldap { args= /etc/dovecot-ldap.conf.domain1.tld1 } userdb ldap { args= /etc/dovecot-ldap.conf.domain1.tld1 } } login_process_per_connection = yes login_max_processes_count = 4 login_processes_count = 1 } server mail.domain2.tld { protocols = imaps pop3s pop3 ssl_cert_file = /etc/pki/cert2.pem ssl_key_file = /etc/pki/cert2.key listen = 123.123.123.2 ssl_listen = 123.123.123.2 default_mail_env = mbox:/tmp:INBOX=/var/mail/domain2.tld/%n:INDEX=MEMORY pop3_uidl_format = %08Xu%08Xv auth default { mechanisms = plain passdb ldap { args= /etc/dovecot-ldap.conf.domain2.tld2 } userdb ldap { args= /etc/dovecot-ldap.conf.domain2.tld2 } } login_process_per_connection = yes login_max_processes_count = 4 login_processes_count = 1 } -------- /etc/dovecot.conf END ---------------- /etc/dovecot-ldap.conf.domain1.tld and /etc/dovecot-ldap.conf.domain2.tld refers to different ldap databases

2 2