- dovecot - dovecot.org

[Dovecot] userdb errors after upgrading to 2.1
by André Rodier 03 Jul '12

03 Jul '12

Hello everybody, I am running debian wheezy for development and test, and I recently upgrade to dovecot 2.1.7 I am using LDAP lookups, and virtual users with the same UID/GID. Everything was working fine before, but now, I have this error when I try to send an email to a local account: -------------------------------------------------------- Jun 26 15:46:52 lapetus dovecot: lmtp(24518): Error: user user.test(a)indienet.com: Auth USER lookup failed Jun 26 15:46:52 lapetus dovecot: auth: Error: userdb(user.test(a)indienet.com,127.0.0.1): client doesn't have lookup permissions for this user: userdb reply doesn't contain uid (change userdb socket -------------------------------------------------------- However, even if I set the permissions to 0666, I still have the same error. Can you point me in the right direction to fix this, please? Kind regards, André Rodier

2 1

[Dovecot] Wrong headers in dovecot-crlf
by Matthieu RAKOTOJAONA 03 Jul '12

03 Jul '12

Hello everyone, I'm using the very good imaptest [0] tool to test my little imap server implementation. I've tried to use the dovecot-crlf [1] file, but it looks like there are some major issues : $ grep -n "In-Reply-To.*;" tests/data/dovecot-crlf 479:In-Reply-To: <20020806175441.GA7148(a)linux.taugt.net>; from rueckert(a)informatik.uni-rostock.de on Tue, Aug 06, 2002 at 07:54:41PM +0200 525:In-Reply-To: <20020806234054.GA30820(a)carpa.ciagri.usp.br>; from marcelo(a)carpa.ciagri.usp.br on Tue, Aug 06, 2002 at 08:40:54PM -0300 564:In-Reply-To: <20020806234054.GA30820(a)carpa.ciagri.usp.br>; from marcelo(a)carpa.ciagri.usp.br on Tue, Aug 06, 2002 at 08:40:54PM -0300 673:In-Reply-To: <20020807231956.GA11240(a)carpa.ciagri.usp.br>; from marcelo(a)carpa.ciagri.usp.br on Wed, Aug 07, 2002 at 08:19:56PM -0300 795:In-Reply-To: <20020808131329.GA30775(a)carpa.ciagri.usp.br>; from marcelo(a)carpa.ciagri.usp.br on Thu, Aug 08, 2002 at 10:13:30AM -0300 964:In-Reply-To: <20020808193533.GA28619(a)carpa.ciagri.usp.br>; from marcelo(a)carpa.ciagri.usp.br on Thu, Aug 08, 2002 at 04:35:33PM -0300 21545:In-Reply-To: <1046294808.30811.66.camel@hurina>; from tss(a)iki.fi on Wed, Feb 26, 2003 at 11:26:48PM +0200 22042:In-Reply-To: <1046373554.18310.4.camel@hurina>; from tss(a)iki.fi on Thu, Feb 27, 2003 at 09:19:14PM +0200 23712:In-Reply-To: <20030227212127.A10927(a)pcx3332.desy.de>; from Juergen.Kahnert(a)DESY.de on Thu, Feb 27, 2003 at 09:21:27PM +0100 25498:In-Reply-To: <OFF6D684CA.26838A7C-ON42256CE8.003A8EFC-42256CE8.003B49AC(a)icoc.org>; from Leslie_Viljoen(a)icoc.org on Thu, Mar 13, 2003 at 12:44:52PM +0200 30654:In-Reply-To: <1048667343.30187.100.camel@hurina>; from tss(a)iki.fi on Wed, Mar 26, 2003 at 10:29:03AM +0200 31126:In-Reply-To: <1048704303.31565.214.camel@hurina>; from tss(a)iki.fi on Wed, Mar 26, 2003 at 08:45:03PM +0200 31313:In-Reply-To: <1048928723.6856.21.camel@hurina>; from tss(a)iki.fi on Sat, Mar 29, 2003 at 11:05:23AM +0200 31820:In-Reply-To: <1049101161.884.126.camel@hurina>; from tss(a)iki.fi on Mon, Mar 31, 2003 at 11:59:21AM +0300 31890:In-Reply-To: <Pine.LNX.4.44.0303311009510.17234-100000(a)vegemite.nssg.mitel.com>; from charlieb-dovecot(a)e-smith.com on Mon, Mar 31, 2003 at 10:12:22AM -0500 32037:In-Reply-To: <Pine.LNX.4.44.0303311414410.17234-100000(a)vegemite.nssg.mitel.com>; from charlieb-dovecot(a)e-smith.com on Mon, Mar 31, 2003 at 02:19:27PM -0500 32463:In-Reply-To: <1049243642.11879.25.camel@hurina>; from tss(a)iki.fi on Wed, Apr 02, 2003 at 03:34:02AM +0300 As you can see, many of the "In-Reply-To" headers are polluted with some junk. The situation is the same for many "Message-ID" headers. I don't know why they are here, but I think it's a mistake. I thought I would let you know. [0] http://imapwiki.org/ImapTest [1] http://www.dovecot.org/tmp/dovecot-crlf Regards, -- Matthieu RAKOTOJAONA

2 1

[Dovecot] Setting up mixed mbox and maildir
by Jonathan Ryshpan 03 Jul '12

03 Jul '12

I'm trying to set up a dovecot server for which mail arrives in an mbox, and mail is stored in a maildir. The wiki (see http://wiki.dovecot.org/Namespaces) refers to this as "Mixed mbox and Maildir". It advises handling this situation by creating two namespaces: one for the mbox and the other for the maildir. Each of these namespaces starts with namespace private { On the other hand the sample configuration in the documentation puts inbox in a namespace starting with: namespace inbox { # Namespace type: private, shared or public #type = private It appears that there has been a change in the configuration syntax after the wiki was written, and that the word following namespace no longer gives a property of the namespace, but rather its name. Is this correct? In any case, how should the configuration be modified to handle mixed mailboxes? Thanks - jon

4 7

[Dovecot] indexer-worker
by Wojciech Puchar 03 Jul '12

03 Jul '12

why this process (which most probably do squat index/update) runs as root, not - like imap process - as user? 29413 root 1 76 0 22820K 9204K kqread 1 0:17 5.86% indexer-worker

2 3

[Dovecot] Proxy config help please
by Zac Israel 03 Jul '12

03 Jul '12

Hello, I am new to dovecot and I am initially trying to setup a basic imap proxy with password forwarding, I can start the dovecot service, connect and give it my password, and that is where I hang. My config is: root@imap-test:/etc/dovecot# doveconf -n # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-24-generic x86_64 Ubuntu 12.04 LTS auth_debug = yes auth_verbose = yes debug_log_path = syslog first_valid_uid = 100 imap_capability = CAPABILITY IMAP4rev1 ACL BINARY CATENATE CHILDREN CONDSTORE ENABLE ESEARCH ESORT I18NLEVEL=1 ID IDLE LIST-EXTENDED LIST-STATUS LITERAL+ LOGIN-REFERRALS MULTIAPPEND NAMESPACE QRESYNC QUOTA RIGHTS=ektx SASL-IR SEARCHRES SORT THREAD=ORDEREDSUBJECT UIDPLUS UNSELECT WITHIN XLIST last_valid_uid = 200 mail_debug = yes mail_gid = 107 mail_uid = 107 passdb { args = proxy=proxy_always nopassword=y host=172.16.0.13 port=143 proxy_timeout=5 starttls=y ssl=any-cert driver = static } protocols = imap service imap-login { inet_listener imap { address = * port = 143 } } ssl = required ssl_cert = </etc/courier/imapd.pem ssl_key = </etc/courier/imapd.pem verbose_ssl = yes The system at 172.16.0.13 is a zimbra proxy. I can see in the logs that it initially complains about my ssl cert, and if I remove ssl=any-cert it fails because my cert is self signed, so I know it is talking to the proxy and doing starttls which is a requirement of zimbra. Unfortunately I have not found a way to see the full exchange between dovecot and my zimbra proxy other than tcp dump, which just shows a small packet exchange. Please let me know if I can provide any other information and thanks in advance for any help. -Zac

3 3

[Dovecot] Dovecot 2.1 stable packages for Debian?
by Krzysztof Trybowski 02 Jul '12

02 Jul '12

Hello all, it is strange, but Dovecot 2.x still didn't make it into Debian (not even backports). It exists in testing, but that's still a long wait. OTOH there are official packages built every day (referenced from the download page). This puzzles me: why isn't there a build created from each stable, released version of Dovecot, so that users of Debian Stable could benefit from the new version, and run it on production environment? Could you (I mean — the Dovecot team) provide such packages? This wouldn't require any major amount of work, since you already have daily builds produced. You would just have to run that building system once per each released version and keep it available for download. The reason for this is relatively simple: I'm about to implement a new mail server, and I'd like to keep to Debian Stable while using Dovecot 2.x. This will make future updates much easier, as I won't have to face 1.2 -> 2.0 migration on a production system. Regards, KT

9 9

[Dovecot] RAID1+md concat+XFS as mailstorage
by Костырев Александр Алексеевич 02 Jul '12

02 Jul '12

Hello! somewhere in maillist I've seen RAID1+md concat+XFS being promoted as mailstorage. Does anybody in here actually use this setup? I've decided to give it a try, but ended up with not being able to recover any data off survived pairs from linear array when _the_first of raid1 pairs got down. thanks!

7 22

[Dovecot] [PATCH] GSSAPI authorization and virtual users
by Sam Morris 02 Jul '12

02 Jul '12

The attached patch makes it possible for Kerberos principals to be associated with a password database entry by adding a new "k5principals" passdb setting. A client that successfully authenticates using GSSAPI will be able to log in as any user who has been associated with the client's Kerberos principal. This means that users can now use their Kerberos identities to access virtual mail accounts. The patch definitely needs review by someone familiar with Dovecot. It works for me on a small test installation using the passwd-file backend. Things that should probably be improved: 1. The list of authorized principals is stored in struct auth_request. I would prefer to store it in struct gssapi_auth_request, but auth-request.c does not know about structs that are specific to the different authentication plugins. This could be fixed in a more general way by adding a new function to struct mech_module to allow authplugins to read fields during passdb lookups. 2. The gssapi authplugin now does a credential lookup in order to trigger parsing of the k5principals setting. In order for this to work, auth_request_set_username is now called before mech_gssapi_userok. AFAICT the only impact of this is that messages logged by this function (and the functions it calls) will now use the name of the virtual account. 3. The credentials lookup triggers an info log message saying that credentials for GSSAPI were requested, "but we have only (e.g.) MD5-CRYPT". The authplugin doesn't actually want the credential, but I think that the only way the authplugin can trigger a passdb lookup is by requesting it. 4. The final part of the code in mech_gssapi_unwrap was moved to the callback that's triggered when the credentials lookup is complete. The code still needs access to the GSSAPI data, so the buffer pointer & length are now stored in struct gssapi_auth_request, making the inbuf parameter to the mech_gssapi_{sec_context,wrap,unwrap} functions superfluous. The parameters should be removed. 5. The k5principals list won't be processed on Solaris. The code added to the end of mech_gssapi_krb5_userok would have to be moved to a separate function and then be called from the Solaris code. 6. GCC tells me about assignment to incompatible pointer types in the code that iterates through gssapi_k5principals. I must be missing something. The patch is licensed under the MIT license. Please let me know what you think. -- Sam Morris <sam(a)robots.org.uk>

2 4

[Dovecot] UTF-8 mailbox name STATUS response
by Ewald Dieterich 02 Jul '12

02 Jul '12

STATUS in Dovecot 2.1.7 returns the UTF-8 decoded folder name in a string literal: . CREATE "INBOX.Euro &IKw-" . OK Create completed. . LIST "" "INBOX.Euro &IKw-" * LIST (\HasNoChildren) "." "INBOX.Euro &IKw-" . STATUS "INBOX.Euro &IKw-" (MESSAGES) * STATUS {14} INBOX.Euro € (MESSAGES 0) . OK Status completed. Is this intended? My Perl script based on Mail::IMAPTalk doesn't like it and I wonder if there are other clients that don't cope with it.

2 3

[Dovecot] lmtp proxy timeout while waiting for reply to DATA reply
by Daniel Parthey 02 Jul '12

02 Jul '12

Hi, we are experiencing similar sporadic data timeout issues with dovecot 2.0.20 as in http://dovecot.org/pipermail/dovecot/2011-June/059807.html at least once a week. Some mails get temporarily deferred in the postfix queue since dovecot director lmtp refuses them and the mails are delivered at a later time. The problem applies to mails delivered to single users as well as distribution lists where the mails gets delivered to several mailboxes by postfix. The postfix log shows the following output: postfix.log.7.gz:Apr 21 18:48:46 10.129.3.233 postfix/lmtp[15868]: 88062C08E: to=<username(a)example.org>, orig_to=<username(a)example.org>, relay=127.0.0.1[127.0.0.1]:20024, delay=35, delays=5.4/0.01/0/30, dsn=4.4.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.4.0 Remote server not answering (timeout while waiting for reply to DATA reply) (in reply to end of DATA command)) The dovecot.log (mailbox and director log there via syslog) shows the following output: Apr 21 18:46:53 10.129.3.233 dovecot: lmtp(15869): Debug: none: root=, index=, control=, inbox=, alt= Apr 21 18:46:53 10.129.3.233 dovecot: lmtp(15869): Connect from 127.0.0.1 Apr 21 18:46:53 10.129.3.233 dovecot: lmtp(15869): Debug: auth input: user=username(a)example.org proxy port=19024 host=10.129.3.190 proxy_refresh=450 Apr 21 18:46:53 10.129.3.233 dovecot: lmtp(15869): Disconnect from 127.0.0.1: Client quit (in reset) Apr 21 18:47:29 10.129.3.233 dovecot: lmtp(15869): Debug: none: root=, index=, control=, inbox=, alt= Apr 21 18:47:29 10.129.3.233 dovecot: lmtp(15869): Connect from 127.0.0.1 Apr 21 18:47:29 10.129.3.233 dovecot: lmtp(15869): Debug: auth input: user=username(a)example.org proxy port=19024 host=10.129.3.190 proxy_refresh=450 Apr 21 18:47:29 10.129.3.233 dovecot: lmtp(15869): Disconnect from 127.0.0.1: Client quit (in reset) Apr 21 18:48:15 10.129.3.233 dovecot: lmtp(15869): Debug: none: root=, index=, control=, inbox=, alt= Apr 21 18:48:15 10.129.3.233 dovecot: lmtp(15869): Connect from 127.0.0.1 Apr 21 18:48:15 10.129.3.233 dovecot: lmtp(15869): Debug: auth input: user=username(a)example.org proxy port=19024 host=10.129.3.190 proxy_refresh=450 Apr 21 18:48:46 10.129.3.233 dovecot: lmtp(15869): Disconnect from 127.0.0.1: Client quit (in reset) One cannot identify the lmtp log origin from the log_format prefixes, but it seems that the "lmtp($PID)" log originated from the director, since proxy port 19024 is mentioned in the logs, which is our dovecot mailbox backend. Config for dovecot (mailbox) and director (proxy) is attached. mail_debug is yes for both dovecot and director. How can we find out more information? Shall I apply the following patches from http://dovecot.org/pipermail/dovecot/2011-June/059987.html or are they already included with version 2.0.20? Regards, Daniel

3 10

[Dovecot] director directing to wrong server (sometimes)
by Angel L. Mateo 02 Jul '12

02 Jul '12

Hello, I have discovered a strange behaviour with director proxying... I have a user, its assigned server is 155.54.211.164. The problem is that I don't know why director sent him yesterday to a different server, because my server was up all the time. Moreover, I'm using poolmon in director servers to check availability of final servers and it didn't report any problem with the server. I have two load balanced director servers. Logs at these servers are: * logs directing him to the correct backend server Jun 28 08:38:18 myotis42 dovecot: auth: Debug: master in: PASS#0111#011<user>@um.es#011service=lmtp#011lip=155.54.211.185#011lport=24#011rip=155.54.212.168#011rport=52255 Jun 28 08:38:18 myotis42 dovecot: auth: Debug: static(<user>,155.54.212.168): lookup Jun 28 08:38:18 myotis42 dovecot: auth: Debug: master out: PASS#0111#011user=<user>#011proxy#011proxy_timeout=150 Jun 28 08:38:18 myotis42 dovecot: lmtp(15889): Debug: auth input: user=<user> proxy proxy_timeout=150 host=155.54.211.164 proxy_refresh=450 Jun 28 08:39:59 myotis42 dovecot: auth: Debug: master in: PASS#01118#011<user>@um.es#011service=lmtp#011lip=155.54.211.185#011lport=24#011rip=155.54.212.166#011rport=40008 Jun 28 08:39:59 myotis42 dovecot: auth: Debug: static(<user>,155.54.212.166): lookup Jun 28 08:39:59 myotis42 dovecot: auth: Debug: master out: PASS#01118#011user=<user>#011proxy#011proxy_timeout=150 Jun 28 08:39:59 myotis42 dovecot: lmtp(15361): Debug: auth input: user=<user> proxy proxy_timeout=150 host=155.54.211.164 proxy_refresh=450 * now, the other director server sends him to an incorrect backend server Jun 28 09:01:12 myotis41 dovecot: auth: Debug: static(<user>,155.54.66.38): lookup Jun 28 09:01:12 myotis41 dovecot: auth: Debug: static(<user>,155.54.66.38): Allowing any password Jun 28 09:01:12 myotis41 dovecot: auth: Debug: client out: OK#01134556#011user=<user>#011proxy#011proxy_timeout=150#011pass=<hidden> Jun 28 09:01:12 myotis41 dovecot: auth: Debug: static(<user>,155.54.66.38): lookup Jun 28 09:01:12 myotis41 dovecot: auth: Debug: static(<user>,155.54.66.38): Allowing any password Jun 28 09:01:12 myotis41 dovecot: auth: Debug: client out: OK#01152763#011user=<user>#011proxy#011proxy_timeout=150#011pass=<hidden> Jun 28 09:01:12 myotis41 dovecot: imap-login: proxy(<user>): started proxying to 155.54.211.162:143: user=<<user>>, method=PLAIN, rip=155.54.66.38, lip=155.54.211.186 Jun 28 09:01:12 myotis41 dovecot: imap-login: proxy(<user>): started proxying to 155.54.211.162:143: user=<<user>>, method=PLAIN, rip=155.54.66.38, lip=155.54.211.186 Jun 28 09:01:13 myotis41 dovecot: auth: Debug: static(<user>,155.54.66.38): lookup Jun 28 09:01:13 myotis41 dovecot: auth: Debug: static(<user>,155.54.66.38): Allowing any password * Now, the first director sends him to the incorrect one too Jun 28 09:33:50 myotis42 dovecot: auth: Debug: master in: PASS#01132#011<user>@um.es#011service=lmtp#011lip=155.54.211.185#011lport=24#011rip=155.54.212.168#011rport=46830 Jun 28 09:33:50 myotis42 dovecot: auth: Debug: static(<user>,155.54.212.168): lookup Jun 28 09:33:50 myotis42 dovecot: auth: Debug: master out: PASS#01132#011user=<user>#011proxy#011proxy_timeout=150 Jun 28 09:33:50 myotis42 dovecot: lmtp(17284): Debug: auth input: user=<user> proxy proxy_timeout=150 host=155.54.211.162 proxy_refresh=450 I haven't found any error log for the correct backend server between the correct redirection and the incorrect one. In fact, I have lot of logs of other users directed to it, and logs of the same director directing connections to the correct server. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 868887590 Fax: 868888337

3 3

[Dovecot] Config off by a nuance or a gross?
by Michael Brian Bentley 01 Jul '12

01 Jul '12

Hi, I am trying to establish an IMAP mail service accessible using a current Thunderbird on a laptop. I used Macports to install Dovecot2 (2.1.5) on an older Snow Leopard Mac mini with Intel Core Duo (specifically a Macmini1,1). My goal is to be able to run sieve under dovecot2 and offload the email triage from my work laptop to the little mail server. Mail appears to show up on the server just fine. I'm having trouble getting Tbird to log in and access properly. Because there are so many components in play (Tbird, pam, Dovecot2, macports, OS X Snow Leopard 10.6.8) (dovecot by itself seems to have quite a few settings), it is hard to tell what bit is out of whack. The message I get from Tbird 13.0.1 for OS X (on Lion) is: Alert: The IMAP server bentley on TheMini does not support the selected authentication method. Please change the 'Authentication method' in the 'Account Settings | Server settings'. When I set up the account, Tbird's automatic configuration invents a fake mail service based on my domain name, but appears to configure things sensibly once I switch to the manual configuration and fill in the relevant IP information. It does not appear to care whether it has a password or not. When I set up the account manually on TBird, I let it set up as: IMAP (ipv4)xx.xxx.xx.xx Port: 143 Connection security: None Authentication method: Password, transmitted insecurely SMTP xxxxxxxx.com Port: 587 The dovecot.conf tree includes these: passdb { driver = pam } userdb { driver = passwd } default_login_user = _dovenull default_internal_user = _dovecot service imap-login { executable = /opt/local/libexec/dovecot/imap-login inet_listener imap { address = * port = 143 } } service imap { executable=/opt/local/libexec/dovecot/imap process_limit = 1024 } service lmtp { unix_listener lmtp { } } Issuing the command: dovecot --build-options produces: Build options: ioloop=kqueue notify=kqueue ipv6 openssl io_block_size=8192 Mail storages: shared mdbox sdbox maildir mbox cydir imapc pop3c raw SQL drivers: Passdb: checkpassword pam passwd passwd-file Userdb: checkpassword passwd prefetch passwd-file The /etc/pam.d/dovecot file contains: # pop3, imap, smtp : auth account password session auth required pam_opendirectory.so account required pam_permit.so password required pam_deny.so session required pam_permit.so Dovecot provides the following debug messages on the console when I add args = failure_show_msg=yes to passdb in the relevant dovecot conf file: Jul 1 11:12:38 xx-xxx-xx-xx-nerewhon dovecot[3871]: auth: Debug:auth client connected (pid=5047) Jul 1 11:12:40 xx-xxx-xx-xx-nerewhon dovecot[3871]: imap-login: Disconnected (no auth attempts in 2 secs): user=<>, rip=192.168.xx.xx, lip=xx.xxx.xx.xx I recently discovered doveadm and used it with: doveadm config to create what I think is the current dovecot.conf file. I hesitate to inflict that on the list without being told, "yeah, we need that," there may be digest subscribers out there... I also see these messages show up; they appear unrelated to what I do with Tbird: Jul 1 11:37:33 xx-xxx-xx-xx-nerewhon dovecot[3871]: auth: Debug: Loading modules from directory: /opt/local/lib/dovecot/auth auth: Debug: auth client connected (pid=5094) auth: Debug: client in: AUTH 1 PLAIN service=imap secured lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=49774 auth: Debug: client out: CONT 1 auth: Debug: client in: CONT 1 AGJlbnRsZXkAZ3IxbmNo auth-worker(5100): Debug: Loading modules from directory: /opt/local/lib/dovecot/auth auth-worker(5100): Debug: pam(bentley,127.0.0.1): lookup service=dovecot auth-worker(5100): Debug: pam(bentley,127.0.0.1): #1/1 style=1 msg=Password: auth-worker(5100): pam(bentley,127.0.0.1): pam_authenticate() failed: authentication error (password mismatch?) (given password: whatever) auth: Debug: client out: FAIL 1 user=bentley reason=Password: auth: Debug: client in: AUTH 2 PLAIN service=imap secured lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=49774 resp=AGJlbnRsZXkAZ3IxbmNo auth-worker(5100): Debug: pam(bentley,127.0.0.1): lookup service=dovecot auth-worker(5100): Debug: pam(bentley,127.0.0.1): #1/1 style=1 msg=Password: auth-worker(5100): pam(bentley,127.0.0.1): pam_authenticate() failed: authentication error (password mismatch?) (given password: whatever) auth: Debug: client out: FAIL 2 user=bentley reason=Password: imap-login: Disconnected (auth failed, 2 attempts in 9 secs): user=<bentley>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured auth: Debug: Loading modules from directory: /opt/local/lib/dovecot/auth

1 0

[Dovecot] ot: trying to understand log entries, etc
by Voytek Eymont 01 Jul '12

01 Jul '12

totally of, I'm trying to understand what's happening, aka, 'how does email works' ? I have Dovecot 1.x, all works fine I noticed in the logs failed access from no-longer-hosted account/user, physical account deleted/removed, most likely from user's BBerry, every ~15 minutes: from /var/log/maillog --- Jun 24 07:31:25 dovecot: imap-login: Disconnected: Inactivity (auth failed, 1 attempts): user=<vvv@tld>, method=PLAIN, rip=101.222.222.222, lip=111.111.111.111 --- I recreated account/physical path /var/mail/.../tld/vvv@tld I logged in with webmail, all works, webmail logged out I physically copied some emails (from another account) to physical path ../../tld/vvv@tld/new after a while, I see the email files NO LONGER in ../../../new BUT now in ../../tld/vvv@tld/cur Q: that means the email was accessed, doesn't it ? BUT, I don't see any more access in the /var/log/maillog, not failed, not OK I did see one, after I recreated account Jun 30 20:01:53 dovecot: IMAP(vvv@tld): Disconnected: Logged out bytes=32/666 NONE since, but email files move from new to cur ?? if I observe email files moving from 'new' to 'cur' shouldn't I see some action logged in /var/log/maillog to correspond ? perplexed.... -- Voytek

1 0

[Dovecot] moving from BSD to Ubuntu
by spamvoll＠googlemail.com 30 Jun '12

30 Jun '12

hi.. im planning to move my Mailserver from an FreeBSD Box to an Ubuntu 12.04 LTS Box. Both Boxes run Dovecot 2.0 Does anyone did this before and experienced any problems ? Downtime is no problem, my plan is to stop Dovecot on the Bsd Box and copy all Mailbox files to the Uuntu system and start dovecot. Regards Hans

2 1

Re: [Dovecot] started with dovecot sieve
by Daniel Parthey 30 Jun '12

30 Jun '12

Rolf wrote: > Am 2012-06-25 23:59, schrieb Daniel Parthey: > >Hi Rolf, > > > >Rolf wrote: > >>Jun 25 20:22:54 rolf14 dovecot: lda(rolf): Error: setegid(privileged) failed: Operation not permitted Doesn't lda(rolf) mean it is being executed under user "rolf", not root or dovecot? How exactly do you invoke lda from your /etc/postfix/master.cf? You might also try to use LMTP via TCP to deliver mails from postfix to dovecot to work around any permission problems. > I have installed dovecot and docecot-sieve by Debians aptitude You don't seem to be the only one with these problems, see Debian BTS: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626130 > As far as I understand the "ps -f ax" output (see > below) dovecot runs with root privileges and postfix runs with its > own user privileges. > > root 20998 1 0 Jun25 ? Ss 0:03 /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf Well, the master process often runs as root, but child processes like lda may be configured to run as an unprivileged, or even as the user which owns the mailbox. > The mbox files below /var/mail are owned by > their respective users and have "mail" as their group, both can > write, world can do nothing. I added every related system user to > the mail group, also restarted postfix and dovecot. > root@rolf14:/var/mail# more /etc/group | grep mail: mail:x:8:amavis,dovecot,clamav,postfix User "rolf" is not a member of group "mail", but I don't think he needs to be, otherwise he would be able to read the mails of all users on the system and this would be a security risk. > As I understand it, postfix activates the lda "deliver" as user > "postfix". Therefore it should be able to write to the mboxes at > /var/mail. If needed dovecot can write there as well. The lda should rather switch to the owner of the respective INBOX, e.g. /var/mail/rolf. Log message "lda(rolf)" looks like this happens. To summarize, I think LMTP will be the easiest way to fix the permission problems. Otherwise you would need to fiddle out how to prevent dovecot lda from switching to group additional group "mail", since unprivileged user "rolf" is not allowed to do that. Regards, Daniel -- https://plus.google.com/103021802792276734820

2 4

[Dovecot] how to announce shared folders to clients using non-default mail prefix
by Tom Lieuallen 30 Jun '12

30 Jun '12

We're using dovecot 2.1.3 and I've been doing some testing with 2.1.7. We have shared mail (maildir) folders working along with our default mbox mailboxes. Our problem is trying to get this to work in a reasonable fashion with our iPhone or iPad mail.app clients. It's well known that they don't honor the subscription list; they show all available mail folders and do not collapse trees of folders. I have 381 folders in directories under mail. Normal clients are fine, but this is unmanageable in IOS. What we have been doing is changing the mail prefix for the iPhone to a subfolder, then using soft links to point to the most commonly used folders we use. This works, but when one changes the mail prefix, any shared folders are not presented. I'm suspicious that this is a design decision. If there is some way to make it work, I'd be very grateful. Note the two 'sharedimap' folders listed in the first 'list'. Note that if I change the prefix for that shared namespace to 'iphonemail/', it does present my shared folders as well as anything in a personal iphonemail directory. However, 'select' didn't work with the personal folders. My guess is it's mostly due to the difference in mail formats between the two (mbox & maildir). But, it does show that somewhere in the code it's checking the mail prefix against namespaces and not displaying shared folders in non-default prefixes. I wish this were a configurable option. thank you Tom Lieuallen Oregon State University . list "" * * LIST (\Noselect \HasChildren) "/" "foo1" * LIST (\NoInferiors \UnMarked) "/" "foo1/folder1" * LIST (\Noselect \HasChildren) "/" "iphonemail" * LIST (\NoInferiors \Marked) "/" "iphonemail/foo1" * LIST (\NoInferiors \UnMarked) "/" "Sent" * LIST (\NoInferiors \UnMarked) "/" "Trash" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\HasNoChildren) "/" "sharedimap/cesupport" * LIST (\HasNoChildren) "/" "sharedimap/mimesupport" . OK List completed. . list "iphonemail/" * * LIST (\NoInferiors \Marked) "/" "iphonemail/foo1" . OK List completed. =============== # 2.1.7: /private/dovecot/etc/dovecot/dovecot.conf # OS: SunOS 5.10 sun4v auth_debug = yes auth_verbose = yes default_client_limit = 10245 default_process_limit = 5120 first_valid_uid = 100 mail_location = mbox:~/mail:INBOX=/var/mail/%u:INDEX=/a2/imap-index/%u mail_nfs_storage = yes mail_plugins = quota acl namespace { inbox = yes location = prefix = separator = / type = private } namespace { hidden = yes inbox = no list = children location = maildir:/a1/dove-shared:INDEX=/a2/imap-index/dove-shared/%u prefix = sharedimap/ separator = / type = shared } passdb { driver = pam } passdb { args = scheme=CRYPT username_format=%u /private/dovecot/etc/passwd driver = passwd-file } plugin { acl = vfile quota = fs:INBOX:mount=/a1 quota2 = fs:Home quota:mount=%h } protocols = imap lmtp service imap-login { inet_listener imaps { port = 993 ssl = yes } process_min_avail = 16 service_count = 1 } service imap { process_limit = 2048 } ssl_ca = </private/ssl/certs/SSL_CA_Bundle.pem ssl_cert = </private/ssl/certs/mail.crt ssl_key = </private/ssl/certs/mail.key userdb { driver = passwd } userdb { args = username_format=%u /private/dovecot/etc/passwd driver = passwd-file } protocol imap { mail_plugins = quota acl imap_quota imap_acl } protocol pop3 { pop3_uidl_format = %08Xv%08Xu }

2 6

[Dovecot] Adding IMAP SORT and THREAD Extensions but THREAD=ORDEREDSUBJECT functionality to Dovecot 2.x.y !
by Oooo1 30 Jun '12

30 Jun '12

Hi. Can somebody add IMAP SORT and THREAD Extensions THREAD=ORDEREDSUBJECT function to the just next version of Dovecot ? It is necessary to GroupWare server. At the moment I have made it workable together, but there is one unstable point, as I have understood SOGo needs THREAD=ORDEREDSUBJECT sorting functions and if it not to get it, GroupWare server makes unworkable some of its component. If it needs additional info, you are welcome.

1 0

[Dovecot] What does "namespace inbox {..." mean
by Jonathan Ryshpan 30 Jun '12

30 Jun '12

I'm trying to set up a dovecot server for which mail arrives in an mbox, and mail is stored in a maildir. The wiki (see http://wiki.dovecot.org/Namespaces) refers to this as "Mixed mbox and Maildir". It advises handling this situation by creating two namespaces: one for the mbox and the other for the maildir. On the other hand the sample configuration coming with dovecot in my distro puts inbox in a namespace starting with: namespace inbox { # Namespace type: private, shared or public #type = private It appears from the wiki that the word following the namespace declarator (if this is the right word) should be either "public", "shared", or "private", and describes a property of the namespace being declared. So what does: namespace inbox {... mean? Similarly in another part of the wiki (see http://wiki2.dovecot.org/Plugins/Virtual) I read that it's possible to have namespace virtual { namespace real { ... which only increases my perplexity. Please advise! Thanks - jon

2 1

[Dovecot] Preferred LDAP Attribute for home/mail location
by Edgar Fuß 29 Jun '12

29 Jun '12

Is there, among the dovocot community, any preferred LDAP schema and attribute to use for setting the home/mail storage location? Some people seem to use the qmail schema, some a Jamm schema (whatever that is), and Markus Effinger has even created a dovecot schema (https://www.effinger.org/blog/2009/01/11/eigenes-ldap-schema-erstellen/) There may be more. I could even create my own given we have been assigned an official OID a decade ago anyway. However, sometimes I prefer to use what most other people do. I would effectively only need to store the name of the relevant NFS server.

2 1

Re: [Dovecot] RAID1+md concat+XFS as mailstorage
by Dr Josef Karthauser 29 Jun '12

29 Jun '12

Kelsey Cummings wrote: > On 06/28/12 05:56, Ed W wrote: >> So given the statistics show us that 2 disk failures are much more >> common than we expect, and that "silent corruption" is likely occurring >> within (larger) real world file stores, there really aren't many battle >> tested options that can protect against this - really only RAID6 right >> now and that has significant limitations... > > Has anyone tried or benchmarked ZFS, perhaps ZFS+NFS as backing store > for spools? Sorry if I've missed it and this has already come up. > We're using Netapp/NFS, and are likely to continue to do so but still > curious. Hi Kelsey, We're running ZFS here, and have just started using dovecot on it. No stats yet to report, but you might be interested in this edge case. One of our server started behaving badly... the database would randomly crash and not restart due to corrupted indexed. It turns out that the memory had gone bad, and that it had been bad for a while. Disk blocks were getting corrupted on read, and some on write! Luckly because we were on ZFS, which checksums all data, we were able to detect and repair most of the data (some 80mb of bad blocks distributed evenly thoughout the entire file system!) automatically, and also know exactly which files were unrecoverable (in the end just two or three files!). Also, we have hourly snapshots of all the file systems, so we were able to recover older versions of those files with minimal loss. I will never rely on a non-checksumming file system for production use again, for data that is existed to persist over time. Joe

2 1

[Dovecot] auth service: out of memory
by Mailing List SVR 29 Jun '12

29 Jun '12

Hi, I have some out of memory errors in my logs (file errors.txt attached) I'm using dovecot 2.0.19, I can see some memory leaks fix in hg after the 2.0.19 release but they seem related to imap-login service, I attached my config too, is something wrong there? Should I really increase the limit based on my settings? Can these commits fix the reported leak? http://hg.dovecot.org/dovecot-2.0/rev/6299dfb73732 http://hg.dovecot.org/dovecot-2.0/rev/67f1cef07427 Please note that the auth service is restarted when it reach the limit so no real issues, please advice thanks Nicola

2 4

[Dovecot] Removing specific entry in user/auth cache
by Angel L. Mateo 29 Jun '12

29 Jun '12

Hi, We have dovecot configured with auth cache. Is there any way to remove a specific entry (not all) from this cache? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 868887590 Fax: 868888337

4 4

[Dovecot] Integrating Dovecot with Amazon Web Services
by Gary Mort 29 Jun '12

29 Jun '12

I did some searching in the mail archives and didn't see any discussion of integration with AWS, so I wanted to through out my thoughts/plans and see if it has been done before. I am setting up my own personal website on EC2 along with an email server, and I really don't like the idea of using the disk drive as permanent mail storage. EBS is too small instance storage is ephermeral. Looking over the docs, the dbox format seems most easily copied for my needs. http://wiki2.dovecot.org/MailboxFormat/dbox To make life easy, I'll stick with just single-dbox as a start, however multi-dbox would be doable. With dbox, the only thing that I need to change is the alternate storage model: "An upshot of the way alternate storage works is that any given storage file (mailboxes/<folder>/dbox-Mails/u.* (sdbox) or storage/m.* (mdbox)) can only appear *either* in the primary storage area *or* the alternate storage area but not both — if the corresponding file appears in both areas then there is an inconsistency." First I want to add AWS S3 as a storage option for alternate storage. Then instead of the above model, the new model would be that email is always stored in alternate storage, and may be in primary storage. So, when mail comes in, I'd have Dovecot save the email to the alternate storage S3 bucket and update the indexs and other information[ideally, for convenience purposes, a few bits of relevant indexing information can be stored as metadata in the S3 object - sufficient so that instead of retrieving the entire S3 object, just the meta data can be pulled to build indexes. When a client attempts to retrieve an email message, Dovecot would check primary storage as it does now, if the message is not found than it will retrieve it from the alternate storage system AND store a copy in the primary storage. Primary storage can be periodically purged, have quota's to keep it from growing too large, etc. In this way, primary storage can be viewed as a message cache, just keeping the messages that are currently of interest, while S3 is the real data. [Ideally, this can be expanded so that when a message comes in, in addition to storing a copy in S3, an AWS SNS notification can be issued so if multiple IMAP servers are running, they can all subscribe to the same SNS channel and update themselves as needed]. This give me unlimited disk storage at S3 prices, I would even like to be able to set a few options based on the folder, so I can enable versioning on important message folders, use the even cheaper reduced redundancy storage for archives, and set expiration dates on email in the trash and spam folders so S3 will automatically purge the messages after a month. Secondly, I'd like to replace the Mysql database usage with a simpleDB database. While simpleDB lacks much of MySQL's sophistication, it doesn't seem that Dovecot is really using any of that, so simpleDB can be functionally equivalent. The primary purpose of using simpleDB is that this way the entire Dovecot system can be ephermeral. When a properly configured dovecot AMI is launched, it will start up, pull it's config data from an S3 bucket, subscribe to the SNS channel for new updates, and then start the Dovecot server. It won't care if it is the only Dovecot server, or if there are 500 other servers running. They all share the same simpleDB database. Whenever any change is made that is relevant to server configuration, a notice is generated to SNS, and all the email is stored in S3. As a starting point, I'm thinking the best place for me to start coding is the single-s3-dbox message store as it has the least moving parts[mainly just fix up the save function to run the way I need it to, and the retrieve function to make a local copy of any incoming email...additional metadata functionality can be added later]. Has anyone else been working on something similar? -Gary

4 10

[Dovecot] Mail migration to dovecot with doveadm backup
by Reinhard Vicinus 28 Jun '12

28 Jun '12

Hi, i try to migrate mails from a non dovecot imap server to a dovecot imap server with doveadm backup as described there: http://wiki2.dovecot.org/Migration/Dsync i first tried (local-mailbox port 18143 is the non dovecot imap server): /usr/bin/doveadm -o imapc_user=user(a)example.org -o imapc_password=imappw -o imapc_host=local-mailbox -o imapc_features=rfc822.size -o imapc_port=18143 -o mailbox_list_index=no -v -D backup -R -f -u user(a)example.org -m Sent imapc: and got the following error: dsync(user(a)example.org): Fatal: dsync backup: Looks like you're trying to run backup in wrong direction. Source is empty and destination is not. As the dovecot imap account is newly created and therefore empty it seams to try to backup from the dovecot imap server to the non dovecot imap server. So i tried instead: /usr/bin/doveadm -o imapc_user=user(a)example.org -o imapc_password=imappw -o imapc_host=local-mailbox -o imapc_features=rfc822.size -o imapc_port=18143 -o mailbox_list_index=no -v -D backup -f -u user(a)example.org -m Sent imapc: Sometimes (every other time?) i got the following segmentation fault: bt #0 0x00007f15e2c9ed74 in strcasecmp () from /lib/libc.so.6 #1 0x00007f15e327eaff in imapc_save_callback (reply=0x7fff56096a70, context=<value optimized out>) at imapc-save.c:168 #2 0x00007f15e32853fe in imapc_command_reply_free (conn=0x72f040) at imapc-connection.c:946 #3 imapc_connection_input_tagged (conn=0x72f040) at imapc-connection.c:1039 #4 0x00007f15e3285668 in imapc_connection_input_one (conn=0x72f040) at imapc-connection.c:1085 #5 imapc_connection_input_pending (conn=0x72f040) at imapc-connection.c:1407 #6 0x00007f15e3285922 in imapc_connection_input (conn=0x72f040) at imapc-connection.c:1100 #7 0x00007f15e2fe6176 in io_loop_call_io (io=0x792510) at ioloop.c:379 #8 0x00007f15e2fe71ff in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:213 #9 0x00007f15e2fe6118 in io_loop_run (ioloop=0x7529a0) at ioloop.c:398 #10 0x00007f15e3281e49 in imapc_client_run_pre (client=0x7333e0) at imapc-client.c:142 #11 imapc_client_run (client=0x7333e0) at imapc-client.c:161 #12 0x00007f15e3280f24 in imapc_storage_run (storage=0x732bd0) at imapc-storage.c:118 #13 0x00007f15e327f003 in imapc_save_append (_ctx=0x74dcb0) at imapc-save.c:232 #14 imapc_save_finish (_ctx=0x74dcb0) at imapc-save.c:255 #15 0x00007f15e1bf06a1 in quota_save_finish (ctx=0x74dcb0) at quota-storage.c:227 #16 0x00007f15e3292487 in mailbox_save_finish (_ctx=0x7f15e2d4ca40) at mail-storage.c:1669 #17 0x000000000042b736 in local_worker_save_msg_continue (worker=0x73c770) at dsync-worker-local.c:1681 #18 0x000000000042b98c in local_worker_msg_save (_worker=0x73c770, msg=0x7f15e38e4298, data=0x7fff56096db0, callback=0x4269f0 <msg_save_callback>, context=0x78a610) at dsync-worker-local.c:1739 #19 0x000000000042b0d9 in dsync_worker_msg_save (worker=0x73c770, msg=<value optimized out>, data=0x7fff56096db0, callback=0x4269f0 <msg_save_callback>, context=0x78a610) at dsync-worker.c:234 #20 0x0000000000426ac5 in msg_get_callback (result=<value optimized out>, data=0x7fff56096db0, context=0x78a610) at dsync-brain-msgs-new.c:79 #21 0x000000000042dca9 in local_worker_msg_get_next (worker=0x726f30, get=0x7fff56096e00) at dsync-worker-local.c:1844 #22 0x000000000042def8 in local_worker_msg_get (_worker=0x0, mailbox=<value optimized out>, uid=3805596224, callback=0x2670, context=0x58) at dsync-worker-local.c:1865 #23 0x000000000042ace6 in dsync_worker_msg_get (worker=0x726f30, mailbox=0x7f15e38e40f1, uid=1, callback=0x426a40 <msg_get_callback>, context=<value optimized out>) at dsync-worker.c:261 #24 0x000000000042689e in dsync_brain_msg_sync_add_new_msg (iter=0x7f15e38e41d8) at dsync-brain-msgs-new.c:181 #25 dsync_brain_mailbox_add_new_msgs (iter=0x7f15e38e41d8) at dsync-brain-msgs-new.c:216 #26 dsync_brain_msg_sync_add_new_msgs (iter=0x7f15e38e41d8) at dsync-brain-msgs-new.c:315 #27 0x0000000000426164 in dsync_brain_msg_sync_more (sync=0x7f15e38e4050) at dsync-brain-msgs.c:436 #28 0x0000000000424979 in dsync_brain_sync_msgs (brain=0x7351c0) at dsync-brain.c:736 #29 dsync_brain_sync (brain=0x7351c0) at dsync-brain.c:857 #30 0x0000000000425849 in dsync_brain_subs_list_finished (context=0x750fa0) at dsync-brain.c:169 #31 dsync_worker_subs_input (context=0x750fa0) at dsync-brain.c:222 #32 0x0000000000424cbd in dsync_brain_sync (brain=0x7351c0) at dsync-brain.c:842 #33 0x00000000004256bc in dsync_brain_mailbox_list_finished (context=0x743a60) at dsync-brain.c:98 #34 dsync_worker_mailbox_input (context=0x743a60) at dsync-brain.c:125 #35 0x0000000000424afe in dsync_brain_sync (brain=0x7351c0) at dsync-brain.c:833 #36 0x0000000000425568 in dsync_brain_sync_all (brain=0x7351c0) at dsync-brain.c:897 #37 0x0000000000422ad6 in cmd_dsync_start (ctx=0x706560, worker1=<value optimized out>, worker2=<value optimized out>) at doveadm-dsync.c:342 #38 0x0000000000422dfa in cmd_dsync_run (_ctx=0x706560, user=0x7209c0) at doveadm-dsync.c:387 #39 0x000000000040f888 in doveadm_mail_next_user (ctx=0x706560, input=<value optimized out>, error_r=0x7fff560973d0) at doveadm-mail.c:311 #40 0x0000000000410071 in doveadm_mail_cmd (cmd=0x704880, argc=7, argv=0x6fe418) at doveadm-mail.c:518 #41 0x0000000000410501 in doveadm_mail_try_run (cmd_name=0x6fe4e4 "backup", argc=1443460960, argv=0x4377c7) at doveadm-mail.c:577 #42 0x00000000004170d1 in main (argc=7, argv=0x6fe3e8) at doveadm.c:373 The other times it shows the following error message (It seams to connect both times to the non dovecot imap server): doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm doveadm(root): Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_lookup (this is usually intentional, so just ignore this message) doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so doveadm(root): Debug: Skipping module doveadm_zlib_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_zlib_plugin.so: undefined symbol: i_stream_create_deflate (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_list_backend (this is usually intentional, so just ignore this message) doveadm(user(a)example.org): Debug: auth input: user(a)example.org home=/mail/dovecot/example.org/user uid=1000 gid=1000 quota_rule=*:bytes=2000M:messages=0 doveadm(user(a)example.org): Debug: Added userdb setting: plugin/quota_rule=*:bytes=2000M:messages=0 doveadm(user(a)example.org): Debug: Effective uid=1000, gid=1000, home=/mail/dovecot/example.org/user doveadm(user(a)example.org): Debug: Quota root: name=User quota backend=dict args=:proxy::quota doveadm(user(a)example.org): Debug: Quota rule: root=User quota mailbox=* bytes=2097152000 messages=0 doveadm(user(a)example.org): Debug: Quota rule: root=User quota mailbox=Trash bytes=+104857600 messages=0 doveadm(user(a)example.org): Debug: Quota warning: bytes=1992294400 (95%) messages=0 reverse=no command=quota-warning 95 user(a)example.org doveadm(user(a)example.org): Debug: Quota warning: bytes=1677721600 (80%) messages=0 reverse=no command=quota-warning 80 user(a)example.org doveadm(user(a)example.org): Debug: dict quota: user=user(a)example.org, uri=proxy::quota, noenforcing=0 doveadm(user(a)example.org): Debug: fs: root=/mail/dovecot/example.org/user/mail, index=, control=, inbox=, alt= doveadm(user(a)example.org): Debug: Namespace : Using permissions from /mail/dovecot/example.org/user/mail: mode=0700 gid=-1 dsync(user(a)example.org): Debug: Effective uid=1000, gid=1000, home=/mail/dovecot/example.org/user dsync(user(a)example.org): Debug: Quota root: name=User quota backend=dict args=:proxy::quota dsync(user(a)example.org): Debug: Quota rule: root=User quota mailbox=* bytes=2097152000 messages=0 dsync(user(a)example.org): Debug: Quota rule: root=User quota mailbox=Trash bytes=+104857600 messages=0 dsync(user(a)example.org): Debug: Quota warning: bytes=1992294400 (95%) messages=0 reverse=no command=quota-warning 95 user(a)example.org dsync(user(a)example.org): Debug: Quota warning: bytes=1677721600 (80%) messages=0 reverse=no command=quota-warning 80 user(a)example.org dsync(user(a)example.org): Debug: dict quota: user=user(a)example.org, uri=proxy::quota, noenforcing=0 dsync(user(a)example.org): Debug: imapc: root=, index=, control=, inbox=, alt= dsync(user(a)example.org): Debug: imapc(local-mailbox:18143): Looking up IP address dsync(user(a)example.org): Debug: imapc(local-mailbox:18143): Connecting to 10.10.10.10:18143 dsync(user(a)example.org): Debug: imapc(local-mailbox:18143): Server capabilities: IMAP4 IMAP4rev1 AUTH=LOGIN ACL NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE dsync(user(a)example.org): Debug: imapc(local-mailbox:18143): Authenticating as user(a)example.org dsync(user(a)example.org): Debug: imapc(local-mailbox:18143): Authenticated successfully dsync(user(a)example.org): Debug: imapc(local-mailbox:18143): Looking up IP address dsync(user(a)example.org): Debug: imapc(local-mailbox:18143): Connecting to 10.10.10.10:18143 dsync(user(a)example.org): Debug: imapc(local-mailbox:18143): Server capabilities: IMAP4 IMAP4rev1 AUTH=LOGIN ACL NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE dsync(user(a)example.org): Debug: imapc(local-mailbox:18143): Authenticating as user(a)example.org dsync(user(a)example.org): Debug: imapc(local-mailbox:18143): Authenticated successfully dsync(user(a)example.org): Warning: Destination mailbox Sent has been modified, need to recreate it before we can continue syncing dsync(user(a)example.org): Warning: Mailbox changes caused a desync. You may want to run dsync again. dsync(user(a)example.org): Debug: imapc(local-mailbox:18143): Disconnected dsync(user(a)example.org): Debug: imapc(local-mailbox:18143): Disconnected i think the problem could be that the account name on the remote server and the local server is absolute identical and doveadm backup has therefore problems discerning between the two locations. But that's only a stab in the dark and any help is appreciated. Kind regards Reinhard

3 9

[Dovecot] Default for non-present LDAP attributes?
by Edgar Fuß 28 Jun '12

28 Jun '12

With 1.2, is there a syntax to, for LDAP lookups, use a given fixed replacement for a non-present LDAP attribute? E.g. something that would extend user_attrs = mailFileServer=mail=maildir:/import/mail/%$/%d to use maildir:/import/mail/foo/%d in case the mailFileServer attribute is not present?

2 3