- dovecot - dovecot.org

[Dovecot] Public namespaces with global ACLs 1.2+
by Thomas Leuxner 18 Aug '09

18 Aug '09

Hi, I'm having trouble to get ACLs working in a more restrictive way with namespaces. I would like to grant certain users the ability to create new mailboxes in a public namespace e.g. "Public/Newsletters" etc. It works when I add the users to a ".DEFAULT" ACL file like this: user=username lrwk Anyway I'd like to limit their permissions on the Namespace "Public", or even better - being more restrictive, on "Public/Newsletters". Neither global ACL files for "Public" nor "Newsletters" nested in the global path seem to work. For now only the .DEFAULT ACL (/var/vmail/ domain/etc/acls/.DEFAULT) seems to mitigate the problem which is undesirable. dovecot -n excerpt: plugin: acl: vfile:/var/vmail/%d/etc/acls:cache_secs=300 Thanks Thomas

3 9

[Dovecot] Any dovecot-sieve 1.2.3 1.2.3-0_98 el5 x86 rpm?
by Δημήτριος Καραπιπέ ρης 18 Aug '09

18 Aug '09

Hi all Do u have by chance dovecot-sieve 1.2.3 1.2.3-0_98 el5 x86-64 rpm? I have Dovecot binary package installed and I need the binary sieve counterpart. Many thanks Dimitrios

1 0

[Dovecot] Dovecot and LDAP-Quotas
by south africa 17 Aug '09

17 Aug '09

Hi all, I have configured Dovecot as a POP/IMAP-Server in front of a Postfix-Server. Every thing works without one thing: LDAP-quotas The main-quota-rule works: quota_rule: *:storage=8M Only the LDAP-quota won't be used by Dovecot: user_attrs = msRADIUSFramedIPAddress=quota_rule=*:storage=%$k I have to use the special LDAP-field "msRADIUSFramedIPAddress" because my W2003 domain controller don't have a regular quota field. This LDAP-field is the only "free integer" LDAP-field. Could anyone please give me a hint? Greetings Paul #dovecot -n # 1.2.3: /etc/dovecot.conf # OS: Linux 2.6.18-128.4.1.el5 x86_64 CentOS release 5.3 (Final) ext3 log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log protocols: pop3 pop3s imap imaps listen(default): 123.456.789.71 listen(imap): 123.456.789.71 listen(pop3): 123.456.789.72 ssl_listen(default): ssl_listen(imap): ssl_listen(pop3): 123.456.789.72:995 ssl_ca_file: /etc/pki/dovecot/certs/pop_core_uk/trustcenter_intermediate.crt ssl_cert_file: /etc/pki/dovecot/certs/pop_core_uk/server.crt ssl_key_file: /etc/pki/dovecot/private/pop_core_uk/server.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: maildir:/home/vmail/%Lu/Maildir/ mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh lda: debug: yes postmaster_address: postmster(a)core.uk hostname: smtp.core.uk mail_plugins: quota quota_full_tempfail: yes log_path: /var/log/dovecot-deliver.log log_timestamp: %b %d %H:%M:%S rejection_reason: Ihre Nachricht an <%t> wurde automatisiert abgewiesen:%n%r auth default: mechanisms: plain login username_translation: @_._ verbose: yes debug: yes debug_passwords: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: passwd userdb: driver: static args: uid=500 gid=500 home=/home/vmail/%Lu allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: postfix plugin: quota: maildir:User quota quota_rule: *:storage=8M quota_warning: storage=90%% /usr/local/bin/quota-warning.sh 90 quota_warning2: storage=75%% /usr/local/bin/quota-warning.sh 75 dovecot-ldap.conf ----------------- hosts = 123.456.789.123 123.456.789.124 base = OU=one,OU=two,OU=London,OU=GB,OU=User Accounts,DC=three,DC=core,DC=uk ldap_version = 3 auth_bind = yes auth_bind_userdn = %u(a)core.uk user_filter = (&(objectClass=person)(cn=%u)) user_attrs = msRADIUSFramedIPAddress=quota_rule=*:storage=%$k _____________________________________________________________ Get your FREE TheDoghouseMail email address at http://www.thedoghousemail.com

2 1

[Dovecot] BUG: mbox_snarf causes message duplication when two IMAP connections are open
by Robert Lazzurs 17 Aug '09

17 Aug '09

