- 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