- dovecot - dovecot.org

[Dovecot] quota warning - take 2
by Nicolas Boullis 16 Jul '07

16 Jul '07

Hi, About one month ago, I sent a patch to this list to implement warnings when a user is close to reach his quota. I tried to follow Timo's advice to improve my code, and here (at last) is a new patch. Things I did not fix: - This patch is still for dovecot 1.0, as I will need warnings with dovecot 1.0. I may rewrite it for CVS HEAD in the future but can't promise. - I'm still using system() rather than fork()+exec()+waitpid() since I don't know a good time to run waitpid(). Comments are welcome. Timo, will you consider to add this to your unofficial patches? Cheers, Nicolas Boullis

3 5

[Dovecot] v1.0.2 released
by Timo Sirainen 15 Jul '07

15 Jul '07

http://dovecot.org/releases/dovecot-1.0.2.tar.gz http://dovecot.org/releases/dovecot-1.0.2.tar.gz.sig Fixes several bugs. This release also adds compatibility with upcoming Dovecot v1.1 so it'll be possible to upgrade to v1.1 and back to v1.0.2 without anything breaking. * 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 - deliver: Don't bounce the mail if Sieve plugin returns failure

2 2

[Dovecot] INBOX empty
by Mohamed Navas 15 Jul '07

15 Jul '07

Hi list, We have been using the mail server with postfix and dovecot IMAP. This is the second time we are facing the problem of inbox of some users are completely empty. Pls advice anyway to recover and to rectify the problem for such threat in future. Thanks, M.Navas Mob: +971 55 5973731

2 1

[Dovecot] How to stop POP clients from downloading mail after directory corruption
by Frank Church 15 Jul '07

15 Jul '07

Transferring my email from a Courier server, as well as some corruption in my dovecot installation caused all POP mails to be downloaded again. I surmised that the dovecot-uidlist file was not present in the first instance, and was probably out of sync in the second. Is there a way to do some reindexing and uid-list regeneration that can stop the problem from occurring? - Frank

2 1

[Dovecot] More Descriptive Logging Needed
by Joseph D. Wagner 15 Jul '07

15 Jul '07

(Everything herein refers to dovecot-1.0.1.) I'm sorry to say that I've been having troubles with dovecot. While attempting to troubleshoot them, I've found the existing logs to be lacking. In particular, I've had a lot of difficulty with the client<->server connection disconnecting, but the only message I get in the logs is "Disconnected". After dissecting the code a bit, I've found quite a number of places where the code will close the connection logging nothing more than the word "Disconnected", or worse, it will not specify a reason in which case the code in client_destroy() will log the default "Disconnected". Because of this, isolating the offending code has been a bit difficult. (I realize the problem may lie with the client, but I cannot even begin to program a work around until I isolate the exact place and cause of failure.) In an attempt to change the logging to be more descriptive myself, I already changed src/imap/cmd-fetch.c:85 on my own copy of dovecot from: client_disconnect(cmd->client, "Disconnected"); to: client_disconnect(cmd->client, "Disconnected in FETCH"); This makes the logging both more descriptive and more in line with other parts of code, like src/imap/cmd-append.c:50 which already say: client_destroy(client, "Disconnected in APPEND"); As luck would have it, my problem was not in the FETCH command. I'm now looking at the client_read() function in src/imap-login/client.c:318-334. If I'm reading the code right, then "i_stream_read(client->input)" returning "-1" means that the socket/stream is already disconnected, right? In other words, some function attempted to read off of a socket/stream that was already closed, right? If so, shouldn't the client_read() function not have been called in the first place? Please let me know if I'm wrong. I've been banging my head against the wall trying to make sense of all the different code. Any assistance you can offer would be appreciated. Joseph D. Wagner

2 1

[Dovecot] problem with subscriptions file version 1.0.1
by Liz 13 Jul '07

13 Jul '07

Hello, I am currently working on a patch to add IMAPdir support to dovecot. (For those who do not know, IMAPdir is exactly like Maildir except that instead of having a folder .foo it would just be foo. The advantage is that the file system is slightly easier to search through without the dot in front of the folders.) The first thing I did was get the configuration file working for Maildir. So I know that the problem has nothing to do with the configuration file. Next I looked through the actual source code to find any place where a dot might be added to the beginning of a folder. It transpired that there is a constant, MAILDIR_FS_SEP_S, which is assigned the value ".". I deleted all the occurrences of this constant, compiled the source code again, and ran into a rather interesting problem. When I try to create a new folder through Thunderbird on a separate machine, the folder is not visible unless I restart Thunderbird. I checked on the machine acting as a server and the folder is created and the subscriptions file is updated, and the dot at the beginning is indeed absent. So I see no reason why this should not work. If I had deleted some of the constants that ought not have been deleted, the subscriptions file would not be readable at all and I would not be able to see the folder when Thunderbird restarts. If there were some sort of deadlock going on with the subscriptions file, one would think that it would not be caused by deleting the constants. I would have run into the problem before editing any of the source code. I know for fact that the only thing different about my source code and the code available for downloading is the deleted constants. If anyone has any ideas, please let me know. If you need more information, please feel free to prompt me for it because I have no idea what might be useful that I have not already provided. Regards, Elizabeth Bermel

2 3

[Dovecot] telnet to dovecot not creating mbox
by Andy Fadich 13 Jul '07

13 Jul '07

Hi, Whenever I create a new email user, telnet fails until an email is sent to that user to create his mbox. This is the error that it gives. Anyone know how to fix this? I could create the email account script to touch the users mbox, but I havn't needed to do this in the past with ipop3d and dovecot on a different server. [root@mail log]# telnet localhost 110 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK Dovecot ready. user testact +OK pass +OK Logged in. -ERR Internal error occurred. Refer to server log for more information. [2007-07-13 10:37:15] Connection closed by foreign host. Jul 13 10:33:43 mail dovecot: pop3-login: Login: user=<testact>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured Jul 13 10:33:43 mail dovecot: POP3(testlol): open(/var/spool/mail/testact, O_CREAT) failed: Permission denied Jul 13 10:33:43 mail dovecot: POP3(testlol): access() failed with mbox file /var/spool/mail/testact: No such file or directory Jul 13 10:33:43 mail dovecot: POP3(testlol): stat() failed with mbox file /var/spool/mail/testact: No such file or directory Jul 13 10:33:43 mail dovecot: POP3(testlol): Couldn't init INBOX: Internal error occurred. Refer to server log for more information. [2007-07-13 10:33:43] Jul 13 10:33:43 mail dovecot: POP3(testlol): Mailbox init failed top=0/0, retr=0/0, del=0/0, size=0 Andy

3 2

[Dovecot] Today's hg pull doesn't compile
by Ralf Hildebrandt 13 Jul '07

13 Jul '07

I get: Making all in auth make[3]: Entering directory /usr/src/dovecot/src/auth' rm -f libpassword.a ar cru libpassword.a mycrypt.o password-scheme.o password-scheme-md5crypt.o password-scheme-otp.o password-scheme-rpa.o ranlib libpassword.a gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-sql -I../../src/lib-settings -I../../src/lib-ntlm -I../../src/lib-otp -DAUTH_MODULE_DIR=\""/usr/local/lib/dovecot/auth"\" -DPKG_LIBEXECDIR=\""/usr/local/libexec/dovecot"\" -std=gnu99 -fstack-protector -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT auth-request.o -MD -MP -MF .deps/auth-request.Tpo -c -o auth-request.o auth-request.c auth-request.c: In function ‘is_ip_in_network’: auth-request.c:874: error: ‘const union <anonymous>’ has no member named ‘ip6’ auth-request.c:875: error: ‘union <anonymous>’ has no member named ‘ip6’ make[3]: *** [auth-request.o] Error 1 make[3]: Leaving directory /usr/src/dovecot/src/auth' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory /usr/src/dovecot/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory /usr/src/dovecot' make: *** [all] Error 2 -- 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 Any technology sufficiently advanced is indistinguishable from magic.

2 2

[Dovecot] Maildir and Windows NFS server
by Julian Jimenez 13 Jul '07

13 Jul '07

Hi, I want to migrate form Courier to Dovecot. The problem is that our NFS server is a Windows server. We use Debian stable (Etch) and maildir. With Courier, we need to compile from the source, changing the parameter MDIRSEP from ":" to ";", because Windows cannot handle files with this character in their name. Anyone knows the name of the parameter in Dovecot that I need to change to do the same? Thanks in advance. Julián

2 1

[Dovecot] Dovecot login failing
by Richard Ellis 13 Jul '07

13 Jul '07

Fedora 7 Dovecot version 1.0.1 Hi All, I've been using a combination of getmail/Dovecot/Squirrelmail for a while now and its all been fine. However, last week when trying to demonstrate how to use Squirrelmail to my wife, her login failed. I then tried mine, which I had used many times before and it also fails. Looking in the logs, Dovecot appears to be trying to add a domain name against the login, instead of just checking that user against the UNIX logins of my machine. I thought at first this was because when I'm away from home, I use a no-ip address to access my mailserver, but it also fails when I'm in the house, or even on the server console. dovecot: Jul 12 12:04:56 Info: imap-login: Aborted login: user=< rick(a)servehttp.com>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff: 127.0.0.1, secured dovecot: Jul 12 12:10:00 Info: pop3-login: Login: user=<rick>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured Anybody any idea how to rectify this? I can't see an option in the /etc/dovecot.conf file to stop it and using auth_default_realm = doesn't seem to make any difference. If I telnet into dovecot using my local username and password, it works fine. Any advice would be most welcome before I break it fiddling. Thanks Rik -- The Truth is out there, does anyone have the URL?

5 5

[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 13 Jul '07

13 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

[Dovecot] 1.0.1: corrupt index on fresh mailbox, ideas?
by Troy Engel 12 Jul '07

12 Jul '07

A new employee started today, when logging into his new mailbox this morning during a walk-through I got a nasty server error response in Thunderbird - something I never see, DC runs smooth as butter for us. Checking the server log I see this: == snip == dovecot: Jul 09 09:38:54 Error: IMAP(xxxxxxx): Maildir /home/x/xxxxxxx/Maildir sync: UIDVALIDITY changed (1183406107 -> 1183999134) dovecot: Jul 09 09:39:06 Error: IMAP(xxxxxxx): Corrupted transaction log file /var/spool/dovecot/indexes/x/xxxxxxx/.INBOX/dovecot.index.log.2: invalid indexid (1183406107 != 1183999146) dovecot: Jul 09 09:39:06 Error: IMAP(xxxxxxx): Corrupted index cache file /var/spool/dovecot/indexes/x/xxxxxxx/.INBOX/dovecot.index.cache: indexid changed == snip == Some facts that make this a strange occurrence: 1) new IMAP mailbox, only one email was in it that I had sent last week (boilerplate Welcome email) 2) was working perfectly fine on Friday when I set things up (Thunderbird and SquirrelMail) and tested with the same client laptop and same Thunderbird 3) nothing bad happened with the servers over the weekend, all is tip-top - no restarts, reboots, nothing. 4) DC does use NFS mounted maildirs, but there is only one DC accessing any maildir - no other servers touch ~/Maildir/. mmap is disabled. What could be a reason for this index to have gotten corrupted? This is the first time I've had an index go corrupt out of all the users, so I'd like to try and track down the cause of this... thx, -te == dovecot -n == # 1.0.1: /etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imap imaps listen: * ssl_cert_file: /opt/SSL/server.pem ssl_key_file: /opt/SSL/server.pem login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_process_per_connection: no mail_location: maildir:~/Maildir:INDEX=/var/spool/dovecot/indexes/%1u/%u mmap_disable: yes namespace: type: private separator: . prefix: INBOX. inbox: yes auth default: cache_size: 4096 cache_ttl: 7200 passdb: driver: pam args: cache_key=%u dovecot userdb: driver: passwd args: blocking=yes == end == -- Troy Engel | Systems Engineer Fluid, Inc | http://www.fluid.com

5 12

[Dovecot] Fixing lda user_query error introduces new fault in mail delivery
by Frank Church 12 Jul '07

12 Jul '07

I was getting these errors below and after fixing it delivery errors were introduced dovecot/error_log ============== dovecot: Jul 11 06:19:28 Error: auth-worker(default): sql(user(a)domain.com): User query failed: Table 'postfix.users' doesn't exist deliver(user(a)domain.com): Jul 11 06:19:28 Error: BUG: Unexpected input from auth master: FAIL 1 dovecot: Jul 11 06:21:41 Error: auth-worker(default): sql(admin(a)achimota.com,127.0.0.1): User query failed: Table 'postfix.users' doesn't exist ============== It turns out that using prefetch with dovecot lda required a user_query in dovecot/sql.conf I fixed it by adding this query to dovecot/sql.conf user_query = SELECT concat('/var/vmail/', maildir) as home, 601 as uid, 12 as gid FROM mailbox WHERE username = '%u' AND active = '1' This resulted in a new mailbox /var/vmail/domain.com/user(a)domain.com being created when although /var/vmail/domain.com/user already exists and is what the query returns It seems that prior to that when the query was failing the mail was properly delivered somehow by dovecot, but fixing it created a new problem. It appears that the mail_location = maildir:/var/vmail/%d/%u in dovecot.conf could be related as %u is user(a)domain.com Is there a fix for this? Does the deliver line in postfix/master.cf need to be adjusted in some way I will probably have to disable the user_query and restart for the time being dovecot version - 1.0rc26 Here is dovecot.conf =============== ssl_cert_file = /etc/pki/dovecot/certs/abc.domain.net.crt ssl_key_file = /etc/pki/dovecot/private/abc.domain.net.key ssl_ca_file = /etc/pki/dovecot/certs/ca-bundle.crt mail_location = maildir:/var/vmail/%d/%u mail_extra_groups = mail first_valid_uid = 601 last_valid_uid = 601 maildir_copy_with_hardlinks = yes protocol imap { mail_plugins = quota imap_quota imap_client_workarounds = outlook-idle delay-newmail } protocol pop3 { mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { postmaster_address = postmaster(a)domain.net mail_plugins = quota log_path = /var/log/dovecot/deliver.log info_log_path = /var/log/dovecot/deliver.log } auth default { mechanisms = plain passdb sql { args = /etc/dovecot/sql.conf } userdb prefetch { } userdb sql { args = /etc/dovecot/sql.conf } user = nobody socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = vmail group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = mail } } } dict { } plugin { quota = maildir:storage=10240:messages=1000 acl = vfile:/etc/dovecot/acls trash = /etc/dovecot/trash.conf } dovecot/sql.conf ============== default_pass_scheme = PLAIN-MD5 driver = mysql connect = host=localhost dbname=postfix user=dovecot password=password password_query = SELECT username as user, password, concat('/var/vmail/', maildir) as userdb_home, concat('maildir:/var/vmail/', maildir) as userdb_mail, 601 as userdb_uid, 12 as userdb_gid, concat('dirsize:storage=', cast(quota as char)) AS userdb_quota FROM mailbox WHERE username = '%u' AND active = '1' user_query = SELECT concat('/var/vmail/', maildir) as home, 601 as uid, 12 as gid FROM mailbox WHERE username = '%u' AND active = '1' dovecot line in postfix/master.cf ======================= # Dovecot LDA dovecot unix - n n - - pipe flags=DRhu user=vmail:mail argv=/usr/local/libexec/dovecot/deliver -d ${recipient} - Frank

2 1

[Dovecot] Can Wiki entry on dovecot LDA/deliver be clarified?
by Frank Church 11 Jul '07

11 Jul '07

Hi guys, I am having some problems relating to this "Fixing lda user_query error introduces new fault in mail delivery" and I'd like to know if the above wiki comment holds even if a user_query is configured to return the correct mail folder. According to this LDA delivers only to the mail_location setting. Does that mean that it will stick to the value in dovecot.conf or will the value returned in the query override it? This appears to be the problem I am experiencing with the previous thread. >From wiki entry at wiki.dovecot.org/LDA ============================ Problems with deliver Currently deliver doesn't support namespaces. The mails can be delivered only to mailboxes specified by the mail_location setting. If you are using prefetch userdb, keep in mind that deliver does not make a password query and thus will not work if -d parameter is used. The UserDatabase/Prefetch page explains how to fix this. ================================== Any ideas? - Frank

1 1

[Dovecot] target doesn't allow inferior mailboxes
by Adam Williams 11 Jul '07

11 Jul '07

