- dovecot - dovecot.org

[Dovecot] doveconf: Warning: Obsolete settings.... in /etc/dovecot/dovecot.conf: ...
by D Chen 05 Mar '12

05 Mar '12

Got duplicated Warnings from the "doveconf -n" output ! Can anyone explain and fix them ? thx! admin@server:/etc/dovecot$ doveconf -n # 2.0.13: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:716: protocol managesieve {} has been replaced by protocol sieve { } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:888: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:926: passdb pam {} has been replaced by passdb { driver=pam } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1039: userdb passwd {} has been replaced by userdb { driver=passwd } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1101: auth_user has been replaced by service auth { user } doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:716: protocol managesieve {} has been replaced by protocol sieve { } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:888: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:926: passdb pam {} has been replaced by passdb { driver=pam } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1039: userdb passwd {} has been replaced by userdb { driver=passwd } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1101: auth_user has been replaced by service auth { user } # OS: Linux 3.0.0-16-server x86_64 Ubuntu 11.10 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:~/Maildir mail_privileged_group = mail 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 passdb { driver = pam - Ignored: } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/auth-client { group = postfix mode = 0660 user = postfix } unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } user = root } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } userdb { driver = passwd } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r }

4 4

[Dovecot] Log sybnch error
by Stephen Davies 05 Mar '12

05 Mar '12

My mail log has many entries like: Mar 2 12:34:13 server dovecot: imap(john): Error: Log synchronization error at seq=2,offset=4264 for /home/john/Mail/INBOX/.imap/SMS Emails/dovecot.index: Extension header update points outside header size Version 2.1.1 dovecot -n gives: # 2.1.1: /usr/etc/dovecot/dovecot.conf # OS: Linux 2.6.33.5-desktop-2mnb i686 Mandriva Linux 2010.2 mail_access_groups = mail mail_privileged_group = mail passdb { driver = pam } protocols = pop3 imap service anvil { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = anvil extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 1 protocol = service_count = 0 type = anvil unix_listener anvil-auth-penalty { group = mode = 0600 user = } unix_listener anvil { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service auth-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = auth -w extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener auth-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service auth { chroot = client_limit = 0 drop_priv_before_exec = no executable = auth extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener auth-client { group = mode = 0600 user = } unix_listener auth-login { group = mode = 0600 user = $default_internal_user } unix_listener auth-master { group = mode = 0600 user = } unix_listener auth-userdb { group = mode = 0666 user = } unix_listener login/login { group = mode = 0666 user = } user = root vsz_limit = 18446744073709551615 B } service config { chroot = client_limit = 0 drop_priv_before_exec = no executable = config extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = config unix_listener config { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service dict { chroot = client_limit = 1 drop_priv_before_exec = no executable = dict extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dict { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service director { chroot = . client_limit = 0 drop_priv_before_exec = no executable = director extra_groups = fifo_listener login/proxy-notify { group = mode = 00 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener director-admin { group = mode = 0600 user = } unix_listener login/director { group = mode = 00 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service dns_client { chroot = client_limit = 1 drop_priv_before_exec = no executable = dns-client extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dns-client { group = mode = 0666 user = } unix_listener login/dns-client { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service doveadm { chroot = client_limit = 1 drop_priv_before_exec = no executable = doveadm-server extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener doveadm-server { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service imap-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = imap-login extra_groups = group = idle_kill = 0 inet_listener imap { address = port = 143 ssl = no } inet_listener imaps { address = port = 993 ssl = yes } privileged_group = process_limit = 0 process_min_avail = 0 protocol = imap service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service imap { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = imap service_count = 1 type = unix_listener login/imap { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service indexer-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = indexer-worker extra_groups = group = idle_kill = 0 privileged_group = process_limit = 10 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service indexer { chroot = client_limit = 0 drop_priv_before_exec = no executable = indexer extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service ipc { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = ipc extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener ipc { group = mode = 0600 user = } unix_listener login/ipc-proxy { group = mode = 0600 user = $default_login_user } user = $default_internal_user vsz_limit = 18446744073709551615 B } service lmtp { chroot = client_limit = 1 drop_priv_before_exec = no executable = lmtp extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 type = unix_listener lmtp { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service log { chroot = client_limit = 0 drop_priv_before_exec = no executable = log extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = log unix_listener log-errors { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service pop3-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = pop3-login extra_groups = group = idle_kill = 0 inet_listener pop3 { address = port = 110 ssl = no } inet_listener pop3s { address = port = 995 ssl = yes } privileged_group = process_limit = 0 process_min_avail = 0 protocol = pop3 service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service pop3 { chroot = client_limit = 1 drop_priv_before_exec = no executable = pop3 extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = pop3 service_count = 1 type = unix_listener login/pop3 { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service ssl-params { chroot = client_limit = 0 drop_priv_before_exec = no executable = ssl-params extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = startup unix_listener login/ssl-params { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service stats { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = stats extra_groups = fifo_listener stats-mail { group = mode = 0600 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener stats { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } ssl_cert = </etc/pki/tls/certs/dovecot.pem ssl_key = </etc/pki/tls/private/dovecot.pem userdb { driver = passwd } -- ============================================================================= Stephen Davies Consulting P/L Voice: 08-8177 1595 Adelaide, South Australia. Fax : 08-8177 0133 Records & Collections Management. Mobile:040 304 0583

2 4

[Dovecot] doveadm -A stops processing at first uid<first_valid_uid
by Joseph Tam 04 Mar '12

04 Mar '12

I would like to run various doveadm commands that involves all (mail) users like doveadm expunge -A mailbox Trash savedbefore 30d but any doveadm command that uses "-A" to iterate through all users will stop processing at the first account with UID<first_valid_uid. doveadm(sysdaemon): Error: user sysdaemon: Couldn't drop privileges: Mail access for users with GID 5551 not permitted (see first_valid_gid in config file, gid from userdb lookup). doveadm(sysdaemon): Error: User init failed doveadm: Error: Failed to iterate through some users However, these accounts are system accounts (locked password, no shell) and are in userdb to provide UID<->name mapping for utilities like ls, chown, etc. There are various workaround like iterating manually, or setting first_valid_uid to zero, or even reordering users to put all system accounts at the end, but is there a better way to do this? Joseph Tam <jtam.home(a)gmail.com>

2 3

[Dovecot] Multiple namespaces seems to be used at the same time
by Steve Campbell 04 Mar '12

04 Mar '12

I've just converted from an old Centos 3 box to a Centos 6.2 box. I've switched from UW-imap to dovecot in the process. In my configurations, I've placed the multiple namespace sections as suggested by the "Backward compatability" part of the wiki. I use mbox since I mostly copied the home directories from the old to the new server. On some of the clients, it appears that the client is using multiple namespaces at the same time. When they view their subscribed folders, they see multiple "mail" folders instead of just the single "mail" folder under their home directory. The .subscription files are more than likely not correct (haven't looked yet, but will fix them as a user calls), but should this ever happen? I'm also sure the client's prefix isn't set since the old system never required it and there are just so many other things that are required right now on this conversion. Speaking of prefixes, I'd like to get the default of "" (nothing entered) to work for the majority of the users to avoid having to add this to the multiple users we have. Hopefully, by going through each user's home directory and copying the old .mailboxlist to a new .subscriptions file and ensuring the imap folders are in ~/mail will do this. Does this sound resonable? Thanks for any help. The learning curve is getting less steep, but it's still a ways off to the top of the hill. steve campbell

2 1

[Dovecot] doveadm fetch prints duplicate results in 2.1
by Christoph Bußenius 04 Mar '12

04 Mar '12

Hi, when the private namespace has "prefix = INBOX." and you use doveadm fetch to search for "mailbox INBOX", then it prints every message twice: # doveadm fetch -u testuser 'mailbox uid guid' mailbox INBOX mailbox: INBOX uid: 1 guid: 1757c403a4ec4d4fbf040000463889b5 mailbox: INBOX uid: 1 guid: 1757c403a4ec4d4fbf040000463889b5 Without "prefix = INBOX." in the configuration, the messages are only printed once. In 2.0, they were never printed twice. doveconf -n # 2.1.1: /usr/local/dovecot/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-35-server x86_64 Ubuntu 10.04.4 LTS disable_plaintext_auth = no mail_gid = vmail mail_location = mdbox:~/mdbox mail_plugins = acl mail_uid = vmail namespace { inbox = yes location = prefix = INBOX. separator = . } passdb { args = scheme=CRYPT username_format=%u /usr/local/dovecot/etc/dovecot/users driver = passwd-file } protocols = imap service auth { unix_listener auth-userdb { group = vmail mode = 0660 } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = username_format=%u /usr/local/dovecot/etc/dovecot/users driver = passwd-file } protocol imap { mail_plugins = acl imap_acl } Cheers, Christoph -- Christoph Bußenius Rechnerbetriebsgruppe der Fakultäten Informatik und Mathematik Technische Universität München +49 89-289-18519 <> Raum 00.05.055 <> Boltzmannstr. 3 <> Garching

2 2

[Dovecot] 2.1.1: Incorrect quoting of RFC 2822 personal parts in ENVELOPE data
by Michael M Slusarz 04 Mar '12

04 Mar '12

I'm seeing this: 1 UID FETCH 31734 (ENVELOPE) * 23 FETCH (UID 31734 ENVELOPE ("Fri, 2 Mar 2012 19:05:24 -0500 (EST)" "XXXXXX" (({22} XXXXX \"X-XX\" XXXXXX NIL "XXXXXXX" "XXXXXXXXX.XXX")) (({22} XXXXX \"X-XX\" XXXXXX NIL "XXXXXXX" "XXXXXXXXX.XXXXXX.XXX")) ((NIL NIL "XXXXXXX" "XXXXXXXXX.XXX")) ((NIL NIL "slusarz" "curecanti.org")) NIL NIL NIL "<1109380587237.1109118788902.20323.7.35190001@scheduler>")) It should be: 1 UID FETCH 31734 (ENVELOPE) * 23 FETCH (UID 31734 ENVELOPE ("Fri, 2 Mar 2012 19:05:24 -0500 (EST)" "XXXXXX" (({20} XXXXX "X-XX" XXXXXX NIL "XXXXXXX" "XXXXXXXXX.XXX")) (({20} XXXXX "X-XX" XXXXXX NIL "XXXXXXX" "XXXXXXXXX.XXXXXX.XXX")) ((NIL NIL "XXXXXXX" "XXXXXXXXX.XXX")) ((NIL NIL "slusarz" "curecanti.org")) NIL NIL NIL "<1109380587237.1109118788902.20323.7.35190001@scheduler>")) since the RFC 2822 quoting characters must be removed. michael

2 1

[Dovecot] LIST-STATUS issue
by Michael M Slusarz 04 Mar '12

04 Mar '12

