- dovecot - dovecot.org

[Dovecot] Dsync and compressed mailboxes
by Joseba Torre 13 Jan '12

13 Jan '12

Hi, I will begin two migrations next week, and in both cases I plan to use compressed mailboxes with mdbox format. But in the last minute one doubt has appeared: is dsync aware of compressed mailboxes? I'm not sure if dsync -u $USER mirror mdbox:compressed_mdbox_path works, or if I have to use something else (I guess that with a running dovecot dsync backup should work). Thanks.

2 1

[Dovecot] (no subject)
by Geoffrey Broadwell 13 Jan '12

13 Jan '12

I'm working on a Dovecot plugin, but I'm pretty new to Dovecot, so there's a LOT to learn about the code base and it's pretty slow going. I've got a few things coded so far, but I want to make sure I'm headed down the right path and get some advice before I go too much further. A couple years ago, I wrote some code for our Courier implementation that sent a magic UDP packet to a small server each time a user modified their voicemail IMAP folder. That UDP server would then connect back to Courier via IMAP again and check whether the folder had any unread messages left in it. Finally, it would contact our phone switches to modify the state of the message waiting indicator (MWI) on that user's phone line appropriately. Fast forward to now, and we want to migrate wholesale to Dovecot 2.x. The servers are all in place, they've been well tested and burned in (with Dovecot 2.0.15 I believe), and the final migration is pretty much waiting on a port to Dovecot of the MWI update functionality. The good news is that I originally spent some effort to isolate the UDP packet generation and delivery, and I used purely standard portable code as per APUE2, so I think that chunk of code should be reusable with only minor modifications. I'm aware that internally Dovecot has its own memory, buffer, and string management functions, but it doesn't feel like a win to try to convert the existing code. It's small, completely isolated, and well reviewed -- I'd be more afraid of using the new (to me) Dovecot API incorrectly than I am that the existing code has bugs in buffer handling. By cribbing from other plugins and editing appropriately, I've also created the skeleton for my plugin: Makefile, docs, conf snippet, .spec (I'll be deploying the plugin as an RPM), and so on. I've got the beginnings of the .h and .c written, just enough to init and deinit the plugin by calling mail_storage_hooks_{add,remove}() with some stub hook functions. This all seems good so far; test builds are error-free and seem sane. So now the hard part is writing the piece that I can't just crib from elsewhere -- making sure that I hook every place in Dovecot that the user's voicemail folder can be changed in a way that would change it between having one or more unread messages, and not having any unread messages at all (or vice-versa, of course). At the same time, I want to minimize the performance impact to Dovecot (and the load on the UDP server) by only hooking the places I need to, filtering out as many false positives as I can without introducing massive complexity, and only pinging the UDP server when it's most likely to notice a change in the state of that user's voicemail server. It seems to me that I need to at least capture mailbox_allocated from the mail_storage hooks, for a couple reasons: 1. The state of the voicemail folder could be changed because the entire folder is created, destroyed, or renamed. 2. I want to only do further checks when I'm sure I'm looking at the voicemail folder. There's no reason to do work when the user is working with any other folder. So now the questions: Does all of the above seem sane so far? Do I need to hook mail_allocated as well, or will I be able to see any change I need to monitor just from the mailbox? Finally, I'm lost about what operations on the mailbox and the mails within it I need to check. Can anyone offer some advice (or doc pointers) on this? Thank you! -'f

4 5

[Dovecot] dsync conversion and ldap attributes
by Jan-Frode Myklebust 13 Jan '12

13 Jan '12

I have: mail_home = /srv/mailstore/%256RHu/%d/%n mail_location = maildir:~/:INDEX=/indexes/%1u/%1.1u/%u userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } and the dovecot-ldap.conf.ext specifies: user_attrs = mailMessageStore=home, mailLocation=mail, mailQuota=quota_rule=*:storage=%$ Now I want to convert individual users to mdbox using dsync, but how to I tell location2 to not fetch "home" and "mail" from ldap and use different mail_location (mdbox:~/mdbox) ? I.e. I want converted accounts stored in mail_location mdbox:/srv/mailstore/%256RHu/%d/%n/mdbox. -jf

1 0

[Dovecot] more than 200 imap processes for one user
by Götz Reinicke 13 Jan '12

13 Jan '12

HI, recently I noticed, that our dovecot server (RH EL 5.7 dovecot-1.0.7-7.el5_7.1) 'fires' up a lot of imap processes only for one user. I counted 214 :-) most of tham in the 'S' state and are started nearly at the same time within 5 minutes. Usually users do have about 4 to 10 .... Dose anyone has an idea, what could be the cause? Thanks for any suggestion and best regards . Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 420 Fax +49 7141 969 55 420 E-Mail goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: Jürgen Walter MdL Staatssekretär im Ministerium für Wissenschaft, Forschung und Kunst Baden-Württemberg Geschäftsführer: Prof. Thomas Schadt

2 1

[Dovecot] proxy, managesieve and ssl?
by Nicolas KOWALSKI 12 Jan '12

12 Jan '12

Hello, On a dovecot 2.0.14 proxy, I found that proxying managesieve works well when using 'starttls' option in pass_attrs, but does not work when using 'ssl' option. The backend server is also dovecot 2.0.14; when using the ssl option, it reports "no auth attempts" in the logs about managesieve-login, and meanwhile the MUA, Thunderbird with sieve plugin, reports [TRYLATER] account is temporary disabled; no problem when using starttls option on the proxy, all works well. I would like to use IMAPs, instead of IMAP+STARTTLS, from proxy to backend, and have Managesieve still working. Is this supported? Thanks, -- Nicolas