Using Seamonkey as my email client, and IMAP to check mail. If I create a new IMAP folder, and then delete it, I get the error: The current command did not succeed. The mail server responded: Target mailbox doesn't allow inferior mailboxes. Tried a google search, didn't really come up with anything. I have rw permissions on /home/awilliam/Mail/* and delete the files fine using rm -rf /home/awilliam/Mail/whatever and editing the folder out of .subscriptions. Any ideas? [root@roark ~]# dovecot --version 1.0.1 [root@roark ~]# dovecot -n # 1.0.1: /etc/dovecot.conf login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: mbox:~/Mail/:INBOX=/var/spool/mail/%u mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: passdb: driver: pam userdb: driver: passwd

3 3

[Dovecot] About a simultaneous session of Dovecot(IMAP)
by Takateru Ueda 11 Jul '07

11 Jul '07

The construction of the mail server with Postfix+Dovecot(IMAP) is examined. ・The number of mailboxes is about 1000. ・The reception protocol uses IMAP and the Maildir form. ・OS is Redhat Enterprise Linux ES4. ・MUA uses Outlook Express. ・Postfix and Dovecot use latest Ver. In the above-mentioned environment, it is understanding person. how much the number of maximum sessions (number of people) that can be used at the same time becomes from MUA (When grounds of the calculation are understood, it is the best. )

2 2

[Dovecot] Connecting to dovecot/imap without a password
by Don Russell 11 Jul '07

11 Jul '07

I have written a script that connects (localhost) to the dovecot/imap server and performs various maintenance on my mail, by folder..... deleting old stuff, keeping the n most recent, that sort of crap, er good stuff. :-) My script is written in php (I use the various imap_* functions), and it connects to the imap server running on the same machine... is there a way to connect to the server without having to specify my user name and password? I was thinking there may be some form of "implied" logon if a request from user "don" requests to log on to user "don", then there's no need for a password check, when the connection is via localhost. That way I don't have to deal with userid/password related issues. :-) Thanks

2 2

[Dovecot] postfix pipe to deliver, null_sender.
by Erland Nylend 11 Jul '07

11 Jul '07

Hello, I just noticed a problem on our servers .. If I send myself a bounce, like this: | [en@mailserver ~]$ telnet localhost 25 | Trying 127.0.0.1... | Connected to localhost.localdomain (127.0.0.1). | Escape character is '^]'. | 220 mailserver ESMTP Postfix | helo foo | 250 mailserver | mail from: <> | 250 2.1.0 Ok | rcpt to: my(a)mail.address.tld | 250 2.1.5 Ok | data | 354 End data with <CR><LF>.<CR><LF> | testing | . | 250 2.0.0 Ok: queued as 673072767C | quit | 221 2.0.0 Bye | Connection closed by foreign host. Then the resulting mail message I get, has this header: | Return-Path: <MAILER-DAEMON> | Delivered-To: my(a)mail.address.tld | Received: from foo (localhost.localdomain [127.0.0.1]) | by mailserver (Postfix) with SMTP id 673072767C | for <my(a)mail.address.tld>; Wed, 11 Jul 2007 13:36:07 +0200 (CEST) | Message-Id: <20070711113611.673072767C@mailserver> | Date: Wed, 11 Jul 2007 13:36:07 +0200 (CEST) | From: MAILER-DAEMON | To: undisclosed-recipients:; It seems that postfix changes the return-path, and I dont see why it would do something like that. The bounce is not a bounce anymore, and if a user fetches the mail with e.g. fetchmail, and it cannot be delivered, then the bounce will be bounced, to MAILER-DAEMON .. My master.cf entry looks like this: dovecot unix - n n - - pipe flags=DRhu user=atmail:atmail argv=/usr/local/dovecot/libexec/dovecot/deliver -d ${recipient} If I add null_sender= , then that resolves it: dovecot unix - n n - - pipe flags=DRhu user=atmail:atmail null_sender= argv=/usr/local/dovecot/libexec/dovecot/deliver -d ${recipient} What do other postfix/dovecot-users do? Will this change break anything? I cannot see why empty null_sender isn't default .. so I'm wondering if there is something I've missed. Should we update the examples on http://wiki.dovecot.org/LDA/Postfix to include empty null_sender? -- Erland Nylend

1 0

[Dovecot] [Patch] Samba's proposed "ntlm_auth + winbind" support for dovecot-auth
by Dmitry Butskoy 11 Jul '07

11 Jul '07

The Samba team recommends to use their "ntlm_auth" command line helper for "NTLM" and "GSS-SPNEGO" authentication. This helper interacts with the Samba's winbind daemon, and this way can authenticate users against NT or Active Directory windows domain. Currently Dovecot can do "NTLM" authentication too, but just "locally" (against a local or sql database etc.). I've made a patch (attached), which adds "ntlm_auth" (or "winbind") support for Dovecot. The idea is to add two new authentication mechanisms: "mech_winbind_ntlm" and "mech_winbind_spnego". Both are coded in one additional file, "mech-winbind.c". An option "auth_ntlm_use_winbind" specifies whether to use the current implementation of ntlm, or do it by the "ntlm_auth" helper. "GSS-SPNEGO" always performed by the helper. Normally, "ntlm_auth" is invoked once, for all further requests. Such a way, "ntlm_auth helper from the Samba package, interacting with the Samba's winbind daemon", is used now by Squid, Apache and AFAIK some other applications. It is "strongly recommended" by the Samba team, and was already proposed even in this maillist 3 year ago (see f.e. http://www.dovecot.org/list/dovecot/2004-September/004775.html ). I hope there are no any serious performance issues for such a "complex way" -- f.e. with our web proxy, using this way, ~200 users do not feel any actual delays etc. I've successfully tested this patch with NTLM against AD domain. This patch can considerably improve the situation of "Email client on Windows desktop under Windows domain, but imap/pop at UNIX server". Currently, windows users have to specify their "login/password" for email accounts manually. There is an "SPA" (Secure Password Authentication) alternative for them, where just the desktop's login is used transparently, but it cannot be used now, because Dovecot cannot perform NTLM against, say, Active Directory domain. Since "dovecot-auth" daemon can be utilized by MTA as well (Postfix and other), the support of "ntlm_auth" in Dovecot can satisfy both SMTP and IMAP servers at UNIX side, and solve the issue completely. Questions and requests: - I try to code things most close to used style, i.e. using Dovecot's memory-management and io-pipe routines etc., but could someone look at it and check whether I've missed something or not? - Perhaps some names (of routines, modules) could be chosen better? - Maybe some other options should be implemented, i.e. "auth_winbind_helper_ntlm" and "auth_winbind_helper_spnego" to specify the helper's cmdline exactly ? - Currently I strip domain part of the username returned, i.e. from "DOMAIN\user" just to "user". Maybe better add some option "auth_winbind_strip_domain" for this? Certainly, it will be fine if someone else check it more, especially for "GSS-SPNEGO" which I cannot test for a while. Regards, Dmitry Butskoy http://www.fedoraproject.org/wiki/DmitryButskoy

2 6

[Dovecot] NFS and Filesystem quota
by Joseba Torre 11 Jul '07

11 Jul '07

Hi, I've recently moved my mailboxes to a NFS share (on an emc Celerra), and, as expected, the quota extensions no longer works. However, I've read that adding http://dovecot.org/patches/quota-rquotad.c to $DOVECOT/src/plugins/quota, adding a line to $DOVECOT/src/plugins/quota/Makefile.am and rebuilding, it should work again. Unfortunately, it doesn't compile in my RHEL 4.0: /usr/bin/gcc4 -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib -I../../../src/lib-dict -I../../../src/lib-index -I../../../src/lib-mail -I../../../src/lib-storage -I../../../src/lib-storage/index -I../../../src/lib-storage/index/maildir -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -I/usr/kerberos/include -MT quota-rquotad.lo -MD -MP -MF .deps/quota-rquotad.Tpo -c quota-rquotad.c -fPIC -DPIC -o .libs/quota-rquotad.o quota-rquotad.c: In function 'debugmsg': quota-rquotad.c:50: warning: implicit declaration of function 'i_vinfo' quota-rquotad.c: In function 'rquotad_quota_add_storage': quota-rquotad.c:90: error: storage size of 'statbuf' isn't known quota-rquotad.c:97: warning: implicit declaration of function 'statfs' quota-rquotad.c:99: error: 'MNT_LOCAL' undeclared (first use in this function) quota-rquotad.c:99: error: (Each undeclared identifier is reported only once quota-rquotad.c:99: error: for each function it appears in.) quota-rquotad.c:104: error: 'MNAMELEN' undeclared (first use in this function) quota-rquotad.c:90: warning: unused variable 'statbuf' quota-rquotad.c: At top level: quota-rquotad.c:225: warning: initialization from incompatible pointer type quota-rquotad.c: In function 'rquota_get': quota-rquotad.c:256: warning: dereferencing type-punned pointer will break strict-aliasing rules quota-rquotad.c:267: warning: passing argument 3 of 'clnt->cl_ops->cl_call' from incompatible pointer type quota-rquotad.c:267: warning: passing argument 4 of 'clnt->cl_ops->cl_call' from incompatible pointer type quota-rquotad.c:267: warning: passing argument 5 of 'clnt->cl_ops->cl_call' from incompatible pointer type quota-rquotad.c:267: warning: passing argument 6 of 'clnt->cl_ops->cl_call' from incompatible pointer type quota-rquotad.c: In function 'rquotad_quota_root_update': quota-rquotad.c:275: error: storage size of 'statfsbuf' isn't known quota-rquotad.c:291: error: 'MNT_LOCAL' undeclared (first use in this function) quota-rquotad.c:275: warning: unused variable 'statfsbuf' make[4]: *** [quota-rquotad.lo] Error 1 make[4]: Leaving directory `/home/lgstosej/dovecot/dovecot-1.0.1/src/plugins/quota' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/lgstosej/dovecot/dovecot-1.0.1/src/plugins' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/lgstosej/dovecot/dovecot-1.0.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/lgstosej/dovecot/dovecot-1.0.1' make: *** [all] Error 2 Any help? Is there any plan to have official support for this? Aaaaaaaaaagur. -- Joseba Torre. CIDIR Bizkaia.

2 1

[Dovecot] Migrating subscription lists
by Stewart Dean 10 Jul '07

10 Jul '07

I thought this would be relatively straightforward....I would create .subscriptions by doing an ls -1 of ~/mail. I'm running into some problems. 1) the ~/mail directories haves directories in them for 5% of the accounts! AFAIK, our mail sevice has always been UWIMAP with mbox format INBOXes, and it was my understanding that the mbox format is flat and NOT hierarchical and thus I'd have thought that ~/mail would be all folders and wouldn't have a directory with folders in it. Plus our users are not, as a rule, power/geek user that would understand even making subdirs in ~mail, so I don't know how this would have come to pass. Should this be? Or am I misunderstanding things? 2) Some people are consciously or unconsciously using the UWIMAP .mailboxlist subscription file as it is meant to be used, namely to *restrict* the folders shown. If/when I generated the Dovecot .subsbcriptions file by just doing an ls -1 of their mail directory, they will be surprised to see stuff not previously displayed....that they may very well not know they'd had. Murphy must be a terribly overworked deity...you'd think he'd take a rest now and then from maximizing entropy -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

[Dovecot] mbox vs maildir
by Don Russell 10 Jul '07

10 Jul '07

I'm using Dovecot 1.0.1-12 on Linux/Fedora 7 along with sendmail and procmail all running on the same box mail is stored in mbox format It's a small system with a half dozen or so e-mail "accounts". Each with 40-60MB of messages in various folders. I keep seeing messages about how mbox is antiquated and anybody with more than 100 messages etc should not use mbox, but use maildir instead. I'm not entirely convinced.... there seem to be pros and cons for each. Is there a discussion somewhere that really highlights why one format is so much better than the other? The last time I tried to convert from mbox to maildir, things got pretty botched up, no data loss, but it wasn't pretty. :-) Can Dovecot handle mbox for some users and maildir for others? I'd like to try a conversion for one user... I'll probably create a new user, then have procmail copy (via ! action code) all mail for one user to that new user. Thank you

16 40

[Dovecot] secure pop for outside pop inside
by arjan 10 Jul '07

10 Jul '07

Hi all, I've a server with dovecot running in secure pop mode. For connections from the outside world, I don't want to enable pop. However, this machine is also the host for a vserver. In this vserver I have a webserver running the WebGUI Content Management System. One can add content via email. For this the cms has to be able to check a pop emailbox. The cms doesn't support secure pop. It's not nescessary either, because dovecot and cms are on the same machine. How can I configure Dovecot in such a way that I can enable pop just for one ip-adress and have secure pop for connections on another adress? Any help would be very much appreciated. Kind regards, Arjan

2 3

[Dovecot] Repeated references to non existent users table
by Frank Church 10 Jul '07

10 Jul '07

Dovecot keeps returning messages in the general log about a users table, where my users table is called mailbox, based on my postfixadmin configuration. dovecot: Jul 10 11:37:27 Info: auth-worker(default): sql(user(a)domain.com): SELECT home, uid, gid FROM users WHERE userid = 'user(a)domain.com' dovecot: Jul 10 11:37:27 Info: auth(default): prefetch(user(a)domain.com): passdb didn't return userdb entries I get errors stating that table postfix.users does not exist which is right because my table is named mailbox my dovecot-sql.conf files don't contain any references to a table named users. dovecot.conf ========= protocol lda { postmaster_address = postmaster(a)abc.meripol.net mail_plugins = quota log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log } main.cf ========== # ---------------------- SASL PART START ---------------------- smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = smtpd_sasl_exceptions_networks = smtpd_sasl_security_options = noanonymous broken_sasl_auth_clients = yes # ---------------------- SASL PART END ---------------------- master.cf ======= dovecot unix - n n - - pipe flags=DRhu user=vmail:mail argv=/usr/local/libexec/dovecot/deliver -d ${recipient}

1 0

[Dovecot] dovecot lda with fetchmail
by JC Júnior 10 Jul '07

10 Jul '07

hi all, I'm new in dovecot, and i need to setup a machine that download emails from an external pop3 server, and delivers to my internal network via imap, for this , i want ( if possible ) to use fetchmail with the option mda to dovecot's deliver, because all user must be virtual users stored in a sqlite database, and my question is: 1- it is possible?? 2- theres a better way to do this?? 3- someone knows some howto about this configuration??? thanks for all JC Júnior

3 6

[Dovecot] Upgrade from 1.00 to 1.0.1
by Jon 09 Jul '07

09 Jul '07

Hi, I'm getting a bunch of errors since I upgraded to 1.0.0. I understand now that some of them are bug related to release 1.0.0. I'm about to upgrade to 1.0.1. Does anyone know if there are changes in the config file btwn these to versions? Also, what is the best way to do the upgrade? Can I just run ./configure : make : make install : killlall -HUP dovetcot? Best Regards - Jon

7 9

[Dovecot] Tbird-DC state problem
by Stewart Dean 09 Jul '07

09 Jul '07

A experienced sysadmin who's doing some guinea-pig use of DC just ran into the following situation: 1) He brings up SeaMonkey 2) About 30 minutes later, he's in the middle of some involved messaging, mistakenly hits the redX in the top right of the SeaMonkey window, knocking himself out of SeaMonkey. 3) He immediately reinvokes SeaMonkey, all appeared to be OK Viewed some e-mail and some web page references, tries to send a message and then the Send hung for a time with a message "Sending Authenticate Info"..after some minutes, a new E-mail window appeared stating the "Server reported a timeout". As far as the message, it was apparently sent successfully, and saved in the Sent folder successfully. 4) He calls me in. I look through the syslog logging. There is nothing in the syslog critical stuff...and everything in the maillog looks normal. 5) He starts another message, tries to save it to Drafts and that hangs 6) I look more closely at the maillog and see a lot of logins (one a minute in some cases, but all appear to have been cleanly executed) plus one bunch of disconnected messages with one disconnected in idle in the period when the write to the Drafts would have been hung. Could it be that DC was in the middle of clean up in the initial disconnect/reconnect and SeaMonkey came back in the middle of it and one or the other's state tables got messed up (or both of them)? Shutting out of SeaMonkey, waiting a minute and reconnecting seems to have gotten things working again. Any comments? Anything I should be looking for? OTOH, this is the first real problem I've seen in some person-months of testing..... -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

1 0

[Dovecot] PHP implementation of dovecotpw passwords
by Frank Church 09 Jul '07

09 Jul '07

I am looking for PHP functions that implement passwords that much the dovecotpw implementation. I downloaded one from PEAR, Crypt_HMAC, but the passwords it generates look nothing like the dovecotpw passwords, which could be my fault because I know nothing about the field. Is there a guide or some library that implements them to match dovecotpw?

4 4

[Dovecot] Your IMAP server has closed the connection.
by Dehnert James Sr 09 Jul '07

09 Jul '07

I'm getting a large number of ... "Your IMAP server has closed the connection. This may occur if you have left the connection idle for too long." errors. These are confusing my clients. Is there a way to set the timeout on the dovecot server to help avoid this?

4 6

[Dovecot] Unable to send email out using Dovecot SASL
by dovecot＠convergenz.biz 06 Jul '07

06 Jul '07

Hi, I am currently using Dovecot 1.0.rc17 with Postfix 2.3.8 on Ubuntu. So far I'm able to receive my email using dovecot pop3 but I can't send out the email. Anybody managed to get Postfix with Dovecot SASL support so far? What do I missed out? Below is my configure: #-----------/dovecot.conf-------------- base_dir: /var/run/dovecot/ log_timestamp: .%Y-%m-%d %H:%M:%S . protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/ssl/mail-cert.pem ssl_key_file: /etc/ssl/mail-key.pem 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 first_valid_uid: 150 last_valid_uid: 150 mail_extra_groups: mail mail_location: maildir:/var/vmail/%d/%u maildir_copy_with_hardlinks: 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 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: user: nobody verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: mail #-----------/dovecot.conf end-------------- #-----------/dovecot-sql.conf-------------- driver = mysql connect = host=localhost dbname=postfix user=postfix password=Password default_pass_scheme = MD5-CRYPT user_query = SELECT '/var/vmail/%d/%n' as home, 'maildir:/var/vmail/%d/%n' as mail, 150 AS uid, 8 AS gid, concat('dirsize:storage=', quota) AS quota FROM mailbox WHERE username = '%u' AND active = '1' password_query = SELECT username as user, password, '/var/vmail/%d/%n' as userdb_home, 'maildir:/var/vmail/%d/%n' as userdb_mail, 150 as userdb_uid, 8 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' #-----------/dovecot-sql.conf end-------------- Rgds CH

4 3

[Dovecot] utime : operation not permitted
by Jim Horner 06 Jul '07

06 Jul '07

With the upgrade to 1.0.1, I am seeing some errors/warnings dovecot: IMAP(jhorner(a)arinbe.com): utime(/home/arinbe/Maildir/.info/tmp) failed: Operation not permitted: 1 Time(s) dovecot: IMAP(jhorner(a)arinbe.com): utime(/home/arinbe/Maildir/.resumes.vabch/tmp) failed: Operation not permitted: 1 Time(s) Different directories on different days. Different users on different days. Always /tmp directory. Always a /tmp of a shared namespace. The /tmp directory in question is mode 770, with group users, just like the rest of the /arinbe/Maildir hierarchy. As far as I can tell it doesn't affect anything on the client side. dovecot -n ssl_cert_file: /etc/ssl/arinbe/arinbe-godaddy.crt ssl_key_file: /etc/ssl/arinbe/arinbe.key ssl_cipher_list: ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:!LOW:!SSLv2:+EXP:@STRENGTH login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting: I am the IMAP Whisperer and I am ready. mail_location: maildir:%h/Maildir umask: 7 mail_plugins: acl imap_client_workarounds: delay-newmail outlook-idle namespace: type: public separator: . prefix: COMPANY. location: maildir:/home/arinbe/Maildir:CONTROL=%h/shared-settings/company/control:INDEX=%h/shared-settings/company/index namespace: type: public separator: . prefix: ROOTMAIL. location: maildir:/home/rootmail/Maildir:CONTROL=%h/shared-settings/rootmail/control:INDEX=%h/shared-settings/rootmail/index namespace: type: private separator: . prefix: INBOX. inbox: yes auth default: mechanisms: plain login default_realm: arinbe.com user: nobody passdb: driver: ldap args: /etc/dovecot/dovecot-ldap-arinbe.conf passdb: driver: ldap args: /etc/dovecot/dovecot-ldap-domains.conf userdb: driver: prefetch userdb: driver: ldap args: /etc/dovecot/dovecot-ldap-arinbe.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap-domains.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 438 user: postfix group: postfix master: path: /usr/local/var/run/dovecot/auth-master mode: 432 user: nobody group: mail plugin: acl: vfile:/etc/dovecot/dovecot-acls

2 9

[Dovecot] Debian packages for Dovecot 1.0.1xx (sarge)
by Moritz Mertinkat 06 Jul '07

06 Jul '07

Hi there, i'm looking for Debian sarge dovecot packages (yes, still running sarge). Anyone here that has a backported package? Greetings, Moritz

2 1

[Dovecot] modules/imap/lib02_imap_quota_plugin.so: undefined symbol: quota_set
by Philipp Kolmann 06 Jul '07

06 Jul '07

Hi, I wanted to enable FS quota support in dovecot, and have configured the following directives: protocol imap { mail_plugins = imap_quota } plugin { quota = fs } With this additional settings, my normally working dovecot.conf doesn't start anymore: Starting mail server: dovecotEdlopen(/usr/lib/dovecot/modules/imap/lib02_imap_quota_plugin.so) failed: /usr/lib/dovecot/modules/imap/lib02_imap_quota_plugin.so: undefined symbol: quota_set Error: imap dump-capability process returned 89 I have tested this issue on the following versions: * Debian etch: 1.0.rc15 * RedHat AS 5: 1.0.rc15 * Debian sid: 1.0.0 Thanks for any help in this issue. Philipp Kolmann -- If you have problems in Windows: REBOOT If you have problems in Linux: BE ROOT

3 3

[Dovecot] assertion failed & invalid password field
by Ralf Hildebrandt 06 Jul '07

06 Jul '07

I'm getting these in my log: Jul 6 09:52:51 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 6 09:52:51 postamt dovecot: child 31576 (login) killed with signal 6 Jul 6 10:37:44 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 6 10:37:44 postamt dovecot: child 25241 (login) killed with signal 6 Jul 6 13:14:51 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 6 13:14:51 postamt dovecot: child 4418 (login) killed with signal 6 and I get those for accounts I deactivated using "usermod -L", maybe dovecot should log something like "account disabled" instead: Jul 6 11:07:01 postamt dovecot: auth(default): shadow(vnedwed,77.128.63.72): invalid password field Jul 6 11:07:06 postamt dovecot: auth(default): shadow(vnedwed,77.128.63.72): invalid password field Jul 6 14:12:40 postamt dovecot: auth(default): shadow(jechafch,141.42.4.251): invalid password field This is dovecot-1.0.1 -- 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 Your eyes are weary from staring at the CRT. You feel sleepy. Notice how restful it is to watch the cursor blink. Close your eyes. The opinions stated above are yours. You cannot imagine why you ever felt otherwise.

1 0

[Dovecot] Virtual servers
by John Hedges 06 Jul '07

06 Jul '07

Hello I'm migrating from Courier to Dovecot (1.0.rc15) on Debian. I am trying to set up virtual servers based on the principal in this thread: http://www.dovecot.org/list/dovecot/2006-October/017165.html which suggests something like this to support multiple certificates: server foo { listen = 1.2.3.4 ssl_cert_file = /etc/ssl/certs/foo.cer } server bar { listen = 1.2.3.5 ssl_cert_file = /etc/ssl/certs/bar.cer } My virtual configs look like this: server mail.domain1.org { listen = 1.2.3.4 protocols = pop3 pop3s imap imaps ssl_cert_file = /etc/mail/hosts/domain1.org/ssl.crt ssl_key_file = /etc/mail/hosts/domain1.org/ssl.key auth default { mechanisms = plain passdb passwd-file { args = /etc/mail/hosts/domain1.org/userdb } userdb passwd-file { args = /etc/mail/hosts/domain1.org/userdb } } } server mail.domain2.org { listen = 1.2.3.5 protocols = imap imaps ssl_cert_file = /etc/mail/hosts/domain2.org/ssl.crt ssl_key_file = /etc/mail/hosts/domain2.org/ssl.key auth default { mechanisms = plain passdb passwd-file { args = /etc/mail/hosts/domain2.org/userdb } userdb passwd-file { args = /etc/mail/hosts/domain2.org/userdb } } } but I can't get ithis to work. Dovecot starts but authorisation fails. Is this kind of setup possible - is it possible to configure different passwd-files for connections on different IPs, or am I going to have to run separate instances of Dovecot for each virtual host? Thanks John

2 1

[Dovecot] Dovecot with iPhone
by Erik Dasque 05 Jul '07

05 Jul '07

Hi, anyone using their Dovecot server with an iPhone ? While the iPhone is able to see the Inbox, I can't get it to see the other folder. I have tried ~/Maildir, /home/ed/Maildir and Maildir as the IMAP prefix but to no avail. Anything I am overlooking ? Erik

3 4

[Dovecot] Index question
by Stewart Dean 05 Jul '07

05 Jul '07

The day I switch our user to dovecot and it goes into production, there will be a few thousand people all generating their indices for the first time (we have a legacy requirement for procmail, at least for now), so I wondered: 1) Is there is anyway to pre-emptively force indexing? 2) Is there any value in doing so? That is, will I gain much in terms of making the first time everyone connects to dovecot quicker (not that big initial wait)? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

7 8

Re: [Dovecot] Permission errors when creating/reading files in users' mail directories
by Bryan K. Wright 05 Jul '07

05 Jul '07

tss(a)iki.fi said: >> Jul 5 09:25:49 imap dovecot: IMAP(uid): open() failed with mbox file >> /var/spool/mail/uid: Permission denied > Sounds like your userdb is returning wrong uid. Set mail_debug=yes to see what > Dovecot is really using. Excellent! After looking at the uids, I found that my test user had both an entry in our ldap database and the local /etc/passwd file. Removing the spurious /etc/passwd entry (and fixing the local file ownerships) gets rid of the permission problems. Thanks for your help. Bryan -- ======================================================================== Bryan Wright |"If you take cranberries and stew them like Physics Department | applesauce, they taste much more like prunes University of Virginia | than rhubarb does." -- Groucho Charlottesville, VA 22901| (434) 924-7218 | bryan(a)virginia.edu ========================================================================

1 0

[Dovecot] Mark E-Mail as read
by Jens M. 05 Jul '07

05 Jul '07

Hi all, is there a way to configure Dovecot, so that it marks my e-mails as read, when I recieve them with pop3, but leave them on the server? Regards, Jens

4 4

[Dovecot] Permission errors when creating/reading files in users' mail directories
by Bryan Wright 05 Jul '07

05 Jul '07

Hi folks, I'm trying to migrate an old uw-imap server to dovecot, and running into puzzling (to me) permission problems. I've configured mail_location as follows: mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u and each user's mail directory has permissions like this: drwx------ 2 uid gid 4096 Jul 5 09:26 /home/uid/mail But when I try to check a user's mail using an imap client, I see the following error: Jul 5 09:59:49 imap dovecot: IMAP(uid): mkdir_parents(/home/uid/mail/.imap/ INBOX) failed: Permission denied If I open up the permissions so anyone can write, I find that the .imap directory is successfully created, and owned by "uid". Is dovecot initially creating the directory with some other ownership, and then changing the ownership to "uid"? I can get around this problem by setting INDEX in mail_location, and pointing it to a directory with more open permissions, but then I run into the next problem: Jul 5 09:25:49 imap dovecot: IMAP(uid): open() failed with mbox file /var/spool/mail/uid: Permission denied In this case, the permissions are set as follows: -rw------- 1 bkw1a mail 1267 Jul 5 08:47 /var/spool/mail/uid How should the permissions be set on the spool files? Thanks in advance, Bryan -- ======================================================================== Bryan Wright |"If you take cranberries and stew them like Physics Department | applesauce, they taste much more like prunes University of Virginia | than rhubarb does." -- Groucho Charlottesville, VA 22901| (434) 924-7218 | bryan(a)virginia.edu ========================================================================

2 1

[Dovecot] dovecot.conf pop3_uidl_format
by Peter Eriksson 05 Jul '07

05 Jul '07

From the Dovecot 1.0.1 sample dovecot.conf file: # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu ... # Note that Outlook 2003 seems to have problems with %v.%u format which was # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. # # NOTE: Nowadays this is required to be set explicitly, since the old # default was bad but it couldn't be changed without breaking existing # installations. %08Xu%08Xv will be the new default, so use it for new # installations. # pop3_uidl_format = %08Xu%08Xv Notice the *very* small difference in the format between UW's ipop3d and the ones mentioned a little bit below? I think I just got bitten by this (we moved from UW's ipop3d to Dovecot). Loooots of users just got a lot of new (old) mail again ("Leave mail on server" is a popular setting). Ah well. They really should move to IMAP anyway and now they got some summer reading to do :-) Is the difference intentional? If so then perhaps this should be more clearly pointed out! - Peter

2 2

[Dovecot] dotlock O_EXCL query
by derek kit hoong foo 05 Jul '07

05 Jul '07

Hi there, I was wondering if someone can assist with clarifying why O_EXCL does not always work with NFS. Is it related to NFS protocol version support or export permissions mode out of the Celerra/Netapp ( e.g: mixed mode, unix file permissions ? ) Please advise. Thanks. Regards, new dovecot user.

2 1

[Dovecot] MailMan option
by Sergey A. Kobzar 05 Jul '07

05 Jul '07

Hi guys, Is it possible receive my own posts to the list? I have configured such option "Receive your own posts to the list? - Yes" on Mailman page but it still does not work. Any ideas? -- Sergey

2 2

[Dovecot] problem with quota
by juan carlos 04 Jul '07

04 Jul '07

hi everyone I have dovecot 1.0.rc15-2, postfix 2.3.8 and virtual users and domains installed in debian sarge, the users quota are not working. I have applied the pacth VDA and didn't work, if a I sent a mail to another user which exceeds his quota this user can receive the mail without problem, this said to me that the quota doesn't work. I use maildir in mi configuration. Please help me with this problem.

3 2

[Dovecot] PAM timed out, kill failed, auth SEGV
by Thomas Arnett 04 Jul '07

04 Jul '07

My log is full of blocks like this: auth(default): pam(?): PAM child process 13576 timed out, killing it auth(default): PAM: kill(13576) failed: No such process Often, this is recorded for several pids at once. Occasionally, there's a single burst when a virtual user logs in, immediately before pam_authenticate() fails and checkpassword is executed. When this happens, pam() contains the username and remote IP. Usually, it starts 2 minutes after a login attempt (successful or not) and repeats every 10 seconds indefinitely. pam() contains something else: ~87% ? ~ 9% [garbage],master ~ 4% ?,master < 1% [empty] [garbage] varies; it seems to be constant for an instance of auth, but I haven't verified this. Eventually, auth segfaults: Core was generated by `dovecot-auth'. Program terminated with signal 11, Segmentation fault. ... #0 0x08087a68 in str_sanitize_append (dest=0x80a8950, src=0x3d9 <Address 0x3d9 out of bounds>, max_len=64) at str-sanitize.c:11 p = 0x3d9 <Address 0x3d9 out of bounds> #1 0x08057a1d in get_log_str (auth_request=0x80c6a00, subsystem=0x808f7cd "pam", format=0x808f9ac "PAM child process %s timed out, killing it", va=0x597f8c5c ":\211\n\b?|\t\b?|\t\b?\214\177Y") at auth-request.c:1121 ip = 0xa <Address 0xa out of bounds> str = (string_t *) 0x80a8950 #2 0x08057c62 in auth_request_log_error (auth_request=0x80c6a00, subsystem=0x808f7cd "pam", format=0x808f9ac "PAM child process %s timed out, killing it") at auth-request.c:1177 va = 0x597f8c5c ":\211\n\b?|\t\b?|\t\b?\214\177Y" #3 0x080658ee in pam_child_timeout (context=0x0) at passdb-pam.c:537 request = (struct pam_auth_request *) 0x80c6de8 iter = (struct hash_iterate_context *) 0x80bcdb0 key = (void *) 0xa9e value = (void *) 0x80c6de8 timeout = 1182548633 #4 0x08079fc5 in io_loop_handle_timeouts (ioloop=0x80b09b0, update_run_now=true) at ioloop.c:294 t = (struct timeout *) 0x80b4ca8 called_timeouts = (struct timeout *) 0x80b4ca8 tv = {tv_sec = 0, tv_usec = 0} t_id = 2 #5 0x0807b32e in io_loop_handler_run (ioloop=0x80b09b0) at ioloop- epoll.c:175 ctx = (struct ioloop_handler_context *) 0x80b09d8 events = (struct epoll_event *) 0x80b0a18 event = (const struct epoll_event *) 0x80b0a18 list = (struct io_list *) 0x80c42d8 io = (struct io *) 0x0 tv = {tv_sec = 1, tv_usec = 180418} events_count = 12 t_id = 2 msecs = 1181 ret = 0 i = 1 j = 3 call = true #6 0x0807a0a8 in io_loop_run (ioloop=0x80b09b0) at ioloop.c:329 No locals. #7 0x0805d7ee in main (argc=1, argv=0x597f8ec4) at main.c:321 foreground = false My config (Gentoo Linux hardened/x86/2.6): # 1.0.1: /etc/dovecot/dovecot.conf listen: [::1] ssl_listen: [::] ssl_cert_file: /etc/ssl/misfeature.net/crt ssl_key_file: /etc/ssl/misfeature.net/key ssl_cipher_list: HIGH login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_greeting_capability: yes verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 100 mail_location: maildir:~/mail mail_debug: yes maildir_copy_with_hardlinks: yes mail_drop_priv_before_exec: yes imap_client_workarounds: delay-newmail outlook-idle auth default: verbose: yes debug: yes passdb: driver: pam args: * passdb: driver: checkpassword args: /usr/local/bin/checkpassword userdb: driver: passwd userdb: driver: prefetch socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix I turned on the various logging options while investigating this problem; the messages appear even without. -- TA

2 1

[Dovecot] Maildir configuration vs ZFS and snapshots...
by Peter Eriksson 04 Jul '07

04 Jul '07

I have a little tricky issue around here. First some background: Every user is assigned their own ZFS filesystem, and it's mounted as /home/USER with a Maildir inside it. The there is a filesystem snapshot (read-only) taken automatically every day by the system. The idea is to allow users easy access to backup copies of their mail so that they can restore things themself.. For example this structure (somewhat abbreviated, some files/dirs removed): /home/testson/ .zfs/ snapshot/ 2007-06-18/ Maildir/ cur/ new/ tmp/ .Trash/ cur/ new/ tmp/ Maildir/ cur/ new/ tmp/ .Trash/ cur/ new/ tmp/ Now,I can access the normal Maildir INBOX and folders nicely via Dovecot/IMAP. The thing is I'd like to be able to access the snapshot too via Dovecot/IMAP somehow. My first idea was to use Dovecots namespace feature like this in the config file: namespace private { separator = / prefix = snapshot/ location = maildir:~/.zfs/snapshot/2007-06-18/Maildir:CONTROL=~/.dovecot/control:INDEX=~/.dovecot/index } This works great for the mail folders inside the Maildir - but not for the INBOX which isn't displayed at all... (Ie, under the "snapshot" prefix I only see "Trash" etc when looking at the folder from an IMAP client). I think that I'd need to use the "INBOX=" option for Dovecot to see the top-level "new/cur/tmp" directories in the snapshot folder, but you can only have one INBOX if I'm not mistaken? Any suggestions on how best to configure this? - Peter

3 6

[Dovecot] multiple userdb/passdb
by Thomas Balsfulland 04 Jul '07

04 Jul '07

hi all, i am using debian etch with dovecot imap (version 1.0.rc15-2) and mysql-database for the virtual mailuser. all informations (username, password, mailbox format, mailbox location, quota) are find in the sql. the maildir are locates at /home/vmail/, every is working fine. now i want to use imap for the system user as well - at the moment they cant user imap because they are not find in the sql db. so i set a second userdb/passwd in the dovecot.conf for the local system-user. now the config says: auth default { passdb passwd-file { args = /etc/dovecot/localuser } passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb passwd-file { args = /etc/dovecot/localuser } userdb sql { args = /etc/dovecot/dovecot-sql.conf } } and /etc/dovecot/localuser looks: localuser1:password:1000:1000::/home/localuser1::userdb_mail=mbox:~/Mail:INBOX=~/Mail/incoming now the local user is able to authenticate, but cant acces his mailboxes the logfile says: host dovecot: imap-login: Login: user=<localuser1>,method=PLAIN, rip=195.xxx.xxx.xxx, lip=193.yyy.yyy.yyy, TLS host dovecot: IMAP(tbals): lstat(/home/vmail//localuser1/cur) failed: Permission denied host dovecot: IMAP(tbals): lstat(/home/vmail/shared) failed: Permission denied it seems dovevot ignore the settings in /etc/dovecot/localuser. could someone help? regards thomas -- thomas balsfulland tbals(a)ctrl-c.de zwischen mut und dummheit liegt nur ein grat der sich durch das vorbereitetsein unterscheidet

1 0

[Dovecot] OT - Claws Mail on Mac OS X
by Gerard 04 Jul '07

04 Jul '07

Someone on this list recently asked regarding the availability of Claws Mail on Mac OS X architecture, A BETA release has just been issued. http://damien.krotkine.com/claws/ -- Gerard

1 0

[Dovecot] convert plugin: endless conversion and duplicate messages
by Andrew Ziem 03 Jul '07

03 Jul '07

Hi, When an mbox has a filename with a period, the Dovecot 1.0.1 convert plugin will endlessly convert the same mbox causing duplicate messages. To reproduce, create try converting two mboxes: one with a valid name and another with an invalid name. Then, repeat the login procedure a few times. Dovecot should do something more graceful such as replacing periods with another character. Here's /var/log/mail/errors Jul 2 08:29:44 aslan dovecot: IMAP(crystalp): Mailbox conversion: Couldn't create mailbox Print Shop Misc.: Invalid mailbox name Jul 2 08:39:46 aslan dovecot: IMAP(crystalp): Mailbox conversion: Couldn't create mailbox Print Shop Misc.: Invalid mailbox name Jul 2 08:48:54 aslan dovecot: IMAP(crystalp): Mailbox conversion: Couldn't create mailbox Print Shop Misc.: Invalid mailbox name Jul 2 08:48:58 aslan dovecot: IMAP(crystalp): Mailbox conversion: Couldn't create mailbox Print Shop Misc.: Invalid mailbox name Jul 2 08:49:39 aslan dovecot: IMAP(crystalp): Mailbox conversion: Couldn't create mailbox Print Shop Misc.: Invalid mailbox name Jul 2 08:59:40 aslan dovecot: IMAP(crystalp): Mailbox conversion: Couldn't create mailbox Print Shop Misc.: Invalid mailbox name Jul 2 09:09:40 aslan dovecot: IMAP(crystalp): Mailbox conversion: Couldn't create mailbox Print Shop Misc.: Invalid mailbox name Jul 2 09:20:23 aslan dovecot: IMAP(crystalp): Mailbox conversion: Couldn't create mailbox Print Shop Misc.: Invalid mailbox name I didn't test other non-{alphanumeric,whitespace} characters. Other than this and my previous e-mails, our conversion from UW-IMAP mboxes went nicely. I notice the performance difference, and our users will be happy to finally have proper subfolders. Andrew

1 0

[Dovecot] listen parm questions
by Stewart Dean 03 Jul '07

03 Jul '07

Q1: My imap server has 4 interfaces, but only one is used for imap traffic. Can I do this: listen = 10.20.30.40:10143 (when imap.mycollege.edu is 10.20.30.40) Or is there even any benefit to doing this? Q2: Can I specify more than one port....during test eval, I've had the IT dept using port 1043 for listen....which I will, of course, change to 143 when DC goes production. So my department isn't cut off by that switchover, can I do this? listen = *:10143,143 or this listen = 10.20.30.40:10143,143 I did look at the wiki but didn't see anything -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

3 2

[Dovecot] [Fwd: Bounce action notification]
by Timo Sirainen 03 Jul '07

03 Jul '07

Anyone have ideas why this happened? Nothing special in logs, all tss(a)iki.fi deliveries went OK. Mailman's bounce log is unhelpful. Why does it say it tried to deliver to dovecot(a)dovecot.org and when it failed it disabled my account? Why doesn't it even bother saying which remote host gave an error? Grepping mail.log for 'This user' shows nothing.

5 7

[Dovecot] dovecot + winbind problem
by Gregorics Tamás 03 Jul '07

03 Jul '07

Hi! I'm having some problem with our setup. I have a linux server authenticating from a win2k3 domain controller via winbind and pam. When i try to log in I receive the following error messages: Jul 3 10:26:10 zeusz pam_winbind[20375]: user 'tamas' granted access Jul 3 10:26:10 zeusz pam_winbind[20375]: user 'tamas' OK Jul 3 10:26:10 zeusz pam_winbind[20375]: user 'tamas' granted access Jul 3 10:26:10 zeusz dovecot: auth(default): userdb(tamas,127.0.0.1): user not found from userdb Jul 3 10:26:10 zeusz dovecot: imap-login: Internal login failure: user=<tamas>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured But when i try other services which also use winbind via pam (like popa3d) i can log in without any problem. Any ideas?

2 4

[Dovecot] NameSpases
by Sergey A. Kobzar 03 Jul '07

03 Jul '07

Hi guys, I have a problem with namespases in Dovecot: namespace public { separator = / prefix = Public/ location = maildir:/home/mail/public } namespace private { separator = / prefix = inbox = yes } namespace private works well, but I can't subscribe to namespace Public in Outlooks Express, The Bat! and Mozilla Thunderbird. Outlook shows error 'Mailbox doesn't exist: Public'. Same with The Bat!. maildir:/home/mail/public exists and has correct rights: # ls -alh /home/mail/public/ total 0 drwx------ 5 mail mail 184 Jul 2 21:55 . drwxr-x--- 4 mail root 104 Jul 2 21:01 .. drwx------ 2 mail mail 48 Jul 2 21:01 cur -rw-r--r-- 1 mail mail 0 Jul 2 21:54 dovecot-shared drwx------ 2 mail mail 48 Jul 2 21:01 new -rw-r--r-- 1 mail mail 0 Jul 2 21:55 subscriptions drwx------ 2 mail mail 48 Jul 2 21:01 tmp # dovecot --version 1.0.1 # uname -rsm Linux 2.6.20-gentoo-r8 i686 Any help appreciated :) -- Sergey

2 2

[Dovecot] Leaky dovecot-auth ?
by Christian Balzer 03 Jul '07

03 Jul '07

Hello, as mentioned before, we are migrating our mailboxes from a 0.99 cluster to a 1.0.0 one. With 0.99 dovecot-auth (with LDAP as backend) was leaking quite happily and the dovecot-auth processes frequently did hit their size limit and thus were killed and restarted. Which in 0.99 at least lead to authentication failures on a busy server, as the dovecot master process just killed off the auth process w/o disabling new connections to it first and letting any current authentications finish. The activity per cluster node on the 0.99 boxes was about 700k logins (mostly pop3) per day and 5 dovecot-auth processes with a 64MB limit each. The migrated users so far are of the less active kind and on one node of the 1.0.0 cluster we see about 70k logins/day and currently the dovecot-auth process there is hovering at 123/84MB (VIRT/RES in top). It was at 121/82MB when I checked 4 hours ago and no new users have been added to that node for 2 days. Authentication backend is still LDAP, no caching, 256MB process size limit. There are just 16k users on that node at this point in time, with only 1200 distinct users generating those 70k logins/day. We will start migrating the rest of the users tomorrow and now I'm wondering: 1. How and why would the memory footprint of dovecot-auth grow when there is no change in the amount of users in the DB? 2. What will happen when the single dovecot-auth process reaches 256MB in the end? Internal housekeeping attempts of that process? A whack to the head from the master process like in 0.99 and thus more erroneous authentication failures, potentially aggravated by the fact that there is just single dovecot-auth process? I guess at the current rate of leakage we shall know the answers to #2 soon one way or another. ;) Regards, Christan -- Christian Balzer Network/Systems Engineer NOC chibi(a)gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/

3 15

[Dovecot] Semi-static userdb...?
by John Robinson 03 Jul '07

03 Jul '07

I'm trying to add "virtual" mailboxes to a system. Real users with different uids own domains. Each domain has a passwd-file passdb. I don't want to use this passwd-file for the userdb, because I want to fix the home, mail and uid/gid settings. Can I use the static userdb in a less static manner, e.g. userdb static { args = uid=%{owner of /vmail/%d} gid=%{gid of /vmail/%d} home=/vmail/%d/users/%u mail=mbox:/vmail/%d/users/%u/mail:INBOX=/vmail/%d/users/%u/INBOX } Or is it just a bad idea to let relatively untrusted domain owners manage their own passwd-file at all...? Cheers, John.

2 4

[Dovecot] userdb nss
by Timo Sirainen 03 Jul '07

03 Jul '07

I remembered people complaining how glibc ignores NSS errors with getpwent(), so I thought I'd see how easy it is to use NSS directly. Unless I misunderstood something, this should work: http://hg.dovecot.org/dovecot/rev/c9b49ed99d28 Tested only with "files" backend. Also it won't work with Solaris, it seems to have completely different NSS modules. Don't know about BSDs. Can someone test how it handles LDAP/NIS failures (or if it even works with them)?

1 0

[Dovecot] Force rebuild v1.0.1
by Bruce Bodger 02 Jul '07

02 Jul '07

Haven't seen a thread discussing forcing rebuilding of indexes / cache, so the question is, if these files in a users home directory were deleted... -rw------- 1 bb admin 80 May 17 15:05 dovecot-keywords -rw------- 1 bb admin 85449 Jul 2 06:15 dovecot-uidlist -rw------- 1 bb admin 6832 Jul 2 06:15 dovecot.index -rw------- 1 bb admin 752640 Jul 2 06:19 dovecot.index.cache -rw------- 1 bb admin 95416 Jul 2 06:20 dovecot.index.log -rw------- 1 bb admin 131104 Jun 27 21:32 dovecot.index.log.2 ...would they be rebuilt by dovecot? Thank you, B. Bodger

3 4

[Dovecot] Debian packages
by Moritz Mertinkat 02 Jul '07

02 Jul '07

Hi there, anyone interested in Debian Dovecot 1.0.1 packages? I have created a package for etch/stable... Could do that for sarge/oldstable as well. Greets, Maurice.

2 2

[Dovecot] v1.1 max connections per user
by Timo Sirainen 02 Jul '07

02 Jul '07

v1.1 has now: # Maximum number of connections allowed for a user. The limits are enforced # separately for IMAP and POP3 connections, so you can move this setting # inside protocol {} to have separate settings for them. NOTE: The user names # are compared case-sensitively, so make sure your userdb returns usernames # always using the same casing so users can't bypass this limit! #mail_max_user_connections = 10 Is 10 a good default? Currently new connections just fail authentication with a "Maximum number of connections exceeded" error message. v2.0 hopefully will instead disconnect the oldest idling connection with IMAP.

5 7

[Dovecot] Mbox vs maildir
by Simon Gao 02 Jul '07

02 Jul '07

> The upcoming dbox and cydir formats of course beat everything in > performance :) Is dbox in Dovecot 1.1 tree now? Is it the redesigned dbox? How close is dbox ready for general use? I am interested in testing it out. Where can I find instruction on how to configure dovecot to use dbox? Simon

2 1

[Dovecot] auto Cc: with dovecot+mysql
by albinootje 02 Jul '07

02 Jul '07

hi, i'm migrating 1 mail-server from LDAP+postfix+courier to mysql+postfixadmin+dovecot, on a debian etch machine i have followed this howto : http://wiki.dovecot.org/HowTo/DovecotLDAPostfixAdminMySQL (changed uid and gid for usage in debian, the SVN-postfixadmin didn't work for me, so i used the stable version, and haven't tested the SASL-part yet) this works great, except the LDAP+postfix setup has for some users an automatic Cc: say, for example, 1 user, with email-address jeremy(a)mydomain.org, will also have all the emails going to jeremy(a)gmail.com so far i have failed to find out whether this can be done with postfix in that setup, following above mentioned howto (postfixadmin can do aliases, but not "auto Cc: for virtual domains afaik) can this be done by dovecot LDA maybe ? or ... can i have a dovecot.conf where certain users use LDAP instead of mysql for lookups and those kind of preferences ? grtz, albi

2 1

[Dovecot] Differences in deliver and IMAP
by Andy Shellam 01 Jul '07

01 Jul '07

Hi I've now got Dovecot 1.0.1 authenticating with PostgreSQL for the IMAP service, but deliver doesn't seem to work the same. I'm using the "prefetch" passdb, but deliver doesn't seem to recognise it. Here's the log for a deliver attempt: dovecot: Jul 01 16:51:35 Info: auth(default): master in: USER 1 andy.shellam(a)mailnetwork.co.uk service=deliver dovecot: Jul 01 16:51:35 Error: auth(default): prefetch(andy.shellam(a)mailnetwork.co.uk): passdb didn't return userdb entries dovecot: Jul 01 16:51:35 Info: auth(default): master out: NOTFOUND 1 And here's the log for an IMAP login attempt straight after: dovecot: Jul 01 16:51:46 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=84.45.66.158 rip=82.165.38.62 resp=AGFuZHkuc2hlbGxhbUBtYWlsbmV0d29yay5jby51awBhYzI5Y2U4NHN5ZA== dovecot: Jul 01 16:51:46 Info: auth(default): sql(andy.shellam(a)mailnetwork.co.uk,82.165.38.62): query: SELECT <user_field> as user, <password_field> as password, <home_directory> AS userdb_home, <mail_directory> AS userdb_mail, <chroot_directory> AS userdb_chroot, <uid_field> AS userdb_uid, <gid_field> AS userdb_gid FROM <user_table> WHERE <user_field> = 'andy.shellam(a)mailnetwork.co.uk' dovecot: Jul 01 16:51:46 Info: auth(default): client out: OK 1 user=andy.shellam(a)mailnetwork.co.uk dovecot: Jul 01 16:51:46 Info: auth(default): master in: REQUEST 1 24949 1 dovecot: Jul 01 16:51:46 Info: auth(default): prefetch(andy.shellam(a)mailnetwork.co.uk,82.165.38.62): success dovecot: Jul 01 16:51:46 Info: auth(default): master out: USER 1 andy.shellam(a)mailnetwork.co.uk home=<home_directory> mail=maildir:<mail_directory> chroot=<chroot_directory> uid=<uid> gid=<gid> dovecot: Jul 01 16:51:46 Info: imap-login: Login: user=<andy.shellam(a)mailnetwork.co.uk>, method=PLAIN, rip=82.165.38.62, lip=84.45.66.158 This works if I use separate userdb and passdb queries. Does deliver not support the prefetch authentication method? Thanks, Andy.

2 1

Re: [Dovecot] v1.1 max connections per user
by Bill Boebel 01 Jul '07

01 Jul '07

On Sat, June 30, 2007 7:50 pm, Charles Marcus said: > Timo Sirainen, on 6/30/2007 7:25 PM, said the following: >> On Sat, 2007-06-30 at 19:11 -0400, Charles Marcus wrote: >>> Timo Sirainen, on 6/30/2007 6:43 PM, said the following: >>>> v1.1 has now: >>>> >>>> # Maximum number of connections allowed for a user. The limits are enforced >>>> # separately for IMAP and POP3 connections, so you can move this setting >>>> # inside protocol {} to have separate settings for them. NOTE: The user names >>>> # are compared case-sensitively, so make sure your userdb returns usernames >>>> # always using the same casing so users can't bypass this limit! >>>> #mail_max_user_connections = 10 >>>> >>>> Is 10 a good default? >>> I'm assuming this is per IP? >> >> No. I'm not sure if it should. Perhaps. It's mostly intended to prevent >> unintentional abuse by stupid clients, so having 3+ thunderbirds open in >> different locations with each having 5 connections should probably be >> allowed. > > Ok - you said 10 was the default - but then said that 15 (3 TBirds x 5) > connections should be allowed, which is more than 10... so... you just > meant that one could accommodate that by upping this limit to 15? I like 15. That way it is high and isn't as likely to affect existing installations unless they manually set it to something lower. Or if you want to have a separate default for POP vs IMAP, I'd use 5 for POP and 15 for IMAP.

3 2

[Dovecot] Copyright notices in code
by Timo Sirainen 30 Jun '07

30 Jun '07

I thought about committing this change to all .c files: Removed all Copyright Timo Sirainen comments. They weren't always correct and the year numbers were rarely updated when something was changed. Copyright is owned by the creator by default in practically all countries, there's no need to advertise it everywhere. Can anyone think of reasons why this wouldn't be a good idea?

7 7

Re: [Dovecot] connection dropped by imap
by Mantas 30 Jun '07

30 Jun '07

apache log say nothing. dovecot log : dovecot: Jun 30 10:56:06 Info: auth(default): passwd(diana(a)aaaaa.lt,127.0.0.1): unknown user dovecot: Jun 30 10:56:06 Info: auth(default): passwd(diana(a)aaaaa.lt,127.0.0.1): unknown user dovecot: Jun 30 10:56:06 Info: imap-login: Login: user=<diana(a)aaaaa.lt>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Jun 30 10:56:06 Info: IMAP(diana(a)aaaaa.lt): Disconnected: Logged out dovecot: Jun 30 10:56:07 Info: auth(default): passwd(diana(a)aaaaa.lt,127.0.0.1): unknown user dovecot: Jun 30 10:56:07 Info: auth(default): passwd(diana(a)aaaaa.lt,127.0.0.1): unknown user dovecot: Jun 30 10:56:07 Info: imap-login: Login: user=<diana(a)aaaaa.lt>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Jun 30 10:56:07 Info: IMAP(diana(a)aaaaa.lt): Disconnected: Logged out dovecot: Jun 30 10:57:07 Info: auth(default): passwd(diana(a)aaaaa.lt,127.0.0.1): unknown user dovecot: Jun 30 10:57:07 Info: auth(default): passwd(diana(a)aaaaa.lt,127.0.0.1): unknown user dovecot: Jun 30 10:57:07 Info: imap-login: Login: user=<diana(a)aaaaa.lt>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured when error "connection dropped by imap" appear, allways login procedure repeated 3 times (in log file). On Fri, 29 Jun 2007 23:24:12 +0200, Philipp Wollermann <philipp(a)igowo.de> wrote: > Mantas wrote: >>> when i create imap account in mail client (ex: outlook, thunderbird) > it's >>> allright. but if i want login with this account to webmail (i have 2 >>> webmail: squirrelmail and roundcube) commonly i get error. squirrelmail >>> say: Connection droped by imap. roundcube say nothing(white screen). > But >>> sometimes i can login. >>> > So.. what exactly appears in your system logfiles in /var/log when you > try to login and it does not work? Shouldn't that be the first thing to > look for? :) > > Regards, > Philipp

1 0

[Dovecot] connection dropped by imap
by Mantas 30 Jun '07

30 Jun '07

hello, when i create imap account in mail client (ex: outlook, thunderbird) it's allright. but if i want login with this account to webmail (i have 2 webmail: squirrelmail and roundcube) commonly i get error. squirrelmail say: Connection droped by imap. roundcube say nothing(white screen). But sometimes i can login. and i see one thing... when i restart apache, i can login above 1-2 hours, but later i can't login. i restart apache again and again i can login 1-2 hours. please help

2 2

[Dovecot] Document variable modifiers in pop3_uidl_format
by Ben Winslow 29 Jun '07

29 Jun '07

Attached is a trivial patch to document the fact one can use variable modifiers in pop3_uidl_format. -- Ben Winslow <rain(a)bluecherry.net>

1 0

[Dovecot] wiki.dovecot.org double-escapes capcha info
by Ben Winslow 29 Jun '07

29 Jun '07

The "capcha" on wiki.dovecot.org seems to be double-escaping HTML entities in the informational message, such that the wiki displays "Captcha to prevent wiki spam, write Dovecot here:" [sic.] When I dutifully entered "Dovecot," it didn't work, saying "You didn't provide the correct captcha. Use the browser's Back button and try again, or register an account to avoid this." [sic] It took a few minutes for me to realize what was going on and simply enter "Dovecot" for the capcha... -- Ben Winslow <rain(a)bluecherry.net>

1 0

[Dovecot] dovecot help
by Andy Fadich 29 Jun '07

29 Jun '07

Hello, I have a mail server which I upgraded yesterday. OLD: Redhat 9 sendmail (very old version) UW ipop3d usermin with readmail module for webmail access (very old version) NEW: Fedora Core 6 sendmail 8.13.8 Usermin for webmail again dovecot 1.0.0 # /etc/dovecot.conf protocols: pop3 login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login mail_location: mbox:/home/%u/mail:INBOX=/var/spool/mail/%u mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/pop3 pop3_uidl_format: %08Xv%08Xu auth default: passdb: driver: pam userdb: driver: passwd Everything is working great, besides a few glitches here and there. However, When accessing mailboxes via webmail (usermin) an email shows up with a subject of DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA. As far as I can tell, this is an IMAP folder directory portion of the mailbox file that should be hidden. We don't use IMAP at all, and it is confusing people when they see this message that never was in their webmail before. Anyone know how to hide, remove or otherwise fix? Thank you in advance. Andy

4 9

[Dovecot] FreeBSD NFS file locking mechanism
by Tony Tsang 29 Jun '07

29 Jun '07

Hi all, I have some machines running FreeBSD and dovecot deployed. User's home dir is on NFS mount and I've found that dovecot only works with dotlock file locking mechanism, fcntl and flock failed. Now it causes problem with thunderbird (thunderbird is cachine connections) waiting forever and I noticed that dovecot is trying to acquire a lock but unsuccessful since the lock file is in place. Is it possible to use file locking other than dotlock on FreeBSD NFS mounted homedir? How do I achieve this? Thanks a lot. Tony Tsang.

4 4

[Dovecot] Server 1.0.1 migration: Maildir : UID inserted in the middle of mailbox
by damien chambe - EGS 29 Jun '07

29 Jun '07

Hello all, Since a migration from dovecot 1.rc16 to Dovecot 1.0.1 + new server, every day I have a lot of errors like this : Jun 21 17:42:34 dovecot1 deliver(damien.chambe(a)egs-gestion.fr): msgid=<467A9B3E.5070605(a)egs-gestion.fr>: saved mail to INBOX Jun 21 17:42:34 dovecot1 postfix/pipe[10242]: 92DD11FA8B: to=<damien.chambe(a)egs-gestion.fr>, relay=dovecot, delay=0, status=sent (egs-gestion.fr) Jun 21 17:42:34 dovecot1 postfix/qmgr[2724]: 92DD11FA8B: removed Jun 21 17:42:37 dovecot1 dovecot: IMAP(damien.chambe(a)egs-gestion.fr): Maildir /mnt/baie/hula/dovecot/maildir/damien.chambe sync: UID inserted in the middle of mailbox (374 > 1, file = 1182330228.P30307Q0M224874.dovecot1:2,ST) Jun 21 17:42:37 dovecot1 dovecot: IMAP(damien.chambe(a)egs-gestion.fr): Disconnected: Mailbox is in inconsistent state, please relogin. Jun 21 17:51:41 dovecot1 dovecot: imap-login: Login: user=<damien.chambe(a)egs-gestion.fr>, method=PLAIN, rip=10.6.1.104, lip=10.5.3.38 Jun 21 17:51:41 dovecot1 dovecot: IMAP(damien.chambe(a)egs-gestion.fr): Corrupted index cache file /opt/dovecot/indexes/damien.chambe/.INBOX/dovecot.index.cache: indexid changed After this error, all UID are regenerated. And, when the user logs in, all headers are sent back to the client (IMAP / thunderbird 1.5.x or 2.0.0.4). No email are lost or duplicated, but it cause a huge traffic on our DSL lines, and user are complaining... There's also other errors related to UID: Jun 21 16:11:01 dovecot1 deliver(pr(a)egs-gestion.fr): rename(/mnt/baie/hula/dovecot/maildir/pr/dovecot-uidlist.lock, /mnt/baie/hula/dovecot/maildir/pr/dovecot-uidlist) failed: No such file or directory Jun 21 16:11:01 dovecot1 deliver(pr(a)egs-gestion.fr): file_dotlock_replace(/mnt/baie/hula/dovecot/maildir/pr/dovecot-uidlist) failed: No such file or directory Jun 21 16:11:02 dovecot1 deliver(pr(a)egs-gestion.fr): /mnt/baie/hula/dovecot/maildir/pr/dovecot-uidlist: next_uid was lowered (374 -> 373) Jun 21 16:11:02 dovecot1 deliver(pr(a)egs-gestion.fr): msgid=<467A85CB.50009(a)fica.fr>: saved mail to INBOX Jun 21 16:11:02 dovecot1 dovecot: IMAP(pr(a)egs-gestion.fr): rename(/mnt/baie/hula/dovecot/maildir/pr/dovecot-uidlist.lock, /mnt/baie/hula/dovecot/maildir/pr/dovecot-uidlist) failed: No such file or directory Here's the context: Our Dovecot server had to be changed due to a hardware problem I was forced to use SUSE SLES 10 for the new one, instead of SLES 9 on the old server. X86-32 I've kept the same configuration files for postfix, dovecot. We use dovecot deliver. Old postfix version was 2.1.1, now I have 2.2.9 During the migration, I've changed dovecot 1.rc16 to dovecot 1.0.0 When I saw this error, I upgraded to dovecot 1.0.1, but same problem (I use suse rpm packages ) I have 400 mailbox, all Maildir. The problem happens 50 times a day, so not on every mail received. I store mails on NFS, and index on local disk. There's only one dovecot server, so no multiple access. I've tried to remove all index files, and remove dovecot-uidlist, all is correctly re-created, but the problem remains. Could it be an NFS locking problem ? Since only mail are stored on maildir + NFS, and index on local disk, so I didn't set lock_method or nmap_disable Could it be related to this: see email from from Doug Concil : [Dovecot] NFS lock contention for dovecot-uidlist on may 17 , 2007 ? dovecot -n # 1.0.1: /etc/dovecot/dovecot.conf protocols: imap pop3 ssl_disable: yes 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 login_user: dovecotlogin login_process_per_connection: no login_processes_count: 5 max_mail_processes: 2048 first_valid_uid: 120 first_valid_gid: 12 default_mail_env: maildir:/mnt/baie/hula/dovecot/maildir/%n:INDEX=/opt/dovecot/indexes/%n mail_location: maildir:/mnt/baie/hula/dovecot/maildir/%n:INDEX=/opt/dovecot/indexes/%n 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: verbose: yes passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: dovecot group: mail plugin: quota: maildir:storage=1500000:messages=40000 Thanks, -- Cordialement, Damien Chambe EGS 42 bld jules janin - BP 240 - 42006 Saint Etienne Cedex 1 Tel : 04 77 49 48 16 Fax : 04 77 49 48 45 Site institutionnel : http://www.groupe-laurent.com Site catalogue : http://ecat.groupe-laurent.com

3 4

[Dovecot] lda and mail_location
by Mark Edwards 28 Jun '07

28 Jun '07

I have the following set in the main level of my dovecot.conf file: mail_location = maildir:/var/mail/virtual/%u I decided to enable the lda protocol for local delivery from postfix, so I could use sieve plugins. The lda protocol seems to ignore settings in the rest of the dovecot.conf file, however, such as the above. Unless lda has a pre-existing maildir mailbox, it can't create one. How do I give lda defaults to follow, if the above statement doesn't do it? Here is the output of dovecot -n Thanks! ---- # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap pop3 imaps pop3s listen: 127.0.0.1 ssl_listen: [::] ssl_cert_file: /etc/ssl/private/mail.antsclimbtree.com.pem ssl_key_file: /etc/ssl/private/mail.antsclimbtree.com.pem 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 valid_chroot_dirs: /var/mail verbose_proctitle: yes first_valid_uid: 8 last_valid_uid: 8 first_valid_gid: 8 last_valid_gid: 8 mail_extra_groups: mail mail_location: maildir:/var/mail/virtual/%u maildir_copy_with_hardlinks: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/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 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: / inbox: yes auth default: mechanisms: plain login username_format: %Lu verbose: yes passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: mail group: mail

2 13

[Dovecot] UW-IMAP conversion part 2
by Andrew Z 28 Jun '07

28 Jun '07

FWIW, the Dovecot 1.0.1 convert plugin works with all my UW-IMAP mboxes moved to ~/mail. At least that shows that my system otherwise works. Also, I wrote a script to move the mboxes and preserve the IMAP subscriptions. (I hope the list accepts the attached script.)

1 0

[Dovecot] Locking problems on Dovecot 1.x in Maildir
by Ronald MacDonald 28 Jun '07

28 Jun '07

Hi list, Overall, everything works fine, and all the emails are delivered without anything messing up. But then, from time to time, the transaction logs for some users become corrupted, meaning emails cannot be read at all from dovecot. With a bit of a search on google, it seems to be a problem with locking on the transaction log. The individual files are fine - it's maildir, so the chances of 2 accesses on the same file are near impossible. But the problem seems to come when things get a bit busy, and inevitably, the transaction log tends to get corrupted all too often now for me to just go in and delete the log, and start afresh. I've addressed the issue temporarily by putting the index in memory by the :INDEX=MEMORY as opposed to a static file. This isn't ideal, but it seems to save the system going up in arms. Is there an alternative to using this system? Ronald. -- Ronald MacDonald http://www.rmacd.com/ 0777 235 1655

3 7

[Dovecot] convert plugin problem from UW-IMAP
by Andrew Z 28 Jun '07

28 Jun '07

Though there are conversion scripts, I'd like to give the convert plugin a chance. I have Dovecot 1.0.1 on Trustix Secure Linux 2.2 (Linux 2.4.27), and we had UW IMAP 2002e. Dovecot seems to work OK (e.g. I can add copy messages to it), but things break when I activate the convert plugin. The Wiki suggests convert_mail = mbox:~/:INBOX=/var/mail/%u # <--- locally changed to /var/spool/mail/%u convert_skip_broken_mailboxes=yes However, when I start Dovecot, then I get: Starting Dovecot Imap: ILoading modules from directory: /usr/lib/dovecot/imap IModule loaded: /usr/lib/dovecot/imap/lib20_convert_plugin.so IEffective uid=65534, gid=65534, home= Imbox: data=~/:INBOX=/var/spool/mail/dump-capability Imbox: root=, index=, inbox=/var/spool/mail/dump-capability Eopen(/.temp.localhost.localdomain.7834.96dd6ef6b7dfc402) failed: Permission denied Error: imap dump-capability process returned 89 Fatal: Invalid configuration in /etc/dovecot.conf So based on a tip on the mailing list, I try convert_mail = mbox:/home/users/%u:INBOX=/var/spool/mail/%u But the session fails, and Thunderbird can't connect properly. /var/log/dovecot.log Jun 26 11:39:25 Info: IMAP(andrewz): Module loaded: /usr/lib/dovecot/imap/lib20_convert_plugin.so Jun 26 11:39:25 Info: IMAP(andrewz): Effective uid=501, gid=501, home=/home/users/andrewz Jun 26 11:39:25 Info: IMAP(andrewz): mbox: data=/home/users/andrewz:INBOX=/var/spool/mail/andrewz Jun 26 11:39:25 Info: IMAP(andrewz): mbox: root=/home/users/andrewz, index=/home/users/andrewz, inbox=/var/spool/mail/andrewz Jun 26 11:39:25 Info: IMAP(andrewz): mbox: data=/home/users/andrewz:INBOX=/var/spool/mail/andrewz Jun 26 11:39:25 Info: IMAP(andrewz): mbox: root=/home/users/andrewz, index=/home/users/andrewz, inbox=/var/spool/mail/andrewz Jun 26 11:39:25 Info: IMAP(andrewz): maildir: data=/home/users/andrewz/Maildir Jun 26 11:39:25 Info: IMAP(andrewz): maildir: root=/home/users/andrewz/Maildir, index=/home/users/andrewz/Maildir, control=, inbox= Jun 26 11:39:25 Info: imap-login: Login: user=<andrewz>, method=PLAIN, rip=192.168.0.230, lip=192.168.0.60 /var/log/mail/errors Jun 26 11:39:25 localhost dovecot: IMAP(andrewz): Mailbox conversion: Couldn't copy mailbox Maildir/cur/1182879232.P7263Q0M965055.localhost.localdomain:2,Sa: BUG: Unknown internal error Jun 26 11:39:25 localhost dovecot: IMAP(andrewz): Mailbox conversion: Couldn't create mailbox directory Maildir..Trash Jun 26 11:39:25 localhost dovecot: IMAP(andrewz): Sending log messages too fast, throttling.. Jun 26 11:39:25 localhost dovecot: child 7888 (imap) returned error 89 I also tried convert_mail = mbox:%h:INBOX=/var/spool/mail/%u , but that acts like mbox:/home/users/%u. Then, I tried removing ~/Maildir . That doesn't help. When I connect via telnet, I get "1 OK Logged in.", and the remote host closes the connection. Also, I am not clear how Dovecot knows when to stop. With mbox in ~/mail, then dovecot can rename it, but we have mbox in ~/ which of course cannot be renamed. (I suggest moving mboxes to a new subdirectory.) I rebuild Dovecot based from a modified Fedora RPM .spec. My configuration is: # 1.0.1: /etc/dovecot.conf info_log_path: /var/log/dovecot.log protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_location: maildir:~/Maildir mail_debug: yes mail_plugins: convert auth default: passdb: driver: pam userdb: driver: passwd plugin: convert_mail: mbox:/home/users/%u:INBOX=/var/spool/mail/%u convert_skip_broken_mailboxes: yes Andrew

1 0

[Dovecot] deliver without lookup
by Bruno Puga 28 Jun '07

28 Jun '07

Hello friends! Is it possible to make deliver delivery a message without making a lookup using virtual users? I've read the section "Without a Lookup" (http://wiki.dovecot.org/LDA) in the wiki but I can´t do the same thing in my config and I can´t figure this out. From the forum I found this thread ( http://www.mail-archive.com/dovecot@dovecot.org/msg02956.html) but didn't understand why it didn't work in my config. I've tried: HOME=/path/to/user/homedir deliver -f test(a)test.com and I receive the message: Fatal: destination user parameter (-d user) not given I'm asking this because I need to migrate a system from maildrop to dovecot that has a script made by the system admin before me that makes something like follow. When someone send a message to all(a)domain.com, postfix call a transport that calls a script like this: ################################ cat > /tmp/message.txt cd /home/vmail/domain.com/ for i in *; do cat /tmp/message.txt | maildrop -d vmail $i domain.com done ################################ Where $i is all my users that have an domain account. This script delivery the message direct to the user's maildir, without making a lookup. I know to do this with Dovecot deliver making a lookup, but I'd like to do this without. Again, is it possible with deliver ? Or any ideas to workaround this? version 1.0.0 dovecot -n # /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot-imapd.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/lib/dovecot/imap-login mail_location: maildir:/home/vmail/%d/%n/ mail_debug: yes mail_plugins: quota imap_quota acl imap_client_workarounds: outlook-idle delay-newmail namespace: type: private separator: . prefix: INBOX. inbox: yes namespace: type: private separator: . auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: acl: vfile:/etc/dovecot/acls Thanks, Bruno.

2 1

[Dovecot] deliver errors
by azher＠niit.edu.pk 28 Jun '07

28 Jun '07

Hi, I am using ver 1.0.1 and getting the following errors in mail.log and auth.log respectively. However I can login to imap and retrieve emails no problem, while sending email is also ok. Jun 27 23:59:21 webmail sm-mta[1889]: l5RIvhQE001865: Warning: program /usr/local/libexec/dovecot/deliver unsafe: Group writable directory Jun 27 23:27:30 webmail dovecot-auth: (pam_unix) authentication failure; logname= uid=0 euid=0 tty=dovecot ruser= rhost=127.0.0.1 user=azher Can someone plz suggest what can be wrong. Regards -Azher

4 7

[Dovecot] IMAP IDLE goes to sleep
by Julian Cowley 28 Jun '07

28 Jun '07

First of all, let me say that I'm really impressed with Dovecot. It is great. Problem description =================== Now I've got a possible bug I'd like to report. I've been learning about the IMAP protocol recently, and have started playing with the IDLE command. The problem is that Dovecot doesn't always notify the client when there is new mail available. While notifications work for the most part, it seems that Dovecot occasionally gets itself into a rut where it fails to notice any changes to the mailbox (new messages, flag changes, etc.). The problem usually becomes apparent when there is more than one email client accessing the same mailbox. In fact, this may be a requirement -- I only tested it once, but I couldn't reproduce the problem when I had only one connection open to the mailbox (which is in maildir format in my case). An example is included below. Any feedback on how to debug this problem further would be appreciated. An aside ======== After I found out about the IDLE command, I looked for implementations. I ran across this plug-in for Apple Mail (one of my favorite mail clients): http://www.rothwell.us/imapidle/index.html The web page notes that Leopard's Apple Mail may support the IDLE command natively, which is good news if true. It would be really cool if Dovecot's IDLE command can be made robust enough to make this feature really come alive. Example ======= This transcript is copied from an SSL connection directly to dovecot using openssl s_client. At the same time a separate client (Horde/IMP) has the same mailbox open: A0017 IDLE + idling * 7927 FETCH (FLAGS (\Seen \Recent)) * 7927 FETCH (FLAGS (\Deleted \Seen \Recent)) * OK Still here * OK Still here * OK Still here * OK Still here * 7940 EXISTS * 22 RECENT * OK Still here * OK Still here * OK Still here * OK Still here * OK Still here * OK Still here * OK Still here * OK Still here * OK Still here * OK Still here * 7941 EXISTS [At some point after this, something happens (or doesn't happen) and dovecot no longer notifies of new messages. The other client is still reading messages in the same mailbox and new mail is still arriving.] * OK Still here * OK Still here * OK Still here * OK Still here * OK Still here [The above message repeated another 30 times here. Finally, IDLE mode is terminated:] * OK Still here DONE * 7941 EXPUNGE A0017 OK Idle completed. [Now a NOOP is issued to gather any more untagged responses, and there's a deluge of responses, presumably all the stuff that happened while dovecot was asleep. Notice that the highest message is 7967 whereas the last one heard about was 7941.] A0018 NOOP * 7913 FETCH (FLAGS (\Deleted \Recent)) * 7914 FETCH (FLAGS (\Deleted)) * 7915 FETCH (FLAGS (\Deleted)) * 7916 FETCH (FLAGS (\Deleted)) * 7917 FETCH (FLAGS (\Deleted)) * 7918 FETCH (FLAGS (\Deleted)) * 7919 FETCH (FLAGS (\Deleted \Recent)) * 7920 FETCH (FLAGS (\Deleted \Recent)) * 7921 FETCH (FLAGS (\Deleted \Recent)) * 7922 FETCH (FLAGS (\Deleted \Seen)) * 7923 FETCH (FLAGS (\Deleted \Seen)) * 7925 FETCH (FLAGS (\Deleted \Seen)) * 7928 FETCH (FLAGS (\Deleted \Recent)) * 7967 EXISTS * 30 RECENT A0018 OK NOOP completed. Configuration ============= Here are the specifications of the dovecot used in the above test: version dovecot 1.0.1 os linux distro centos 4.5 fs ext3 arch x86_64 kernel 2.6.9-55.ELsmp configure --without inotify --with pam_stack --with forcequota2 cc gcc (GCC) 3.4.6 20060404 (Red Hat 3.4.6-8) In addition, I'm using the deliver LDA as the Postfix mailbox_command, and am using the dovecot-sieve plugin (which is used to set customized IMAP keywords). dovecot -n: # 1.0.1: /etc/dovecot.conf ssl_cert_file: /usr/lib/courier-imap/share/imapd.pem ssl_key_file: /usr/lib/courier-imap/share/imapd.pem login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login first_valid_uid: 100 mail_location: maildir:~/Maildir maildir_copy_with_hardlinks: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 namespace: type: private separator: / inbox: yes auth default: default_realm: lava.net verbose: yes passdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot-sql.conf ps. Good thing there's no POP IDLE command!

5 7

[Dovecot] Can't see public folder contents after renaming folder
by Robert Fraser 28 Jun '07

28 Jun '07

Hi We are using Thunderbird 2.0.0.x (Linux and Windows) with IMAP accounts against Dovecot 1.0.beta3 on Ubuntu 6.06 Dapper with Maildir. It is all working well except when we rename a folder in the public namespace, the person who renames it can no longer see the contents of the folder. If we rename it back to the original name , the person can see the contents again. If we delete the files in the index directory for that folder on the file system, the user can see the folder contents again. Can anyone tell me how to fix this? Many thanks Rob Relevant dovecot.conf details follow ------------------------------- default_mail_env = maildir:~/.Mail namespace private { separator = / inbox = yes } namespace public { separator = / prefix = Public/ location = maildir:/home/mail/public:CONTROL=~/.Mail/control/public:INDEX=~/.Mail/index/public } maildir_copy_with_hardlinks = yes umask = 0007

4 4

[Dovecot] LSUB/SUBSCRIBE under namespaces
by bhayden＠umn.edu 27 Jun '07

27 Jun '07

Hi folks. Here's our situation: Migrating from UW-IMAP. Have lots (as in, tens of thousands) of clients set up using '~/mail' as the IMAP root, and using subscriptions. Dovecot mail_location is using '~' for mbox storage. We've disabled full filesystem access in Dovecot in order to use ACLs for shared folders. Hence we have a hidden namespace for backwards compatibility with those clients using '~/mail' (dovecot -n output is at the end of this message so you can see exact settings). Here's the problem. If the client is not taking advantage of this hidden namespace--say it's configured to use plain old 'mail' as the root directory--LSUB and SUBSCRIBE work as I'd expect. Subscribing to a folder called 'foo' puts this in the user's subscriptions file: mail/foo And this (from Thunderbird's log) is the LSUB exchange: 48203776[ed8ebe0]: 2e03600:server.umn.edu:A:SendData: 6 lsub "" "mail/*" 48203776[ed8ebe0]: ReadNextLine [stream=ed8ef88 nb=26 needmore=0] 48203776[ed8ebe0]: 2e03600:serverl.umn.edu:A:CreateNewLineFromSocket: * LSUB () "/" "mail/foo" 48203776[ed8ebe0]: ReadNextLine [stream=ed8ef88 nb=38 needmore=0] (trimmed...) 48203776[ed8ebe0]: 2e03600:bhayden.email.umn.edu:A:CreateNewLineFromSocket: 6 OK Lsub completed. All is well. However, when the client is configured with '~/mail' as the root and hence triggers the hidden namespace for such, SUBSCRIBE only writes a path relative to that namespace prefix. So as opposed the 'mail/foo' in the first example, we get: foo written to the subs folder. This leads to three problems: 1. Folders subscribed to when using this namespace will either disappear or break in a client using a different IMAP root setting that actually refers to the same place. For example, if this user moves to a client (such as both of the webmail offerings on campus) that use 'mail/' as the prefix, these folders will not be visible. This is a fairly sizeable population of our users, whom we aren't necessarily in the position to say "too bad" to. :) 2. Users moved over from UW-IMAP, who were using '~/mail' for the IMAP root, have a subscriptions file full of: ~/mail/bar Dovecot, with the same client configuration (since it's expecting a bare folder name to which it will prepend the namespace prefix), interprets this as so: 49036288[fa7e740]: 2eabc00:server.umn.edu:A:CreateNewLineFromSocket: * LSUB () "/" "~/mail/~/mail/foobar" Leading to having the folder displayed in the client's list, but giving an error on SELECT. Now, this one we could theoretically "solve" by scrubbing the prefixes out of subs files as we convert; however, that leaves us with #1 above, where the bare folder name in the subs file depends on (to the average user) an obscure client config setting, which in practice in a large heterogeneous environment is unreliable. 3. Users who have been using an IMAP root of 'mail' in some client and subscribed to folders, who then use a client with the root set to '~/mail' see what appears to be "duplicates" of the same folder at the top level and then within a bogus 'mail/' subdirectory. They (quite reasonably, from their perspective), delete one of these, only to find they've deleted the only copy of said folder. Not good. Also, users can't solve some of these problems by unsubbing and re-subbing on their own, as trying to unsubscribe from a folder that doesn't exist (such as ~/mail/~/mail/foobar in the example above) fails. So, I'm wondering if there's any way to address this. I looked through the list archives and code pretty thoroughly. Only thing I noticed was a CVS log mentioning a "subscriptions=yes" setting for namespaces, which sounded like it might address this problem. However, putting that setting into dovecot.conf causes it to fail to start with a "Unrecognized config option" error, and using an imap_executable wrapper that sets the env variable as specified in the code (NAMESPACE_<number>_SUBSCRIPTIONS) sets it, as I can see from the dovecot log output: Namespace: type=private, prefix=~/mail/, sep=/, inbox=no, hidden=yes, subscriptions=yes But doesn't seem to have any effect. These two things combined lead me to believe this option was deprecated at some point? Any thoughts or suggestions? While we're moving away from UW for a reason ;), it does seem to handle this one thing more coherently as it recognizes, for example, that if the server equivalent of mail_location's storage is '~', then subscription file entries: '~/mail/foo' and 'mail/foo' are the same thing, while 'foo' is '~/foo'--regardless of client settings or namespaces. Whereas in the same situation Dovecot handles a client IMAP root of '~/mail' vs 'mail' differently, even though they are in fact the same thing. This is also internally inconsistent, because (as noted above) when a namespace is not in effect Dovecot SUBSCRIBEs using a path relative to the mail_location storage--including the client's IMAP root portion of the path--whereas when a namespace is in effect it SUBSCRIBEs with only the bare mailbox name without the current client's IMAP root to give it context and meaning. Wouldn't it seem better to have these be consistent in this respect? We need to figure this out somehow before going any further with our migration. We'll modify the source if necessary, but are hoping for a solution that doesn't require maintaining local mods to the source code unless we absolutely have to. :) And this seems like a basic enough issue that it'd be good to handle it in the real codebase. Thanks for any help or insight, -Brian Hayden Internet Services University of Minnesota dovecot -n output: (The shell script mail_executable doesn't come into play here--it sets some namespace settings only for special shared accounts using Maildir, and doesn't touch anything for the normal mbox accounts discussed above.) # /etc/opt/dovecot/dovecot.conf syslog_facility: local6 protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/opt/openssl/certs/dovecot.pem ssl_key_file: /etc/opt/openssl/private/dovecot.pem shutdown_clients: no login_dir: /var/opt/dovecot/run/dovecot/login login_executable(default): /opt/dovecot/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot/libexec/dovecot/pop3-login max_mail_processes: 8192 first_valid_uid: 99 mail_location: mbox:~:INBOX=/var/mail/%u:INDEX=/var/mail/.dovecot-index/%1u/%u/ mail_debug: yes mail_executable(default): /opt/dovecot/libexec/dovecot/mail_path.sh mail_executable(imap): /opt/dovecot/libexec/dovecot/mail_path.sh mail_executable(pop3): /opt/dovecot/libexec/dovecot/pop3 mail_plugins(default): zlib mail_plugins(imap): zlib mail_plugins(pop3): mail_plugin_dir(default): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv namespace: type: private separator: / inbox: yes namespace: type: private separator: / prefix: ~/mail/ location: mbox:%h/mail/:INDEX=/var/mail/.dovecot-index/%1u/%u/ hidden: yes namespace: type: private separator: / prefix: ~%u/mail/ location: mbox:~%u/mail/:INDEX=/var/mail/.dovecot-index/%1u/%u/ hidden: yes namespace: type: private separator: / prefix: Shared/ location: maildir:~/Maildir/Shared:INDEX=/var/mail/.dovecot-index/%1u/u/shared auth default: username_format: %Lu passdb: driver: pam args: session=yes * userdb: driver: passwd plugin: acl: vfile:

2 2

[Dovecot] Dovecot 1.0.01 / Outlook error 0x800CCCD2
by Dave Hatton 27 Jun '07

27 Jun '07

Hi. I'm having a problem with a user running outlook 2003 against dovecot 1.0.1. A second user works fine and I haven't moved on to create a third (or more yet). On a send and receive I get an error from outlook "Task 'Checking for new mail in subscribed folders on server.' reported error (0x800CCCD2) : 'Outlook is unable to download folder (null) from the IMAP e-mail sever for account Server. Error: The server responded: 'Permission denied'....' Now I've check permissions and as a precaution "chown -R" to make sure I got them all. If I cancel the error I seem to be able to continue without a problem. It's just very annoying to get an error I can fix. Can anyone shed on light on this or suggest a plan of attack? Thanks Daveh

2 1

[Dovecot] Dovecot LDA munging INBOX access times?
by Steven F Siirila 27 Jun '07

27 Jun '07

We are running Dovecot 1.0.0 using mbox format (currently in the midst of conversion from UW IMAP). We discovered today that the Dovecot LDA is accessing the user's INBOX at delivery time! Not only do our users rely on this access time being when they last accessed their e-mail, we also rely on it to migrate "inactive" users to cheaper disk. I consider this a major bug for us and wondered if there is some reason why the LDA is doing this. I can understand that in the absence of index files it may choose to build them from scratch and therefore need to access the INBOX, but in normal cases I don't see that being necessary. It seems to me there should be a few options for how the LDA operates: 1) Deliver to INBOX, do not create or update the index. This would avoid accessing the INBOX. 2) Deliver to INBOX, update the index only if it is already current. This would avoid accessing the INBOX. (not sure if this is possible) 3) Deliver to INBOX, update/create the index as necessary to make it current. This obviously may involve accessing the INBOX. We would rather not go with option #1 -- what's the point of using Dovecot LDA in that scenario?? Comments appreciated. -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

4 12

[Dovecot] User mapping via pam
by Flannery, Andrew 27 Jun '07

27 Jun '07

Hi, I'm trying to change the PAM_USER within a pam module, and observed that dovecot 0.99 does not support this. I then looked at 1.x and found: src/auth/passdb-pam.c:232: /* FIXME: this doesn't actually work since we're in the child process.. */ status = pam_get_item(pamh, PAM_USER, (linux_const void **)&item); if (status != PAM_SUCCESS) { *error = t_strdup_printf("pam_get_item() failed: %s", pam_strerror(pamh, status)); return status; } auth_request_set_field(request, "user", item, NULL); however it appeared to me that the auth process was passing this username to the parent in its response. Is this issue resolved? I compiled and tested mapping the username sso to the user andrew: Jun 27 13:38:45 itsrv dovecot: auth-worker(default): pam(sso,10.x.x.x): lookup service=imap Jun 27 13:38:45 itsrv dovecot: auth(default): auth(sso,10.x.x.x): username changed sso -> andrew Jun 27 13:38:45 itsrv dovecot: auth(default): client out: OK 1 user=andrew Jun 27 13:50:57 itsrv dovecot: auth(default): master in: REQUEST 1 19761 1 Jun 27 13:50:57 itsrv dovecot: auth(default): passwd(andrew,10.x.x.x): lookup Jun 27 13:50:57 itsrv dovecot: auth(default): master out: USER 1 andrew system_user=andrew uid=1001 gid=1001 home=/home/Andrew Also, is this behavior dependant on me setting blocking=yes for "passdb pam" in dovecot.conf? (for this test It was set) Thanks, Andrew Flannery

