- dovecot - dovecot.org

[Dovecot] Shared mailboxes with dovecot problem service=lib-storage
by Tomislav Mihalicek 29 Mar '12

29 Mar '12

Hi Could someone explain what this strings mean in dovecot 2.1.3 debug log? Mar 27 11:18:11 cartman dovecot: auth: Debug: master in: USER 1 test1(a)example.net service=lib-storage Mar 27 11:18:11 cartman dovecot: auth: Debug: master in: USER 2 test2(a)example.net service=lib-storage -- View this message in context: http://old.nabble.com/Shared-mailboxes-with-dovecot-problem-service%3Dlib-s… Sent from the Dovecot mailing list archive at Nabble.com.

2 1

[Dovecot] Namespace, prefix questions
by Steve Campbell 29 Mar '12

29 Mar '12

We've got some users who are using Outlook Express version 6. The client allows me to specify the root folder, but not a prefix or namespace. I'm still struggling with some users on our new server that have crazy imap folder layouts, so I've got a few questions. When I specify the root folder, does that bypass any namespace/prefix definitions on the imap server? On some clients, like Thunderbird, I have the option of specifying namespace OR prefix. How do these differ? I thought that the prefix was the "name" of the namespace. It appears that I have to delete and re-create the account on these OE 6 clients to make the list of folders show properly. Does that sound right? This all came about because one of these OE 6 users was not able to use their imap folders (server errors). Turns out it was one of the users that had their folders directly under ~. So I moved them to ~/mail, created a .subscriptions file from their .mailboxlist file and tried everything in the world to get the folders to list properly. Only after specifying the root folder as ~/mail after recreating the account and restarting OE did it show properly and the folders remained listed. My default config has this setup as the "mail_location" parm, but blanks as the root folder don't seem to work in this situation. I'm also wondering where I specify the "list", "hidden" and other parms that are usually set in namespace blocks. dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-220.4.1.el6.x86_64 x86_64 CentOS release 6.2 (Final) disable_plaintext_auth = no listen = * mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u mbox_write_locks = fcntl namespace { hidden = yes inbox = yes list = yes location = mbox:~/mail:INBOX=/var/spool/mail/%u prefix = separator = / type = private } namespace { hidden = yes list = no location = mbox:~/mail:INBOX=/var/spool/mail/%u prefix = "#mbox/" separator = / type = private } namespace { hidden = yes list = no location = prefix = mail/ separator = / type = private } namespace { hidden = yes list = yes location = mbox:~/mail:INBOX=/var/spool/mail/%u prefix = ~/mail/ separator = / type = private } namespace { hidden = yes list = no location = prefix = ~%u/mail/ separator = / type = private } passdb { driver = pam } protocols = pop3 imap ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } Thanks steve campbell Thanks steve campbell

2 2

[Dovecot] fts-solr not indexing body content
by Bård Johannessen 29 Mar '12

29 Mar '12

This could easily be me missing something, but I can't seem to get the fts-solr plugin to index message bodies. Tcpdump shows me the following being sent from Dovecot to Solr as a messages is indexed: <add><doc><field name="uid">6549</field><field name="box">fde08816e80d6b4f26650000b5f0b4b2</field><field name="user">user</field><field name="id">6549/fde08816e80d6b4f26650000b5f0b4b2/user</field><field name="body"> </field><field name="hdr">Return-path: ... As you can see, the <field name="body"/>-node contains just an empty line. The above is just a snippet to illustrate the problem. A full dump can be found at the following URL: http://db.org/temp/solr.xml.txt Full text search is configures such: plugin { fts = solr fts_solr = break-imap-search url=http://127.0.0.1:8080/solr/ } So; am I missing something, or is this a Dovecot problem? dovecot.conf: http://db.org/temp/dovecot.conf Regards, Bård Johannessen

2 4

[Dovecot] Merge mails from two mail_locations
by Patrick Westenberg 29 Mar '12

29 Mar '12

Hi guys, recently I had some trouble with my ocfs2 cluster and it unmounted itself from /var/mail. Unfortunately I received mails while my mailstore was unmounted and some mails are stored in /var/mail on the hosts local harddisk. Now I need to merge/move these locally stored mails to my ocfs2 mailstore but I don't know how to do this. Regards Patrick

2 1

[Dovecot] Need fast Maildir to mdbox conversion
by Jeff Gustafson 29 Mar '12

29 Mar '12

I looked around the 'Net to see if there might be a custom program for offline Maildir to mdbox conversion. So far I haven't turned up anything. The problem for us is that the dsync program simply takes a lot of time to convert mailboxes. I wonder if time could be saved with a program that is optimized to convert mailboxes without the fancy locking that dsync needs to do. Does have (or seen) a tool that could do this? We're hoping that converting away from Maildir will help us speed up the backup processes by reducing the number of files to process. ...Jeff