3 4

[Dovecot] could not start dovecot - unknown section type
by Daminto Lie 12 Jan '12

12 Jan '12

Hi, I was wondering if I could get some help with the following error when trying to start dovecot service on Ubuntu Server 10.04. The error message is as follows * Starting IMAP/POP3 mail server dovecot Error: Error in configuration file /usr/local/etc/dovecot/dovecot.conf line 15: Unknown section type Fatal: Invalid configuration in /usr/local/etc/dovecot/dovecot.conf [fail] I have just managed to upgrade it from 1.2.19 to 2.0.17. Then, I tried to start the dovecot by running the command $ sudo /etc/init.d/dovecot start And I received the above message. Below is the configuration for dovecot.conf # 2.0.17 (684381041dc4+): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-37-generic-pae i686 Ubuntu 10.04.3 LTS ext4 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_username_format = %Lu auth_verbose = yes base_dir = /var/run/dovecot disable_plaintext_auth = no first_valid_uid = 1001 last_valid_uid = 2000 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%u/Maildir mail_privileged_group = mail passdb { driver = pam } passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { quota = maildir quota_rule = *:storage=3GB quota_rule2 = Trash:storage=20%% quota_rule3 = Spam:storage=10%% quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2 = storage=80%% /usr/local/bin/quota-warning.sh 80 } protocols = imap service auth { unix_listener /var/run/dovecot-auth-master { group = vmail mode = 0660 user = vmail } unix_listener /var/spool/postfix/private/auth { group = mail mode = 0660 user = postfix } user = root } service imap-login { chroot = login executable = /usr/lib/dovecot/imap-login inet_listener imap { address = * port = 143 } user = dovecot } service imap { executable = /usr/lib/dovecot/imap } service pop3-login { chroot = login user = dovecot } ssl = no userdb { driver = passwd } userdb { args = uid=1001 gid=1001 home=/home/vmail/%u allow_all_users=yes driver = static } verbose_proctitle = yes protocol imap { imap_client_workarounds = delay-newmail mail_plugins = quota imap_quota } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot-auth-master mail_plugins = quota postmaster_address = postmaster(a)example.com rejection_reason = Your message to <%t> was automatically rejected:%n%r sendmail_path = /usr/lib/sendmail } Any help would be greatly appreciated. Thank you

2 2

[Dovecot] Dovecot LDA and address extensions - folders flood
by huret deffgok 11 Jan '12

11 Jan '12

Hi list, This post is slightly OT, I hope no one will take offense. I was following the wiki on using dovecot LDA with postfix and implemented, for our future mail server, the address extensions mechanism: an email sent to "validUser+foldername(a)mydomain.com" will have dovecot-lda automagically create and subscribe the "foldername" folder. With some basic scripting I was able to create hundreds of folders in a few seconds. So my question is how do you implement this great feature in a secure way so that funny random people out there cant flood your mailbox with gigatons of folder. Thanks, kfx

2 3

[Dovecot] Log imap commands
by forumer＠smartmobili.com 11 Jan '12

11 Jan '12

Hi, I am trying to optimize an imap library and I am comparing with some existing webmail, for instance from roundcube I can log the imap commands with the following format : [11-Jan-2012 14:22:55 +0100]: [DBD1] S: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. [11-Jan-2012 14:22:55 +0100]: [DBD1] C: A0001 ID ("name" "Roundcube Webmail" "version" "0.6" "php" "5.3.5-1ubuntu7.4" "os" "Linux" "command" "/") [11-Jan-2012 14:22:55 +0100]: [DBD1] S: * ID NIL [11-Jan-2012 14:22:55 +0100]: [DBD1] S: A0001 OK ID completed. [11-Jan-2012 14:22:55 +0100]: [DBD1] C: A0002 AUTHENTICATE CRAM-MD5 [11-Jan-2012 14:22:55 +0100]: [DBD1] S: + RDM1MTE1NjkxOTQzODE4NDEuMTMyNjI4ODE3NUBzZC0zMDYzNT4= [11-Jan-2012 14:22:55 +0100]: [DBD1] C: d2ViZ3Vlc3RAc21hcnRtb2JpbGkuY29tIDczODMxNjUzZmVlYzdjNDVlNzRkYTg1YjIwMjk2NWM0 [11-Jan-2012 14:22:55 +0100]: [DBD1] S: A0002 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS FUZZY] Logged in [11-Jan-2012 14:22:55 +0100]: [DBD1] C: A0003 NAMESPACE [11-Jan-2012 14:22:55 +0100]: [DBD1] S: * NAMESPACE (("" ".")) NIL NIL [11-Jan-2012 14:22:55 +0100]: [DBD1] S: A0003 OK Namespace completed. [11-Jan-2012 14:22:55 +0100]: [DBD1] C: A0004 LOGOUT [11-Jan-2012 14:22:55 +0100]: [DBD1] S: * BYE Logging out ... And now I would like to do the same from my imap library so I have started wireshark but it's a bit messy and difficult to compare. I was wondering if dovecot allows to log imap communications ? Thanks

3 5

[Dovecot] How to solve a "Connection queue full problem" - dovecot version 2.0.16
by Didier Gervaise 11 Jan '12

11 Jan '12