2 1

[Dovecot] ?? Error: child 1064 (imap) killed with signal 4
by Benton Haynes 27 Jun '07

27 Jun '07

After noticing a commit to the HG repository, http://hg.dovecot.org/dovecot-1.0/rev/f88b1e225be5 about, " We didn't update last_output timestamp with long fetches, causing Dovecot to idle-disconnect the client." I chekced out the latest from the DOVECOT-1.0 repo, and built again. Unfortunately, this problem still exists. Login simply disconnects. Any help, anyone? -- Ben

3 7

[Dovecot] Dovecot and SUSE 10: inotify_init()
by damien chambe - EGS 27 Jun '07

27 Jun '07

Hello all, Since my migration to SUSE SLES 10, I have a new error message : dovecot1 dovecot: IMAP(damien.chambe(a)egs-gestion.fr): inotify_init() failed: Too many open files It seems to occurs when thunderbird is idle, or when I click on sub folders I have a ulimit for open files a bit low, 1024 I have changed to 4096, but same error message. It has no visible consequences. I am on dovecot 1.0.1 I don't think it is related to dovecot config, any idea ? ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited pending signals (-i) 24573 max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited open files (-n) 4096 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 24573 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited -- Cordialement, Damien Chambe EGS - Groupe Laurent 42 bld jules janin - BP 240 - 42006 Saint Etienne Cedex 1 Tel : 04 77 49 48 16 Fax : 04 77 49 48 45 Site institutionnel : http://www.groupe-laurent.com Site catalogue : http://ecat.groupe-laurent.com

