- dovecot - dovecot.org

Re: [Dovecot] Bug tracker
by interfaSys sàrl 11 Apr '12

11 Apr '12

I second that. New version 3.2 supports sub-projects, editions and components and is user-friendly. Cheers, Olivier > On Wed, Apr 11, 2012 at 09:26:20AM +0300, Timo Sirainen wrote: > > So, any suggestions for what software could do these things? I think > Request > Tracker has those features, but it's not really the nicest/prettiest > thing. > > May be worth to take a look at http://www.thebuggenie.com/. > > Thomas >

1 0

[Dovecot] Folder Aliases - Revisited Yet Again
by Daniel L. Miller 11 Apr '12

11 Apr '12

I just did a search through my archives - seems this topic has been requested a few times since my posting two years ago. I asked about a specific implementation - which Mr. Sirainen never commented on. He was probably focused on something more important at the time - like a paying job. So I'll ask again... Calling Timo! If we can't get clients to agree on a "standard" set of folders (probably reasonably safe assumption) and if protocol implementations of variations of "*LIST*" are too far in the future...what about having alternative folder names presented based on login name - maybe by an extension? So where my usual login might be "user(a)domain.com", and that would continue to be supported as the default login, I could now have "user(a)domain.com+thunderbird", "user(a)domain.com+mobile", etc.? And each of those extensions would then have a system-wide map defining folder name relationships, like "Sent=Sent Items". Does this seem doable? -- Daniel

2 4

[Dovecot] F5 SLB iRule - POP3 TLS Offload & Add Realm
by Lee Standen 11 Apr '12

11 Apr '12