Looked at the hg commits since 2.1.1, but didn't see anything that was exactly on-point to this... UNSEEN counts seem to be broken when done in a LIST-STATUS call. I see this, for example: >> Timestamp: Thu, 01 Mar 2012 10:55:47 -0700 [...] C: 3 LIST "" (INBOX IN.dovecot) RETURN (STATUS (UNSEEN)) S: * LIST () "." "IN.dovecot" S: * STATUS "IN.dovecot" (UNSEEN 0) S: * LIST () "." "INBOX" S: * STATUS "INBOX" (UNSEEN 3) S: 3 OK List completed. 3 seconds later... >> Timestamp: Thu, 01 Mar 2012 10:55:50 -0700 S: * OK [CAPABILITY IMAP4rev1 LITERAL+ LOGIN-REFERRALS ID ENABLE AUTH=LOGIN XIMAPPROXY] Dovecot ready. C: [LOGIN Command - username: slusarz] S: * OK [XPROXYREUSE] IMAP connection reused by squirrelmail-imap_proxy S: 1 OK User logged in C: 2 EXAMINE IN.dovecot (QRESYNC (1254166849 25800 18484,20260,20393,20705,20860:20868)) S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft impflag1 impflag2 impflag0 Junk seen NonJunk) S: * OK [PERMANENTFLAGS ()] Read-only mailbox. S: * 13 EXISTS S: * 0 RECENT S: * OK [UNSEEN 5] First unseen. S: * OK [UIDVALIDITY 1254166849] UIDs valid S: * OK [UIDNEXT 20869] Predicted next UID S: * OK [HIGHESTMODSEQ 25800] Highest S: 2 OK [READ-ONLY] Select completed. [...] C: 7 SEARCH RETURN (COUNT) UNSEEN S: * ESEARCH (TAG "7") COUNT 8 S: 7 OK Search completed (0.000 secs). I can confirm that I did not receive 8 dovecot list messages in 3 seconds. :) Once the mailbox is accessed, I am seeing correct counts in LIST-STATUS return again: >> Timestamp: Thu, 01 Mar 2012 10:57:28 -0700 [...] C: 3 LIST "" (INBOX IN.dovecot) RETURN (STATUS (UNSEEN)) S: * LIST () "." "IN.dovecot" S: * STATUS "IN.dovecot" (UNSEEN 8) S: * LIST () "." "INBOX" S: * STATUS "INBOX" (UNSEEN 3) S: 3 OK List completed. I am using imapproxy for these connections, so all access are happening in the same Dovecot access. michael

2 8

[Dovecot] directly addressable public folders issues
by Tom Fernandes 04 Mar '12

04 Mar '12

Hi, I would like to have an address info(a)example.com whose mails are stored in a public folder. I also want certain users to be able to create sieve-filter-rules and subfolders. From what I understand it's a good idea to have a separate location for home and for mail_location. For my normal accounts I have: home = /var/vmail/<user> mail_location = ~/Maildir Is there a way to have the same for public folders? This are my current settings: namespace public { separator = / prefix = public/ location = maildir:/var/vmail/public subscriptions = no } user_attrs = homeDirectory=home=/var/vmail/%$, =mail=maildir:~/Maildir The LDAP-homeDirectory-attribute for info(a)example.com is "public/.info" Like this an incoming mail is stored below /var/vmail/public/.info/Maildir which is good. The MUA seems to read to read from /var/vmail/public/.info though. How can I make the MUA read from /var/vmail/public/.info/Maildir instead? And in case this works - is it possible to have only certain users modify the sieve-rule for this public folder or do I definitely need a passdb-entry for info(a)example.com? Modifying scripts via commandline is not an option... I'm using dovecot 1.2. regards, Tom Fernandes

2 1

[Dovecot] Dovecot clustering with dsync-based replication
by Timo Sirainen 03 Mar '12

03 Mar '12

This document describes a design for a dsync-replicated Dovecot cluster. This design can be used to build at least two different types of dsync clusters, which are both described here. Ville has also drawn overview pictures of these two setups, see http://www.dovecot.org/img/dsync-director-replication.png and http://www.dovecot.org/img/dsync-director-replication-ssh.png First of all, why dsync replication instead of block level filesystem replication? - dsync won't replicate filesystem corruption. - A cold restart of replication won't go through all of the data in the disks, but instead quickly finds out what has changed. - Split brain won't result in downtime or losing any data. If both sides did changes, the changes are merged without data loss. - If using more than 2 storages, the users' replicas can be divided among the other storages. So if one storage goes down, the extra load is shared by all the other storages, not just one. Replication mail plugin ----------------------- This is a simple plugin based on notify plugin. It listens for all changes that happen to mailboxes (new mails, flag changes, etc.) Once it sees a change, it sends an asynchronous (username, priority) notification to replication-notify-fifo. The priority can be either high (new mails) or low (everything else). Optionally the replication plugin can also support synchronous replication of new mail deliveries. In this way it connects to replication-notify UNIX socket, tells it to replicate the user with sync (=highest) priority and waits until it is done or replication_sync_timeout occurs. The IMAP/LMTP client won't see an "OK" reply until the mail is replicated (or the replication has failed). The synchronous replication probably adds a noticeable delay, so it might not be acceptable for IMAP, but might be for LMTP. So, what is listening in those replication-notify* sockets? It depends on if Dovecot is running on director-based setup or not. Aggregator ---------- When running in Dovecot director-based setup, all of the Dovecot backends (where replication plugin runs) also run "aggregator" process. Its job is very simple: It proxies the notifications from mail plugin and sends them via a single TCP connection to the replicator process running in Dovecot proxies. This is simply an optimization to avoid tons of short lived TCP connections directly from replication plugin to director server. When not running in Dovecot director setup (i.e. there is only a single Dovecot instance that handles all of the users), there is no point in having an aggregator proxy, because the replicator process is running on the same server. In this kind of setup the replicator process directly listens on the replication-notify* sockets. Replicator ---------- The initial design for replicator isn't very complex either: It keeps a priority queue of all users, and replicates those users at the top of the queue. Notifications about changes to user's mailboxes (may) move the user up in the priority queue. If the user at the top of the queue already has been replicated "recently enough", the replicator stops its work until new changes arrive or the "recently enough" is no longer that. dsync can do two types of syncs: quick syncs and full syncs. A quick sync trusts indexes and does the replication with the least amount of work and network traffic. A quick sync is normally enough to replicate all changes, but just in case something has gone wrong there's also the full sync option, which guarantees that the mailboxes end up being fully synced. A full sync is slower though, and uses more network traffic. The priority queue is sorted by: 1. Priority (updated by a notification from replication plugin) 2. If priority!=none: Last fast sync (those users are replicated first whose last replication time is oldest) 2. If priority=none: Last full sync (these users should already be fully synced, but do a full sync for them once in a while anyway) All users get added to the replication queue at replicator startup with "none" priority. The list of users is looked up via userdb iteration. If the previous replication state is found from a disk dump, it's used to update the priorities, last_*_sync timestamps and other replication state. Replicator process creates such dumps periodically [todo: every few mins? maybe a setting?]. Replicator starts replicating users at the top of the queue, setting their priorities to "none" before starting. This means that if another change notification arrives during replication, the priority is bumped up and no changes get lost. replication_max_conns setting specifies how many users are replicated simultaneously. If the user's last_full_sync is older than replication_full_sync_interval setting, a full sync is done instead of a fast sync. If the user at the top of the queue has "none" priority and the last_full_sync is newer than replication_full_sync_interval, the replication stops. [todo: it would be nice to prefer doing all the full syncs at night when there's hopefully less disk I/O] (A global replication_max_conns setting isn't optimal in proxy-based setup, where different backend servers are doing the replication. There it should maybe be a per-backend setting. Then again, it doesn't account for the replica servers that also need to do replication work. Also to properly handle this each backend should have its own replication queue, but this requires doing a userdb lookup for each user to find out their replication server, and this would need to be done periodically in case the backend changes, which can easily happen often with director-based setup. So all in all, none of this is being done in the initial implementation. Ideally the users are distributed in a way that a global replication queue would work well enough.) In director-based setup each director runs a replicator server, but only one of them (master) actually asks the backends to do the replication. The rest of them just keep track of what's happening, and if the master dies or hangs, one of the others becomes the new master. The server with lowest IP address is always the master. The replicators are connected to a ring like the directors, using the same director_servers setting. The communication between them is simply about notifications of what's happening to users' priorities. Preferably the aggregators would always connect to the master server, but this isn't required. In general there's not much that can go wrong, since it's not a problem if two replicators request a backend to start replication for the same user or if the replication queue states aren't identical. If the replication is running too slowly [todo: means what exactly?], log a warning and send an email to admin. So, how does the actual replication happen? Replicator connects to doveadm server and sends a "sync -u user@domain" command. In director-based setup the doveadm server redirects this command to the proper backend. doveadm sync ------------ This is an independent feature from all of the above. Even with none of it implemented, you could run this to replicate a user. Most of this is already implemented. The only problem is that currently you need to explicitly tell it where to sync. So, when the destination isn't specified, it could do a userdb lookup and use the returned "mail_replica" field as the destination. Multiple (sequentially replicated) destinations could be supported by returning "mail_replica2", "mail_replica3" etc. field. In NFS-based (or shared filesystem-based in general) setup the mail_replica setting is identical to mail_location setting. So your primary mail_location would be in /storage1/user/Maildir, while the secondary mail_replica would be in /storage2/user/Maildir. Simple. In non-NFS-based setup two Dovecot servers talk dsync protocol to each others. Currently dsync already supports SSH-based connections. It would also be easy to implement direct TCP-based connections between two doveadm servers. In future these connections could be SSL-encrypted. Initially I'm only supporting SSH-based connections, as they're already implemented. So what does the mail_replica setting look like in this kind of a setup? I'm not entirely sure. I'm thinking that it could be either "ssh:host" or "ssh:user@host", where user is the SSH login user (this is opposite of the current doveadm sync command line usage). In future then it could support also tcp:host[:port]. Both of these ssh: and tcp: prefixes would also be supported by doveadm sync command line usage (and perhaps the prefixless user@domain be deprecated). dsync can run without any long lived locking and it typically works fine. In case mailbox was modified during dsync, the replicas may not end up being identical, but nothing breaks. dsync currently usually notices this and logs a warning. When these conflicting changes was caused by imap/pop3/lda/etc. this isn't a problem, they've already notified replicator already to perform another sync that will fix it. Running two dsyncs at the same time is more problematic though, mainly related to new emails. Both dsyncs notice that mail X needs to be replicated, so both save it and it results in having a duplicate. To avoid this, there should be a dsync-lock. If this lock exists, dsync should wait until the previous dsync is done and then do it again, just in case there were more changes since the previous sync started. This should conclude everything needed for replication itself. High-availability NFS setup --------------------------- Once you have replication, it's of course nice if the system automatically recovers from a broken storage. In NFS-based setups the idea is to do soft mounts, so if the NFS server goes away things start failing with EIO errors, which Dovecot notices and switches to using the secondary storage(s). In v2.1.0 Dovecot already keeps track of mounted filesystems. Initially they're all marked as "online". When multiple I/O errors occur in a filesystem [todo: how many exactly? where are these errors checked, all around in the code or checking the log?] the mountpoint is marked as "offline" and the connections accessing that storage are killed [todo: again how exactly?]. Another job for replication plugin is to hook into namespace creation. If mail_location points to a mountpoint marked as "offline", it's replaced with mail_replica. This way the user can access mails from the secondary storage without downtime. If the replica isn't fully up to date, this means that some of the mails (or other changes) may temporarily be lost. These will come back again after the original storage has come back up and replication has finished its job. So as long as mails aren't lost in the original storage, there won't be any permanent mail loss. When an offline storage comes back online, its mountpoint's status is initially changed to "failover" (as opposed to "online"). During this state the replication plugin works a bit differently when the user's primary mail_location is in this storage: It first checks if the user is fully replicated, and if so uses the primary storage, otherwise it uses the replica storage. Long running IMAP protocesses check the replication state periodically and kill themselves once the user is replicated, to move back to primary storage. Once replicator notices that all users have been replicated, it tells the backends' to change the "failover" state to "online" (via doveadm server). High-availability non-NFS setup ------------------------------- One possibility is to use Dovecot proxies, which know which servers are down. Instead of directing users to those servers, it would direct them to replica servers. The server states could be handled similar to NFS setup's online vs. failover vs. offline states. Another possibility would be to do the same as above, except without separate proxy servers. Just make "mail.example.com" DNS point to two IP addresses, and if one Dovecot notices that it's not the user's primary server, it proxies to the secondary server, unless it's down. If one IP is down, clients hopefully connect to the other.