3 4

[Dovecot] Using getmail with sieve
by Orr, Steve 28 Mar '12

28 Mar '12

I'm trying to setup a personal "mailmover" where I use getmail to retrieve remote IMAP server mail and load it into my local Dovecot then filter all email on the Dovecot server side with sieve. (I'm using Dovecot v. 2.0.9 with IMAP/Maildir.) 1) From the docs I gather that Dovecot sieve will not work as mail is loaded by getmail and I need to refilter the email after it has been loaded with getmail, right? 2) In http://wiki2.dovecot.org/HowTo/RefilterMail it says, "This HOWTO helps you create a folder for mail that needs refiltering..." But contrary to the doc I don't see any actual instructions about creating said folder. The HOWTO assumes mail already exists in a folder called "REFILTER' but doesn't say how this folder was populated. "How to?" 3) As a test I manually created the "REFILTER" folder and put my inbox mail in it (with Thunderbird) then following the HOWTO I ran my getmail script and my sieve script performed as expected. 4) How do I automate this? I tried a new getmail script to run against the inbox and tag new email so a subsequent getmail script could move it into the REFILTER folder for later sieve processing. This seems like way too much work. The HOWTO doc seems incomplete or presumes other knowledge, especially for an IMAP server and email sieve nubie. TIA, D. B. ---------------------------------------------- $ dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-131.0.15.el6.i686 i686 Red Hat Enterprise Linux Server release 6.1 (Santiago) log_path = /var/log/dovecot 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 mbox_write_locks = fcntl passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = test@host1 protocols = imap lmtp service lmtp { user = test } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" }

1 0

[Dovecot] Dovecot upgrade from 1.2.x to 2.0.x: roundcube/squirrelmail sent folder doesn't work any more
by Gerhard Wiesinger 27 Mar '12

27 Mar '12

Hello, After upgrading from 1.2.x to 2.0.x I'm having problems using sent folder in Webmail applications like roundcube mail and squirrelmail. Relevant config dovecot.conf: mail_location = mbox:~:INBOX=/var/mail/%u Different LIST behaviour from rawlog: 1.2.x: with Prefix ~/Mail A002 LIST "" "~/Mail/sent" * LIST (\NoInferiors \UnMarked) "/" "~/Mail/sent" A002 OK List completed. 2.0.x: with Prefix ~/Mail A0003 LIST "" ~/Mail/sent A0003 OK List completed.: Configured prefix for private spaces in roundcube mail is ~/Mail . Roundcube Webmail application checks for existence of the folder but dovecot doesn't return anything in 2.x.latest. Is this by design? Any ideas to fix it by configuration? (I tried prefix Mail/ in roundcube mail without success) Thunderbird works well. Thnx. Ciao, Gerhard

1 0

[Dovecot] Problem with DOVECOT - long authentication time
by Jacek Kowalski 27 Mar '12

27 Mar '12

Hi all, I want to start new server with Postfix (I still have qmail ) and I think I have a problem with authentication in dovecot - it takes 3 seconds. Is this normal time? My configuration: Usernames: from MySQL Passwords: from Active Directory dovecot -n # 1.1.20: /etc/dovecot.conf # OS: Linux 2.6.18-274.7.1.el5 i686 CentOS release 5.7 (Final) ext3 log_path: /var/log/dovecot.log protocols: pop3 pop3s imap imaps listen: * ssl_cert_file: /etc/pki/tls/certs/iRedMail_CA.pem ssl_key_file: /etc/pki/tls/private/iRedMail.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_uid: 500 mail_gid: 500 mail_location: maildir:/xxx/%u:INDEX=/xxx/%u mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota zlib mail_plugins(imap): quota imap_quota zlib mail_plugins(pop3): quota zlib mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 lda: postmaster_address: postmaster(a)domain.com mail_plugins: cmusieve quota log_path: /var/log/sieve.log auth default: mechanisms: plain login default_realm: infor.pl username_format: %Lu debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: sql args: /etc/dovecot-ldap.conf userdb: driver: sql args: /etc/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/dovecot-auth mode: 438 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 438 user: vmail group: vmail plugin: quota_warning: storage=85%% /usr/local/bin/dovecot-quota-warning.sh 85 quota_warning2: storage=90%% /usr/local/bin/dovecot-quota-warning.sh 90 quota_warning3: storage=95%% /usr/local/bin/dovecot-quota-warning.sh 95 quota: maildir quota_rule: *:storage=300M quota_rule2: *:messages=0 expire: Trash 7 Trash/* 7 Junk 30 expire_dict: proxy::expire auth_socket_path: /var/run/dovecot/auth-master sieve: /xxx/sieve/%Ld/%Ln/dovecot.sieve dict: expire: db:/xxx/expire.db grep -v '^ *$#.*$\?$' dovecot-mysql.conf driver = mysql default_pass_scheme = CRYPT connect = host=localhost dbname=xxx user=xxx password=xxx #password_query = SELECT password FROM mailbox WHERE username='%u' AND active='1' user_query = SELECT CONCAT(storagebasedirectory, '/', storagenode, '/', maildir) AS home, CONCAT('*:bytes=', quota*1048576) AS quota_rule FROM mailbox WHERE username='%u' AND active='1' AND enable%Ls%Lc='1' postfix: postfix-2.5.9-5.ired dovecot: dovecot-1.1.20-1_98.el5 mysql: mysql-server-5.0.77-4.el5_6.6 This is not a TCP connection problem, because i have results from tcpdump and wireshark. There is a information that Active directory is answering with password in 0,2 second. Regards Jacek