Hello, I put in production dovecot yesterday. After an hour, nobody could log in ("Max number of imap connection" error message on Thunderbird) Afterward, I found these messages in the logs: Jan 10 09:21:20 mailsrv dovecot: [ID 583609 mail.info] imap-login: Disconnected: Connection queue full (no auth attempts): rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx In the panic, I changed these values in /usr/local/etc/dovecot/conf.d/10-master.conf default_process_limit = 20000 default_client_limit = 20000 This apparently solved the problem but now I have these messages when I start dovecot: Jan 11 14:41:08 mailsrvspare dovecot: [ID 583609 mail.info] master: Dovecot v2.0.15 starting up Jan 11 14:41:08 mailsrvspare dovecot: [ID 583609 mail.warning] config: Warning: service auth { client_limit=4096 } is lower than required under max. load (103024) Jan 11 14:41:08 mailsrvspare dovecot: [ID 583609 mail.warning] config: Warning: service anvil { client_limit=20000 } is lower than required under max. load (60003) What should I do ? - adding "service_count = 0" in service imap-login { ... } and removing the modifications I did in 10-master.conf ? or - should I configure differently default_process_limit and default_client_limit ? It is a small site (about 1000 users). Currently I have 666 imap processes and 136 imap-login processes. Additionnal infos: The Server is a Solaris 10 Sun X4540 32GB RAM mailsrv:~ % /usr/local/sbin/dovecot -n # 2.0.16: /usr/local/etc/dovecot/dovecot.conf doveconf: Warning: service auth { client_limit=4096 } is lower than required under max. load (103024) doveconf: Warning: service anvil { client_limit=20000 } is lower than required under max. load (60003) # OS: SunOS 5.10 i86pc default_client_limit = 20000 default_process_limit = 20000 disable_plaintext_auth = no first_valid_uid = 100 mail_debug = yes mail_plugins = " quota" mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { driver = pam } plugin { quota = maildir:User quota quota_rule = ?:storage=4G quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=90%% quota-warning 90 %u quota_warning3 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_dir = ~/ } postmaster_address = postmaster(a)esrf.fr protocols = imap pop3 lmtp sieve service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 } } service imap { process_limit = 2000 } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = dovecot } user = dovecot } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol lda { mail_plugins = " sieve" } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = " quota imap_quota" } Best Regards -- ________________________________________________________ Didier GERVAISE didier.gervaise(a)esrf.fr 04 76 88 27 28 System Administrator ---- Computing Services ESRF 6 rue Jules Horowitz 38043 Grenoble Cedex 09 ________________________________________________________

1 0

[Dovecot] Providing shared folders with multiple backend servers
by Sven Hartge 11 Jan '12

11 Jan '12

Hi *, I am currently in the planning stage for a "new and improved" mail system at my university. Right now, everything is on one big backend server but this is causing me increasing amounts of pain, beginning with the time a full backup takes. So naturally, I want to split this big server into smaller ones. To keep things simple, I want to pin a user to a server so I can avoid things like NFS or cluster aware filesystems. The mapping for each account is then inserted into the LDAP object for each user and the frontend proxy (perdition at the moment) then uses this information to route each access to the correct backend storage server running dovecot. So far this has been working nice with my test setup. But: I also have to provide shared folders for users. Thankfully users don't have the right to share their own folders, which makes things easier (I hope). Right now, the setup works like this, using Courier: - complete virtual mail setup - global shared folders configured in /etc/courier/shared/index - inside /home/shared-folder-name/Maildir/courierimapacl specific user get access to a folder - each folder a user has access is mapped to the namespace #shared like #shared.shared-folder-name Now, if I split my backend storage server into multiple ones and user-A is on server-1 and user-B is on server-2, but both need to access the same shared folder, I have a problem. I could of course move all users needing access to a shared folder to the same server, but in the end, this will be a nightmare for me, because I forsee having to move users around on a daily basis. Right now, I am pondering with using an additional server with just the shared folders on it and using NFS (or a cluster FS) to mount the shared folder filesystem to each backend storage server, so each user has potential access to a shared folders data. Ideas? Suggestions? Nudges in the right direction? Grüße, Sven. -- Sigmentation fault. Core dumped.

6 34

[Dovecot] Dovecot under Virtual Host environment??
by sparkietm 10 Jan '12

10 Jan '12

Hi all, Could anyone point me to a walk-through of setting up Dovecot for multiple domains under a Virtual Host environment? I'd like to offer clients their own email domain for each virtual host e.g john(a)client_1.com, sue(a)client_2.com. I'm guessing this is fairly common set-up, but a search on "multiple domains" didn't bring much back. Also, would it be possible to offer each client webmail? Many thanks in advance Mark -- View this message in context: http://old.nabble.com/Dovecot-under-Virtual-Host-environment---tp33114381p3… Sent from the Dovecot mailing list archive at Nabble.com.

2 1

[Dovecot] dsync panic
by Jürgen Obermann 10 Jan '12

10 Jan '12

