- dovecot - dovecot.org

[Dovecot] v1.0.2 release candidate
by Timo Sirainen 13 Jul '07

13 Jul '07

http://dovecot.org/tmp/dovecot-1.0.2-rc.tar.gz Unless someone finds something broken, I'll release v1.0.2 in a few days. The most important changes since v1.0.1: * dbox isn't built anymore by default. It will be redesigned so it shouldn't be used. + Maildir: Support reading dovecot-uidlist (v3) files created by Dovecot v1.1. - Maildir: "UIDVALIDITY changed" errors could happen with newly created mailboxes - If "INBOX." namespace was used, LIST returned it with \HasNoChildren which caused some clients not to show any other mailboxes. - Maildir++ quota: If multiple processes were updating maildirsize at the same time, we failed with "Unknown error". - IMAP: IDLE didn't actually disconnect client after 30 minutes of inactivity. - LDAP passdb/userdb was leaking memory - deliver: %variables in plugin {} weren't expanded

4 9

[Dovecot] Monitoring Recomendations
by Dehnert James Sr 13 Jul '07

13 Jul '07

I have a client that I have installed Dovecot 1.0.1 for is having some performance issues. Especially when using IMAP from various Outlook clients. I have TLS installed and all the IMAP connections are secured. I'm wondering is anyone has any recommendations for monitoring dovecot performance. I'd like to try and nail down where the real performance issues are. I suspect outlook, but I want to eliminate Dovecot as the cause of any problems, or, if I have a problem with Dovecot, I want to identify any issues I can and fix them. Thanks, Zeke -- James "Zeke" Dehnert mailto:jdehnert@norcalnetworks.com Phone: +1 707.546.6620 x602 Fax: +1 707.324.8043 "Life is racing, everything else is just waiting"

4 4

[Dovecot] dovecot sieve notify mailto
by Kupor Laszlo 13 Jul '07

13 Jul '07

Hello, I try to migrate to dovecot-lda from procmail, but some script can't run under lda cmusieve plugin. dovecot version: dovecot-1.0(debian) revelant config dovecot.conf: protocol lda { postmaster_address = postmaster(a)wizard.dunanet.hu hostname = wizard.dunanet.hu mail_plugin_dir = /usr/lib/dovecot/modules/lda #sendmail_path = /usr/lib/sendmail auth_socket_path = /var/run/dovecot/auth-master mail_plugins = cmusieve } .forward | "/usr/lib/dovecot/deliver" .dovecot.sieve (revelant part) require ["fileinto","notify"]; ... ... notify :method "mailto" :options "9141141(a)sms1.pgsm.hu" :id "test" :message; if true { keep; } ... I can compile with sievec, deliver also can compile to .dovecot.sievec (no errors) i can decompile with sieved: 1935: NOTIFY METHOD({6}mailto) ID({5}willy) OPTIONS {20}9141141(a)sms1.pgsm.hu PRIORITY(13) MESSAGE({17}$from$: $subject$) 1954: IF (ends at 1957)true 1957:JUMP 1960 1959: KEEP full len is: 1960 But notification does not work.. Jul 3 17:50:38 WiZARD deliver(willy): Loading modules from directory: /usr/lib/dovecot/modules/lda Jul 3 17:50:38 WiZARD deliver(willy): Module loaded: /usr/lib/dovecot/modules/lda/lib90_cmusieve_plugin.so Jul 3 17:50:38 WiZARD deliver(willy): mbox: data=/home/willy/mail/:INBOX=/var/mail/willy Jul 3 17:50:38 WiZARD deliver(willy): mbox: root=/home/willy/mail, index=/home/willy/mail, inbox=/var/mail/willy Jul 3 17:50:38 WiZARD deliver(willy): cmusieve: Using sieve path: /home/willy/.dovecot.sieve Jul 3 17:50:38 WiZARD deliver(willy): cmusieve: Executing script /home/willy/.dovecot.sievec Jul 3 17:50:38 WiZARD postfix/smtpd[15234]: disconnect from donci.dunanet.hu[62.77.204.40] Jul 3 17:50:38 WiZARD deliver(willy): msgid=<Pine.LNX.4.62.0707031750280.28802(a)donci.dunanet.hu>: saved mail to INBOX Jul 3 17:50:38 WiZARD deliver(willy): sieve runtime error: Notify: Generic Error Jul 3 17:50:38 WiZARD postfix/local[15239]: B31B419746C: to=<willy(a)wizard.dunanet.hu>, relay=local, delay=0.1, delays=0.07/0/0/0.02, dsn=2.0.0, status=sent (delivered to command: /usr/lib/dovecot/deliver) I always get sieve runtime error: Notify: Generic Error Fileinto, and redirect works fine, but notify does not. I try "dovecot-sieve-1-0-64a7986b5e55.tar.bz2" without success. Please help debug "Generic Error". Thanks, Udv.: Willy -- PGP GNUPG/1.0 ID = 5BFA0D36 Kupor Laszlo Attila <willy(a)dunanet.hu> Key fingerprint = 3F68 9483 5B65 8E2F CD30 5326 50F9 5A33 5BFA 0D36