Hello, I have used dovecot to replace an ageing wu-imap installation using the mbox_snarf plugin however I have noticed that when we have more than one client checking the INBOX we then have messages being duplicated in the INBOX. Below is the configuration used as requested in the bug report page. I have confirmed that the duplicates are being caused by dovecot by doing an strace of both processes that have both the INBOX (/mail_home/$username/INBOX) and mail spool file (/var/spool/dovecot/$username) open and delivering a new message through exim to the mail spool file in /var/spool/dovecot/$username. I then see in strace first one process check the spool and copy the message over and then the other processes do the same. If anyone requires any further information to confirm this bug please let me know. Kind regards. Version: 1.2.1 [root@wine ~]# dovecot -n # 1.2.1: /etc/dovecot.conf # OS: Linux 2.6.18-128.el5 i686 CentOS release 5.3 (Final) ext3 protocols: imap listen: *:10143 *:143 ssl: no login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_access_groups: accounts agen directors extsw fax ftpguest imapshared operat ions personnel sysadmin mail_privileged_group: mail mail_location: mbox:/mail_home/%u/:INBOX=/var/spool/dovecot/%u mail_debug: yes mbox_dirty_syncs: no mbox_lazy_writes: no mail_plugins: mbox_snarf imap_client_workarounds: tb-extra-mailbox-sep namespace: type: shared prefix: shared/ location: mbox:/mail_home/imapshared/ list: yes namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: mail/ hidden: yes list: no subscriptions: yes namespace: type: private separator: / prefix: ~/mail/ hidden: yes list: no subscriptions: yes namespace: type: private separator: / prefix: ~%u/mail/ hidden: yes list: no subscriptions: yes auth default: passdb: driver: pam userdb: driver: passwd plugin: mbox_snarf: /mail_home/%u/INBOX

3 6

[Dovecot] More Migration Questions
by Richard Hobbs 17 Aug '09

17 Aug '09

Hello, I was on here a month or two ago asking lots of questions about migrating from uw-imapd/qpopper/mbox to dovecot/maildir. I am now at the stage where i'm trying to convert all my emails, but i have a few questions... Where should i convert my mbox mailboxes into? "/home/username/Maildir/" or "/somewhere/maildirs/"? Does it actually matter? Is there a standard location that they *should* go? I've tried converting them into "/somewhere/maildirs/username/", but then i found a dovecot page that says they are usually stored in "/home/username/Maildir" so now i don't know where to put them! Also, having converted the mbox files into maildir files, i do seem to have one email per file, as intended, but the files have names like "1250253965.000586.mbox,S=8167,W=8427:2,S". Should they have the word "mbox" in their filename if they are maildir files? Finally, it appears that our existing IMAP users (all mbox) have mailboxes stored simply in their home directory, not necessarily inside the "~/mail/" directory - is this going to be a problem? The command i'm using to convert is this one: ./migrateuser.sh username /home/username /vol2/maildirs/username This script (and the latest mb2md.py that goes with it, to preserve msg IDs) were obtained from here: http://wiki.dovecot.org/Migration/MailFormat The stage i'm at with the server overall is that uw-imapd and qpopper have been completely removed, exim is currently setup to deliver via it's own method into the mbox files in /var/spool/mail but the exim service is stopped because i'm migrating, and dovecot 1.1 is installed but stopped, and has had no configuration done to it yet whatsoever. So... any advice? Thanks in advance! Richard. -- Richard Hobbs (IT Specialist) Toshiba Research Europe Ltd. - Cambridge Research Laboratory Email: richard.hobbs(a)crl.toshiba.co.uk Web: http://www.toshiba-europe.com/research/ Tel: +44 1223 436999 Mobile: +44 7811 803377

2 6

[Dovecot] install sieve without any dovecot sources
by Δημήτριος Καραπιπέ ρης 17 Aug '09

17 Aug '09

Hi all I have dovecot 1.1.16 (dovecot-1.1.16-0_94.el5 x86-64) installed on a Red Hat Enterprise v.5. I am already using Dovecot's deliver for virtual users local delivery and need to install the cmusieve plugin for the filtering capabilities. I don't have any sources, since I installed Dovecot from a binary package. Is there any way to install the cmusieve plugin? Thanks in advance Dimitrios Karapiperis

1 0

[Dovecot] Crash in v1.2.3: istream.c: assertion failed on line 99
by Phillip Macey 17 Aug '09

17 Aug '09