3 5

[Dovecot] keywords/flags questions
by Arnaud Abélard 03 Mar '12

03 Mar '12

Hello, I am currently using dovecot 2.0.13 and I have been working on keywords handling our webmail and I have a few questions about how dovecot handles them. First, if I am not mistaken keywords neeed to be UTF-7 encoded. That means I need to encode special caracters using values between & and - chars. UTF-7 encoding is case sensitive, &AOA- isn't the same chars as &aoa-. But docevot save keywords in lowercase or am I mistaken? For example: . STORE 1:1 flags &AOA-_refaire * 1 FETCH (FLAGS (&aoa-_refaire)) This makes retrieving the keyword properly impossible. What did I miss? My other question is about the permanent flags being displayed upon selecting a mailbox. I'm trying to understand why unused keywords are still showing up in there. Is there a way to force the definitive removal of a keyword from a mailbox? are old keywords kept undefinitely? Thanks in advance, Arnaud -- Arnaud Abélard jabber: arnaud.abelard(a)univ-nantes.fr / twitter: ArnY Administrateur Système DSI Université de Nantes -

3 2

[Dovecot] Desperately need help ! a default dovecot.conf and/or Ubuntu 11.10 postfix/dovecot server configuration issue!
by D Chen 03 Mar '12

03 Mar '12

When ungraded from Ubuntu 11.04 to 11.10, dovecot can't start successfully with lots of errors i.e. "dovecot: doveconf: Warning: ... 'imaps' protocol is no longer necessary, remove it"... At any rate, I want to setup a postfix(MTA)/dovecot(MDA) servers on Ubuntu 11.10, by following the Postfix installation and configuration instruction in Ubuntu Serverguide, in "1.4 Configuring SASL" section on page 190, after run "sudo apt-get install dovecot-common", it requires to edit the section of "auth default" and the "socket listen" option...,in the /etc/dovecot/dovecot.conf file, BUT my /etc/dovecot/dovecot.conf (only about 4k byes) CAN'T find the "auth default" "socket listen" ! I also checked into the /usr/share/doc/dovecot-common/dovecot/example-config, there is a dovecot.conf, it's also about 4k size, and there is no such "auth default" or "socket listen" words can be found ! where is the default dovecot.conf file I can get a copy ? BTW, there is the dovecot.conf.ucf file (what is this for?) which's about 50k and has the "auth default" and "socket listen" words there ! what is supposed the size for the /etc/dovecot/dovecot.conf ? i'm confused! Thx.

3 2

[Dovecot] fts size
by Jan-Frode Myklebust 02 Mar '12

02 Mar '12

Does anybody have any numbers for how large storage one will need for the fts indexing server? I see the wiki says 30% of mailbox size for Squat (partial=4 full=4). Is it similar for lucene/solr? Do I understand correctly if I think http://wiki2.dovecot.org/Plugins/FTS/Lucene will create an index for each user in his home directory? Will this be accounted for in the users' quota? -jf

3 5

[Dovecot] Thanks, was Re: need simpler instructions for user authentication
by David Benfell 02 Mar '12

02 Mar '12

Thanks to everyone who responded to my request. And I apologize that this message isn't properly threaded. I'm in trouble whenever I have to send mail from my gmail account because I automatically pull it down into the same place from which I send my regular mail (from benfell(a)parts-unknown.org ) and I haven't configured that to deal with the gmail account. That makes it difficult to reply properly to mail on this list which I have subscribed to with the gmail account so that I'd actually receive it even when I'm having problems with my main mail system. Timo Sirainen <tss(a)iki.fi> responded that I needed a userdb and offered that I should probably add the following to dovecot.conf : userdb { driver = passwd } As near as I can tell--and it's been over a day now--that solved the problem. Thanks!

1 0

[Dovecot] 2.1.1: subscriptions: Removing invalid entry
by Ralf Hildebrandt 01 Mar '12

01 Mar '12

Admittedly, it's not a valid folder name and dovecot is right in removing it: Feb 28 17:50:05 postamt dovecot: imap(kbaessle): Warning: Subscriptions file /home/k/b/kbaessle/Maildir/subscriptions: Removing invalid entry: Entw�rfe ...but when looking at the subscription file AFTER the removal, that file contained an empty line. I don't think that's correct. -- 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 2

[Dovecot] need simpler directions on user authentication
by David Benfell 01 Mar '12

01 Mar '12

Hi all, My situation is this: I have postfix running on a Linode under Arch Linux. A recent upgrade to dovecot broke the configuration. Now I get "Couldn't drop privileges: User is missing UID (see mail_uid setting)." I do not want virtual users. I do not particularly want SQL or LDAP. I do have multiple domains. I do use Maildir. I already have SSL certificates for the server which I did manage to get dovecot to quit complaining about. The documentation is driving me nuts. It keeps telling me about stuff I think I don't need. And I can't tell what I actually *do* need. All I want is for system users, including myself, to be able to get their mail. How do I do this? Thank you! David Benfell dbenfell(a)gmail.com

2 1

[Dovecot] need simpler instructions for user authentication
by David Benfell 01 Mar '12

01 Mar '12

Hi all, My situation is this: I have postfix running on a Linode under Arch Linux. A recent upgrade to dovecot broke the configuration. Now I get "Couldn't drop privileges: User is missing UID (see mail_uid setting)." I do not want virtual users. I do not particularly want SQL or LDAP. I do have multiple domains. I do use Maildir. I already have SSL certificates for the server which I did manage to get dovecot to quit complaining about. The documentation is driving me nuts. It keeps telling me about stuff I think I don't need. And I can't tell what I actually *do* need. All I want is for system users, including myself, to be able to get their mail. How do I do this? Thank you! David Benfell dbenfell(a)gmail.com

2 2

[Dovecot] Permission problems
by David Renstrom 01 Mar '12

01 Mar '12

Hi, I've set up a Postfix and Dovecot (only IMAP) combination using MySQL and Postfixadmin on Fedora. Almost everything works correctly now. The only thing bugging me right now is that I always have to change the access privileges of the directories in /var/run/dovecot/ manually to 777 to make it work. As you understand, I'm not particularly happy about this as it doesn't feel secure at all. And I also have to do this every time I reboot since Dovecot resets the old access priviliges (600). As you see I've got a vmail user who belongs to the mail group. Almost all directories under /var/run/dovecot belong to user root and group root. They all have the permissions rw--------. Below is some output from the log file dovecot.log: Mar 01 03:31:17 auth: Fatal: net_connect_unix(auth-worker) in directory /run/dovecot failed: Permission denied (euid=101(vmail) egid=12(mail) missing +r perm: /run/dovecot/auth-worker, dir owned by 0:97 mode=0755) Mar 01 03:31:17 master: Error: service(auth): command startup failed, throttling Mar 01 03:31:46 imap-login: Info: Disconnected (auth failed, 1 attempts): method=PLAIN, rip=94.254.99.6, lip=91.123.204.174 What is wrong here and how can I correct it? Thanks in advance! /David R.

3 2

[Dovecot] remove messages once downloaded
by Michael Sidoric 01 Mar '12

01 Mar '12

> > I need some help with the dovecot configuration. I want to remove > downloaded messages from Mail Server once the messages have been > successfully downloaded by pop3-clients, even when the clients have been > configured to save copy of messages in the Server. timo is quite correct -- consider imap instead, that's why the protocol exists.

5 5

[Dovecot] dovecot-2.1-pigeonhole-0.3.0 identifier redeclared: sieve_multiscript_run (patch)
by Piotr Tarnowski 29 Feb '12

29 Feb '12