Hey Guys, I figured someone might have use of this at some point. I've created an iRule for our F5 Load Balancer which performs the following tasks: - Appends STLS to the POP3 Capability list (it does this blindly, so expects the backend POP3 server to not return this) - Watches for the STLS command and initiates SSL negotiation with the client (leaves the connection to the backend POP3 server unencrypted) - Watches for the USER command (login attempt) and appends a realm if the user hasn't supplied one - Stops watching once a successful login occurs It's designed to be attached to port 110 and port 995 at the same time, and will disable SSL if the user is connecting to port 110 until the STLS command is issued. This is a first pass, so there's probably room for improvement, but it does seem to work. This will require LTM v10 (at least), as the SSL::collect command didn't exist prior to that version. Here's the rule: when CLIENT_ACCEPTED { if { [TCP::local_port clientside] == "110" } { # Disable SSL if we're on port 110 (as we're doing TLS Offload) set secure 0 SSL::disable } else { set secure 1 } set realm "mydomain.com" set debug 0 set loggedin 0 } when SERVER_CONNECTED { TCP::collect } when CLIENTSSL_HANDSHAKE { SSL::collect set secure 1 } when CLIENTSSL_DATA { if { $debug } { log local0. "CLIENT DATA: [SSL::payload]" } set lcpayload [string tolower [SSL::payload]] if { $lcpayload starts_with "user" } { scan [SSL::payload] {%s%s} command user set pos [string first $user [SSL::payload] 0] SSL::payload replace $pos [string length $user] "$user@$realm" if { $debug } { log local0. [SSL::payload] } } SSL::release if { $loggedin == 0 } { SSL::collect } } when CLIENT_DATA { if { $debug } { log local0. "CLIENT DATA: [TCP::payload]" } set lcpayload [string tolower [TCP::payload]] if { $lcpayload starts_with "stls" } { TCP::respond "+OK Begin TLS negotiation\r\n" TCP::payload replace 0 [TCP::payload length] "" TCP::release SSL::enable return } elseif { $lcpayload starts_with "user" } { scan [TCP::payload] {%s%s} command user set pos [string first $user [TCP::payload] 0] TCP::payload replace $pos [string length $user] "$user@$realm" if { $debug } { log local0. [TCP::payload] } } TCP::release if { $loggedin == 0 } { TCP::collect } } when SERVER_DATA { if { $debug } { log local0. "SERVER DATA: [TCP::payload]" } set lcpayload [string tolower [TCP::payload]] if { $lcpayload starts_with "+ok logged in" } { TCP::release set loggedin 1 event disable if { $debug } { log local0. "POP3 Login Successful" } return } elseif { $lcpayload contains "capa" } { TCP::payload replace [expr [TCP::payload length] - 3] 0 "STLS\r\n" } if { $secure == 1 && $loggedin == 0 } { clientside { SSL::collect } } elseif { $secure == 0 && $loggedin == 0 } { clientside { TCP::collect } } TCP::release if { $loggedin == 0 } { TCP::collect } }

1 0

[Dovecot] sieve replace dot string for foldername
by Robert Schetterer 11 Apr '12

11 Apr '12

Hi, i am playing about mail archive this is what allready works for me require ["variables","date","fileinto","mailbox","envelope","subaddress","regex"]; # Extract date info if currentdate :matches "year" "*" { set "year" "${1}"; } if currentdate :matches "month" "*" { set "month" "${1}"; } if currentdate :matches "day" "*" { set "day" "${1}"; } if envelope :detail :matches "to" "*" { set "to" "${1}"; } if true { fileinto :create "INBOX.${year}.${month}.${day}.${to}"; stop; } but ${to} may have a dot included, foldernames with dot are not allowed in my dove setup yet ( and i dont want to change it ) i am looking for a way ( guess regex ) for replace a dot in string replaced by a space char on the fly -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 2

[Dovecot] Username from rfc822Name subject alternative name
by Бранко Мај ић 11 Apr '12

11 Apr '12

Hello, I'm looking into adding support for extracting the username from client certificate's rfc822Name (from the subjectAltName extension). The question I have is what would be the best approach to do this? Current implementation has a kind of clean code since it just goes through the subject name, extracting the values with X509_NAME_get_text_by_NID (while NID is obtained with OBJ_txt2nid). If I were to add this, it's bound to make the code a little bit more complicated since SAN's can't be retrieved in the same way. So far in terms of options I have, I can see the following: 1. Create a distinct configuration option for the ssl_cert_username_field (i.e. specify something like "sanrfc822Name" to have Dovecot extract the username from the designated alternative name). 2. Make the current code fail-over to rfc822Name SAN if emailAddress is provided for ssl_cert_username (less invasion in code, but less flexibility as well). Any input/recommendation/directioning is welcome. I've wanted to actually first write a patch, and then submit it, but I think it might be better to check what would be preferable by Dovecot maintainers/devs. Best regards -- Branko Majic Jabber: branko(a)majic.rs Please use only Free formats when sending attachments to me. Бранко Мајић Џабер: branko(a)majic.rs Молим вас да додатке шаљете искључиво у слободним форматима.

3 3

[Dovecot] Dsync test on 2.1.3
by Jitendra Bhaskar 10 Apr '12

10 Apr '12

Hi, I am using dovecot version 2.1.3 on centos. I tested dsync from my live server to one of backup server. But I got that its working for most of the user and there is problem for few user. Some users got duplicated mail to their mailbox and I saw there is some extra folders i.e Sent Items_* , Draft_* and Trash_* in few users mail box. and I synced only from main server to backup server. I didn't enable mail_plugin in backup server. My configuration for testing of Dsync on master server is as: mail_plugins = $mail_plugins notify replication service aggregator { fifo_listener replication-notify-fifo { user = vmail mode = 0666 } unix_listener replication-notify { user = vmail mode = 0666 } } service replicator { # start replication at startup process_min_avail = 1 } plugin { #host1 replicates to host2 mail_replica = remote:root@backup_server } #dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u -l%{lock_timeout} -n%{namespace} dsync_remote_cmd = ssh -l root %{host} doveadm dsync-server -u%{user} -l%{10} -n%{namespace} service doveadm { user = root } And in backup server : service doveadm { user = root } 1. Problem is I am not getting why some user getting lots of duplicate mails. 2. Why duplicate folders like Sent Items_* and Trash_* created for few users 3. I used only one way syncing then why both replicated. Note: i am using root only for testing purpose * Thanks & Regards * *Jitendra Kumar Bhaskar* Cell:- +91 7306311531 +91 8102997821

1 0

[Dovecot] Authentication mechanism and Password scheme
by Костырев Александр Алексеевич 10 Apr '12

10 Apr '12

Good day! I'm just trying to figure out that my understanding of subject is correct. So, if I want to store passwords in my database encrypted with SSHA512 scheme, my only choice for Authentication mechanism is plaintext? Thanks in advance! -- С уважением, Костырев Александр системный администратор ЗАО "Сервер-Центр" тел.: (423) 262-02-62 (доб. 2037) факс: (423) 262-02-10

3 3

[Dovecot] Per IP virtual domain
by Stéphane Locatelli 10 Apr '12

10 Apr '12

Hello, My dovecot server (2.0.18 on FreeBSD 9) has multiple interface. I would like to configure the authentication (pop and imap) to append different domain according to the local IP address. I've tested this: local 10.0.0.1 { auth_default_realm = domain1.com } local 10.0.0.2 { auth_default_realm = domain2.com } But it doesn't work. I get this error message: doveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/dovecot.conf line 58: Auth settings not supported inside local/remote blocks: auth_default_realm -- Stephane Locatelli

2 2

[Dovecot] 2.0/2.1 - different behavior for LIST-EXTENDED
by Peter Mogensen 10 Apr '12

10 Apr '12

Hi Timo, We are sitting here wondering if this difference in behaviour between dovecot 2.0.17 and 2.1.3 is intended. When you create a folder, subscribe to it and rename it (without changing the subscription) these are the behaviours: For 2.0.17: . list (SUBSCRIBED) "" "*" RETURN (STATUS (MESSAGES)) * LIST (\Subscribed \NonExistent) "." "INBOX.test" For 2.1.3: . list (SUBSCRIBED) "" "*" RETURN (STATUS (MESSAGES)) * LIST (\Subscribed) "." "INBOX.test" * NO Mailbox doesn't exist: test If you don't use rfc5819 the folder will just get silently ignored by dovecot 2.1.x, but if you actually try to get the number of messages you'll get the error. It seems to me from reading rfc5258 that the 2.0.x behaviour is the correct ?? /Peter

2 1

[Dovecot] Problem with quota warning
by Patrick Westenberg 10 Apr '12

10 Apr '12

Hi again, my test environment is working now and finally I tried to implement my quota warning but it is not working. LDA says the mailbox is full even it is not (only 81% and that is why the quota warning is executed). Further I used :noenforcing in my script. Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: Namespace INBOX.: Using permissions from /var/mail/k-team.info/test/mdbox: mode=0700 gid=-1 Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: Quota root: name=User quota backend=dict args=:file://mdbox/dovecot-quota:noenforcing Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: Quota warning: bytes=0 (90%) messages=0 reverse=no command=quota-warning 90 raw mail user Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: Quota warning: bytes=0 (75%) messages=0 reverse=no command=quota-warning 75 raw mail user Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: dict quota: user=raw mail user, uri=file://mdbox/dovecot-quota:noenforcing, noenforcing=0 Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: none: root=, index=, control=, inbox=, alt= Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: Destination address: test(a)k-team.info (source: user@hostname) Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): msgid=unspecified: save failed to INBOX: Quota exceeded (mailbox for user is full) Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): msgid=unspecified: rejected: Quota exceeded (mailbox for user is full) Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): msgid=: Return-Path missing, rejection reason: Quota exceeded (mailbox for user is full) # 2.1.3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.4 auth_debug = yes auth_debug_passwords = yes auth_verbose = yes listen = 172.17.99.96 mail_debug = yes mail_gid = vmail mail_home = /var/mail/%d/%n mail_location = mdbox:~/mdbox:INDEX=/var/indexes/%d/%n mail_plugins = quota mail_uid = vmail 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 namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { autocreate = INBOX.Sent autocreate2 = INBOX.Trash autocreate3 = INBOX.Drafts autocreate4 = INBOX.Spamverdacht autosubscribe = INBOX.Sent autosubscribe2 = INBOX.Trash autosubscribe3 = INBOX.Drafts autosubscribe4 = INBOX.Spamverdacht quota = dict:User quota::file:%h/mdbox/dovecot-quota quota_rule2 = INBOX.Trash:storage=+100M quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=75%% quota-warning 75 %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve } protocols = imap pop3 lmtp sieve service auth { unix_listener auth-userdb { user = vmail } } service imap-login { service_count = 1 } service lmtp { inet_listener lmtp { address = 172.17.99.96 port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } service quota-warning { executable = script /usr/local/etc/dovecot/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl = required ssl_cert = </etc/ssl/certs/imap.wk-serv.de.crt ssl_key = </etc/ssl/certs/imap.wk-serv.de.key userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota sieve } protocol imap { mail_plugins = quota imap_quota autocreate } protocol pop3 { pop3_client_workarounds = oe-ns-eoh, outlook-no-nuls } #!/bin/sh PERCENT=$1 USER=$2 cat << EOF | /usr/local/libexec/dovecot/dovecot-lda -d $USER -o "plugin/quota=dict:User quota::file:%h/mdbox/dovecot-quota:noenforcing" From: support(a)example.com Reply-To: support(a)example.com Subject: Speicherplatz Ihrer Mailbox ...

2 5

[Dovecot] Multiply mailboxes vs one huge
by Alexander Chekalin 10 Apr '12

10 Apr '12

Hello, as I need to store a lot of messages on my IMAP server (order of 900K-1000K; this is an archive for some time, maybe a year or so), I see some "slowness" in dealing with such a huge amount. I mainly need to do searches like "get all messages from user1(a)domain1.com to user2(a)domain2.tld recieved between date1 and date2". So I really interested will it be wise to a) split all messages into several smaller mailboxes (per-month, or per-day, or create 2-level-structure like "month/day/") b) use dbox (vs currently used mbox) storage scheme (I'm afraid of mdbox as I still not sure I'll be able to parse it by scripts later "just in case") Dovecot is the latest one (2.1.3). No compression Dovecot-side, but it mails are in zfs volume with compression on. I ask this mainly due to my not fully understand how Dovecot indexes are working. I also test another approach: to use my own index somewhere outside Dovecot which will store reference between emails and UIDs, and dates and UIDs, so I'll simple query my index for things I need. But then, that's exactly what IMAP index can do, so I simple slow my search down, isn't it? The only reason I think about my own index is I won't use 'all header' as search scope, I need to deal only with From:, To:, Cc:, Bcc: (if any), Recieved (if nowehere else I see the from/to info), and date field(s) - I doubt IMAP will care for that for me. Yours, Alexander