1 1

[Dovecot] quota ldap
by Alain DEFRANCE 27 Mar '12

27 Mar '12

hello all, i'm using quota + ldap with dovecot 2 in dovecot-ldap.conf.ext file i have the line : user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,quota=quota_rule=*:storage=%$B how can i add "Trash:storage= " to have more place for deleting messages like in 90-quota.conf file ? quota_rule2 = Trash:storage thanks for help regards -- *Alain DEFRANCE* - Ingénieur systèmes et réseaux Direction des systèmes d'information (DiSI) Centre d'Exploitation des Infrastructures Informatiques (CEDII) Cellule Réseau et Expertise Systèmes Bât Ile de France - RDC - Bureau 58 Université d'Evry Val d'Essonne 4, Bd F. Mitterrand - 91025 EVRY Cedex Tel : 01.69.47.80.69 - Fax : 01.69.47.80.24 Mail : alain.defrance(a)univ-evry.fr Site UEVE : http://www.univ-evry.fr

2 3

[Dovecot] Dovecot IMAP is broken after upgrade from 2.1.2 to 2.1.3
by Michael Neubert 27 Mar '12

27 Mar '12

Hello, I just upgraded my servers from Dovecot 2.1.2 to Dovecot 2.1.3-0~auto+5 by using Debian binaries from "http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.1 main". The config was not touched but now IMAP connections are not possible anymore (LMTP works fine). When I try to connect to a mailbox, the connect fails. Some log entries: ############################################################################################################### Mar 23 21:45:28 imap-login: Warning: SSL: where=0x10, ret=1: before/accept initialization [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2001, ret=1: before/accept initialization [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv2/v3 read client hello A [xxx.xxx.xxx.xxx] Mar 23 21:45:28 auth: Debug: auth client connected (pid=3431) Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 read client hello A [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write server hello A [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write certificate A [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write key exchange A [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write server done A [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 flush data [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 read client key exchange A [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 read finished A [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write session ticket A [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write change cipher spec A [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write finished A [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 flush data [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x20, ret=1: SSL negotiation finished successfully [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap-login: Warning: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [xxx.xxx.xxx.xxx] Mar 23 21:45:28 auth: Debug: client in: AUTH 1 PLAIN service=imap secured lip=yyy.yyy.yyy.yyy rip=xxx.xxx.xxx.xxx lport=993 rport=51379 Mar 23 21:45:28 auth: Debug: client out: CONT 1 Mar 23 21:45:28 auth: Debug: client in: CONT 1 AG5lbWlAdmlzaXQtd29ybGQuZGUAUHJvNDUwLnN1 Mar 23 21:45:28 auth-worker(3433): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Mar 23 21:45:28 auth-worker(3433): Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Mar 23 21:45:28 auth-worker(3433): Info: mysql(zzz.zzz.zzz.zzz): Connected to database dovecot Mar 23 21:45:28 auth-worker(3433): Debug: sql(username,xxx.xxx.xxx.xxx): query: SELECT password, 'directory' AS userdb_home, 'mail' AS userdb_uid, 'mail' AS userdb_gid FROM users WHERE username = 'username' AND domain = 'domain' AND active = 'Y' Mar 23 21:45:28 auth: Debug: client out: OK 1 user=username Mar 23 21:45:28 auth: Debug: master in: REQUEST 2286813185 3394 1 4727968fd3514dd45f623ad9f944e305 Mar 23 21:45:28 auth-worker(3433): Debug: sql(username,xxx.xxx.xxx.xxx): SELECT home, uid, gid FROM users WHERE username = 'username' AND domain = 'domain' Mar 23 21:45:28 auth: Debug: master out: USER 2286813185 username home=directory uid=8 gid=8 Mar 23 21:45:28 imap-login: Info: Login: user=<username>, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=yyy.yyy.yyy.yyy, mpid=3434, TLS Mar 23 21:45:28 imap-login: Warning: SSL alert: where=0x4008, ret=256: warning close notify [xxx.xxx.xxx.xxx] Mar 23 21:45:28 imap(username): Info: Connection closed in=0 out=303 ############################################################################################################### The MySQL authentification seems to work fine, but after this the connection is closed with the SSL alert. In Dovecot 2.1.2 everything worked fine. The SSL certifcate is also correct. Any hints are welcome to identify the problem. Thanks in advance. Beste wishes Michael

