August 2009 - dovecot

[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

[Dovecot] Operation not permitted
by André Labuschagné 16 Aug '09

16 Aug '09

Hi all, Slowly but surely moving forward, I hope... I get the following error (in the maillog file) after I've installed Managesieve: *Aug 13 10:13:52 li73-31 dovecot: deliver(andre at paranoidandroid.co.za): Fatal: setgid(501(paranoidandroid)) failed with euid=104(vmail), gid=106(vmail), egid=106(vmail): Operation not permitted* /Does anybody know what this means and how to fix it?/ Don't know if it has anything to do with sieve (I've changed the /usr/etc/dovecot.conf file from mail_plugins = cmusieve to mail_plugins = sieve) My config is below: dovecot config: ---------------------- # 1.2.1: /usr/etc/dovecot.conf # OS: Linux 2.6.18.8-x86_64-linode1 x86_64 CentOS release 5.3 (Final) protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/pki/paranoidandroidCA/server.crt ssl_key_file: /etc/pki/paranoidandroidCA/server.key login_dir: /usr/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_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/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: mechanisms: plain login cram-md5 ntlm passdb: driver: sql args: /etc/dovecot/dovecot_sql_passdb.conf userdb: driver: sql args: /etc/dovecot/dovecot_sql_userdb.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /usr/var/run/dovecot/auth-master mode: 384 user: vmail postfix config: -------------------- alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 header_checks = regexp:/etc/postfix/header_checks html_directory = no inet_interfaces = all local_recipient_maps = $alias_maps $virtual_mailbox_maps unix:passwd.byname mail_owner = postfix mailq_path = /usr/bin/mailq manpage_directory = /usr/local/man mydestination = localhost mydomain = paranoidandroid.co.za myhostname = mail.paranoidandroid.co.za mynetworks_style = host myorigin = $myhostname newaliases_path = /usr/bin/newaliases queue_directory = /var/spool/postfix readme_directory = no sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail setgid_group = postdrop smtpd_recipient_limit = 500 smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot unknown_local_recipient_reject_code = 550 virtual_alias_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf virtual_mailbox_base = / virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/mysql_virtual_domains_maps.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_mailbox_maps.cf virtual_transport = dovecot master.cf: ------------- pickup fifo n - n 60 1 pickup cleanup unix n - n - 0 cleanup qmgr fifo n - n 300 1 qmgr #qmgr fifo n - n 300 1 oqmgr tlsmgr unix - - n 1000? 1 tlsmgr rewrite unix - - n - - trivial-rewrite bounce unix - - n - 0 bounce defer unix - - n - 0 bounce trace unix - - n - 0 bounce verify unix - - n - 1 verify flush unix n - n 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - n - - smtp relay unix - - n - - smtp -o smtp_fallback_relay= showq unix n - n - - showq error unix - - n - - error retry unix - - n - - error discard unix - - n - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - n - - lmtp anvil unix - - n - 1 anvil scache unix - - n - 1 scache dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -d ${recipient}

2 3

[Dovecot] Released Sieve v0.1.10 for Dovecot v1.2.2
by Stephan Bosch 15 Aug '09

15 Aug '09

Hello Dovecot users, In the last week two nasty bugs were found in the new Sieve implementation. Primarily, the include extension did not work when a compiled binary was loaded from disk. This is something that is still not tested by the test suite, giving this bug the opportunity to slip through. Also, the value matching implementation would sometimes cause a assertion failure. Other than that, various small bugs were fixed. On the more positive side, I have implemented support for the new mailbox extension (RFC 5490), which provides the means to test whether a mailbox exists. Also, it adds the :create argument to the fileinto command, which makes sure that the target folder is created before saving is attempted. Of course, this is only useful when deliver is used with the -n option. There wasn't a great need for this extension, but I could use it in the test suite and it was almost trivial to implement. In other news, I have further developed the sieve-filter command line tool. It is getting closer to a usable state, being able to filter a large number of messages in an existing mailbox, but its use is currently still very much discouraged as it tends to be very good at eating mailboxes when the user is less attentive. It needs more command line configuration options, a simulation mode to perform a dry run, and a man page that describes its use and its dangers. Changelog for Sieve v0.1.10: * Changed action execution of fileinto and keep. These changes depend on API additions in Dovecot, making this release depend on Dovecot v1.2.2 or newer. * Further developed the sieve-filter command line tool. This required a few changes to the action execution of the Sieve engine. The tool was successfully tested on folders with a few 100k spam messages. However, the commandline options are still incomplete, a man page is missing and it needs much more testing before I can recommend anyone to use this tool. + Added support for the mailbox extension. This allows checking whether a mailbox exists using the mailboxexists command and it adds the :create argument to the fileinto command to create the mailbox when it is missing. The :create feature is useless unless the Deliver LDA is run with the -n option. + Improved the testsuite with tests for message delivery. Messages stored using keep and fileinto can be fed back into the Sieve engine for verification. This includes testing of applied IMAP flags. + Updated the man pages with the new method of specifying the supported extensions using + and - (for the -x parameter of the sieve tools) + Further developed the deprecated notify extension. A dummy for the denotify command exists, meaning that its use does not cause an error anymore. - Fixed a bug in the derivation of the binary path from the script path. A bare filename would yield a path relative to root. - Fixed a bug in the value matching code. The context data now uses a proper pool in stead of the data stack. Bug reported by Jan Sechser. - Fixed assertion fail in the include extension caused by missing initialization upon binary load. This bug surfaces only for stored binaries. Bug reported by Tom Hendrikx. - Fixed include error message for failed :global include. It mentioned the wrong config parameter. - Fixed broken wiki reference in an error message of the plugin about the 'sieve' setting. - Fixed behavior of fileinto when delivering into a namespace prefix. Previous fix used the wrong storage. The release is available as follows: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.10.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.10.tar.gz.sig Have fun testing the new releases and don't hesitate to notify me when there are problems. Please include your configuration, the involved Sieve scripts and an example message in any bug or problem report when possible, so that I can easily reproduce the issue. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 8

Re: [Dovecot] Redirecting mail gives 'mail forwarding loop' to the sender - calling for sieve help
by Andrés Yacopino 15 Aug '09

15 Aug '09

Yes, the configuration seems odd or interesting as you said. The idea behind this is: - Before scripts will be use for filtering spam, when they have SPAM header. Not problem at it. - User scripts will be used for vacation messages. These are created with Squirrelmail and avelsize plugin (user interaction) - After scripts will be used for doing redirections, such as forwarding mail to a blackberry account(not problem at it) or forwarding to another user account (in the same domain, the problem is here). The reason not to put the redirections or forwarding in users scripts is to avoid users deleting redirections and have in one file all the redirections. I also try to use redirections from avelsieve plugin (0.9.9.9) and it works the forwarding but it didn't work the keep command, the mail is forwarded but the user doesn't have a copy of it. I will investigate your advice for envelope or try to use user's scripts. I didn't know about original headers, if this in RFC sieve documents? Thanks Timo and thanks Stephan for the tips. Greetings, Andrés. Andrés Yacopino. Dpto Sistemas AcaSalud

1 0