2 1

[Dovecot] LogicMail for Blackberry and Dovecot
by Rick Romero 27 Jun '07

27 Jun '07

FYI - I just had a great interaction with the developer of this software. LogicMail for Blackberry is a true IMAP/POP client for Blackberry, which wasn't working correctly with Dovecot's IMAP. I merely posted in the sourceforge forums and got a VERY fast response with a working fix. http://logicmail.sourceforge.net/ Unfortunately I'm not a Blackberry user, but I know IMAP clients are hard to find. So I can't comment on it's usability or features, but I thought I'd give it a little press for his quick response :) Rick

2 1

[Dovecot] 1.0.rc28 released
by Timo Sirainen 27 Jun '07

27 Jun '07

http://dovecot.org/releases/dovecot-1.0.rc28.tar.gz http://dovecot.org/releases/dovecot-1.0.rc28.tar.gz.sig Still a bit more fixes. My coding TODO list is again empty. Unless something special happens in the next few weeks, I'll still make rc29 with the documentation included and v1.0 will be released April 13. * deliver + userdb static: Verify the user's existence from passdb, unless allow_all_users=yes * dovecot --exec-mail: Log to configured log files instead of stderr * Added "-example" part to doc/dovecot-sql-example.conf and doc/dovecot-ldap-example.conf. They are now also installed to $sysconfdir with "make install". + When copying/syncing a lot of mails, send "* OK Hang in there" replies to client every 15 seconds so it doesn't just timeout the connection. + Added idxview and logview utilities to examine Dovecot's index files + passdb passwd and shadow support blocking=yes setting now also + mbox: If mbox file changes unexpectedly while we're writing to it, log an error. + deliver: Ignore -m "" parameter to make calling it easier. + deliver: Added new -n parameter to disable autocreating mailboxes. It affects both -m parameter and Sieve plugin's fileinto action - mbox: Using ~/ in the mail root directory caused a ~ directory to be created (instead of expanding it to home directory) - auth cache: If unknown user was found from cache, we didn't properly return "unknown user" status, which could have caused problems in deliver. - mbox: Fixed "UID inserted in the middle of mailbox" in some conditions with broken X-UID headers - Index view syncing fixes - rc27 didn't compile with some non-GCC compilers - vpopmail support didn't compile in rc27 - NFS check with chrooting broke home direcotry for the first login - deliver: If user lookup returned "unknown user", it logged "BUG: Unexpected input" - convert plugin didn't convert INBOX

8 18

[Dovecot] Fatal: Login process must not run as root
by santhosh 27 Jun '07

27 Jun '07

Hi all, I am new to dovecot, i had installed dovecot in RH9 machine and when i tried to run( as root) it, i am getting the below message in the log file. dovecot: Jun 11 18:57:16 Fatal: Login process must not run as root I have done the installation as below ( as normal user): ./configure make sude make install When i try to run as a normal user i am getting the error like Error: Can't write to log directory /var/log: Permission denied Can anybody tell me where i am doing mistake ? Thanks in advance Regards, Santhosh

4 4

[Dovecot] Public Namespace and ACLs with pure virtual users
by Marc Delling 27 Jun '07

27 Jun '07

hi! i would appreciate to have some comments on my below scenario: # from the config userdb static { args = uid=vmail gid=mail home=/vmail/%d/%n } namespace public { separator = / prefix = All/ location = maildir:/vmail/%d/all/Maildir:CONTROL=~/Maildir/control/ all:INDEX=~/Maildir/index/all inbox = no hidden = no } namespace private { separator = / prefix = location = maildir:~/Maildir inbox = yes hidden = no } # end config the public namespace is also the maildir of the user "all@mydomain". a sieve skript is dropping mail for all@mydomain to the appropriate maildir within this maildir/namespace (e.g. .Support/) first of all: this works to some point but is such a configuration valid? can a public namespace be the maildir of a user? if a new mail for all@mydomain comes in, all subscribed users (of this domain) can view it and it is marked as /Seen individually. the important feature to me: the /Seen flags are managed per user as configured in the public namespace now the problem: the whole mail system runs with one uid/gid and virtual users, which has the effect that some user can delete mails in the public namespace or drop mails into it, create folders etc. this is not wanted. i wanted a read-only public namespace. so i decided to use acls. as namespace prefixes are ignored i needed to create them globally. my first try was: /etc/dovecot/acls/Support: owner lrwstiekxa authenticated lr which lead to the result that other users than all@mydomain cannot manipulate the public namespace at all, including setting their /Seen flag. that was the first surprise to me as i thought this flag would be managed seperately in the users homes. after a (very short) thought i came to this (allow setting the /Seen flag for others): owner lrwstiekxa authenticated lrs which lead to another unexpected result: the /Seen flag is now set globally. if one user marks a mail /Seen, it is /Seen for all other users too. where is the problem? except for the iso/osi layer 8 problem i am aware of... marc

4 7

[Dovecot] dovecot -n segfault
by Luca Corti 26 Jun '07

26 Jun '07

# uname -a Linux ns2 2.6.18-4-sparc64 #1 Mon Mar 26 11:16:07 UTC 2007 sparc64 GNU/Linux # dovecot -n # 1.0.1: /usr/local/etc/dovecot.conf Segmentation fault uhu? ciao Luca

3 4

[Dovecot] set maildir and directory default for deliver?
by Mark Edwards 26 Jun '07

26 Jun '07

I asked this question in a more detailed post, with no response, so I'm going to ask point blank. Is there a way make dovecot's deliver use default mailbox and directory settings? I'm thinking of the mail_location parameter, which deliver seems to ignore. Thanks! -- Mark Edwards

1 0

[Dovecot] APPEND fails
by Dirk Müller 26 Jun '07

26 Jun '07

hi list, i wrote a small tool in java which transfers all mails from one imap-server account to another imap-server account using the javax.mail API. when i use cyrus as source and destination imap server everything is fine. when i use dovecot as destination server occasionally exceptions occur when appending the mails. i was not able to see what's really going wrong so i used wireshark to get the imap command that fails: A23 APPEND INBOX.MYSUBFOLDER () "14-Mar-2007 14:20:45 +0100" {0+} A23 NO Append aborted. this is easy to check via telnet, always the same error. i'm not sure why the javax.mail API uses the "{0+}" but somehow it occurs every now and then. sending this command to a cyrus imap server does not fail. any idea? is this a javax.mail problem? thanks and best regards, dirk

2 1

Re: [Dovecot] dovecot.conf authentication after Debian upgrade
by Didier Misson 25 Jun '07

25 Jun '07

Bruno Puga a écrit : > I don't know what are the exactly parameters changed from sarge to etch, > but you can send us more detailed information changing this settings in > your dovecot's conf: > http://wiki.dovecot.org/Debugging/Authentication > > See this section to find out if you are looking for logs in the right > place accordingly to you configuration. > http://wiki.dovecot.org/Logging <http://wiki.dovecot.org/Logging> > > Send us the dovecot -n output instead of dovecot.conf. Thanks for you reply Bruno ;-) Between Sarge and Etch, many parameters changed between the 2 Dovecot version ... example : imaps_listen = * ---> replace by ---> replace by protocol imap { listen = 127.0.0.1:143 ssl_listen = *:993 } ... of course, simply replacing the package version, and new Dovecot doesn't run ! :-( --------------------------------------------- dovecot -n (I discover this command today) ks:/etc/dovecot# dovecot -n # /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_timestamp: %Y-%m-%d %H:%M:%S listen: 127.0.0.1:143 ssl_listen: *:993 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login first_valid_uid: 1000 mail_extra_groups: mail default_mail_env: maildir:~/Maildir mail_location: maildir:~/Maildir imap_client_workarounds: outlook-idle delay-newmail netscape-eoh tb-extra-mailbox-sep auth default: passdb: driver: passwd userdb: driver: passwd --------------------- I will try to read the documentation on the authentication debugging. Thanks a lot for your help. ;-) -- Didier Google Talk : didier.misson(a)gmail.com Jabber : didier.misson(a)amessage.be http://didier.misson.net

2 2

Re: [Dovecot] dovecot.conf authentication after Debian upgrade
by Didier Misson 25 Jun '07

25 Jun '07

Bruno Puga a écrit : > but you can send us more detailed information changing this settings in > your dovecot's conf: > http://wiki.dovecot.org/Debugging/Authentication > > See this section to find out if you are looking for logs in the right > place accordingly to you configuration. > http://wiki.dovecot.org/Logging <http://wiki.dovecot.org/Logging> > > Send us the dovecot -n output instead of dovecot.conf. I read this documentation about Authentication and Logging debuggind. I add : auth_debug=yes auth_debug_passwords=yes --------------------------- for this test, I change my password = "MyPasswd" (and I change again after) My client is Thunderbird on Ubuntu 7.04 in /var/log/syslog dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=IMAP^Isecured^Ilip=87.98.98.98^Irip=212.71.11.157 dovecot: auth(default): client out: CONT^I1^I dovecot: auth(default): client in: CONT^I1^IAGRpZGllcgBNeVBhc3N3ZA== dovecot: auth(default): passwd(didier,212.71.11.157): password mismatch dovecot: auth(default): client out: FAIL^I1^Iuser=didier I try to check myself : printf 'didier\didier\MyPasswd' | mmencode ZGlkaWVyXGRpZGllclxNeVBhc3N3ZA== The end seem to be the same... Is it correct ? So why Dovecot don't accept my password ? Dovecot or Debian ? ... I don't know what I can check more... Thanks ;-) -- Didier Google Talk : didier.misson(a)gmail.com Jabber : didier.misson(a)amessage.be http://www.misson.net

1 0

[Dovecot] Setting retention policies
by Don Russell 25 Jun '07

25 Jun '07

I access e-mail from different PCs, typically using Thunderbird e-mail client. Thunderbird has a a "retention policy" it can set on a folder by folder basis. Policies such as how long to keep messages for, or how many messages to keep. Is there a way to set those policies on the server itself? Thank you

4 6

[Dovecot] Quota from passdb sql
by Bruno Puga 25 Jun '07

25 Jun '07

Hello folks! Is it possible to retrieve quota information from a passdb sql lookup and using static userdb? I've tried here without success, and I can't find in the wiki or forum. Some ways I configured dovecot-sql.conf: 1) password_query = SELECT email AS user, CONCAT('maildir:storage=',quota) AS quota, password FROM users WHERE email = '%u' 2) password_query = SELECT email AS user, CONCAT('maildir:storage=',quota) AS userdb_quota, password FROM users WHERE email = '%u' With userdb sql things worked perfect, but as I can use static userdb I just need quota information per user from passwd sql. Thanks, Bruno.

2 2

[Dovecot] quota calculating
by Scott Zahn 25 Jun '07

25 Jun '07

Hey everyone, Currently where I work we use qmail. Every time a message is delivered, qmail seems to walk through the user's entire maildir in order to calculate quota usage. Delivering messages simultaneously to just a few users who are allowed large maildirs (1-2GB) will bring our servers to their knees. Which brings me to dovecot. I use dovecot whereever I can, but haven't yet needed to set up quotas. I would like to migrate my servers at work to use dovecot, but have a few questions regarding quotas. Could someone explain how dovecot calculates quota usage on mail delivery? Also, is there anyone here on the list that uses quoatas on large maildirs (>=2GB)? How well has it worked for you? thanks, Scott

3 3

[Dovecot] LIST % not returning correct data?
by J.Wendland＠scan-plus.de 25 Jun '07

25 Jun '07

Hi list, I have namespace private { prefix = INBOX. separator = . inbox = yes } in an installation migrated from courier. I am testing with Outlook Mobile 5 (OM) which uses 'LIST "" %' to get the folder list. Now courier used to return * LIST (\HasChildren) "." "INBOX" whereas dovecot returns * LIST (\HasNoChildren) "." "INBOX" which is why OM failes to display any folder. Is this dovecot's failure or am I missing something here? Thanks, Jörg -- Sicherheit - Verfügbarkeit - Kontinuität ------------------------------------------------------------------------- IT-Service-Management von ScanPlus GmbH Tel. +49 731 92013 150 Lise-Meitner-Straße 5, D-89081 Ulm, Germany Fax. +49 731 92013 29 150 Web: http://www.scan-plus.de/ Mail: wendland(a)scan-plus.de -------------------------------------------------------------------------

4 4

[Dovecot] dovecot.conf authentication after Debian upgrade
by Didier Misson 25 Jun '07

25 Jun '07

Hello, I'm new on this mailing list. I run a Dovecot imaps server since several month on a Debian server. I just upgrade a Debian server from Debian Sarge --> Etch and I discover that a lot of parameters have changed (must be changed) in the dovecot.conf. I finally find an exemple an try to adapt it to our server. We never defined special authentification or password scheme. It was simple the "passwd". Dovecot is running, but impossible for users to connect :-( Actually, this is my dovecot.conf : ====================================== base_dir = /var/run/dovecot/ protocols = imap imaps protocol imap { listen = 127.0.0.1:143 ssl_listen = *:993 } # protocol pop3 { # # listen = *:110 # # ssl_listen = *:995 # # } ssl_disable = no ssl_cert_file = /etc/ssl/certs/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " login_dir = /var/run/dovecot/login #login_dir = /var/log/dovecot login_chroot = yes login_user = dovecot login_process_per_connection = yes login_greeting = Dovecot ready. first_valid_uid = 1000 last_valid_uid = 0 first_valid_gid = 1 last_valid_gid = 0 mail_extra_groups = mail # #default_mail_env = mbox:/var/mail/%u default_mail_env = maildir:~/Maildir protocol imap { imap_client_workarounds = outlook-idle delay-newmail netscape-eoh tb-extra-mailbox-sep } # # protocol pop3 { # # } auth default { mechanisms = plain ##### Didier Misson : must be check !!! #passdb passwd-file { #args = /etc/dovecot/pass #} #passdb pam { passdb passwd { } #userdb passwd-file { #args = /etc/dovecot/users #} userdb passwd { } user = root } plugin { } ===================================================================== in /var/log/syslog Jun 25 11:14:02 ks36586 dovecot: Dovecot v1.0.rc15 starting up Jun 25 11:14:53 ks36586 dovecot: imap-login: Aborted login: user=<sebastien-descy>, method=PLAIN, rip=62.235.215.24, lip=87.98.219.84, TLS Jun 25 11:14:59 ks36586 dovecot: imap-login: Aborted login: user=<dominique>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jun 25 11:15:01 ks36586 /USR/SBIN/CRON[16295]: (root) CMD (/usr/local/rtm/bin/rtm 41 >/dev/null 2>/dev/null) I hope somebody already solved this king of problem. Thanks a lot. ;-) -- Didier http://didier.misson.net

1 0

[Dovecot] Authors wanted for Linux Magazine
by Markus Feilner 25 Jun '07

25 Jun '07

Hello list, as an editor at the german linux magazine I am looking for an author who would like to write about 5-6 pages on dovecot clustering (as a workshop or presenting a detail of special interest) If you are interested, please send me an email to: <mfeilner(a)linuxnewmedia.de> Mit freundlichen Gruessen - Best Regards, Markus Feilner -- Linux New Media AG, Sueskindstr. 4, 81929 Muenchen, Germany Phone: +49 89 9934 1122, Fax: +49 89 9934 1199 mfeilner(a)linuxnewmedia.de - http://www.linuxnewmedia.de Linux New Media - The Pulse of Linux Lawrence - Malaga - Manchester - Muenchen - Sao Paulo - Timisoara - Warszawa --------------------------------------------------- Sitz der Gesellschaft: Sueskindstrasse 4, 81929 Muenchen Amtsgericht Muenchen: HRB 129161 Vorstand: Rosemarie Schuster, Hermann Plank Aufsichtsratsvorsitzender: Rudolf Strobl

1 0

[Dovecot] Dovecot and Sendmail Working Together . . .
by Eddie Johnson Jr 24 Jun '07

24 Jun '07

I am new to this, I was just given the responsibility Thursday to get Sendmail/SquirrelMail/Dovecot to work in sync. How do I start? iloadmin

2 1

Re: [Dovecot] Dovecot won't stay running
by Gunter Ohrner 22 Jun '07

22 Jun '07

Am Freitag, 22. Juni 2007 schrieb Jon Slater: > You are AWESOME!!! Thank you!!! Mh, I think this is one of the few times I read that someone was actually greatful for a "RTFM" he got... ;) > Jun 22 01:27:56 servername dovecot: Time just moved backwards by 37 > seconds. This might cause a lot of problems, so I'll just kill myself That's bad and may cause a lot of other (and more subtle) troubles than Dovecot committing suicide. I'f your' using something like "ntpdate" to periodically step the time, do not do that but run an ntp server instead which will gradually skew the clock to keep the system's time accurate. Greetings, Gunter -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ I would actually distinguish between problems with compiling the kernel, and problems with the kernel after compiling. -- Karol 'sziwan' Kozimor auf der swsusp-Mailingliste +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + PGP-verschlüsselte Mails bevorzugt! + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

1 0

Re: [Dovecot] test program #2: mmaping
by Bill Boebel 22 Jun '07

22 Jun '07

On Wed, June 20, 2007 9:28 pm, Timo Sirainen <tss(a)iki.fi> said: > Attached another test program. I don't expect it to print any errors > with any OS, but I'd like to confirm it for non-Linux SMP kernels. # ./concurrency writing, page size = 4096 4: reading, page size = 4096 3: reading, page size = 4096 2: reading, page size = 4096 1: reading, page size = 4096 0: reading, page size = 4096 Red Hat ES3 (2.4.21-32.0.1.EL) athlon i386

1 0

Re: [Dovecot] Dovecot won't stay running
by Jochen Schulz 22 Jun '07

22 Jun '07

Jon Slater schrieb: > > So I got the same suggestion several times, and I upgraded to Dovecot 1.0.1. > > At 1:27am and again at 5:23am Dovecot stopped running. My cron was able to > restart the service in both instances, but how do I debug why this is > happening? Take a look at http://wiki.dovecot.org. It contains useful instructions for debugging. J.

2 1

Re: [Dovecot] Dovecot won't stay running
by Jon Slater 22 Jun '07

22 Jun '07

So I got the same suggestion several times, and I upgraded to Dovecot 1.0.1. At 1:27am and again at 5:23am Dovecot stopped running. My cron was able to restart the service in both instances, but how do I debug why this is happening? Thanks!!! Jon > -----Original Message----- > From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] > On Behalf Of Jon Slater > Sent: Thursday, June 21, 2007 5:19 PM > To: dovecot(a)dovecot.org > Subject: [Dovecot] Dovecot won't stay running > > This weekend I upgraded my OS from FC4 to FC6. At the same time I > updated > Dovecot from 0.99 to 1.0.0. > > Now, dovecot periodically shuts off. > > It will run fine for several hours then just dies. > > Right now my solution is to run a cron every 5 minutes to see if it’s > still > running, and if not, re-start it. > > I’m also having trouble finding any sort of meaningful logs to tell me > what’s going on. > > Where should I start? > > Thanks in advance! > > Jon > > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.9.2/858 - Release Date: > 6/21/2007 > 1:46 PM > > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.9.2/858 - Release Date: > 6/21/2007 1:46 PM > No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.9.4/860 - Release Date: 6/21/2007 5:53 PM

1 0

[Dovecot] Dovecot won't stay running
by Jon Slater 22 Jun '07

22 Jun '07

This weekend I upgraded my OS from FC4 to FC6. At the same time I updated Dovecot from 0.99 to 1.0.0. Now, dovecot periodically shuts off. It will run fine for several hours then just dies. Right now my solution is to run a cron every 5 minutes to see if it’s still running, and if not, re-start it. I’m also having trouble finding any sort of meaningful logs to tell me what’s going on. Where should I start? Thanks in advance! Jon No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.9.2/858 - Release Date: 6/21/2007 1:46 PM

1 0

Re: [Dovecot] Fwd: LDAP subtree search on AD
by Bruno Puga 22 Jun '07

22 Jun '07

Timo, I have sent this message below before but I didn't saw that it was delivered to you personal email instead to the list, I just see this now, sorry. Because I'm in a hurry I gave up using Dovecot + AD and start using Mysql as my userdb and passdb and things worked perfect until the moment. I have some doubts but I will open a new thread for this. Anyway, if you get some news about this issue I would appreciate to know, if not, that's OK. Many thanks for your help. Bruno. On 6/18/07, Bruno Puga <brpuga(a)gmail.com> wrote: > > Timo, I had set this in the dovecot.conf: > > auth_verbose = yes > auth_debug = yes > auth_debug_passwords = yes > > ########################################################### > ### My dovecot logs shows this using auth_bind = yes and userdn template > ### > > dovecot: 2007-06-17 12:35:52 Warning: Killed with signal 15 > dovecot: 2007-06-17 12:35:53 Info: Dovecot v1.0.0 starting up > dovecot: 2007-06-17 12:37:23 Info: auth(default): client in: AUTH > 1 PLAIN service=IMAP secured lip= 192.168.0.251 rip=192.168.0.251 > resp=AHRlc3RlAHRlc3Rl > dovecot: 2007-06-17 12:37:23 Info: auth(default): ldap(teste,192.168.0.251): > bind: dn=teste > dovecot: 2007-06-17 12:37:23 Info: auth(default): client out: OK > 1 user=teste > dovecot: 2007-06-17 12:37:23 Info: auth(default): master in: REQUEST > 1 31290 1 > dovecot: 2007-06-17 12:37:23 Info: auth(default): ldap(teste,192.168.0.251): > user search: base=DC=tecnicopias01,DC=com,DC=br scope=subtree > filter=(&(objectClass=organizationalPerson)(sAMAccountName=teste)) > fields=info > dovecot: 2007-06-17 12:40:23 Info: imap-login: Disconnected: Inactivity: > user=<teste>, method=PLAIN, rip=192.168.0.251 , lip=192.168.0.251, secured > > dovecot: 2007-06-17 12:52:46 Error: auth(default): ldap(teste, > 192.168.0.251): ldap_search() failed: Operations error > dovecot: 2007-06-17 12:52:46 Info: auth(default): master out: FAIL 1 > dovecot: 2007-06-17 12:52:46 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > dovecot: 2007-06-17 13:07:46 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > dovecot: 2007-06-17 13:22:47 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > > As we can see, first dovecot bind correct, but after it open a new > connection as showed in the ngrep output, and without bind try to make the > ldap_search, in that point AD blocks the search saying that for the new > connection opened is necessary a successful bind. > ########################################################### > > ### Now, changing for User database Lookups authenticating with krb5 ### > > dovecot: 2007-06-18 10:14:35 Info: auth(default): client in: AUTH > 1 PLAIN service=IMAP secured lip=192.168.0.251 rip= > 192.168.0.251 resp=AHRlc3RlAHRlc3Rl > dovecot: 2007-06-18 10:14:35 Info: auth(default): pam(teste,192.168.0.251): > lookup service=dovecot > dovecot: 2007-06-18 10:14:35 Info: auth(default): client out: OK > 1 user=teste > dovecot: 2007-06-18 10:14:35 Info: auth(default): master in: REQUEST > 1 32029 1 > dovecot: 2007-06-18 10:14:35 Info: auth(default): ldap(teste,192.168.0.251): > user search: base=DC=tecnicopias01,DC=com,DC=br scope=subtree > filter=(&(objectClass=organizationalPerson)(sAMAccountName=teste)) > fields=info > dovecot: 2007-06-18 10:17:35 Info: imap-login: Disconnected: Inactivity: > user=<teste>, method=PLAIN, rip=192.168.0.251 , lip=192.168.0.251, secured > > dovecot: 2007-06-18 10:29:25 Error: auth(default): ldap(teste, > 192.168.0.251): ldap_search() failed: Operations error > dovecot: 2007-06-18 10:29:25 Info: auth(default): master out: FAIL 1 > dovecot: 2007-06-18 10:29:25 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > dovecot: 2007-06-18 10:44:26 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > dovecot: 2007-06-18 10:59:26 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > > ########################################################### > > After some time, the dovecot logs starts logging this last 3 lines saying > it "Can't contact LDAP server", and ngrep shows this: > > ########################################################### > ############# > T 192.168.0.251:49043 -> 192.168.0.11:389 [AP] > 0E...`@....1CN=postfix,CN=Users,DC=tecnicopias01,DC=com,DC=br..post123! > # > T 192.168.0.11:389 -> 192.168.0.251:49043 [AP] > 0........a............ > ### > T 192.168.0.251:49043 -> 192.168.0.11:389 [AP] > 0....B. > ####### > T 192.168.0.251:42083 -> 192.168.0.11:389 [AP] > 0E...`@....1CN=postfix,CN=Users,DC=tecnicopias01,DC=com,DC=br..post123! > # > T 192.168.0.11:389 -> 192.168.0.251:42083 [AP] > 0........a............ > ### > T 192.168.0.251:42083 -> 192.168.0.11:389 [AP] > 0....B. > ####### > T 192.168.0.251:52084 -> 192.168.0.11:389 [AP] > 0E...`@....1CN=postfix,CN=Users,DC=tecnicopias01,DC=com,DC=br..post123! > # > T 192.168.0.11:389 -> 192.168.0.251:52084 [AP] > 0........a............ > # > > Dovecot after a while keep trying to connect to LDAP server without any > requests being sent to server. So it keep logging this line below forever: > > LDAP: ldap_result() failed: Can't contact LDAP server > ########################################################### > > If I change the base to the same location as the user being authenticating > is, the userdb lookup is successfully because he's find at a first > ldap_seach try, and no subtree search is necessary. So again I think dovecot > must not open other connections then that opened at the bind time to make > the subtree search, like postfix do. > > Timo, I'm waiting for your reply. > > Thanks in advance to spent your time to contribute with free software, > Bruno.

1 0

[Dovecot] test program #2: mmaping
by Timo Sirainen 21 Jun '07

21 Jun '07

Attached another test program. I don't expect it to print any errors with any OS, but I'd like to confirm it for non-Linux SMP kernels. (Except for OpenBSD, it doesn't work correctly in it anyway because it doesn't support mixing write()s and mmap())

8 8

[Dovecot] Status update
by Timo Sirainen 21 Jun '07

21 Jun '07

I'm leaving soon and I'll be away until sunday. Sorry about not replying to all mails yet, most of them are somewhat tricky and require some time to reply (other than "I don't know"). The new index code for v1.1 seems to be finally working pretty nicely. After 9 hours of running imaptest I haven't gotten a single error yet. I'll leave it running until I'm back. The new code makes the internal index file design a lot easier to understand. For v1.0 I just wanted to get it working and I didn't dare try to clean up the code, so it was kind of magic sometimes why it worked. :) All that magic is finally gone and I understand completely how everything is supposed to work (and hopefully also how it does work). Most important problem with the new code is that \Recent flags are completely broken. I think they're not completely correctly working in v1.0 either, or at least I'm not sure why they're working even as well as they are now.. Maildir syncing in v1.1 is also a bit bad. For example EXPUNGE command could have to be given twice to get it to work. Again it worked badly with v1.0 also but since the index code worked differently it wasn't visible. Cydir is a pretty nice format for stress testing index code. It's really lightweight so it's practically testing only the index code. Because of it I've found a couple of race conditions in the code that existed also in v1.0 tree (v1.0.2 will fix them). My earlier stress testing with maildir never saw those problems, probably because with maildir there was a lot of other code running as well so the race condition was really unlikely to hit.

1 0

[Dovecot] pop3 creates bad index file
by Onno Molenkamp 21 Jun '07

21 Jun '07

Hi, When I use pop3 to log on to a (Maildir) mailbox that doesn't yet exist in the filesystem, the pop3 server autocreates it for me. This works. Jun 21 10:50:45 mail-04 dovecot: pop3-login: Login: user=<hwx7s(a)gqh7x.test>, method=PLAIN, rip=::ffff:192.168.42.105, lip=::ffff:192.168.42.97 Jun 21 10:50:48 mail-04 dovecot: POP3(hwx7s(a)gqh7x.test): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 When I log on a second time, it will complain about UIDVALIDITY that has changed, and will disconnect me: Jun 21 10:50:52 mail-04 dovecot: pop3-login: Login: user=<hwx7s(a)gqh7x.test>, method=PLAIN, rip=::ffff:192.168.42.105, lip=::ffff:192.168.42.97 Jun 21 10:50:52 mail-04 dovecot: POP3(hwx7s(a)gqh7x.test): Maildir /data/mail/898/gqh7x.test/hwx7s/Maildir sync: UIDVALIDITY changed (1182415845 -> 1182415852) Jun 21 10:50:52 mail-04 dovecot: POP3(hwx7s(a)gqh7x.test): Disconnected: Mailbox is in inconsistent state. top=0/0, retr=0/0, del=0/0, size=0 Jun 21 10:50:52 mail-04 dovecot: POP3(hwx7s(a)gqh7x.test): Couldn't init INBOX: Internal error occurred. Refer to server log for more information. [2007-06-21 10:50:52] When I log on a third time, everything seems to work from the client side, but the server still complains: Jun 21 10:51:01 mail-04 dovecot: pop3-login: Login: user=<hwx7s(a)gqh7x.test>, method=PLAIN, rip=::ffff:192.168.42.105, lip=::ffff:192.168.42.97 Jun 21 10:51:01 mail-04 dovecot: POP3(hwx7s(a)gqh7x.test): Corrupted index cache file /data/mail/898/gqh7x.test/hwx7s/Maildir/dovecot.index.cache: indexid changed Jun 21 10:51:02 mail-04 dovecot: POP3(hwx7s(a)gqh7x.test): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Fourth (and further) logons work without errors. When the Maildir is created by imap or deliver, pop3 works fine from the start. The only real difference I see with idxview between the dovecot.index created by pop3 and one created by imap is that with pop3 sync stamp is 0, and with imap it contains a timestamp. Onno

2 1

[Dovecot] mail_log plugin updates
by Timo Sirainen 21 Jun '07

21 Jun '07

It supports configuration now in devel version: # Events to log. Default is all. #mail_log_events = delete undelete expunge copy mailbox_delete # Group events within a transaction to one line. #mail_log_group_events = # Available fields: uid, box, msgid, size, vsize # size and vsize are available only for expunge and copy events. #mail_log_fields = uid box msgid size Without grouping you get pretty similar output than before: Info: copy: uid=13, dest=Trash, msgid=<20040702035043.7296C300DFC1A@asdf>, size=789 Info: delete: uid=13, msgid=<20040702035043.7296C300DFC1A@asdf> Info: expunge: uid=13, msgid=<20040702035043.7296C300DFC1A@asdf>, size=789 With mail_log_group_events=yes you get output like this: Info: copy: uids=15-17,24,26, dest=Trash, size=1534 Info: delete: uids=15-17,24,26 Info: expunge: uids=15-17,24,26, size=1534 The size is the summed size of all the messages. msgids aren't suppported. "size" means physical message size, "vsize" means the virtual size with CR+LF linefeeds. Does someone want something more?

2 2

[Dovecot] Question about pre-indexing maildirs
by David Favor 21 Jun '07

21 Jun '07

I have a situation with many users and an existing mail delivery agent. Seems like I once saw an imaptest program which I imagine might be used to pre-index maildirs. For example... - remember which users and user maildirs have changed since last pre-index - when system quiet pre-index any maildirs which have had mail delivered and no access by a mail client (using some inotify magic) If this sounds do-able, let me know where I can find an imaptest version which works with latest dovecot trunk code and the syntax for using it. Seems like I saw this once on the dovecot site. Thanks. - David -- Like feeling your best ever, all day, every day? Here's how... Your simple secrets are here - http://RadicalHealth.com

2 1

[Dovecot] how do I download concurrency.c
by Stewart Dean 20 Jun '07

20 Jun '07

When I click on the link I get not found on the server. I run on a 4 way and AIX has some pretty fancy concurrency so it would be interesting. But then I'm leaving this afternoon and won't be back until Monday..... -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

[Dovecot] testing needed: log file concurrency
by Timo Sirainen 20 Jun '07

20 Jun '07

http://dovecot.org/tmp/concurrency.c I'd want to know what results this program gives with different systems. Please test and reply (but don't bother if someone already replied with the same OS+result). I expect it to print: - SMP kernels: "page size cut" once in a while - UP (uniprocessor) kernels: Nothing - The most important thing is that it never prints "broken data" It might take a while for it to print anything. With my computer it takes anything from a few seconds to a minute or so. See the file itself for compiling/running instructions. So far I've tested only with Linux 2.6.21 x86-64/SMP and a slow Solaris/Sparc/UP. If you're interested in knowing what this is about: Dovecot writes to dovecot.index.log files by first writing the transaction with its size being 0. After that it writes the 4 size bytes again (using a bit special format with all bytes ORed with 0x80). I expected that when another process is read()ing the file and it notices the size being valid (all bytes having 0x80) that the whole transaction could always be read. But looks like if the size happens to be just before a memory page boundary, it's possible that the updated size is read, but the rest of the transaction isn't.

13 18

[Dovecot] (OT) Advice on best way to collect mail from multiple domains and deliver to users via Dovecot IMAP.
by Dave Hatton 20 Jun '07

20 Jun '07