2 3

[Dovecot] v2.1.4 released
by Timo Sirainen 10 Apr '12

10 Apr '12

http://dovecot.org/releases/2.1/dovecot-2.1.4.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.4.tar.gz.sig + Added mail_temp_scan_interval setting and changed its default value from 8 hours to 1 week. + Added pop3-migration plugin for easily doing a transparent IMAP+POP3 migration to Dovecot: http://wiki2.dovecot.org/Migration/Dsync + doveadm user: Added -m parameter to show some of the mail settings. - Proxying SSL connections crashed in v2.1.[23] - fts-solr: Indexing mail bodies was broken. - director: Several changes to significantly improve error handling - doveadm import didn't import messages' flags - mail_full_filesystem_access=yes was broken - Make sure IMAP clients can't create directories when accessing nonexistent users' mailboxes via shared namespace. - Dovecot auth clients authenticating via TCP socket could have failed with bogus "PID already in use" errors.

3 3

[Dovecot] mount
by Luigi Rosa 09 Apr '12

09 Apr '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a Dovecot installation on CentOS 5 where I sometimes mount external fs in /mnt Every Dovecot data is in local / file system, nothing is mounted elswhere After upgrading to 1.2.4 I rebooted the system for other reasons and at startup I got this on Dovecot log: master: Warning: /mnt is no longer mounted. If this is intentional, remove it with doveadm mount No /mnt entry in /etc/fstab and nothing pmounted under /mnt I THINK that the last time I used /mnt to mount something was few weeks ago to update VMware tools. Is there a way toi tell Dovecot to ignore /mnt ? Ciao, luigi - -- / +--[Luigi Rosa]-- \ $100 invested at 7% interest for 100 years will become $100,000, at which time it will be worth absolutely nothing. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+C58gACgkQ3kWu7Tfl6ZRc0wCgl0Z4OtblYbfYwzvOp1/vUifV PqYAoIvfltvmq3cijvDbOEKV2Tai2rpu =hyrI -----END PGP SIGNATURE-----