3 5

[Dovecot] Quota Messages
by Hermann wacker 13 Jul '07

13 Jul '07

Hi @all, First: I'm sorry when my english isn't understandable, please just ask if I messed things up. I switched from Cyrus to Dovecot (Cyrus was on Debian Sarge, Dovecot is now on a Etch) and I'm quite happy with it. There is just one thing that I'm missing in Dovecot. in Cyrus when users reached 90% of their Quota, a message popped up in their Mailclients, telling them to clean up their Mailboxes. Dovecot delivers the quotausage to the Client (I can see in my Thunderbird a small Statusbar), but when you don't look carefully, you will mostly miss the point where you can delete the messages without having a fight with the quotalimit (because mails in trash using the quota). At the moment I'm using "quota = fs" so there is no good way to keep the trash out of the quotathing and that's not the point of my question. The question is: Is there a way where Dovecot (or Postfix) inform the user that his quota is reaching its limit? Or maybe the postmaster, thats not important. The important thing is a way where my mailsystem tells somebody that quotas are reaching their limits. Greetings from Germany Hermann Wacker Dovecot Version: 1.0.rc15 Postfix Version: 2.3.8-2+b1 quotaconf: # /etc/dovecot/dovecot.conf IEffective uid=65534, gid=65534 ILoading modules from directory: /usr/lib/dovecot/modules/imap IModule loaded: /usr/lib/dovecot/modules/imap/lib01_quota_plugin.so IModule loaded: /usr/lib/dovecot/modules/imap/lib02_imap_quota_plugin.so log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_extra_groups: mail mail_location: maildir:%h/mails mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: passdb: driver: shadow userdb: driver: passwd

2 1

[Dovecot] Quota exceeded messages
by Frank Church 13 Jul '07

13 Jul '07

When I try to move messages between folders I get 'Quota exceeded' messages. I installed dovecot without any major configuration and accounts are created with PostfixAdmin. Is there some common setting that I must be missing? Version in use is 1.0 rc26 - Frank

3 7

[Dovecot] Patches to log imap bandwidth?
by Jason Fesler 13 Jul '07

13 Jul '07

Anyone patch dovecot to syslog bytes transfered during a session or anything of that sort? I'm trying to track down imap bandwidth spikes, and unfortunately the uid (according to ipfw) for the imap port spikes is 0. (Presumably FreeBSD's ipfw accounting is based on who started the app instead of the effective user id?) -- Jason Fesler, email/jabber <jfesler(a)gigo.com> resume: http://jfesler.com "Give a man fire, and he'll be warm for a day; set a man on fire, and he'll be warm for the rest of his life."

2 2

[Dovecot] Today's stable hg pull destroyed dovecot...
by Ralf Hildebrandt 13 Jul '07

13 Jul '07

I performed a hg pull today for 1.0.1 and after recompilation my log was flooded with: Jul 12 10:29:21 postamt dovecot: IMAP(kxx4): UID larger than next_uid in file /home/k/j/kxx4/Maildir/dovecot-uidlist (6 >= 0) Jul 12 10:29:21 postamt dovecot: IMAP(rexxxes): UID larger than next_uid in file /home/r/e/rexxxes/Maildir/dovecot-uidlist (1 >= 0) Jul 12 10:29:21 postamt dovecot: IMAP(sxxkim): Maildir /home/s/i/sxxkim/Maildir sync: UIDVALIDITY changed (1184228955 -> 3086699759) and people were reporting "the IMAP server closing and dropping connections". I then downloaded 1.0.1 from the webpage, rebuilt and the problems are gone. Now I'm getting those: Jul 12 10:33:10 postamt dovecot: IMAP(blxxe): Corrupted index cache file /home/b/l/blxxe/Maildir/dovecot.index.cache: indexid changed Somethin amiss with the index code? -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin, 1759

2 1

[Dovecot] v1.1 status and benchmarks
by Timo Sirainen 13 Jul '07

13 Jul '07