Hello, when I try to convert from mbox to mdbox with dsync with one user it always panics: # /opt/local/bin/dsync -v -u userxy backup ssh root@minerva1 /opt/local/bin/dsync -v -u userxy dsync-local(userxy): Info: Papierkorb: uidnext changed: 161 != 1 dsync-local(userxy): Info: INBOX: uidnext changed: 9139 != 9105 dsync-local(userxy): Info: Trash: uidnext changed: 3924 != 3915 dsync-local(userxy): Info: Drafts: uidnext changed: 1563 != 1 dsync-local(userxy): Info: Gesendet: uidnext changed: 369 != 1 dsync-local(userxy): Info: Sent: uidnext changed: 1955 != 1 dsync-remote(userxy): Panic: Trying to allocate 2147483648 bytes dsync-remote(userxy): Error: Raw backtrace: 0xff14bc30 -> 0xff1658c0 -> 0xff15744c -> 0xff157520 -> 0xff159d90 -> 0xff156540 -> 0xff15cf5c -> 0xff156540 -> 0xff157100 -> 0xff16d158 -> 0xff16cfe8 -> 0xff26e350 -> 0x251c4 -> 0x2547c -> 0x21110 -> 0x20494 -> 0x1f230 -> 0x1f3d4 -> 0xff15e46c -> 0xff15f738 -> 0xff15e530 -> 0xff140ec8 -> 0x1525c -> 0x14608 Abort dsync-local(userxy): Error: read() from worker server failed: EOF dsync-local(userxy): Error: Unexpected reply from server: My local configuration is: # /opt/local/bin/doveconf -n # 2.0.16: /opt/local/etc/dovecot/dovecot.conf # OS: SunOS 5.10 sun4v auth_verbose = yes disable_plaintext_auth = no lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = imap.hrz.uni-giessen.de localhost mail_fsync = always mail_location = mbox:~/Mail:INBOX=/var/mail/%u mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = mail_log notify zlib 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 mmap_disable = yes namespace { inbox = yes location = prefix = separator = / type = private } namespace { hidden = yes list = no location = prefix = Mail/ separator = / subscriptions = yes type = private } passdb { driver = pam } passdb { args = /opt/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { autocreate = Trash autocreate2 = caughtspam autocreate3 = Sent autocreate4 = Drafts autosubscribe = Trash autosubscribe2 = caughtspam autosubscribe3 = Sent autosubscribe4 = Drafts mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = postmaster(a)hrz.uni-giessen.de quota_full_tempfail = yes sendmail_path = /usr/lib/sendmail service auth { client_limit = 11120 } service imap-login { process_min_avail = 16 service_count = 0 vsz_limit = 640 M } service imap { process_limit = 4096 vsz_limit = 1 G } ssl_cert = </etc/ssl/imap_hrz.crt ssl_key = </etc/ssl/imap_hrz.key syslog_facility = local0 userdb { driver = passwd } version_ignore = yes protocol lda { info_log_path = log_path = mail_plugins = mail_log notify zlib sieve } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags mail_max_userip_connections = 20 mail_plugins = mail_log notify zlib autocreate imap_zlib } protocol lmtp { mail_plugins = mail_log notify zlib sieve } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xv%08Xu } On the remote side the configuration is # 2.0.16: /opt/local/etc/dovecot/dovecot.conf # OS: SunOS 5.10 sun4u zfs auth_debug = yes auth_debug_passwords = yes auth_verbose = yes disable_plaintext_auth = no lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = minerva1.hrz.uni-giessen.de mail_debug = yes mail_fsync = always mail_location = mdbox:/sanpool/mail%h/mdbox mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = mail_log notify quota zlib 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 mdbox_rotate_interval = 1 days mdbox_rotate_size = 16 M mmap_disable = yes namespace { inbox = yes location = prefix = separator = / type = private } namespace { hidden = yes list = no location = prefix = Mail/ separator = / subscriptions = yes type = private } namespace { location = maildir:/var/mail/public:CONTROL=/sanpool/mail/%u/Maildir/public:INDEX=/sanpool/mail/%u/Maildir/public prefix = Public/ separator = / subscriptions = no type = public } passdb { driver = pam } passdb { args = /opt/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { autocreate = Trash autocreate2 = caughtspam autocreate3 = Sent autocreate4 = Drafts autosubscribe = Trash autosubscribe2 = caughtspam autosubscribe3 = Sent autosubscribe4 = Drafts fts = squat mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = fs:Home-Verzeichnis:noenforcing zlib_save = gz zlib_save_level = 3 } postmaster_address = postmaster(a)hrz.uni-giessen.de quota_full_tempfail = yes sendmail_path = /usr/lib/sendmail service auth { client_limit = 11120 } service imap-login { process_min_avail = 16 service_count = 0 vsz_limit = 640 M } service imap { process_limit = 4096 vsz_limit = 1 G } ssl_cert = </etc/ssl/server.crt ssl_key = </etc/ssl/server.key syslog_facility = local0 userdb { driver = passwd } version_ignore = yes protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags mail_max_userip_connections = 20 mail_plugins = mail_log notify quota zlib autocreate fts fts_squat imap_quota imap_zlib } protocol lda { info_log_path = log_path = mail_plugins = mail_log notify quota zlib sieve } protocol lmtp { mail_plugins = mail_log notify quota zlib sieve } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xv%08Xu } Thank you, Jürgen Obermann Hochschulrechenzentrum der Justus-Liebig-Universität Gießen Heinrich-Buff-Ring 44 Tel. 0641-9913054

2 2

[Dovecot] A small bug and a question about CONTEXT=SEARCH
by Anders 10 Jan '12

10 Jan '12