2 2

[Dovecot] Director pop-login and imap-login processes exiting on signal 11
by Andy Dills 09 Apr '12

09 Apr '12

We recently upgraded our cluster to 2.1.3, to enable director proxying. Everything appears to be working fine for the most part; the only odd thing is that I'm seeing a lot of entries in the logs like this: Apr 7 02:18:05 mail-out06 dovecot: pop3-login: Fatal: master: service(pop3-login): child 75029 killed with signal 11 (core not dumped - set service pop3-login { drop_priv_before_exec=yes }) This is on the proxy side, not that backend side. When I try to get a dump out of it, and add drop_prive_before_exec and chroot= to the pop3-login statement on the proxy, I keep running into permissions errors with the various service sockets. Any suggestions? Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 ---

2 2

[Dovecot] v2.0.20 released
by Timo Sirainen 09 Apr '12

09 Apr '12

http://dovecot.org/releases/2.0/dovecot-2.0.20.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.20.tar.gz.sig + doveadm user: Added -m parameter to show some of the mail settings. - doveadm import didn't import messages' flags - Make sure IMAP clients can't create directories when accessing nonexistent users' mailboxes via shared namespace. - Dovecot auth clients authenticating via TCP socket could have failed with bogus "PID already in use" errors.

1 0

[Dovecot] Director simplification?
by Timo Sirainen 09 Apr '12

09 Apr '12

An idea I just had: Director basically works by assigning the backend IP address by: ip = vhosts[ md5(username) mod vhosts_count ].ip The rest of director is about what happens when vhosts[] or vhosts_count changes. What about instead doing this on IP address level? ip = ip_pool[ md5(username) mod ip_pool_size ] When a backend dies, you'll reassign the backend's IPs to other backends. Each backend should have many IPs. The main restriction here is that the IP pool cannot change without stopping the entire Dovecot. But if you initially allocate enough IPs, that shouldn't be a problem. And the advantage of this over the current director? To guarantee that one director can't break others, because they don't need to communicate with each others. The disadvantage of course is that it's a little less flexible and requires more planning ahead. The IP address reassignment would also need some distro-specific scripts. This could be implemented as an alternative director-lite or something. The doveadm director status-related commands could still work with it.