Hi, I have a couple of people bumping into an issue with their imap process crashing - from the users perspective, their mail client (thunderbird) just stops recieving new mail. It still seems to be possible for them to read their mail using squirell mail. When it crashes, it leaves behind a log message like this on the server: Aug 12 15:52:25 fury dovecot: imap-login: Login: user=<zhi>, method=PLAIN, rip=10.8.5.15, lip=10.10.0.26 Aug 12 15:52:25 fury dovecot: IMAP(zhi): Panic: file istream.c: line 99 (i_stream_read): assertion failed: ((size_t)ret+old_size == _stream->pos - _stream->skip) Aug 12 15:52:25 fury dovecot: IMAP(zhi): Raw backtrace: imap [0x49ddc0] -> imap [0x49de23] -> imap [0x49d4a6] -> imap [0x4a252e] -> imap [0x4a4691] -> imap(i_stream_read+0x48) [0x4a23f8] -> imap(i_stream_read_data+0x28) [0x4a2558] -> imap [0x4ab22e] -> imap(o_stream_send_istream+0x2e) [0x4aa63e] -> imap(maildir_save_continue+0x32) [0x443d12] -> imap(mail_storage_copy+0x6a) [0x462a1a] -> imap(maildir_copy+0x5e) [0x441d2e] -> imap(cmd_copy+0x1fe) [0x41a94e] -> imap(cmd_uid+0x78) [0x41f8d8] -> imap [0x42053c] -> imap [0x4205f2] -> imap(client_handle_input+0x3f) [0x42072f] -> imap(client_input+0x5f) [0x42127f] -> imap(io_loop_handler_run+0xf8) [0x4a5b08] -> imap(io_loop_run+0x1d) [0x4a4c1d] -> imap(main+0x620) [0x428b80] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x353e41d974] -> imap [0x4198f9] Aug 12 15:52:25 fury dovecot: dovecot: child 14759 (imap) killed with signal 6 (core dumps disabled) I was able to fairly reliably trigger the same behaviour myself by attempting to move a bunch (thousands) of emails in my account using thunderbird - I dont know exactly what it is that triggers the crash though. I tried enabling core dumps using 'ulimit -c unlimited' and messing around with some environment variables to stop the startup scripts from forcing core dumps off again (DAEMON_COREFILE_LIMIT=18446744073709551615 /etc/init.d/dovecot restart). After doing that, I do not see anything in the logs any more - but I still seem to be having problems moving the emails around in my account. It would seem that it is still broken but Im just not getting any logs telling me so. There don't seem to be any core dumps sitting around anywhere either. My 'dovecot -n' is: # 1.2.3: /etc/dovecot.conf # OS: Linux 2.6.18-128.1.16.el5.centos.plus x86_64 CentOS release 5.3 (Final) xfs syslog_facility: local0 shutdown_clients: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login max_mail_processes: 1024 first_valid_uid: 300 mail_location: maildir:/u/%u/Maildir mail_drop_priv_before_exec: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 lda: postmaster_address: example(a)example.com auth default: mechanisms: gssapi gss-spnego plain krb5_keytab: /etc/opt/quest/vas/imap.keytab gssapi_hostname: $ALL passdb: driver: passwd-file args: /etc/dovecot.deny # empty file deny: yes passdb: driver: pam args: dovecot userdb: driver: passwd userdb: driver: static args: home=/u/%u -- Thanks, Phill Macey

3 12

[Dovecot] How to disable system users from receiving mail?
by Paul H Park 17 Aug '09

17 Aug '09

I know that login can be disable for system users and groups, but how do I refuse email for system groups? It's a bit of a security/maintenance irritation - I don't want to check for such spam mail, since that is possible. Thanks for any help!! Answer preferably given, so that I can configure it through webmin please.

3 2

[Dovecot] can't deliver with Kerberos username
by Nikolay Shopik 16 Aug '09

16 Aug '09

I've been trying to use Kerberos and PLAIN text file for authentication. I've setup deliver in postfix master.cf and make sure correct username are expanded but deliver is always told me "user unknown". I can logon into mailbox using Kerberos w/o problems and can send emails. Looks like Dovecot lookup up passwd files and not finding users which are in Kerberos realm. # 1.0.15: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log protocols: imap ssl_cert_file: /etc/postfix/new_chained.crt ssl_key_file: /etc/postfix/mail.pem login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_greeting_capability: yes mail_location: maildir:/var/mail/store/%u dotlock_use_excl: yes maildir_copy_with_hardlinks: yes auth default: mechanisms: PLAIN CRAM-MD5 GSSAPI passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=vmail gid=vmail home=/var/mail/store/%u socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 438 user: root group: root plugin: sieve: /var/mail/store/%u/sieve

3 7

[Dovecot] Listing shared mailboxes with a domainpart
by Mathias Tausig 16 Aug '09

16 Aug '09

Hy! I am currently configuring a new mailserver using postfix and dovecot 1.2.1. The filesystem strucutre in my spool directory is user1/ user2/ domain/info/ domain/office/ user1 and unser2 are ordinary users mailboxes, the latter two contain the virtual mailboxes for info@domain and office@domain as created by postfix. I want these virtual mailboxes (all of them are in maildir format) to be shared to certain real users. I configured a shared namespace: namespace shared { separator = / prefix = shared/%%d/%%n/ location = maildir:/var/spool/vmaildir/%%d/%%n/ #I tried ths as well # prefix = shared/%%u/ # location = maildir:/var/spool/vmaildir/%%u/ hidden = no subscriptions = no list = yes inbox = no } Then I configured a dictionary to list the folders, as described in the wiki: plugin { acl_shared_dict = proxy::acl } dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf } where /etc/dovecot/dovecot-dict-sql.conf holds map { pattern = shared/shared-boxes/user/$to/$from table = virtual_user_shares value_field = dummy fields { from_user = $from to_user = $to } } The database table consists of +-------------+------------+-------+ | from_user | to_user | dummy | +-------------+------------+-------+ | info@domain | user1 | 1 | +-------------+------------+-------+ But when I login as user1 I can neither see nor subscribe to the info@domain mailbox. In the "flat" case (sharing the user2 mailbox to user1), this setup works. I am pretty clueless how to go on. cheers Mathias

2 3