2 7

[Dovecot] Error: Couldn't create namespace 'Share/' Dovecot 2.1.3 ldap
by Tomislav Mihalicek 27 Mar '12

27 Mar '12

Mar 26 16:38:58 cartman dovecot: imap(miha(a)example.com): Error: Couldn't create namespace 'Share/' for user miha-share(a)example.com: userdb didn't return a home directory, but location used it (%h): maildir:%%h/Maildir:INDEX=%h/index/Shared/%%u Where is the problem, the same config worked with Dovecot 1.2.x -- View this message in context: http://old.nabble.com/Error%3A-Couldn%27t-create-namespace-%27Share-%27-Dov… Sent from the Dovecot mailing list archive at Nabble.com.

2 2

[Dovecot] dovecot-1.2.9: OK No messages copied
by Attila Sipos 26 Mar '12

26 Mar '12

Hi, When I issue an IMAP copy command using the wrong UID, the server gives an "OK No messages copied" response. This seems like the wrong response to me. If the UID doesn't exist, then it should respond with a "No" response - maybe something like "NO - copy error: bad UID" I believe "OK No messages copied" would only be a suitable response if the email with the supplied UID had already been known to be copied successfully. I am using dovecot 1.2.9 - has this been fixed in newer versions of dovecot? Regards Attila Attila Sipos Netcall Telecom Ltd Registered in England 2831215. Registered Office : 3rd Floor, Hamilton House, 111 Marlowes, Hemel Hempstead, Herts, HP1 1BB

2 7

[Dovecot] Many messages clustered around the same date.saved value
by Joseph Tam 26 Mar '12

26 Mar '12

Subject: Different user messages clustered around the same date.saved value After updating dovecot to 2.1.3, I can now use "doveadm expunge -A ..." to iterate through all user trash folders and expunge old messages. However, I noticed a strange thing: querying what would have been deleted doveadm -ftab fetch -A "date.saved" mailbox Trash savedbefore 7d showed many date.saved values are clustered around the same timestamp, even among different user's Trash mailbox. One user's trash mailbox having the same date.saved is explained by a user deleting a lot of message at one time, but I can't explain why many different users would have messages with the same (or closeby) date.saved value. For example, the output of the above query on my system showed the 10s window /2012-03-05 18:08:0[0-9]/ matched 7658 messages among 22 different user Trash mailboxes, which is statistically unlikely. I did't see anything special in the dovecot logs at this time to explain this. What would cause this? Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] dovecot.log warning
by Jitendra Bhaskar 26 Mar '12

26 Mar '12

Hi Guys, Just I installed dovecot-2.1.0 in centos 5.7. and did copy of all user data i.e home directory and mail data from previous server which was on dovecot 1.2.8 to new one. Every thing is working fine. Mails are going and coming. But in dovecot.log file I an getting like imap(user@example.com):Warning: fscking index file /home/ example.com/user/mail/.imap/VISA/dovecot.index Can any one specify why its coming and how can I fix it ? -- * Thanks & Regards * *Jitendra Kumar Bhaskar* Cell:- +91 7306311531 +91 8102997821

2 1

[Dovecot] delivering with maildrop
by Radim Kolar 26 Mar '12

26 Mar '12

Can somebody provide maildrop syntax for using deliver-lda as final delivery program during sorting mail in user mailfilter? i mean replacement for "to" statement if ( /^(To|Cc):.*dovecot@dovecot.org/:h ) { to $MAIL/.dovecot/ }

3 3

[Dovecot] migrating mailboxes on dovecot
by Spyros Tsiolis 25 Mar '12

25 Mar '12

Hello all, I want to ask about something I never did before. I have a dovecot/XMail/LAMP/Horde installation on a CentOS 5.5 32-bit system with two domains : domainA and domainB All the users used to have their mailboxes on domainA. However the personell dept decided that 90% of the users will have to have their mailboxes set to domainB and the other 10% will stay at domainA. So, I need to migrate those mailboxes from domainA to domainB. The only thing is I haven't done that ever. The directory structure is : "/var/MailRoot/domains/domainX/Username/Maildir/" and under there the usual suspects : cur (directory) dovecot.index.cache (file) dovecot-keywords (file) dovecot-uidvalidity (file) new (directory) tmp (directory) dovecot.index (file) dovecot.index.log (file) dovecot-uidlist (file) dovecot-uidvalidity.4cc055c6 (file) subscriptions (file) Using dovecot v1.2.15 Any help would be appreciated. Iam supposed to do this today !! :-) Thank you all, s. ---- "I merely function as a channel that filters music through the chaos of noise" - Vangelis