Hi, I have been looking at search and sorting with dovecot and have run into some things. The first one I think may be a minor bug because a set of commands result in the socket connection being closed without warning: UID SEARCH RETURN (SAVE COUNT) CHARSET UTF-8 (UNDELETED TEXT "foo") UID SEARCH RETURN (COUNT MIN) CHARSET UTF-8 () $ The empty paranthesis before the reference to the previous search result ($) is not legal IMAP, but should not cause the socket to be closed I think. Then I have question about RFC5267 and the announcement of CONTEXT=SEARCH in the capabilities. I think this RFC is supported by dovecot, or maybe just part of the RFC is supported? At least when I include the CONTEXT ADDTO or REMOVEFROM keywords I get an error, but UPDATE and CANCELUPDATE seem to be supported. The RFC has been updated by the RFC describing the NOTIFY extension to IMAP so maybe it has been decided to not add these keywords until a later time? I am using dovecot version 2.0.15 (with patches from Apple). Best Regards Anders

2 1

[Dovecot] rewriting mail_location
by Burckhard Schmidt 10 Jan '12

10 Jan '12

Hello, I have LDAP as userdb. Entries containing attributes mail=alias.user1(a)some.domain.de and uid=user1 Mail to alias.user1(a)some.domain.de gets delivered into /datatest/user/alias.user1 instead of /datatest/user/user1 by lda. I have userdb { args = /usr/dovecot/etc/ldapuser.conf driver = ldap } with a ldapuser.conf: hosts ... base ... user_filter = (&(|(mail=%u)(mail=%n(a)some.domain) (uid=%u))(objectClass=posixAccount)) user_attrs = uid=mail_location=maildir:/datatest/user/%$, uidNumber=29,gidNumber=133 I hoped local part of attribute mail could be replaced by uid for local delivery with dovecots lda? Any hints how to do that? (With postfix I could rewrite the address to uid@host and use local_transport = dovecot.) postfix has virtual_transport = dovecot. LDAP entry: mail: alias.user1(a)some.domain.de uid: user1 homeDirectory: /dev/null uidNumber: 464 gidNumber: 100 mail to alias.user1(a)some.domain.de Jan 10 14:03:24 ubu1004 postfix/qmgr[25221]: C434D1EE: from=<user@domain>, size=239, nrcpt=1 (queue active) Jan 10 14:03:24 ubu1004 dovecot: lda: Debug: Loading modules from directory: /usr/dovecot/lib/dovecot Jan 10 14:03:24 ubu1004 dovecot: lda: Debug: Module loaded: /usr/dovecot/lib/dovecot/lib20_autocreate_plugin.so Jan 10 14:03:24 ubu1004 dovecot: auth: Debug: master in: USER#0111#011alias.user1#011service=lda Jan 10 14:03:24 ubu1004 dovecot: auth: Debug: ldap(alias.user1): user search: base=ou=users,ou=...,c=de scope=subtree filter=(&(|(mail=alias.user1)(mail=alias.user1(a)some.domain.de)(uid=alias.user1))(objectClass=posixAccount)) fields=uid,uidNumber,gidNumber some substitutions are visibly: Jan 10 14:03:24 ubu1004 dovecot: auth: Debug: ldap(alias.user1): result: uid(location=maildir:/datatest/user/%$/maildir)=user1 gidNumber(133)=100 uidNumber(29)=464 Jan 10 14:03:24 ubu1004 dovecot: auth: Debug: master out: USER#0111#011alias.user1#011location=maildir:/datatest/user/user1/maildir#011133=100#01129=464 Jan 10 14:03:24 ubu1004 dovecot: lda: Debug: auth input: alias.user1 location=maildir:/datatest/user/user1/maildir 133=100 29=464 Jan 10 14:03:24 ubu1004 dovecot: lda: Debug: Added userdb setting: plugin/location=maildir:/datatest/user/user1/maildir but alias "alias.user1" still used for delivery: Jan 10 14:03:24 ubu1004 dovecot: lda: Debug: Added userdb setting: plugin/133=100 Jan 10 14:03:24 ubu1004 dovecot: lda: Debug: Added userdb setting: plugin/29=464 Jan 10 14:03:24 ubu1004 dovecot: lda(alias.user1): Debug: Effective uid=29, gid=133, home= Jan 10 14:03:24 ubu1004 dovecot: lda(alias.user1): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/datatest/user/alias.user1/maildir:INDEX=/datatest/addons/index/alias.user1:CONTROL=/datatest/user/alias.user1/control:LAYOUT=fs Jan 10 14:03:24 ubu1004 dovecot: lda(alias.user1): Debug: fs: root=/datatest/user/alias.user1/maildir, index=/datatest/addons/index/alias.user1, control=/datatest/user/alias.user1/control, inbox=/datatest/user/alias.user1/maildir, alt= Jan 10 14:03:24 ubu1004 dovecot: lda(alias.user1): Debug: Namespace : Using permissions from /datatest/user/alias.user1/maildir: mode=0700 gid=-1 Jan 10 14:03:24 ubu1004 dovecot: lda(alias.user1): Debug: none: root=, index=, control=, inbox=, alt= Jan 10 14:03:24 ubu1004 dovecot: lda(alias.user1): Debug: Destination address: alias.user1@ubu1004 (source: user@hostname) Jan 10 14:03:24 ubu1004 dovecot: lda(alias.user1): msgid=unspecified: saved mail to INBOX Jan 10 14:03:24 ubu1004 postfix/pipe[25226]: C434D1EE: to=<alias.user1(a)some.domain.de>, relay=dovecot, delay=14, delays=14/0.01/0/0.02, dsn=2.0.0, status=sent (delivered via dovecot service) Jan 10 14:03:24 ubu1004 postfix/qmgr[25221]: C434D1EE: removed dovecot -n # 2.0.17 (684381041dc4+): /usr/dovecot/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-34-generic-pae i686 Ubuntu 10.04.3 LTS ext4 mail_gid = sysdov mail_location = maildir:/datatest/user/%n/maildir:INDEX=/datatest/addons/index/%n:CONTROL=/datatest/user/%n/control:LAYOUT=fs mail_plugins = autocreate mail_uid = sysdov passdb { args = failure_show_msg=yes imap driver = pam } service auth { client_limit = 30000 unix_listener auth-userdb { group = sysdov #effective 133 mode = 01204 user = sysdov #effective 29 } } userdb { args = /usr/dovecot/etc/ldapuser.conf driver = ldap } protocol lda { mail_plugins = autocreate } and ldapuser.conf: hosts ... base ... user_filter = (&(|(mail=%u)(mail=%n(a)some.domain) (uid=%u))(objectClass=posixAccount)) user_attrs = uid=mail_location=maildir:/datatest/user/%$, uidNumber=29,gidNumber=133 local part of mail should be replaced by uid for local delivery -- Regards --- Burckhard Schmidt