1 0

[Dovecot] Outlook (2010) -> Dovecot (IMAP) >10x slower with high network load and many folders
by Thomas von Eyben 09 Apr '12

09 Apr '12

Hi, I am seeing a >10x as slow performance when trying to complete a "send/receive" from an Outlook 2010 client to Dovecot via IMAP, but only when the LAN is fully loaded with other traffic, EG file copying. It seems the problem is when outlook is trying to identify folders that have changed since last "send/receive" thus traversing the hierachy. Observations: - Apple's Mail.app does not have problems when exposed to the same environment. - Eliminating Outlook is not an option. - The tests have been performed during the easter vacation, thus almost no other clients are using the network/mailserver. Under normal load there are 2-300 users using the network. Description of the environment: Server sw: Mac OS X Server 10.6.8 running dovecot: 1.1.20apple0.5 (OS = fully updated 10.6.x) Server hw: Xserve Quadcore intel Xeon 2.26 GHz 12 GB RAM - Never having a cpu load > 20%, mail is stored on a Promise vtrack RAID connected via Fibre Channel Client: Windows 7, Outlook 2010 The client have maybe 50 folders (and each folder about a handfull of subfolders) the size of the mailbox is around 3-5 GB. Test results: CLIENT-1 is having the problems when CLIENT-2 is using all the (100Mbps) bandwidth eg. copying files to MAIL-SRV. If I move CLIENT-1 to CLIENT-3 then almost all the delay is gone. NB.: I have not (yet) tested if the problem also exists when CLIENT-2 generates traffic to MAIL-SRV as opposed to OTHER-SRV (but I am expecting the same problems). When dumping the traffic on CLIENT-1 (with Wireshark) one thing is catching my eyes for the 'bad' case: There is a very long delay after each "REQUEST IDLE" until the next "REQUEST DONE" ca. 0,3 seconds. Comparing to the 'good' setup the pause at the same place in the communication is less than 1 ms ! So why this delay? Where/how shall I continue my debugging? - Run dtruss/dtrace scripts on the server? - Get dovecot to output more debug info (I guess it's doing it's best so no problems will be seen there…)? Are there any dovecot configurations that can be altered to workaround [what I think is a limitation in Outlook's IMAP implementation]? The current dovecot configuration is Apple's defaults (+POP3 disabled)) I am seing one warning from dovecotd -n though: - But I see the same warning on a clean installed not-yet-configured OS X Server so I guess it's not 'that' bad: Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 456). Either grow the limit or change login_max_processes_count and max_mail_processes settings Physical setup: +---------------+ +------------------------------+ +-----------------+ | CLIENT-1 | | CLIENT-2 | | CLIENT-3 | | Outlook "bad" | | Traffic generator, eg. Samba | | Outlook "good" | +---------------+ +------------------------------+ +-----------------+ | | | +-------------------------------------------------+ | | 100Mbps switch (clients) | | +-------------------------------------------------+ | | | +------------------------------------------------------------------------+ | 1Gbps switch (for servers) | +------------------------------------------------------------------------+ | | +-----------------------------+ +-----------+ | MAIL-SRV: Dovecot, AFP, SMB | | OTHER-SRV | +-----------------------------+ +-----------+ Wireshark dump - IMAP communication: |Time | 10.211.55.3 | | | | 10.0.0.10 | |9.851 | Response: gatq OK L |IMAP: Response: gatq OK Logged in. | |(49433) <------------------ (143) | |9.852 | Request: o47u SELEC |IMAP: Request: o47u SELECT "1_GROUPS" | |(49433) ------------------> (143) | |9.853 | Response: * FLAGS ( |IMAP: Response: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) | |(49433) <------------------ (143) | |9.854 | Request: 3y4b NOOP |IMAP: Request: 3y4b NOOP | |(49433) ------------------> (143) | |9.854 | Response: 3y4b OK N |IMAP: Response: 3y4b OK NOOP completed. | |(49433) <------------------ (143) | |9.855 | Request: 4vlj IDLE |IMAP: Request: 4vlj IDLE | |(49433) ------------------> (143) | |9.856 | Response: + idling |IMAP: Response: + idling | |(49433) <------------------ (143) | |10.108 | Request: DONE |IMAP: Request: DONE | |(49433) ------------------> (143) | |10.108 | Response: 4vlj OK I |IMAP: Response: 4vlj OK Idle completed. | |(49433) <------------------ (143) | |10.108 | Request: wh89 SELEC |IMAP: Request: wh89 SELECT "1_GROUPS.Adm" BR Thomas von Eyben