4 5

[Dovecot] sysconfdir depreacted
by Noel Butler 25 Mar '12

25 Mar '12

The purpose of any build scripts --sysconfdir is to tell the configuration to build in a path for its binaries configuration file(s). Dovecot 2.1.3, seems to insist that that directory is now /etc/dovecot/ ignoring --sysconfdir=/etc as in 1.2.x and previous majors before that, is this a bug? if not, then I see no point of sysconfdir any more and it should be removed, if dovecot deliberately ignores what it is told to use.

7 16

[Dovecot] dovecot and cloudfile systems
by jackie sparks 24 Mar '12

24 Mar '12

I'm trying to store mailboxes in a cloudfile system and I am running into alot of problems using courier, between time skew, file locking and cache creation problems. I was wondering if dovecot has any problems using maildirs across a limited fuse file system. I cant lock files, This is accessed using the fuse library. I thought taking out the standard checking for return values would be a work around because everything imap daemon is doing can be done from a shell by hand except filelocking and setting times on files. I am doing this on Rack Spaces cloud files. This is something that not many if any are doing. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-= This e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. Sections 2510-2521, is confidential, and is intended solely for the use of the individuals or entities to whom it is addressed. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing, or copying of this e-mail and any file attachments is strictly prohibited. If you have received this e-mail in error, please immediately notify me by email at jackie.craig.sparks(a)live.com. You must destroy the original transmission and its contents.

2 3

Re: [Dovecot] kernel problem in RedHat? -- RH specific, or what linux kernels does this affect?
by Linda Walsh 24 Mar '12

24 Mar '12

Is this redhat's version of the kernel only? Or does it apply to other linux kernels and other distros? Any idea what linux kernel versions might cause this? (from main dovecot webpage news) Thu Mar 22 14:38:53 EET 2012 Red Hat/CentOS users: A recent kernel update <https://bugzilla.redhat.com/show_bug.cgi?id=681578> causes Dovecot to start failing after it has reached 1000 child processes. To fix this, downgrade your kernel until Red Hat releases a fixed kernel.

2 1

[Dovecot] Problems with upgrade 2.0.16 -> 2.1.3
by Joseph Tam 24 Mar '12

24 Mar '12

I ran into two issues trying to upgrade our dovecot installation (Solaris 10). 1) Does not compile with OpenSSL 0.9.7 Not a big deal, as I was able to successfully against OpenSSL 0.9.8, but does dovecot require OpenSSL >= 0.9.8 now? libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test -std=gnu99 -O3 -fomit-frame-pointer -mcpu=ultrasparc -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -MT istream-openssl.lo -MD -MP -MF .deps/istream-openssl.Tpo -c istream-openssl.c -fPIC -DPIC -o .libs/istream-openssl.o iostream-openssl-context.c:9:28: openssl/engine.h: No such file or directory iostream-openssl-context.c: In function `ssl_iostream_deinit_global': iostream-openssl-context.c:431: warning: implicit declaration of function `ENGINE_finish' iostream-openssl-context.c:432: warning: implicit declaration of function `ENGINE_cleanup' ... 2) Dovecot's LDA does not work After stopping the the old dovecot, and starting dovecot 2.1.3 using tghe exact same config file, local mail delivery tempfails: Mar 23 02:51:51 server dovecot: auth: Error: getpeerucred() failed: Bad address Mar 23 02:51:51 server dovecot: auth: Error: userdb connection: Failed to get peer's credentials Mar 23 02:51:51 server dovecot: lda: Error: userdb lookup(j.tam): Disconnected unexpectedly Mar 23 02:51:51 server dovecot: lda: Fatal: Internal error occurred. Refer to server log for more information. # Sendmail reports stat=Deferred: local mailer (/var/dovecot/libexec/dovecot-lda) exited with EX_TEMPFAIL After seeing 2) in the logs, I had to revert back to 2.0.16. Any hints on what could be wrong? Joseph Tam <jtam.home(a)gmail.com> # 2.0.16: /var/dovecot/etc/dovecot/dovecot.conf # OS: SunOS 5.10 sun4u nfs auth_cache_negative_ttl = 10 mins auth_cache_size = 64 k auth_cache_ttl = 1 days auth_failure_delay = 5 secs auth_master_user_separator = * auth_socket_path = /var/dovecot/run/auth-userdb auth_username_chars = abcdefghijklmnopqrstuvwxyz01234567890.-_ auth_worker_max_count = 1 base_dir = /var/dovecot/run default_vsz_limit = 64 M deliver_log_format = first_valid_gid = 10000 first_valid_uid = 10000 hostname = our.mail.domain last_valid_gid = 19999 last_valid_uid = 19999 lda_mailbox_autocreate = yes log_timestamp = login_greeting = Ready. mail_location = mbox:/nfs/home/%n/mail:INBOX=/nfs/mail/%n:INDEX=/data/dc-cache/%n mail_nfs_storage = yes mail_temp_dir = /var/tmp mbox_very_dirty_syncs = yes mbox_write_locks = dotlock_try fcntl namespace { inbox = yes location = prefix = separator = / } namespace { hidden = yes list = no location = prefix = / separator = / } namespace { hidden = yes list = no location = prefix = ~/mail/ separator = / } namespace { hidden = yes list = no location = prefix = mail/ separator = / } passdb { args = /var/dovecot/etc/master-users driver = passwd-file master = yes pass = yes } passdb { args = /var/yp/etc/passwd driver = passwd-file } postmaster_address = MAILER-DAEMON(a)our.mail.domain protocols = imap pop3 sendmail_path = /usr/lib/sendmail service auth-worker { user = dovecot } service auth { idle_kill = 1 hours } service imap-login { process_limit = 2 service_count = 0 } service imap { process_limit = 512 } service pop3-login { process_limit = 1 service_count = 0 } service pop3 { process_limit = 64 } shutdown_clients = no ssl_cert = </var/dovecot/etc/ssl/imap.pem ssl_key = </var/dovecot/etc/ssl/imap.pem syslog_facility = local0 userdb { args = /var/dovecot/etc/passwd driver = passwd-file } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep imap_id_log = * mail_max_userip_connections = 12 ssl_cert = </var/dovecot/etc/ssl/imap.pem ssl_key = </var/dovecot/etc/ssl/imap.pem } protocol pop3 { mail_max_userip_connections = 3 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = io=%i/%o top=%t/%p, retr=%r/%b, del=%d/%m, size=%s uid=%u pop3_reuse_xuidl = yes ssl_cert = </var/dovecot/etc/ssl/pop.pem ssl_key = </var/dovecot/etc/ssl/pop.pem }