v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to have a stable v1.1 in a month or two. The rest of the features that didn't make it into v1.1 will go to v1.2. I'll write more about this when v1.1 alpha is released. I also did a bit of benchmarking. v1.1's performance improvements are looking pretty great, it seems to be twice as fast as v1.0. v1.0: Maildir, dovecot-1.0 hg + inotify dotlock wait patch, mmap_disable=yes v1.1: Maildir, dovecot hg, mmap_disable=no cydir: Cydir, dovecot hg, mmap_disable=no 1 client -------- ./imaptest logout=0 seed=1 secs=10 clients=1 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 30% 5% v1.0: 1 1221 1179 1 2420 3458 323 1934 2419 2552 v1.1: 1 2606 2597 1 5221 7352 688 4181 5221 5489 cydir: 1 4495 4534 1 8960 12786 1216 7224 8959 9434 10 clients ---------- ./imaptest logout=0 seed=1 secs=10 clients=10 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 30% 5% v1.0: 10 2058 2102 10 4157 6019 1426 3348 4157 4391 v1.1: 10 5029 5072 10 10064 14352 3176 8092 10064 10624 cydir: 10 6332 6393 10 12664 17965 3958 10154 12663 13336

5 11

[Dovecot] NFS cache flush tester
by Timo Sirainen 12 Jul '07

12 Jul '07

http://dovecot.org/tools/nfstest.c I wrote a test utility that tests different ways to flush NFS attribute cache and data cache. Please test in your NFS setup and show me the results, so I can make Dovecot v1.1 works well with NFS. Run the test several times (3 should be enough) to make sure the output stays the same, because the attribute cache flushes might incorrectly say "OK". And of course attribute cache must not be disabled for this test to work. If you have other ideas how to flush either cache please tell me and I'll update the test utility. I'd like to have a way to flush the cache without having the NFS client send anything to server. Unfortunately all of the below ways do that. Results for Linux v2.6.15 and v2.6.18: Info: Testing attribute cache.. Info: Attr cache flush fchown(-1, -1): failed Info: Attr cache flush fchown(uid, gid): OK Info: Attr cache flush fchmod(mode): OK Info: Attr cache flush chown(-1, -1): failed Info: Attr cache flush chown(uid, gid): OK Info: Attr cache flush chmod(mode): OK Info: Testing data cache.. Info: data cache: Appends weren't noticed (ret = 0) Info: - Attribute cache flush helped Info: data cache (no caching): failed Info: data cache (attr cache): failed Info: data cache (lockf()): OK Info: data cache (flock(shared)): OK Info: data cache (flock(exclusive)): OK

7 25

[Dovecot] Problem with Dovecot SASL in Postfix
by Chris McMacken 12 Jul '07

12 Jul '07

I'm trying to configure my postfix server to use Dovecot as an SASL server and running into some problems. My server supports a couple of domain, I have multiple user/password files for multiple domains to make the files a little easier to manage. Not sure if this question should belong in the dovecot mailing list or the postfix one, but here goes anyway. I have everything configured to use CRAM-MD5 authentication, including my mail client. Here the auth section of my dovecot conf. auth default { mechanisms = plain cram-md5 passdb passwd-file { # Path for passwd-file args = /usr/local/etc/dovecot/%d/passwd } userdb passwd-file { # Path for passwd-file args = /usr/local/etc/dovecot/%d/passwd } user = root # It's possible to export the authentication interface to other programs: socket listen { client { # The client socket is generally safe to export to everyone. Typical use # is to export it to your SMTP server so it can do SMTP AUTH lookups # using it. path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } heres a sample line from one of the passwd files: chrism:{CRAM-MD5}a67a65704086a046b3f875d1eaac8cb5c6fd13406507fead30d9bcb1bf… and to login through SASL I am trying to use the username chrism(a)example.com when I use the full email address like this to login like this I get this output into my postfix log: Jul 10 18:46:59 mail postfix/smtpd[57343]: connect from unknown[12.244.148.123] Jul 10 18:46:59 mail postfix/smtpd[57343]: NOQUEUE: reject: RCPT from unknown[12.244.148.123]: 554 5.7.1 <chrism(a)gmail.com>: Relay access denied; from=<chrism(a)example.com> to=<chrism(a)gmail.com> proto=ESMTP helo=<[192.168.1.14]> Jul 10 18:47:00 mail postfix/smtpd[57343]: disconnect from unknown[12.244.148.123] (not actually using example.com but I changed it here) heres my smtpd_recipient_restricitons from postconf smtpd_recipient_restrictions = permit_mynetworks, reject_unauth_destination, permit_sasl_authenticated so when I use the full user name (chrism(a)example.com) it doesn't appear to even attempt logging into the sasl server. If I change it to simply chrism, heres the output: Jul 10 18:50:36 mail postfix/smtpd[57356]: connect from unknown[12.244.148.123] Jul 10 18:50:38 mail postfix/smtpd[57356]: warning: unknown[12.244.148.123]: SASL CRAM-MD5 authentication failed: PDI3NjU4MTE4NDExMTQzN0BtYWlsPg== Jul 10 18:50:39 mail postfix/smtpd[57356]: lost connection after AUTH from unknown[12.244.148.123] Jul 10 18:50:39 mail postfix/smtpd[57356]: disconnect from unknown[12.244.148.123] if I put my user name in as chrism and don't add the @example.com it tried to login but it can't login. anyone have any ideas?

2 1