Hi Sorry if this is an inappropriate question to ask here. If it is maybe there is a better place to ask this question? I would like to collect email sent to multiple users (with previously unknown usernames) sent to multiple domains and then deliver this email to a specific set of users on my server based upon some predefined rules, with a catchall for mails that aren't caught by these rules. So as an example, I might have domains:- example.com, example.co.uk, someotherdomain.com and I'd like to say to a sender "just send a mail to anything(a)example.com". I'd like to be able to make up recipients on the fly when subscribing to a service so that I can filter mails to this address out at a later time. The method I devised when I set this up using dovecot .99 is as follows. I currently have the hosting service for the domains forwarding all email to a singular mailbox at my ISP and I user fetchmail to pop3 the mail down from this one mailbox. The mail is then passed to postfix where I use the luser_relay option to map all unknown recipients to a local address so that it doesn't get bounced. Postfix then delivers the mail via the mailbox_command to maildrop where a series of rules inspect the envelope headers and write the mail using the "to" option to an appropriate maildir for the target user. Is this a good approach? Would I be better off using dovecot LDA and sieve? Any advice or ideas would be gratefully received. Daveh

1 0

Re: [Dovecot] testing needed: log file concurrency
by Bill Boebel 20 Jun '07

20 Jun '07

On Tue, June 19, 2007 7:41 pm, Timo Sirainen <tss(a)iki.fi> said: > http://dovecot.org/tmp/concurrency.c > > I'd want to know what results this program gives with different systems. > Please test and reply (but don't bother if someone already replied with > the same OS+result). I expect it to print: ./concurrency writing, page size = 4096 ./concurrency 1 reading, page size = 4096 Red Hat ES3 (2.4.21-32.0.1.EL) athlon i386

1 0

[Dovecot] Error: net_connect(/opt/local/var/run/dovecot/auth-master) failed: No such file or directory
by J Charles Ferrari 20 Jun '07

20 Jun '07

What is auth-master, and how do I create it? Using postfix 2.1.5 dovecot 1.0.0 # /opt/local/etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot_error.log info_log_path: /var/log/dovecot.log protocols: imap pop3 ssl_disable: yes login_dir: /var/run/dovecot/login login_executable(default): /opt/local/libexec/dovecot/imap-login login_executable(imap): /opt/local/libexec/dovecot/imap-login login_executable(pop3): /opt/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: maildir:/var/Maildir/%u mail_debug: yes mail_executable(default): /opt/local/libexec/dovecot/imap mail_executable(imap): /opt/local/libexec/dovecot/imap mail_executable(pop3): /opt/local/libexec/dovecot/pop3 mail_plugin_dir(default): /opt/local/lib/dovecot/imap mail_plugin_dir(imap): /opt/local/lib/dovecot/imap mail_plugin_dir(pop3): /opt/local/lib/dovecot/pop3 auth default: verbose: yes debug: yes passdb: driver: pam userdb: driver: passwd socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: mail Thanks Charles

4 3

Re: [Dovecot] dovecot Digest, Vol 50, Issue 54
by Kenny Dail 20 Jun '07

20 Jun '07

> - SMP kernels: "page size cut" once in a while does several hundred in about 4 minutes count as once in a while? Got many "page size cut" on 2.6.17-gentoo-r8 #2 SMP i686 Dual Pentium III (Katmai) no output from a FreeBSD 4.9-RELEASE-p5 single Pentium III (Katmai) -- Kenny Dail <kend(a)amigo.net>

1 0

[Dovecot] save failed to INBOX
by Erland Nylend 19 Jun '07

19 Jun '07

Hello, I'm seeing som error messages in the mail log, like this: Jun 12 12:50:44 <mail.info> smtp2 deliver(user1(a)domain.tld): msgid=<10784847.1181644475592.foo.bar@foo99>: save failed to INBOX Jun 12 12:50:44 <mail.info> smtp2 deliver(user1(a)domain.tld): msgid=<30757588.1181644556388.foo.bar@foo99>: saved mail to INBOX It seems that when two or more messages are being delivered at the same time, only one delivery succeeds. Both the maildirs and the indexes are stored on a SAN .. I'll try to read the source, to find out whether this is a locking problem. I would think that if a deliver -process finds that a maildir is locked, then it should wait, and retry? -- Erland Nylend

3 41

[Dovecot] Odd error from deliver
by Ralf Hildebrandt 19 Jun '07

19 Jun '07

I found these errors in my log today: Jun 18 01:02:11 postamt deliver(cpxxxsch): msgid=<FSL%200706180000356580.6412(a)JISCMAIL.AC.UK>: save failed to INBOX: Unknown error Jun 18 01:02:11 postamt deliver(cpxxxsch): msgid=<FSL%200706180000356580.6412(a)JISCMAIL.AC.UK>: Rejected: Unknown error Jun 18 15:37:22 postamt deliver(roxxxmy): msgid=<E1I0HPz-0002OZ-00(a)p15110889.pureserver.info>: save failed to INBOX: Unknown error Jun 18 15:37:22 postamt deliver(roxxxmy): msgid=<E1I0HPz-0002OZ-00(a)p15110889.pureserver.info>: Rejected: Unknown error This is deliver from dovecot-1.0.1 What exactly IS "Unknown error"? -- 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 Ballmer should step down in favour of Mr T, because he pity the fool who don't got high-end video cards and 4GB RAM for Vista Aero!

3 12

[Dovecot] parameters to deliver
by Bruce Bodger 19 Jun '07

19 Jun '07

Read this in the dovecot sieve wiki: "The envelope sender is taken from a Return-Path: header in the message. The envelope recipient is taken from -d option passed to deliver." Is "-d" still a valid deliver switch? When I configure postfix's main.cf like so... mailbox_command = /usr/local/libexec/dovecot/deliver -d -e ..it sqwaks with, "Jun 18 18:44:50 G518X2 deliver(-e): net_connect(/ usr/local/var/run/dovecot/auth-master) failed: No such file or directory" when configured like so... mailbox_command = /usr/local/libexec/ dovecot/deliver -e -d ${recipient} ..it burps with, "Jun 18 18:56:40 G518X2 postfix/local[19766]: 3BBC16C96E0: to=<me(a)mydomain.com>, relay=local, delay=0, status=bounced (command line usage error. Command output: Fatal: Missing destination argument )" It doesn't like... mailbox_command = /usr/local/libexec/dovecot/ deliver -e -d "$recipient" either! Is -d required any longer... and if so, how, please. B. Bodger

3 4

[Dovecot] Problem with deliver
by David Favor 19 Jun '07

19 Jun '07

Per the wiki page: http://wiki.dovecot.org/LDA Doing the following should create a Maildir directory structure in an arbitrary directory, deposit a message and create/update any dovecot indexes: mkdir /common/foo export HOME=/common/foo export PATH=/usr/libexec/dovecot:$PATH cat 1180102308.88215.4145.davidfavor.com:2,RS | deliver -f doda(a)foobar.com This gives an error "(-d user) not given" and when '-d user' given an exit code of 75 is silently returned. Let me know the correct way to test how the deliver program works. Thanks. - David -- Like feeling your best ever, all day, every day? Here's how... Your simple secrets are here - http://RadicalHealth.com

2 1

[Dovecot] Outlook 2003 - Disappearing favorite folders
by Phillip T. George 18 Jun '07

18 Jun '07

Hello all, I'm having an issue with Outlook 2003, where favorite folders seem to disappear. Specifically, they are subfolders of the Inbox. The Inbox favorite folder stays there without a problem. Any clues as to what the problem may be? With the previous IMAP server (courier I believe) this wasn't a problem...so it leads me to believe that Dovecot might be the problem. I'm working with Dovecot 1.0.rc28 Thanks, Phillip

5 10

[Dovecot] v1.0.1 released
by Timo Sirainen 17 Jun '07

17 Jun '07

http://dovecot.org/releases/dovecot-1.0.1.tar.gz http://dovecot.org/releases/dovecot-1.0.1.tar.gz.sig Lots of small fixes. * deliver: If Return-Path doesn't contain user and domain, don't try to bounce the mail (this is how it was supposed to work earlier too) * deliver: %variables in mail setting coming from userdb aren't expanded anymore (again how it should have worked). The expansion could have caused problems if paths contained any '%' characters. + Print Dovecot version number with dovecot -n and -a + deliver: Added -e parameter to write rejection error to stderr and exit with EX_NOPERM instead of sending the rejection by executing sendmail. + dovecot --log-error logs now a warning, an error and a fatal - Trying to start Dovecot while it's already running doesn't anymore wipe out login_dir and break the running Dovecot. - maildir: Fixed "UID larger than next_uid" errors which happened sometimes when dovecot-uidlist file didn't exist but index files did (usually because mailbox didn't have any messages when it was selected for the first time) - maildir: We violated maildir spec a bit by not having keyword characters sorted in the filename. - maildir: If we don't have write access to cur/ directory, treat the mailbox as read-only. This fixes some internal error problems with trying to use read-only maildirs. - maildir: Deleting a symlinked maildir failed with internal error. - mbox: pop3_uidl_format=%m wasn't working right - mbox: If non-filesystem quota was enabled, we could have failed with "Unexpectedly lost From-line" errors while saving new messages - mysql auth: %c didn't work. Patch by Andrey Panin - APPEND / SEARCH: If internaldate was outside valid value for time_t, we returned BAD error for APPEND and SEARCH never matched. With 64bit systems this shouldn't have happened. With 32bit systems the valid range is usually for years 1902..2037. - COPY: We sent "Hang in there.." too early sometimes and checked it too often (didn't break anything, but was slower than needed). - deliver: Postfix's sendmail binary wasn't working with mail_debug=yes - Don't corrupt ssl-parameters.dat files when running multiple Dovecot instances. - Cache compression caused dovecot.index.cache to be completely deleted with big endian CPUs if 64bit file offsets were used (default) - Fixed "(index_mail_parse_header): assertion failed" crash

5 6

Re: [Dovecot] index
by Timo Sirainen 17 Jun '07

17 Jun '07

(Ccing again the list in case someone else has similar problems) On Sun, 2007-06-17 at 20:14 +0200, Lucas -LandM- wrote: > Hi Timo, > > I patched the source and same result. We think the problem is because > everytime user access to his mailbox, dovecot do the index again. And it > consume near the 80% in iowait because, as strace shows, read all mails. The problem isn't that Dovecot indexes it. The problem is that Dovecot ISN'T indexing it. Dovecot commits changes to cache file only after a FETCH command finished successfully. So if the client is disconnected in the middle of doing the FETCH, all of the work that Dovecot did so far gets lost on Dovecot's side. And apparently your client also starts everything from the beginning, even though it already knew some of the messages' sizes.. So the previous patch I sent was supposed to prevent this because originally Dovecot was the one that disconnected the client. It logged "Disconnected for inactivity in reading our output" as the disconnect reason. This shouldn't happen anymore after you patched it, so why did the client still get disconnected? Anyway, here's another patch that makes Dovecot not forget all of its work if the client gets disconnected in the middle of FETCH: http://hg.dovecot.org/dovecot-1.0/rev/e1cd11c5e00a If the client is still disconnecting, it probably takes a couple of tries to get everything read and cached, but after that it should all work nicely. Here's a similar patch for POP3: http://hg.dovecot.org/dovecot-1.0/rev/86766f448e50

1 0

[Dovecot] subdir disappeared
by Luigi Rosa 17 Jun '07

17 Jun '07

I have an installation that sometimes acts strangely: Jun 12 11:28:00 mail dovecot: imap-login: Login: user=<nadia>, method=PLAIN, rip=10.10.10.103, lip=10.10.10.254 Jun 12 11:53:59 mail dovecot: IMAP(nadia): inotify_add_watch(/var/spool/mail/nadia/new) failed: No such file or directory Jun 12 11:53:59 mail dovecot: IMAP(nadia): stat(/var/spool/mail/nadia/new) failed: No such file or directory Jun 12 11:56:14 mail last message repeated 5 times Jun 12 11:58:14 mail last message repeated 2 times Jun 12 12:00:14 mail last message repeated 2 times Jun 12 12:02:14 mail last message repeated 2 times Jun 12 12:02:14 mail dovecot: IMAP(nadia): stat(/var/spool/mail/nadia/new) failed: No such file or directory Jun 12 12:03:23 mail dovecot: IMAP(nadia): Disconnected: Logged out ..... Jun 13 12:08:01 mail dovecot: IMAP(nadia): unlink(/var/spool/mail/nadia/cur/:2,ST) failed: Is a directory Needless to say that no modification has been made to the server for many days and the user did not complain until that time. Could it be Dovecot? Is there a way to trace this error? The MTS is Postfix and in that period the user did not receive any mail The system is a Fedora 6 2.6.20-1.2952.fc6 #1 SMP Wed May 16 17:59:13 EDT 2007 i686 i686 i386 GNU/Linux Ciao, luigi -- / +--[Luigi Rosa]-- \ You cannot achieve the impossible without attempting the absurd.

2 4

[Dovecot] 60 seconds problem
by Waheed Rahuman 17 Jun '07

17 Jun '07

I am using Dovecot-1.0-0_27.rc10.e14. And when try to login with outlook there is an error saying "You server did not respond do u want to try again in 60 seconds" Any solutions please help regards Waheed

2 1

Re: [Dovecot] Per user based protocol access and pause after failed login?
by Mart Pirita 17 Jun '07

17 Jun '07

Tere. > %c expands to "secured" or empty. So you could use eg. > passdb pam { > args = %s%c > } > > and create imap, imapsecured, pop3, pop3secured > > More better, so for example user1 can access only imaps, using Yous suggestion, I have to list all users, except user1 in imap, pop3, pop3secured. But it should works also in other way, that by default all users are allowed to use all protocols and then I exclude user1 from imap, pop3, pop3secured. So I tried: passdb pam { args = %s%c } /etc/pam.d/ includes imap, imapsecured, pop3, pop3secured files which includes: auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth session required pam_stack.so service=system-auth and only imapsecured has this line: auth required pam_listfile.so item=user sense=deny file=/etc/imapsusers onerr=succeed and /etc/imapsusers includes user1 But now even pop user can't login:(. -- Mart

2 1

[Dovecot] using 'socat' to relay Dovecot SASL's auth socket over TCP?
by snowcrash 17 Jun '07

17 Jun '07

hi, i've been running Exim & Dovecot together on the same box. Exim's been sharing Dovecot/SASL auth info over a local unix socket. works great. i'm now splitting Exim & Dovecot onto two different boxes. iiuc, Dovecot ONLY provides a UNIX (local) socket; *not* a TCP socket for over-the-network access. SUre, I could mount the Dovecot socket's volume over NFS ... but just don't want to go there. i've just discovered, socat - Multipurpose relay http://www.dest-unreach.org/socat/ "Socat is a command line based utility that establishes two bidirectional byte streams and transfers data between them. Because the streams can be constructed from a large set of different types of data sinks and sources (see address types), and because lots of address options may be applied to the streams, socat can be used for many different purposes. It might be one of the tools that one `has already needed'." which, iiuc (?), can bidirectionally bridge the Dovecot unix-socket to a TCP socket that Exim can talk/listen to. reading further, "address types" (http://www.dest-unreach.org/socat/doc/socat.html#ADDRESS_TYPES) seem to include BOTH unix & tcp sockets ... can anyone here comment further on this? known to work? possible? no way? etc etc thanks!

2 1

[Dovecot] index
by Lucas -LandM- 17 Jun '07

17 Jun '07

Hi, First of all congratulations for you development. It´s really good. We have a customer that has a copy of all inbound and outbound mail in an account. When he tries to open the mail, the process of index all mail consume all cpu and memory. How can we avoid this kinds of things? Thank you in advance, Lucas

4 7

Re: [Dovecot] dovecot under attack
by Dani 16 Jun '07

16 Jun '07

A Dissabte 16 Juny 2007 16:10, Jon Slater va escriure: > Hi, > > I’ve posted this before but no one was able to help. I can’t figure > out what they are trying to do, and if I should be concerned. > I am running dovecot version 0.99.14 on Fedora Core 4. It appears > that my dovecot server is under attack. This morning in my system > e-mail I saw this: Hi Jon, just my 5 cents, eventually you can figure out if they are trying to login directly to you imap/pop3 ports or maybe through a webmail? In every case why don't you give a try to a fail2ban program to block automatically login failures through iptables and of course upgrade your dovecot's installation? http://drees76.blogspot.com/2006/08/fail2ban-dovecot-and-brute-force.html greetings, dani

1 0

[Dovecot] 1st DOVECOT installation automatically quitting on login
by Benton Haynes 16 Jun '07

16 Jun '07

Hi there. I have just installed DOVECOT 1.0.1 for the first time. After launching it, I can verify that ps -ax | grep -i dovecot 1052 ?? Ss 0:00.03 /usr/local/dovecot/sbin/dovecot -c /etc/dovecot/dovecot.conf 1053 ?? S 0:00.06 dovecot-auth 1058 p2 R+ 0:00.01 grep -i dovecot ps -ax | grep -i imap 1054 ?? S 0:00.08 imap-login 1055 ?? S 0:00.08 imap-login 1056 ?? S 0:00.08 imap-login 1060 p2 R+ 0:00.01 grep -i imap Then, if I telnet to DOVECOT/IMAP & login telnet 192.168.1.30 143 Trying 192.168.1.30... Connected to 192.168.1.30. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS QUOTA STARTTLS AUTH=PLAIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] haynes.name IMAP4 server ready x login ben(a)haynes.name benpass x OK Logged in. Connection closed by foreign host. ^^^^^^^^^^^^^^^^^^^ It disconnects automatically. In my dovecot.conf, I currently have defined verbose_ssl = no auth_verbose = no auth_debug = yes mail_debug = no And, in dovecot.log, I get only, dovecot: Jun 15 18:51:10 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=192.168.1.30 rip=192.168.1.3resp=<hidden> dovecot: Jun 15 18:51:10 Info: auth(default): passwd-file(user= ben(a)haynes.name,192.168.1.3) lookup: user=ben(a)haynes.namefile=/etc/dovecot/user.file dovecot: Jun 15 18:51:10 Info: auth(default): client out: OK 1 user=ben(a)haynes.name dovecot: Jun 15 18:51:10 Info: auth(default): master in: REQUEST 11054 1 dovecot: Jun 15 18:51:10 Info: auth(default): master out: USER 1 ben(a)haynes.name static uid=500 gid=500 home=/var/mail/imap/haynes.name/accounts/ben nice=10 dovecot: Jun 15 18:51:10 Info: imap-login: Login: user=<user=ben(a)haynes.name>, method=PLAIN, rip=192.168.1.3, lip=192.168.1.30 dovecot: Jun 15 18:51:14 Error: child 1064 (imap) killed with signal 4 Ihaven't been able to figure out why this is happening. Is there some more detailed debugging I should turn on? Any ideas why this is going on? -- Ben

2 4

Re: [Dovecot] dovecot under attack
by Mart Pirita 16 Jun '07

16 Jun '07

Tere. > > > Does anyone know what this is? Or someone I could ask? > > Normal dictionary attack? -- Mart

1 0

Re: [Dovecot] dovecot under attack
by Charles Marcus 16 Jun '07

16 Jun '07

Hi Jon, I cannot help with the specific question, but in my opinion, your first and primary goal should be to get that server updated to 1.0.1 asap... 0.99.x is no longer supported - and *very* dated... Jon Slater wrote: > Hi, > > > > I’ve posted this before but no one was able to help. I can’t figure out > what they are trying to do, and if I should be concerned. > > > > I am running dovecot version 0.99.14 on Fedora Core 4. It appears that my > dovecot server is under attack. This morning in my system e-mail I saw > this: > > > > dovecot: > > Authentication Failures: > > rhost= : 23431 Time(s) > > adm: 33 Time(s) > > bin: 33 Time(s) > > mail: 33 Time(s) > > mysql: 21 Time(s) > > nobody: 15 Time(s) > > news: 14 Time(s) > > operator: 8 Time(s) > > sshd: 2 Time(s) > > Unknown Entries: > > check pass; user unknown: 23431 Time(s) > > > > But, when I check my log files I can’t find an IP address for the attacker. > So, for example, if I search my logs for “operator” I see: > > ./messages:Jun 15 23:30:56 lambdacenter dovecot(pam_unix)[15512]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:00 lambdacenter dovecot(pam_unix)[15670]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:16 lambdacenter dovecot(pam_unix)[16332]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:20 lambdacenter dovecot(pam_unix)[16480]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:27 lambdacenter dovecot(pam_unix)[16695]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:38 lambdacenter dovecot(pam_unix)[16884]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:55 lambdacenter dovecot(pam_unix)[17080]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:32:11 lambdacenter dovecot(pam_unix)[17182]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971858.967:156312): user > pid=15512 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971862.772:156382): user > pid=15670 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971878.710:156707): user > pid=16332 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971882.379:156775): user > pid=16480 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971908.712:156879): user > pid=16695 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181972032.080:156904): user > pid=16884 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181972047.607:156917): user > pid=17080 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181972066.325:156928): user > pid=17182 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > > > I’ve checked my snmplog for port activity on port 110 (for POP3) and 143 > (for IMAP), but I don’t see anything unusual. I also systematically > filtered out everything I knew was okay (ssh, and httpd) . > > > > Does anyone know what this is? Or someone I could ask? > > > > Thanks!!!!!!!!!!!!!!!!!!!! > > > > Jon > > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.8.17/850 - Release Date: 6/15/2007 > 11:31 AM > >

1 0

[Dovecot] dovecot under attack
by Jon Slater 16 Jun '07

16 Jun '07

Hi, I’ve posted this before but no one was able to help. I can’t figure out what they are trying to do, and if I should be concerned. I am running dovecot version 0.99.14 on Fedora Core 4. It appears that my dovecot server is under attack. This morning in my system e-mail I saw this: dovecot: Authentication Failures: rhost= : 23431 Time(s) adm: 33 Time(s) bin: 33 Time(s) mail: 33 Time(s) mysql: 21 Time(s) nobody: 15 Time(s) news: 14 Time(s) operator: 8 Time(s) sshd: 2 Time(s) Unknown Entries: check pass; user unknown: 23431 Time(s) But, when I check my log files I can’t find an IP address for the attacker. So, for example, if I search my logs for “operator” I see: ./messages:Jun 15 23:30:56 lambdacenter dovecot(pam_unix)[15512]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:00 lambdacenter dovecot(pam_unix)[15670]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:16 lambdacenter dovecot(pam_unix)[16332]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:20 lambdacenter dovecot(pam_unix)[16480]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:27 lambdacenter dovecot(pam_unix)[16695]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:38 lambdacenter dovecot(pam_unix)[16884]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:55 lambdacenter dovecot(pam_unix)[17080]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:32:11 lambdacenter dovecot(pam_unix)[17182]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./audit/audit.log:type=USER_AUTH msg=audit(1181971858.967:156312): user pid=15512 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181971862.772:156382): user pid=15670 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181971878.710:156707): user pid=16332 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181971882.379:156775): user pid=16480 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181971908.712:156879): user pid=16695 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181972032.080:156904): user pid=16884 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181972047.607:156917): user pid=17080 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181972066.325:156928): user pid=17182 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' I’ve checked my snmplog for port activity on port 110 (for POP3) and 143 (for IMAP), but I don’t see anything unusual. I also systematically filtered out everything I knew was okay (ssh, and httpd) . Does anyone know what this is? Or someone I could ask? Thanks!!!!!!!!!!!!!!!!!!!! Jon No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.8.17/850 - Release Date: 6/15/2007 11:31 AM

1 0

[Dovecot] Per user based protocol access and pause after failed login?
by Mart Pirita 16 Jun '07

16 Jun '07

Hello. Tried search, no luck, sorry, if this is already answered, but I'm still looking a solution using pam_auth how to define in dovecot which user can access which protocol, for example, default is: protocols = pop3 pop3s imap imaps I'd like to use something like this: exclude_using_pop = user1, user2, @group exclude_using_pops = user1, user2, @group exclude_using_imap = user1, user2, @group exclude_using_imaps = user1, user2, @group The idea is security and also preventing imap user by accident logging in using pop3 and downloading (clearing inbox for imap) all inbox. And also some throttling, for example the adjustable time to pause access after failed login etc would be great. -- Mart

2 2

[Dovecot] SHA256 password patch
by Jasper Slits 16 Jun '07

16 Jun '07

Hi, I made a patch against branch-1.0 for SHA256 password hashing support for Dovecot. Courier Authlib supports this hashing scheme and in order to migrate from Courier to Dovecot, I've added SHA256 support to Dovecot. The attached patch is based on BSD licensed code from Olivier Gay (http://www.ouah.org/ogay/sha2/) Changes made by me in Olivier's sha2{.h,.c} code: - Prototype for sha256_transf is added to sha2.h - sha256_get_digest() is added to sha2{.h,.c} - Code for UNROLL_LOOPS is removed - Support for SHA224,SHA384,SHA512 was removed - Functions are renamed to match those in sha1{.h,.c} - SHA256_DIGEST_SIZE is renamed to SHA256_RESULTLEN I can add safe_memset calls if requested. Patch is attached and can also be found at http://www.malochia.nl/dovecot/sha256.patch Kind regards, Jasper diff -r -u -N --exclude=Makefile.in --exclude=.deps --exclude=Makefile src/auth/password-scheme.c auth/password-scheme.c --- src/auth/password-scheme.c 2007-02-21 13:30:38.756711250 +0100 +++ auth/password-scheme.c 2007-02-21 14:18:49.645380500 +0100 @@ -10,6 +10,7 @@ #include "mycrypt.h" #include "randgen.h" #include "sha1.h" +#include "sha2.h" #include "str.h" #include "password-scheme.h" @@ -153,6 +154,17 @@ return str_c(str); } +static const char *sha256_generate(const char *plaintext, + const char *user __attr_unused__) +{ + unsigned char digest[SHA256_RESULTLEN]; + string_t *str; + sha256_get_digest(plaintext, strlen(plaintext), digest); + str = t_str_new(MAX_BASE64_ENCODED_SIZE(sizeof(digest)+1)); + base64_encode(digest, sizeof(digest), str); + return str_c(str); +} + static const void * password_decode(const char *password, unsigned int result_len) { @@ -196,6 +208,23 @@ return memcmp(sha1_digest, data, SHA1_RESULTLEN) == 0; } +static bool sha256_verify(const char *plaintext, const char *password, + const char *user) +{ + unsigned char sha256_digest[SHA256_RESULTLEN]; + const char *data; + + sha256_get_digest(plaintext, strlen(plaintext), sha256_digest); + + data = password_decode(password, SHA256_RESULTLEN); + if (data == NULL) { + i_error("sha256_verify(%s): Invalid password encoding", user); + return 0; + } + + return memcmp(sha256_digest, data, SHA256_RESULTLEN) == 0; +} + static const char *ssha_generate(const char *plaintext, const char *user __attr_unused__) { @@ -466,6 +495,7 @@ { "MD5-CRYPT", md5_crypt_verify, md5_crypt_generate }, { "SHA", sha1_verify, sha1_generate }, { "SHA1", sha1_verify, sha1_generate }, + { "SHA256", sha256_verify, sha256_generate }, { "SMD5", smd5_verify, smd5_generate }, { "SSHA", ssha_verify, ssha_generate }, { "PLAIN", plain_verify, plain_generate }, diff -r -u -N --exclude=Makefile.in --exclude=.deps --exclude=Makefile src/lib/Makefile.am lib/Makefile.am --- src/lib/Makefile.am 2007-02-21 13:30:38.792713500 +0100 +++ lib/Makefile.am 2007-02-21 14:21:59.437241750 +0100 @@ -73,6 +73,7 @@ sendfile-util.c \ seq-range-array.c \ sha1.c \ + sha2.c \ str.c \ str-sanitize.c \ strescape.c \ @@ -146,6 +147,7 @@ sendfile-util.h \ seq-range-array.h \ sha1.h \ + sha2.h \ str.h \ str-sanitize.h \ strescape.h \ diff -r -u -N --exclude=Makefile.in --exclude=.deps --exclude=Makefile src/lib/sha2.c lib/sha2.c --- src/lib/sha2.c 1970-01-01 01:00:00.000000000 +0100 +++ lib/sha2.c 2007-02-23 14:03:46.857739818 +0100 @@ -0,0 +1,257 @@ +/* + * FIPS 180-2 SHA-224/256/384/512 implementation + * Last update: 02/02/2007 + * Issue date: 04/30/2005 + * + * Copyright (C) 2005, 2007 Olivier Gay <olivier.gay(a)a3.epfl.ch> + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. Neither the name of the project nor the names of its contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + */ + +#include <string.h> + +#include "sha2.h" + +#define SHFR(x, n) (x >> n) +#define ROTR(x, n) ((x >> n) | (x << ((sizeof(x) << 3) - n))) +#define ROTL(x, n) ((x << n) | (x >> ((sizeof(x) << 3) - n))) +#define CH(x, y, z) ((x & y) ^ (~x & z)) +#define MAJ(x, y, z) ((x & y) ^ (x & z) ^ (y & z)) + +#define SHA256_F1(x) (ROTR(x, 2) ^ ROTR(x, 13) ^ ROTR(x, 22)) +#define SHA256_F2(x) (ROTR(x, 6) ^ ROTR(x, 11) ^ ROTR(x, 25)) +#define SHA256_F3(x) (ROTR(x, 7) ^ ROTR(x, 18) ^ SHFR(x, 3)) +#define SHA256_F4(x) (ROTR(x, 17) ^ ROTR(x, 19) ^ SHFR(x, 10)) + +#define UNPACK32(x, str) \ +{ \ + *((str) + 3) = (uint8) ((x) ); \ + *((str) + 2) = (uint8) ((x) >> 8); \ + *((str) + 1) = (uint8) ((x) >> 16); \ + *((str) + 0) = (uint8) ((x) >> 24); \ +} + +#define PACK32(str, x) \ +{ \ + *(x) = ((uint32) *((str) + 3) ) \ + | ((uint32) *((str) + 2) << 8) \ + | ((uint32) *((str) + 1) << 16) \ + | ((uint32) *((str) + 0) << 24); \ +} + +#define UNPACK64(x, str) \ +{ \ + *((str) + 7) = (uint8) ((x) ); \ + *((str) + 6) = (uint8) ((x) >> 8); \ + *((str) + 5) = (uint8) ((x) >> 16); \ + *((str) + 4) = (uint8) ((x) >> 24); \ + *((str) + 3) = (uint8) ((x) >> 32); \ + *((str) + 2) = (uint8) ((x) >> 40); \ + *((str) + 1) = (uint8) ((x) >> 48); \ + *((str) + 0) = (uint8) ((x) >> 56); \ +} + +#define PACK64(str, x) \ +{ \ + *(x) = ((uint64) *((str) + 7) ) \ + | ((uint64) *((str) + 6) << 8) \ + | ((uint64) *((str) + 5) << 16) \ + | ((uint64) *((str) + 4) << 24) \ + | ((uint64) *((str) + 3) << 32) \ + | ((uint64) *((str) + 2) << 40) \ + | ((uint64) *((str) + 1) << 48) \ + | ((uint64) *((str) + 0) << 56); \ +} + +/* Macros used for loops unrolling */ + +#define SHA256_SCR(i) \ +{ \ + w[i] = SHA256_F4(w[i - 2]) + w[i - 7] \ + + SHA256_F3(w[i - 15]) + w[i - 16]; \ +} + + + +uint32 sha256_h0[8] = + {0x6a09e667, 0xbb67ae85, 0x3c6ef372, 0xa54ff53a, + 0x510e527f, 0x9b05688c, 0x1f83d9ab, 0x5be0cd19}; + + +uint32 sha256_k[64] = + {0x428a2f98, 0x71374491, 0xb5c0fbcf, 0xe9b5dba5, + 0x3956c25b, 0x59f111f1, 0x923f82a4, 0xab1c5ed5, + 0xd807aa98, 0x12835b01, 0x243185be, 0x550c7dc3, + 0x72be5d74, 0x80deb1fe, 0x9bdc06a7, 0xc19bf174, + 0xe49b69c1, 0xefbe4786, 0x0fc19dc6, 0x240ca1cc, + 0x2de92c6f, 0x4a7484aa, 0x5cb0a9dc, 0x76f988da, + 0x983e5152, 0xa831c66d, 0xb00327c8, 0xbf597fc7, + 0xc6e00bf3, 0xd5a79147, 0x06ca6351, 0x14292967, + 0x27b70a85, 0x2e1b2138, 0x4d2c6dfc, 0x53380d13, + 0x650a7354, 0x766a0abb, 0x81c2c92e, 0x92722c85, + 0xa2bfe8a1, 0xa81a664b, 0xc24b8b70, 0xc76c51a3, + 0xd192e819, 0xd6990624, 0xf40e3585, 0x106aa070, + 0x19a4c116, 0x1e376c08, 0x2748774c, 0x34b0bcb5, + 0x391c0cb3, 0x4ed8aa4a, 0x5b9cca4f, 0x682e6ff3, + 0x748f82ee, 0x78a5636f, 0x84c87814, 0x8cc70208, + 0x90befffa, 0xa4506ceb, 0xbef9a3f7, 0xc67178f2}; + + +/* SHA-256 functions */ + +void sha256_transf(sha256_ctx *ctx, const unsigned char *message, + unsigned int block_nb) +{ + uint32 w[64]; + uint32 wv[8]; + uint32 t1, t2; + const unsigned char *sub_block; + int i,j; + + + for (i = 0; i < (int) block_nb; i++) { + sub_block = message + (i << 6); + + for (j = 0; j < 16; j++) { + PACK32(&sub_block[j << 2], &w[j]); + } + + for (j = 16; j < 64; j++) { + SHA256_SCR(j); + } + + for (j = 0; j < 8; j++) { + wv[j] = ctx->h[j]; + } + + for (j = 0; j < 64; j++) { + t1 = wv[7] + SHA256_F2(wv[4]) + CH(wv[4], wv[5], wv[6]) + + sha256_k[j] + w[j]; + t2 = SHA256_F1(wv[0]) + MAJ(wv[0], wv[1], wv[2]); + wv[7] = wv[6]; + wv[6] = wv[5]; + wv[5] = wv[4]; + wv[4] = wv[3] + t1; + wv[3] = wv[2]; + wv[2] = wv[1]; + wv[1] = wv[0]; + wv[0] = t1 + t2; + } + + for (j = 0; j < 8; j++) { + ctx->h[j] += wv[j]; + } + } +} + +void sha256(const unsigned char *message, unsigned int len, unsigned char *digest) +{ + sha256_ctx ctx; + + sha256_init(&ctx); + sha256_loop(&ctx, message, len); + sha256_result(&ctx, digest); +} + +void sha256_init(sha256_ctx *ctx) +{ + int i; + for (i = 0; i < 8; i++) { + ctx->h[i] = sha256_h0[i]; + } + + ctx->len = 0; + ctx->tot_len = 0; +} + +void sha256_loop(sha256_ctx *ctx, const unsigned char *message, + unsigned int len) +{ + unsigned int block_nb; + unsigned int new_len, rem_len, tmp_len; + const unsigned char *shifted_message; + + tmp_len = SHA256_BLOCK_SIZE - ctx->len; + rem_len = len < tmp_len ? len : tmp_len; + + memcpy(&ctx->block[ctx->len], message, rem_len); + + if (ctx->len + len < SHA256_BLOCK_SIZE) { + ctx->len += len; + return; + } + + new_len = len - rem_len; + block_nb = new_len / SHA256_BLOCK_SIZE; + + shifted_message = message + rem_len; + + sha256_transf(ctx, ctx->block, 1); + sha256_transf(ctx, shifted_message, block_nb); + + rem_len = new_len % SHA256_BLOCK_SIZE; + + memcpy(ctx->block, &shifted_message[block_nb << 6], + rem_len); + + ctx->len = rem_len; + ctx->tot_len += (block_nb + 1) << 6; +} + +void sha256_result(sha256_ctx *ctx, unsigned char *digest) +{ + unsigned int block_nb; + unsigned int pm_len; + unsigned int len_b; + int i; + + block_nb = (1 + ((SHA256_BLOCK_SIZE - 9) + < (ctx->len % SHA256_BLOCK_SIZE))); + + len_b = (ctx->tot_len + ctx->len) << 3; + pm_len = block_nb << 6; + + memset(ctx->block + ctx->len, 0, pm_len - ctx->len); + ctx->block[ctx->len] = 0x80; + UNPACK32(len_b, ctx->block + pm_len - 4); + + sha256_transf(ctx, ctx->block, block_nb); + + for (i = 0 ; i < 8; i++) { + UNPACK32(ctx->h[i], &digest[i << 2]); + } +} + +void sha256_get_digest(const void *data, size_t size, + unsigned char result[SHA256_RESULTLEN]) +{ + sha256_ctx ctx; + + sha256_init(&ctx); + sha256_loop(&ctx, data, size); + sha256_result(&ctx, result); +} + diff -r -u -N --exclude=Makefile.in --exclude=.deps --exclude=Makefile src/lib/sha2.h lib/sha2.h --- src/lib/sha2.h 1970-01-01 01:00:00.000000000 +0100 +++ lib/sha2.h 2007-02-23 14:22:32.952116316 +0100 @@ -0,0 +1,72 @@ +/* + * FIPS 180-2 SHA-224/256/384/512 implementation + * Last update: 02/02/2007 + * Issue date: 04/30/2005 + * + * Copyright (C) 2005, 2007 Olivier Gay <olivier.gay(a)a3.epfl.ch> + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. Neither the name of the project nor the names of its contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + */ + +#ifndef SHA2_H +#define SHA2_H + +#define SHA256_RESULTLEN ( 256 / 8) + +#define SHA256_BLOCK_SIZE ( 512 / 8) + +#ifndef SHA2_TYPES +#define SHA2_TYPES +typedef unsigned char uint8; +typedef unsigned int uint32; +typedef unsigned long long uint64; +#endif + + +typedef struct { + unsigned int tot_len; + unsigned int len; + unsigned char block[2 * SHA256_BLOCK_SIZE]; + uint32 h[8]; +} sha256_ctx; + +void sha256_transf(sha256_ctx *ctx, const unsigned char *message, + unsigned int block_nb); + + +void sha256_init(sha256_ctx * ctx); +void sha256_loop(sha256_ctx *ctx, const unsigned char *message, + unsigned int len); +void sha256_result(sha256_ctx *ctx, unsigned char *digest); +void sha256(const unsigned char *message, unsigned int len, + unsigned char *digest); +void sha256_get_digest(const void *data, size_t size, + unsigned char result[SHA256_RESULTLEN]); + + + +#endif /* !SHA2_H */ +