2 2

Re: [Dovecot] Dovecot 2.1.3 Proxy creates mailbox on proxy
by Ed Nitido 23 Mar '12

23 Mar '12

Ooops, didn't email the list... it working now thanks to Timo, solution below On Fri, Mar 23, 2012 at 4:14 PM, Timo Sirainen <tss(a)iki.fi> wrote: > >> On 23.3.2012, at 22.01, Ed Nitido wrote: >> >> > pass_attrs = >> uid=user,userPassword=password,=proxy,=master=doveadmin,=pass=xxxxxx >> >> I guess it doesn't like the "=proxy" part. I guess I should fix it. For >> now just set "=proxy=y". >> > >

1 0

[Dovecot] Advice for new dovecot / imap proxy? setup
by Luca Lesinigo 23 Mar '12

23 Mar '12

Hello list. I'm planning a new mail servers for our company's customers to replace the oldish Courier-IMAP based one, we already started to deploy some mail accounts on a dovecot-2.0 server as an early test. I'd like to implement the new system with dovecot-2 (I'll probably go straight to dovecot-2.1.x) and I'd like to get it right from the beginning so I'm here asking for some advice. The issue I'm investigating right now is how to manage a single IMAP / POP / SMTP / webmail "entry point" for multiple mail servers... in other words an IMAP proxy. It would be desirable for multiple reasons: - graceful migration from the current system: we'd make the mailserver hostname point to the proxy (along with its SSL certificates) and then the proxy would route each domain to the correct IMAP non-ssl server on our LAN. No need to update customer's systems configuration and we can move one domain at a time from the old to the new server, behind the scenes - be ready for similar migrations in the future (eg. right now we're still keeping the imap servers with the qmail MTA, but we'd like to switch to postfix+dovecot in the future) - be ready for sharding mail domains on multiple IMAP servers (if/when current hardware reach its capacity or needs to be swapped out for new gear) - be ready to serve traffic over IPv6 without touching our precious mailbox servers - isolate the mailbox servers from direct external access and just run IMAP on them, let other systems run ssl, pop3, smtp, webmail, etc... Ideally the 'proxy' system would run dovecot imap and pop3 (SSL protected) and Roundcube webmail (PHP, on https) and just speak IMAP to the underlying mail servers on our internal LAN. We'd like to support all the recent IMAP goodies to make modern users happy (IMAP IDLE, LEMONADE, etc) and possibly implement Maildir quota on the new backend mailbox server to improve our operations (currently we just run du in a cronjob once a day on the current mailserver, IMAP clients including the webmail do not know about quota and thus cannot show amount of free space). In addition to that, customer's will hit the SMTP server running on that 'proxy' system and this is good to keep its configuration separated from the SMTP server of the actual mail servers (which has a different configuration and is restricted to get connections only from our MX systems and not from outside sources). I'd like to know if that plan sounds reasonable or if there's something stupid in it. Also, is the proxy going to support all kind of IMAP stuff of the backend server (IDLE, CONDSTORE, Maildir quota, immediate notification of IDLE clients thanks to linux inotify, etc...) or will it limit me somehow? thanks, -- Luca Lesinigo