1 0

[Dovecot] Proxy login failures
by Urban Loesch 10 Jan '12

10 Jan '12

Hi, I'm using two dovecot pop3/imap proxies in front of our dovecot servers. Since some days I see many of the following errors in the logs of the two proxy-servers: ... dovecot: pop3-login: Error: proxy: Remote "IPV6-IP":110 disconnected: Connection closed: Connection reset by peer (state=0): user=<myuser>, method=PLAIN, rip=remote-ip, lip=localip ... dovecot: imap-login: Error: proxy: Remote "IPV6-IP":143 disconnected: Connection closed: Connection reset by peer (state=0): user=<myuser>, method=PLAIN, rip=remote-ip, lip=localip ... When this happens the Client gets the following error from the proxy: -ERR [IN-USE] Account is temporarily unavailable. System-details: OS: Debian Linux Proxy: 2.0.5-0~auto+23 Backend: 2.0.13-0~auto+54 Have you any idea what could cause this type of error? Thanks and regards Urban Loesch doveconf -n from one of our backendservers: # 2.0.13 (02d97fb66047): /etc/dovecot/dovecot.conf # OS: Linux 2.6.38.8-vs2.3.0.37-rc17-rol-em64t-timerp x86_64 Debian 6.0.2 ext4 auth_cache_negative_ttl = 0 auth_cache_size = 40 M auth_cache_ttl = 12 hours auth_mechanisms = plain login auth_username_format = %Lu auth_verbose = yes deliver_log_format = msgid=%m: %$ %p %w disable_plaintext_auth = no login_trusted_networks = our Proxy IP's (v4 and v6) mail_gid = mailstore mail_location = mdbox:/home/vmail/%d/%n:INDEX=/home/dovecotindex/%d/%n mail_plugins = " quota mail_log notify zlib" mail_uid = mailstore 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 imapflags notify mdbox_rotate_size = 5 M passdb { args = /etc/dovecot/dovecot-sql-account.conf driver = sql } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size from mail_log_group_events = no quota = dict:Storage used::file:%h/dovecot-quota sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags sieve_max_redirects = 10 zlib_save = gz zlib_save_level = 5 } protocols = imap pop3 lmtp sieve service imap-login { inet_listener imap { port = 143 } service_count = 0 vsz_limit = 256 M } service lmtp { inet_listener lmtp { address = * port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } vsz_limit = 512 M } service pop3-login { inet_listener pop3 { port = 110 } service_count = 0 vsz_limit = 256 M } ssl = no ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql-account.conf driver = sql } protocol lmtp { mail_plugins = " quota mail_log notify zlib sieve zlib" } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 40 mail_plugins = " quota mail_log notify zlib imap_quota imap_zlib" } protocol pop3 { mail_plugins = " quota mail_log notify zlib" pop3_logout_format = bytes_sent=%o top=%t/%p, retr=%r/%b, del=%d/%m, size=%s uidl_hash=%u }

2 4

[Dovecot] Strange error: DIGEST-MD5 mechanism can't be supported with given passdbs
by Yubao Liu 10 Jan '12

10 Jan '12

Hi all, I have no idea about that message, here is my configuration, what's wrong? Debian testing, Dovecot 2.0.15 $ doveconf -n # 2.0.15: /etc/dovecot/dovecot.conf # OS: Linux 3.1.0-1-686-pae i686 Debian wheezy/sid auth_default_realm = corp.example.com auth_krb5_keytab = /etc/dovecot.keytab auth_master_user_separator = * auth_mechanisms = gssapi digest-md5 auth_realms = corp.example.com auth_username_format = %n first_valid_gid = 1000 first_valid_uid = 1000 mail_location = mdbox:/srv/mail/%u/Mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { driver = pam } plugin { sieve = /srv/mail/%u/.dovecot.sieve sieve_dir = /srv/mail/%u/sieve } protocols = " imap lmtp sieve" service auth { unix_listener auth-client { group = Debian-exim mode = 0660 } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = home=/srv/mail/%u driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } # cat /etc/dovecot/master-users xxx@corp.example.com:zzzzzzzz The zzzzz is obtained by "doveadm pw -s digest-md5 -u xxx(a)corp.example.com", I tried to add prefix "{DIGEST-MD5}" before the generated hash and/or add "scheme=DIGEST-MD5" to the passwd-file passdb's "args" option, both don't help. The error message: dovecot: master: Dovecot v2.0.15 starting up (core dumps disabled) dovecot: auth: Fatal: DIGEST-MD5 mechanism can't be supported with given passdbs gold dovecot: master: Error: service(auth): command startup failed, throttling I opened debug auth log, it showed dovecot read /etc/dovecot/master-users and parsed one line, then the error occurred. Doesn't passwd-file passdb support digest-md5 password scheme? If it doesn't support, how do I configure digest-md5 auth mechanism with digest-md5 password scheme for virtual users? Regards, Yubao Liu