4 4

[Dovecot] Setting ACL for master user after login
by PL MB 09 Apr '12

09 Apr '12

Hello, I'd like to log in to normal user accounts as a master user but retain the normal users' ACLs. The Master Users page on the Dovecot 1.x wiki (1) says that I can set the master user's ACLs in a postlogin script. The documentation for master users on the 2.x wiki (2) no longer has any statements about master user ACLs. Has something important in this regard changed? Can I no longer override the ACLs in a postlogin script? Thanks in advance. (1) http://wiki.dovecot.org/Authentication/MasterUsers (2) http://wiki2.dovecot.org/Authentication/MasterUsers

2 1

[Dovecot] POP3 dele to Trash?
by Kelsey Cummings 09 Apr '12

09 Apr '12

To simplify recovery of accidentally deleted messages we'd like to send all messages that are deleted by pop clients to their Trash folder. (Which is auto expired already.) This allows a POP client who deletes an important email to restore it themselves by logging into our webmail client and move the lost message from Trash to the Inbox where it would be fetched by their client again. Has anyone already done this? Should this be possible via a plugin? I see the deleted-to-trash imap plugin. We are using Maildir if it makes a difference. -- Kelsey Cummings - kgc(a)corp.sonic.net sonic.net, inc. System Architect 2260 Apollo Way 707.522.1000 Santa Rosa, CA 95407

2 2

[Dovecot] distributed mdbox
by James Devine 09 Apr '12

09 Apr '12

Anyone know how to setup dovecot with mdbox so that it can be used through shared storage from multiple hosts? I've setup a gluster volume and am sharing it between 2 test clients. I'm using postfix/dovecot LDA for delivery and I'm using postal to send mail between 40 users. In doing this, I'm seeing these errors in the logs Mar 21 09:36:29 test-gluster-client2 dovecot: lda(testuser34): Error: Fixed index file /mnt/testuser34/mdbox/storage/dovecot.map.index: messages_count 272 -> 271 Mar 21 09:36:30 test-gluster-client2 dovecot: lda(testuser28): Error: Log synchronization error at seq=4,offset=3768 for /mnt/testuser28/mdbox/storage/dovecot.map.index: Append with UID 516, but next_uid = 517 Mar 21 09:36:30 test-gluster-client2 dovecot: lda(testuser28): Error: Log synchronization error at seq=4,offset=4220 for /mnt/testuser28/mdbox/storage/dovecot.map.index: Extension record update for invalid uid=517 Mar 21 09:36:30 test-gluster-client2 dovecot: lda(testuser28): Error: Log synchronization error at seq=4,offset=5088 for /mnt/testuser28/mdbox/storage/dovecot.map.index: Extension record update for invalid uid=517 Mar 21 09:36:30 test-gluster-client2 dovecot: lda(testuser28): Warning: fscking index file /mnt/testuser28/mdbox/storage/dovecot.map.index Mar 21 09:36:30 test-gluster-client2 dovecot: lda(testuser34): Warning: fscking index file /mnt/testuser34/mdbox/storage/dovecot.map.index This is my dovecot config currently: jdevine@test-gluster-client2:~> dovecot -n # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 3.0.0-13-server x86_64 Ubuntu 11.10 lock_method = dotlock mail_fsync = always mail_location = mdbox:~/mdbox mail_nfs_index = yes mail_nfs_storage = yes mmap_disable = yes passdb { driver = pam } protocols = " imap" ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd }

5 19

[Dovecot] Using a namespace for providing access to mail snapshots for user based on-demand restoration of email backups
by Charles Marcus 09 Apr '12

09 Apr '12