4 5

[Dovecot] Dovecot 2.1.3 Proxy creates mailbox on proxy
by Ed Nitido 23 Mar '12

23 Mar '12

Hey all, I've upgraded from a working Dovecot 2.0.17 Proxy with a master user setup to Dovecot 2.1.3 and I've merged my conf settings from 2.0.17 into 2.1.3. I'm able to start up dovecot proxy and telnet localhost, however it creates the users home director on the proxy server instead of going to the backend dovecot server (which has already been successfully upgraded to 2.1.3 from 2.0.17). In my old 2.0.17, I had the entire namespace section commented out in 10-mail.conf. To achieve the same in 2.1.3 I had to remove the file 15-mailboxes.conf, otherwise my error log would have the following if I just commented out the namespace section and left that file in place: *Error: user edward(a)dev.domain.com: Initialization failed: namespace configuration error: inbox=yes namespace missing* *Error: Invalid user settings. Refer to server log for more information.* So now I'm trying to figure out why the proxy doesn't get the mail server IP from director, when doveadm has the backend server listed *# doveadm director status* *mail server ip vhosts users* *192.168.12.205 100 0* Can anyone see something I've missed? Here's my doveconf output: # 2.1.3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-openvz-amd64 i686 Debian 6.0.4 auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_mechanisms = plain login auth_socket_path = /usr/local/var/run/dovecot/auth-master auth_verbose = yes debug_log_path = /var/log/dovecot-debug.log director_doveadm_port = 542 director_mail_servers = 192.168.12.205 director_servers = 192.168.12.209 disable_plaintext_auth = no info_log_path = /var/log/dovecot-info.log listen = * lmtp_proxy = yes log_path = /var/log/dovecot-err.log mail_debug = yes mail_gid = vmail mail_location = maildir:%h/Maildir 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 passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/home/%d/shared-mailboxes quota = maildir:User quota quota_rule = *:storage=1G sieve = %h/.dovecot.sieve sieve_dir = ~/sieve sieve_max_actions = 32 sieve_max_redirects = 4 sieve_max_script_size = 1M sieve_quota_max_scripts = 0 sieve_quota_max_storage = 0 } postmaster_address = postmaster(a)dev.domain.com protocols = imap pop3 lmtp sieve quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0666 user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 541 } inet_listener { port = 542 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director inet_listener imap { port = 143 } } service lmtp { inet_listener lmtp { port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { user = postfix } } service managesieve-login { executable = managesieve-login director inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service pop3-login { executable = pop3-login director inet_listener pop3 { port = 110 } } ssl_cert = </usr/local/etc/dovecot/dovecot.pem ssl_key = </usr/local/etc/dovecot/dovecot.key userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { args = uid=vmail gid=vmail home=/home/%d/%u driver = static } verbose_proctitle = yes protocol lmtp { auth_socket_path = /usr/local/var/run/dovecot/director-userdb mail_plugins = " quota quota sieve" passdb { args = proxy=y nopassword=y port=24 driver = static } } protocol lda { info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota imap_acl acl" } protocol sieve { mail_max_userip_connections = 10 mail_plugins = managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 managesieve_notify_capability = managesieve_sieve_capability = } protocol pop3 { mail_plugins = " quota quota" pop3_fast_size_lookups = no pop3_uidl_format = %08Xu%08Xv }

2 2

[Dovecot] dovecot 2.1.3 dsync Unexpected finish reply
by Micah Anderson 23 Mar '12

23 Mar '12