3 2

[Dovecot] SEGV with Dovecot v1.0.0 Deliver and cmusieve v1.0.1 and vacation
by Steffen Kaiser 16 Jun '07

16 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have a small Sieve script that tries to use vacation that segfaults. The script is the one from http://wiki.dovecot.org/LDA/Sieve. When I change the email address (I changed the local part into "skai"), hence, vacation is skipped, the mail is delivered without any problem. ==== script start require ["fileinto", "vacation"]; # Move spam to spam folder if exists "X-Spam-Flag" { fileinto "spam"; # Stop here so that we do not reply on spams stop; } vacation # Reply at most once a day to a same sender :days 1 :subject "Out of office reply" # List of allowed recipient addresses from auto reply should be sent. :addresses ["ska(a)ux-2s11-9.inf.fh-bonn-rhein-sieg.de"] "I'm out of office, please contact Joan Doe instead. Best regards John Doe"; ========== END ========== Out of sieved .dovecot.sievec Sievecode version 3 4: IF (ends at 13)exists{11}X-Spam-Flag 13:JUMP 20 19: FILEINTO {4}spam 19: STOP 20: VACATION {39}ska(a)ux-2s11-9.inf.fh-bonn-rhein-sieg.de 40 SUBJ({19}Out of office reply) 60 MESG({73}I'm out of office, please contact Joan Doe instead. Best regards John Doe) DAYS(1) MIME(0) full len is: 62 ========== END gdb output: Core was generated by `/usr/local/dovecot/libexec/dovecot/deliver'. Program terminated with signal 11, Segmentation fault. #0 0xb7eef3a3 in strlen () from /lib/tls/i686/cmov/libc.so.6 (gdb) bt full #0 0xb7eef3a3 in strlen () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #1 0xb7e2bcf3 in sieve_execute_bytecode (bc=0x80e3eb0, interp=0x80e3de8, script_context=0xbfb57800, message_context=0xbfb577c4) at script.c:398 hash = "\000\000\000\000¸Z0F\000\000\000\000¸Z0F" actions = (action_list_t *) 0x80e3850 notify_list = (notify_list_t *) 0x80e3830 actions_string = "Action(s) taken:\n", '\0' <repeats 4078 times> errmsg = 0x0 imapflags = {flag = 0x0, nflags = 0} #2 0xb7e1eb2c in cmu_sieve_run (storage=0x80d0a20, mail=0x80e03c8, script_path=0x80cbc48 "/home/ska/.dovecot.sieve", username=0x80cb030 "ska", mailbox=0x80bae92 "INBOX") at sieve-cmu.c:573 fd = <value optimized out> interp = (sieve_interp_t *) 0x80e3de8 bytecode = (sieve_bytecode_t *) 0x80e3eb0 sdata = {username = 0x80cb030 "ska", storage = 0x80d0a20, errors = 0x0} mdata = {mail = 0x80e03c8, mailbox = 0x80bae92 "INBOX", id = 0x80e4860 "<200704260754.l3Q7sWdu002894(a)ux-2s11-9.inf.fh-bonn-rhein-sieg.de>", return_path = 0x0, authuser = 0x80cb030 "ska", temp = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}} compiled_path = 0x80cbc68 "/home/ska/.dovecot.sievec" path = 0xb7fb0ff4 "<Í\022" ret = <value optimized out> #3 0xb7e1da72 in cmusieve_deliver_mail (storage=0x80d0a20, mail=0x80e03c8, username=0x80cb030 "ska", mailbox=0x80bae92 "INBOX") at cmusieve-plugin.c:72 script_path = 0x80cbc48 "/home/ska/.dovecot.sieve" #4 0x08057536 in main (argc=Cannot access memory at address 0x0 ) at deliver.c:679 tab = (struct var_expand_table *) 0x80cb068 config_path = 0x80bb79c "/usr/local/dovecot/etc/dovecot.conf" envelope_sender = 0x80bae98 "MAILER-DAEMON" mailbox = 0x80bae92 "INBOX" auth_socket = <value optimized out> home = <value optimized out> destination = 0x80cb030 "ska" user = 0x80cb030 "ska" mail_env = <value optimized out> flags = 1025 lock_method = MAIL_STORAGE_LOCK_FCNTL storage = (struct mail_storage *) 0x80d0a20 mbox_storage = (struct mail_storage *) 0x80d2d48 box = (struct mailbox *) 0x80dcc88 input = (struct istream *) 0x80d4044 t = (struct mailbox_transaction_context *) 0x80de2a0 mail = (struct mail *) 0x80e03c8 process_euid = 30000 i = 63 ret = <value optimized out> (gdb) - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRjBdji9SORjhbDpvAQICoggAnzLxTlL8mDonntaDvwr/4JN6eWPIAm7o XP6hSw9JlbTsPY55keQMZpN/UNB/FXojcqI6lD4f/2dJqCEHmeB40NQZEMUN+f60 6+BHkE6vb2sMnXa09eQWg2d5zVKp6bHdSsbtzmWIsYX0stUFMncFTJVQgatHstDm DaSGMf6V2SwiPst/0tUbeTMqYhud9LU2YLhU3+T9AuTmcSGztohnJPGnqC1GLP+N m+KLbLF6B7ZMQ2RX+M+arzz8EQRHZ2622aqiLKoT+rVZ8LkLPzp4Whd9HK1MqMld KSjJuZBKgKuJr61SGqPboPOip635DgJH7g2BKgGnOHWvJf6E7U+Q9A== =1M3a -----END PGP SIGNATURE-----

3 3

[Dovecot] auth process(es)
by Thomas Hummel 16 Jun '07

16 Jun '07

Hello Timo, I've got some questions about dovecot-auth processes which I cannot answer just by reading the doc : [ Note : my problem is that I often see dovecot: pop3-login: Can't connect to auth server at default: Connection refused and I'm looking for a way to tweak dovecot.conf parameters to allow more login <-> auth connections ] - I'm not sure I get the auth worker process concept right : is there a master dovecot-auth which listens to new incoming connections from login processes and fork/exec the real job of authenticating against the pass/userdbs to a child, called an auth worker ? - is it safe to increment the number of auth processes (the 'count' parameter in the auth block (auth_default { ...} for instance) ? - my understanding is that login processes communicate with auth processes through a unix type socket (named 'default') : can I create a second auth block in dovecot.conf (for instance 'aut extra {...}') in addition to the existing 'auth default {...}' one ? would it create an second unix socket and thus allowing a heavier login processes load ? what would be the difference between that and, say, changing the 'count' parameter to '2' in the 'auth default' section ? thanks. -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 5

[Dovecot] different configurations for individual user
by Joshua C.S. Chen 16 Jun '07

16 Jun '07

Hi everyone, I am planning to upgrade my current uw-imap to dovecot. I am using Linux (Redhat EL 4). The main purpose is to use maildir instead of mbox. For some reason, I don't want to upgrade all users' mail boxes all at a time, but I want to change the imap server first (to dovecot), while keeping all mbox files, then convert them to maildir user by user (one user at a time). My question is: Is it possible that dovecot can setup individual user's own configuration? so that some users can setup mail_location = mbox but others = maildir. Thanks in advance Joshua

2 1

[Dovecot] LDAP subtree search on AD
by Bruno Puga 16 Jun '07

16 Jun '07

Hello people! I'm new to the list and to dovecot too. In advance I'd like to thank everybody who could help me, and I'll be very glad if a could help somebody here. I'm working in a project to integrate dovecot and active directory authentication for 2 weeks without total success. I've tried so many waysto solve my problem, but no one gave me the right answer. I'll appreciate if someone could help me. First off all let me show some needed data. Distro: Debian Etch dovecot --version 1.0.0 dovecot -n # /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot-imapd.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/lib/dovecot/imap-login mail_debug: yes imap_client_workarounds: outlook-idle delay-newmail auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: pam args: dovecot userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail /etc/dovecot/dovecot-ldap.conf hosts = 192.168.0.11 dn = cn=dovecot,cn=Users,dc=tecnicopias01,dc=com,dc=br dnpass = password ldap_version = 3 auth_bind = yes base = DC=tecnicopias01,DC=com,DC=br deref = never scope = subtree user_attrs = info=mail user_filter = (&(objectClass=organizationalPerson)(sAMAccountName=%u)) user_global_uid = 5000 user_global_gid = 5000 I can authenticate using pam+krb5 with success, but when I try to make a userdb search to get maillocation for the authenticated user, I get in trouble. The ldap_search doesn't make subtree search, making only onelevel search. So, if I point the base directive (/etc/dovecot/dovecot-ldap.conf) to where the user that is authenticating in that moment is, I can perfect login and get the maillocation. My question is: Why dovecot doesn't make ldap subtree search? Or, am I missing anything? Thanks Bruno.

2 5

[Dovecot] Looking for plugin docs
by Rajkumar S 16 Jun '07

16 Jun '07

Hello all, I had gone through the wiki, but could not find any page about writing new plugins. Any pointers towards plugin api/docs will be very helpful. with warm regards, raj

3 14

Re: [Dovecot] auth process(es)
by Kenny Dail 15 Jun '07

15 Jun '07

> > - is it safe to increment the number of auth processes (the 'count' > > parameter in the auth block (auth_default { ...} for instance) ? > > Should be. > > > - my understanding is that login processes communicate with auth > > processes through a unix type socket (named 'default') : > > > > can I create a second auth block in dovecot.conf (for instance > > 'aut extra {...}') in addition to the existing 'auth default {...}' > > one ? would it create an second unix socket and thus allowing a heavier > > login processes load ? > > > > what would be the difference between that and, say, changing the > > 'count' parameter to '2' in the 'auth default' section ? > > Increasing count allows heavier load, because there are then more > processes listening for incoming connections in the same socket. Actually increasing the count doesn't work. At least not for me on 1.0.0: Jun 14 12:28:39 mail5 dovecot: Dovecot v1.0.0 starting up Jun 14 12:28:39 mail5 dovecot: Auth process died too early - shutting down Jun 14 12:28:39 mail5 dovecot: child 19080 (auth) returned error 89 Jun 14 12:28:39 mail5 dovecot: auth(default): Socket already exists: /var/run/dovecot/auth-client -- Kenny Dail <kend(a)amigo.net>

3 2

[Dovecot] shared folders
by T. Horsnell 14 Jun '07

14 Jun '07

A number of our users would greatly benefit from truly shareable mail folders. I know we can bodge this with symlinks, but mailbox corruptions seem to occur when simultaneous updates are made, but this may be a client issue I guess. So I wonder if true shareability is creeping up the agenda. By true shareability, I mean such that if two users have the same folder open and one of them makes a modification to it, the display of that folder on the other user's screen immediately reflects that change. I guess this may well require a co-operating client... Cheers, Terry --

2 1

[Dovecot] postfix+dovecot delivering to wrong (/var/mail/%u) place
by Tom Lobato 14 Jun '07

14 Jun '07

(Dovecot 1.0.rc15) Hello I'm tring to configure postfix+dovecot on debian etch. In dovecot I use passdb pam and userdb passwd-file. I can connect pop3 clients and reveice mails and connect smtp clients and send mails, but it is delivered to /var/mail/%u instead the configured mailboxes in /var/local/dovecot/%u. I`ve configured postfix as say http://wiki.dovecot.org/LDA/Postfix. /etc/postfix/main.cf: ----------------------------------- smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) biff = no append_dot_mydomain = no myhostname = coan alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mydestination = coan.com.br myorigin = /etc/mailname relayhost = mynetworks = 121.120.0.0/16 mailbox_size_limit = 0 inet_interfaces = all smtpd_recipient_restrictions = reject_unauth_destination virtual_transport = dovecot dovecot_destination_recipient_limit = 1 ----------------------------------- belong master.cf. Below the syslog when I send mail via smtp... /var/log/syslog: -------------------------------- postfix/smtpd[16656]: connect from 201-95-99-135.dsl.telesp.net.br[201.95.99.135] postfix/smtpd[16656]: C76F948E3D7: client=201-95-99-135.dsl.telesp.net.br[201.95.99.135] postfix/cleanup[16660]: C76F948E3D7: message-id=<1181769218.7844.6.camel@mobile> postfix/qmgr[16653]: C76F948E3D7: from=<tom(a)coan.com.br>, size=457, nrcpt=1 (queue active) postfix/local[16661]: C76F948E3D7: to=<tom(a)coan.com.br>, relay=local, delay=0.52, delays=0.45/0.01/0/0.07, dsn=2.0.0, status=sent (delivered to mailbox) postfix/qmgr[16653]: C76F948E3D7: removed postfix/smtpd[16656]: disconnect from 201-95-99-135.dsl.telesp.net.br[201.95.99.135] ------------------------------- If I change 'virtual_transport = dovecot' to 'local_transport = dovecot', syslog output changes relay-local to relay=dovecot, but bounces the mail saying 'passwd-file(tom(a)coan.com.br): unknown user'. However I'm sure that the user is in the passwd-file and dovecot has permissions to read it. Can you give some hints about what can be happening? Dovecot conf: ----------------------- # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/pop3-login mail_extra_groups: mail mailboxes mail_location: maildir:/var/local/dovecot/%u mail_executable: /usr/lib/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/modules/pop3 pop3_uidl_format: %v.%u auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: pam userdb: driver: passwd-file args: /etc/mailsystem/userdb socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 438 ----------------------- Thank you Tom Lobato

1 1

[Dovecot] How do I test new code?
by Stewart Dean 14 Jun '07

14 Jun '07

I know how to run a second instance of the *base* code (to check different functionality/config) and documented it in http://wiki.dovecot.org/RunningDovecot What I realize I don't know how to do is to run an altogether different version or build of the code as that second instance, which would be good to have to check out upgrades before they go into production. While I could do a build in the regular fashion and put DC somewhere else or name it something else, so I could invoke this different code, presumably that different code will still look for the subsidiary executables in the usual place. Do I have to change the DESTDIR parm when doing the make install or some such? I do realize that, just as I did with running a second instance of the *same* code, I'd have to change the config file, have a separate /var/run directory...... -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

[Dovecot] errors in dovecot-uidlist
by Erland Nylend 14 Jun '07

14 Jun '07

We have migrated a mailsystem to postfix/dovecot, using the courier migrate script, and we have run into a problem with dovecot-uidlist. The messages are not listed in the correct order .. This is an example dovecot-uidlist -file: 1 1177585200 49 22 1179084774.P7191Q0M321163.webmail1,S=8245:2,S 24 1179377823.P15932Q0M835219.smtp1,S=3462:2,S 25 1179668346.P23942Q0M941365.webmail1,S=4820357:2,S 31 1179864561.P22903Q0M433768.smtp2,S=3306:2,S 34 1180344355.P25491Q0M17232.smtp2,S=5111:2,S 35 1180454170.P14932Q0M841649.smtp2,S=2024:2, 36 1168867750.H82058P20971.smtp1:2,SR 37 1170339716.H537368P4032.smtp1:2,S 38 1171291025.H352867P8785.smtp2:2,SR 39 1171357049.H141820P2105.smtp1:2,SR 40 1171460195.H933928P14324.smtp1:2,SR 41 1171616121.H812220P27503.smtp2:2,SR 42 1171872919.H950768P16201.smtp1:2,S 43 1173694618.H330094P23347.smtp1:2,S 44 1175238705.H589518P693.smtp1:2,SR 45 1176800600.H716261P10514.smtp1:2,SR 46 1177615732.H355340P10418.webmail1:2,SR 47 1180471524.P30985Q0M109430.smtp2,S=16621 48 1180597849.P8169Q0M990486.smtp1,S=33326 As you can see, the unix timestamps are descending between uid 35 and uid 36 .. and this causes problems if we intend to make webmail access the messages through imap. (it expects to receive the messages sorted by when they were received) Is there any way I can sort the list accourding to the unix timestamps, and still make it transparent to the pop3/imap clients? I would prefer a solution that does not involve users downloading allready downloaded messages via pop3. -- Erland Nylend

2 3

[Dovecot] 1.0.1 release candidate 3
by Timo Sirainen 14 Jun '07

14 Jun '07

http://dovecot.org/tmp/dovecot-1.0.1rc3.tar.gz Looks like I managed to do a lot of changes today. So I'll wait a few more days before v1.0.1 release. The important changes since rc2: + deliver: Added -e parameter to write rejection error to stderr and exit with EX_NOPERM instead of sending the rejection by executing sendmail. + dovecot --log-error logs now a warning, an error and a fatal - APPEND / SEARCH: If internaldate was outside valid value for time_t, we returned BAD error for APPEND and SEARCH never matched. With 64bit systems this shouldn't have happened. With 32bit systems the valid range is usually for years 1902..2037. See ChangeLog for more.

8 9

[Dovecot] Updating Folders in Mail box
by Wade Smart 13 Jun '07

13 Jun '07

Im looking on the dovecot documentation about how to update the folder structure. I had some computer problems so I back up my mail and when I reinstalled I got rid of a bunch of unused old mail. But now when I open my mail client it still things all of those folders are still there. Im looking for how to update the file on what is and isnt there. wade

5 5

[Dovecot] Domain part / auth_username_format
by Robert Coup 13 Jun '07

13 Jun '07

Hey folks, I want to authenticate a pop3 user without a domain part and then use the domain part to specify a Maildir subfolder to grab messages from. So, this was my attempt: # use the domain part to access a subfolder mail_location = maildir:/mail/%n/Maildir/%d # strip of the domain part for authentication purposes auth_username_format = %n login: testuser@.INBOX.SubFolder Authentication of testuser works great, but mail_debug shows me that the domain-part (%d) is empty when expanding mail_location. Any bright ideas? Rob :) [ Dovecot 1.0.rc15, Debian Sarge, PAM auth. ]

2 2

[Dovecot] No auto-conversion of .customflags?
by Christian Balzer 13 Jun '07

13 Jun '07

Hello, I'm in the process of migrating 0.99 dovecot maildir boxes to a pair of new machine. These servers were running the stable (etch) 1.0rc15 package of dovecot until yesterday and existing .customflags files were correctly converted to dovecot-keywords. Yesterday I upgraded to the (finally, thanks to who did this) 1.0.0 etch backports package and since then freshly migrated boxes get this error: --- Jun 12 09:48:06 mb11 dovecot: IMAP(username): stat(/longandboringpath/username/.customflags/cur) failed: Not a directory --- Firstly, I thought Linux was one of the OS' that had a free dir stat, but I guess I could have just hallucinated that. But more importantly, obviously .customflags does NOT get converted anymore and thus shows up in IMAP LIST commands. Since I doubt that the backport people did change anything in the code I suppose that this is a genuine 1.0.0 problem which probably should be addressed for the upcoming 1.0.1 release. Regards, Christian -- Christian Balzer Network/Systems Engineer NOC chibi(a)gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/

2 3

[Dovecot] 1.0.1 release candidate 2
by Timo Sirainen 13 Jun '07

13 Jun '07

I'll release v1.0.1 in a day or two, but it would be nice to get some testing before the release to see if I managed to break something after the Mercurial conversion. And did I forget something that should be fixed for v1.0.1? http://dovecot.org/tmp/dovecot-1.0.1rc2.tar.gz Changes since v1.0.0: * deliver: If Return-Path doesn't contain user and domain, don't try to bounce the mail (this is how it was supposed to work earlier too) * deliver: %variables in mail setting coming from userdb aren't expanded anymore (again how it should have worked). The expansion could have caused problems if paths contained any '%' characters. + Print Dovecot version number with dovecot -n and -a - Trying to start Dovecot while it's already running doesn't anymore wipe out login_dir and break the running Dovecot. - maildir: Fixed "UID larger than next_uid" errors which happened sometimes when dovecot-uidlist file didn't exist but index files did (usually because mailbox didn't have any messages when it was selected for the first time) - maildir: We violated maildir spec a bit by not having keyword characters sorted in the filename. - maildir: If we don't have write access to cur/ directory, treat the mailbox as read-only. This fixes some internal error problems with trying to use read-only maildirs. - maildir: Deleting a symlinked maildir failed with internal error. - mbox: pop3_uidl_format=%m wasn't working right - mbox: If non-filesystem quota was enabled, we could have failed with "Unexpectedly lost From-line" errors while saving new messages - mysql auth: %c didn't work. Patch by Andrey Panin - COPY: We sent "Hang in there.." too early sometimes and checked it too often (didn't break anything, but was slower than needed). - deliver: Postfix's sendmail binary wasn't working with mail_debug=yes - Don't corrupt ssl-parameters.dat files when running multiple Dovecot instances. - Cache compression caused dovecot.index.cache to be completely deleted with big endian CPUs if 64bit file offsets were used (default) - Fixed "(index_mail_parse_header): assertion failed" crash

5 12

[Dovecot] Help with new syslog errmsgs
by Stewart Dean 12 Jun '07

12 Jun '07

I am bringing more people onto Dovecot...and am beginning to see syslog error messages I've never seen before...what are they/are they critical? 1 =========================== > Jun 12 09:53:21 mercury mail:err|error dovecot: IMAP(gregory): Corrupted index c > ache file /var/dcndx/gregory/.imap/INBOX/dovecot.index.cache: indexid changed This has the same date stamp as the user's change date on his .subscriptions...which he created by copying his UWIMAP .mailboxlist from a login prompt. Is this what happens when the user with active sessions overwrites/creates the .subscriptions file? 2 =========================== > Jun 12 11:32:36 mercury mail:err|error dovecot: IMAP(gregory): UIDVALIDITY chang > ed (1100532544 -> 1178155834) in mbox file /home/hcrc/gregory/mail/Sent Have no idea what this is about...... -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 2

[Dovecot] Phantom message using mixed namespaces
by Ian R. Justman 12 Jun '07

12 Jun '07