Hi all, I'm planning on implementing this in my new upcoming dovecot instance, and would like to hear thoughts on how best to accomplish this. We will be paying Timo's support company to do the work, but obviously, the less work in the form of coding he has to do to get this working (I'm hoping it won't be a lot), the more money it will save us... ;) First - I currently use rsnapshot to backup emails, so that is the use-case I'm most interested in getting working. It is rsync based, and like other rsync based backup programs it uses hardlinks to save storage space - so you can have a *lot* of backups (going back months, or even years), where each snapshot only adds a little more to the total disk space being used. The snapshots are stored with the following filesystem layout: /path/to/snapshotsdir/hourly.0 ... /path/to/snapshotsdir/hourly.4 /path/to/snapshotsdir/daily.0 ... /path/to/snapshotsdir/daily.7 /path/to/snapshotsdir/weekly.0 ... /path/to/snapshotsdir/weekly.4 /path/to/snapshotsdir/monthly.0 ... /path/to/snapshotsdir/monthly.12 /path/to/snapshotsdir/yearly.0 ... /path/to/snapshotsdir/yearly.5 The 'names' (hourly, daily, weekly, monthly, yearly) are arbitrary (this is a bit confusing to people new to rsnapshot), and would *not* be used for displaying the mail folders to the users - it is the Date/Time stamps of each of the snapshot dirs above that would be used to display the folder names under the 'Time Machine' namespace. This is, I imagine, the part that will need some actual coding by Timo to get working - maybe just some new config variables added to the namespace code for mapping the date/time stamps of the directories to user friendly folder names in the namespace. That said, I'd like to design this and have it coded such that it will work with almost any type of backup storage that stores snapshots as date/time stamped directories like this (there must be others, right?). Also, it goes without saying that this code will be (if Timo is ok with it) part of the core dovecot code going forward, so anyone else will be able to benefit from it. What I'm envisioning is something like this... 1. Define a namespace - for this example we'll call it 'Time Machine' 2. Under this namespace, each user will see their, and *only* their snapshots So, each user would see something like this: My Mail Account Inbox Drafts Templates Sent Time Machine (sorted above user created folders if possible) -4/3/12, 8:00am (first subfolder) Inbox Drafts etc... (all other folders and sub-folders shown here) +4/3/12, 12:00pm (first subfolder) etc... Other User Folders ... Or even better, I'm thinking some magical code that can group them by Date, like: -4/3/12 (first subfolder) -8:00am (next sub-folder) Inbox Drafts Etc... (all folders and sub-folders shown here) +12:00pm +4:00pm +8:00pm +4/4/12 etc... Comments? Suggestions? Flames? -- Best regards, Charles

3 4

Re: [Dovecot] Using a namespace for providing access to mail snapshots for user based on-demand restoration of email backups
by Joseph Tam 09 Apr '12

09 Apr '12

A timely topic as I was just mulling over ways to provide this to my users. Charles Marcus wrote: > The snapshots are stored with the following filesystem layout: > > /path/to/snapshotsdir/hourly.0 > ... This is familiar to NetApp users. > The 'names' (hourly, daily, weekly, monthly, yearly) are arbitrary (this > is a bit confusing to people new to rsnapshot), and would *not* be used > for displaying the mail folders to the users - it is the Date/Time > stamps of each of the snapshot dirs above that would be used to display > the folder names under the 'Time Machine' namespace. This is, I imagine, > the part that will need some actual coding by Timo to get working - > maybe just some new config variables added to the namespace code for > mapping the date/time stamps of the directories to user friendly folder > names in the namespace. > > That said, I'd like to design this and have it coded such that it will > work with almost any type of backup storage that stores snapshots as > date/time stamped directories like this (there must be others, right?). One idea is to take this complexity entirely out of dovecot and create a synthetic filesystem using hard or soft links (as rsnapshot has done) and create your own, with whatever weird and wonderful naming scheme you want. /path/to/TimeMachine/<friendlylabel>/<user> -> /path/to/snapshotsdir/<snaplabel>/<user> namespace { prefix = TimeMachine location = maildir:/path/to/TimeMachine:INDEX=MEMORY ... } This might not be very scalable depending on how big your userbase is. I would probably define memory indices for this namespace, and take the performance hit on the assumption that access will be a once-in-a- while thing. On-disk indices will probably get out of date with each snapshot rollover, if if you have a lot of snapshots/mailboxes, it could consume a non-trivial amount of space without a lot of benefits. Or you could run a cron script to rename or remove old indices, but that seems more trouble than it's worth. One other consideration (at least for me) is if the INBOX and personal mail folders are stored in two separate FS's. It would be nice to fuse the two sets of backups under the same namespace, but I don't know how the namespace prefix matching works and whether you can define hierarchical namespaces like namespace { prefix = backup/inbox location = mbox:/path/to/inbox-snapdir/%u ... } namespace { prefix = backup/mail location = mbox:/path/to/mail-snapdir/%u ... } The above can also be accomplished with a synthetic filesystem. Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] 2.1.3: Overly lax FETCH parsing
by Michael M Slusarz 09 Apr '12

09 Apr '12