I've been moving users from one system to another by doing a dsync mirror operation. The first dsync mirror takes some time, because of the number of users involved, so I am doing an initial sync, and then I direct the users to the new location and do a final 'freshening' sync to get any changes that happened during the longer sync. The problem seems to be with this freshening sync, it seems quite fragile breaking with things like: dsync-local(user(a)example.com): Error: msg-get failed: box=Spam uid=3034 guid=1ad456015ae9694f083b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69096 guid=c22b541a71e4694fc93700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69097 guid=4b6d6b13d0e9694f505700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69098 guid=175b1c2e4aea694fc97100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69099 guid=bfb08c1b3bee694f133e00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69100 guid=fa5d630c17ef694fa75f00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69101 guid=7ca96011dcef694f3f0400001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69102 guid=ef547107eff1694ff96700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69103 guid=5597bc0519f2694f2e7000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69104 guid=8336a53a54f5694fb21000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69105 guid=96169d13c8fd694f831800001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69106 guid=af21a5183f036a4f263200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69107 guid=d0fde3348e036a4ff44000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69108 guid=4ce01d1a59056a4fee2200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69109 guid=497f96066e056a4f322700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69110 guid=ef34f505c0066a4fc26b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69111 guid=81adcb2c6e076a4f751100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69112 guid=a110841e8a076a4fa21500001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69113 guid=60d8e70a970d6a4fae2100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69114 guid=7c6cb41572106a4ff13c00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69115 guid=aaf4d32b2f126a4ff21000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69116 guid=ab52f43a58126a4ffd1800001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69117 guid=eb543a2179186a4fe45800001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69118 guid=cd7cb408a12a6a4f272100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69119 guid=2ec02e2ef2326a4f9e1100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69120 guid=e7a4552ff8336a4f7f6700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69121 guid=0724b023d33a6a4f1b3300001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69122 guid=9985c91afe3b6a4f127100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69123 guid=9300751b913d6a4f7a4000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69124 guid=822ff806ae3f6a4f293b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69125 guid=eac8ed1f2b426a4f164200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69126 guid=4109561ae3426a4ff26700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69127 guid=30bc832e5e496a4f563600001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69128 guid=c0b36410bd4b6a4f102b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69129 guid=38a9d41a534d6a4ff40200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69130 guid=b8e84d239b4d6a4fd11000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69131 guid=f060ef22154f6a4f2b5c00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69132 guid=e2999c107c4f6a4f5a7600001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69133 guid=8d09280aae506a4f073500001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69134 guid=43d7ec3aa6556a4f963a00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69135 guid=c5800130d2556a4f594200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69136 guid=83a91e08b4566a4f197100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69137 guid=50cf9721f95e6a4f7e4400001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69138 guid=fda2a82886606a4f881700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69139 guid=97ee1d1ad1636a4fc94d00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69140 guid=4f50671f85666a4f306100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69141 guid=0fea590fb4666a4f7a6b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69142 guid=f3210b02a5676a4ffa1f00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69143 guid=8d325a06686a6a4f2b3600001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69144 guid=0cbf1839f1756a4f8f6800001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69145 guid=d6209a2898796a4f671a00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69146 guid=576ade31da7d6a4f5f5700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69147 guid=70a15b34247e6a4f445a00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69148 guid=3ff92631cd886a4ffd6300001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69149 guid=3ff2081568916a4f134d00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69150 guid=d1a67b0907ab6a4f546000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69151 guid=3d4cb1197ee96a4fbf5f00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69152 guid=aae2542818266b4f7d1e00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2077 guid=c5a0930248e8694fb77c00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2078 guid=dce63e1a6bee694f470200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2079 guid=dde63e1a6bee694f470200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2080 guid=dee63e1a6bee694f470200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2081 guid=dfe63e1a6bee694f470200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2082 guid=a110b53585056a4fe81b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2083 guid=a210b53585056a4fe81b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2084 guid=93afeb1f7d0b6a4f694e00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2085 guid=ef2bb1098a2e6a4fcf1b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2086 guid=d8ba601bee2e6a4f982f00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2087 guid=d9ba601bee2e6a4f982f00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2088 guid=7e5b483b433d6a4fd93600001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2089 guid=7f5b483b433d6a4fd93600001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2090 guid=b08c5205ba646a4f106700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2091 guid=805b483b433d6a4fd93600001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2092 guid=815b483b433d6a4fd93600001d12b59f dsync-local(user(a)example.com): Error: Unexpected finish reply: by ims-d13.mx.aol.com (8.14.1/8.14.1) with ESMTP id q2LEhqXZ017169; dsync-local(user(a)example.com): Error: Unexpected reply from server: Wed, 21 Mar 2012 10:43:52 -0400 dsync-local(user(a)example.com): Warning: Mailbox changes caused a desync. You may want to run dsync again. those final "Unexpected finish reply" and "Unexpected reply from server" are a bit surprising results. Running dsync again seems to resolve things, but there seems to be a bug here that is causing unexpected results to leak through to the dsync process? thanks, micah

1 1

Re: [Dovecot] sysconfdir depreacted
by Joseph Tam 23 Mar '12

23 Mar '12

On Fri, 23 Mar 2012, dovecot-request(a)dovecot.org wrote: >> See http://dovecot.org/list/dovecot/2009-January/036131.html > > Yes, I was also thinking about that, but it's about removing the > dovecot/ suffix from other directories as well. That might be > something worth doing (--without-package-suffix or something?). +1. I fake it now with symlinks (e.g. etc/dovecot -> .). Joseph Tam <jtam.home(a)gmail.com>

1 0