4 10

[Dovecot] Postfix user map
by Timo Sirainen 10 Jan '12

10 Jan '12

http://hg.dovecot.org/dovecot-2.1/rev/f562bcaca215 implements "postmap" type sockets, which follow Postfix's tcp_table(5) protocol. So you can ask: get user@domain and Dovecot answers one of: - 200 1 - 500 User not found - 400 Internal failure So you can use this with Postfix: virtual_mailbox_maps = tcp:127.0.0.1:1234 With Dovecot you can enable it with: service auth { inet_listener postmap { listen = 127.0.0.1 port = 1234 } } Anyone have ideas if this could be improved, or used for some other purposes?

3 9

[Dovecot] Solr plugin
by Daniel L. Miller 10 Jan '12

10 Jan '12

On 1/8/2012 3:40 PM, Daniel L. Miller wrote: > On 1/6/2012 12:32 PM, Daniel L. Miller wrote: >> On 1/6/2012 9:36 AM, Timo Sirainen wrote: >>> On 6.1.2012, at 19.30, Daniel L. Miller wrote: >>> > > Jan 8 15:40:09 bubba dovecot: imap(user1(a)domain.com): Error: > fts_solr: Lookup failed: 400 undefined field CC > Jan 8 15:40:09 bubba dovecot: imap: Error: > > Looking at the Solr output - looks like the CC parameter is being capitalized while all the other fieldnames are lowercase. -- Daniel

2 3

[Dovecot] uid / gid and systemusers
by xamiw＠arcor.de 10 Jan '12

10 Jan '12

Hi all, I'm facing a problem when a user (q and g in this example) is logging into dovecot. Can anybody tell some hint? Thanks in advance. George /var/log/mail.log: ... Jan 8 16:18:28 test dovecot: User q is missing UID (see mail_uid setting) Jan 8 16:18:28 test dovecot: imap-login: Internal login failure (auth failed, 1 attempts): user=<q>, method=PLAIN, rip=AAA.BBB.CCC.DDD, lip=EEE.FFF.GGG.HHH TLS <--- edited by me Jan 8 16:18:28 test dovecot: dovecot: User g is missing UID (see mail_uid setting) Jan 8 16:18:28 test dovecot: imap-login: Internal login failure (auth failed, 1 attempts): user=<g>, method=PLAIN, rip=AAA.BBB.CCC.DDD, lip=EEE.FFF.GGG.HHH TLS <--- edited by me /etc/dovecot/dovecot.conf: protocols = imaps disable_plaintext_auth = yes shutdown_clients = yes log_timestamp = "%Y-%m-%d %H:%M:%S " ssl = yes ssl_cert_file = /etc/ssl/certs/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail mbox_write_locks = fnctl dotlock auth default { mechanisms = plain passdb shadow { } } /etc/passwd: ... g:x:1000:1000:test1,,,:/home/g:/bin/bash q:x:1001:1001:test2,,,:/home/q:/bin/bash /etc/group: ... g:x:1000: q:x:1001:

2 2

[Dovecot] FTS-Solr plugin
by Daniel L. Miller 09 Jan '12

09 Jan '12

Solr plugin appears to break when mailbox names have an ampersand in the name. The messages appear to indicate '&' gets translated to '&--'. -- Daniel

2 1

[Dovecot] change initial permissions on creation of mail folder
by mailinglist 09 Jan '12

09 Jan '12

Installed dovcot from Debian .deb file. Creating a new account for system users sets permission for user-only. Where to change initial permissions on creation of mail folder and other subdirectories. Installed dovecot using "apt-get install dovecot-imapd dovecot-pop3d". Any time when I create a new account in my mail client for a system user, Dovecot tries to create ~/mail/.imap/INBOX. The permissions for mail and .imap are set to 0700. By this permissions INBOX can not be created leading to an error message in log files. When I manualy change the permissions to 0770, INBOX is created

2 1

[Dovecot] failed: Too many levels of symbolic links
by David Egbert 09 Jan '12

09 Jan '12

All, My dovecot install works great except for one error I keep seeing this in my logs. The folder has 7138 messages in it. I am informed the user they needed to reduce the number of messages in the folder and believe this will fix the problem. My question is about where the problem lies. Is the problem related to an internal limit with Dovecot v2.0.15 or with my Debian (3.1.0-1-amd64)? Thanks --- dovecot: imap(XXXXX(a)XXXXX.com): Error: readdir(/XXXX/XXXX/XXXXXXXXX/XXXXX/XXXXXXX/XXXXXXXXXXXXXXXXXXX/XXX) failed: Too many levels of symbolic links David Egbert Paperclip Systems, LLC --- This message, its contents, and attachments are confidential and are only authorized for the intended recipient. Disclosure, re-distribution, or use of said information is strictly prohibited, and may be excluded from disclosure by applicable law. If you are not the intended recipient, or their intermediary, please notify the sender and delete this message.