Hi, I recently compiled dovecot-2.1.1 on Solaris 10 with Sun Studio, but when I want to compile Sieve for this version (dovecot-2.1-pigeonhole-0.3.0) I get an error: "sieve.c", line 578: identifier redeclared: sieve_multiscript_run and I see that declaration in sieve.h is different from definition in sieve.c, so compilation process fails with SunStudio cc compiler. I have done a quick hack to correct this, and then compiled successfully. Patch is included as attachment. Full output, OS and compiler versions below: libtool: compile: cc -DHAVE_CONFIG_H -I. -I../.. -I/home/soft/dovecot/dovecot-2.1.1 -I/home/soft/dovecot/dovecot-2.1.1/src/lib -I/home/soft/dovecot/dovecot-2.1.1/src/lib-dict -I/home/soft/dovecot/dovecot-2.1.1/src/lib-dns -I/home/soft/dovecot/dovecot-2.1.1/src/lib-mail -I/home/soft/dovecot/dovecot-2.1.1/src/lib-imap -I/home/soft/dovecot/dovecot-2.1.1/src/lib-fs -I/home/soft/dovecot/dovecot-2.1.1/src/lib-charset -I/home/soft/dovecot/dovecot-2.1.1/src/lib-index -I/home/soft/dovecot/dovecot-2.1.1/src/lib-storage -I/home/soft/dovecot/dovecot-2.1.1/src/lib-storage/index -I/home/soft/dovecot/dovecot-2.1.1/src/lib-storage/index/raw -I/home/soft/dovecot/dovecot-2.1.1/src/lib-lda -I/home/soft/dovecot/dovecot-2.1.1/src/lda -I/home/soft/dovecot/dovecot-2.1.1/src/lib-master -I/home/soft/dovecot/dovecot-2.1.1/src/lib-settings -DMODULEDIR=\"/usr/local/dovecot-2.1.1/lib/dovecot\" -I/usr/local/openldap/include -I/usr/local/ssl/include -I/usr/local/include -xO3 -xautopar -c sieve.c -KPIC -DPIC -o .libs/sieve.o "sieve-common.h", line 33: warning: useless declaration "/home/soft/dovecot/dovecot-2.1.1/src/lib-storage/mailbox-list.h", line 13: warning: useless declaration "sieve.c", line 578: identifier redeclared: sieve_multiscript_run current : function(pointer to struct sieve_multiscript {pointer to struct sieve_instance {..} svinst, pointer to struct sieve_result {..} result, pointer to const struct sieve_message_data {..} msgdata, pointer to const struct sieve_script_env {..} scriptenv, int status, _Bool active, _Bool keep, pointer to struct ostream {..} teststream}, pointer to struct sieve_binary {}, pointer to struct sieve_error_handler {pointer to struct pool {..} pool, int refcount, pointer to struct sieve_instance {..} svinst, pointer to struct sieve_error_handler {..} parent, unsigned int max_errors, unsigned int errors, unsigned int warnings, _Bool log_info, _Bool log_debug, pointer to function(..) returning void verror, pointer to function(..) returning void vwarning, pointer to function(..) returning void vinfo, pointer to function(..) returning void vdebug, pointer to function(..) returning void free}, unsigned int, _Bool) returning _Bool previous: function(pointer to struct sieve_multiscript {pointer to struct sieve_instance {..} svinst, pointer to struct sieve_result {..} result, pointer to const struct sieve_message_data {..} msgdata, pointer to const struct sieve_script_env {..} scriptenv, int status, _Bool active, _Bool keep, pointer to struct ostream {..} teststream}, pointer to struct sieve_binary {}, pointer to struct sieve_error_handler {pointer to struct pool {..} pool, int refcount, pointer to struct sieve_instance {..} svinst, pointer to struct sieve_error_handler {..} parent, unsigned int max_errors, unsigned int errors, unsigned int warnings, _Bool log_info, _Bool log_debug, pointer to function(..) returning void verror, pointer to function(..) returning void vwarning, pointer to function(..) returning void vinfo, pointer to function(..) returning void vdebug, pointer to function(..) returning void free}, enum sieve_runtime_flags {SIEVE_RUNTIME_FLAG_NOGLOBAL(1)}, _Bool) returning _Bool : "sieve.h", line 168 cc: acomp failed for sieve.c *** Error code 1 dmake: Fatal error: Command failed for target `sieve.lo' Current working directory /home/soft/dovecot/dovecot-2.1-pigeonhole-0.3.0/src/lib-sieve *** Error code 1 The following command caused the error: fail= failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='plugins'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && dmake $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ dmake "$target-am" || exit 1; \ fi; test -z "$fail" dmake: Fatal error: Command failed for target `all-recursive' % uname -a SunOS soft 5.10 Generic_142909-17 sun4u sparc SUNW,Sun-Fire-V890 Solaris % version Machine hardware: sun4u OS version: 5.10 Processor type: sparc Hardware: SUNW,Sun-Fire-V890 The following components are installed on your system: Sun Studio 12 update 1 Sun Studio 12 update 1 C Compiler Sun Studio 12 update 1 C++ Compiler Sun Studio 12 update 1 Tools.h++ 7.1 Sun Studio 12 update 1 C++ Standard 64-bit Class Library Sun Studio 12 update 1 Garbage Collector Sun Studio 12 update 1 Fortran 95 Sun Studio 12 update 1 Debugging Tools (including dbx) Sun Studio 12 update 1 IDE Sun Studio 12 update 1 Performance Analyzer (including collect, ...) Sun Studio 12 update 1 Performance Library Sun Studio 12 update 1 Scalapack Sun Studio 12 update 1 LockLint Sun Studio 12 update 1 Building Software (including dmake) Sun Studio 12 update 1 Documentation Set Sun Studio 12 update 1 /usr symbolic links and GNOME menu item version of "/opt/sunstudio12.1/bin/../prod/bin/../../bin/cc": Sun C 5.10 SunOS_sparc 2009/06/03 version of "/opt/sunstudio12.1/bin/../prod/bin/../../bin/CC": Sun C++ 5.10 SunOS_sparc 2009/06/03 version of "/opt/sunstudio12.1/bin/../prod/bin/../../bin/f90": Sun Fortran 95 8.4 SunOS_sparc 2009/06/03 version of "/opt/sunstudio12.1/bin/../prod/bin/../../bin/dbx": Sun DBX Debugger 7.7 SunOS_sparc 2009/06/03 version of "/opt/sunstudio12.1/bin/../prod/bin/../../bin/analyzer": Sun Analyzer 7.7 SunOS_sparc 2009/06/03 version of "/opt/sunstudio12.1/bin/../prod/bin/../../bin/dmake": Sun Distributed Make 7.9 SunOS_sparc 2009/06/03 Regards -- [ Piotr Tarnowski piotr.tarnowski(a)us.edu.pl ] [ Unix Administrator at University of Silesia, Katowice, Poland ]

2 1

[Dovecot] What's behind the message ...
by Frank Elsner 29 Feb '12

29 Feb '12

... Warning: /media/Backup28a is no longer mounted. If this is intentional, remove it with doveadm mount Hello, the above message appeared when I restarted dovecot. What has dovecot to deal with my USB-Backup-Disk? Dovecot cares about filesystem without any relation to the mail system? Why this? What's bedind? Thanks in advance, Frank Elsner

2 2

[Dovecot] per-user limit?
by Peter Hessler 29 Feb '12

29 Feb '12

I am seeing a problem where users are limited to 6 imap logins total. One of my users has a bunch of phones and computers, and wants them all on at the same time. I'm looking through my configuration, and I cannot see a limit on how many times a single user can connect. He is connecting from different IPs. Any ideas? My logs show the following error when they attempt to auth for a 7th time: dovecot: imap-login: Disconnected (no auth attempts): rip=111.yy.zz.xx, lip=81.209.183.113, TLS $ dovecot -n # 2.0.16: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.1 amd64 ffs auth_mechanisms = plain login base_dir = /var/dovecot/ listen = *, [::] mail_location = maildir:/usr/home/%u/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 ihave mbox_write_locks = fcntl passdb { driver = bsdauth } service auth { unix_listener /var/run/dovecot/auth-master { mode = 0600 } unix_listener /var/spool/postfix/private/auth { group = wheel mode = 0660 user = _postfix } user = root } service imap-login { process_limit = 128 process_min_avail = 6 service_count = 1 user = _dovecot } service pop3-login { process_limit = 64 process_min_avail = 6 service_count = 1 user = _dovecot } ssl_cert = </etc/ssl/dovecotcert.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve postmaster_address = postmaster(a)theapt.org } -- We are all in the gutter, but some of us are looking at the stars. -- Oscar Wilde

4 4

[Dovecot] Post-login scripting - Trash cleanup
by list＠airstreamcomm.net 29 Feb '12

29 Feb '12

We are considering using the post-login scripting to clear trash older than 90 days from user accounts. has anyone done this, and if so did this cause logins to slow down too much waiting for the trash to purge? One idea was to execute the trash purge script once a day by tracking their logins and seeing that it has already ran that day. Another idea was to call the trash purge script in the background and continue without acknowledging that it has finished to keep logins speedy.

3 4

[Dovecot] Master user
by Emiliano Rago 29 Feb '12

29 Feb '12

Hi, I'd like to have a master user that can read the other users mailboxes. I have only one user who read and write the mail (i.e. I use the static userdb) and I use namespace for public and shared mailboxes. I can authenticate to the server but I am not able to list the mailboxes: > emiliano@dovecot:~$ telnet localhost imap > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. > 1 login user*master password > 1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS ACL RIGHTS=texk] Logged in > 5 LIST "" * > * LIST (\Unmarked) "." "INBOX" > * LIST (\Noselect \HasNoChildren) "." "shared" > * LIST (\Noselect \HasChildren) "." "public" > 5 OK List completed. > * BYE Server shutting down. > Connection closed by foreign host. This is my conf: > # 2.0.9: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.32-131.0.15.el6.x86_64 x86_64 Scientific Linux release 6.1 (Carbon) ext4 > auth_master_user_separator = * > disable_plaintext_auth = no > mail_location = maildir:/data/MAIL/MAILDIR/%u:INBOX=/data/MAIL/INBOX/%u:INDEX=/data/MAIL/METADATA/%u > mbox_write_locks = fcntl > namespace { > inbox = yes > location = > prefix = > separator = . > type = private > } > namespace { > list = yes > location = maildir:/data/MAIL/MAILDIR/%%u:INDEX=/data/MAIL/MAILDIR/shared/%u/%%u > prefix = shared.%%u. > separator = . > subscriptions = no > type = shared > } > namespace { > list = yes > location = maildir:/data/MAIL/SHARED > prefix = public. > separator = . > subscriptions = no > type = public > } > passdb { > driver = pam > } > passdb { > args = /etc/dovecot/master-shared > driver = passwd-file > master = yes > } > plugin { > acl = vfile:/etc/dovecot/global-acls:cache_secs=300 > acl_anyone = allow > acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes.db > } > protocols = imap > service auth { > unix_listener auth-userdb { > group = mailreader > mode = 0600 > user = mailreader > } > } > ssl = no > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > ssl_key = </etc/pki/dovecot/private/dovecot.pem > userdb { > args = uid=mailreader gid=mailreader home=/ allow_all_users=yes > driver = static > } > protocol lda { > mail_plugins = acl > } > protocol imap { > mail_plugins = acl imap_acl > } And in /etc/dovecot/master-shared: > master:{PLAIN}password What I did wrong? Thanks, Emiliano

2 6

[Dovecot] quota warning script not working after upgrade to 2.1.1
by Ralf Hildebrandt 28 Feb '12

28 Feb '12