Hi, all. At home, I have a mailbox where mbox is the default (for inbox and some smaller mailboxes) and all my lists are in a Maildir format. I'm building a mailstore server at work where I want to use Maildir as the default mailstore, but I want to keep mbox on the side to aid in archiving messages. My configs are as follows for mail location and namespaces: Home: mail_location = mbox:~/mail:INBOX=/var/mail/%u namespace private { separator = / inbox = yes hidden = no prefix = "mbox/" location = mbox:~/mail:INBOX=/var/mail/%u } namespace private { separator = / prefix = "Maildir/" location = maildir:~/Maildir } Work: mail_location = maildir:~/Maildir namespace private { separator = / inbox = yes prefix = "Maildir/" location = maildir:~/Maildir } namespace private { separator = / hidden = no prefix = "mbox/" location = mbox:~/mail } Here's the thing: My home mailbox server looks the way it should, offering me "mbox" and "Maildir" names to expand for more mailboxes. Work on the other hand, by and large, works as well (in fact, I based its config on the home machine's config with some slight changes). However, strange things started happening the moment I did a "mkdir ~/mail" while I was at the machine's prompt to make ready for an mbox repository. My mail program nearly immediately shows a "phantom message" in the main inbox. If I try to select this "phantom message", the mailer goes into a very tight loop (I've tried this with Seamonkey and T'bird with the same results. I get cycles of these in the log: Jun 12 11:29:14 (censored) dovecot: imap-login: Login: user=<xxxx>, method=PLAIN, rip=x.x.x.x, lip=y.y.y.y Jun 12 11:29:14 (censored) dovecot: IMAP(xxx): FETCH for mailbox INBOX UID 3 got too little data: 0 vs 512 Jun 12 11:29:14 (censored) dovecot: IMAP(xxxx): Disconnected: Disconnected I'm running the Dovecot 1.0.0 under FreeBSD 4.11 (work) (I can't run anything later on this machine, strangely enough; I haven't tried any of the later releases since updating the BIOS recently, however) and 1.0.rc17 under Ubuntu Feisty (home). If I need to provide more info, please let me know. I'd also be interested to know if it's something dumb I'm doing or if it perhaps may be a bug. Thanks! --Ian.

2 2

[Dovecot] New experimental XEXEC plugin status
by Marc Perkel 12 Jun '07

12 Jun '07

No to long ago I proposed an experimental extension to the IMAP protocol to allow IMAP to execute extername server side code and talk to email plugins to create custom client/server applications over an existing authenticated IMAP connection. I am happy to say they we have working code. It's not quite ready to download yet but we do have some life happening. I have started to document it on the Dovecot wiki here. http://wiki.dovecot.org/Plugins/xexec I'm looking to see if I can generate some interest in this. XEXEC Plugin XEXEC is an experimental non-standard extension to the IMAP protocol that allows you to run and server side application and have it communicate with email plugins (Thunderbird) allowing custom client/server applications to communicate over an existing authenticated IMAP channel. The email client sends the XEXEC command with the name of the server side module that it wishes to run along with parameters to pass to the server. Here are some examples: XEXEC blacklist add joe(a)example.com XEXEC whitelist del joe(a)example.com XEXEC changepassword MyNewPassword XEXEC forwardmail myaccount(a)yahoo.com Uses for XEXEC The XEXEC can be used to run anything but in theory it should be used for client server applications that relate to email or groupware applications like calendars and contact lists. Its main purpose is to allow email clients to set server side settings over the existing authenticated channel without having the user have to log in separately using a different application to control user settings. Examples of possible usage includes: * Setting server side white lists and black lists * Changing the password for the email account * Allowing users to set email forwarding preferences * Allowing users to set vacation messages * Allowing users to exclude email from specific countries or language character sets * Allowing users to control server side spam filter settings * Server Side Calendar and Group Contact Applications like MS Exchange has * SMTP over IMAP for sending outgoing email without separate SMTP settings * Setting rules for server side folder delivery. * Setting text message alerts to cell phones for important email notification Wouldn't it be nice if you could change your email password i your email client and have it set the new password on the server at the same time? This would eliminate the need to change the server and client passwords separately. Or imagine sending outgoing email without having to configure SMTP. You just set up the incoming email and the outgoing email works as well. Or wouldn't you like to do some of the fancy tricks that Microsoft Exchange Servers do without having to use Exchange? It is our hope that this experimental protocol will lead to significant expansion of IMAP functionality. About this Plugin This plugin is the idea of Marc Perkel of Junk Email Filter <http://www.junkemailfilter.com> who hired Nicolas Boullis ( nicolas.boullis(a)free.fr <mailto:nicolas.boullis@free.fr>) to write the code. I (Marc Perkel marc(a)perkel.com <mailto:marc@perkel.com>) am trying to get the concept out there in some sort of working form with the idea that it will catch on. Hopefully other people who find this concept useful will build on the idea, do it right, and perhaps some variation of this concept will eventually become a standard. Status This plugin is a nonstandard experimental extension to the IMAP protocol. It is offered as a proof of concept and it is my hope that it will catch on in some form and make it into the IMAP officially. At this point there is nothing on the client side to talk to anything on the server side. So this code is presently useless until more development is done. Configuration To activate and configure this plugin you have to first add it to your dovecot.conf file. You can do so as follows: protocol imap { mail_plugins = xexec } Then to add applications you specify the module name and map it to a server side executable program. xexec = module:executable Here are some examples: plugin { xexec = blacklist:/usr/local/dovecot/blacklist.sh %u xexec2 = whitelist:/usr/local/dovecot/whitelist.sh %u xexec3 = average:/usr/local/dovecot/average xexec4 = smtp:/usr/local/dovecot/smtp } The idea is that the module name will be a reference to an executable and will hide what is happening on the server. When the command XEXEC module <parameters> is passed then the server will run the executable and pass the parameters to the executable. Interacting with XEXEC A typical session with XEXEC might look like this. * OK Dovecot ready. 001 login marc(a)perkel.com password 001 OK Logged in. 002 xexec blacklist add joe(a)example.com * OK Adding joe(a)example.com to server side blacklist for marc(a)perkel.com 002 OK command exited successfully 003 xexec changepassword MyNewPassword * OK New Password set Sucessfully for marc(a)perkel.com 003 OK command exited successfully Many of the details of how everything will work under different conditions have yet to be developed. Download and Installation Coming Soon! License This software and the concepts behind is are free. No patent or copyrights are asserted on the concept. This is a gift to the world community. Code is released under GPL2. Help Needed We could use some help with this project. We haven't even started writing any client side code. We are looking for sharp people with good ideas to help develop this concept in a way that will eventually lead to becoming part of the standard. We envision that certian commands to do ordinary universal stuff (password, smpt, whit list, black list, forwarding) will become standardized so that features to set server side settings can become part of standard email applications.

1 0

[Dovecot] Warning about NFS but using local fs for INDEX
by Herbert Gasiorowski 12 Jun '07

12 Jun '07

I am playing around with dovecot and want to use local filesystem for indexing. But whenever I open a new imap connection the following warning is shown: Apr 30 10:14:42 beira dovecot: Mailbox indexes in /app/home/gasi are in NFS mount. You must set mmap_disable=yes to avoid index corruptions. If you're sure this check was wrong, set nfs_check=no. /app/home is a NFS mounted filesystem, but I want dovecot to use /export/dovecot/gasi for indexing (See namespaces below). I shurely can follow the hints(nfs_check=no), but I am not shure if I did something wrong or maybe someday will change the configuration and forget to enable the nfs check. dovecot version: dovecot-1.0-1.2.rc15.el5 on CentOS 5.0 (with all updates). [root@beira etc]# dovecot -n # /etc/dovecot.conf syslog_facility: local6 login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 namespace: type: private separator: / location: mbox:~/Mail:INBOX=/var/spool/mail/%u:INDEX=/export/dovecot/%u inbox: yes namespace: type: private separator: / prefix: #home-tmp/ location: mbox:~:INDEX=/export/dovecot/%u auth default: passdb: driver: pam args: imap userdb: driver: passwd

2 2

[Dovecot] error in logfile
by Luigi Rosa 12 Jun '07

12 Jun '07

With Dovecot 1.0.0: May 11 12:16:35 mail dovecot: IMAP(xxx): stat(/var/spool/mail2/xxx/.Trash.Squid-it/new) failed: No such file or directory With Thunderbird 2.0 IMAP client: * user deleted the mailbox * TB moved the mailbox to Trash * user asked TB to empty Trash * the above message appeared No warning/error was reported bt TB to user. I don't think it's an error and should not be logged. Ciao, luigi -- / +--[Luigi Rosa]-- \ You can tune a radio, but you can't tuna fish.

2 1

[Dovecot] Getting rid of the common newbie problems
by Timo Sirainen 12 Jun '07

12 Jun '07

I think the most common Dovecot newbie problems are: - Not looking at the (correct) logs for errors - Authentication problems - Mail location problems - Mail permission problems Below are some of my ideas how I could stop people from asking these questions with future Dovecot (v1.1+) releases. Suggestions welcome. Distribution people especially should say if they're against some change. * Logging The log file problem is the most annoying one, because a lot of the other problems can be solved once the admin figures out that Dovecot is actually giving useful error messages. Often the admin is only looking at the log file where "info" messages go (eg mail.log) because Dovecot logs its startup message and login messages there, but not where the errors go (eg mail.err). This has happened even with people who in general are experienced sysadmins. Logging to eg. /var/log/dovecot.log by default would be helpful here, but it's probably better to log via syslog by default. Cyrus logs to "local6" by default. Perhaps for Dovecot v1.1 I should make that the default too? Looks like in my Debian system the info messages then go to both /var/log/messages and /var/log/syslog. Error messages only go to /var/log/syslog. So there still isn't by default a single log file where the errors are logged, but it might help a bit. * Authentication Authentication problems can usually be solved by telling the user to set auth_debug_passwords=yes and looking at the logs. I'm not sure if there's anything that can be helped in here. Except the logging message could be updated a bit: "Aborted login: user=<asdga>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, 1 failed authentications" So the last "n failed authentications" could be added, where n could also be 0. Another possibility would be to make Dovecot remember if there have been any successful logins (/var/lib/dovecot/success file) and if not, give a bit more helpful error messages: - Client gets: "NO Authentication failed. Refer to server log for more information." instead of the normal "NO Authentication failed." - Log contains: "Aborted login: user=<asdga>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, 1 failed authentications (set auth_debug_passwords=yes to debug the problem)" I'm not sure if this is a good idea. * Mail location It seems to be difficult for some people to set mail_location. I don't know if anything can be done before Dovecot v2.0 where I'll split it to multiple settings, such as: driver = maildir root_dir = ~/Maildir index_dir = /var/indexes/%u Another problem that seems to be difficult to understand is why the mail directory contains "HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB". The whole userdb concept appears to be weird. This could anyway be fixed by giving an error message earlier and failing the login with internal error. Probably the best place to give the error message would be already in the userdb lookup in dovecot-auth, but that would require that doveoct-auth knows if the home directory is really needed, and to give a useful error message it would also need to tell where it's tried to be used (mail_location, or some namespace's location, or ..). Probably too much trouble to be worth it. So the next best thing is to give the error when it's used: "Home directory is used in mail_location, but userdb didn't return a home directory" It would be nice if it didn't say userdb, but rather the userdb's name. I guess that would be possible if dovecot-auth told master (or deliver) which userdb was used, but that would normally be just extra overhead. * Mail permissions If mail location is difficult for some, then the concept of UIDs are how they're used in Dovecot is pretty much impossible for some to understand. One of the problems is that there exists "dovecot" user. So people think that their mails should be owned by the dovecot user. Although I've mentioned in everywhere I can think of that this should not be done, it won't help because either people won't read the pages or even if they do, they somehow still fail to ignore it even though it's written in bold. So unless people (and most importantly, distributions) are against it, I think the "dovecot" user should be renamed. "dovelogin" perhaps. In future I might split dovecot-auth even more, and then I would like to create a "doveauth" user as well. Another possibility would be to drop the dovecot user completely and instead use "nobody". That would mean that other nobody processes could kill Dovecot's login processes, but that's pretty much it. Once people understand that "dovecot" isn't the right user, they hit the next problem: "How do I tell Dovecot to run as vmail user?" I can paste links to wiki pages or tell them to "make userdb return uid=vmail", but that just doesn't seem to get through. There needs to be an easier way, and I think I figured out what it is: Add new "mail_uid" and "mail_gid" settings to dovecot.conf. Deprecate user_global_uid/gid in dovecot-ldap.conf and make all the userdbs mention that the uid/gid returned by userdb can be used to override the global mail_uid/gid. Perhaps also add "mail_home" template. This change makes it unnecessary to have a userdb configured at all. - "How do I tell Dovecot to run as vmail user?" - "Set mail_uid = vmail" in dovecot.conf - "Thanks"

10 36

[Dovecot] Dovecot LDA and address extensions
by Tom Metro 12 Jun '07

12 Jun '07

I'm converting over a virtual user installation that used Postfix and maildrop with a MySQL back-end for mailbox lookups to use Dovecot LDA. The maildrop setup used a database table like: +-------------------------+--------+-------------+--------------------+ | address | owner | domain | mailbox | +-------------------------+--------+-------------+--------------------+ | postmaster(a)example.com | tmetro | example.com | .admin.postmaster/ | | root(a)example.com | tmetro | example.com | .admin.root.lex/ | | tmetro(a)example.com | tmetro | example.com | .INBOX/ | | tmetro+spam(a)example.com | tmetro | example.com | .spam.tmetro/ | [...] where maildrop was handed ${recipient} from postfix, and it queries the above table matching ${recipient} to the address column, getting back the expression CONCAT_WS('/','/var/mail',domain,owner) as the home directory, and CONCAT_WS('/','/var/mail',domain,owner,mailbox) as the mailbox. The UID/GID are fixed, as this is a virtual user setup. So looking up the mailbox for the user postmaster(a)example.com returns: /var/mail/example.com/tmetro/.admin.postmaster/ Currently I'm using a static user database with Dovecot. This SQL appears to replicate the maildrop setup: user_query = SELECT CONCAT_WS('/','/var/mail',domain,owner) as home, CONCAT_WS('/','maildir:/var/mail',domain,owner,mailbox) as mail, 5000 as uid, 5000 as gid FROM vmbx2 WHERE userid = '%u' And this works for mail deliveries. The problem with this is that not only is a database lookup overkill for the IMAP server, as the root mail location for IMAP users follows a simple pattern adequately represented by the static userdb, it also breaks IMAP, because the returned 'mail' overrides mail_location, (currently set to maildir:/var/mail/%d/%n/), so for user tmetro(a)example.com it returns: maildir:/var/mail/example.com/tmetro/.INBOX/ instead of: maildir:/var/mail/example.com/tmetro/ (which is the same as the home directory). Can the "userdb sql" directive be added to the "protocol lda" section? Or perhaps instead create a new "auth lda" section, and move the "userdb sql" and "socket listen" directives to that section? The second issue is how to best deal with address extensions, something that wasn't fully implemented in the maildrop setup. Ideally I'd like a setup where a lookup is first performed for user+ext@domain, and if it fails to return a mailbox, then lookup user@domain. Assuming Dovecot can handle a multi-row query result (grabbing the first record and ignoring the rest), this can probably be hacked using an appropriate WHERE expression. But the difficulty is getting the address components. Postfix will provide them, but Dovecot's deliver doesn't seem to have a way of receiving them and passing them on to the user query. The example LDA setup shown here: http://wiki.dovecot.org/LDA/Postfix suggests passing the extension as an argument to the mailbox (-m) switch. But this assumes that one wants a one-to-one direct mapping between extensions and mailbox names. I suppose I could switch from: -d ${user}@${nexthop} to: -d ${recipient} and add even more complexity to the SQL to parse out the extension. But I'd rather avoid embedding the extension separator character in the SQL, and would rather eliminate it from the database as well. Maybe Sieve is the answer. I presume the argument to -m could be inspected in a Sieve script, which could then map to the desired target mailbox. The non-IMAP users (like postmaster(a)example.com) could be reimplemented as aliases that redirect to a user+ext(a)example.com address for the user responsible for that domain. But using Sieve scripts for extension to mailbox mappings seems far less elegant than using a database. Maybe I need to wedge a wrapper program between Postfix and deliver that will accept the address components from postfix, perform the lookup, and convert the results into a -d argument pointing to the "owner" (see table above) and a -m argument pointing to the mailbox. On a side note... When I used this command in postfix's master.cf: /usr/lib/dovecot/deliver -d ${user}@${nexthop} -n -m ${extension} as recommended in the wiki, the following error gets logged: ... status=bounced (command line usage error. Command output: Fatal: Unknown argument: -d Usage: deliver [-c <config file>] [-d <destination user>] [-m <mailbox>] [-f <envelope sender>] ) which doesn't make a lot of sense. I suspect what it is trying to say is that it didn't like something about the argument to the -d switch. Maybe that should be ${domain} instead of ${nexthop}. (What's up with all the whitespace between "[-m <mailbox>]" and "[-f <envelope sender>]"? Also, might be a good idea to have deliver always write errors - even startup errors - to the specified logging facility, given that not all programs that launch it will report what it writes to STDERR. I notice most postfix commands - even the ones people interact with - log errors.) I ended up switching to -d ${recipient} to emulate the old maildrop setup for now, and that worked fine. The sample dovecot.conf has: ## dovecot-lda specific settings ## # socket listen { # master { # path = /var/run/dovecot/auth-master I uncommented the first two lines, but left the 'path' directive commented, under the assumption that the comment was showing the default. But without it uncommented, the socket doesn't get created. This is an inconsistency compared to how defaults are shown elsewhere in dovecot.conf. -Tom

2 1

[Dovecot] vpopmail quota
by Onno Molenkamp 12 Jun '07

12 Jun '07

Hi, I'd like the vpopmail user database to return the quota settings for users, instead of having to rely on the validity of the maildirsize files. It doesn't look like this is currently possible. Would simply adding a auth_stream_reply_add call for "quota" with a suitable value in vpopmail_lookup be sufficient to make this work? (the quota can be read from the pw_shell field of the vqpasswd struct) Onno

2 3

[Dovecot] Date error bug
by Bgs 12 Jun '07

12 Jun '07

Hi all, I encountered a bug, that prevents me from moving mail and as a side effect it messes up all thunderbird/mozilla mail clients (they won't do any message copy/move until I restart them). Here is the info and the header of the mail that produces the error (a spam mail): Dovecot version: 1.0.0 Mail header: Return-Path: <xxdwwu(a)boboakes.com> Delivered-To: bgs-hu-bgs(a)bgs.hu Received: (qmail 10895 invoked from network); 7 Jun 2007 16:51:21 -0000 Received: from unknown (HELO 86.109.208.58.broad.sz.js.dynamic.163data.com.cn) (58.208.109.86) by 0 with SMTP; 7 Jun 2007 16:51:21 -0000 Received: from [58.208.109.86] by INBOUND.BOBOAKES.COM.NETSOLMAIL.NET; Tue, 15 May 2085 16:51:38 -0800 From: Nigel <xxdwwu(a)boboakes.com> To: <bgs(a)bgs.hu> Subject: explore this offer Date: Tue, 15 May 2085 16:51:38 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_021F0ADE.78E00150" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: Aca6Q09K1THIO7J1RUMI4LVVDU6VQF== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 . Message-ID: <021f0a9b$6abcc150$566dd03a@xxdwwu> Attached is the error window with the actual error message. It seems that the year 2085 date is not handled but dovecot. Regards Bgs PS: Probably unrelated but here are the other infos: Linux, local XFS, AMD Athlon XP, clients Seamonket 1.1.1 and Thunderbird 2.0.0.0

2 2

[Dovecot] SEGV when user over filesystem quota and "Move to Trash"
by Steffen Kaiser 12 Jun '07

12 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've configured Dovecot v1.0.0 with filesystem quota and to use hardlinks. Latter I use intentionally to save disk space and to achieve that an user can delete mails even if over quota and using the "Delete to Trash" feature. The following happens, when the directory file of .Trash/* fills up and would need to be expanded, but fails because of an over-quota condition. The crash is not so problematic, because you can wait some time (I guess until the lock of .Trash/dovecot-uidlist.lock expires) and you can delete mails from Trash to make room. However, there are leftover files in .Trash/tmp, what may make problems. First you get a "Out of quota" error in the MUA, maybe a second or a third time, too. Then: dovecot: Jun 12 09:10:38 Info: IMAP(dvtest) [3492]: copy -> Trash: uid=500, msgid=<cs-HoeqDW06gzBNu-9HdUBR4A@> dovecot: Jun 12 09:10:38 Error: child 3492 (imap) killed with signal 11 When you try to delete another mail: process #1: nanosleep({0, 158957000}, NULL) = 0 lstat64("/var/cache/dovecot/31045/control/.Trash/dovecot-uidlist.lock", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0 time(NULL) = 1181630732 nanosleep({0, 170189000}, NULL) = 0 lstat64("/var/cache/dovecot/31045/control/.Trash/dovecot-uidlist.lock", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0 time(NULL) = 1181630732 process #2: gettimeofday({1181630713, 945424}, NULL) = 0 poll([{fd=4, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=2, events=POLLERR|POLLHUP|POLLNVAL}, {fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 3, 9335) = 0 gettimeofday({1181630723, 281935}, {4294967176, 0}) = 0 gettimeofday({1181630723, 282014}, NULL) = 0 poll([{fd=4, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=2, events=POLLERR|POLLHUP|POLLNVAL}, {fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 3, 9999) = 0 gettimeofday({1181630733, 281949}, {4294967176, 0}) = 0 gettimeofday({1181630733, 282149}, NULL) = 0 .Trash/tmp contains 28 items (growing) After the "Connection timeout" error in the client process #1 still loops repeatedly. Eventually the processes stops. Maybe it is waiting for the release of the lock by the process killed by segv? Finally it dumps core, too. dovecot: Jun 12 09:10:38 Info: IMAP(dvtest) [3821]: copy -> Trash: uid=500, msgid=<cs-HoeqDW06gzBNu-9HdUBR4A@> dovecot: Jun 12 09:12:39 Error: child 3821 (imap) killed with signal 11 Core was generated by `imap [dvtest 10.20.10.63]'. Program terminated with signal 11, Segmentation fault. #0 maildir_sync_get_keywords_sync_ctx (ctx=0xffffffff) at maildir-sync.c:242 242 { (gdb) bt #0 maildir_sync_get_keywords_sync_ctx (ctx=0xffffffff) at maildir-sync.c:242 #1 0x0806ddd4 in maildir_mf_get_path (ctx=0x0, mf=0x20) at maildir-save.c:263 #2 0x0806de80 in maildir_transaction_unlink_copied_files (ctx=0x80fcbb0, pos=0x0) at maildir-save.c:477 #3 0x0806e5cb in maildir_transaction_save_commit_pre (ctx=0x80fcab0) at maildir-save.c:561 #4 0x080693c4 in maildir_transaction_commit (_t=0x8101eb8, flags=0) at maildir-transaction.c:28 #5 0xb7ddbbd0 in quota_mailbox_transaction_commit (ctx=0x8101eb8, flags=0) at quota-storage.c:74 #6 0x08057965 in cmd_copy (cmd=0x80df0f0) at cmd-copy.c:124 #7 0x0805b1be in cmd_uid (cmd=0x80df0f0) at cmd-uid.c:19 #8 0x0805b728 in client_handle_input (cmd=0x80df0f0) at client.c:335 #9 0x0805b7b7 in client_handle_input (cmd=0x80df0f0) at client.c:389 #10 0x0805be3c in _client_input (context=0x80df0a8) at client.c:432 #11 0x080bc902 in io_loop_handler_run (ioloop=0x80dc9b0) at ioloop-poll.c:199 #12 0x080bbb58 in io_loop_run (ioloop=0x80dc9b0) at ioloop.c:326 #13 0x08063e80 in main (argc=Cannot access memory at address 0x0 ) at main.c:290 I also managed it to have to two processes waiting for /var/cache/dovecot/31045/control/.Trash/dovecot-uidlist.lock. dovecot -n: # /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log protocols: imap imaps pop3 pop3s ssl_ca_file: /etc/ssl/certs/ca.crt ssl_cert_file(default): /etc/ssl/certs/imap.pem ssl_cert_file(imap): /etc/ssl/certs/imap.pem ssl_cert_file(pop3): /etc/ssl/certs/pop3.pem ssl_key_file(default): /etc/ssl/private/imap.key ssl_key_file(imap): /etc/ssl/private/imap.key ssl_key_file(pop3): /etc/ssl/private/pop3.key disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot//login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_log_format_elements: %p: user=<%u> method=%m rip=%r lip=%l %c verbose_proctitle: yes first_valid_uid: 1000 mail_location: maildir:%h/MailDir:CONTROL=/var/cache/dovecot/%i/control:INDEX=/var/cache/dovecot/%i/index mail_debug: yes dotlock_use_excl: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/rawlog /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/rawlog /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_log zlib mail_plugins(imap): quota imap_quota mail_log zlib mail_plugins(pop3): quota mail_log mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 mail_log_prefix: %Us(%u) [%p]: mail_log_max_lines_per_sec: 0 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %u pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): oe-ns-eoh namespace: type: private separator: . inbox: yes hidden: yes auth default: mechanisms: plain login cache_size: 10 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890 verbose: yes debug: yes passdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf userdb: driver: passwd-file args: /etc/passwd socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 432 group: mail plugin: quota: fs Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRm5VCi9SORjhbDpvAQLDQwgAp0Zcg4SbTXXyFTUFVsxRHjhRr1V2ZuoE Ajpar7u5hoG8IfJ8u6noxk2XvNlD0rL0g/oXHJDeRTuZs6PVwcQpSEyQ0DNUx8BY bUyX5i3sR02MOrwbKvlq6ynvV3VE5PY4fpgCfqUv7ZE4W72u577IQ4l/C3+hgC+Y qzKw2URlVzoJj6apyXEIZcv4gvxkxl4mMtOmoXrTj5nMfz7EFbbuXuK9aYfFhLFp YB/Q0FxsU3YylpYYbFGronbmrAUGb2TCJckRAwDdTzT1s++6uvbJt5BLRnwiOK6H UAEuJJllwoDcwx0WIwMzf3SXP52OSqHdEVBuJprxpHrTI7Fe2fm5FA== =WkkL -----END PGP SIGNATURE-----

2 2

[Dovecot] Cannot get cmusieve to work
by Dani 12 Jun '07

12 Jun '07

Hi, # I messed with the identities in my MUA and sent the email with a non registered address, sorry for the incinvenience ## I'm not able to make cmusieve to work to filter emails. Below is my configuration. I'm using a .dovecot-sieve example from the wiki: require "fileinto"; if exists "X-Spam-Flag" { fileinto ".Junk/"; } I've been following (as acurately as I could) the documentation, tuts and examples. I found this in the dovecot list: http://www.dovecot.org/list/dovecot/2007-March/020674.html and I used the CONCAT method but anyway mails don't filter because of two "//". *********LOGS******** Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): Loading modules from directory: /usr/lib/dovecot/modules/lda Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): Module loaded: /usr/lib/dovecot/modules/lda/lib90_cmusieve_plugin.so Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: dani(a)exampledomain.org Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: maildir=dani(a)exampledomain.org/ Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: uid=110 Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: gid=8 Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: home=/home/vmail/exampledomain.org/dani@exampledomain.org/ Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): maildir: data=/home/vmail/exampledomain.org/dani@exampledomain.org Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): maildir: root=/home/vmail/exampledomain.org/dani@exampledomain.org, index=/home/vmail/exampledomain.org/dani@exampledomain.org, control=, inbox= Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): cmusieve: Using sieve ****path: /home/vmail/exampledomain.org/dani(a)exampledomain.org//.dovecot.sieve*** Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): msgid=<20070612110825.F38F61054E8(a)sc8-sf-spam1.sourceforge.net>: saved mail to INBOX I've been looking into the problem and I must have forget something obvious, but I cannot make it work. does anyone can point me to the problem? thanks in advance. Dani CONFIGS ************** dovecot --version 1.0.0 (debian) ************** ******************** # /etc/dovecot/dovecot.conf protocol lda { postmaster_address = postmaster(a)exampledomain.org mail_plugin_dir = /usr/lib/dovecot/modules/lda sendmail_path = /usr/lib/sendmail auth_socket_path = /var/run/dovecot/auth-master mail_plugins = cmusieve } *************** dovecot-sql.conf *************driver = mysql connect = dbname=postfix user=postfix password=qwe123dsazxc port=3306 host=localhost default_pass_scheme = CRYPT password_query = SELECT password FROM mailbox WHERE username ='%u' user_query = SELECT maildir, 110 AS uid, 8 AS gid, CONCAT('/home/vmail/%d/', @home := maildir) AS home FROM mailbox WHERE username = '%u

2 2

[Dovecot] per mailbox maildir format
by Bgs 12 Jun '07

12 Jun '07

Hi all, Is it possible to set the maildir format at mailbox level? I'd like to us Maildir++ for most of my clients, but want to emulate the other one for one of my users. Can this be done with dovecot? Thanks Bgs

2 2

[Dovecot] how to create new user account
by santhosh 12 Jun '07

12 Jun '07

Hi, I am using dovecot1.0.0. How to create new user in dovecot ? Thanks in advance Regards, Santhosh

3 2

[Dovecot] difference b/w user and login_user
by santhosh 12 Jun '07

12 Jun '07

Hi, Can any one tell what is the difference between user and login_user in dovecot.conf file ? Thanks in advance Regards, Santhosh

2 1

[Dovecot] Can't send/receive mail from other domain
by Jeremy Gillick 12 Jun '07

12 Jun '07

I've followed the instructions ( http://wiki.dovecot.org/DovecotLDAPostfixAdminMySQL) to setup Dovecot with MySql and Postfix but cannot receive from (or send mail to) other domains. FYI: email messages are supposed to be stored under /var/mail/mozmonkey.com/<user>/ Directory Permissions: drwxr-xr-x 5 vmail mail 4096 May 10 12:57 mozmonkey.com OS: Linux, Fedora 4 Dovecot version: 1.0.0 --------- CONFIG START --------- $ sudo dovecot -n # /etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 imaps pop3s ssl_listen: [::] login_dir: /var/run/dovecot//login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no first_valid_uid: 101 last_valid_uid: 101 mail_extra_groups: mail mail_location: maildir:/var/mail/%d/%u mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: mechanisms: plain digest-md5 cram-md5 user: nobody debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/sql.conf userdb: driver: sql args: /etc/dovecot/sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: vmail group: mail master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: mail --------- CONFIG END --------- --------- LOG START (modified email address to prevent spam) --------- Jun 10 22:48:23 mozmonkey postfix/smtpd[27592]: connect from n9.bullet.re3.yahoo.com[68.142.237.94] Jun 10 22:48:23 mozmonkey postfix/trivial-rewrite[27595]: warning: do not list domain mozmonkey.com in BOTH mydestination and virtual_mailbox_domains Jun 10 22:48:23 mozmonkey postfix/smtpd[27592]: C0093210021: client= n9.bullet.re3.yahoo.com[68.142.237.94] Jun 10 22:48:23 mozmonkey postfix/cleanup[27599]: C0093210021: message-id=< 568874.40698.qm(a)web57505.mail.re1.yahoo.com> Jun 10 22:48:23 mozmonkey postfix/qmgr[27282]: C0093210021: from=< jeremymailing123(a)yahoo.com>, size=2242, nrcpt=1 (queue active) Jun 10 22:48:23 mozmonkey postfix/trivial-rewrite[27595]: warning: do not list domain mozmonkey.com in BOTH mydestination and virtual_mailbox_domains Jun 10 22:48:23 mozmonkey postfix/local[27600]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled Jun 10 22:48:23 mozmonkey postfix/smtpd[27592]: disconnect from n9.bullet.re3.yahoo.com[68.142.237.94] Jun 10 22:48:23 mozmonkey postfix/local[27600]: C0093210021: to=< jerxyz(a)mozmonkey.com>, relay=local, delay=0.27, delays=0.2/0.03/0/0.04, dsn= 5.2.0, status=bounced (cannot update mailbox /var/mail/jerxyz for user jerxyz. cannot open file: Permission denied) Jun 10 22:48:24 mozmonkey postfix/cleanup[27599]: 041A7210033: message-id=< 20070611054824.041A7210033(a)mozmonkey.com> Jun 10 22:48:24 mozmonkey postfix/qmgr[27282]: 041A7210033: from=<>, size=4181, nrcpt=1 (queue active) Jun 10 22:48:24 mozmonkey postfix/bounce[27602]: C0093210021: sender non-delivery notification: 041A7210033 Jun 10 22:48:24 mozmonkey postfix/qmgr[27282]: C0093210021: removed Jun 10 22:48:24 mozmonkey dovecot: auth(default): master in: USER 1 jeremymailing(a)yahoo.com service=deliver Jun 10 22:48:24 mozmonkey dovecot: auth-worker(default): sql( jeremymailing(a)yahoo.com) SELECT concat('/var/mail/', maildir) as home, concat('maildir:/var/mail/', maildir) as mail, 101 AS uid, 12 AS gid, concat('dirsize:storage=', quota) AS quota FROM mailbox WHERE (username = ' jeremymailing(a)yahoo.com' OR simpleuser = 'jeremymailing(a)yahoo.com') AND active = '1' Jun 10 22:48:24 mozmonkey dovecot: auth-worker(default): sql( jeremymailing(a)yahoo.com) User not found Jun 10 22:48:24 mozmonkey dovecot: auth(default): master out: NOTFOUND 1 Jun 10 22:48:24 mozmonkey postfix/pipe[27603]: 041A7210033: to=< jeremymailing(a)yahoo.com>, relay=dovecot, delay=0.08, delays=0.02/0.03/0/0.03, dsn=5.1.1, status=bounced (user unknown) Jun 10 22:48:24 mozmonkey postfix/qmgr[27282]: 041A7210033: removed --------- LOG END --------- Thanks, Jeremy

2 1

[Dovecot] 20070605 still hanging with SSL
by David Favor 12 Jun '07

12 Jun '07

Thought this was fixed and now it's back. No help from rawlog as the hang appears prior to authentication. Notice there is around a 90 second delay before authentication fires. Let me know how to proceed debugging. Thanks. _____ Here's my config: listen: *:143 ssl_listen: *:993 ssl_cipher_list: ALL:!LOW:!SSLv2 disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/pkgs/dovecot-20070605/libexec/dovecot/imap-login login_greeting: IMAP ready. login_process_per_connection: no login_processes_count: 5 verbose_proctitle: yes first_valid_uid: 12 default_mail_env: maildir:~/Maildir mail_location: maildir:~/Maildir mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable: /usr/local/pkgs/dovecot-20070605/libexec/dovecot/rawlog \ /usr/local/pkgs/dovecot-20070605/libexec/dovecot/imap auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: shadow userdb: driver: passwd Here's a maillog snippet: Jun 11 07:50:40 net1 dovecot: Dovecot v20070522 starting up ... Immediately click on INBOX or other box and hang occurs... Jun 11 07:52:00 net1 dovecot: auth(default): client in: AUTH \ 1 PLAIN service=imap secured lip=69.94.137.124\ rip=71.155.185.14 Jun 11 07:52:00 net1 dovecot: auth(default): client out: CONT 1 Jun 11 07:52:00 net1 dovecot: auth(default): client in: CONT 1 \ AGRhdmlkAGZpcmUyM2JyaWNr Jun 11 07:52:00 net1 dovecot: auth(default): shadow(david,71.155.185.14): lookup Jun 11 07:52:00 net1 dovecot: auth(default): client out: OK 1 user=david Jun 11 07:52:00 net1 dovecot: auth(default): master in: REQUEST 1 30912 1 Jun 11 07:52:00 net1 dovecot: auth(default): passwd(david,71.155.185.14): lookup Jun 11 07:52:00 net1 dovecot: auth(default): master out: USER 1 \ david system_user=david uid=510 gid=506 home=/vhost/davidfavor.com/users/david Jun 11 07:52:00 net1 dovecot: imap-login: Login: user=<david>, method=PLAIN, \ rip=71.155.185.14, lip=69.94.137.124, TLS Jun 11 07:52:00 net1 dovecot: IMAP(david): Effective uid=510, gid=506,\ home=/vhost/davidfavor.com/users/david Jun 11 07:52:00 net1 dovecot: IMAP(david): maildir: \ data=/vhost/davidfavor.com/users/david/Maildir Jun 11 07:52:00 net1 dovecot: IMAP(david): maildir++: \ root=/vhost/davidfavor.com/users/david/Maildir, index=, control=, \ inbox=/vhost/davidfavor.com/users/david/Maildir -- Like feeling your best ever, all day, every day? Here's how... Your simple secrets are here - http://RadicalHealth.com

2 1

[Dovecot] SSL_CTX_set_info_callback problem in latest source
by David Favor 11 Jun '07

11 Jun '07

In the file ./src/login-common/ssl-proxy-openssl.c appears the code: if (verbose_ssl) SSL_CTX_set_info_callback(ssl_ctx, ssl_info_callback); It appears the SSL_CTX_set_info_callback symbol only occurs in the openssl development branch starting with 0x00909000L as this symbol is missing from openssl 0.9.8b and 0.9.8e (no check of the latest nightly snapshot of the stable 0.9.8 branch). It appears there should be a compilation guard around this code. Perhaps... #if OPENSSL_VERSION_NUMBER >= 0x00909000L if (verbose_ssl) SSL_CTX_set_info_callback(ssl_ctx, ssl_info_callback); #endif -- Like feeling your best ever, all day, every day? Here's how... Your simple secrets are here - http://RadicalHealth.com

2 4

[Dovecot] lazy_expunge and emails from Inbox, doesn't list INBOX in deleted
by Roger Binns 11 Jun '07

11 Jun '07

I'm using the dovecot available on Ubuntu Feisty (1.0rc17) and am trying to migrate from courier-imap. A really important feature for me from courier is that expunged messages end up in Trash where they are removed after 7 days. I can get an approximation of this feature as described in the documentation: namespace private { prefix = INBOX. seperator = . inbox = yes } namespace private { prefix = DELETED. seperator = . location = maildur:~/Maildir/deleted } lazy_expunge = DELETED. DELETED. DELETED. This all works fine except for messages that were deleted from the Inbox. They do end up in the right place (~/Maildir/deleted/cur) but that location is not listed as a subscribable folder. Here you can see that deleted messages from my ciontope folder show up, but not the inbox. a LIST "DELETED." * * LIST (\HasNoChildren) "." "DELETED.ciontope" a OK List completed. You can't examine the namespace itself: a EXAMINE DELETED a NO Unknown namespace. a EXAMINE DELETED. a NO Invalid mailbox name But the folder does exist: a EXAMINE DELETED.INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 4 EXISTS * 0 RECENT * OK [UIDVALIDITY 1181423860] UIDs valid * OK [UIDNEXT 5] Predicted next UID a OK [READ-ONLY] Select completed. Is there any way to convince dovecot to list DELETED.INBOX so that clients can see it an subscribe to it? Roger

3 5

[Dovecot] Multiple IP(or Host) listen in dovecot.conf.
by Yoshihiro Kawabe 11 Jun '07

11 Jun '07

Hi. Does someone make update for `Multiple IP(or Host) listen in dovecot.conf'? I made trivial patch so. But this patch doesn't solve `Support listening in multiple sockets' in TODO. It appends only the capability as multiple listen in dovecot.conf. So, `login_processes_count' becomes ambiguous. In CASE1, login_processes_count = 2, forked imap-login processes are 8. -- samples dovecot.conf applied this patch are following. CASE 1: listen = 127.0.0.1, 192.168.0.10, imap-server1, imap-server2.example.com or CASE 2: protocol imap { listen = 127.0.0.1:143, imap-server1:10143 ssl_listen = imap-server2:10943, 127.0.0.1 .. } protocol pop3 { listen = 127.0.0.1, pop-server1:10100 .. } -- Update brief. src/master/ master-setting.h: listen_fd and related members changed to array_t. also name add (s). master-setting.c: few member initialization delete. main.c: handle multiple IP and port, fds as array_t. resolve_ip argment change. login-process.h: add listen_fd and ssl_listen_fd member to login_group structre. login-process.c: add login_groups_create function for mapping login process to each listen fd. change dup2 source fd in create_login_process. src/lib network.c: change getnameinfo error value. -- Kawabe,Yoshihiro <sowhat(a)amnis.co.jp> As the stars blink in the night sky, our married hearts are never splitted. Even if we will unclasp each other hands, until we retain that. by H.S.

2 3

[Dovecot] dovecot-20070605 runtime problems
by David Favor 11 Jun '07

11 Jun '07

I've build this nightly snapshot with my installed openssl, which is 0.9.8b (Fedora 6) and the latest openssl development tree. The 20070605 version of dovecot starts up doing ssl protocol perfect, then after clicking a few directories, then when clicking back to INBOX, dovecot hangs. There is no logging info, even with --enable-debug on and all .conf file directives I can find. Doing a 'ngrep port 993' shows no SSL dialog. If I go through my same compile sequence using the dovecot-1.0.0 source all is well with both the system openssl and the latest openssl snapshot, so it appears something is wrong in the current nightly snapshot. My primary question is howto debug this hang, short of attaching gdb to the process. Any suggestions are appreciated. Thanks. I'm using the latest Thunderbird version 2.0.0.4 (20070604). I've build it using: [root@net1 dovecot-20070605]# build_dovecot mkdir -p /build/work/dovecot-20070605 cd /build/work/dovecot-20070605 unset CDPATH export CPPFLAGS='-pipe -O2 -I/usr/local/include' export LDFLAGS='-L/usr/local/lib' make distclean ./configure --prefix=/usr/local/pkgs/dovecot-20070605 --disable-nls --with-deliver --with-sqlite --without-vpopmail --with-notify=inotify --with-ioloop=epoll --with-ssl=openssl --enable-debug --enable-asserts make make check rm -rf /usr/local/pkgs/dovecot-20070605 make install install -c -m 555 doc/mkcert.sh /usr/local/pkgs/dovecot-20070605/sbin/dovecot-mkcert shmk /usr/local/pkgs/dovecot-20070605/sbin /usr/local/sbin mkdir -p /etc/ssl/certs /etc/ssl/private rm -f /etc/ssl/certs/dovecot.pem /etc/ssl/private/dovecot.pem export OPENSSLCONFIG=/tools/conf/dovecot-openssl.conf dovecot-mkcert cp -f /etc/ssl/certs/dovecot.pem /var/www/html/. chmod ugo+r /var/www/html/dovecot.pem groupadd dovecot || /bin/true groupadd: group dovecot exists useradd -M -g dovecot -d /usr/local -s /sbin/nologin dovecot || /bin/true useradd: user dovecot exists (cd /etc/init.d && ln -sf /tools/init.d/dovecot .) -- Like feeling your best ever, all day, every day? Here's how... Your simple secrets are here - http://RadicalHealth.com

2 3

[Dovecot] DC V1.0.1 release date
by Stewart Dean 11 Jun '07

11 Jun '07

Is there a sense of when this might be? Will it include a fix for SSL with a second invocation? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

1 0

[Dovecot] Connection dropped by IMAP server _ Internal login failure: root
by Saeed Abbassi 11 Jun '07

11 Jun '07

Dear reader, Please help me find a way through this problem, I have CentOS 4.2, dovecot-0.99.11-4.EL4, squirrelmail-1.4.8, While I try to log in as Root (username: root; password: password) I get the error that says, > ERROR: Connection dropped by IMAP server. > Query: CAPABILITY > Content of the file /var/log/maillog is as follows > Jun 7 12:56:59 PBX sendmail[5170]: l57Guxxr005170: from=root, > size=126838, class=0, nrcpts=1, msgid=< > 200706071656.l57Guxxr005170(a)PBX.COMPANY.COM>, relay=root@localhost > Jun 7 12:57:05 PBX sendmail[5171]: l57GuxDv005171: from=< > root(a)PBX.COMPANY.COM>, size=127100, class=0, nrcpts=1, msgid=< > 200706071656.l57Guxxr005170(a)PBX.COMPANY.COM>, proto=ESMTP, daemon=MTA, > relay=localhost.localdomain [127.0.0.1] > Jun 7 12:57:05 PBX sendmail[5170]: l57Guxxr005170: to=root, ctladdr=root > (0/0), delay=00:00:06, xdelay=00:00:06, mailer=relay, pri=156838, relay=[ > 127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (l57GuxDv005171 Message > accepted for delivery) > Jun 7 12:57:05 PBX sendmail[5172]: l57GuxDv005171: to=admin, ctladdr=< > root(a)PBX.COMPANY.COM> (0/0), delay=00:00:00, xdelay=00:00:00, > mailer=local, pri=157317, dsn=2.0.0, stat=Sent > Jun 7 22:26:11 PBX dovecot: Killed with signal 15 > Jun 11 11:39:00 PBX dovecot: Dovecot starting up > Jun 11 11:39:01 PBX sendmail[2704]: alias database /etc/aliases rebuilt by > root > Jun 11 11:39:01 PBX sendmail[2704]: /etc/aliases: 79 aliases, longest 10 > bytes, 811 bytes total > Jun 11 11:39:01 PBX sendmail[2709]: starting daemon (8.13.1): > SMTP+queueing@01:00:00 > Jun 11 11:39:01 PBX sm-msp-queue[2717]: starting daemon (8.13.1): > queueing@01:00:00 > Jun 11 11:51:27 PBX dovecot: Logins with UID 0 not permitted (user root) > Jun 11 11:51:27 PBX imap-login: Internal login failure: root [::ffff: > 127.0.0.1] And I says, [root@PBX etc]# dovecot -c dovecot.conf Fatal: listen(143) failed: Address already in use Any help is appreciated in advance, Cheers, Saeed144

2 1

[Dovecot] [Debian] Packages available for 1.0.0
by Brian T Glenn 11 Jun '07

11 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 They aren't thoroughly tested, but I've been running on them for a little while and they seem stable. This is based on the latest RC from backports.org and is built for sarge. deb http://debian.delink.net/ sarge-delink main Enjoy, - -- http://www.delink.net/ Ok, so he's got a cellphone in one hand and latte in the other, I know what he's using to steer, but what is that soccer mom using, a strap-on? - Brian Kantor in the monastery -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGZdGMFy/L+4MovqIRApa7AJ4s3jU0La4dCijm08iOpa7m9dSaowCeN1eW 6he6hZFEzREtzZ/iA4mvEms= =Ln6h -----END PGP SIGNATURE-----

2 2

[Dovecot] Can't connect to SMTP outside localhost
by Jeremy Gillick 11 Jun '07

11 Jun '07

I have Dovecot setup with Postfix and can't seem to connect to to the SMTP server (port 25) unless I'm on the server itself (telnet localhost 25). For example, I cannot use my mail client, Thunderbird, to send mail from my laptop -- it cannot even connect to the server. I checked the logs and nothing shows up for the attempted connection. Dovecot version: 1.0.0 Postfix version: 2.3.6 ---------- START DOVECOT CONFIG ---------- $ sudo dovecot -n # /etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 imaps pop3s ssl_listen: [::] login_dir: /var/run/dovecot//login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no first_valid_uid: 101 last_valid_uid: 101 mail_extra_groups: mail mail_location: maildir:/var/mail/%d/%u mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: mechanisms: plain digest-md5 cram-md5 user: nobody debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/sql.conf userdb: driver: sql args: /etc/dovecot/sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: vmail group: mail master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: mail ---------- END DOVECOT CONFIG ---------- ---------- POSTFIX CONFIG (main.cf) ---------- queue_directory = /var/spool/postfix command_directory = /usr/sbin daemon_directory = /usr/libexec/postfix mail_owner = postfix myhostname = mozmonkey.com mydomain = mozmonkey.com inet_interfaces = $myhostname, localhost mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain local_recipient_maps = $virtual_mailbox_maps unknown_local_recipient_reject_code = 550 mail_spool_directory = /var/mail debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5 sendmail_path = /usr/sbin/sendmail.postfix newaliases_path = /usr/bin/newaliases.postfix mailq_path = /usr/bin/mailq.postfix setgid_group = postdrop html_directory = no manpage_directory = /usr/share/man sample_directory = /usr/share/doc/postfix-2.3.6/samples readme_directory = /usr/share/doc/postfix-2.3.6/README_FILES address_verify_map = btree:/var/spool/postfix/address_verify virtual_mailbox_domains = proxy:mysql:$config_directory/mysql_virtual_domains_maps.cf virtual_mailbox_base = /var/mail virtual_mailbox_maps = proxy:mysql:$config_directory/mysql_virtual_mailbox_maps.cf virtual_alias_maps = proxy:mysql:$config_directory/mysql_virtual_alias_maps.cf virtual_minimum_uid = 101 virtual_uid_maps = static:101 virtual_gid_maps = static:12 virtual_transport = dovecot dovecot_destination_recipient_limit = 1 smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_security_options = noanonymous broken_sasl_auth_clients = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtp_tls_CAfile = /etc/pki/tls/cert.pem smtp_tls_cert_file = /etc/pki/tls/certs/localhost.crt smtp_tls_key_file = /etc/pki/tls/private/localhost.key smtp_tls_session_cache_database = btree:/var/spool/postfix/smtp_tls_session_cache smtp_tls_security_level = may smtpd_tls_dh1024_param_file = $config_directory/dh_1024.pem smtpd_tls_dh512_param_file = $config_directory/dh_512.pem smtpd_tls_received_header = yes smtpd_tls_ask_ccert = yes smtpd_tls_loglevel = 1 tls_random_source = dev:/dev/urandom relay_domains = proxy:mysql:$config_directory/mysql_relay_domains_maps.cf ---------- POSTFIX CONFIG END (main.cf) ---------- ---------- POSTFIX CONFIG (master.cf) ---------- smtp inet n - n - - smtpd smtps inet n - n - - smtpd -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions=permit_sasl_authenticated,reject pickup fifo n - n 60 1 pickup cleanup unix n - n - 0 cleanup qmgr fifo n - n 300 1 qmgr tlsmgr unix - - n 1000? 1 tlsmgr rewrite unix - - n - - trivial-rewrite bounce unix - - n - 0 bounce defer unix - - n - 0 bounce trace unix - - n - 0 bounce verify unix - - n - 1 verify flush unix n - n 1000? 0 flush proxymap unix - - n - - proxymap smtp unix - - n - - smtp relay unix - - n - - smtp -o fallback_relay= showq unix n - n - - showq error unix - - n - - error discard unix - - n - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - n - - lmtp anvil unix - - n - 1 anvil scache unix - - n - 1 scache maildrop unix - n n - - pipe flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient} old-cyrus unix - n n - - pipe flags=R user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -m ${extension} ${user} cyrus unix - n n - - pipe user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -r ${sender} -m ${extension} ${user} uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) ifmail unix - n n - - pipe flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) bsmtp unix - n n - - pipe flags=Fq. user=foo argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient dovecot unix - n n - - pipe flags=DRhu user=vmail:mail argv=/usr/libexec/dovecot/deliver -d ${recipient} ---------- POSTFIX CONFIG END(master.cf) ---------- <dovecot(a)dovecot.org>

2 1

[Dovecot] auth_username_format
by Sergio Souza 11 Jun '07

11 Jun '07

I configured in the archive dovecot.conf the parameter auth_username_format = "%Ld_%Ln" because the users of my server have access yours e-mail accounts based in /etc/passswd where they are registered in format domain.com_user. This configuration work without problems via pop3 and imap (squirrelmail). My server is CentOS 5.0 and dovecot is 1.0.rc15. The problem that occurs currently is: when the users go to have access the interface of change preferences (ISPCONFIG) where the supplied data of authentication are not the data of the email account (eg. user(a)domain.com) and yes of /etc/passwd the dovecot inserts underscore before the domain (eg. _domain.com_user) when it would have to make this only between the domain and the user. Exists a way to solve this problem? Thank in advance. -- Sergio Souza Wireless Support

1 0

[Dovecot] dovecot vs. Outlook Mobile
by J.Wendland＠scan-plus.de 10 Jun '07

10 Jun '07

Hi, I am testing dovecot with Outlook Mobile 5 (OM5), which is currently not working. OM5 connects, says "NOOP" and "CAPABILITY", does login correctly and simply loggs out after that telling the user that it could not download any messages. When I put an imapproxy[0] in front of dovecot, OM5 works perfectly well. That leads me to the thought, that something in the way dovecot sends its responses makes OM5 upset. Does anybody on this have seen this before? Thanks, Jörg [0] http://www.imapproxy.org -- Sicherheit - Verfügbarkeit - Kontinuität ------------------------------------------------------------------------- IT-Service-Management von ScanPlus GmbH Tel. +49 731 92013 150 Lise-Meitner-Straße 5, D-89081 Ulm, Germany Fax. +49 731 92013 29 150 Web: http://www.scan-plus.de/ Mail: wendland(a)scan-plus.de -------------------------------------------------------------------------

2 1

[Dovecot] Lost login process PID XXXXX
by Patrick Linstruth 10 Jun '07

10 Jun '07

Dear List: We installed Dovecot v1.0.0 a couple days ago. After running the software for a couple days, the following happened: Jun 6 15:58:10 cello dovecot: POP3(sgtdohara): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Jun 6 15:58:10 cello dovecot: POP3(dorene): Disconnected: Logged out top=0/0, retr=1/4652, del=1/1, size=4635 Jun 6 15:58:10 cello dovecot: Lost login process PID 17214 Jun 6 15:58:12 cello dovecot: Dovecot v1.0.0 starting up Jun 6 15:58:12 cello dovecot: Socket already exists: /qnet/var/run/dovecot/dict-server Jun 6 15:58:12 cello dovecot: net_listen_unix(/qnet/var/run/dovecot/login/default) failed: Address already in use Jun 6 15:58:12 cello dovecot: Couldn't create auth process listener Jun 6 15:58:12 cello dovecot: net_listen_unix(/qnet/var/run/dovecot/login/default) failed: Address already in use Jun 6 15:58:12 cello dovecot: Couldn't create auth process listener Jun 6 15:58:12 cello dovecot: login: Authentication process 17253 doesn't exist Jun 6 15:58:12 cello dovecot: login: Authentication process 17253 doesn't exist Jun 6 15:58:13 cello dovecot: login: Authentication process 17253 doesn't exist Jun 6 15:58:13 cello dovecot: login: Authentication process 17253 doesn't exist Jun 6 15:58:14 cello dovecot: login: Authentication process 17253 doesn't exist Jun 6 15:58:14 cello dovecot: login: Authentication process 17253 doesn't exist Jun 6 15:58:14 cello dovecot: login: Authentication process 17253 doesn't exist The "Authentication process 17253 doesn't exist" message continued until I changed inetd.conf to run our old POP3/IMAP server. Server vitals: BSD/OS 4.2 BSDI BSD/OS 4.2 Kernel #2: Tue Feb 21 11:10:22 PST 2006 4:46PM up 431 days, 16:40, 6 users, load averages: 1.19, 1.27, 1.02 Any help would be appreciated. We don't want to enable the software again until we know what caused the problem and hopefully find a solution to keep it from happening again. Patrick

2 3

[Dovecot] user lookups not working when using dovecot as lda
by Sven 10 Jun '07

10 Jun '07

Hi Currently I'm using local from postfix for delivering mails. Now I want to change this to using the dovecot lda as I want to use plus addressing. I configured postfix to use dovecot as I found in the wiki and several howtos in the net. My Problem is the following: dovecot delver accepts the mail but bounces it with error: user unknown. Logging in and authentication via imap4 and pop3 works, only deliver seems to be unable to lookup the users from userdb. Has anyone an idea where my mistake is? Here is my actual configuration: dovecot version: 1.0.beta9 postfix version: 2.2.10 system: FreeBSD 6.1-STABLE The system is using maildirs. I changed my postfix/master.cf to the following: dovecot unix - n n - - pipe flags=DRhu user=dovecot:dovecot argv=/usr/local/libexec/dovecot/deliver -d ${recipient} -m ${extension} In my postfix/main.cf I use the following: dovecot_destination_recipient_limit = 1 local_transport = dovecot lda & auth specific settings from my dovecot.conf: protocol lda { postmaster_address = postmaster(a)my-domain.org hostname = mail.my-domain.org #mail_plugins = #mail_plugin_dir = /usr/local/lib/dovecot/imap sendmail_path = /usr/sbin/sendmail auth_socket_path = /var/run/dovecot/auth-master log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log # syslog_facility = mail } auth_executable = /usr/local/libexec/dovecot/dovecot-auth auth_process_size = 256 auth_debug = yes auth_verbose = yes auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 user = dovecot group = dovecot } client { path = /var/run/dovecot/auth-client mode = 0660 } } } plugin { } Any help is appreciated as I dont know where to look for my mistake. regards, Sven

2 1

[Dovecot] bug in passdb-vpopmail.c
by Moritz Mertinkat 10 Jun '07

10 Jun '07

Hi there, i've tried to compile dovecot-latest.tar.gz (currently dovecot-20070522) with vpopmail support and spotted the following bug (patch is also attached): --- dovecot-20070522/src/auth/passdb-vpopmail.c.orig 2007-05-20 23:11:36.000000000 +0200 +++ dovecot-20070522/src/auth/passdb-vpopmail.c 2007-06-06 09:02:01.968750000 +0200 @@ -66,7 +66,7 @@ password = vpopmail_password_lookup(request, TRUE, &result); if (password == NULL) { - callback(result, "", request); + callback(result, "", 0, request); return; } Greets, Moritz. --- dovecot-20070522/src/auth/passdb-vpopmail.c.orig 2007-05-20 23:11:36.000000000 +0200 +++ dovecot-20070522/src/auth/passdb-vpopmail.c 2007-06-06 09:02:01.968750000 +0200 @@ -66,7 +66,7 @@ password = vpopmail_password_lookup(request, TRUE, &result); if (password == NULL) { - callback(result, "", request); + callback(result, "", 0, request); return; }

2 1

[Dovecot] [Fwd: mulitple instance run problem]
by Stewart Dean 10 Jun '07

10 Jun '07

As I explained, I want to be able to run a second instance of DC through another port to do testing while not interrupting the users using the primary instance in the the regular port. I was instructed to create a second config file with different listen ports and a separate base_dir. I did so and invoked dc with -c pointing to dovecot2.conf. Jun 7 10:04:23 mercury mail:info dovecot: Dovecot v1.0.0 starting up I pointed my client at the non-SSL port, and everything worked fine....until 3 hours later. The client wasn't getting things through, so I checked the syslog on the dc server where I saw rapidly repeating errmsgs:... Jun 7 12:51:07 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 12:58:55 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 12:58:59 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 12:59:01 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 12:59:05 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist and many more, then...... Jun 7 13:34:20 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 13:36:30 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 13:36:54 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist I kill the second instance.....but things don't clear up....rather I now get a different errmsg....which must be from the primary dc instance, since the 2nd instance and all of its children are gone (I checked the ps) Jun 7 13:39:20 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 13:40:00 mercury mail:err|error dovecot: imap-login: Can't connect to aut h server at default: Connection refused Jun 7 13:40:06 mercury mail:err|error dovecot: imap-login: Can't connect to aut h server at default: Connection refused Jun 7 13:40:06 mercury mail:err|error dovecot: imap-login: Can't connect to aut h server at default: Connection refused Finally I do a kill -1 of the primary instance and that cleans things up Jun 7 13:45:46 mercury mail:warn|warning dovecot: SIGHUP received - reloading configuration Is there something I'm doing wrong? Have other people run two instances without problem? I tried starting the second instance and killing it immediately thereafter....that wnet OK, but it hasn't been 3 hours yet. -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

4 5

[Dovecot] auth_username_format
by Sergio Souza 10 Jun '07

10 Jun '07

I configured in the archive dovecot.conf the parameter auth_username_format = “%Ld_%Ln” because the users of my server have access yours e-mail accounts based in /etc/passswd where they are registered in format domain.com_user. This configuration work without problems via pop3 and imap (squirrelmail). My server is CentOS 5.0 and dovecot is 1.0.rc15. The problem that occurs currently is: when the users go to have access the interface of change preferences (ISPCONFIG) where the supplied data of authentication are not the data of the email account (eg. user(a)domain.com) and yes of /etc/passwd the dovecot inserts underscore before the domain (eg. _domain.com_user) when it would have to make this only between the domain and the user. Exists a way to solve this problem? Thanks in advance. -- Sergio Souza

1 0

[Dovecot] Listen on several (but not all) Interfaces
by Dominik Schulz 09 Jun '07

09 Jun '07

Hi, I'm using Dovecot 1.0rc15 from Debian stable/etch. I'd like to have Dovecot listen on more than one interface. It shall listen on one IPv4 Interface and on one IPv6 Interface. The comments in the sample configuration file say, that it's not possible to listen on more than one interface at a time. Sadly it's no option to me to listen on all interfaces. So I'd like to ask if there is a chance that Dovecot will support listening on several selected interfaces anytime soon? Thanks in advance for every helpful reply. Best Regards Dominik

5 4

[Dovecot] Dot Lock probelm resolution
by Stewart Dean 08 Jun '07

08 Jun '07

For the record/archive, so some other unfortunate dovecot implementer won't spend weeks figuring out this particular way dotlocks can have problems... here is what was trashing our dotlocks Basically, I was seeing this: May 14 15:59:58 mercury mail:warn|warning dovecot: IMAP(sdean): Our dotlock file /var/spool/mail/sdean.lock was deleted (kept it 1 secs) > May 14 15:59:58 mercury mail:err|error dovecot: IMAP(sdean): file_dotlock_delete() failed with mbox file /var/spool/mail/sdean: No such file or directory Timo justifiably blamed the usual suspect, NFS, but when I dug into the maillog to see what was going on when the locks were getting trashed, in almost all cases, NFS wasn't involved. And I had recompiled procmail so that it used the same locking strategy (and checked it), deactivated NFS client attribute caching, etc., etc. It turned out that my predecessor had done something 10 years ago that was arcane, inscrutable and kludgy in the .procmailrc file. This *purposefully* trashed the dotlock. Not knowing what it did when I took over (predecessor long gone, things in disarray), I left it in, because I worried that something would break if we removed it. We have perpetuated it in creation of all new accounts. This procmailrc stanza looks like this: ####### BEGIN SYS ADMIN ADDED LINES ####### ## !!!!!! Do not remove these lines !!!!!! ## They have been placed here by System Admin ## If removed, your mail will run slower and ## generate error messages!!!!!!!! LOCKFILE #removes preexisting lockfile LOG='lockfile $DEFAULT$LOCKEXT ' TRAP="rm -f $DEFAULT$LOCKEXT" :0 $DEFAULT ####### END OF SYS ADMIN ADDED LINES ####### # IF YOU ADD STUFF, DO IT ABOVE THIS BLOCK # I sent a note to the procmail mailing list hoping to get a clue of what is doing. Here are my Qs and their As: >> 2) Is it syntactically correct? > I think so, though highly obfuscated and semantically worthless. >> 3) Is what it's doing real/worthwhile? > No. My guess is it was a kludge to work around some error with an > older version of procmail, if it ever served any function at all. Since we removed it, there have been no dotlocking errmsgs in the syslog. -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

1 0

[Dovecot] User unknown in local recipient table? Dovecot LDA/Postfix
by Yu Chen 08 Jun '07

08 Jun '07

This probably is a postfix problem, but I think there are lots of postfix experts/users on this list, and have heard a lot good things about this list, so I am just giving it a try. Thanks in advance! I am using dovecot-1.0.0-8_56.src.rpm downloaded from atrpms.net, and rebuilt from it(rpmrebuild ...). Postfix is 2.4.3. I followed documents at http://wiki.dovecot.org/LDA and LDA/Postfix, and used passwd-file (created /etc/passwd.dovecot file) both as password Database and User database. I can send emails, but not receiving, keep getting the "User unknow error". Do I need to change the "local_recipient_map" in main.cf, and if so, how? Here are some related configuration: ########### dovecot -n ########### # /etc/dovecot.conf log_path: /var/log/dovecot.log ssl_ca_file: /etc/pki/dovecot/certs/ca-bundle.crt verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Dovecot ready. verbose_proctitle: yes first_valid_uid: 102 mail_extra_groups: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u:INDEX=/var/mail_indexes/%d/%n mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle auth default: mechanisms: plain login executable: /usr/local/libexec/dovecot/dovecot-auth verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /etc/passwd.dovecot userdb: driver: passwd-file args: /etc/passwd.dovecot socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: mail master: path: /var/run/dovecot/auth-master mode: 384 ############### postconf -n ################ alias_database = hash:/etc/postfix/aliases alias_maps = hash:/etc/postfix/aliases broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2 html_directory = /usr/share/doc/postfix-2.4.3-documentation/html inet_interfaces = $myhostname, localhost invalid_hostname_reject_code = 450 mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man maps_rbl_reject_code = 450 mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain myhostname = my.host.com mynetworks = myip/24, 127.0.0.0/8 newaliases_path = /usr/bin/newaliases.postfix non_fqdn_reject_code = 450 queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.4.3-documentation/readme sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtp_tls_CAfile = /usr/share/ssl/certs/ca-bundle.crt smtp_tls_cert_file = /usr/share/ssl/certs/postfix.pem smtp_tls_key_file = /usr/share/ssl/certs/postfix.pem smtp_tls_session_cache_database = btree:/var/spool/postfix/smtp_tls_session_cache smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, permit_tls_clientcerts, reject_unauth_destination, check_relay_domains smtpd_sasl_auth_enable = yes smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_CAfile = /usr/share/ssl/certs/ca-bundle.crt smtpd_tls_cert_file = /usr/share/ssl/certs/postfix.pem smtpd_tls_key_file = /usr/share/ssl/certs/postfix.pem smtpd_tls_loglevel = 2 smtpd_tls_session_cache_database = btree:/var/spool/postfix/smtpd_tls_session_cache tls_random_source = dev:/dev/urandom unknown_local_recipient_reject_code = 550 virtual_transport = dovecot Regards, C.Y =========================================== Yu Chen Howard Hughes Medical Institute Chemistry Building, Rm 182 University of Maryland at Baltimore County 1000 Hilltop Circle Baltimore, MD 21250 phone: (410)455-6347 (primary) (410)455-2718 (secondary) fax: (410)455-1174 email: chen(a)hhmi.umbc.edu ===========================================

2 1

[Dovecot] PAM info please
by Frank Bonnet 07 Jun '07

07 Jun '07

Hello I'm searching infos on using Dovecot with pam_ldap and FreeBSD 6.2 any pointers welcome :-) Thanks -- Frank

2 2

[Dovecot] Latest MANAGESIEVE patch -- how to start daemon?
by Andreas Ntaflos 07 Jun '07

07 Jun '07

Hello list, I'm using Dovecot 1.0.0 on FreeBSD 6.2-RELEASE and applied the latest MANAGESIEVE patch v3 [1] which seems to have worked smoothly, i.e. all hunks succeeded and no compilation problems. Now this may be stupid question with an obvious answer, but I am at a loss at how to start the daemon? What's the binary called that starts the sieve server? Is there a special way to invoke it? I haven't been able to find anything useful on that matter and there doesn't seem to be a TFM to R yet, the Wiki just links to [1]. What do I have to do? Did I forgot to patch something? I'd appreciate any insight on this subject! Thanks in advance! Andreas [1] http://dovecot.org/list/dovecot/2007-March/021130.html -- Andreas "daff" Ntaflos Vienna, Austria GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4

5 8

[Dovecot] Quota Warning Message
by Gabriele Fergola 06 Jun '07

06 Jun '07

Hi to everyone, i try to implement in dovecot the quota warning message for the user but withouot success. I do the Patch found on the site but .. nothing happened. Anyone can help me please? Workino

1 0

[Dovecot] Replication plans
by Timo Sirainen 06 Jun '07

06 Jun '07

Several companies have been interested in getting replication support for Dovecot. It looks like I could begin implementing it in a few months after some other changes. So here's how I'm planning on doing it: What needs to be replicated: - Saving new mails (IMAP, deliver) - Copying existing mails - Expunges - Flag and keyword changes - Mailbox creations, deletions and renames - Subscription list - IMAP extension changes, such as ACLs I'll first talk about only master/slave configuration. Later then master/multi-slave and multi-master. Comments? Basic design ------------ Since the whole point of master-slave replication would be to get a reliable service, I'll want to make the replication as reliable as possible. It would be easier to implement much simpler master-slave replication, but in error conditions that would almost guarantee that some messages get lost. I want to avoid that. Both slave and master would be running a dovecot-replication process. They would talk to each others via TCP connection. Master would be feeding changes (transactions) to slave, and slave would keep replying how far it's committed the changes. So there would be an increasing sequence number sent with each transaction. Master keeps all the changes in memory until slave has replied that it has committed the changes. If the memory buffer gets too large (1MB?) because the slave is handling the input too slowly or because it's completely dead, the master starts writing the buffer to a file. Once the slave is again responding the changes are read from the file and finally the file gets deleted. If the file gets too large (10MB?) it's deleted and slave will require a resync. Master always keeps track of "user/mailbox -> last transaction sequence" in memory. When the slave comes back up and tells the master its last committed sequence, this allows the master to resync only those mailboxes that had changed. If this mapping doesn't exist (master was restarted), all the users' mailboxes need to be resynced. The resyncing will also have to deal with new mailboxes, ACL changes and such. I'm not completely sure yet how the resyncing will work. Probably the only important thing here is that it would be good if it would resolve any message UID conflicts (even though they shouldn't happen, see below) by comparing either the messages' MD5 contents, or with maildir it would be enough to just compare the maildir filename. It's possible that the slave doesn't die completely but only some transactions fail. This shouldn't normally happen, so the easiest way to handle it would be to try a full resync, and if that still fails stop the whole slave. Another way would be to just mark that one user or mailbox as dirty and try to resync it once in a while. imap, pop3 and deliver would connect to dovecot-replication either using UNIX sockets or POSIX message queue. Queue could be faster, but sockets would allow better security checks. Or I suppose it would be possible to send some kind of a small authentication token in each message with queues. The communication protocol would be binary and the existing dovecot.index.log format would be used as much as possible (making it simple for slave to append changes to mailboxes' dovecot.index.log). dovecot-replication process would need read/write access to all users' mailboxes. So either it would run as root or it would need to have at least group-permission rights to all mailboxes. A bit more complex solution would be to use multiple processes each running with their own UIDs, but I think I won't implement this yet. The replication would require support for shared mailboxes. That way the mailboxes could be accessed using the configured shared namespaces, for example "shared/<username>/INBOX". (LMTP server could be implemented in a similar way BTW) Configuration ------------- I'm not yet sure how this should work. The simplest possibility would be just to configure a single slave and everything would be replicated there. But it should be possible to split users into multiple slaves (still one slave/user). The most configurable way to do this would be to have userdb return the slave host. Hmm. Actually that could work pretty well if the userdb returned slave's name and each slave would have a separate socket/queue where dovecot-replication listens in. I'm not sure if they could all still be handled by a single dovecot-replication process or if there should be a separate one for each of them. The configuration would then be something like: # slave for usernames beginning with letters A..K replication users_a_k { host = slave1.example.com # other options? } # L..Z and others replication users_l_z_rest { host = slave2.example.com } Saving ------ This is the most important thing to get right, and also the most complex one. Besides replicating mails that are being saved via Dovecot, I think also externally saved mails should be replicated when they're first seen. This is somewhat related to doing an initial sync to a slave. The biggest problem with saving is how to robustly handle master crashes. If you're just pushing changes from master to slave and the master dies, it's entirely possible that some of the new messages that were already saved in master didn't get through to slave. So when you switch to using slave, those messages are gone. The biggest problem with this is that when saving new mails, they'll be assigned UIDs that were already used by the original master. If a locally caching client had already seen the UID from the original master, it'll think the message is the original one instead of the new one. So the newly added message pretty much gets lost, and if the user could expunge the message (thinking it's the original one) without ever even seeing it. This UID conflict could be avoided by making the master tell slave whenever it's saving new mails. The latency between master-slave communication could be avoided with a bit of a trick: - When beginning to save/copy a mail, tell slave to increase UID counter by one. Slave replies with the new highest-seen-UID counter. - UID allocation is done after all the mails are saved/copied within a transaction. At this stage wait until slave has replied that it has reserved UIDs at least as high as we're currently allocating (other processes could have caused it to get even higher). - If save/copy is aborted, tell the slave to decrease the UID counter by the number of aborted messages. - UID counter desync shouldn't happen, but if it does handle that also somehow. Then the UID allocation latency depends on how long it takes to write the message, and where the message comes from. With IMAP APPEND there's probably no wait required, unless the APPEND command and the whole message arrives in one IP packet. With deliver and copying it might have to wait a while. So the UID allocation should work with minimal possible latency. It could use a separate TCP connection to slave and maybe a separate high priority process in the slave that would handle only UID allocations. The above will make sure that conflicting UIDs aren't used, but it doesn't make sure that messages themselves aren't lost. If the master's hard disk failed completely and it can't be resynced anymore, the messages saved there are lost. This could be avoided by making the saving wait until the message is saved to slave: - save mail to disk, and at the same time also send it to slave - allocate UID(s) and tell to slave what they were, wait for "mail saved" reply from slave before committing the messages to mailbox permanently This would however add more latency than the simpler UID allocation counter. I don't know if it should be optional which way is used. Perhaps I'll implement the full save-sync first and if it seems too slow then I'll implement optionally the UID allocation counter. Save messages from imap/deliver would contain at least: 1. user name (unless using UNIX sockets, then it's already known) 2. mailbox name 3. UIDVALIDITY 4a) UID 4b) global UID, filename, offset and size of the message 4a) would be used with the UID allocation counter behavior. The message would be sent after the message was saved and UIDs were allocated. 4b) would be used with the wait-slave-to-save behavior. The message would be sent immediately whenever new data was received for the message, so possibly multiple times for each message. The last block would then contain size=0. After saving all the mails in a transaction, there would be a separate "allocate UIDs x..y for global UIDs a, b, c, d, etc." message which the slave then replies and master forwards the reply to imap/deliver. If the slave is down, or if a timeout (a few seconds?) occurs while waiting for the reply from slave, imap/deliver could just go on saving the message. If this is done it's possible that if the master also dies soon, there will be UID conflicts. But since this should be a rare error condition, it's unlikely that the master will die soon after a misbehaving slave. Copying ------- Copying has similar UID conflict problems than saving. The main difference is that there's no need to transfer message contents, which makes it faster to handle copies reliably. Copying could be handled with the UID allocation counter way described above. Since the message already exists in the server, there's no way that the message gets lost. So it would be possible to allow master and slave to go into desync, because the user would still find the message from the original mailbox. Move operation is done with "copy + mark \deleted + expunge" combination. This could be problematic if the master had managed to do all that before slave saw the COPY at all. Since the message isn't yet copied to the new mailbox in slave, clients wouldn't see it there, but locally caching clients might not see the message in the original mailbox either because they had already received EXPUNGE notification for it. So this should be avoided in some way. Perhaps it would be better to just treat copies the same way as saves: Require a notification from slave before replying to client with OK message. Alternatively the wait could be done at EXPUNGE command, as described below. Expunges -------- Losing expunge transactions wouldn't be too bad, because the worst that can happen is that the user needs to expunge the message again. Except that having an expunged message suddenly appear again in the middle of the mailbox violates IMAP protocol. I don't know if/how that will break clients. Solution here would again be that before EXPUNGE notifications are sent to client we'll wait for reply from slave that it had also processed the expunge. Flag and keyword changes ------------------------ Most likely doesn't matter if some of them are lost. If someone really cares about them, it would be possible to again do the slave-waiting for either all the changes or just when some specific flags/keywords change. Other changes ------------- Mailbox creations, deletions, renames and subscription changes could all be handled in a similiar way to flag/keyword changes. Handling changes implemented by IMAP extensions such as ACL is another thing. It's probably not worth the trouble to implement a special replication handler for each plugin. These changes most likely will happen somewhat rarely though, so they could be implemented by sending the whole IMAP command to slave and have it execute the command using a regular imap process. The commands could be marked with some "replication" flag so Dovecot knows that they need to be sent to slave. Although instead of executing a new imap process for each user (probably each command), it could be possible to use one imap process and just change the mailbox name in the command. So instead of eg. "setacl mailbox (whatever)" the IMAP process would execute "setacl shared/username/mailbox (whatever)". That would require telling Dovecot what parameter contains the mailbox name. Should be pretty easy to implement, unless some IMAP extensions want multiple mailbox names or the position isn't static. I can't think of any such extensions right now though. Master/multi-slave ------------------ Once the master/slave is working, support for multiple slaves could be added. The main thing to be done here is to have the slaves select which one of them is the new master, and then they'll have to sync the mailboxes with each others, because each of them might have seen some messages that others hadn't. This is assuming that save/etc. operations that are waiting for a reply from slave would wait for only one reply from the first slave that happens to respond. The number of slave replies to wait for could be also configurable, in case you're worried of a simultaneous master+slave crash. Multi-master ------------ After master/multi-slave is working, we're nearly ready for a full multi-master operation. The master farm will need global locking. Perhaps there is a usable existing implementation which could be used. In any case there needs to be a way to keeps track of what master owns what locks. The easiest way to implement multi-master is to assume that a single user isn't normally accessed from different servers at the same time. This wouldn't be a requirement, but it would make the performance better. For most users you could handle this by making sure that load balancer transfers all connections from the same IP to the same server. Or you could use a Dovecot proxy that transfers the connections. So, once the user is accessed only from one server, the operation becomes pretty much like master/multi-slave. You'll just need to be able to dynamically change the current master server for the user. This can be done by grabbing a global per-user lock before modifying the mailbox. The lock wouldn't have to be released immediately though. If no other server needs the lock, there's no point in locking/unlocking constantly. Instead the lock server could request the current lock owner to release the lock whenever another server wants it.

8 20

[Dovecot] multiple dovecot invocations
by Stewart Dean 05 Jun '07

05 Jun '07

I need to have multiple invocations of dovecot running, one for productions and then one or more for test/dev, doing things like trying different authentication methods, getting quota working, etc. I knew how to do this with inetd, but I have been convinced that direct invocation is preferable, so I need to know how to do multiple invocations of dovecot. I had thought that perhaps I could do this: dovecot -c /usr/local/etc/dovecot2.conf where dovecot2.conf has different different listen port parms. This I did, and while it does seem to work, I get this error in the syslog: > Jun 5 14:42:43 mercury mail:err|error dovecot: Socket already exists: /usr/local/var/run/dovecot/dict-server > Jun 5 14:42:43 mercury mail:crit dovecot: execv(/usr/local/libexec/dovecot/dict) failed: No such file or directo > ry > Jun 5 14:42:43 mercury mail:err|error dovecot: child 1437914 (dict) returned error 84 (exec() failed) How do I correctly run multiple dc instances? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1