These commands both work in Dovecot (as of 2.1.3): 1 UID FETCH 1:* () (CHANGEDSINCE 1) * 1 FETCH (UID 30097 MODSEQ (19554)) [...] 1 OK Fetch completed. 2 FETCH 1:* () (CHANGEDSINCE 1) * 2 FETCH (MODSEQ (19554)) [...] 2 OK Fetch completed. However, RFC 3501 indicates that an empty FETCH attribute list is incorrect: fetch = "FETCH" SP sequence-set SP ("ALL" / "FULL" / "FAST" / fetch-att / "(" fetch-att *(SP fetch-att) ")") fetch-att = "ENVELOPE" / "FLAGS" / "INTERNALDATE" / "RFC822" [".HEADER" / ".SIZE" / ".TEXT"] / "BODY" ["STRUCTURE"] / "UID" / "BODY" section ["<" number "." nz-number ">"] / "BODY.PEEK" section ["<" number "." nz-number ">"] In other words, fetch-att is not allowed to be empty. (RFC 4466 does not alter this requirement when using FETCH modifiers). While useful that Dovecot is more liberal about what it receives, 3501 seems pretty clear that incorrect FETCH parameters must return a BAD. I can verify that the above commands fail on Cyrus. I don't disagree that the way Dovecot handles this is correct - or at least is the way that I wish the RFCs were written. Since this seems a bit redundant, but is necessary under the ABNF: 1 UID FETCH 1:* UID (CHANGEDSINCE 1) -or- 1 UID FETCH 1:* (UID) (CHANGEDSINCE 1) michael

2 1

[Dovecot] lmtp sometimes fails to deliver a message to all recipients
by Artur Zaprzała 09 Apr '12

09 Apr '12

Dovecot version: 2.1.3 lmtp config: protocol lmtp { mail_plugins = zlib acl sieve } Running strace on lmtp reveals that when lmtp delivers a message to multiple recipients it saves the message to a file in the first mailbox and hard links that file to other mailboxes. But when in the meantime of delivery that file is deleted, lmtp fails to deliver the message to remaining mailboxes. For example a message for 46 recipients is delivered by lmtp to the first 12 only (fortunately postfix retries delivery for remaining recipients) and for the rest lmtp logs the following error messages: lmtp(3344, foo@domain): Error: RU1WMnueeU9QDQABxjIODQ: sieve: msgid=unspecified: failed to store into mailbox 'INBOX': Message was expunged (guid) lmtp(3344, foo@domain): Error: RU1WMnueeU9QDQABxjIODQ: sieve: script /vmail/domain/foo/.dovecot.sieve failed with unsuccessful implicit keep (user logfile /vmail/domain/foo/.dovecot.sieve.log may reveal additional details) I'm seeing this error for about 10 messages per hour. Best regards, Artur Zaprzała

2 3

[Dovecot] Problem with polish characters and sieve fileinto
by l.chelchowski＠eurocar.pl 06 Apr '12

06 Apr '12

Hi, I have problems with sieve fileinto and polish characters in folder names: # rule:[ąćęłńóśźżĄĆĘŁŃÓŚŹŻ] elsif anyof (header :contains "Subject" "ąćęłńóśźżĄĆĘŁŃÓŚŹŻ") { fileinto "INBOX/&AQUBBwEZAUIBRADzAVsBegF8AQQBBgEYAUEBQwDTAVoBeQF7-"; } dovecot log: Apr 5 15:17:42 mailer dovecot: lmtp(54203, test(a)test1.com) rmHVJHabfU+70wAA9hAjDg: sieve: msgid=<4F7D9B68.4030206(a)test2.com>: stored mail into mailbox 'INBOX' Apr 5 15:17:42 mailer dovecot: lmtp(54203, test(a)test1.com) Error: rmHVJHabfU+70wAA9hAjDg: sieve: execution of script /home/vmail/test1.com/test//.dovecot.sieve failed, but implicit keep was successful (user logfile /home/vmail/test1.com/test//.dovecot.sieve.log may reveal additional details) Apr 5 15:17:42 mailer postfix/lmtp[54202]: 941B1E2681F: to=<test(a)test1.com>, relay=m.test1.com[private/dovecot-lmtp], delay=0.04, delays=0/0.01/0/0.03, dsn=2.0.0, status=sent (250 2.0.0 <test(a)test1.com> rmHVJHabfU+70wAA9hAjDg Saved) dovecot.sieve.log: sieve: info: started log at Apr 05 15:17:42. error: msgid=<4F7D9B68.4030206(a)test2.com>: failed to store into mailbox 'INBOX/&AQUBBwEZAUIBRADzAVsBegF8AQQBBgEYAUEBQwDTAVoBeQF7-' (INBOX/&-AQUBBwEZAUIBRADzAVsBegF8AQQBBgEYAUEBQwDTAVoBeQF7-): Mailbox doesn't exist: INBOX.&-AQUBBwEZAUIBRADzAVsBegF8AQQBBgEYAUEBQwDTAVoBeQF7-. Thanks for help. -- Pozdrawiam Łukasz

3 3