With 2.0.18 I was using a quota warning script like this: plugin { ... # Quota quota = maildir quota_rule = INBOX.Trash:storage=+2048M quota_warning = storage=99%% quota-warning 99 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u } # der schickt die Quota warnmails service quota-warning { executable = script /usr/local/scripts/quota-warning2.1 user = root unix_listener quota-warning { mode = 0666 user = vmail group = users } } -rwxr-xr-x 1 root staff 3081 Feb 28 16:56 /usr/local/scripts/quota-warning2.1 But now I'm gettting this in my log: Feb 28 19:19:03 postamt quota-warning2(phxxxpsu): writing message failed Feb 28 19:19:03 postamt dovecot: quota-warning: Fatal: master: service(quota-warning): child 15065 returned error 1 Feb 28 19:40:13 postamt quota-warning2(lxxxve): writing message failed Feb 28 19:40:13 postamt dovecot: quota-warning: Fatal: master: service(quota-warning): child 3318 returned error 1 What is failing here? #!/bin/sh # # Should be run by the Local Delivery Agent # #set -x SCRIPT_NAME="quota-warning2" MAIL_TO=$2 MAIL_FROM="postmaster(a)charite.de" MAIL_QUOTA_PERCENT=$1 MAIL_SUBJECT="Ihre Mailbox ist zu "$1"% voll!" BIN_CAT="/bin/cat" BIN_DATE="/bin/date" BIN_HOSTNAME="/bin/hostname" BIN_LOGGER="/usr/bin/logger" BIN_MV="/bin/mv" BIN_STAT="/usr/bin/stat" #set -x # set misc values HOSTNAME="`${BIN_HOSTNAME}`" # set mail value MAIL_DATE="`${BIN_DATE} '+%a, %d %b %Y %T %z (%Z)'`" MAIL_MESSAGE_ID="`${BIN_DATE} '+%Y%m%d%H%M%S'`@${HOSTNAME}" #To: ${MAIL_TO} # write out message ${BIN_CAT} << EOF | /usr/local/dovecot-2.1/libexec/dovecot/dovecot-lda -d $MAIL_TO -o "plugin/quota=maildir::noenforcing" From: ${MAIL_FROM} Subject: ${MAIL_SUBJECT} Message-Id: <${MAIL_MESSAGE_ID}> Date: ${MAIL_DATE} MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit some warning in german EOF [ "$?" -gt 0 ] && \ ${BIN_LOGGER} -p mail.error -t "${SCRIPT_NAME}(${MAIL_TO})" \ "writing message failed" && exit 1 # log warning attempt ${BIN_LOGGER} -p mail.info -t "${SCRIPT_NAME}(${MAIL_TO}) ${MAIL_QUOTA_PERCENT}%" "delivered!" echo "${MAIL_DATE}: ${SCRIPT_NAME}(${MAIL_TO}) ${MAIL_QUOTA_PERCENT}% delivered!" >> /home/${SCRIPT_NAME}.log -- 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

1 1

[Dovecot] Question: Is Server Side Search announced somehow via the IMAP CAPABILITY string?
by Charles Marcus 28 Feb '12

28 Feb '12

Hey Timo, Subject says it all... This question is a result of an ongoing discussion on the mozilla enterprise list... Is there a standard/reliable way for an IMAP client to determine that an IMAP server supports server side search (with indexes)? Thanks, -- Best regards, Charles

2 4

[Dovecot] Deny create folders
by S. Kremer 28 Feb '12

28 Feb '12

Hi all, is it possible to configure dovecot in that way that special folders do not create automatically by some imap clients? i.e: outlook or thunderbird creates a folder junk-mail i would like that such folders are not created automatically or by users Best regards Stefan

5 6

[Dovecot] ANN: automx - automated mail account provisioning
by Patrick Ben Koetter 28 Feb '12

28 Feb '12

automx I am pleased to announce automx a tool that makes setting up a mail account easy. All your users need to provide is real name, mail address and password. Their mail client and automx will safely handle the rest. Say goodbye to mistyped server settings! Put an end to endless phone calls trying to coach users to configure settings, whose dialogs they can't find. Raise user satisfaction, relieve support and regain time to work on other issues. automx unifies Microsofts and Mozillas mail account provisioning standards in one powerful Open Source tool. Choose from many backends, including LDAP and SQL, and let automx create standard and individualized profiles for multiple domains on the fly! See the details on http://automx.org. p@rick -- state of mind () Digitale Kommunikation http://www.state-of-mind.de Franziskanerstraße 15 Telefon +49 89 3090 4664 81669 München Telefax +49 89 3090 4666 Amtsgericht München Partnerschaftsregister PR 563

1 0

[Dovecot] POP/IMAP on proxy rip issue
by Tomislav Mihalicek 28 Feb '12

28 Feb '12

I have a proxy setup for pop/imap. The proxies are defined in login_trusted_networks = x.x.x.x and for the imap it works fine but for pop3 connections displays the ip address of proxy IP... Dovecots are both 1.2 from the debian repo deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-1.2 main thanks -- View this message in context: http://old.nabble.com/POP-IMAP-on-proxy-rip-issue-tp33400491p33400491.html Sent from the Dovecot mailing list archive at Nabble.com.

2 3

[Dovecot] remove messages once downloaded
by julioarr＠fisica.uh.cu 28 Feb '12

28 Feb '12

I need some help with the dovecot configuration. I want to remove downloaded messages from Mail Server once the messages have been successfully downloaded by pop3-clients, even when the clients have been configured to save copy of messages in the Server. thanks, Julio

4 5

[Dovecot] LDA alias resolution problems..
by Nick Warr 28 Feb '12

28 Feb '12

I use postfix + dovecot LDA + mysql virtual users and up til friday, everything was working just fine. Dovecot is 2.0.beta6 (3156315704ef) Like I said, up til friday, when I added a vacation entry into postfix (which I have now removed to see if it was the reason) mails to the alias virusalert (which is aliased to me) went through just fine. Now I get these sort of errors from the LDA: Feb 27 11:54:03 cluster2 postfix/pipe[31267]: 866F0A41173: to=<virusalert(a)mobilia.it>, relay=dovecot, delay=357414, delays=357413/0.79/0/0.05, dsn=4.3.0, status=deferred (temporary failure. Command output: lda: Fatal: Unknown user ) Other aliases work perfectly, the only difference is that these emails are of local origin, (they're messages from Amavisd) I'm not sure why this has started to be a problem. Can anyone give me an idea where I should start looking? Nick

4 9

[Dovecot] iPhone and custom imap folders problem
by "Przemysław.Orzechowski" 27 Feb '12

27 Feb '12

Hi Im using Dovecot 1.0.10 and everything seems work ok except one client He is accessing his mailbox using iPhone There are several custom folders created and mail is directed to them using procmail The problem is iPhone mail app only sees changes in INBOX and when new mail arrives to other folders it will not see it unlers user accesses this particular folder Is there some kind of workaround for this? Im quite sure its iPhones fault as all other email clients are workin perfectly fine.

6 5

[Dovecot] value for client_limit
by ml 27 Feb '12

27 Feb '12

hello guys hello master Timo i build the last release of dovecot on my centos 5 work well and fine but what the correct value for client limit in service auth { client_limit=6000 } and service anvil { client_limit=6000 } my current dovecot -n ks37777 i386]# dovecot -n # 2.1.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31.5-xxxx-rt14-ipv6-32 i686 CentOS release 5.7 (Final) auth_mechanisms = plain login base_dir = /var/run/dovecot/ lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = [::] log_path = /var/log/maillog log_timestamp = %Y-%m-%d %H:%M:%S login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_debug = yes mail_location = maildir:~/Maildir mail_max_userip_connections = 30 mail_plugins = " quota trash zlib" managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date spamtest spamtestplus virustest namespace { inbox = yes location = prefix = separator = . } passdb { driver = pam } plugin { autocreate = Trash autocreate2 = Junk autocreate3 = Sent autocreate4 = Drafts autosubscribe = Trash autosubscribe2 = Junk autosubscribe3 = Sent autosubscribe4 = Drafts deleted_to_trash_folder = Trash plugin = $mail_plugins autocreate managesieve sieve quota quota = maildir:User quota quota_exceeded_message = Quota exceeded, please go to http://www.fakessh.eu/over_quota_help.html for instructions on how to fix this. quota_rule = *:storage=10GB quota_rule2 = Trash:storage=+10% quota_rule3 = Spam:storage=+20% quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_before = /var/sieve-scripts/roundcube.sieve sieve_dir = ~/sieve sieve_global_path = whatever trash = /etc/dovecot/dovecot-trash.conf.ext zlib_save = bz2 zlib_save_level = 9 } protocols = sieve imap pop3 service anvil { client_limit = 6000 } service auth { client_limit = 6000 process_limit = 1 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } unix_listener auth-master { mode = 0666 } unix_listener auth-userdb { mode = 0666 } vsz_limit = 64 M } service imap-login { client_limit = 0 inet_listener imap { port = 0 } inet_listener imaps { address = * , [::] port = 993 } process_limit = 1024 service_count = 1 vsz_limit = 64 M } service imap { process_limit = 1024 process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve-login { inet_listener managesieve-login { address = * , [::] port = 2000 } process_limit = 1 vsz_limit = 64 M } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { address = * , [::] port = 995 } process_limit = 1 vsz_limit = 64 M } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = mail } user = dovecot } ssl_ca = </etc/pki/tls/certs/class3.crt ssl_cert = </etc/pki/tls/certs/ks37777.kimsufi.com.cert ssl_key = </etc/pki/tls/private/ks37777.kimsufi.com.key ssl_verify_client_cert = yes userdb { driver = passwd } userdb { driver = passwd } version_ignore = yes protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep imap_max_line_length = 64 k mail_plugins = " quota trash zlib autocreate quota imap_quota zlib imap_zlib" } protocol pop3 { mail_plugins = autocreate quota quota autocreate zlib deleted_to_trash pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s } protocol lda { hostname = r13151.ovh.net info_log_path = log_path = mail_plugins = autocreate sieve quota postmaster_address = postmaster(a)fakessh.eu sendmail_path = /usr/lib/sendmail } protocol sieve { managesieve_implementation_string = dovecot managesieve_logout_format = bytes ( in=%i : out=%o ) managesieve_max_line_length = 65536 } -- http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC2626742 gpg --keyserver pgp.mit.edu --recv-key C2626742 http://urlshort.eu fakessh @ http://gplus.to/sshfake http://gplus.to/sshswilting http://gplus.to/john.swilting https://lists.fakessh.eu/mailman/ This list is moderated by me, but all applications will be accepted provided they receive a note of presentation

3 2

[Dovecot] Mail delivery to subfolders via address extension, and prefered lda method
by Micha Krause 27 Feb '12

27 Feb '12

Hi, I want to deliver mails directly to subfolders, based on address extensions. Example: Emails sent to: micha+test(a)example.com Should be stored into user micha, folder INBOX.test I was able to reproduce this with exim and dovecot-lda: command = /usr/lib/dovecot/dovecot-lda -e -m "INBOX.${substr_1:$local_part_suffix}" But I was wondering if I could do this within dovecot, which would enable me to use LMTP instead of dovecot-lda. Which brings me to my second question: Which method is "better" for dovecot, lda or LMTP? Micha Krause

2 2

[Dovecot] Virtual Folders
by jacob＠alltechservices-ia.com 27 Feb '12

27 Feb '12

Hello, I am trying to get virtual folders to work properly, and I can't seem to. I will be as detailed as possible to remove confusion. Thank you in advance. Goal: Essentially, a gmail clone, but one that I can make work on cPanel hosts with roundcube and squirrel mail, etc. By default, cpanel creates user mail dir structure of (maildir++) inbox, drafts, sent, junk, and trash (with no dovecot specific files until first login) I would like to replace all those folders with virtual representations with more capabilities. I would like to achieve the conversation view that gmail has pulled off so well. cPanel, stock, generates the following dovecot -n: (i am still not sure how it negotiates mail_location yet) # 1.2.17: /etc/dovecot.conf # OS: Linux 2.6.18-238.5.1.el5xen x86_64 CentOS release 5.7 (Final) ssl_cert_file: /etc/dovecot/ssl/dovecot.crt ssl_key_file: /etc/dovecot/ssl/dovecot.key ssl_cipher_list: ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_process_per_connection: no login_processes_count: 10 login_max_processes_count: 100 login_max_connections: 500 mail_max_userip_connections: 200 maildir_copy_preserve_filename: yes mail_plugins: quota imap_quota namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes lda: postmaster_address: postmaster(a)example.com auth default: mechanisms: plain login cache_size: 2048 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789!#$-=?^_{}~./@+% passdb: driver: checkpassword args: /usr/local/cpanel/bin/dovecot-auth userdb: driver: prefetch socket: type: listen client: path: /var/run/dovecot/auth-client mode: 438 plugin: quota: maildir quota_rule: Trash:ignore I started a test box with Debian running the same version of dovecot (1.2.x) and on that system I run into problems every time I make a virtual folder a root folder. I assume it is trying to look up a normal folder instead of the virtual ones and I am confusing it. So I came here because it would be really really neat if I could pull this off. Again, thank you in advance. -cornfeed

2 1

[Dovecot] Dovecot 2.1 with custom OpenSSL fails to build
by Andreas M. Kirchwitz 27 Feb '12

27 Feb '12

Hello Dovecot users! There seems to be a new dependency in some modules (eg, lib-storage, libdovecot-lda, libdovecot-ssl) on OpenSSL. In Dovecot 2.0, those modules didn't require OpenSSL, but 2.1 does. For the linking process the path to the OpenSSL library isn't specified properly (SSL_LIBS). Dovecot fails to build if OpenSSL is in a non-standard path. (Haven't checked if SSL_CFLAGS isn't properly used as well.) Example for lib-storage: env SSL_CFLAGS="-I/usr/local/ssl/include" SSL_LIBS="-L/usr/local/ssl/lib -Wl,-R/usr/local/ssl/lib -lcrypto -lssl" ./configure --prefix=/usr/local/${DOVECOTVER} --with-ssl=openssl --with-ssldir=/usr/local/${DOVECOTVER}/etc/dovecot/certs make gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-master -I../../src/lib-settings -I../../src/lib-mail -I../../src/lib-storage -DPKG_RUNDIR=\""/usr/local/Dovecot-2.1.1/var/run/dovecot"\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/usr/local/ssl/include -MT master-connection.o -MD -MP -MF .deps/master-connection.Tpo -c -o master-connection.o master-connection.c mv -f .deps/master-connection.Tpo .deps/master-connection.Po /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/usr/local/ssl/include -no-undefined -Wl,--as-needed -o indexer-worker indexer-worker.o indexer-worker-settings.o master-connection.o ../../src/lib-storage/libdovecot-storage.la ../../src/lib-dovecot/libdovecot.la -export-dynamic -ldl -lrt libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/usr/local/ssl/include -Wl,--as-needed -o .libs/indexer-worker indexer-worker.o indexer-worker-settings.o master-connection.o -Wl,--export-dynamic ../../src/lib-storage/.libs/libdovecot-storage.so ../../src/lib-dovecot/.libs/libdovecot.so -ldl -lrt -Wl,-rpath -Wl,/usr/local/Dovecot-2.1.1/lib/dovecot /usr/bin/ld: warning: libcrypto.so.1.0.0, needed by ../../src/lib-storage/.libs/libdovecot-storage.so, not found (try using -rpath or -rpath-link) /usr/bin/ld: warning: libssl.so.1.0.0, needed by ../../src/lib-storage/.libs/libdovecot-storage.so, not found (try using -rpath or -rpath-link) ../../src/lib-storage/.libs/libdovecot-storage.so: undefined reference to `OBJ_txt2nid' ../../src/lib-storage/.libs/libdovecot-storage.so: undefined reference to `SSL_set_ex_data' [...] # ldd src/lib*/.libs/*.so src/lib-dovecot/.libs/libdovecot.so: linux-gate.so.1 => (0x00979000) libdl.so.2 => /lib/libdl.so.2 (0x00c31000) librt.so.1 => /lib/librt.so.1 (0x009ed000) libc.so.6 => /lib/libc.so.6 (0x0054d000) /lib/ld-linux.so.2 (0x00c12000) libpthread.so.0 => /lib/libpthread.so.0 (0x008f4000) src/lib-lda/.libs/libdovecot-lda.so: linux-gate.so.1 => (0x0096d000) libdovecot-storage.so.0 => /usr/local/src/dovecot-2.1.1/src/lib-storage/.libs/libdovecot-storage.so.0 (0x00ae4000) libdovecot.so.0 => /usr/local/src/dovecot-2.1.1/src/lib-dovecot/.libs/libdovecot.so.0 (0x00110000) librt.so.1 => /lib/librt.so.1 (0x00189000) libc.so.6 => /lib/libc.so.6 (0x00192000) libcrypto.so.1.0.0 => not found libssl.so.1.0.0 => not found libdl.so.2 => /lib/libdl.so.2 (0x0031c000) libpthread.so.0 => /lib/libpthread.so.0 (0x00ebc000) /lib/ld-linux.so.2 (0x003f8000) src/lib-sql/.libs/libdovecot-sql.so: linux-gate.so.1 => (0x00a95000) libdovecot.so.0 => /usr/local/src/dovecot-2.1.1/src/lib-dovecot/.libs/libdovecot.so.0 (0x002b6000) libdl.so.2 => /lib/libdl.so.2 (0x00ab8000) librt.so.1 => /lib/librt.so.1 (0x0072a000) libc.so.6 => /lib/libc.so.6 (0x008f7000) /lib/ld-linux.so.2 (0x00ebd000) libpthread.so.0 => /lib/libpthread.so.0 (0x00619000) src/lib-ssl-iostream/.libs/libdovecot-ssl.so: linux-gate.so.1 => (0x00da6000) libcrypto.so.1.0.0 => not found libssl.so.1.0.0 => not found libdl.so.2 => /lib/libdl.so.2 (0x00df0000) librt.so.1 => /lib/librt.so.1 (0x00112000) libc.so.6 => /lib/libc.so.6 (0x00b5e000) /lib/ld-linux.so.2 (0x00e76000) libpthread.so.0 => /lib/libpthread.so.0 (0x005a6000) src/lib-storage/.libs/libdovecot-storage.so: linux-gate.so.1 => (0x006ed000) libcrypto.so.1.0.0 => not found libssl.so.1.0.0 => not found libdovecot.so.0 => /usr/local/src/dovecot-2.1.1/src/lib-dovecot/.libs/libdovecot.so.0 (0x00c66000) libdl.so.2 => /lib/libdl.so.2 (0x00491000) librt.so.1 => /lib/librt.so.1 (0x00be2000) libc.so.6 => /lib/libc.so.6 (0x00110000) /lib/ld-linux.so.2 (0x0036b000) libpthread.so.0 => /lib/libpthread.so.0 (0x0029a000) Without SSL_CFLAGS and SSL_LIBS but just PKG_CONFIG_PATH, it also won't work. Help appreciated ... Andreas

2 1

[Dovecot] Error with 2.0.18
by Ralf Hildebrandt 27 Feb '12

27 Feb '12

Today I found this in my log: Feb 26 14:27:51 postamt dovecot: imap(tscxxxf): Error: mmap(/home/t/s/tscxxxf/Maildir/dovecot.index.search.uids) failed: Cannot allocate memory Feb 26 14:27:51 postamt dovecot: imap(tscxxxf): Error: Corrupted squat uidlist file /home/t/s/tscxxxf/Maildir/dovecot.index.search.uids: uidlist not found Feb 26 14:27:52 postamt dovecot: imap(tscxxxf): Panic: file squat-trie.c: line 289 (squat_trie_lock): assertion failed: (trie->fd != -1) Feb 26 14:27:52 postamt dovecot: imap(tscxxxf): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x3d44a) [0xb771644a] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x3d4bb) [0xb77164bb] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb7716d87] -> /usr/local/lib/dovecot/lib21_fts_squat_plugin.so(+0x3bfa) [0xb74e1bfa] -> /usr/local/lib/dovecot/lib21_fts_squat_plugin.so(squat_trie_build_deinit+0x9fc) [0xb74e4d3c] -> /usr/local/lib/dovecot/lib21_fts_squat_plugin.so(+0x2a95) [0xb74e0a95] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(fts_backend_build_deinit+0x1b) [0xb752f6bb] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x3726) [0xb7530726] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x51d3) [0xb75321d3] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x5c34) [0xb7532c34] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x3b) [0xb778b0cb] -> dovecot/imap [tscxxxf 141.42.206.38 SELECT UID SEARCH]() [0x805ce6e] -> dovecot/imap [tscxxxf 141.42.206.38 SELECT UID SEARC Feb 26 14:27:55 postamt dovecot: master: Error: service(imap): child 18468 killed with signal 6 (core dumped) -- 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

2 2

[Dovecot] Dovecot altmove questions
by Maria Arrea 27 Feb '12

27 Feb '12

Hello We are using Dovecot 2.0.17 with mdbox+zlib and we are evaluating alternative storage. These are the relevant settings mdbox_rotate_interval = 1d mdbox_rotate_size=60m [...] zlib_save_level = 9 # 1..9 zlib_save = gz # or bz2 [...] zlib plugin enabled in dovecot-lda These are my questions: 1º General mdbox question. We are happy usings zlib_save, but we would like to try bzip2 compression. Can we change zlib to bzlib without problems? In other words, can we mix & match gzipped and bzipped messages in the same mdbox file ? 2º With doveadm altmove we can move messages matching a pattern to alternate storage. I have read an older post in this mailing list about passing specific mdbox options to doveadm altmove. Should be a good idea to have a "main" mdbox area with zlib 9 and mdbox_rotate=1d and mdox_rotate_size=60m and an "alternate area" with bzip9, mdbox_rotate=1 week and rotate_size > 60 MB? In the alternate area should only be "old" mail (1 year older). 3º We have separate raids for indexes (raid 1+0) and mdboxes (raid 5). We have almost 3 TB of gzipped mdboxes, and our backup (bacula) is taking almost 16 hours to make a full backup. Our main problem is that indexes are backupd hours before mdboxes, and that bring us some inconsistencies. What is the "right" way of backing up for separate indexes and mdboxes? Thank you for your support. Maria

3 2

[Dovecot] IMAP-proxy or not with sogo webmail and dovecot backend
by Jan-Frode Myklebust 27 Feb '12

27 Feb '12

We've been collecting some stats to see what kind of benefits UP/SquirrelMail's IMAP Proxy in for our SOGo webmail users. Dovecot is running in High-performance mode http://wiki2.dovecot.org/LoginProcess with authentication caching http://wiki2.dovecot.org/Authentication/Caching During the weekend two servers (webmail3 and webmail4) has been running with local imapproxy and two servers without (webmail1 and webmail2). Each server has served about 1 million http requests, over 3 days. server avg. response time # requests ---------------------------------------------------- webmail1.example.net 0.370411 1092386 webmail2.example.net 0.374227 1045141 webmail3.example.net 0.378097 1043919 imapproxy webmail4.example.net 0.378593 1028653 imapproxy ONLY requests that took more than 5 seconds to process: server avg. response time # requests ---------------------------------------------------- webmail1.example.net 26.048 1125 webmail2.example.net 26.2997 1080 webmail3.example.net 28.5596 808 imapproxy webmail4.example.net 27.1004 964 imapproxy ONLY requests that took more than 10 seconds to process: server avg. response time # requests ---------------------------------------------------- webmail1.example.net 49.1407 516 webmail2.example.net 53.0139 459 webmail3.example.net 59.7906 333 imapproxy webmail4.example.net 58.167 384 imapproxy The responstimes are not very fast, but they do seem to support the claim that an imapproxy isn't needed for dovecot. -jf

5 31

[Dovecot] FreeBSD maintainer ?
by Frank Bonnet 27 Feb '12

27 Feb '12

Hello Does the FreeBSD Dovecot's port maintainer read this mailing-list ? Thanks

4 4

[Dovecot] v2.0.13 problems after kernel patch for CVE-2011-1083 applied on Centos 5
by Doug Henderson 27 Feb '12

27 Feb '12

Greetings, This email is both a request for assistance/help and a heads-up. [8irgehuq] CVE-2011-1083: Algorithmic denial of service in epoll. After ksplice automatically installed the above patch on our mail servers, most/all IMAP/POP3 connections began experiencing time-outs trying to connect, or extreme timeouts in the auth procedure. dovecot: imap-login: Disconnected (no auth attempts): rip=a.a.a.a, lip=b.b.b.b, TLS handshaking: Disconnected dovecot: pop3-login: Disconnected (no auth attempts): rip=a.a.a.a, lip=b.b.b.b, TLS handshaking: Disconnected dovecot: pop3-login: Panic: epoll_ctl(add, 6) failed: Invalid argument dovecot: pop3-login: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x3cb543baa0] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3cb543baf6] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3cb543afb3] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_add+0x118) [0x3cb5447708] -> /usr/lib64/dovecot/libdovecot.so.0(io_add+0xa5) [0x3cb5446e15] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_init_finish+0x1c6) [0x3cb54355a6] -> /usr/lib64/dovecot/libdovecot-login.so.0(main+0x136) [0x37a000bdf6] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3cb301d994] -> dovecot/pop3-login(main+0x49) [0x401b99] dovecot: master: Error: service(pop3-login): child 27603 killed with signal 6 (core not dumped - add -D parameter to service pop3-login { executable } dovecot: master: Error: service(pop3-login): command startup failed, throttling dovecot: imap-login: Panic: epoll_ctl(add, 6) failed: Invalid argument dovecot: imap-login: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x3cb543baa0] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3cb543baf6] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3cb543afb3] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_add+0x118) [0x3cb5447708] -> /usr/lib64/dovecot/libdovecot.so.0(io_add+0xa5) [0x3cb5446e15] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_init_finish+0x1c6) [0x3cb54355a6] -> /usr/lib64/dovecot/libdovecot-login.so.0(main+0x136) [0x37a000bdf6] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3cb301d994] -> dovecot/imap-login(main+0x39) [0x402069] dovecot: master: Error: service(imap-login): child 27604 killed with signal 6 (core not dumped - add -D parameter to service imap-login { executable } Once this patch was removed, everything started working again. Is it possible that dovecot is trying to re-add already-added connections to the polling list - which this specific 'patch' prevents? We haven't dug deeper yet, but the error is being thrown from the method io_loop_handle_add in ioloop-epoll.c http://hg.dovecot.org/dovecot-2.0/file/aa8dfa085a99/src/lib/ioloop-epoll.c Thanks Doug

3 7

[Dovecot] upgrade to dovecot 2.1.1 any question
by ml 27 Feb '12

27 Feb '12

hi guys hi master of "Fu" hi Timo I am having problems to migrate to dovecot dovecot 2.0.18 to 2.1.1 I encounter fatal errors. I created it myself rpms available here http://ns.fakessh.eu/rpms/dovecot-2.1.1-1.centme.el5.src.rpm I can not run dovecot with this config file like this http://ns.fakessh.eu/rpms/dovecot-2.1.1-1.centme.el5.src.rpm i run this config ks37777 ~]# dovecot -n # 2.0.18: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31.5-xxxx-rt14-ipv6-32 i686 CentOS release 5.7 (Final) auth_mechanisms = plain login base_dir = /var/run/dovecot/ lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = [::] log_path = /var/log/maillog log_timestamp = %Y-%m-%d %H:%M:%S login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_debug = yes mail_location = maildir:~/Maildir mail_max_userip_connections = 30 mail_plugins = " quota trash zlib" managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date spamtest spamtestplus virustest namespace { inbox = yes location = prefix = separator = . } passdb { driver = pam } plugin { antispam_mail_notspam = --ham antispam_mail_sendmail = /usr/bin/sa-learn antispam_mail_sendmail_args = --username=%u antispam_mail_spam = --spam antispam_mail_tmpdir = /tmp antispam_signature = X-Spam-Flag antispam_signature_missing = move antispam_spam = SPAM;Spam;spam;Junk;junk antispam_trash = trash;Trash;Deleted Items;Deleted Messages autocreate = Trash autocreate2 = Junk autocreate3 = Sent autocreate4 = Drafts autosubscribe = Trash autosubscribe2 = Junk autosubscribe3 = Sent autosubscribe4 = Drafts deleted_to_trash_folder = Trash plugin = $mail_plugins autocreate managesieve sieve quota quota = maildir:User quota quota_exceeded_message = Quota exceeded, please go to http://www.fakessh.eu/over_quota_help.html for instructions on how to fix this. quota_rule = *:storage=10GB quota_rule2 = Trash:storage=+10% quota_rule3 = Spam:storage=+20% quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_before = /var/sieve-scripts/roundcube.sieve sieve_dir = ~/sieve sieve_global_path = whatever trash = /etc/dovecot/dovecot-trash.conf.ext zlib_save = bz2 zlib_save_level = 9 } protocols = sieve imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } unix_listener auth-master { mode = 0666 } unix_listener auth-userdb { mode = 0666 } vsz_limit = 64 M } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { address = * , [::] port = 993 } process_limit = 1 vsz_limit = 64 M } service imap { client_limit = 1024 service_count = 0 } service managesieve-login { inet_listener managesieve-login { address = * , [::] port = 2000 } process_limit = 1 vsz_limit = 64 M } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { address = * , [::] port = 995 } process_limit = 1 vsz_limit = 64 M } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = mail } user = dovecot } ssl_ca = </etc/pki/tls/certs/class3.crt ssl_cert = </etc/pki/tls/certs/ks37777.kimsufi.com.cert ssl_key = </etc/pki/tls/private/ks37777.kimsufi.com.key ssl_verify_client_cert = yes userdb { driver = passwd } userdb { driver = passwd } version_ignore = yes protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep imap_max_line_length = 64 k mail_plugins = " quota trash zlib autocreate quota imap_quota zlib antispam imap_zlib" } protocol pop3 { mail_plugins = autocreate quota quota autocreate zlib deleted_to_trash pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s } protocol lda { hostname = r13151.ovh.net info_log_path = log_path = mail_plugins = autocreate sieve quota postmaster_address = postmaster(a)fakessh.eu sendmail_path = /usr/lib/sendmail } protocol sieve { managesieve_implementation_string = dovecot managesieve_logout_format = bytes ( in=%i : out=%o ) managesieve_max_line_length = 65536 } -- http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC2626742 gpg --keyserver pgp.mit.edu --recv-key C2626742 http://urlshort.eu fakessh @ http://gplus.to/sshfake http://gplus.to/sshswilting http://gplus.to/john.swilting https://lists.fakessh.eu/mailman/ This list is moderated by me, but all applications will be accepted provided they receive a note of presentation

2 7

[Dovecot] deliver(test@[***domain_name***]): Fatal: setgid(5000) failed with ... Operation not permitted
by fxCode 26 Feb '12

26 Feb '12

Hi, I am relatively new to linux, and have set up my first lamp server around a month ago. The server is housed in a data centre a few miles from my house, and is working as a web server (with apache, tomcat, mysql) just fine. I have now been trying for a week to get Postfix and Dovecot working with postfixadmin and mysql. (below I have replaced my test domain name with [***domain_name***]) The story so far; I can send 'welcome' emails from within postfix admin to an external email address... and they are received by the mail client on my computer at home no problem. I can set up alias email addresses within postfix admin, such as webmaster@[***domain_name***], and emails sent to this address are redirected to the proper address as expected. But - if I set up a standard mailbox within postfix admin - test@[***domain_name***] , and email it from my home system, nothing appear in postfixadmin (after a fetch request) or the mysql database. Here is the fail point in my mail.log file ; Feb 26 12:50:27 quantum dovecot: deliver(test@[***domain_name***]): Fatal: setgid(5000) failed with euid=8(mail), gid=8(mail), egid=8(mail): Operation not permitted I don't know what the setguid(5000) is, or where it is being set, or what it should be! I have been changing permissions with the 'socket listen' section of my /etc/dovecot/dovecot.conf file, and when I restart dovecot it creates the auth-master file with the permissions as expected; socket listen { master { path = /var/run/dovecot/auth-master mode = 0777 user = vmail group = mail } client { path = /var/spool/postfix/private/auth mode = 432 #user = postfix #group = postfix } } my mail folders should be located at /var/vmail, but the folder is empty. I have chmod the permissions to be as follows; me@myserver: ls -ld /var/vmail drwxrwxrwx 2 vmail mail 4096 2012-02-11 08:40 /var/vmail Can anyone spot where this is going wrong? Thanks in advance for any help, it is very very much appreciated!!! My hosts file is as follows; 127.0.0.1 localhost [**server_ip***] quantum.[***domain_name***] quantum # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ...and 'dovecot -n' replies as follows; me@myserver: dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-38-server x86_64 Ubuntu 10.04.4 LTS ext4 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_location: maildir:/var/vmail/%d/%n mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 lda: log_path: /var/log/dovecot-deliver.log auth_socket_path: /var/run/dovecot/auth-master postmaster_address: fxcode(a)me.com mail_plugins: sieve auth default: mechanisms: plain login passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 master: path: /var/run/dovecot/auth-master mode: 511 user: vmail group: mail

1 1

[Dovecot] IMAP NOTIFY extension
by Timo Sirainen 26 Feb '12

26 Feb '12

http://hg.dovecot.org/dovecot-2.2-notify/ contains the initial implementation of IMAP NOTIFY extension. It's less than half-working, but the difficult part of it is done I think. If I give it a command like: x notify set (personal (messagenew messageexpunge flagchange)) and then in another session I copy a message to another mailbox, it sends: * STATUS "foobar" (MESSAGES 77 UIDNEXT 78 UIDVALIDITY 1329431281 UNSEEN 75) This requires mailbox_list_index=yes to work. It works by following the dovecot.list.index.log changes, so it's going to be pretty efficient. Some TODO that I've so far noticed: - NOTIFY is handled currently only for non-selected mailboxes. (handling the new features for selected mailbox should be simple) - initial STATUS sending isn't done with STATUS option - only MessageNew, MessageExpunge and FlagChange notifications are sent currently - MailboxName handling probably needs to be able to get "old" and "new" views, figure out what changed in them and send those changes (dsync has similar code) - mailbox list indexes seem to be adding too much stuff, which results in: - STATUS duplicates, but there should already be code to avoid these so I'm not sure what's going on - ACLs and shared mailboxes don't work right - add 0.5s delay before notifying IMAP code, so multiple changes can be bundled into one

1 0

[Dovecot] Solr not indexing
by Daniel L. Miller 26 Feb '12

26 Feb '12

What did I do wrong to make this happen? "doveadm(dmiller(a)amfes.com): Debug: fts: Indexes disabled for namespace 'shared/%n/'" doveadm -D fts rescan -u dmiller(a)amfes.com doveadm(root): Debug: Loading modules from directory: /usr/local/lib/dovecot doveadm(root): Debug: Module loaded: /usr/local/lib/dovecot/lib01_acl_plugin.so doveadm(root): Debug: Module loaded: /usr/local/lib/dovecot/lib20_fts_plugin.so doveadm(root): Debug: Module loaded: /usr/local/lib/dovecot/lib21_fts_solr_plugin.so doveadm(root): Debug: Loading modules from directory: /usr/local/lib/dovecot/doveadm doveadm(root): Debug: Module loaded: /usr/local/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so doveadm(root): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_lookup (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_zlib_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib10_doveadm_zlib_plugin.so: undefined symbol: i_stream_create_deflate (this is usually intentional, so just ignore this message) doveadm(root): Debug: Module loaded: /usr/local/lib/dovecot/doveadm/lib20_doveadm_fts_plugin.so doveadm(dmiller(a)amfes.com): Debug: Added userdb setting: mail=mdbox:/var/mail/amfes.com/dmiller/mdbox doveadm(dmiller(a)amfes.com): Debug: Added userdb setting: plugin/acl_groups='allshared' doveadm(dmiller(a)amfes.com): Debug: Effective uid=5000, gid=8, home=/var/mail/amfes.com/dmiller doveadm(dmiller(a)amfes.com): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mdbox:/var/mail/amfes.com/dmiller/mdbox doveadm(dmiller(a)amfes.com): Debug: fs: root=/var/mail/amfes.com/dmiller/mdbox, index=, control=, inbox=, alt= doveadm(dmiller(a)amfes.com): Debug: Namespace : Using permissions from /var/mail/amfes.com/dmiller/mdbox: mode=0700 gid=-1 doveadm(dmiller(a)amfes.com): Debug: acl: initializing backend with data: vfile:/usr/local/etc/dovecot/global-acls:cache_secs=300 doveadm(dmiller(a)amfes.com): Debug: acl: acl username = dmiller(a)amfes.com doveadm(dmiller(a)amfes.com): Debug: acl: owner = 1 doveadm(dmiller(a)amfes.com): Debug: acl vfile: Global ACL directory: /usr/local/etc/dovecot/global-acls doveadm(dmiller(a)amfes.com): Debug: Namespace : type=shared, prefix=shared/%n/, sep=/, inbox=no, hidden=no, list=children, subscriptions=no location=mdbox:/var/mail/%d/%n/mdbox doveadm(dmiller(a)amfes.com): Debug: shared: root=/usr/local/var/run/dovecot, index=, control=, inbox=, alt= doveadm(dmiller(a)amfes.com): Debug: fts: Indexes disabled for namespace 'shared/%n/' doveadm(dmiller(a)amfes.com): Debug: acl: initializing backend with data: vfile:/usr/local/etc/dovecot/global-acls:cache_secs=300 doveadm(dmiller(a)amfes.com): Debug: acl: acl username = dmiller(a)amfes.com doveadm(dmiller(a)amfes.com): Debug: acl: owner = 0 doveadm(dmiller(a)amfes.com): Debug: acl vfile: Global ACL directory: /usr/local/etc/dovecot/global-acls -- Daniel

2 3

[Dovecot] Maildir migration: Courier-imap 4.4.3 to Dovecot 1.2.
by Rafał Radecki 25 Feb '12

25 Feb '12

Hi all. I am currently gathering information about migration of Maildir/ structures from Courier to Dovecot. What do you think about http://wiki.dovecot.org/Migration/Courier ? For each courier Maildir account I want to use http://www.dovecot.org/tools/courier-dovecot-migrate.pl to produce dovecot-uidlist file mv courierimapsubscribed subscriptions sed sed -i 's/INBOX\.//' subscriptions rm -r courierimaphieracl rm courierimapacl rm courierimapkeywords I want also to leave default pop3_uidl_format (%08Xu%08Xv) in dovecot.conf Should I look into something else? Have I missed something? Best regards, Rafal.

3 2

[Dovecot] Apple od/ad authentication problem
by Troy Shafer 25 Feb '12

25 Feb '12

Hello all. Im pretty new to dovecot and postfix world. I'm completely stumped. OS X 10.7.3, behind a Cisco asa NAT. When trying to authenticate (ssl or not) via the webmail interface I get this error... NAT IP is the public ip I assigned. It doesn't work for an AD account or an account local to the Mac server. However it DOES work on the internal LAN. Feb 22 18:15:36 mail dovecot[3501]: auth: Error: od (username,natIP): verify plain: lookup failed for user: username Feb 22 18:15:51 mail dovecot[3501]: auth: Error: od[getpwnam_ext](username,natIP): No record for user I figured I'm missing something in the dovecot config. I have followed apple's kb articles for AD webmail authentication and kerberos, and that works internally.

2 3

[Dovecot] How to limit max number of connections for ip address
by Wilberth Perez 25 Feb '12

25 Feb '12

Hi List: Does any one , knows if is possible configure dovecot for limit max number of connections for IP address? I would like to prevent future fork-bombing attacks for pop3 and imap login process in my email server. Our dovecot version is : 1.2.10 Thanks, Wilberth.

3 4

[Dovecot] How to achieve proper privilege separation?
by "Tóth Attila" 24 Feb '12

24 Feb '12

I'm using a simple mbox config with regular Unix users and pam authentication. I'm also using grsecurity. That's why I see what dovecot does in which users' name. As times goes by and new versions are coming I can frustratedly see, that more and more tasks are performed as root. Why? When I used 1.x series of Dovecot, imap process started in the name of the user whose mbox was accessed. Now I can see, that nearly every task is performed by root. Why? It even tampers with the mail directories of each user as root instead of the user as it was usual long before. Please let me know how should I change the config to make dovecot stop using root privileges and revert it back to the old behavior. Thanks for your help: Dw. Here's my current config: dovecot -n # 2.0.17 (684381041dc4+): /etc/dovecot/dovecot.conf # OS: Linux 3.2.6-hardened i686 Gentoo Base System release 2.0.3 auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes auth_worker_max_count = 16 base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_gid = 99 first_valid_uid = 1000 hostname = host.name last_valid_gid = 65533 last_valid_uid = 1003 listen = * mail_access_groups = mail mail_full_filesystem_access = yes mail_gid = mail mail_location = mbox:~/mail/:INBOX=/var/spool/mail/%u mail_max_keyword_length = 150 mail_privileged_group = mail mail_uid = mail passdb { args = * driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = postmaster(a)host.name protocols = imap service auth-worker { user = root } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } service_count = 1 vsz_limit = 16 M } service imap { process_limit = 4 vsz_limit = 64 M } ssl_cert = </etc/apache2/ssl/cert-file.pem ssl_key = </etc/apache2/ssl/key-file.pem userdb { driver = passwd } verbose_proctitle = yes protocol lda { mail_plugins = sieve } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags imap_max_line_length = 64 k -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057

2 7

[Dovecot] From Maildir back to smtp
by Marc Perkel 24 Feb '12

24 Feb '12

Not sure how this can be done. Right now I'm running a free backup MX record service. People point their high MX records to my servers and if they go down we store the email. When they come back up it's delivered. What I want to do is have a premium service that would allow them to view through IMAP the stored email. In order to do that I would have to deliver the email locally to a dovecot server - to a single account perhaps - and they can view/forward/delete etc. But - when their server comes back online I'd like to gather up all the delivered email stored in Maildir format and run it back into smtp for delivery. Has anyone even done something like this? Or is there an easier way that I'm missing? Thanks in advance

4 4

[Dovecot] dsync 2.0.x versus 2.1.x field report
by Michael Grimm 24 Feb '12

24 Feb '12

Hi -- I used to run two mailservers with identical MX priorities (poor man's fail-over approach) with Maildir mail folders accessed by Dovecot. Synchronization has been achieved using unison, mirroring all files except dovecot index files. Once in a while some oddities could be observed, like reappearing of deleted mails, duplicates and such alike. But the all-over performance was quite good. Then I wanted to migrate to mdbox, and I became interested in dsync. I did start with 2.0.16 a couple of month ago, and recently upgraded to 2.0.18. My experience with the 2.0.x dsync version is as follows (synchronization time: every minute): -- As long as mail is not stored in corresponding mailboxes at both servers at the same time, all mailboxes become synchronized perfectly well, and no oddites like reappearing of deleted mails or generation of duplicates can be observed. -- If mail is stored into corresponding mailboxes at both servers simultaneously in between two synching runs, it gets worrying. -- If I do run dsync without '-f' those two mailboxes end up in becoming asynchronous. -- If I do run dsync with '-f' both mailboxes will become synchronized let's say in 95% of all synchronization runs. BUT in 5%, I do experience asynchronicity. Here a 'doveadm force-resync' sometimes works, but not always, what worries me a lot. -- I can see the missing mail in the mdbox storage file using UNIX' little helpers but not with the help of dovecot tools. (Or I was unable to use them properly.) -- Modifying MX priorities in a way, that I do now have a primary and backup mailserver scenario, very much reduced the risk of losing legitimate mail. -- But sometimes I do lose some syslog mail being produced at the same time. Therefore I modified runtimes in way to omit synchronicity. Ok, I could have lived with that, but I was anxious to learn, if 2.1.x dsync would perform better ;-) Here my observations sofar (synchronization time: every minute): -- No losses sofar using 'doveadm sync' with '-f' -- A *lot* of reappearing deleted mails or mails moved from one mailbox to the other. -- Quite often I am unable to delete those mails using client functionality (Mail.app, Roundcube). -- In those cases one needs to stop synchronization, run 'doveadm force-resync', delete all reappearing mail (quite a lot sometimes), empty 'Deleted' folders, and finally run 'doveadm purge'. -- Running of 'doveadm sync' without '-f' doesn't improve the situation. Still I do have to struggle with reappearing mails, and sometimes with appearing duplicates. -- I do have a test setup running for 24 hours now, where I do generate test mails in a 6 minutes interval at both servers. Mails become synchronized perfectly well, irrespectively if '-f' is set or not. This is a major improvement to 2.0x. dsync (sofar). -- But running the synchronization without '-f' still shows a *lot* of reappering mail, though. I do have the feeling that dsync became very much improved with regard to missing mail in synchronization, good. But those reappearing mails make me think about switching back to 2.0.x dsync and live with the drawback of preventing mail to arrive synchronously at both servers. Is someone out there experiencing a similar behaviour with dsync 2.1.x regarding reappearing, thus indelible mail? Regards, Michael

1 0