2 6

Re: [Dovecot] Newbie: LDA Isn't Logging
by Michael Papet 09 Jan '12

09 Jan '12

I did some testing on a Debian testing VM. I built 2.0.17 from sources and copied the config straight over from the malfunctioning machine. LDA logging worked. So, it could be something about my system. But, running /usr/lib/dovecot/deliver still doesn't return a value on the command line as documented on the wiki. I've attached strace files from both the malfunctioning Debian packages machine and the built from sources VM. Unfortunately, I'm a new strace user, so I don't know what it all means. Michael --- On Tue, 1/3/12, Timo Sirainen <tss_no_spam(a)iki.fi> wrote: > From: Timo Sirainen <tss_no_spam(a)iki.fi> > Subject: Re: [Dovecot] Newbie: LDA Isn't Logging > To: "Michael" <mpapet_no_spam(a)yahoo.com> > Cc: dovecot(a)dovecot.org > Date: Tuesday, January 3, 2012, 4:15 AM > On Mon, 2012-01-02 at 22:48 -0800, > Michael wrote: > > Hi, > > > > I'm a newbie having some trouble getting deliver to > log anything. Related to this, there are no return > values unless the -d is missing. I'm using LDAP to > store virtual domain and user account information. > > > > Test #1: /usr/lib/dovecot/deliver -e -f mpapet(a)yahoo.com > -d zed(a)mailswansong.dom > < bad.mail > > Expected result: supposed to fail, there's no zed > account via ldap lookup and supposed to get a return code > per the wiki at http://wiki2.dovecot.org/LDA. > Supposed to log too. > > Actual result: nothing gets delivered, no return code, > nothing is logged. > > As in return code is 0? Something's definitely wrong there > then. > > First check that deliver at least reads the config file. > Add something > broken in there, such as: "foo=bar" at the beginning of > dovecot.conf. > Does deliver fail now? > > Also running deliver via strace could show something > useful. > > >

2 1

[Dovecot] Resetting a UID
by Tom Clark 09 Jan '12

09 Jan '12

Hi, We've got a client with a Blackberry that hass deleted his emails off his Blackberry device. The BES won't re-download the messages as it believes it has already downloaded them (apparently it matches on UID). Is there any way of resetting a folder (and messages in the folder) UID? I know in courier you used to be able to touch the directory. Thanks, Tom Clark

2 1

Re: [Dovecot] dovecot: imap-login: Disconnected (no auth attempts)
by Robert Schetterer 09 Jan '12

09 Jan '12

Am 09.01.2012 10:37, schrieb Simon Loewenthal: > On 09/01/12 10:27, Robert Schetterer wrote: >> Am 09.01.2012 10:16, schrieb J4K: >>> Morning everyone, >>> >>> On the 8th of Jan the TLS/SSL certificate I use with Dovecot expired. I >>> replaced it with a new on the 9th of Jan. I tested this with >>> Thunderbird and all is well. >>> >>> This morning people tell me they cannot get their email using their >>> mobile telephones : K9 Mail >>> >>> I have reverted the SSL cert back to the old one just in case. >>> Thunderbird will works. >>> >>> >>> Dovecot 1:1.2.15-7 running on Debian 6 >>> >>> The messages in the logs are: >>> >>> Jan 9 10:11:37 logout dovecot: imap-login: Disconnected (no auth >>> attempts): rip=90.131.95.130, lip=88.119.95.13, TLS: Disconnected >>> Jan 9 10:11:38 logout dovecot: imap-login: Disconnected (no auth >>> attempts): rip=90.131.95.130, lip=88.119.95.13, TLS: Disconnected >>> >>> In dovecot.conf I have this set : >>> >>> disable_plaintext_auth = no >>> >>> And the auth default mechanisms are set to: >>> mechanisms = plain login >>> >>> What is strange is the only item that changed is the SSL cert, which has >>> since been changed back to the old one (which has expired... ^^). >>> >>> Any ideas where I may look or change? >>> >>> Regards, S >> if you only changed the crt etc, and youre sure you did everything right >> >> perhaps you have forgot adding a needed intermediate cert ? >> >> read here >> http://www.trustico.co.uk/install/how-to-install-ssl-certificate.php >> >> Required Intermediate Certificates (CA Certificates) >> >> To successfully install your SSL Certificate you may be required to >> install an Intermediate CA Certificate. Please review the above >> installation instructions carefully to determine if an Intermediate CA >> Certificate is required, how to obtain it and correctly import it into >> your system. For more information please Contact Us. >> Alternatively, and for systems not covered by the above installation >> instructions, please use our Intermediate Certificate Wizard to find the >> correct CA Certificate or Root Bundle that is required for your SSL >> Certificate to function correctly. Find Out More Information > I know that the intermediate certs are messed up, which is why I rolled > back to the old expired certificate. I did not expect an expired > certificate to block authentication, and it does not mean that it does > block. The problem may be elsewhere. that might be a k9 problem ( older versions ) or in android older versions, is there a ignore ssl failure option as workaround what does thunderbird tell you about the new cert ? but for sure the problem may elsewhere > > -- > PGP is optional: 4BA78604 > simon @ klunky . org > simon @ klunky . co.uk > I won't accept your confidentiality > agreement, and your Emails are kept. > ~Ö¿Ö~ > -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

3 2