- dovecot - dovecot.org

[Dovecot] v1.1.rc7 released
by Timo Sirainen 30 May '08

30 May '08

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc7.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc7.tar.gz.sig One extra RC release, just to fix compiling problems with non-Linux OSes. Nothing else changed since rc6.

1 0

[Dovecot] Web-based shared calendar synchronizable with Outlook
by Samuel HAMEAU 30 May '08

30 May '08

Hi, I know this request is a a little off-topic but may be interesting for dovecot users (at least i hope!) Does anybody has already had an experience with a calendar sharing solution including a webcalendar and an outlook connector, "compatible" with dovecot ? Today, there are many projects aiming to be a "M$ Exchange Killer" (such as Zimbra, OBM, open-exchange, etc) but they offers a global package with MTA and imap server included. I saw the page about BynariConnector (http://wiki.dovecot.org/HowTo/BynariConnector) but unfortunatly they do not provide a webmail :( I'm afraid What I am looking for is a shared agenda solution providing a webcalendar, an outlook connector and eventually a pda connector, using (or not) dovecot, and a corporate ldap server... What are you guys using ? sam

5 7

[Dovecot] Dovecot 1.1 significantly faster than 1.0
by Marc Perkel 30 May '08

30 May '08

It appears to be that 1.1 is a lot faster that 1.0. And server load levels have dropped.

2 1

[Dovecot] v1.1.rc6 released won't compile
by webbie 30 May '08

30 May '08

I got a compile error with rc6, rc5 works fine. amd64:dovecot-1.1.rc6# uname -a FreeBSD amd64.objtech.com 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #3: Fri Apr 18 02:18:13 EDT 2008 ./configure \ --prefix=/opt1/dovecot \ --localstatedir=/var \ --without-shadow \ --without-cyrus-sasl2 \ --without-pop3d \ --without-gssapi \ --disable-ipv6 \ --disable-debug \ --with-ioloop=kqueue \ --with-ssl=openssl make [trimmed] gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-mail -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT mail-index-view-sync.o -MD -MP -MF .deps/mail-index-view-sync.Tpo -c -o mail-index-view-sync.o mail-index-view-sync.c mv -f .deps/mail-index-view-sync.Tpo .deps/mail-index-view-sync.Po gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-mail -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT mail-index-write.o -MD -MP -MF .deps/mail-index-write.Tpo -c -o mail-index-write.o mail-index-write.c mail-index-write.c: In function 'mail_index_write': mail-index-write.c:179: error: 'struct stat' has no member named 'st_ctim' mail-index-write.c:179: error: 'struct stat' has no member named 'st_ctim' *** Error code 1 Stop in /opt1/source/dovecot-1.1.rc6/src/lib-index. *** Error code 1 Stop in /opt1/source/dovecot-1.1.rc6/src. *** Error code 1 Stop in /opt1/source/dovecot-1.1.rc6. *** Error code 1 Stop in /opt1/source/dovecot-1.1.rc6.

6 7

[Dovecot] no bookeeping using public folders
by Claude Frantz 30 May '08

30 May '08

Using dovecot 1.0.10. In the config: namespace public { separator = / hidden = no prefix = Flock/ location = maildir:/home/baratin/PublicMaildir:CONTROL=~/Maildir/control/Flock:INDEX=/var/dovecot/index/%u/Flock } This should be a public mail folder owned by "baratin", "read only" for all other users. Every user has his/her own control and index area related to this public folder. I have verified, they are owner and "group" of the respective control and index area. The problem, while using Thunderbird: The "read only" user can delete messages or mark then read. But after a new session, all the messages are still "new". Of course, only "baratin" is the owner. The problem, while using mutt and IMAP: mutt refuse to change any flag because the folder is "read only". Of course, this is correct. My question: Why is no bookkeeping maintained for "other" users, although every one has his/her own control and index structure ? Thanks a lot ! Claude

3 4

[Dovecot] Compile error with 1.1rc6
by Trent Stevens 30 May '08

30 May '08

I'm trying a very basic ./configure; make of v1.1rc6 under Mac OS X 10.5.3. I have previously installed v1.1rc5 with no problems (although I was running OS X 10.5.2 at the time). Machine is an Intel based Mac Mini running on an Journaled HFS+ partition. When I attempt the make I am running into: <snip> gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib- mail -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing- declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad- function-cast -Wstrict-aliasing=2 -MT mail-index-view-sync.o -MD -MP - MF .deps/mail-index-view-sync.Tpo -c -o mail-index-view-sync.o mail- index-view-sync.c mv -f .deps/mail-index-view-sync.Tpo .deps/mail-index-view-sync.Po gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib- mail -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing- declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad- function-cast -Wstrict-aliasing=2 -MT mail-index-write.o -MD -MP - MF .deps/mail-index-write.Tpo -c -o mail-index-write.o mail-index- write.c mail-index-write.c: In function 'mail_index_write': mail-index-write.c:179: error: 'struct stat' has no member named 'st_ctim' mail-index-write.c:179: error: 'struct stat' has no member named 'st_ctim' make[3]: *** [mail-index-write.o] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2

1 0

[Dovecot] Upgrading from 1.0x to 1.1x
by Marc Perkel 30 May '08

30 May '08

OK - about to jump to the new version of dovecot. Is there anything I need to change in the config files or things I should know? I'm using maildir format running under Fedora 8.

3 4

[Dovecot] Problem deleting folders with Thunderbird?
by Knute Johnson 30 May '08

30 May '08

I am running Thunderbird 2.0.0.14 on Windows XP. When I try to delete one of the folders I get a dialog with the following "The current command did not succeed. The mail server responded: Target mailbox doesn't allow inferior mailboxes." I am running dovecot version 1.0.13-6.fc8 under Fedora 8. The output of dovecot -n is below; [root@www knute]# dovecot -n # 1.0.13: /etc/dovecot.conf protocols: imaps pop3s disable_plaintext_auth: yes 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 auth default: passdb: driver: pam userdb: driver: passwd Is there something to be configured to allow mail box deletion? I know there was a similar discussion this week about users deleting their mailboxes accidentally. Are folders within folders allowed by dovecot? Thanks very much, -- Knute Johnson linux(a)www.knutejohnson.com

3 3

[Dovecot] dovecot's deliver and SELinux
by Dan Horák 29 May '08

29 May '08

Hello, I am the new maintainer of dovecot for Fedora and Red Hat and so I am trying to cleanup some old reported bugs. One of them is a problem when "deliver" writes of temporary files into /tmp are blocked by SELinux policy (https://bugzilla.redhat.com/show_bug.cgi?id=424091) From the SELinux's point of view it is bad when system services try to write into /tmp (for detail see http://danwalsh.livejournal.com/11467.html) The solution looks simple - just to switch from /tmp to PKG_RUNDIR (line 472 in deliver.c for dovecot 1.0) for writing the temp files. But this raises two questions - will it really work and when yes, is it acceptable for the author? Thanks, Dan -- Fedora and Red Hat package maintainer

3 3

[Dovecot] Fwd: Re: [SOLVED] Configuring Quota on Dovecot 1.0.13-1~bpo40+1
by Lucas Carlessi 29 May '08

29 May '08

Thank you Tomasz! The quota per user worked fine now... The problem was that in dovecot.conf I had these lines: userdb static { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } And I just changed to: userdb sql { args = /etc/dovecot/dovecot-sql.conf } Now it's working... bye! On Wed, 28 May 2008 21:08:51 +0200, Tomasz Suchodolski <suchodolski.tomasz(a)gmail.com> wrote: >> Hi all! >> I have just updated my dovecot 1.0.rc15 to 1.0.13-1~bpo40+1 > >> I have a mysql table with this structure: > >> +----------+--------------+------+-----+---------+-------+ >> | Field | Type | Null | Key | Default | Extra | >> +----------+--------------+------+-----+---------+-------+ >> | email | varchar(91) | YES | | NULL | | >> | password | varchar(32) | NO | | | | >> | quota | bigint(20) | NO | | | | >> | home | varchar(255) | NO | | | | >> +----------+--------------+------+-----+---------+-------+ > >> email returns email(a)domain.com > >> password returns the pass in mysql-crypt format > >> quota returns the quota in bytes(like 100000000) > >> home returns the path to the user home(like >> /home/vmail/domain.com/email/) > >> the mail user and group id are 5000. > >> Now the question: How can I configure the quotas by user using >> mysql... in dovecot 1.0.rc15 didn't work... >> Thanks for your >> help! > > http://wiki.dovecot.org/Quota/1.0 > Set global quota and see examples for sql queries. Also try with > kilobytes. > > Ps. 1.0.rc15 - quota per user(with mysql) works - I have tested it. > > Regards

1 0

[Dovecot] "storage error during logout"
by Vegard Svanberg 29 May '08

29 May '08

What is this error message actually trying to tell me? May 28 13:47:24 yyy dovecot: POP3(aaa@bbb): Disconnected: Storage error during logout. top=0/0, retr=2/73195, del=0/435, size=13509375 This user is accessing his mailbox using both POP3 and IMAP, I don't know if that's relevant. The POP3 check is quite aggressive; once every minute or so. Dovecot 1.0.13-1~bpo40+1 -- Vegard Svanberg <vegard(a)svanberg.no> [*Takapa@IRC (EFnet)]

2 1

[Dovecot] Trim trailing whitespace from username
by David Jonas 29 May '08

29 May '08

Recently we changed Postfix to use Dovecot for our SASL authentication and we ran into trouble with some of our clients having extraneous spaces at the end of their usernames. The quick fix was to add a space to username_chars. The slightly longer fix was a pretty simple patch to Dovecot. I put the trimming in auth_request_fix_username. I didn't think it warranted a full strfuncs function. If there is a better way to do this I'm all ears. I don't really like patching with my own code, even if I did essentially steal if from the kernel's strstrip(). diff -u dovecot-1.1.rc5/src/auth/auth-request.c dovecot-1.1.rc5-patched/src/auth/auth-request.c --- dovecot-1.1.rc5/src/auth/auth-request.c 2008-05-04 15:01:52.000000000 -0700 +++ dovecot-1.1.rc5-patched/src/auth/auth-request.c 2008-05-16 00:44:15.000000000 -0700 @@ -22,6 +22,7 @@ #include <stdlib.h> #include <sys/stat.h> +#include <ctype.h> struct auth_request * auth_request_new(struct auth *auth, const struct mech_module *mech, @@ -750,6 +751,7 @@ { unsigned char *p; char *user; + size_t size; if (strchr(username, '@') == NULL && request->auth->default_realm != NULL) { @@ -759,6 +761,16 @@ user = p_strdup(request->pool, username); } + /* Trim trailing whitespace from the username */ + size = strlen((unsigned char*)user); + if(size) { + p = user + size - 1; + while (p != user && isspace(*p)) + p--; + *(p + 1) = '\0'; + p = NULL; + } + for (p = (unsigned char *)user; *p != '\0'; p++) { if (request->auth->username_translation[*p & 0xff] != 0) *p = request->auth->username_translation[*p & 0xff];

3 6

[Dovecot] Sieve/Vacation
by Ulrich Schreiner 29 May '08

29 May '08

hi, i'm using 1.1.rc5 but the same error occured with 1.0.13. the dovecot package was installed on centos 5 with rpm's from atrpms. exim 4.69. everything works fine except the vacation's from sieve. don't get me wrong, sieve works for everything, including mailforwards, or sorting in subfolders. but when i have a vacation, the script is compiled, but it produces the following output: sieve_execute_bytecode(/var/virtuser/test@<adomain>.sievec) failed (the "<adomain>" is replaced with the real domain of the user). i use virtual users in different domains. the sieve-scripts are generated by horde/ingo and stored via ftp in the "/var/virtuser" directory with the pattern "%u.sieve". the "sievec" files are up-to-date, because: a) i can delete the "sievec" files and they are regenerated b) i can "sieved" them and get an disassembled output with the vacation rule inside but when executing the script (when a mail arrives) the upper error is logged and no vacation is processed. the same error occured with 1.0.13 thank you </usc>

2 1

[Dovecot] Configuring Quota on Dovecot 1.0.13-1~bpo40+1
by Lucas Carlessi 28 May '08

28 May '08

2 1

[Dovecot] Configuring Quota on Dovecot 1.0.13-1~bpo40+1
by Lucas Carlessi 28 May '08

28 May '08

Hi all! I have just updated my dovecot 1.0.rc15 to 1.0.13-1~bpo40+1 from backports... I need some help in configure quotas by user using mysql

1 0

[Dovecot] Dovecot 1.0 rc15 + Quota by user using mysql
by Lucas Carlessi 28 May '08

28 May '08

Hi all, I installed the Dovecot on a Debian by apt-get, it's all working except quota by user.. I have a database with all quotas in bytes, and that lines in /etc/dovecot/dovecot-sql.conf : driver = mysql connect = host=127.0.0.1 dbname=mailserver user=USER password=PASS default_pass_scheme = CRYPT password_query = SELECT email as user, password FROM view_users WHERE email='%u'; #Quota: user_query = SELECT home AS maildir, 5000 AS uid, 5000 AS gid, CONCAT('dirsize:storage=', ROUND( view_users.quota / 1024) ) AS quota FROM view_users WHERE email='%u'; and in /etc/dovecot/dovecot.conf : protocol imap { mail_plugins = quota imap_quota } protocol pop3 { pop3_uidl_format = %08Xu%08Xv mail_plugins = quota } plugin { #quota = maildir:ignore=Trash } But when I open the webmail I have no limit quotas! If I put quota = maildir:storage=101480 in plugin the quota works fine at 100MB, but in all users... Is the query right? There is another way to configure quotas by user in Dovecot 1.0 using mysql? Sorry my bad English, and thank you all!

2 2

[Dovecot] Error when using include directive in Sieve
by Juan Asensio Sánchez 28 May '08

28 May '08

Hi I have two sieve scripts: # cat /var/vmail/sieve/global require ["include"]; include :global "spam"; include :personal "sieve"; # cat /var/vmail/sieve/spam require "fileinto"; if exists "X-Spam-Flag" { fileinto "Junk"; } # ls -l /var/vmail/sieve/ total 16 -rw-r--r-- 1 mailuser mailgroup 68 2008-05-28 00:40 global -rw------- 1 mailuser mailgroup 80 2008-05-28 00:40 globalc -rw-r--r-- 1 mailuser mailgroup 68 2008-05-27 21:15 spam -rw------- 1 mailuser mailgroup 80 2008-05-27 21:25 spamc # cat /etc/dovecot/dovecot.conf [...] sieve_global_dir = /var/vmail/sieve/ sieve_global_path = /var/vmail/sieve/global [...] When delivering a message I get: deliver(*****@*******): May 28 00:39:04 Error: sieve_execute_bytecode(/var/vmail/sieve/globalc) failed Personal sieve script is not sure to exist, only if the user has created it. If I put the contents of the spam script in the global script (replacing the content), everything works fine. Why does this happen? Is it because the personal script doesn't exists?Or is the syntax incorrect (i don't think this because the script is compiled)? Thanks in advance.

3 3

[Dovecot] Vanishing maildirsize files with 1.0.7 using 'deliver' via postfix
by Jason Forester 28 May '08

28 May '08

Aloha, I've searched the list and have found no similar reports, so I'm asking here. We have 3 RH5.1 boxes running the stock Postfix 2.3.3, but due to issues with the stock Dovecot 1.0rc15, Redhat supplied us with the version of Dovecot 1.0.7 that will be in Redhat 5.2. The mail store is automounted per-user from a Sun box via NFS. We were using it with no problems until last Friday, when we attempted to implement quotas. I had done quite a lot of testing on a single system, so I didn't anticipate any issues here. I created maildirsize files for each user in the NFS-mounted /var/spool/mail/$USER and everything seemed fine. I changed mailbox_command to /usr/libexec/dovecot/deliver in postfix main.cf. Mail was delivered, quota files updated, all good. However almost immediately a maildirsize folder vanished. Soon after another, then another, and now we're missing nearly 40 of them. Any ideas as to why they're vanishing? Something to do with NFS? I've tried to trigger it by massively sending to the same user on all three systems but have yet to reproduce it at will. Any clues would be appreciated. For reasons of support I cannot upgrade to a later dovecot at this time. Best Regards, - jason

3 8

[Dovecot] Dovecot quota for mailadministrator
by Markus Hofer 27 May '08

27 May '08

Hallo, i have a question for the quota with dovecot. I plan to go from our cyrus installation to dovecot. I have just install dovecot without problem with mysqldb and quota per user. Quota work well and the user receive always via Webmail or client the quota information. My question is: With cyrus the mailadministrator has the possibility to see the quota for all users with the command "quota". Output or example: 300000 9 28305 user.tinfo With that way the administrator could have always a look if some users have quota problems. My question is, if dovecot has some similar command for the administrator? Thanks in advance. Markus

2 3

[Dovecot] Problem with checkpassword-reply
by sawyer x 27 May '08

27 May '08

Hello I posted an earlier post on problems with getting usernames. That one is solved, thank you. I'm currently having trouble executing checkpassword-reply. The maillog shows the following error: (substituting rip/lip/user/domain) May 27 07:21:06 saw dovecot: Logins with UID 0 not permitted (user user(a)domain.com> May 27 07:21:06 saw dovecot: imap-login: Internal login failure: user=<user(a)domain.com>, method=plain, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, TLS My script reads fd3 right and gets all the details correct. Then runs the following code: --- $REPLY = $ARGV[0] || exit 111; # this is actually run much earlier $ENV{HOME} = "$USERSHOME/$domain/$user"; $ENV{USER} = $user; # effective gid $) = 300; # effective uid $> = 300; exec $REPLY; --- I've looked at the checkpassword-reply code (thank god for open source software) and I saw that it opens fd4 for writing. I couldn't find any documentation about this and couldn't find anyone who is using checkpassword-reply. No sample scripts, no examples, and the documentation on the site is extremely scarce. The wiki docs indicate I should just execute it - which I do - but that does not help. Also, the debugging isn't very meaningful. I'm definitely changing the UID and GID, but it's not apparent in the maillog. The fie permissions on checkpassword-reply show I could execute it under any user and I've tried that with "sudo -u <user> /path/to/checkpassword-reply. On a post somewhere in the vortex of the internet someone said Dovecot does not allow any uid/gid under 99 (which is why I tried 300), but I couldn't find any documentation for that anywhere in the wiki either. What am I missing and is there anything I've missed that would have prevented me from emailing the mailing list with this long email? Thanks, Sawyer.

1 0

[Dovecot] Asking for password
by Aziz KNINA 27 May '08

27 May '08

Hi, I'm a new user of Dovecot. I have installed it in a server in combination of Postfix. I have created a system user and given him a password, this is a final user. when I try to add the account in my mail client (outlook), I get the window of authentication asking for password, even if I enter the correct password, this window does not disappear. below my configuration. dovecot --version: 1.0.13 dovecot -n: # 1.0.13: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no 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/local/libexec/dovecot/pop3-login mail_privileged_group: mail mail_location: INBOX=/var/spool/mail/$u mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/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/local/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %m auth default: passdb: driver: pam userdb: driver: passwd can someone help me with this? thank you at advance. -- RG Aziz KNINA

2 2

[Dovecot] mbox From escaping implementation ?
by Nicolas KOWALSKI 27 May '08

27 May '08

Hello, I read in the wiki (http://wiki.dovecot.org/MailboxFormat/mbox) about "From Escaping": "Dovecot doesn't currently do this escaping however. Instead it prevents this confusion by adding Content-Length headers so it knows later where the next message begins. Dovecot doesn't either remove the '>' characters before sending the data to clients. Both of these will probably be implemented later." As I understand it, this makes the mbox format of dovecot slightly incompatible with other mbox-capable clients, because if they read the data files directly, they may understand a line starting with an unescaped 'From ' as the start of a new message. Right ? Are there any plans to implement this escaping in the future (1.1.x or 2.0.x?) Thanks, -- Nicolas

2 3

[Dovecot] Sieve plugin changes 'To' header on redirect
by Patrick Nagel 27 May '08

27 May '08

Hi, I'm a bit confused by the fact that the 'To' header is being modified by sieve when a message is being redirected. RFC3028 states in chapter 4.3: > The "redirect" action is used to send the message to another user at > a supplied address, as a mail forwarding feature does. The > "redirect" action makes no changes to the message body or existing > headers, but it may add new headers. The "redirect" modifies the > envelope recipient. (see http://www.ietf.org/rfc/rfc3028.txt) The situation here is as follows: I'm sending a mail to "city(a)company.net" (To: ...), which is being delivered to "city(a)city.company.net" (Delivered-To: ...). User city has the following sieve script: redirect "other(a)company.net"; keep; One would expect, that the 'To:' header is identical in both mails, but instead I get something like this: Mail in 'city' mailbox: > Delivered-To: city(a)city.company.net > To: city(a)company.net > Subject: test mail (Redirected) Mail in 'other' mailbox: > Delivered-To: other(a)city.company.net > To: city(a)city.company.net > Subject: test mail It seems as if sieve uses the 'Delivered-To' header as the 'To' header in the redirected mail - which is not what I need. Am I misunderstanding something here, or does dovecot's sieve plugin not act according to the RFC? Patrick. -- STAR Software (Shanghai) Co., Ltd. http://www.star-group.net/ Phone: +86 (21) 5427 7799 x 826 Fax: +86 (21) 6485 0071 PGP key: https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005

2 1

[Dovecot] Problem of using dovecot as sasl implement for postfix
by sosogh 27 May '08

27 May '08

Hi list I install postfix dovecot on my debian etch box I install them via apt-get I want to use dovecot to be postfix sasl implement,but i got the following error message in the mail log: Apr 27 21:28:39 sosogh postfix/smtpd[19776]: warning: SASL: Connect to private/auth failed: No such file or directory Apr 27 21:28:39 sosogh postfix/smtpd[19776]: fatal: no SASL authentication mechanisms Apr 27 21:28:40 sosogh postfix/master[19765]: warning: process /usr/lib/postfix/smtpd pid 19776 exit status 1 my configuration: postfix: Mail:/etc/dovecot# more /etc/postfix/main.cf smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth Mail:/etc/dovecot# postconf | grep mail_version mail_version = 2.3.8 Mail:/etc/dovecot# postconf | grep -i mail_owner mail_owner = postfix Mail:/etc/dovecot# ls -al /var/spool/postfix/private/ total 8 drwx------ 2 postfix root 4096 2008-04-27 22:11 . drwxr-xr-x 19 root root 4096 2008-01-20 23:12 .. srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 anvil srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 bounce srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 bsmtp srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 defer srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 discard srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 dspam srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 error srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 ifmail srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 lmtp srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 local srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 maildrop srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 mailman srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 policy srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 proxymap srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 relay srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 rewrite srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 scache srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 scalemail-backend srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 smtp srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 tlsmgr srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 trace srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 uucp srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 verify srw-rw-rw- 1 postfix postfix 0 2008-04-27 22:11 virtual dovecot: Mail:/etc/dovecot# dovecot --version 1.0.rc15 Mail:/etc/dovecot# dovecot -n # /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log 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_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 auth default: mechanisms: plain login verbose: yes debug: yes passdb: 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: Mail:/etc/dovecot# more dovecot.conf protocols = imap imaps pop3 pop3s auth_debug = yes auth_verbose = yes log_path = /var/log/dovecot.log disable_plaintext_auth = no auth default { mechanisms = plain login user = postfix passdb sql { args = /etc/dovecot/dovecot-sql.conf } user = root socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } I wonder why private/auth does not exsit THANK YOU！ BEST RGDS! ****************** sosogh(a)126.com 2008-05-26 *******************

2 4

[Dovecot] Bug: subscriptions file does not take on the same perms as dovecot-shared
by Damon Atkins 27 May '08

27 May '08

All, Version: 1.1.rc5 Solaris x86 on ZFS Shared Folder Bug, renamed a folder with sub folders (Maildir format) After the rename the subscriptions file is own by the person who renamed the folders, and access is owner rw only. Instead it should be the same as dovecot-shared which would general be rw owner, and rw group for a shared folder. Cheers Damon.

4 4

[Dovecot] Multiple files for sieve
by Adrián Ribao Martínez 27 May '08

27 May '08

Hello, I have this line in the plugins configuration section : sieve = /etc/dovecot/sieve Where: /etc/dovecot/sieve: require "fileinto" if header :contains "Subject" "****SPAM****"{ fileinto "spam"; } I want this filter for all the users of the system, but I also want to tell dovecot to look in the /home/user/mail/.sieve file for custom per-user filters. Can I do this? Thank you. -- Adrián Ribao Martínez

3 2

[Dovecot] Dovecot crash in 1.0.9
by Peter Eriksson 26 May '08

26 May '08

I've been having a problem with a crashing Dovecot the last couple of months where it crashes after a couple of weeks of uptime. Been a bit difficult to diagnose. Anyway, we're now running 1.0.9 on a Sun Fire T1000 running Solaris 10. Any good ideas on how to pin-point the problem? - Peter Here's the output from syslog when the last crash happened: May 14 11:46:50 ifm.liu.se dovecot: [ID 107833 mail.info] imap-login: Login: user=<hidta>, method=PLAIN, rip=130.236.160.20, lip=13 0.236.160.6, secured May 14 11:46:50 ifm.liu.se dovecot: [ID 107833 mail.info] auth(default): new auth connection: pid=4054 May 14 11:46:51 ifm.liu.se dovecot: [ID 107833 mail.error] IMAP(joher): file maildir-uidlist.c: line 143: assertion failed: (UIDLIS T_IS_LOCKED(uidlist)) May 14 11:46:51 ifm.liu.se dovecot: [ID 107833 mail.error] IMAP(joher): Raw backtrace: 0x100082768 -> 0x1000298ec -> 0x100027e70 -> 0x100028fa8 -> 0x1000294a8 -> 0x10002057c -> 0x100014824 -> 0x100016cb4 -> 0x1000170d4 -> 0x10008a458 -> 0x100089938 -> 0x100022ad 8 -> 0x10000fe7c May 14 11:46:51 ifm.liu.se dovecot: [ID 684838 mail.error] child 3677 (imap) killed with signal 6 May 14 11:46:51 ifm.liu.se dovecot: [ID 107833 mail.warning] IMAP(hidta): Killed with signal 15 May 14 11:46:51 ifm.liu.se dovecot: [ID 107833 mail.warning] IMAP(peber): Killed with signal 15 ... May 14 11:46:51 ifm.liu.se dovecot: [ID 107833 mail.info] IMAP(yohell): Server shutting down May 14 11:46:51 ifm.liu.se dovecot: [ID 107833 mail.warning] imap-login: Killed with signal 15 May 14 11:46:51 ifm.liu.se dovecot: [ID 107833 mail.warning] auth(default): Killed with signal 15 May 14 11:46:51 ifm.liu.se dovecot[7743]: [ID 711832 mail.warning] I/O leak: 10000a578 (268) May 14 11:46:51 ifm.liu.se dovecot[7743]: [ID 711832 mail.warning] I/O leak: 10000a578 (275) May 14 11:46:51 ifm.liu.se dovecot[7743]: [ID 711832 mail.warning] I/O leak: 10000a578 (261) May 14 11:46:51 ifm.liu.se dovecot[7743]: [ID 711832 mail.warning] I/O leak: 10000a578 (256) May 14 11:46:51 ifm.liu.se dovecot[7743]: [ID 711832 mail.warning] I/O leak: 10000a578 (197) May 14 11:46:51 ifm.liu.se dovecot[7743]: [ID 711832 mail.warning] I/O leak: 10000a578 (254)

3 20

[Dovecot] 1.1rc5 Panic: mailbox-tree.c: line 171 (mailbox_tree_iterate_set_next_node)
by Jeffrey Rice 25 May '08

25 May '08

Hi, I do hope this hasn't been covered. I googled and looked in the archives but didn't see anything related, so hopefully I am not covering old ground. I recently upgraded from 1.0.10 to 1.1rc5. I am seeing this error from clients: May 25 11:01:54 finity dovecot: Panic: IMAP(xxx(a)here.org): file mailbox-tree.c: line 171 (mailbox_tree_iterate_set_next_node): assertion failed: (len <= ctx->parent_pos) May 25 10:21:19 finity dovecot: IMAP(xxx(a)here.org): Raw backtrace: imap [0x80ced44] -> imap [0x80ce99a] -> imap [0x80a0c63] -> imap(maildir_list_iter_next+0x33) [0x806ba53] -> imap [0x805c49b] -> imap(cmd_list_full+0x4b2) [0x805d1d2] -> imap(cmd_lsub+0x1a) [0x805d55a] -> imap [0x805f83c] -> imap [0x805f8e5] -> imap [0x80600c5] -> imap(client_input+0x5e) [0x80602ce] -> imap(io_loop_handler_run+0x110) [0x80d6ad0] -> imap(io_loop_run+0x28) [0x80d5d28] -> imap(main+0x4a1) [0x8067e71] -> /lib/libc.so.6(__libc_start_main+0xe0) [0xb7de6450] -> imap [0x8059d61] ## In my old install, I did have mail_extra_groups = vmail I commented that out and put in: mail_access_groups = vmail mail_privileged_group = vmail The documentation on these parameters is a bit light, so I'm not sure which (or both) to use. Can someone clarify? All the maildirs are owned by group vmail. ### dovecot -n # 1.1.rc5: /etc/dovecot/dovecot.conf ssl_cert_file: /etc/dovecot/ssl/certs/dovecot_cert.pem ssl_key_file: /etc/dovecot/ssl/private/dovecot_key.pem ssl_cipher_list: ALL:!LOW login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting: IMAP ready. login_process_per_connection: no login_processes_count: 1 mail_access_groups: vmail mail_location: maildir:/home/vmail/%u maildir_copy_preserve_filename: yes mail_process_size: 70 auth default: mechanisms: plain cram-md5 login passdb: driver: sql args: /etc/dovecot/dovecot-mysql.cnf userdb: driver: passwd userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%u/home socket: type: listen client: path: /var/spool/postfix/private/dovecot-auth-client mode: 432 user: postfix group: postfix

2 3

[Dovecot] Sort output of dovecot -n alphabetically?
by Charles Marcus 25 May '08

25 May '08

Is there a way? Postfix does this by default, and it makes it much less likely to miss/overlook a setting... If there is no way, any chance to modify it so that it does? Thanks for dovecot! Really looking forward to 1.1 release! -- Best regards, Charles

4 6

[Dovecot] dovecot developer documentation
by Piotr Wadas 25 May '08

25 May '08

Hello, I want to create some specific plugin for dovecot v1.1 (rc5). Where can I find some developer documentation ? Can I build my plugin separately, or do I need to rebuild dovecot again ? I'm looking into code, and analyzing some simple plugins, but hooks documentation or any hints you could give would be very helpful.. AFAIK there's no search for mailing list archives available, to let me search for some older guidance in this case :( Regards, Piotr

5 5

[Dovecot] singe system user for all virtual users
by Wojtek Bogusz 25 May '08

25 May '08

hi, i would like to have all the emails stored under one system user and system group. i keep user passwords in LDAP. for userdb i wanted to use static. but i keep getting this error: Error: Error in configuration file /usr/local/etc/dovecot.conf line 909: Unknown setting: userdb Fatal: Invalid configuration in /usr/local/etc/dovecot.conf i am using version 1.0.13 my /usr/local/etc/dovecot.conf without comments is: base_dir = /var/run/dovecot/ protocols = imaps imap listen = * disable_plaintext_auth = no shutdown_clients = yes log_timestamp = "%Y-%m-%d %H:%M:%S " ssl_disable = no ssl_cert_file = /etc/apache2/ssl/server.pem ssl_key_file = /etc/apache2/ssl/server.key mail_location = maildir:/home/MAIL/%n mail_privileged_group = mail protocol imap { login_greeting_capability = yes imap_client_workarounds = tb-extra-mailbox-sep } protocol lda { postmaster_address = postmaster(a)frontlinedefenders.org hostname = base auth_socket_path = /var/run/dovecot/auth-master } auth_verbose = yes auth_debug = yes auth_debug_passwords = yes auth default { mechanisms = plain passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb static { args = uid=mail gid=mail home=/home/MAIL/%n } auth_userdb = user = mail socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = mail # User running Dovecot LDA group = mail # Or alternatively mode 0660 + LDA user in this group } } } dict { } plugin { } what do i do wrong? best regards, Wojtek

3 4

[Dovecot] Error while set mailQuota=0 with mbox and LDAP backend
by Zhang Huangbin 25 May '08

25 May '08

Hi, all. I have OpenLDAP(+qmail.schema), Dovecot, Postfix installed on RHEL 5.1 (x86_64), and they works fine with mbox format. The problem is if i set 'mailQuota=0' in LDAP, postfix can't send mail to recipient user. But it works fine with 'mailQuota != 0', such as '10240'(10M). What's wrong with my mail server setting? How can i solved this issue? Thanks very much. Bellow is the mail log from /var/log/maillog: ---------------- /var/log/maillog ------------- # mail -s "h" postmaster(a)a.cn < /etc/hosts && tail -0f /var/log/maillog May 23 20:29:35 rh6 postfix/pickup[1608]: 8E8B884949: uid=0 from=<root> May 23 20:29:35 rh6 postfix/cleanup[1896]: 8E8B884949: message-id=<20080524002935.8E8B884949(a)rh6.bibby.org> May 23 20:29:35 rh6 postfix/qmgr[1616]: 8E8B884949: from=<root(a)rh6.bibby.org>, size=467, nrcpt=1 (queue active) May 24 00:29:35 rh6 postfix/smtpd[1901]: connect from localhost.localdomain[127.0.0.1] May 24 00:29:35 rh6 postfix/smtpd[1901]: CFE838494A: client=localhost.localdomain[127.0.0.1] May 23 20:29:35 rh6 postfix/cleanup[1896]: CFE838494A: message-id=<20080524002935.8E8B884949(a)rh6.bibby.org> May 23 20:29:35 rh6 postfix/qmgr[1616]: CFE838494A: from=<root(a)rh6.bibby.org>, size=1076, nrcpt=1 (queue active) May 24 00:29:35 rh6 postfix/smtpd[1901]: disconnect from localhost.localdomain[127.0.0.1] May 24 00:29:35 rh6 postfix/smtp[1898]: 8E8B884949: to=<postmaster(a)a.cn>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.35, delays=0.07/0/0.01/0.27, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as CFE838494A) May 23 20:29:35 rh6 postfix/qmgr[1616]: 8E8B884949: removed May 23 20:29:35 rh6 postfix/pickup[1608]: E47BA84949: uid=2000 from=<> May 23 20:29:35 rh6 postfix/cleanup[1896]: E47BA84949: message-id=<dovecot-1211588975-866451-0(a)rh6.bibby.org> May 23 20:29:35 rh6 postfix/qmgr[1616]: E47BA84949: from=<>, size=2085, nrcpt=1 (queue active) May 23 20:29:35 rh6 postfix/pipe[1902]: CFE838494A: to=<postmaster(a)a.cn>, relay=dovecot, delay=0.12, delays=0.01/0/0/0.11, dsn=2.0.0, status=sent (delivered via dovecot service) May 23 20:29:35 rh6 postfix/qmgr[1616]: CFE838494A: removed May 24 00:29:36 rh6 postfix/smtpd[1901]: connect from localhost.localdomain[127.0.0.1] May 24 00:29:36 rh6 postfix/smtpd[1901]: 390468494F: client=localhost.localdomain[127.0.0.1] May 23 20:29:36 rh6 postfix/cleanup[1896]: 390468494F: message-id=<dovecot-1211588975-866451-0(a)rh6.bibby.org> May 23 20:29:36 rh6 postfix/qmgr[1616]: 390468494F: from=<>, size=2522, nrcpt=1 (queue active) May 24 00:29:36 rh6 postfix/smtpd[1901]: disconnect from localhost.localdomain[127.0.0.1] May 24 00:29:36 rh6 postfix/smtp[1898]: E47BA84949: to=<root(a)rh6.bibby.org>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.34, delays=0.02/0/0.01/0.31, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 390468494F) May 23 20:29:36 rh6 postfix/qmgr[1616]: E47BA84949: removed May 23 20:29:36 rh6 postfix/local[1951]: 390468494F: to=<root(a)rh6.bibby.org>, relay=local, delay=0.04, delays=0.01/0/0/0.03, dsn=4.3.0, status=deferred (temporary failure. Command output: Can't open log file /var/log/sieve.log: Permission denied ) ------------ End maillog --------------- Bellow is my dovecot setting(dovecot -n): ----------- dovecot -n -------------- # 1.0.13: /etc/dovecot.conf log_path: /var/log/dovecot.log protocols: pop3 pop3s imap imaps ssl_cert_file: /etc/pki/dovecot/certs/dovecotCert.pem ssl_key_file: /etc/pki/dovecot/private/dovecotKey.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 mail_location: mbox:/%Lh/%Ld/%Ln:INBOX=/%Lh/%Ld/%Ln/inbox:INDEX=MEMORY mbox_write_locks: dotlock fcntl mbox_min_index_size: 10240 mbox_very_dirty_syncs: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login user: vmail passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: ldap args: /etc/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: 432 user: vmail group: vmail ----------- End dovecot -n -------------- Bellow is /etc/dovecot-ldap.conf: -------------- /etc/dovecot-ldap.conf --------------- hosts = 127.0.0.1:389 ldap_version = 3 auth_bind = yes dn = cn=vmail,dc=osspinc,dc=com dnpass = passwd base = o=%d,o=domains,dc=osspinc,dc=com scope = subtree deref = never user_filter = (&(mail=%u)(objectClass=qmailUser)(accountStatus=active)) pass_filter = (mail=%u) pass_attrs = userPassword=password user_global_uid = 2000 user_global_gid = 2000 default_pass_scheme = CRYPT user_attrs = homeDirectory=home,mailMessageStore=dirsize:mail,mailQuota=quota=dirsize:storage -------------- End /etc/dovecot-ldap.conf --------------- transport entry in Postfix master.cf: ----------- /etc/postfix/master.cf ---------------- dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -d ${recipient} -f ${sender} ----------- End /etc/postfix/master.cf ---------------- -- Best Regards. Zhang Huangbin - Mail Server Solution for Red Hat(R) Enterprise Linux & CentOS 5.x: http://rhms.googlecode.com/

3 6

[Dovecot] Auto-subscribe to folders
by Juan Asensio Sánchez 25 May '08

25 May '08

Hi I will use autocreate plugin in a new installation, and client has asked me if the users can be auto-subscribed to certain folders. Example: the users will have an autocreated Junk folder (for SPAM) and we want the users not to be un-subscribed for this folder; so if the user wants to be unsubscribed (from outlook, webmail, etc), there are two options: a) the action is rejected or denied; b) the next time he/she logins, then the folder is autosubscribed again. Could this be done? How? Thanks in advance.

2 1

[Dovecot] Domain variable in checkpassword
by sawyer x 25 May '08

25 May '08

Hello everyone I'm using the checkpassword method but I don't get the domain a user inputs. I can't cross check per virtual domains if I'm not getting one, which means it renders all my efforts useless. I've tried sending %d as a variable to my checkpassword script, but I'm just getting %d instead. This is a dump of my information: %ENV = { 'USERNAME_TRANSLATION' => '', 'SYSLOG_FACILITY' => '16', 'CACHE_SIZE' => '0', 'RESTRICT_GID_LAST' => '', 'TCPREMOTEIP' => '213.31.43.3', 'RESTRICT_GID_FIRST' => '', 'AUTH_NAME' => 'default', 'CACHE_TTL' => '3600', 'SERVICE' => 'IMAP', 'USERDB_1_DRIVER' => 'prefetch', 'USERNAME_CHARS' => 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@', 'DOVECOT_MASTER' => '1', 'RESTRICT_SETGID' => '', 'AUTH_WORKER_MAX_COUNT' => '30', 'AUTH_WORKER_PATH' => '/var/run/dovecot/auth-worker.25291', 'PASSDB_2_ARGS' => '/etc/exim/checkp %d', 'USERNAME_FORMAT' => '', 'LOCAL_IP' => '128.177.27.100', 'PASSDB_2_DRIVER' => 'checkpassword', 'PASSDB_1_DRIVER' => 'pam', 'REALMS' => '', 'PROTO' => 'TCP', 'ANONYMOUS_USERNAME' => 'anonymous', 'RESTRICT_SETEXTRAGROUPS' => '', 'TCPLOCALIP' => '128.177.27.100', 'LOG_TO_MASTER' => '1', 'MASTER_USER_SEPARATOR' => '', 'RESTRICT_SETUID' => '', 'REMOTE_IP' => '213.31.43.3', 'RESTRICT_USER' => '', 'DOVECOT_VERSION' => '1.0.rc15', 'MECHANISMS' => 'plain', 'RESTRICT_CHROOT' => '', 'DEFAULT_REALM' => '' }; ARGS: @ARGV = [ '%d', '/usr/libexec/dovecot/checkpassword-reply' ]; Thanks, Sawyer.

2 1

[Dovecot] imap-login processes
by Bryan Polk 25 May '08

25 May '08

First, thanks for this great product. We migrated from Courier last week with only small bumps along the way. We have a few hundred active users with a mix of pop3 and imap clients. The server is running on sparc Solaris 9. We're seeing a problem now with the number of "imap-login" processes rising slowly to it's limit and then (understandably) not letting any more logins happen. Legitimate users seem to have no problem logging in until the limit is hit. Another odd thing is that this is not a problem for pop3-login processes, just imap... I've tried changing some obvious things including the passdb from pam to passwd and back again, but here's the current dovecot -n output: # 1.0.13: /opt/dovecot/etc/dovecot.conf protocols: imap imaps pop3 pop3s ssl_cert_file: /opt/dovecot/etc/ssl/certs/dovecot.pem ssl_key_file: /opt/dovecot/etc/ssl/certs/key.pem disable_plaintext_auth: no login_dir: /opt/dovecot/var/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 login_processes_count: 12 login_max_processes_count: 512 verbose_proctitle: yes mail_location: maildir:~/Maildir mmap_disable: yes mail_executable(default): /opt/dovecot/libexec/dovecot/imap mail_executable(imap): /opt/dovecot/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot/libexec/dovecot/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 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv namespace: type: private prefix: INBOX. inbox: yes auth default: verbose: yes passdb: driver: pam userdb: driver: passwd Any ideas or advice? Thanks, Bryan Polk Unix Systems Administrator Communication and Multimedia Services FAMU-FSU College of Engineering bpolk(a)eng.fsu.edu

5 14

[Dovecot] Problems with apple'mail client
by Osvaldo Alvarez Pozo 25 May '08

25 May '08

hi all I use dovecot for smtp authentication this works ok for thunderbird and for outlook express but not for apple'mail client. my config is as follow postfx main.cf . . #authentication 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 # TLS parameters . . Dovecot dovecot.conf ssl_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem ssl_key_file = /etc/ssl/private/ssl-cert-snakeoil.key mail_location = maildir:/var/vmail/%d/%u/Maildir mail_extra_groups = mail first_valid_uid = 5000 last_valid_uid = 5000 maildir_copy_with_hardlinks = yes disable_plaintext_auth = no mail_debug = no dotlock_use_excl=yes protocols = imap pop3 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 pop3_uidl_format = %08Xu%08Xv } protocol lda { postmaster_address = support(a)oc3.fr mail_plugins = quota log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log } auth default { mechanisms = plain login passdb sql { args = /usr/dovecot/etc/sql.conf } # userdb prefetch { # } userdb sql { args = /usr/dovecot/etc/sql.conf } user = nobody socket listen { master { path = /usr/dovecot/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 { } Thanks

3 3

[Dovecot] Bug [1.1rc5]: Crash during "CPU architecture changed" index upgrade
by Cabel Sasser 25 May '08

25 May '08

Hello List, We just migrated from a PPC Xserve to an Intel Xserve. I used "rsync" to bring everyone's home directories over, and in the back of my mind wondered about how it would handle the binary index files... only one way to find out! :) Once I tried to login to IMAP, I got the following results: May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): Rebuilding index file /Users/cabel/mail/.imap/INBOX/dovecot.index: CPU architecture changed May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): fscking index file / Users/cabel/mail/.imap/INBOX/dovecot.index May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): Fixed index file / Users/cabel/mail/.imap/INBOX/dovecot.index: log_file_seq 1 -> 637534208 May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): /Users/cabel/ mail/.imap/INBOX/dovecot.index: log_file_head_offset too small May 6 19:46:48 posh dovecot[1169]: Panic: IMAP(cabel): file mail- transaction-log-view.c: line 215 (mail_transaction_log_view_set): assertion failed: (min_file_offset >= view->tail->hdr.hdr_size) May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): Raw backtrace: 2 imap 0x000839d8 i_set_failure_file + 392 -> 3 imap 0x00083283 i_panic + 51 -> 4 imap 0x0006f512 mail_transaction_log_view_set + 1170 -> 5 imap 0x000669c9 mail_index_sync_map + 297 -> 6 imap 0x0005d35c mail_index_map + 1580 -> 7 imap 0x00061f5e mail_index_transaction_open_updated_view + 958 -> 8 imap 0x00062ba6 mail_index_sync_begin_to + 102 -> 9 imap 0x0006352d mail_index_sync_begin + 77 -> 10 imap 0x00030b50 mbox_sync + 1120 -> 11 imap 0x0003203d mbox_storage_sync_init + 77 -> 12 imap 0x0004f21f mailbox_sync + 31 -> 13 imap 0x00006167 cmd_select_full + 231 - > 14 imap 0x0000 May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): 6329 cmd_select + 25 - > 15 imap 0x00008409 client_handle_unfinished_cmd + 201 -> 16 imap 0x000084ab client_handle_unfinished_cmd + 363 -> 17 imap 0x00008705 client_handle_unfinished_cmd + 965 -> 18 imap 0x00008962 client_input + 114 -> 19 imap 0x0008c2e9 io_loop_handler_run + 313 -> 20 imap 0x0008b606 io_loop_run + 70 -> 21 imap 0x000119f7 main + 1207 -> 22 imap 0x000016c6 start + 54 May 6 19:46:49 posh ReportCrash[1222]: Formulating crash report for process imap[1202] May 6 19:46:49 posh dovecot[1169]: child 1202 (imap) killed with signal 6 May 6 19:46:49 posh ReportCrash[1222]: Saved crashreport to /Library/ Logs/CrashReporter/imap_2008-05-06-194648_posh.crash using uid: 0 gid: 0, euid: 0 egid: 0 Naturally, deleting everyone's ".imap" folders fixed the problem. I'll attach the crash report to this e-mail. Hope this is useful to someone on this list! Best, Cabel Panic Process: imap [1202] Path: /usr/local/libexec/dovecot/imap Identifier: imap Version: ??? (???) Code Type: X86 (Native) Parent Process: dovecot [1169] Date/Time: 2008-05-06 19:46:48.366 -0700 OS Version: Mac OS X Server 10.5.2 (9C31) Report Version: 6 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Crashed Thread: 0 Thread 0 Crashed: 0 libSystem.B.dylib 0x96d540ea __kill + 10 1 libSystem.B.dylib 0x96dcb3f2 raise + 26 2 libSystem.B.dylib 0x96dda9af abort + 73 3 imap 0x00083a0a i_internal_fatal_handler + 106 4 imap 0x00083283 i_panic + 51 5 imap 0x0006f512 mail_transaction_log_view_set + 1170 (mail-transaction-log-view.c:143) 6 imap 0x000669c9 mail_index_sync_map + 297 (mail-index-sync-update.c:753) 7 imap 0x0005d35c mail_index_map + 1580 (mail-index-map.c:926) 8 imap 0x00061f5e mail_index_sync_begin_init + 78 (mail-index-sync.c:355) 9 imap 0x00062ba6 mail_index_sync_begin_to + 102 (mail-index-sync.c:418) 10 imap 0x0006352d mail_index_sync_begin + 77 (mail-index-sync.c:323) 11 imap 0x00030b50 mbox_sync + 1120 (mbox- sync.c:1684) 12 imap 0x0003203d mbox_storage_sync_init + 77 (mbox-sync.c:1880) 13 imap 0x0004f21f mailbox_sync + 31 (mail- storage.c:539) 14 imap 0x00006167 cmd_select_full + 231 (cmd-select.c:39) 15 imap 0x00006329 cmd_select + 25 (cmd- select.c:88) 16 imap 0x00008409 client_command_input + 41 (client.c:553) 17 imap 0x000084ab client_command_input + 203 (client.c:604) 18 imap 0x00008705 client_handle_input + 277 (client.c:643) 19 imap 0x00008962 client_input + 114 (client.c:698) 20 imap 0x0008c2e9 io_loop_handler_run + 313 (ioloop-kqueue.c:150) 21 imap 0x0008b606 io_loop_run + 70 (ioloop.c:300) 22 imap 0x000119f7 main + 1207 (main.c:254) 23 imap 0x000016c6 start + 54 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000000 ebx: 0x96dda96f ecx: 0xbfffdcdc edx: 0x96d540ea edi: 0x00201720 esi: 0x00000004 ebp: 0xbfffdcf8 esp: 0xbfffdcdc ss: 0x0000001f efl: 0x00000282 eip: 0x96d540ea cs: 0x00000007 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x00107000 Binary Images: 0x1000 - 0xa9fe0 +imap ??? (???) <10c13baf127aaaae5e5c68a2929781d2> /usr/local/libexec/dovecot/imap 0x8fe00000 - 0x8fe2da53 dyld 96.2 (???) <7af47d3b00b2268947563c7fa8c59a07> /usr/lib/dyld 0x9024c000 - 0x90340ff4 libiconv.2.dylib ??? (???) <c508c60fafca17824c0017b2e4369802> /usr/lib/libiconv.2.dylib 0x935d3000 - 0x935d7fff libmathCommon.A.dylib ??? (???) /usr/lib/ system/libmathCommon.A.dylib 0x93768000 - 0x9376ffe9 libgcc_s.1.dylib ??? (???) <a9ab135a5f81f6e345527df87f51bfc9> /usr/lib/libgcc_s.1.dylib 0x96ce5000 - 0x96e44ff3 libSystem.B.dylib ??? (???) <4899376234e55593b22fc370935f8cdf> /usr/lib/libSystem.B.dylib 0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/ libSystem.B.dylib

2 1

[Dovecot] Maildir locking by LDA of dovecot
by Mike Grozak 25 May '08

25 May '08

Hi all! First of all, I want ti thank the whole Dovecot community (developers for developing and fast responses, users for populating and responses too). Dovecot is a really good and fast IMAP server - it serves near 3000 in our installation. Now I have a problem and request community's help its resolving;) Dovecot version: 1.0.13, compiled with vpopmail support. I have an account spam(a)domain.com (:-), in which we put all our spam (we gather statistic later). There can be 10 and more delivery attempts in a second to maildir of this account during the spam attacks on our server. The queue of our server can grow up to 20k messages, and all of these messages are sent to spam(a)domain.com. I found a lot of such strings in dovecot.log file during such DoS attack: dovecot.log:deliver(spam@domain.com): May 16 04:18:48 Info: msgid=<01c8b6da$a8bacf80$b7af2abe@sale>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:18:59 Info: msgid=<6611811842.20080516012444(a)poiusadfhnvxzmdiasdasgkhlsdkfg.com>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:20:06 Info: msgid=<01c8b6a8$7b552e00$a0a4034c@sale>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:20:14 Info: msgid=<360825920.32055246029506(a)mirgames.ru>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:20:50 Info: msgid=<01c8b6b1$0df9cb00$cc36dfc9@tek2>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:21:00 Info: msgid=<087901c7ca2d$ef272640$1e01a8c0(a)telefonia.InterCable.net>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:21:01 Info: msgid=<000701c8b6d2$01ff999f$c491aca7@snoueiij>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:22:32 Info: msgid=<000801c8b69b$060c0230$3cd8a4b7@cpbvlrx>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:22:45 Info: msgid=<000801c8b6a5$04ba6412$9910848d@aldldr>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:22:45 Info: msgid=<031401c772e2$adc5be40$1e01a8c0(a)mtu-net.ru>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:23:08 Info: msgid=<01c8b6db$0222fe80$b7af2abe@info>: save failed to INBOX: Timeout while waiting for lock What can I do for resolving this locks? The queue of my server becomes really big! May be, while looking into uidlist file, can dovecot LDA lock it? And other deliver processes can't open it and wait for him? $ dovecot --version 1.0.13 # dovecot -n # 1.0.13: /etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imap pop3 ssl_disable: yes 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: Server is ready. login_process_per_connection: no login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_max_connections: 1024 first_valid_uid: 39 last_valid_uid: 39 first_valid_gid: 39 last_valid_gid: 39 fsync_disable: 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_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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 login cram-md5 default_realm: tversu.ru cache_size: 10240 user: vpopmail username_format: %Lu passdb: driver: vpopmail args: cache_key=%u dovecot userdb: driver: vpopmail socket: type: listen client: path: /var/spool/postfix/private/auth mode: 438 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 438 plugin: quota: maildir:ignore=Trash --------------------------- WBR, Mike Grozak, TvSU IC

3 4

[Dovecot] Multiple private namespace question
by Troy Engel 24 May '08

24 May '08

(apologies if this has been covered, can't find it on the Wiki/FAQ, etc.) We have a stellar, fantastic, hard working Dovecot 1.0.5 (yes, I need to upgrade) installation running in Courier-IMAP compatibility mode: mail_location = maildir:~/Maildir:INDEX=/var/spool/dovecot/indexes/%1u/%u namespace private { separator = . prefix = INBOX. inbox = yes } A user purchased a Windows Mobile 6 device which is ignoring the namespace (it's the device's bug for sure, other people report it on forums around the 'net) and there's no way on this device to manually set the Prefix; so, his Sent mails are never making it back to the server when replying from the device because of the missing INBOX. issue. Can I add a second hidden namespace with no prefix: namespace private { separator = . prefix = hidden = yes } ...to fix his problem, but without adversely affecting anyone else? The issue that has given me pause is this comment in the config file: "Default namespace is simply done by having a namespace with empty prefix." ..but then there's also: "If namespace is hidden, it's not advertised to clients via NAMESPACE extension or shown in LIST replies." I'm not sure what exactly will happen by adding a hidden namespace with no prefix after an advertised namespace with a prefix; this is a live server, so mucking up the works with a bad config is not an option. :) Anyone have a clue if this is valid/good/correct and Dovecot will play nicely? Many thanks, -te -- Troy Engel | Systems Engineer Fluid, Inc | http://www.fluid.com

3 8

[Dovecot] Problem compiling antispam plugin with Dovecot 1.1
by Juan Asensio Sánchez 24 May '08

24 May '08

Hi I am trying to compile antispam plugin with Dovecot 1.1, but i get an error when running make install: pdc-server:~/tmp/dovecot-antispam# make cc -c -DHAVE_CONFIG_H -Wall -I/root/tmp/dovecot-1.1.rc5/ -I/root/tmp/dovecot-1.1.rc5/src/ -I/root/tmp/dovecot-1.1.rc5/src/lib/ -I/root/tmp/dovecot-1.1.rc5/src/lib-storage/ -I/root/tmp/dovecot-1.1.rc5/src/lib-mail/ -I/root/tmp/dovecot-1.1.rc5/src/lib-imap/ -I/root/tmp/dovecot-1.1.rc5/src/lib-dict/ -I/root/tmp/dovecot-1.1.rc5/src/lib-index/ -I/root/tmp/dovecot-1.1.rc5/src/imap/ -DCONFIG_DEBUG -DDEBUG_SYSLOG -DCONFIG_DEBUG_VERBOSE -DCONFIG_DOVECOT_11 "-Dmempool_unref(x)=pool_unref(x)" -fPIC -shared -Wall -Wextra -DPLUGINNAME=antispam -o debug.o.o debug.c cc -DHAVE_CONFIG_H -Wall -I/root/tmp/dovecot-1.1.rc5/ -I/root/tmp/dovecot-1.1.rc5/src/ -I/root/tmp/dovecot-1.1.rc5/src/lib/ -I/root/tmp/dovecot-1.1.rc5/src/lib-storage/ -I/root/tmp/dovecot-1.1.rc5/src/lib-mail/ -I/root/tmp/dovecot-1.1.rc5/src/lib-imap/ -I/root/tmp/dovecot-1.1.rc5/src/lib-dict/ -I/root/tmp/dovecot-1.1.rc5/src/lib-index/ -I/root/tmp/dovecot-1.1.rc5/src/imap/ -DCONFIG_DEBUG -DDEBUG_SYSLOG -DCONFIG_DEBUG_VERBOSE -DCONFIG_DOVECOT_11 "-Dmempool_unref(x)=pool_unref(x)" -fPIC -shared -Wall -Wextra -DPLUGINNAME=antispam antispam-storage-1.1.c -o antispam-storage-1.1 cc -o .o cc: no input files make: *** [.o] Error 1 When running make clean to try to compile again, a file called "antispam-storage-1.1.c" (without any extension) is not deleted, and this file was not before running make install. If I run again make install with that file present (after running make clean), i get this output: cc -c -DHAVE_CONFIG_H -Wall -I/root/tmp/dovecot-1.1.rc5/ -I/root/tmp/dovecot-1.1.rc5/src/ -I/root/tmp/dovecot-1.1.rc5/src/lib/ -I/root/tmp/dovecot-1.1.rc5/src/lib-storage/ -I/root/tmp/dovecot-1.1.rc5/src/lib-mail/ -I/root/tmp/dovecot-1.1.rc5/src/lib-imap/ -I/root/tmp/dovecot-1.1.rc5/src/lib-dict/ -I/root/tmp/dovecot-1.1.rc5/src/lib-index/ -I/root/tmp/dovecot-1.1.rc5/src/imap/ -DCONFIG_DEBUG -DDEBUG_SYSLOG -DCONFIG_DEBUG_VERBOSE -DCONFIG_DOVECOT_11 "-Dmempool_unref(x)=pool_unref(x)" -fPIC -shared -Wall -Wextra -DPLUGINNAME=antispam -o debug.o debug.c cc -o .o cc: no input files make: *** [.o] Error 1 If I run make clean and manually deleted that file before running make install, i get again the first output. Why am i getting this error? Regards.

1 0

[Dovecot] I've moved
by Timo Sirainen 24 May '08

24 May '08

I've moved again. If you need to know my new address, whois imapwiki.org (dovecot.org address is still lagging behind). My living costs also increased some because of this, but hopefully I'll get enough money from Dovecot coding to pay for it. :) I'll try to get back to replying mails within the next few days.

2 2

[Dovecot] Disallow folder delete
by Kenneth Porter 24 May '08

24 May '08

Is there a straightforward way to disallow the deletion of all IMAP mailboxes? I have a user who's deleted an important IMAP mailbox and I'm now recovering a recent copy from the backup. But I'd rather just blanket disallow all folder deletions. The user is using Thunderbird and this has happened more than once so I suspect Tbird is willing to let a folder get deleted too easily. Perhaps there was a delay in the confirmation dialog and the user clicked ahead and confirmed something he shouldn't have. I'm looking at <http://wiki.dovecot.org/ACL> and it looks like I should be able to use a group override to disallow "x" (mailbox delete) but the page says that groups aren't implemented, so I don't know how one says that nobody can do this for any mailbox. I'm using 1.2.rc15 from CentOS 5 (RHEL5 equivalent).

7 16

[Dovecot] Don't Understand Error Entry
by Carlos Williams 24 May '08

24 May '08

I am using dovecot-0.99.11-8.EL4 on my system and decided to check the logs since I just took over as the administrator on this system and I noticed the same error entry over and over in the logs. I went to /var/log/dovecot.err and see: imap(rangry): May 22 13:33:31 Error: Error parsing IMAP envelope: "Thu, 20 Apr 2006 10:10:01 -0400" "Re: Hi there I have a question" (("Rodney Angry" NIL "rodney.s.angry" "example.com")) (("Rodney Angry" NIL "rodney.s.angry" " example.com")) ((NIL NIL "rodney.s.angry" "example.com")) (("Gryder, Connie" NIL "CONSTANCE.L.GRYDER" "example.com")) NIL NIL "< DD3761B99DC88F4284EDE00D608383C65DF16C(a)0088-its-exmp01.us.example.com>" NIL I don't understand what this error message means and why its flooding my logs. I do know the that the name in parenthesis on line one is a user on my email server. <rangry> is a user on my domain with a valid email account but I can't tell if the problem is coming from example.com or originating from <rangry>. Anyone happen to know what is causing this? I don't know if you guys need my config here so I don't want to flood this message. If this makes sense to anyone, please let me know what I can do to resolve this or keep this from flooding my email server. Thanks!

4 5

[Dovecot] log contents questions?
by Knute Johnson 24 May '08

24 May '08

I switched from using Pegasus and POP3 to Thunderbird and IMAP for my email. Now I get a lot of "Corrupted index cache file" errors in my log. Dovecot is running under Fedora 8 and is version 1.0.13-6.fc8. The Thunderbird is version 2.0.0.14 running under Windows XP. My wife's Blackberry is also using IMAP and not reporting any errors. Any ideas what the problem is or how to fix it? Thanks, knute... --------------------- Dovecot Begin ------------------------ Dovecot disconnects: Inactivity: 2 Time(s) Logged out: 2606 Time(s) in IDLE: 27 Time(s) **Unmatched Entries** dovecot: IMAP(knute): Connection closed: 5 Time(s) dovecot: IMAP(knute): Corrupted index cache file /home/knute/mail/.imap/CR-FFL/dovecot.index.cache: invalid record size: 3 Time(s) dovecot: IMAP(knute): Corrupted index cache file /home/knute/mail/.imap/INBOX/dovecot.index.cache: invalid record size: 2 Time(s) dovecot: IMAP(knute): Corrupted index cache file /home/knute/mail/.imap/frazmtn.com/dovecot.index.cache: invalid record size: 4 Time(s) dovecot: IMAP(linux): Connection closed: 4 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Dovecot/dovecot.index.cache: invalid record size: 2 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Fedora List/dovecot.index.cache: invalid record size: 4 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Fedora Selinux List/dovecot.index.cache: invalid record size: 1 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Fedora Test List/dovecot.index.cache: invalid record size: 2 Time(s) ---------------------- Dovecot End ------------------------- -- Knute Johnson linux(a)www.knutejohnson.com

2 4

[Dovecot] procmail --> deliver question
by Ben Budts 23 May '08

23 May '08

Hi there, I use dovecot-1.1-rc4, got imap, imaps, pop3 & pop3s working fine with the mbox format. I use sendmail-8.14.2 as an MTA, sendmail uses procmail as an LDA. I migrated to maildir format now, and pipe all my mail to deliver right now to be able to make use of the indexing etc... Problem is I run into some errors : #My .procmailrc PATH=/usr/bin:/usr/local/bin:/usr/sbin SHELL="/bin/bash" SENDMAIL="sendmail -oi -t" DELIVER="/opt/dovecot/libexec/dovecot/deliver" LOGFILE="$HOME/procmail.log" #/dev/null VERBOSE=on LOGABSTRACT = "all" #DEFAULT="$HOME/Maildir/" #MAILDIR="$HOME/Maildir/" :0 w | $DELIVER ##### My procmail.log : procmail: [12743] Wed May 21 13:43:38 2008 procmail: Assigning "LOGABSTRACT=all" procmail: Executing "/opt/dovecot/libexec/dovecot/deliver" Fatal: destination user parameter (-d user) not given procmail: Error while writing to "/opt/dovecot/libexec/dovecot/deliver" procmail: Program failure (64) of "/opt/dovecot/libexec/dovecot/deliver" procmail: Assigning "LASTFOLDER=/opt/dovecot/libexec/dovecot/deliver" procmail: Locking "/var/spool/mail/kris.lock" procmail: Assigning "LASTFOLDER=/var/spool/mail/kris" procmail: Opening "/var/spool/mail/kris" ####" It's not working out and he falls back to delivering his mail to /var/spool/mail/%u Could you guys point me out in the right direction please ? Another question about the logging with deliver... I've put the following in my deliver.conf : deliver.conf in the lda section : log_path = /var/log/dovecot/deliver.log info_log_path = /var/log/dovecot-deliver.log root@blaat:/home/kris# ls -la /var/log/dovecot/ total 232 drwxrwxrwx 2 root root 4096 2008-05-20 10:44 . drwxr-xr-x 11 root root 4096 2008-05-19 10:08 .. -rw-rw-rw- 1 root root 0 2008-05-20 10:44 deliver.log But it's not logging at all... Also tried the syslog alternative, no logging either. Also put set user or group ID on execution (s) on the deliver binary : -rwsr-sr-x 1 root root 693300 2008-05-19 09:38 /opt/dovecot/libexec/dovecot/deliver thx a lot Benjamin

2 1

[Dovecot] dovecot-sieve on freebsd
by Lazar Szilard 22 May '08

22 May '08

Hi,I need some help. I use dovecot and dovecot-sieve on a freebsd 7.0-release. everything worked fine without dovecot sieve. I want to deliver amavisd spam marked messages to the 'spam' folder of the user. the system uses virtual environment with multiple domains (and users).all want is a global sieve, to all users, all domains.I googled, but I cannot find the problem,my protocol lda section:protocol lda {    log_path = /usr/local/vmail/dovecot-deliver.log    sieve_global_dir = /usr/local/vmail/globalsieverc    mail_plugins = cmusieve    mail_debug = yes    log_path = /var/log/dovecot-deliver    info_log_path = /var/log/dovecot-deliver     postmaster_address = postmaster(a)tamann.hu    mail_plugin_dir = /usr/local/lib/dovecot/lda    sendmail_path = /usr/sbin/sendmail}globalsieverc:require "fileinto";if header :contains "X-Spam-Flag" "YES" {        fileinto "Spam";        stop;}thank you for your help,and sorry for my bad english.t

1 0

[Dovecot] auth_socket_path permissiones
by Adrián Ribao Martínez 22 May '08

22 May '08

Hello, I'm using dovecot 1.0 under debian etch. The lda socket path is set to: auth_socket_path = /var/spool/postfix/private/auth But this gives me the error: net_connect(/var/spool/postfix/private/auth) failed: Permission denied I suppose deliver is run as dovecot user. I read about running deliver as root with the suid bit set. I'm not quite sure if this is a good solution. Is there any other way. In the wiki says: "Most MTAs won't let you run deliver as root, so for now you'll need to make it setuid root. However deliver isn't designed to be run as setuid-root" My MTA is postfix, does someone know if postfix let me run deliver as root? If not, should I go to the setuid option? Thank you. -- Adrián Ribao Martínez

3 3

[Dovecot] Clients hang because imap-login discards post-login commands
by Mike Abbott 22 May '08

22 May '08

Some of my IMAP clients hang when connecting to Dovecot 1.1.rc5. I believe the problem is that imap-login reads eagerly rather than sparingly. If a client sends a login user password b select Inbox all at once, without waiting for the login reply before sending the select, imap-login eats the second command (reads it from the socket and does nothing with it; system call tracing confirms this) and the client hangs waiting for a reply to the select command. I can reproduce this simply using telnet to the dovecot on localhost, as long as I send both lines at once (I paste them in together). $ telnet localhost 143 * OK Dovecot ready. a login user password b select Inbox a OK Logged in. <dovecot never replies to select> This may also be true with pop3-login, I have not checked. It does happen (with IMAP) when authentication is delayed and Dovecot responds with "* OK Waiting for authentication process to respond.." but I believe that shares the same underlying cause as the simpler case above. I believe the login processes should read only as much as they need to satisfy the login request and leave subsequent commands in the socket for post-login processing. Or, the login processes should pass the remainder of their input buffers to the mail processes so no commands are dropped. This section of RFC 2060 explains why I think this: 5.5. Multiple Commands in Progress The client MAY send another command without waiting for the completion result response of a command, subject to ambiguity rules (see below) and flow control constraints on the underlying data stream. Similarly, a server MAY begin processing another command before processing the current command to completion, subject to ambiguity rules. [...] The exception is if an ambiguity would result because of a command that would affect the results of other commands. Clients MUST NOT send multiple commands without waiting if an ambiguity would result. If the server detects a possible ambiguity, it MUST execute commands to completion in the order given by the client. So it appears that both the client and Dovecot may be in violation, depending on how you define "ambiguity." The RFC does not explicitly define whether login causes an ambiguity, but I personally believe that login does "affect the results of other commands" (the login may fail, for instance). So the client should not issue commands before receiving the login reply, and Dovecot should not drop commands during login. I have reported the client issue to the developers of the IMAP client, as I am reporting the server issue to you. Fortunately for me, only one or the other needs to change to erase the symptom (hung clients), but fixing both would be best. Thanks for your attention.

3 2

[Dovecot] Dovecot or postfix Quota
by Adrián Ribao Martínez 22 May '08

22 May '08

Hello, I'm a bit confused with the dovecot quota support. What is it for? I thought postfix should be the one managing the quota. If I set up a quota in dovecot, does dovecot keep the messages size under certain limit? What happen when you reach the quota limit? What's the difference between postfix quotas and dovecot quota? I'm confused about this. Thank you! -- Adrián Ribao Martínez

3 4

[Dovecot] VMware and Time moved backwards
by Robert Henjes 22 May '08

22 May '08

Hi, I followed the discussions regarding the "time moved backward" problem and the use of ntp in such cases. At our department we are running two dovecot servers within an vmware server environment, and unfortunately the timedrift (with ntpd active) exceeds sometimes up to 30 minutes virtual drift within 10 minutes realtime (mostly into future). This is due to some overcorrections within the TSC algorithms of the vmware virtual machine. More information and some hints to workaround are documented here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=di… Nevertheless we are currently working on evaluating a stable solution by doing some system measurements, which would be the best option to cope with this problem, since the XEN environment seems to have a similar issue. Running "ntpdate -u" as a cronjob is not an option due to two facts: a) Time is moving quickly and may cause "major problems" ;) b) It is not recommended by the vmware team itself as well We are currently considering two options: a) Using the "clock=pit" kernel option, which may cause the system to be to slow b) using vmware tools and use only the ntp synchronisation of the host (we have currently only little experience with this). Also vmware tools are somewhat critical in case of updates. So our intention was to use as less vmware specific things as possible within the virtual machine, so only our host itself depends on vmware specific software. The question is, which option would you prefer? Is there another solution beside the mentioned ones? According to Timo's postings, workarounds within the dovecot itself to cope with "time moved backward" problems are not planned yet to be impelented. So best regards, Robert

5 5

Re: [Dovecot] VMware and Time moved backwards
by Robert Henjes 21 May '08

21 May '08

Thank you for the prompt answers @Luuk Vosslamber >finding correct values for the following entrys in your vmware(host) >config file might solve some things: >host.cpukHz = 1596000 <== depends on processor speed ;-) >host.noTSC = TRUE >ptsc.noTSC = TRUE >hostinfo.noTSC = TRUE >tools.syntime = TRUE > >Above values go with the presumption that the host CPU is running at a >fixed frequency. The variable frequency seems to be the origin of this >problem.. We tried your parameters already, but they are not an option, unless you have the following a) machine smp disabled (enabled in our case) b) other machines on the host system have really low load c) vmware tools should not be missing on guest @Peter Hessler >never ever ever run ntp on virtual hardware. > >instead, run ntp on the host hardware, and tell the client to always obey the bios clock. I add "* * * * * /sbin/hwclock --localtime -->hctosys" >to my crontab for that. Thank you very much Peter, this hint opens up a bunch of new possibilities only mentioning "adjtimex" ... BUT: And this brings me back to, why I posted this issue to the dovecot mailinglist and not elsewhere: All these guest based solutions lead to a fixed time movement (we used previously ntpdate -u every 7 minutes, ntp itself synchronizes every 11 minutes with the hardware clock for calculating drifts), which happens about once per week, that the time movement backward is larger than 11 seconds between two dovecot imap operations, which leads to an immediate shutdown of the dovecot process. All other services on these machine can cope with this. So the question is how to get these adjustments smooth or close to realtime. Best regards, Robert Btw.: We are running Dovecot 1.0.13 from Debian etch-backports (which is an important information since debian seems to have its own rules ;) )

1 0

[Dovecot] Maildir locking by LDA of dovecot
by Mike Grozak 21 May '08

21 May '08

Hi all! First of all, I want ti thank the whole Dovecot community (developers for developing and fast responses, users for populating and responses too). Dovecot is a really good and fast IMAP server - it serves near 3000 in our installation. Now I have a problem and request community's help its resolving;) Dovecot version: 1.0.13, compiled with vpopmail support. I have an account spam(a)domain.com (:-), in which we put all our spam (we gather statistic later). There can be 10 and more delivery attempts in a second to maildir of this account during the spam attacks on our server. The queue of our server can grow up to 20k messages, and all of these messages are sent to spam(a)domain.com. I found a lot of such strings in dovecot.log file during the such DoS attack: dovecot.log:deliver(spam@domain.com): May 16 04:18:48 Info: msgid=<01c8b6da$a8bacf80$b7af2abe@sale>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:18:59 Info: msgid=<6611811842.20080516012444(a)poiusadfhnvxzmdiasdasgkhlsdkfg.com>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:20:06 Info: msgid=<01c8b6a8$7b552e00$a0a4034c@sale>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:20:14 Info: msgid=<360825920.32055246029506(a)mirgames.ru>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:20:50 Info: msgid=<01c8b6b1$0df9cb00$cc36dfc9@tek2>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:21:00 Info: msgid=<087901c7ca2d$ef272640$1e01a8c0(a)telefonia.InterCable.net>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:21:01 Info: msgid=<000701c8b6d2$01ff999f$c491aca7@snoueiij>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:22:32 Info: msgid=<000801c8b69b$060c0230$3cd8a4b7@cpbvlrx>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:22:45 Info: msgid=<000801c8b6a5$04ba6412$9910848d@aldldr>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:22:45 Info: msgid=<031401c772e2$adc5be40$1e01a8c0(a)mtu-net.ru>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:23:08 Info: msgid=<01c8b6db$0222fe80$b7af2abe@info>: save failed to INBOX: Timeout while waiting for lock My dovecot.conf: $ cat /etc/dovecot.conf | grep -v \# | grep -v ^\n protocols = imap pop3 log_path = /var/log/dovecot.log ssl_disable = yes login_user = dovecot login_process_per_connection = no login_max_connections = 1024 login_greeting = Server is ready. >>dotlock_use_excl = yes - can it be the reason? fsync_disable = yes first_valid_uid = 39 last_valid_uid = 39 first_valid_gid = 39 last_valid_gid = 39 max_mail_processes = 1024 maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = yes protocol imap { mail_plugins = quota imap_quota login_greeting_capability = yes imap_client_workarounds = outlook-idle } protocol pop3 { pop3_lock_session = no pop3_uidl_format = %08Xu%08Xv mail_plugins = quota } protocol lda { postmaster_address = postmaster(a)tversu.ru mail_plugins = quota cmusieve sendmail_path = /usr/lib/sendmail fsync_disable = no } auth_cache_size = 10240 auth_username_format = %Lu auth default { mechanisms = plain login cram-md5 socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 } client { path = /var/spool/postfix/private/auth mode = 0666 user = postfix group = postfix } } passdb vpopmail { args = cache_key=%u dovecot } userdb vpopmail { } user = vpopmail ssl_require_client_cert = no } dict { } plugin { quota = maildir:ignore=Trash } What can I do for resolving this locks? May be, while looking into uidlist file, can dovecot LDA lock it? And other deliver processes can't open it and wait for him? --------------------------- WBR, Mike Grozak, TvSU IC

1 0

[Dovecot] Running sieve filters on already delivered mails
by Axel Gembe 20 May '08

20 May '08

I want to know what the best way to run sieve filters on already delivered mail is. Problem is that I have a rather large unfiltered mailbox and filtering it by hand would be a PITA. I don't mind coding something up to do this, but I just don't think that I'm the first one with this problem. Thanks - Axel

2 2

[Dovecot] Cannot compile current version of antispam
by Steffen Kaiser 20 May '08

20 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, with the current (2008-05-20) repository releases of Dovecot-1.0 and antispam the plugin no longer compiles: antispam-storage-1.0.c: In function âantispam_mail_update_keywordsâ: antispam-storage-1.0.c:285: error: âidxkwd__typeâ undeclared (first use in this function) antispam-storage-1.0.c:285: error: (Each undeclared identifier is reported only once antispam-storage-1.0.c:285: error: for each function it appears in.) antispam-storage-1.0.c:285: warning: type defaults to âintâ in declaration of âtype nameâ antispam-storage-1.0.c:285: warning: initialization from incompatible pointer type Version of antispam: (first entry of git log) commit c3a343290773d6e22a08946cb2ef80b1b8fe8a06 Author: Johannes Berg <johannes(a)sipsolutions.net> Date: Sat Apr 26 20:34:06 2008 +0200 add 1.1 storage. probably doesn't work Base version of Dovecot: changeset: 5551:71c02fdf1b59 branch: branch_1_0 tag: tip Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIMtunVJMDrex4hCIRAjXgAJ9j0oNUa0wGaLMshw6F/kjQoQxvygCdHLE9 Vb7rUcHxSr1kcgN+MHCsI1U= =dBuy -----END PGP SIGNATURE-----

2 2

[Dovecot] New ManageSieve releases: v0.10.2 for Dovecot 1.1.rc4 and v9.3 for Dovecot 1.0.13
by Stephan Bosch 20 May '08

20 May '08

Hello Dovecot users, Recently, I was pointed towards a problem in the managesieve SASL implementation. As it turns out there was a bug in handling mechanisms that expect more than a single client response. That is why the PLAIN mechanism works and the (obsolete) LOGIN mechanism fails (along with probably many others). This problem was present in both v9.2 and v0.10.1 for Dovecot 1.0 and 1.1 respectively. This issue is fixed in the new releases: Change Log v9.3/v0.10.2 ------------------------ * Fixed bug that caused SASL mechanisms that require more than a single client response to fail. Reported by Steffen Kaiser and occured when he tried using the (obsolete) LOGIN mechanism. * Updated installation and configuration documentation to match the information provided in the wiki Installation ------------ The full installation procedure and other relevant information regarding ManageSieve is finally available on the Dovecot wiki at: http://wiki.dovecot.org/ManageSieve New releases: 1.0: (patch) http://www.rename-it.nl/dovecot/1.0/dovecot-1.0.13-MANAGESIEVE-v9.3.diff.gz http://www.rename-it.nl/dovecot/1.0/dovecot-1.0.13-MANAGESIEVE-v9.3.diff.gz… 1.1: (package + patch) http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.2.tar.gz http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.2.tar.gz.s… http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.rc4-managesieve-0.10.2.diff… http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.rc4-managesieve-0.10.2.diff… (my public key (id: 3DFBB4F4) can be found at wwwkeys.pgp.net) Have fun testing the Dovecot ManageSieve service. Don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

2 1

[Dovecot] Looking for suggestions: How to strip attachments from mails
by Patrick Nagel 20 May '08

20 May '08

Hi, I know this is not 100% on-topic, but I'll try anyway... I'm looking for a way to strip attachments from incoming mails on the server. The attachments should be stored on a file server (where users have access via SAMBA) and only a link to the file (UNC path) should remain in the mail body. This is to prevent the mail storage from filling up with a large amount of big mails where at the same time the 'payload' (attached file) is not conveniently accessible by the users. The current setup is postfix / dovecot deliver / dovecot (with sieve plugin). I'm considering piping the mails through something like mimeStrip.pl (http://freshmeat.net/projects/mimestrip.pl/) but therefore I'd probably need to bring procmail/maildrop into the game, right? Or are there other (better) ways to accomplish this? Patrick. -- STAR Software (Shanghai) Co., Ltd. http://www.star-group.net/ Phone: +86 (21) 5427 7799 x 826 Fax: +86 (21) 6485 0071 PGP key: https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005

3 3

[Dovecot] RFC 3516 - IMAP4 Binary Content Extension
by Anton Yuzhaninov 20 May '08

20 May '08

Is Binary Content Extension (rfc3516) support planned? -- WBR, Anton Yuzhaninov

2 3

[Dovecot] child process killed with signal 11
by Zbigniew Szalbot 20 May '08

20 May '08

Hello, Today I have noticed such log entries May 19 23:57:32 relay dovecot: child 40857 (imap) killed with signal 11 I am using v. 1.0.13. Any idea what can be wrong? Dovecot does not die. It seems child processes are being killed. Thanks! -- Zbigniew Szalbot www.lc-words.com

2 1

[Dovecot] messages downloading repeatedly to mozilla/seamonkey pop3 client
by Ben Julian 20 May '08

20 May '08

Hello Dovecot List, I am a bit of a sysadmin novice and this is my first time emailing, so please let me know if I have left some critical information out. I am supporting a small office network supported primarily by linux servers. All of my users are using dovecot as a pop3 daemon on a centOS 5 box, no IMAP users. Seven users are running outlook 2003 on windows XP, two users are running thunderbird on ubuntu, two are running evolution on ubuntu, and one is running mozilla seamonkey on XP. Emails to the mozilla/seamonkey user are downloading multiple times, but not to any of the other users. A typical maillog report following this user's mail client pop3 login: Mar 3 10:37:00 servername dovecot: pop3-login: Login: user=<user>, method=PLAIN, rip=::ffff:192.168.99.13, lip=::ffff:192.168.99.4 Mar 3 10:37:00 servername dovecot: POP3(user): mbox sync: UID inserted in the middle of mailbox /var/mail/user (84873 > 84872, seq=2, idx_msgs=3) Mar 3 10:37:01 servername dovecot: POP3(user): mbox sync: UID inserted in the middle of mailbox /var/mail/user (84877 > 84872, seq=2, idx_msgs=4) Mar 3 10:37:01 servername dovecot: POP3(user): Disconnected: Logged out top=0/0, retr=1/3364, del=1/1, size=3347 Things I've tried: *adding the following lines to dovecot.conf: protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } *deleting the user's homedir mail directory (including all dovecot index files) *restarting dovecot *changing mail clients: tried outlook express, netscape 4.8, thunderbird on user's PC *restarting the server All changes resulted in only a brief (1-2hr) cessation of the problem. I've subscribed for a month or so now and searched the archives, but if I missed a solution to this in there, I apologize. Thanks, Ben Julian

4 7

[Dovecot] Webmail Recommendation
by Peter Sparkes 19 May '08

19 May '08

Hi, I want to install webmail. I am using Dovecot with Exim4. Recommendations requested please. Thanks Peter Sparkes

32 46

[Dovecot] Fixed a Duplicate?
by Nigel Allen 19 May '08

19 May '08

Greetings We have recently switched from mbox to Maildir so that we can implement symlinks for a large email account that is shared (partially) between some 20 or so users. The setup is dovecot-1.0.3-6.fc6, procmail-3.22-17.1, sendmail-8.13.8-2. Procmail has a single recipe in /etc/procmailrc that simply says "DEFAULT=$HOME/Maildir/". The problem is that I am seeing a lot of blank emails being created. For exaample, every time I open a folder from this shared account, I get either one or two emails being created on the spot. The are /always/ created with the current date and time stamp (i.e. now) and at the same time a tail -f of maillog shows something like this: > May 19 09:10:05 sydsrv56 dovecot: IMAP(plans): Fixed a duplicate: > dovecot-shared:2, -> 1211152205.P10039Q1.sydsrv56 The only thing that appears to change is the last modified date and time of the two files, dovecot.index.log and dovecot.index.cache. Should I be maintaining separate index files or lock files for each user in this shared account? Currently the Maildir is shared and has the g+s bit set. Any ideas where I can start looking would be appreciated. Rgds Nigel. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 3

[Dovecot] compile troubles - stat.mtim - 1.1hg
by Daniel Black 18 May '08

18 May '08

having trouble compiling dovecot-1.1hg latest pull I'm amost thinking _GNU_SOURCE needs to be defined as its built to work Any suggestions welcome. make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/dan/software_projects/dovecot-1.1/src/lib-storage/list' Making all in index make[4]: Entering directory `/home/dan/software_projects/dovecot-1.1/src/lib-storage/index' Making all in maildir make[5]: Entering directory `/home/dan/software_projects/dovecot-1.1/src/lib-storage/index/maildir' gcc -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../src/lib -I../../../../src/lib-mail -I../../../../src/lib-imap -I../../../../src/lib-index -I../../../../src/lib-storage -I../../../../src/lib-storage/index -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -I/usr/kerberos/include -MT maildir-uidlist.o -MD -MP -MF .deps/maildir-uidlist.Tpo -c -o maildir-uidlist.o maildir-uidlist.c maildir-uidlist.c: In function 'maildir_uidlist_update_hdr': maildir-uidlist.c:322: error: request for member 'st_mtim' in something not a structure or union make[5]: *** [maildir-uidlist.o] Error 1 make[5]: Leaving directory `/home/dan/software_projects/dovecot-1.1/src/lib-storage/index/maildir' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/dan/software_projects/dovecot-1.1/src/lib-storage/index' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/dan/software_projects/dovecot-1.1/src/lib-storage' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/dan/software_projects/dovecot-1.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/dan/software_projects/dovecot-1.1' fgrep HAVE_STAT config.h /* #undef HAVE_STATFS_MNTFROMNAME */ /* #undef HAVE_STATVFS_MNTFROMNAME */ #define HAVE_STAT_XTIM /* #undef HAVE_STAT_XTIMESPEC */ from config.log configure:28085: checking if struct stat has st_?tim timespec fields configure:28117: gcc -c -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 conftest.c >&5 conftest.c: In function 'main': conftest.c:104: warning: unused variable 'x' configure:28123: $? = 0 configure:28134: result: yes configure:28149: checking if struct stat has st_?timespec fields configure:28181: gcc -c -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 conftest.c >&5 conftest.c: In function 'main': conftest.c:105: error: 'struct stat' has no member named 'st_mtimespec' conftest.c:105: warning: unused variable 'x' configure:28187: $? = 1 configure: failed program was: Portage 2.1.4.4 (default-linux/amd64/2007.0, gcc-4.2.3, glibc-2.6.1-r0, 2.6.22-vs2.2.0.7-gentoo x86_64) ================================================================= System uname: 2.6.22-vs2.2.0.7-gentoo x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ Timestamp of tree: Sat, 17 May 2008 22:15:01 +0000 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] app-shells/bash: 3.2_p33 dev-java/java-config: 1.3.7, 2.1.6 dev-lang/python: 2.4.4-r9 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.4_p6, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.23-r3 features.h #ifdef _GNU_SOURCE # define _BSD_SOURCE 1 #endif .... #if defined _BSD_SOURCE || defined _SVID_SOURCE # define __USE_MISC 1 #endif sys/stat.h includes bits/stat.h #include <features.h> .... struct stat { .... #ifdef __USE_MISC /* Nanosecond resolution timestamps are stored in a format equivalent to 'struct timespec'. This is the type used whenever possible but the Unix namespace rules do not allow the identifier 'timespec' to appear in the <sys/stat.h> header. Therefore we have to handle the use of this header in strictly standard-compliant sources special. */ struct timespec st_atim; /* Time of last access. */ struct timespec st_mtim; /* Time of last modification. */ struct timespec st_ctim; /* Time of last status change. */ -- Daniel Black -- Proudly a Gentoo Linux User. Gnu-PG/PGP signed and encrypted email preferred http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x76677097 GPG Signature D934 5397 A84A 6366 9687 9EB2 861A 4ABA 7667 7097

3 2

[Dovecot] Postfix & Dovecot LDA
by Jochen Schulz 18 May '08

18 May '08

Hi, before I start to write a lengthy email about something that isn't really possible anyway: can I make Postfix use Dovecot's LDA and start it with different user IDs? My scenario: Dovecot authenticates users for Postfix and itself using Postgresql. Mails for two domains should be stored under /srv/<domain>/<user> (which is the location returned by my user_sql query and mail_location). When my clients login (with usernames of the form 'user@domain'), Dovecot creates/opens the correct mailboxes for them, but I can't get LDA to deliver to these mailboxes. Whatever I try, I am always running into some kind of permission problems (either for the mailboxes, or for auth_socket). I want to use a unique UID for every virtual domain, so I guess LDA needs to have permissions for every corresponding mailbox *and* Dovecot's auth_socket_path. Is there a good solution for this which doesn't involve severe security implications? J. -- If all my friends had Playstations I would buy a Nintendo to prove my individuality. [Agree] [Disagree] <http://www.slowlydownward.com/NODATA/data_enter2.html>

6 7

[Dovecot] problem about mbox with quota
by Zhang Huangbin 18 May '08

18 May '08

Hi, all. Does mbox format support quota? I got this error in log file: dovecot: May 18 02:10:36 Error: POP3(www(a)a.cn): Unknown quota backend: storage=10240 How can i solved it? Thanks very much. :) My dovecot configuration: # /etc/dovecot.conf log_path: /var/log/dovecot.log protocols: pop3 pop3s imap imaps ssl_cert_file: /etc/pki/dovecot/certs/dovecotCert.pem ssl_key_file: /etc/pki/dovecot/private/dovecotKey.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 mail_location: mbox:/%Lh/%Ld/%Ln:INBOX=/%Lh/%Ld/%Ln mbox_write_locks: dotlock fcntl mbox_min_index_size: 10240 mbox_very_dirty_syncs: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login user: vmail passdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot-mysql.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: vmail # /etc/dovecot-mysql.conf driver = mysql default_pass_scheme = CRYPT connect = host=127.0.0.1 dbname=vmail user=vmail password=6737$11626@27301!17044&11769*16758)17720 password_query = SELECT password FROM mailbox WHERE username='%u' AND active='1' user_query = SELECT 2000 AS uid, 2000 AS gid, "/home/vmail" AS home, maildir, CONCAT('storage=',quota) AS quota FROM mailbox WHERE username='%u' AND active='1' -- Best Regards. Zhang Huangbin - OpenBSD 4.2 -release, i386. - RHEL 5.1 Client

2 2

[Dovecot] Security Hole in 1.0.13?
by Lawrence Sheed 18 May '08

18 May '08

I'm running 1.0.13 If I run dovecot for a while, I see a /var/run/dotvecot folder created with the following: drwxr-xr-x 3 root root 4096 2008-05-18 13:30 dotvecot drwxr-xr-x 3 root root 4096 2008-05-18 13:47 . drwxr-xr-x 18 root root 4096 2008-05-18 13:47 .. srw------- 1 root root 0 2008-05-18 13:47 auth-worker.15138 srwxrwxrwx 1 root root 0 2008-05-18 13:47 dict-server drwxr-x--- 2 root dovecot 4096 2008-05-18 13:47 login -rw------- 1 root root 6 2008-05-18 13:47 master.pid It appears to be created by imap-login I've tried removing any dovecot remnants and reinstalling from the 1.0.13 tar.gz from the site. After starting dovecot again after a few minutes the files appear. The processes are running something on 6243 and 6244 (Presumably an exploit / login) I have iptables setup to only allow existing ports in/out so I think thats saved me so far. I've switched to courier-imap in the interim. Anyone want to assist in finding out how they are getting in? Definitely dovecot related. If I don't run dovecot, seems secure. As soon as I run dovecot, after a few minutes - rooted... dovecot.conf cat /etc/dovecot/dovecot.conf base_dir = /var/run/dotvecot protocols = imap imaps listen = * disable_plaintext_auth = no shutdown_clients = yes syslog_facility = local7 #<-- Ensure this is set up in syslog conf ssl_disable = no login_max_processes_count = 128 login_max_connections = 256 login_greeting = K-Tex IMAP Server # <-- CUSTOMISE FORYOUR SITE login_process_size = 64 login_process_per_connection = yes login_processes_count = 16 ssl_cert_file = /var/qmail/control/servercert.pem # /usr/local/etc/ssl/ italy1-cert.pem ssl_key_file =/var/qmail/control/clientcert.pem # /usr/local/etc/ssl/ italy1.pem first_valid_uid = 89 first_valid_gid = 89 protocol imap { listen = *:143 ssl_listen = *:993 #mail_plugins = quota imap_quota #login_greeting_capability = no mail_plugin_dir = /usr/local/lib/dovecot/imap imap_client_workarounds = outlook-idle } auth_process_size = 512 auth_cache_size = 512 auth_cache_ttl = 3600 auth default { mechanisms = plain # vpopmail authentication passdb vpopmail { #args = } # vpopmail userdb vpopmail { } user = root } dict { #quota = mysql:/etc/dovecot-dict-quota.conf } plugin { quota = maildir } namespace private { prefix = INBOX. inbox = yes }

7 15

[Dovecot] Development news
by Timo Sirainen 17 May '08

17 May '08

First a list of all the new features and their state: 1. http://hg.dovecot.org/dovecot-threadindexes/ THREAD=REFERENCES indexes. Missing NFS flushes, support for mmap_disable=yes, breaks when more than one session modifies at the same time. Not tested much if the replies are really correct at all. Also started THREAD=X-REFERENCES2 but it doesn't work as expected. 2. http://hg.dovecot.org/dovecot-virtualboxes/ Virtual mailboxes. Nothing changed since http://dovecot.org/list/dovecot/2008-March/029546.html 3. http://hg.dovecot.org/dovecot-condstore/ Implemented CONDSTORE, QRESYNC, ESEARCH, SEARCHRES and WITHIN extensions. The only known problem left is making CONDSTORE's STORE UNCHANGEDSINCE operation atomic, but it requires changing transaction log file format. Maybe I'll do it and just make v1.1 and v1.0 be able to read the format and just ignore the modseq in the record. Those code trees don't contain all the latest changes from v1.1 tree. So at some point I'll start merging all of them into one dovecot-1.2 code tree. v1.1 is coming along pretty nicely. I'll make a new RC release in a few days. After that probably one more and then v1.1.0. Tomorrow begins a 5 week lab course at school. Every day and about 8 hours a day. And then we'll also have to write these reports about what we have done and how/why, which takes quite a lot of time as well. After 5 weeks there's one free week and then probably another 2 week lab course if I get selected there. So I doubt I can get much Dovecot work done for the next two months. It's also likely that I won't be answering mails much in this list either.

2 3

[Dovecot] mysql index control allow nets
by Evaggelos Balaskas 17 May '08

17 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, I am using dovecot 1.0.13 with sieve plugin, index, control and allow nets in my userdb per user. I am trying to have the same configuration with dovecot 1.1 and MySQL. According to log files when a virtual user is connecting to dovecot, the dovecot reads from MySQL the correct values but dovecot doesnt create the dirs for INDEX, CONTROL and the allow_nets is bypasses. - From my logs : dovecot: May 14 20:56:23 Info: auth(default): master out: USER 12 ebalaskas(a)ebalaskas.gr uid=1002 gid=8 mail=maildir:/var/mail/ebalaskas.gr/ebalaskas INDEX=/var/mail/.index/ebalaskas.gr/ebalaskas CONTROL=/var/mail/.control/ebalaskas.gr/ebalaskas allow_nets=10.10.10.192 The connection is ok (i tested via telnet and webmail) but my IP is : 10.10.10.102 and there isnt any /var/mail/.index/ebalaskas.gr/ebalaskas or /var/mail/.control/ebalaskas.gr/ebalaskas folders The only thing is the folder : var/mail/ebalaskas.gr/ebalaskas the dovecot-sql.conf is correct (you can see this from my logs) so what is wrong ??? Evaggelos Balaskas - http://ebalaskas.gr Unix System Engineer Informatics Engineer Technological Education -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIKykUWIK+Pe9twhoRAhemAJ0ff793TAsqhDhrAZ7pbATLmDrJggCfXjDZ Cfiojr0LoJc0Vtif6XjfoTs= =Jeph -----END PGP SIGNATURE-----

2 5

[Dovecot] Panic: IMAP(...): Trying to close mailbox INBOX with open transactions
by Mike Abbott 16 May '08

16 May '08

I have been seeing this crash, which has been reported before but apparently not yet resolved. As with the previous reporters, I do not know how to reproduce it reliably. Dovecot version: 1.1.rc5 Operating system: Mac OS X 10.5.2 CPU architecture: x86 File system: HFS+ Activity: From the backtrace it appears the client logged out while in the middle of some operation. Backtrace: 0 libSystem.B.dylib 0x946210ea __kill + 10 1 libSystem.B.dylib 0x946983f2 raise + 26 2 libSystem.B.dylib 0x946a79af abort + 73 3 imap 0x000743e2 i_internal_fatal_handler + 102 4 imap 0x00073e03 i_fatal + 0 5 imap 0x0004614c mailbox_close + 48 6 imap 0x000053c4 cmd_logout + 74 7 imap 0x00007f14 client_command_input + 41 8 imap 0x000080d9 client_command_input + 494 9 imap 0x000081c5 client_handle_input + 218 10 imap 0x0000835d client_input + 176 11 imap 0x0007c001 io_loop_handler_run + 350 12 imap 0x0007af06 io_loop_run + 44 13 imap 0x00010732 main + 1972 14 imap 0x00001e76 start + 54

2 2

[Dovecot] Sieve plugins 1.0.3 and 1.1.5 released
by Timo Sirainen 16 May '08

16 May '08

http://dovecot.org/releases/sieve/dovecot-sieve-1.0.3.tar.gz http://dovecot.org/releases/sieve/dovecot-sieve-1.0.3.tar.gz.sig http://dovecot.org/releases/sieve/dovecot-sieve-1.1.5.tar.gz http://dovecot.org/releases/sieve/dovecot-sieve-1.1.5.tar.gz.sig I've usually released new Sieve plugins at the same time as new Dovecot versions, but since I wasn't planning on releasing v1.0.14 anytime soon and it looks like v1.0.2 release was quite a while ago, I decided to release these today. Changes: - Improved vacation reply checks, log discarded vacation replies (in v1.0.3, these were already in v1.1.0) - Expand ~ to home directory in sieve path - If compiled script has the exact same mtime as the source script, assume the script hasn't changed (changed "<" check to "<="). - Unfold multiline headers before comparing them. - Improved error logging.

1 0

[Dovecot] deliver exits with status 89 on some but not all mails of a batch
by Patrick Nagel 16 May '08

16 May '08

Hi, I'm trying to get dovecot's LDA 'deliver' to deliver mails that come in through a postfix daemon on the same box. I'm talking about dovecot version 1.0.rc15 (on CentOS 5 as Linux-VServer guest on a CentOS 5 host). Configuration ------------- # /etc/dovecot.conf ssl_cert_file: /etc/pki/selfmade/server.crt ssl_key_file: /etc/pki/selfmade/server.key 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 verbose_proctitle: yes mail_extra_groups: mail mail_location: maildir:~/Maildir 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: verbose: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: ldap args: /etc/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: dovecot group: dovecot dovecot-ldap.conf looks like this: uris = ldap://dbserver dn = cn=dovecot,ou=services,dc=company,dc=net dnpass = secret ldap_version = 3 base = ou=people,dc=company,dc=net scope = onelevel user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = (&(objectClass=posixAccount)(uid=%n)) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = LDAP-MD5 postfix has mailbox_transport set to dovecot, and master.cf contains the following: dovecot unix - n n - - pipe flags=DRhu user=fry:fry argv=/usr/libexec/dovecot/lda/deliver -d ${recipient} Problem ------- When a lot of mails come in 'at the same time', for example because an employee mailed all other (local) employees, the following happens: Some mails are being delivered as advertised, but on some mails, deliver exits with status 89 and the message bounces. Here is a (postfix) log that illustrates the problem. I replaced all receivers with 'xy', but they are in fact all different. May 13 17:58:32 mail1 postfix/smtpd[28164]: connect from unknown[192.168.0.103] May 13 17:58:32 mail1 postfix/smtpd[28164]: 1D6508FD93FF: client=unknown[192.168.0.103] May 13 17:58:33 mail1 postfix/cleanup[28165]: 1D6508FD93FF: message-id=<200805131758288906193(a)company.net> May 13 17:58:33 mail1 postfix/qmgr[27255]: 1D6508FD93FF: from=<zz(a)company.net>, size=1613090, nrcpt=31 (queue active) May 13 17:58:33 mail1 postfix/smtpd[28164]: disconnect from unknown[192.168.0.103] May 13 17:58:33 mail1 postfix/pipe[28169]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=1.9, delays=1.5/0/0/0.35, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:33 mail1 postfix/pipe[28299]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=1.9, delays=1.5/0.02/0/0.34, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:33 mail1 postfix/pipe[28168]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=1.9, delays=1.5/0/0/0.35, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:33 mail1 postfix/pipe[28298]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=1.9, delays=1.5/0.01/0/0.34, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28362]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.21/0/0.95, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:34 mail1 postfix/pipe[28304]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.1/0/1.1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28320]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.13/0/1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28311]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.12/0/1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28313]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.12/0/1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28306]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.11/0/1.1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28333]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.14/0/1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28317]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.12/0/1.1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28337]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.16/0/1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28342]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.8, delays=1.5/0.17/0/1.1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28368]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.9, delays=1.5/0.23/0/1.1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:35 mail1 postfix/pipe[28364]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.1, delays=1.5/0.22/0/1.4, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:35 mail1 postfix/pipe[28350]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.2, delays=1.5/0.19/0/1.5, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:35 mail1 postfix/pipe[28376]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.3, delays=1.5/0.26/0/1.6, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:35 mail1 postfix/pipe[28375]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.3, delays=1.5/0.25/0/1.6, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:35 mail1 postfix/pipe[28334]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.3, delays=1.5/0.15/0/1.7, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:35 mail1 postfix/pipe[28347]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.3, delays=1.5/0.18/0/1.6, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:35 mail1 postfix/pipe[28372]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.3, delays=1.5/0.24/0/1.6, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:35 mail1 postfix/pipe[28355]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.5, delays=1.5/0.2/0/1.7, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:35 mail1 postfix/pipe[28340]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.5, delays=1.5/0.17/0/1.8, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:36 mail1 postfix/pipe[28366]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=4, delays=1.5/0.23/0/2.2, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:36 mail1 postfix/pipe[28325]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=4.2, delays=1.5/0.13/0/2.5, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:36 mail1 postfix/pipe[28323]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=4.2, delays=1.5/0.13/0/2.5, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:36 mail1 postfix/pipe[28330]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=4.2, delays=1.5/0.14/0/2.5, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:36 mail1 postfix/pipe[28359]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=4.3, delays=1.5/0.2/0/2.5, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:36 mail1 postfix/pipe[28354]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=4.4, delays=1.5/0.19/0/2.6, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:51 mail1 postfix/smtp[28292]: 1D6508FD93FF: to=<xy(a)company.net>, relay=10.10.0.1[10.10.0.1]:25, delay=20, delays=1.5/0.09/1.3/17, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 3E8611881EB) May 13 17:58:52 mail1 postfix/cleanup[28160]: F0CE98FD9453: message-id=<20080513095851.F0CE98FD9453(a)mail1.city.company.net> May 13 17:58:52 mail1 postfix/qmgr[27255]: F0CE98FD9453: from=<>, size=7408, nrcpt=1 (queue active) May 13 17:58:52 mail1 postfix/bounce[28379]: 1D6508FD93FF: sender non-delivery notification: F0CE98FD9453 May 13 17:58:52 mail1 postfix/qmgr[27255]: 1D6508FD93FF: removed Does anybody have an idea what could cause this behaviour? How to debug? Patrick. -- STAR Software (Shanghai) Co., Ltd. http://www.star-group.net/ Phone: +86 (21) 5427 7799 x 826 Fax: +86 (21) 6485 0071 PGP key: https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005

2 7

[Dovecot] Dovecot dying when deliver is called
by MyGoddess 15 May '08

15 May '08

Hello, I run a debian etch server with the mail services configured like their: http://workaround.org/articles/ispmail-etch/ It worked during month but of the last upgrade it doesn't work anymore when postfix calls deliver. dovecot version is 1.0.rc15. I don't remember which was the previous version. There is no error accessing dovecot in any other way. Here my configuration: # /etc/dovecot/dovecot.conf log_path: /var/log/dovecot_err.log info_log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 pop3s imap imaps 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_privileged_group: mail mail_location: maildir:/home/vmail/%d/%n mail_debug: yes mail_drop_priv_before_exec: 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 pop3_uidl_format(default): pop3_uidl_format(imap):You can find a copy of the pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: plain login passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: static args: uid=1004 gid=1005 home=/home/vmail/%d/%n allow_all_users=yes 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: vmail I am not able to get a coredump. You can find a copy of the error mail attached. I didn't get any message from log files. If someone have any clue, I will helping. Regards, Pierrick Caillon

3 5

[Dovecot] moving folders bug - rc4
by Anil 15 May '08

15 May '08

I am fairly new to dovecot... I had a user who in outlook tried to move one of the folders into another folder but it crapped out. User tried to move "Djans*" folders into Koi folder. The subscription seems to show the folder move but the actual data is still under ".ClickEats.Clients.Djans" instead of ".ClickEats.Clients.Koi.Djans*. How do I fix this? Thanks. root@the:/apps/mail/clickeats.com/juliam/Maildir# grep -i djan subscriptions ClickEats.Restaurants.Djan's ClickEats.Clients.Koi.Djans.Online Orders ClickEats.Clients.Koi.Djans root@the:/apps/mail/clickeats.com/juliam/Maildir# ls -a |grep -i djan .ClickEats.Clients.Djans .ClickEats.Clients.Djans.Online Orders .ClickEats.Restaurants.Djan's root@the:/apps/mail/clickeats.com/juliam/Maildir#

2 1

[Dovecot] Automounted home dirs not working
by Roy McMorran 15 May '08

15 May '08

I'm testing Dovecot as a possible replacement for UW. In my environment the home directories are automounted via NFS from a NetApp. In general this works fine, but Dovecot isn't picking up the automounted directories. Consider the case of Arthur Dent, test user: May 12 10:30:24 testbed dovecot: [ID 107833 mail.info] imap-login: Login: user=<adent>, method=PLAIN, rip=xxx.xxx.xxx.242, lip=xxx.xxx.xxx.242, secured May 12 10:30:24 testbed dovecot: [ID 107833 mail.error] IMAP(adent): mkdir_parents(/home/adent/Mail) failed: No such file or directory May 12 10:30:24 testbed dovecot: [ID 107833 mail.error] IMAP(adent): Mail storage creation failed with mail_location: mbox:/home/adent/Mail:INBOX=/var/mail/adent May 12 10:30:24 testbed dovecot: [ID 961074 mail.error] child 21816 (imap) returned error 89 (if however I make sure that /home/adent is mounted at the server (eg. cd /home/adent) prior to starting the mail client this error does not occur) Why isn't the automount succeeding? This is Dovecot Version 1.0.13. I'm running under Solaris 10. Thanks! Roy PS: [root@testbed][ /var/log ]# dovecot -n # 1.0.13: /etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/imapd.pem ssl_key_file: /etc/ssl/private/imapd.pem disable_plaintext_auth: no 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/local/libexec/dovecot/pop3-login verbose_proctitle: yes mail_privileged_group: mail mail_location: mbox:~/Mail:INBOX=/var/mail/%u mmap_disable: yes dotlock_use_excl: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/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/local/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xv%08Xu auth default: mechanisms: plain login passdb: driver: pam passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: passwd userdb: driver: ldap args: /etc/dovecot-ldap.conf -- Roy McMorran Systems Administrator MDI Biological Laboratory mcmorran(a)mdibl.org

3 7

Re: [Dovecot] Time moved backwards
by Eugene 15 May '08

15 May '08

Hi people, > From: Adam McDougall <mcdouga9(a)egr.msu.edu> > I would just like to mention a circumstance that happened to me this > Sunday. We had a total power outage in our building, longer than our > UPS's could last and we don't have a generator for servers (nor is it > economical or needed). When the power came back on, my local NTP server > came on at the same time as my mail servers, as well a majority of my > other servers. My servers tried to step their time to be in sync with > my local NTP server, which was still busy trying to sync itself with > outside sources, which takes a while, so my mail servers did not get an > answer. Later, dovecot died because the time finally synced, and I > found out why pretty quick (have seen this before) but this was an > unusual situation. > > My point is, we had an unusual circumstance, and even though I've taken > steps to have my mail servers sync their time at boot and run ntpd > afterwards, there are some circumstances in which this is not enough, > and dovecot still died. Its not always because someone was lazy about > their time setup. My point exactly. It's amazing how some people are quick to ramble about someone else's administrative incompetence without taking time to read the situation. (One person even suggested hacking the dovecot startup script to run ntpdate -- useless as ntpd already occupies the ports). Fact is, ntpd can take unpredictable delay before the initial time-step. Delay that can't be controlled, and it would be unreasonable to delay starting mail services until it is guaranteed to complete. Then, dovecot dies, and admin (who is not always immediately available) has to start it manually anyway (especially as it is not clear what to do with possibly unsynced timestamps) -- only after the unnecessary downtime. So, the question is: why on earth can't we add a single line of code to dovecot to restart itself after terminating? Kind of reminds me of the "fsck_y_enable=YES" option in rc.conf. Without it, if fsck does not like someting during reboot, the server would just sit there in single-user prompt, waiting for (expensive) console operations. Best wishes Eugene

5 6

Re: [Dovecot] thunderbird sane config (OT)
by Moser 15 May '08

15 May '08

rosenfield.albert(a)gmail.com schrieb: > The simplest approach in my situation seems to be the XPI one, where > users can install an XPI into Thunderbird and get a template that > requires only entering username and password. > > Haven't figured how to put the CA certificate that Dovecot uses for > SSL IMAP into the XPI for installation into Thunderbird's certificate > store, but things are definitely improving :-). Isn't this one click at accessing the server the first time!? "Accept this certificate permanently"? But if you figured out, how to add it, let me know! :) Hans

2 1

[Dovecot] Allow_nets + MySQL failing when using range notation
by Javier García 15 May '08

15 May '08

Hello all, I am testing my dovecot installation in order to restrict access via POP3 for IPs outside my network. I have read and understood the instructions in the wiki and I have reached a configuration that works ONLY when single IPs are listed in allow_nets but not when ranges in the notation x.x.x.x/y are listed. Some examples should be more explanatory. I am using 1.0.rc15 patched as for last week as distributed in Debian etch. First of all, everything related to this is stored in a MySQL database, here is my password query: password_query = SELECT u.password as password, t.allow_nets as allow_nets FROM users u, access_type t WHERE u.ID_access_type = t.ID_access and ( t.%Ls = 1 ) and u.mail = '%u' This one should validate all mail addresses when the protocol used is marked as 1 in table access_type and when the allow_nets value in this same table contains the IP used for the access request. The, if access_type looks like: ID_access pop3 imap allow_nets 3 0 1 10.34.128.0/23, 10.34.133.0/24, 192.168.0.0/24 users with ID_access=3 fail to login by either pop3 (normal, value is 0) or imap. Here is the corresponding excerpt from dovecot.log: dovecot: 2008-03-31 11:29:04 Info: auth-worker(default): sql(user(a)domain.com,10.34.133.104): query: SELECT u.password as password, t.allow_nets as allow_nets FROM users u, access_type t WHERE u.ID_access_type = t.ID_access and ( t.imap = 1 ) and u.mail = 'user(a)domain.com' dovecot: 2008-03-31 11:26:39 Info: auth-worker(default): auth(user(a)domain.com,10.34.133.104): allow_nets: Matching for network 192.168.0.0/24 dovecot: 2008-03-31 11:26:39 Info: auth-worker(default): auth(user(a)domain.com,10.34.133.104): allow_nets: Matching for network 10.34.128.0/23 dovecot: 2008-03-31 11:26:39 Info: auth-worker(default): auth(user(a)domain.com,10.34.133.104): allow_nets: Matching for network 10.34.133.0/23 dovecot: 2008-03-31 11:26:39 Info: auth-worker(default): passdb(user(a)domain.com,10.34.133.104): allow_nets check failed: IP not in allowed networks but if it looks like ID_access pop3 imap allow_nets 3 0 1 10.34.133.105, 10.34.133.104 then access is allowed by IMAP dovecot: 2008-03-31 11:34:01 Info: auth-worker(default): sql(user(a)domain.com,10.34.133.104): query: SELECT u.password as password, t.allow_nets as allow_nets FROM users u, access_type t WHERE u.ID_access_type = t.ID_access and ( t.imap = 1 ) and u.mail = 'user(a)domain.com' dovecot: 2008-03-31 11:34:01 Info: auth-worker(default): auth(user(a)domain.com,10.34.133.104): allow_nets: Matching for network 10.34.133.105 dovecot: 2008-03-31 11:34:01 Info: auth-worker(default): auth(user(a)domain.com,10.34.133.104): allow_nets: Matching for network 10.34.133.104 dovecot: 2008-03-31 11:34:01 Info: auth(default): client out: OK 1 user=user(a)domain.com while POP3 still disallowed as expected: dovecot: 2008-03-31 11:34:25 Info: auth-worker(default): sql(user(a)domain.com,10.34.133.104): query: SELECT u.password as password, t.allow_nets as allow_nets FROM users u, access_type t WHERE u.ID_access_type = t.ID_access and ( t.pop3 = 1 ) and u.mail = 'user(a)domain.com' dovecot: 2008-03-31 11:34:25 Info: auth-worker(default): sql(user(a)domain.com,10.34.133.104): unknown user So, is there a bug related to the IP class notation or am I doing something wrong? I have tried to leave a single class (10.34.133.0/24), to explicitly erase any spaces after the commas, but nothing of these worked. Also, note that using 0.0.0.0/0 behaves as expected, this is, access for any IP is allowed. Thanks in advance, Javier

3 8

[Dovecot] Mixed maildir and mbox folder
by Stefan Klatt 15 May '08

15 May '08

Hello, i tried to implement a mixed structure of mbox for spams and spam backscatters and maildir for the rest at dovecot 1.0.13. I used the information at the dovecot wiki: http://wiki.dovecot.org/Namespaces (Multiple Mailbox Locations) But if i try this (complete config is attached with this part) namespace: type: private separator: / prefix: "#md/" location: maildir:/srv/imapd/user/%u/maildir inbox: yes hidden: yes namespace: type: private separator: / location: mbox:/srv/imapd/user/%u/Spam thunderbird can't open a maildir folder:-( The msg is " Mailbox doesn't exist: XXXX" If i use this version: namespace: type: private separator: / location: maildir:/srv/imapd/user/%u/maildir inbox: yes namespace: type: private separator: / prefix: "#mb/" location: mbox:/srv/imapd/user/%u/Spam hidden: yes Thunderbird can open maildir folder but no mbox folder.. " Mailbox doesn't exist: XXXX" :-( Where is my fault? Or is this feature first complete implemented at 1.1? I configured namespaces without hidden like a charme... with hidden i run against a wall :-( Other question... has anybody a script to delete messages older then XY days in a mbox file? Here is my complete config with the first config version: [root@kronos etc]# dovecot -n # 1.0.13: /etc/dovecot.conf ssl_cert_file: /etc/pki/tls/certs/xyz.cert ssl_key_file: /etc/pki/tls/private/xyz.key 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_process_size: 32 mail_access_groups: email dotlock_use_excl: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins: zlib mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle tb-extra-mailbox-sep imap_client_workarounds(imap): outlook-idle tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle namespace: type: private separator: / prefix: #md/ location: maildir:/srv/imapd/user/%u/maildir inbox: yes hidden: yes namespace: type: private separator: / location: mbox:/srv/imapd/user/%u/Spam namespace: type: public separator: / prefix: Public/ location: maildir:/srv/imapd/shared/public/maildir:CONTROL=/srv/imapd/user/%u/shared-settings/public/control:INDEX=/srv/imapd/user/%u/shared-settings/public/index namespace: type: public separator: / prefix: Archiv/ location: mbox:/srv/imapd/shared/archiv/maildir:CONTROL=/srv/imapd/user/%u/shared-settings/archiv/control:INDEX=/srv/imapd/user/%u/shared-settings/archiv/index auth default: passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: static args: uid=600 gid=600 Stefan

2 2

[Dovecot] homedir override problem, MS AD + WINBIND + PAM + SIEVE
by Milan Koudelka - Internet Mall 15 May '08

15 May '08

Hello, i installed my Dovecot with authetification in MS AD throught WINBIND and PAM. Works fine. So I have virtual users with UID, GID from MS AD. I set maildir path as mail_location = maildir:/var/spool/mail/%n/ Then i want to make some vacation system. I install sieve and use dovecot LDA. In postfix main.cf I have mailbox_command = /usr/libexec/dovecot/deliver Setup of lda in dovecot.conf protocol lda { postmaster_address = postmaster(a)mail-server.cz log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log mail_plugins = cmusieve } Sieve user-scripts doesn't work without this: plugin { sieve = /var/spool/mail/%n/.dovecot.sieve } With this settings, LDA and sieve works OK. I can use user-scrips to forward mail by subject or something like this. Vacation rules works too. But it isn't create .dovecot.lda-dupes in user home directory that contains e-mail addresses that was replied. So vacation is sent always. I have this error in dovecot-deliver.log deliver(mkoudelka): May 14 12:24:19 Error: open(/home/MALL/mkoudelka/.temp.cz-dc1-s-018.mall.cz.11302.7e2cc05a1e1df1a7) failed: No such file or directory I tried to override home directory by set this: userdb passwd { args = home=/var/spool/mail/%n } But there isnt't any change. Can you please, help how to set correct home for sieve ? MALL is domain of user mkoudelka. Thank you -- Milan Koudelka Linux & Network Administrator Internet Mall, a.s. Internet Mall - obchody, které si oblíbíte. http://www.MALL.cz ---------------------- Neprehlednete sirokou nabidku benzinovych a elektrickych sekacek. Vyberte si z desitek modelu za akcni ceny na Sekacky.cz. Sezona prave zacina. http://www.sekacky.cz/rotacni-sekacky/ ----------------------

3 2

[Dovecot] Disconnected: BUG internal error
by Ainsley Pereira 15 May '08

15 May '08

Hello, I'm seeing some messages from dovecot in my logs such as: May 8 11:43:41 snowdrift dovecot: IMAP(username): Disconnected: BUG: Unknown internal error I did some searching, and discovered a similar report last month, to which there was a request for more information that didn't seem to get followed up, so I have collected this information too. Dovecot version: 1.0.10 (from Ubuntu hardy package, which includes some patches; details of the patches can be found here: http://svn.debian.org/wsvn/collab-maint/deb-maint/dovecot/trunk/debian/patc… ) OS: Ubuntu 8.04 (Hardy) CPU: x86 Filesystem: ext3 IMAP client: Thunderbird. What was happening with it is not too clear, unfortunately it only seems to occur for one user, and that's not me. Reproducability: Seems to occur fairly frequently, but unable to provide steps. dovecot -n output: # 1.0.10: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps pop3s ssl_cert_file: /etc/ssl/certs/snowdrift-cert.pem ssl_key_file: /etc/ssl/private/snowdrift-key.pem ssl_cipher_list: ALL:!LOW:!SSLv2 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_location: mbox:~/mail:INBOX=/var/mail/%u mail_debug: yes mail_executable(default): /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/rawlog /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 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: passdb: driver: pam userdb: driver: passwd Raw log output: 29 OK Fetch completed. * 632 FETCH (UID 14265 RFC822.SIZE 4373) * BYE BUG: Unknown internal error Immediately before that was a set of headers from an email, so I guess that's what the "29" line's talking about, and it's just the last two that are relevant. Please let me know if there's anything further I can provide to help track this down. Thanks, Ainsley

2 1

[Dovecot] unix style mbox and vmain maildir on the same server
by Glen Lee Edwards 15 May '08

15 May '08

Hi, I'm new to dovecott. Using version 1.0.rc15. I have a mail server that has both the old style unix mbox in /var/mail/%u, and virtual mail maildir in /var/vmail/%d/%n. Debian Linux Etch stable. I'm trying to get dovecot to deliver to /var/mail/%u using mbox format, and to deliver to /var/vmail/%d/%n using maildir format. I can't get it do work. I can get it to access both directories, but not use the two formats. This is what I tried last: namespace private { separator = / inbox = yes hidden = yes prefix = location = mbox:~/mail:INBOX=/var/mail/%u } namespace private { separator = / inbox = no hidden = yes prefix = mail/ location = maildir:/var/vmail/%d/%n } I have since commented out the above two namespaces and set mail_location to mail_location = maildir:/var/vmail/%d/%n. $ dovecot -n # /etc/dovecot/dovecot.conf 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_privileged_group: mail mail_location: maildir:/var/vmail/%d/%n 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 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: plain login passdb: driver: pam args: dovecot passdb: driver: passwd args: blocking=yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: static args: uid=2000 gid=2000 home=/var/vmail/%d/%n allow_all_users=yes 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: vmail Glen

3 5

[Dovecot] Dovecot immediate logout (imap4)
by Дмитрий Бригадиров 15 May '08

15 May '08

I've experienced with automatic client logout (probably after IDLE command sent by a client). I simply run any imap4 client and get this in mail.log: May 14 18:26:37 athlon dovecot: imap-login: Login: user=<neptunix(a)tehexergo.ru>, method=PLAIN, rip=192.168.0.3, lip=192.168.0.3, secured May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Loading modules from directory: /usr/lib/dovecot/modules/imap May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Module loaded: /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Module loaded: /usr/lib/dovecot/modules/imap/lib11_imap_quota_plugin.so May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Effective uid=112, gid=118, home=/var/spool/mail/tehexergo.ru/neptunix May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): maildir: data=/var/spool/mail/tehexergo.ru/neptunix/Maildir:INDEX=/var/spool/mail/tehexergo.ru/neptunix May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): maildir: root=/var/spool/mail/tehexergo.ru/neptunix/Maildir, index=/var/spool/mail/tehexergo.ru/neptunix, control=, inbox= May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Disconnected: Logged out May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Loading modules from directory: /usr/lib/dovecot/modules/imap May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Module loaded: /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Module loaded: /usr/lib/dovecot/modules/imap/lib11_imap_quota_plugin.so May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Effective uid=112, gid=118, home=/var/spool/mail/tehexergo.ru/neptunix May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): maildir: data=/var/spool/mail/tehexergo.ru/neptunix/Maildir:INDEX=/var/spool/mail/tehexergo.ru/neptunix May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): maildir: root=/var/spool/mail/tehexergo.ru/neptunix/Maildir, index=/var/spool/mail/tehexergo.ru/neptunix, control=, inbox= May 14 18:26:37 athlon dovecot: imap-login: Login: user=<neptunix(a)tehexergo.ru>, method=PLAIN, rip=192.168.0.3, lip=192.168.0.3, secured May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Disconnected: Logged out May 14 18:26:37 athlon dovecot: imap-login: Login: user=<neptunix(a)tehexergo.ru>, method=PLAIN, rip=192.168.0.3, lip=192.168.0.3, secured May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Loading modules from directory: /usr/lib/dovecot/modules/imap May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Module loaded: /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Module loaded: /usr/lib/dovecot/modules/imap/lib11_imap_quota_plugin.so May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Effective uid=112, gid=118, home=/var/spool/mail/tehexergo.ru/neptunix May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): maildir: data=/var/spool/mail/tehexergo.ru/neptunix/Maildir:INDEX=/var/spool/mail/tehexergo.ru/neptunix May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): maildir: root=/var/spool/mail/tehexergo.ru/neptunix/Maildir, index=/var/spool/mail/tehexergo.ru/neptunix, control=, inbox= May 14 18:26:37 athlon dovecot: IMAP(neptunix(a)tehexergo.ru): Disconnected: Logged out 3 login attempts each after another. Any way client shows me the inbox and I can manage mail just fine. However it disconnects every time instead of using idle command (this I my guess). Don't know the reason for such a strange situation. Thanks for any help in advance. By the way I can't get rawlog to work. It doesn't write any logs to home directory. dovecot 10.0.10 (from ubuntu hardy repository) dovecot -n # 1.0.10: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S ssl_cert_file: /etc/ssl/private/exim.pem ssl_key_file: /etc/ssl/private/exim.pem verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_greeting: Dovecot MUA ready. login_max_processes_count: 32 login_max_connections: 64 max_mail_processes: 256 verbose_proctitle: yes first_valid_uid: 100 mail_privileged_group: mail mail_location: maildir:/var/spool/mail/%d/%n/Maildir:INDEX=/var/spool/mail/%d/%n mail_debug: yes mail_executable: /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap mail_plugins: quota imap_quota auth default: 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: mail plugin: quota: maildir -- Dmitry Brigadirov

3 4

[Dovecot] missing slash when concatenating strings from userdb static?
by Elod 15 May '08

15 May '08

Dovecot version: 1.0.13 Linux: Debian Testing (kernel 2.6.22) Fs: local # 1.0.13: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap pop3 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 valid_chroot_dirs: /home/email mail_chroot: /home/email first_valid_uid: 109 last_valid_uid: 109 first_valid_gid: 65534 last_valid_gid: 65534 mail_access_groups: nogroup mail_privileged_group: mail mail_location: maildir:~/Maildir 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 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: passdb: driver: passwd-file args: /home/email/%d/passwd userdb: driver: static args: uid=email gid=nogroup home=/%d/%n It finds mails with "/%d/%n" but not with "%d/%n". At another site I have the same version, but with an SQL backend. That one works beautifully with relative (to chroot dir) paths. -- Valkai Elõd

2 1

[Dovecot] need help
by Gabriele Fergola 14 May '08

14 May '08

I tried to migrate from a server courier to dovecot with imapsync but i get this errore: Couldn't append msg #15 (Subject:[Registrazione]) to folder INBOX: Error sending command '16 APPEND INBOX (\Answered \Seen) "" {3478} ': 16 BAD Invalid internal date. thk you in advance Workino

2 2

[Dovecot] Problem with virtual mail user login users uid not permitted
by Neil Muller 14 May '08

14 May '08

Hello, I am trying to run exim 4.68 and dovecot 1.0.13 on Solaris 10 x86 5/08 using dovecot lda and sieve with virtual users and domains, tls and ssl. At the moment certificates are from my internal CA Exim and Dovecot, dovecot lda and dovecot sieve were downloaded and installed from Blastwave. Mail delivery (ie from Exim to dovecot via dovecot lda) is working correctly but when I try to access mail using imap from a client (eg. Thunderbird) the login fails. My mail user for accessing virtual user mail is vmail (uid=954, gid=954). I have attached the messages from dovecot.log and the output of dovecot -n below as well as contents from the passdb file. Can anyone point me to where I've gone wrong, I've had this working fine on Linux but Solaris just doesn't seem to want to play :-) Thanks, Neil -- E neil(a)neologix.net My passdb file contents: lothar# cat /opt/csw/etc/vmail/comms.neologix/passwd neil:{MD5-CRYPT}$1$Lik.5MFj$PJKYoXEfADgTiK1PI6aa01:954:954::/export/ home/vmail/comms.neologix/users/ neil::userdb_quota=maildir:storage=10240 mail_plugins=cmusieve,quota,imap_quota sieve=.dovecot.sieve Contents of dovecot.log: dovecot: May 12 15:13:45 Info: auth(default): passwd-file /opt/csw/etc/ vmail/comms.neologix/passwd: Read 2 users dovecot: May 12 15:13:45 Info: auth(default): passwd-file(neil(a)comms.neologix ,192.168.1.100): lookup: user=neil file=/opt/csw/etc/vmail/ comms.neologix/passwd dovecot: May 12 15:13:45 Info: auth(default): client out: OK 1 user=neil(a)comms.neologix mail_plugins=cmusieve,quota,imap_quota sieve=.dovecot.sieve dovecot: May 12 15:13:45 Error: user neil(a)comms.neologix: Logins with login_user's UID 954 not permitted (see http://wiki.dovecot.org/ UserIds). dovecot: May 12 15:13:45 Info: auth(default): master in: REQUEST 1 16850 1 dovecot: May 12 15:13:45 Info: auth(default): passwd(neil(a)comms.neologix,192.168.1.100): lookup dovecot: May 12 15:13:45 Info: auth(default): passwd(neil(a)comms.neologix,192.168.1.100): unknown user dovecot: May 12 15:13:45 Info: auth(default): passwd-file(neil(a)comms.neologix ,192.168.1.100): lookup: user=neil file=/opt/csw/etc/vmail/ comms.neologix/passwd dovecot: May 12 15:13:45 Info: auth(default): master out: USER 1 neil(a)comms.neologix uid=954 gid=954 home=/export/home/ vmail/comms.neologix/users/neil quota=maildir:storage=10240 dovecot: May 12 15:13:45 Info: imap-login: Internal login failure: user=<neil(a)comms.neologix>, method=PLAIN, rip=192.168.1.100, lip=192.168.1.229, TLS The output from dovecot -n is: lothar# dovecot -n # 1.0.13: /opt/csw/etc/dovecot.conf base_dir: /opt/csw/var/run/dovecot/ log_path: /opt/csw/var/log/dovecot.log ssl_cert_file: /opt/csw/ssl/certs/dovecot-cert.pem ssl_key_file: /opt/csw/ssl/private/dovecot-key-np.pem verbose_ssl: yes login_dir: /opt/csw/var/run/dovecot//login login_executable: /opt/csw/libexec/dovecot/imap-login login_user: vmail first_valid_uid: 900 last_valid_uid: 1900 first_valid_gid: 900 last_valid_gid: 1900 mail_location: maildir:%h/Maildir mail_debug: yes auth default: username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /opt/csw/etc/vmail/%d/passwd userdb: driver: passwd userdb: driver: passwd-file args: /opt/csw/etc/vmail/%d/passwd socket: type: listen client: path: /opt/csw/var/run/dovecot/auth-client mode: 432 master: path: /opt/csw/var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: sieve: %h/.dovecot.sieve quota: maildir

2 2

[Dovecot] Time moved backwards
by Eugene 13 May '08

13 May '08

Hello, I would like to suggest a change in handling of 'Time moved backwards' problem. Right now dovecot just dies. So, the scenario: 1) Colocation server is shut down for some reason. The internal time drifts. 2) Server is started again. 3) Dovecot starts successfully. 4) In about a minute, NTP daemon feels confident about adjusting the system time. 5) Dovecot sees the changed time and dies. 6) Admin has to notice that, login and restart Dovecot manually. I suggest that Dovecot simply terminate the current connections (causing the client to reconnect) or -- if the time change is really that much of a problem -- to restart itself automatically. Maybe a config option could be introduced. Best wishes Eugene

10 20

[Dovecot] Unknown internal error
by Martin Preen 13 May '08

13 May '08

Hello, I just found this message in our dovecot logfiles: "Disconnected: BUG: Unknown internal error" Should I worry about this ? There are no complaints yet (although it is not limited to one user). It seems to occur with different clients (Apple/MacOS mail, Windows/Thunderbird, Pine). We're running dovecot 1.0.10 on Solaris 10 with mboxes (NFS) and local index storage. There are no such messages before the upgrade (from version 1.0.5). Regards. Martin --------------------------------------------------------------- Martin Preen, Universität Freiburg, Institut für Informatik Georges-Koehler-Allee 52, Raum 00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 preen(a)informatik.uni-freiburg.de fax: ++49 761 203-8242 www.informatik.uni-freiburg.de

2 3

[Dovecot] Mailbox problem
by Sadiq Walji 13 May '08

13 May '08

Greetings, I am using dovecot as our POP3 and IMAP server and Squirrelmail for the Webmail. Some of our users get the error message below when trying to access the mailbox using Webmail: "ERROR: Could not complete request. Query: SELECT "INBOX" Reason Given: Internal error occurred. Error report written to server log. [2008-05-12 09:08:39] To resolve this issue, I need to open the /var/spool/mail/<username> (mailbox of the user) and delete an empty line that is inserted at the top of the mailbox file. I am running dovecot-0.99.11-8.EL4 on CentOS release 4.6 (Final). Kindly provide suggestions on how to resolve this issue. Thank you, Sadiq

2 2

[Dovecot] how add size (, S=size) and virtual size (, W=vsize) fields to a maildir filename ?
by Marco Giunta 13 May '08

13 May '08

Hi to all, I'm a sys admin in a college, and we're using Dovecot as IMAP/POP3 server and delivery; we're also patch dovecot to add managesieve capability. I've a question: I've read on dovecot's wiki, that is possible improve the performance on maildir files by adding ,S=<size>,W=<vsize> fields on filename. How is possible to do that ? I've search on all the wiki and on the mailing list, but I didn't find nothing about modify the maildir file name. Someone can help me ? Best regards, Marco

2 2

[Dovecot] Access to the root of a shared mailbox
by RIOTTEAU Gwénaël 13 May '08

13 May '08

I have an issue with shares mailboxes Example : I have 2 users A and B. A must have an access to all mail of B So i create a public namespace namespace public { separator = / prefix = Public/ location = maildir:/home/users/B/Maildir } It's OK for the subfolders, but not for the root (B's inbox, the most important !) it's seems to be like http://www.dovecot.org/list/dovecot/2007-October/025965.html it's the only feature that prevents me to migrate from Courier-IMAP !

2 2

[Dovecot] Dovecot - MySQL Virtual User Virtual Domains
by Evaggelos Balaskas 12 May '08

12 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 i wrote a mini quick and dirty how to install dovecot from mercurial with mysql support to use virtual users and virtual domains. The tutorial doesnt cover much, but still someone could find some help at this. http://ebalaskas.gr/wk/dovecot/dovecotsqlauth any comments (good or bad) can addressed to my email address Evaggelos Balaskas - http://ebalaskas.gr/wk Unix System Engineer Informatics Engineer Technological Education -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIKKTqWIK+Pe9twhoRAgPiAJ0drcy9TYkCYyNY+5cHh+H/If1RJQCgt4bX JZs12hgvVyBrkQq3PTtFAy8= =Tafd -----END PGP SIGNATURE-----

1 0

[Dovecot] imapsync
by Lars Stavholm 12 May '08

12 May '08

Hi All, I'm trying out the imapsync migration tool, migrating user mails from cyrus IMAP to Dovecot IMAP. In order to avoid knowing about each of the users password, I use the cyrus admin user in the cyrus end. Is there such a thing as the dovecot admin user, or is that simply the root user? Any input appreciated /Lars

3 3

[Dovecot] imap memory footprint rather large
by martin f krafft 12 May '08

12 May '08

Dear list, I am experimenting with a new mail handling setup and it involves a single IMAP folder with just under 70'000 messages. When OfflineIMAP connects to the server, the imap process starts to eat up a lot of memory: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 15607 madduck 35 19 283m 244m 239m D 16.9 49.3 0:09.96 imap On the contrary, when "online" client, such as Thunderbird connect, memory usage is around 10m, which is entirely acceptable. The way offlineimap reads may is by FETCHing metadata, then APPENDing new local mail, SEARCHing for the UIDs of each uploaded mail, and finally FETCHing new remote mail. Memory use seems to be O(n) in the size of the folder. On the folder with 70k messages, dovecot seems to allocate 280m of memory, which it then fills to about 70% during the metadata FETCH, and then keeps growing while APPEND/SEARCHing the new local messages. The 70k mailbox is just short of 600Mb in size on disk. Dovecot uses 280Mb to serve it. Is it possible that dovecot is reading too much into memory, or over-optimising? Can I somehow tweak this to lower the memory footprint? Cheers, -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck "the unexamined life is not worth living" -- platon spamtraps: madduck.bogus(a)madduck.net

2 9

[Dovecot] Another numptie question - making maildirs for shared mailboxes.
by Stroller 12 May '08

12 May '08

Hi there, Sorry to have so much trouble with my Dovecot setup & to ask so many questions, but I'm having some problems with shared folders. I've read the thread at <http://dovecot.org/pipermail/dovecot/2005-January/006079.html> and added the following lines to /etc/dovecot.conf: namespace private { separator = / prefix = inbox = yes } namespace public { separator = / prefix = General/ location = maildir:/tmp/dovecot-test/ inbox = no hidden = no } So I create a directory /tmp/dovecot-test/ and an empty file /tmp/dovecot-test/dovecot-shared with liberal (777 & 666 respectively) permissions and then try to subscribe to the "General" folder in Outlook - I get a "failed to subscribe to the folder. The server responded `the mailbox doesn't exist: General`" error message, but cur, new & tmp are created in /tmp/dovecot-test. These subfolders are owned by the user that attempted to subscribe & have 700 permissions; chmod'ing them 777 makes no difference. Since "default_mail_env = maildir:%h/.maildir" in dovecot.conf I make a directory /tmp/dovecot-test/.maildir also containing cur, new, tmp & dovecot-shared. When I select "IMAP folders" in Outlook I am still unable to subscribe to "General" but am now able to subscribe to "General/maildir". The subscribed folder is shown in Outlook underneath the users' Inbox as a sub-folder of general, screenshot at <http://linux.stroller.uk.eu.org/DovecotSharedFolders.png> - see how I can't subscribe to "General" alone, but it is "brought in" by subscribing to "General/maildir"? If I try to copy a test message into General then, after a delay of a minute or so, I get "Can't move the items - this IMAP command could not be sent to the server before the connect was terminated"; if I try to copy the test message into General/maildir then I immediately get "Can't copy the items. The server responded: `Internal error occurred. Refer to server log for more information [2005-12-20 12:05:40]". I've tried tinkering with other directory structures under /tmp/dovecot-test/ with no success - can anyone suggest what I'm doing wrong, please? It's quite important to me that the "General" folder is a fairly high-level one - only one additional folder icon should show up for the users' shared mail. At one point I managed to create a folder General/General, but that's undesirable - the users wouldn't understand the concept of having a folder showing in Outlook that they can't write to, or which is only used as a container for another folder. (In any case, I believe I was still unable to write to it). I was about to say, "I know I could resolve this with the use of a symlink-type shared folder, but that's undesirable because I'd have to manually add the symlink for each user that's added to the system", but writing this it occurs to me that I could resolve that by adding the symlink to the the etc/skel/. Nevertheless, I see the namespaces approach as more elegant, as it allows for different user groups having different shared folders. I'd appreciate any advice - I suspect I'm just getting the directory hierarchies wrong, or the syntax of dovecot.conf wrong AGAIN! If anyone with a working shared folders setup could provide a copy of the appropriate section of dovecot.conf & a listing of the appropriate directories then I'd be EXTREMELY grateful. Stroller.

7 12

[Dovecot] how add size and vsize filed to a maildir filename ?
by Marco Giunta 12 May '08

12 May '08

Hi to all, I'm a sys admin in a college, and we're using Dovecot as IMAP/POP3 server and delivery; we're also patch dovecot to add managesieve capability. I've a question: I've read on dovecot's wiki, that is possible improve the performance on maildir file by adding ,S=<size>,W=<vsize> fields on filename. How is possible to do that ? I've search on all the wiki and on the mailing list, but I didn't find nothing about modify the maildir file name. Someone can help me ? Best regards, Marco

1 0

[Dovecot] IMAP, Shared folders, symlinks and permissions
by Nigel Allen 12 May '08

12 May '08

Greetings Using FC7, dovecot-1.0.3-6.fc6 and maildir I have a recurring problem with permissions. We have a (real) account on the system called "custs". Within the email account for custs there exists some 300 folders, one for each customer. This worked okay originally with mbox. Everyone had access to their own email folders and they all had access to the "custs" account. They only problem is that to find one folder (customers)'s emails, you had to scroll through 300+ folders. For the people who need access to all of the custs' folders, there was no problem (apart from a real estate one of scrolling which sometimes caused people to drag and drop into the wrong folders). The problem is that around 16 staff need only access to a subset of customers (i.e. the ones they manage - around 20 each) while the rest of the staff need access to the lot. What we did was to convert everything to Maildir so that we could use symlinks. So far so good. We created symlinks from /home/custs/Maildir/customer1 to /home/manager1/Maildir/customer1 and from /home/custs/Maildir/customer2 to /home/manager2/Maildir/customer2. Again, so far, so good. Manager 1 gets access to Customer 1 and Manager 2 gets access to Customer 2. The problem comes when someone who ONLY has access to the "custs" account drops an email into Customer 1. The file dovecot-uidlist gets created and suddenly Manager 1 cannot see the folder. We changed (in desperation) the group owner of custs/Maildir to "common" (which everyone is a member of) and did a chmod g+s from the custs/Maildir down. e even set the permissions of the custs/Maildir/* to 777 to watch what was happening. It appears that the permissions on the file dovecot-uidlist is set to 600 every time someone drops an email into the folder. Then when someone else tries to access the folder they get a "permission denied" error on dovecot-uidlist. Can anyone explain to me how to: Change the way dovecot creates the dovecot-uid files so that the permissions are set to 660 or 666 or Set this up better so that we can share all these folders. Any suggestions, questions, comments will be (very) gratefully accepted. Rgds Nigel. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 1

[Dovecot] BUG: Bad grep when building dovecot?
by Andrew Lentvorski 12 May '08

12 May '08

Is dovecot *really* that picky about grep, or did it just happen to pick up an autoconf that's being overly pedantic? I saw this message a couple of times when googling, but no particularly good solution presents itself. I'll probably give it a new GNU grep just to get it to shut up, but I'm a bit surprised. I tried to compile dovecot in an OpenSolaris 2008.5 system in a zone (which is quite a bit more minimal than base OpenSolaris). bash-3.2# uname -a SunOS postfix-s0 5.11 snv_86 i86pc i386 i86pc bash-3.2# ./configure --help `configure' configures dovecot 1.0.12 to adapt to many kinds of systems. bash-3.2# which grep /usr/bin/grep bash-3.2# grep -v Usage: grep -hblcnsviw pattern file . . . bash-3.2# which egrep /usr/bin/egrep Error in configure: checking for cc option to accept ISO C89... (cached) none needed checking dependency style of cc... (cached) none checking how to run the C preprocessor... cc -E checking for grep that handles long lines and -e... configure: error: no acceptable grep could be found in /opt/SunStudioExpress/bin:/usr/sbin:/usr/bin:/usr/xpg4/bin Thanks, -a

2 1

[Dovecot] dovecot mysql
by Evaggelos Balaskas 11 May '08

11 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i am trying to setup dovecot with mysql support (mysql from lampp) but i am getting this : hg clone http://hg.dovecot.org/dovecot-1.1/ dovecot-1.1.hg cd dovecot-1.1.hg ./autogen.sh export -p LDFLAGS="-L/opt/lampp/lib/mysql/" ./configure --with-mysql ... checking mysql.h usability... no checking mysql.h presence... no checking for mysql.h... no configure: error: Can't build with MySQL support: mysql.h not found so i understand that i should use the mysql from mysql.com with the include dir of header files. My question is this : Can somehow use the mysql from lampp ? or dovecot can be installed without the includes header of mysql ? Evaggelos Balaskas - http://ebalaskas.gr Unix System Engineer Informatics Engineer Technological Education -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIJtFnWIK+Pe9twhoRArQeAJ9H3jAuJOg11HqpPNSY+EQErwt2RwCgkBTn 3bwLXjxa4nN8ljVKoaEe77Q= =zmeJ -----END PGP SIGNATURE-----

1 1

[Dovecot] Invalid transaction log size (32684 vs 32784)
by Adam McDougall 09 May '08

09 May '08

May 8 10:17:44 boomhauer dovecot: IMAP(username2): Invalid transaction log size (32684 vs 32784): /home/username2/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.log May 8 10:17:44 boomhauer dovecot: IMAP(username2): Invalid transaction log size (32684 vs 32784): /home/username2/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.log May 8 10:17:44 boomhauer dovecot: IMAP(username2): Invalid transaction log size (32684 vs 32784): /home/username2/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.log

1 0

[Dovecot] dovecot.index.cache: Corrupted virtual size for uid=956: 2182 != 4917
by Adam McDougall 09 May '08

09 May '08

This is from 1.1rc5. I have no idea where the 2182 even came from, all copies of the dovecot-uidlist and all copies of the email in snapshots going back at least 2 weeks show the info below: May 8 22:45:22 hill dovecot: IMAP(username): Corrupted index cache file /home/username/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.cache: Corrupted virtual size for uid=956: 2182 != 4917 dovecot-uidlist: 956 W4917 :1208807110.M854034P88191.hill:2,RS -rw------- 2 username egrstaff 4831 Mar 26 13:53 1208807110.M854034P88191.hill:2,RS

1 0

[Dovecot] LDA/Posfix error: bounce, user unknown
by Colin Brace 09 May '08

09 May '08

Hello, I am trying to get LDA working in conjuction with Postfix, but whenever I activate Dovecot LDA in main.cf and send myself a test messsage, I get an error message in maillog: [...] May 8 20:47:17 venus postfix/pipe[36077]: 4022B5C38: to=<cb(a)lim.nl>, orig_to=<colin(a)lim.nl>, relay=dovecot, delay=0.02, delays=0.01/0/0/0.01, dsn=5.1.1, status=bounced (user unknown) [...] Postfix's virtual LDA has no such problem: [...] May 8 20:49:39 venus postfix/virtual[36181]: F3DF05C37: to=<cb(a)lim.nl>, relay=virtual, delay=0.05, delays=0.03/0/0/0.01, dsn=2.0.0, status=sent (delivered to maildir) May 8 20:49:39 venus postfix/qmgr[36091]: F3DF05C37: removed [...] Here is the LDA section in dovecot.conf: protocol lda { postmaster_address = postmaster(a)lim.nl mail_plugin_dir = /usr/local/lib/dovecot/lda mail_plugins = cmusieve log_path = /var/log/dovecot-deliver info_log_path = /var/log/dovecot-deliver auth_socket_path = /var/run/dovecot/auth-master } My maildirs are here: mail_location = maildir:/home/colin/vmail/%u and Dovecot IMAP has no problem retrieving messages from that location. What might be going wrong with delivery though? Thanks. -- Colin Brace Amsterdam http://lim.nl

2 1

[Dovecot] ipv6 woes
by Jason Fesler 09 May '08

09 May '08

I'm trying to bring up dovecot on a dual stack machine. I tried search for the answers; the answers I found and tried failed :-(. If I try this: protocol imap { listen = 216.218.228.114:143, [2001:470:1:18::114]:143 ssl_listen = 216.218.228.114:993, [2001:470:1:18::114]:993 } (and similiar for pop3) I get: Fatal: listen: Can't resolve address 216.218.228.114:143, [2001:470:1:18::114]: hostname nor servname provided, or not known If I instead use: protocol imap { listen = *, [::] ssl_listen = *, [::] } I get this error: Fatal: listen: Invalid port in address This is while using dovecot 1.0.13 Build options: ioloop=kqueue notify=kqueue ipv6 openssl Any recommendations? -- 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 4

[Dovecot] MBOX to Maildir preserving the UIDL (outlook-tested, no redownloading)
by Horn Wijaya 09 May '08

09 May '08

TESTED AND RUNNING, MIGRATING from MBOX to MAILDIR, PRESERVE UID and OUTLOOK sees the email as downloaded. I hope this helps a lot of people out there. Feel free to post this somewhere else too. By: Horn Wijaya (hwijaya(a)nodens.biz) 8th May 2008 I have been searching for weeks for a foolproof method to migrate all my users mbox to maildir/dovecot without having the pain of downloading all emails again, especially for heavy users. It would cause frustration to thousands of my users. So.... eventually I found out why Outlook will keep downloading the emails despite all the configuration done in the dovecot.conf. Apparently the UID is generated realtime. When it first generated, it took the time the process runs. Before I migrate, here's the email sample which I have downloaded to my outlook (and keep email on server), and then I use telnet to pop to get the uidl list. +OK POP3 localhost.localdomain v2003.83rh server ready user ***** +OK User name accepted, password please pass ***** +OK Mailbox open, 444 messages uidl +OK Unique-ID listing follows 1 47b1303d00004c2d 2 47b1303d00004c2e 3 47b1303d00004c2f ... 47b1303d = 1202794557 = 12 Feb 2008 13:35:57 the date and time the mbox was created 00004c2d = 19501 the IMAP counter so far.... sequently added as you could see with email #2 and email #3 Then I switch my POP server to dovecot, and migrate my MBOX to Maildir, and I do a telnet to get the UIDL +OK Dovecot ready. user ***** +OK pass ***** +OK Logged in. uidl +OK 1 4822815000000001 2 4822815000000002 3 4822815000000003 ... 48228150 = 1210220880 = NOW 00000001 = counter starts at 1 No wonder outlook sees the emails are NOT-DOWNLOADED-YET status. Then I ponder for another few days and the key is in the dovecot-uidlist...... How to fill it with the correct info.... and there's a way. Which I hope useful for converter developer, and could be implemented in the next version of the converter. Here's the step I do to reach my objective which is to get UID 47b1303d00004c2d in the first email: 1. mb2md-3.20.pl -s /var/mail/hwijaya -d home/hwijaya/Maildir/ that's converting 444 emails from mbox to 444 files in the Maildir/cur folder 2. cd /home/hwijaya/Maildir/cur 3. grep IMAPbase * and I get 1210219860.000000.mbox:2,S:X-IMAPbase: 1202794557 19944 The last 2 strings are the KEY to the ORIGINAL UID 4. So in order to prepare the environment to fool it, some calculations are needed: How do we get 19501 as the first counter? as expected in the first POP TEST above: 19944 - 444 emails + 1 = 19501 5. cd /home/hwijaya/Maildir 6. echo '3 V1202794557 N19501' > dovecot-uidlist 7. DONE....... pop it via outlook and nothing will be downloaded, after pop or imap is processed, the dovecot-uidlist is auto-filled, index auto generated. Proof: +OK Dovecot ready. user ***** +OK pass ***** +OK Logged in. uidl +OK 1 47b1303d00004c2d 2 47b1303d00004c2e 3 47b1303d00004c2f ... I assume the same method could be used for individual folders in the imap (under .mailboxlist or .subscriptions) Please do let us know if there's any cases/environment that it won't work. Thanks very much, and a big migration job is in front of me now... ------------------------------------------ Warmest Regards From: Horn Wijaya Consultant hwijaya(a)nodens.biz http://www.nodens.biz/ Nodens Solutions Pte Ltd "where there is freedom in your choice"

3 6

[Dovecot] [Q] IMAP update message header?
by Roderick A. Anderson 08 May '08

08 May '08

More about IMAP, less about Dovecot. This is more an IMAP question than specifically about Dovecot. Sorry to ask here but I've been researching, reading and lurking with no answer so far. What I'm doing is running reports as a user from a remote system to provide a list of messages (Sender/From, Subject, Date, size) in a specific folder(?). In one case it isn't even a Dovecot based server so I only have access as a client. (Though I use Dovecot on several other systems and will need this capability for them.) When a message in the folder has been reported I'd like to add a X-Header-??? indicating that the message has been reported so the next time through it isn't reported again. (After the message is X days old it is deleted.) These reports are run using Perl and I've tried most every CPAN module available but haven't figured out how to change/add a header then save the message back. So far I haven't been able to determine if this is even possible by reading the RFCs. Is there a method as a client from a remote system to make changes to a message then save it back? What is the IMAP verb, command, etc. to do this? Or if there are Perl programmers on the list a brief description (or code) for doing this? TIA (and sorry for the off topic posting), Rod --

6 13

Re: [Dovecot] How do I increase the fd limit on OS X?
by Jerry Yeager 08 May '08

08 May '08

On May 8, 2008, at 1:04 AM, dovecot-request(a)dovecot.org wrote: > > > Message: 6 > Date: Wed, 7 May 2008 13:17:44 -0700 > From: Rob Frohne <rob.frohne(a)wallawalla.edu> > Subject: [Dovecot] How do I increase the fd limit on OS X? > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <1210191465.19769.5.camel(a)frohro-d600.wwc.edu> > Content-Type: text/plain > > Hi All, > > I just upgraded to the new 1.1rc5 from 1.0 that I had been using and > it > advised me to increase the file descriptor limit. I'm not sure how to > do this. There is a command built into tcsh that allows me to do this > called limit, but sudo limit 4224 doesn't work, and usually dovecot is > started from the rc.local file if I recall right, and I'm not sure how > to set this up from there. Any advice. > > Thanks, > > Rob > -- > Rob Frohne <rob.frohne(a)wallawalla.edu> > Walla Walla University > > > Try this your_prompt_$ sudo sysctl -w kern.maxfiles=65536 your_prompt_$ sudo sysctl -w kern.maxfilesperproc=32768 You will be asked for your admin password. This will allow you to test things and see if it works better. The changes will revert to the system pre-defines when you re-boot or restart. IIRC, there is a master setting (unchangeable without recompiling OS X) that will not allow you to go over 65536, but I may be mistaken about that. For a permanent change, add the following lines to the /etc/sysctl.conf file: or the /etc/sysctl-macosxserver.conf file for Mac OS X Server You may have to create the file, especially if you are the only user. (Make sure that only root has access to this file!!!!!!) kern.maxfiles=65536 # System-wide limit kern.maxfilesperproc=32768 # Per-process limit This Is ONLY For OS X 10.3 or later. For earlier versions you need to use /etc/rc which was so long ago that I do not recall all of the commands (sorry). HTH, Jerry

1 0

[Dovecot] How do I increase the fd limit on OS X?
by Rob Frohne 08 May '08

08 May '08

Hi All, I just upgraded to the new 1.1rc5 from 1.0 that I had been using and it advised me to increase the file descriptor limit. I'm not sure how to do this. There is a command built into tcsh that allows me to do this called limit, but sudo limit 4224 doesn't work, and usually dovecot is started from the rc.local file if I recall right, and I'm not sure how to set this up from there. Any advice. Thanks, Rob -- Rob Frohne <rob.frohne(a)wallawalla.edu> Walla Walla University

2 1

Re: [Dovecot] thunderbird sane config (OT)
by Moser 08 May '08

08 May '08

Charles Marcus schrieb: > On 5/7/2008, rosenfield.albert(a)gmail.com (rosenfield.albert(a)gmail.com) > wrote: >> (Background: I'm currently experiencing that Thunderbird does not work >> against Postfix/Dovecot because the wizard interface for setting up an >> account does not accept TLS-only servers. Users just sit there with a >> broken Thunderbird, not knowing what to do :-/.) you can do it. > It would be nice if you had the ability to access the Advanced Options > when setting up a new account in TBird, but currently you don't... Not true! simple way: Just change the default config TB create your account from with the settings you need. You can find the file under your program dir i.e. C:\Programme\Mozilla Thunderbird\defaults\pref Compare the defaults to your working set of setting and change them accordingly. You can activate TLS or CRAM-MD5 and so an. You can also predefine LDAP servers etc. more elaborated way: Mozilla Mission Contol: -> http://developer.mozilla.org/en/docs/MCD,_Mission_Control_Desktop_AKA_AutoC… Hope it helps! Hans

2 1

[Dovecot] thunderbird sane config (OT)
by rosenfield.albert＠gmail.com 08 May '08

08 May '08

Does anyone have any experience putting together a sane config for Thunderbird in an automated fashion? Automated meaning "simple to distribute to users". -- (Background: I'm currently experiencing that Thunderbird does not work against Postfix/Dovecot because the wizard interface for setting up an account does not accept TLS-only servers. Users just sit there with a broken Thunderbird, not knowing what to do :-/.) (PS: Also, giving everybody a GMail-like threaded interface per default would be cool.) (PPS: If anything good comes up, I plan to put this in fx the Dovecot wiki.)

5 7

[Dovecot] pop/imap session
by Tomasz 08 May '08

08 May '08

Hello, Can dovecot log pop/imap session, and notify(by sending mail) admin in case of errors? Something like notify_classes in postfix. Regards Tomasz

4 5

[Dovecot] [bug] bit of a clearer error message desired - Can't load CA file... : Success
by Daniel Black 07 May '08

07 May '08

Not the clearest of error messages. A successful cannot load. May 7 21:05:29 10.10.10.213 dovecot: child 21500 (login) returned error 89 May 7 21:05:29 10.10.10.213 dovecot: child 21501 (login) returned error 89 May 7 21:05:29 10.10.10.213 dovecot: child 21502 (login) returned error 89 May 7 21:05:29 10.10.10.213 dovecot: child 21503 (login) returned error 89 May 7 21:05:29 10.10.10.213 dovecot: child 21505 (login) returned error 89 May 7 21:05:29 10.10.10.213 dovecot: pop3-login: Can't load CA file /etc/dovecot/all.der: Success May 7 21:05:29 10.10.10.213 dovecot: imap-login: Can't load CA file /etc/dovecot/all.der: Success /etc/dovecot/all.der was generated by concatinating the following (all in der format) http://www.cacert.org/certs/root.der http://www.cacert.org/certs/class3.der http://crl.cacert.org/revoke.crl http://crl.cacert.org/class3-revoke.crl # dovecot --version 1.0.10 reiserfs filesystem # uname -a Linux mail.cacert.org 2.6.22-vs2.2.0.7-gentoo #1 SMP Mon May 5 20:21:30 EST 2008 x86_64 GNU/Linux # dovecot -n # 1.0.10: /etc/dovecot/dovecot.conf protocols: imaps pop3s imap pop3 ssl_ca_file: /etc/dovecot/all.der ssl_cert_file: /etc/ssl/certs/ssl-cert-community-cacert.pem ssl_key_file: /etc/ssl/private/ssl-cert-community-cacert.key ssl_verify_client_cert: yes verbose_ssl: yes 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_greeting: You want mail? Well hurry up. first_valid_uid: 5000 mail_location: maildir:~/Maildir mail_read_mmaped: 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 pop3_uidl_format: %08Xu%08Xv auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes ssl_require_client_cert: yes ssl_username_from_cert: yes passdb: driver: pam args: session=yes mail userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix -- Daniel Black -- Proudly a Gentoo Linux User. Gnu-PG/PGP signed and encrypted email preferred http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x76677097 GPG Signature D934 5397 A84A 6366 9687 9EB2 861A 4ABA 7667 7097

2 1

[Dovecot] Clarification wanted on mail_access_groups vs. mail_privileged_group
by Mark Sapiro 07 May '08

07 May '08

I have just upgraded to dovecot 1.0.13. All the documentation I can find in the example .conf file and the NEWS and ChangeLog files seems to say that the mail_privileged_group = mail setting is all I should need to make dovecot use group mail to create dotlock files. My understanding from what I read is that mail_privileged_group is used to set the group used while creating dotlock files in (in my case) /var/spool/mail, and mail_access_groups is used to set the group used to actually access the mailbox. In my case, /var/spool/mail is group 'mail and group writable/searchable drwxrwxr-x 2 root mail 4096 May 7 08:35 /var/spool/mail and the individual mailboxes are owned by the respective users. So it seems that I would need "mail_privileged_group = mail" do be able to create dotlock files in /var/spool/mail, and that I would not need any mail_access_groups as the users can access their own mailboxes. But this doesn't work. With "mail_privileged_group = mail" and mail_access_groups unset, I get May 6 12:48:54 sbh16 dovecot: POP3(xxx): file_lock_dotlock() failed with mbox file /var/spool/mail/xxx: Permission denied Yet with "mail_access_groups = mail" and mail_privileged_group unset, it works with no problem. Is my understanding wrong? Is the documentation wrong? Is the implementation wrong? Or is there just something wierd in my case (possibly pop3_lock_session = yes)? # dovecot -n # 1.0.13: /usr/local/etc/dovecot.conf protocols: pop3 pop3s ssl_cert_file: /etc/postfix/grizz-cert.pem ssl_key_file: /etc/postfix/grizz-key.pem login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_access_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock mail_executable: /usr/local/libexec/dovecot/pop3 mail_plugin_dir: /usr/local/lib/dovecot/pop3 pop3_lock_session: yes pop3_uidl_format: %08Xu%08Xv auth default: mechanisms: plain apop login worker_max_count: 5 passdb: driver: passwd-file args: /usr/local/etc/dovecot.passwd passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 2

[Dovecot] Error in dovecot-auth logging
by Antonio Casado Rodríguez 07 May '08

07 May '08

Hi, i have this in /var/log/messages May 7 09:29:59 blade25 dovecot-auth: pam_ldap: ldap_result Timed out May 7 09:29:59 blade25 dovecot-auth: pam_ldap: ldap_result Can't contact LDAP server but i defined log_path and info_log_path in dovecot.conf "dovecot -n not show different values for "protocol lda"? Regards # dovecot -n # 1.0.10: /etc/dovecot.conf log_path: /Correo/log/dovecot/dovecot.log info_log_path: /Correo/log/dovecot/dovecot.info protocols: imaps pop3 managesieve ssl_cert_file: /etc/pki/dovecot/certs/mycert.crt ssl_key_file: /etc/pki/dovecot/private/mycert.key 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_executable(managesieve): /usr/libexec/dovecot/managesieve-login first_valid_uid: 200 mail_location: maildir:%h/.. mail_executable(default): /usr/local/sbin/post-login-imap-dovecot mail_executable(imap): /usr/local/sbin/post-login-imap-dovecot mail_executable(pop3): /usr/local/sbin/post-login-pop3-dovecot mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 mail_plugin_dir(managesieve): /usr/lib64/dovecot/managesieve namespace: type: private separator: / location: maildir:%h/.. inbox: yes auth default: passdb: driver: pam userdb: driver: passwd plugin: quota: maildir:storage=1048576

2 1

[Dovecot] dovecot pop3 proxy with AUTH PLAIN
by Luis Barrueco 07 May '08

07 May '08

Hi, I tried as hard as I could, but I couldn't get this working. So here I come begging for help :) I need to configure dovecot to proxy some users' incoming pop3 connections to another server running the Zimbra Collaboration Suite, trying to log into zimbra via a master password. The problem I found is that zimbra only allows me to log in as a master user with the "AUTH PLAIN" mechanism, but it seems that dovecot uses the "USER.... PASS" authentication when proxying. Am I missing something? Has anyone ever tried to do the proxy+master password to zimbra? I'll post my configurations down here. I really appreciate your help- ----------------------------- dovecot version: 1.0.13 ----------------------------- "dovecot -n" output: # 1.0.13: /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/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/local/libexec/dovecot/pop3-login mail_privileged_group: mail mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/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/local/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: passdb: driver: pam passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd ----------------------------- /usr/local/etc/dovecot-sql.conf: driver = mysql connect = host=172.16.0.252 dbname=dovecot user=usuario_dovecot password=miclave password_query = SELECT password, 'secret_zimbra' as pass, host, destuser, 'Y' AS proxy FROM proxy WHERE user = '%u' ----------------------------- sudo tcpdump -w output_tcpdump -i eth0 dst host 172.16.0.20 and dst port 110: .........USER mnunez master ......... .........PASS secret_zimbra ----------------------------- I hope this information was helpful! Cheers.

2 1

[Dovecot] Wish: change default log_timestamp
by Steffen Kaiser 07 May '08

07 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'd suggest to change the default value of log_timestamp to something with complete date and time. Currently the string is missing the year. Maybe, %F (ISO date) would fit best. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIHz1uVJMDrex4hCIRAqIiAJsEBSsnhIZg2nGnuzPmJbiSf7VjrwCdHPTX T31joYCErSgOt5OAXa/11OM= =6cC1 -----END PGP SIGNATURE-----

2 1

[Dovecot] FETCH for mailbox INBOX UID 5003 got too little data: 5369 vs 38919
by Adam McDougall 07 May '08

07 May '08

This happened a while back, I was running 1.1rc3 up until today so I have no idea if it would have an effect. Sorry if its something that has been fixed. The error below was repeated many many times, I deleted the index so the user would stop getting disconnected (although I didn't hear any complaints). I have not seen this happen repeatedly in this manner to any other user yet. Apr 15 11:26:48 boomhauer dovecot: IMAP(username): FETCH for mailbox INBOX UID 5003 got too little data: 5369 vs 38919 Apr 15 11:26:48 boomhauer dovecot: IMAP(username): Corrupted index cache file /home/username/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 5003 Apr 15 11:26:48 boomhauer dovecot: IMAP(username): Disconnected: Disconnected bytes=139/145074 Apr 15 11:27:08 boomhauer dovecot: IMAP(username): FETCH for mailbox INBOX UID 5003 got too little data: 5369 vs 38919 Apr 15 11:27:08 boomhauer dovecot: IMAP(username): Corrupted index cache file /home/username/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 5003 Apr 15 11:27:08 boomhauer dovecot: IMAP(username): Disconnected: Disconnected bytes=139/145074 Apr 15 11:28:50 boomhauer dovecot: IMAP(username): FETCH for mailbox INBOX UID 5003 got too little data: 5369 vs 38919 Apr 15 11:28:50 boomhauer dovecot: IMAP(username): Corrupted index cache file /home/username/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 5003 Apr 15 11:28:50 boomhauer dovecot: IMAP(username): Disconnected: Disconnected bytes=139/145074 Apr 15 11:38:02 boomhauer dovecot: IMAP(username): FETCH for mailbox INBOX UID 5003 got too little data: 5369 vs 38919 Apr 15 11:38:02 boomhauer dovecot: IMAP(username): Corrupted index cache file /home/username/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 5003 Apr 15 11:38:02 boomhauer dovecot: IMAP(username): Disconnected: Disconnected bytes=139/145074 Apr 15 11:38:52 boomhauer dovecot: IMAP(username): FETCH for mailbox INBOX UID 5003 got too little data: 5369 vs 38919 Apr 15 11:38:52 boomhauer dovecot: IMAP(username): Corrupted index cache file /home/username/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 5003 Apr 15 11:38:52 boomhauer dovecot: IMAP(username): Disconnected: Disconnected bytes=139/145074 >From dovecot-uidlist: 5003 W38919 S38270 :1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 1208208981.7303_0.hill:2,S # ls -l .snapshot/*/1208208981.7303_0.hill* -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.0/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.1/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.10/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.11/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.12/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.13/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.14/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.15/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.16/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.17/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.18/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.19/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.2/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.20/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.21/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.22/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.3/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.4/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.5/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.6/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.7/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.8/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.9/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/nightly.0/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/nightly.1/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/nightly.2/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/nightly.3/1208208981.7303_0.hill:2,S # mv dovecot.index.cache dovecot.index.cache.broken

2 1

[Dovecot] dovecot + exim + verify recipient / reject bad recipient at SMTP time
by Peter Hudec 07 May '08

07 May '08

hello, I'm quite new to dovecot. My instalation is working good Debian Etch - exim: 4.63-17 - dovecot: 1.0.rc15 I'm using virtual user setup, with LDA delivery method. There is no database backend at this time. Is there any way to configure exim to reject non-existing user /asking dovecot lda/ at SMTP time. The standard exim configuration in ACL section do not work: --- cut --- require message = e-mail address is not valid ($local_part@$domain / $recipient_verify_failure) domains = +virtual_domains verify = recipient --- cut --- Please, have any work working example ? This setup work good witch cyrus-imap and LMTP. best regards Peter Hudec

2 1

[Dovecot] Manual thread breaking from Thunderbird
by Christian Jaeger 07 May '08

07 May '08

Hello I'm looking for a way to manually break threads apart when independent threads are mixed up, mostly by users which aren't aware that they should not be replying to existing threads when starting a new one. Since Thunderbird afaik does the threading itself, it would require a solution that actually changes the In-Reply-To header (and maybe also that other (non-standard?) header which is being sent by the M$ clients). For me modifying the actual emails on disk would be fine, i.e. renaming the In-Reply-To header to Old-In-Reply-To and such. (I'd actually *prefer* a solution that modifies the server side store, as opposed to one which keeps that info on the client side only like mutt seems to be doing.) Is there a way to do this already? Seems like a task for a dovecot plugin--or for the xexec plugin and an external perl script or some such? For triggering the renaming, a hacky solution could be to misuse labels (e.g. marking a message starred and "Later" and "Important" at the same time would trigger the modification and remove the labels). When implementing such a thing: maybe also offer a way to modify subjects (for those cases where people are using short meaningless and recurring subjects--to both help breaking up the ensuing threading as well as giving them a useful replacement), maybe as an IMAP extension or such (to be used by Thunderbird plugins (?), or by web apps). (I can code in C and Perl, but don't generally have much time.) Christian.

6 21

[Dovecot] Problem finding inbox and pam_authenticate failed problem
by Chris Beech 07 May '08

07 May '08

Testing installation of Dovecot. Log is showing two errors. Any ideas how to fix this thing??? dovecot: May 07 05:19:06 Error: auth-worker(default): pam(Yoda,127.0.0.1): pam_authenticate() failed: User not known to the underlying authentication module dovecot: May 07 05:21:48 Error: IMAP(Yoda): open() failed with mbox file /var/mail/Yoda: Permission denied Here's the dovecot.conf file # 1.1.rc4: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:10100 ssl_disable: yes disable_plaintext_auth: no 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/local/libexec/dovecot/pop3-login verbose_proctitle: yes first_valid_uid: 1000 last_valid_uid: 5000 mail_privileged_group: mail mail_location: mbox:/var/empty:INBOX=/var/mail/%u:INDEX=MEMORY mail_debug: yes mbox_write_locks: fcntl mbox_very_dirty_syncs: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/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/local/lib/dovecot/pop3 auth default: debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: passwd passdb: driver: shadow passdb: driver: passwd-file args: /usr/local/etc/dovecot.passdb userdb: driver: passwd userdb: driver: passwd-file args: /usr/local/etc/dovecot.passdb socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: dovecot group: mail ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

1 0

[Dovecot] Question about Maildir automatic cleanup.
by José Ildefonso Camargo Tolosa 07 May '08

07 May '08

Hi! I want to automatically delete old messages from one user's Maildir, and I was thinking on running something like this: find /home/user/Maildir/cur/ /home/user/Maildir/new/ -daystart -mtime +15 -delete but I'm not sure if by deleting messages "manually" I will break the dovecot.index* files. What do you think? Thanks! Ildefonso. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

3 2

[Dovecot] 1.07 to 1.0.13 mail_extra_groups
by Mark Sapiro 07 May '08

07 May '08

I have just upgraded from 1.0.7 to 1.0.13. I read the comments in the example .conf file and it seemed what I needed to enable dotlock access to mailboxes in /var/spool/mail (writable by 'mail' group) was "mail_privileged_group = mail" so I removed the "mail_extra_groups = mail" that I had in 1.0.7 and added "mail_privileged_group = mail", but I got errors like the following: May 6 12:48:54 sbh16 dovecot: POP3(xxx): file_lock_dotlock() failed with mbox file /var/spool/mail/xxx: Permission denied May 6 12:48:54 sbh16 dovecot: POP3(xxx): Couldn't open INBOX: Internal error occurred. Refer to server log for more information. [2008-05-06 12:48:54] May 6 12:48:54 sbh16 dovecot: POP3(xxx): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 May 6 12:48:54 sbh16 dovecot: pop3-login: Login: user=<xxx>, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured I then put "mail_extra_groups = mail" back in the configuration. This seems to have the effect of setting both "mail_privileged_group = mail" and "mail_access_groups = mail" as well as issuing "Warning: mail_extra_groups setting was often used insecurely so it is now deprecated, use mail_access_groups or mail_privileged_group instead" when dovecot is started. So my question is what do I need. I thought it would be just "mail_privileged_group = mail", but that doesn't work. Do I need both "mail_privileged_group = mail" and "mail_access_groups = mail" or just "mail_access_groups = mail". Also, are the comments describing these in the example .conf file correct, or are they reversed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

[Dovecot] dovecot shows inbox of different user wher logged from the same host twice
by Anselmo Rosa herlen 06 May '08

06 May '08

I have squirrenmail 1.4.13 configured on FC8 with sendmail,procmail as delivery agent, dovecot(imap) ,Using MAILDIR, enabled secure_login plugin, and using password/shadow and system user . When I login through squirrelmail every thing works fine . But when I login again from the same host as a different user with new browser session, the mailbox of the new user displays correctly but the first user session displays the inbox of the second user . ie if I have two https sessions from a single machine and login as two different users the inbox of the later user is displayed in both the sessions. I checked the logs of dovecot and the following is noticed dovecot: May 06 11:12:25 Info: imap-login: Login: user=<ath>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured dovecot: May 06 11:12:25 Info: IMAP(ath): Disconnected: Logged out there are lots of messages for a single login . Also the USER shown above is the user of the second session and is displayed when i try to access the first htts session dovecot -n (reports the following) # 1.0.5: /etc/dovecot.conf log_path: /var/log/dovecot protocols: imap imaps ssl_disable: yes login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_location: maildir:~/Maildir auth default: passdb: driver: pam userdb: driver: passwd kindly help Best Jokes, Best Friends, Best Food and more. Go to http://in.promos.yahoo.com/groups/bestofyahoo/

2 1

[Dovecot] deliver custom maildir creation
by Steve Roemen 06 May '08

06 May '08

/ I'm testing a new setup of postfix using deliver to put the messages into the user's maildir, and am curious if there is a way to make deliver create custom maildirs when it delivers to a valid user without a maildir? Right now it only creates the inbox, I'd like it to create the .sent/ .Trash/ and .SPAM dirs. Is this possible? Thanks -------------------------------------- / /Steve Roemen// /

5 8

[Dovecot] Problem with quota.
by john.wall＠cky.se 06 May '08

06 May '08

Hi, Im having problem with quota with 1.0.rc17-1ubuntu2.3. Problem is that dovecot wont bounce when quota are exceeded. I have set my quota limit to 2MB and my test-box is 3MB. here is my config: dovecot.conf: #ssl_cert_file = /etc/pki/dovecot/certs/myserver.example.com.crt #ssl_key_file = /etc/pki/dovecot/private/myserver.example.com.key #ssl_ca_file = /etc/pki/dovecot/certs/ca-bundle.crt mail_location = maildir:/home/vmail/%d/%u first_valid_uid = 5000 last_valid_uid = 5000 maildir_copy_with_hardlinks = yes disable_plaintext_auth = no protocols = imap imaps pop3 pop3s 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)example.com mail_plugins = quota log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log } auth default { # Having "login" also as a mechanism make sure outlook can use the auth smtpd as well # http://wiki.dovecot.org/Authentication/Mechanisms mechanisms = plain login passdb sql { args = /etc/dovecot/sql.conf } userdb sql { args = /etc/dovecot/sql.conf } userdb static { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } userdb prefetch { } user = nobody socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = vmail group = vmail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } dict { } plugin { quota = maildir:storage=1024:messages=1000 acl = vfile:/etc/dovecot/acls trash = /etc/dovecot/trash.conf } sql.conf: driver = mysql connect = host=localhost dbname=mdbv3 user=xxxx password=xxxx user_query = SELECT concat('/home/vmail/', maildir) as home, concat('maildir:/home/vmail/', maildir) as mail, 5000 AS uid, 5000 AS gid, concat('maildir:storage=', quota) AS quota FROM mailbox WHERE username = '%u' AND active = '1' password_query = SELECT username as user, password, concat('/home/vmail/', maildir) as userdb_home, concat('maildir:/home/vmail/', maildir) as userdb_mail, 5000 as userdb_uid, 5000 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' Is this file even nessesary ? (postfix stuff) mysql_virtual_mailbox_limit_maps.cf (not showing login inf etc): query = SELECT quota FROM mailbox WHERE username='%s' AND active = '1'

2 1

[Dovecot] [Solved] Re: Quota not showing correctly after conversion (mb2md.pl)
by k bah 06 May '08

06 May '08

On Fri, 2008-04-25 at 09:56 +0800, k bah wrote: >> I have a problem, when a user has mails that exceed the limit in mb's >> (I set just size limit, no messages limit), neither >> "getquotaroot" (via telnet to port 143), neither webmail software >> (horde) show the quota usage correctly (I'm not talking about new >> mail, talking about those messages copied, when they exceed the size >> limit). Just after trying to delete messages it is shown (gives me an >> error message, quota exceeded, since Trash is not excluded from quota >> limits, for now, I'll exclude it later). This server has some issues: >> many old users have lots of mails, in thousands (1000-15000). Some >> have 50mb to 150mb of mails. The migration is part of the cleanup >> process. > That's quite a confusing paragraph. Do you just mean that "quota is > counted wrong for the old converted messages"? If the user received new mail on the new system, say, around 200kb, and then he/she logs in, messages from the old system are copied. If he had 100Mb of mails (old system), and quota is 20Mb, only the 200kb are shown. Dovecot was not restarted. The problem was what you pointed out, maildirsize had to be deleted, then everything seems to be ok - getquotaroot indicates 100Mb + 200kb. > How badly wrong is the quota? Show me some example values of what they > are and what they're supposed to be? How do you calculate what the quota > is supposed to be? User has +100Mb, quota 20Mb, quota indicates 0 or just the new mail count (messages received on the new system). As you said, just delete maildirsize. >> Is it possible that the migration order (creating dirs in that way) >> is causing the quota usage to be shown wrong? > If all this is before the imap process is started, I don't see any > problems. >> Is it possible that the amount of messages and the size can be the >> cause? > No. >> How can I manually tell dovecot to recalculate the quota, after >> copying messages (when a user logs in, and didn't receive new mails on >> the new mail system, but had messages big enough to exceed the quota >> limit) from the old system? > Deleting maildirsize file recalculates the quota. That was the problem! >> Should I run any commands to rebuild indexes or any operation to keep >> information integrity about the mails/mailboxes to dovecot, after >> copying the converted messages? > No. Ok = -- Powered by Outblaze

1 0

[Dovecot] imap fs quota (rpc) won't work?
by Adam McDougall 06 May '08

06 May '08

In the past I dabbled with the imap quota plugin with the fs backend because I wanted to report usage to my users (not limit them). At the time, the quota plugin would make dovecot crash when trying to write to a folder (I can bring up this report if needed). However, in a later beta of dovecot 1.1 I tried quota again but I cannot get it to report any results. I've been wanting to use fs:noenforcing but also tried just quota = fs to simplify. When I right click a folder stored in my homedir, thunderbird tells me 'the server does not support quotas' in the folder properties. What else can I do? Thanks! IModule loaded: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so IModule loaded: /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so Feb 5 21:53:16 gribble dovecot: IMAP(mcdouga9): fs quota add storage dir = /home/mcdouga9/Maildir Feb 5 21:53:16 gribble dovecot: IMAP(mcdouga9): fs quota block device = cypher:/vol/mail/home Feb 5 21:53:16 gribble dovecot: IMAP(mcdouga9): fs quota mount point = /home gribble# quota -v mcdouga9 | grep home /home 10766672 20480000 20480000 963778 4294967295 4294967295 # 1.1.beta14: /usr/local/etc/dovecot.conf ssl_cert_file: /usr/local/etc/apache2/ssl/mail.pem ssl_key_file: /usr/local/etc/apache2/ssl/mail.pem login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_max_userip_connections: 25 verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_extra_groups: postlocal mail_location: maildir:%h/Maildir:CONTROL=%h/Maildir/dovecot/private/control:INDEX=%h/Maildir/dovecot/private/indexes mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_plugins: acl fts fts_squat quota imap_quota mail_log_max_lines_per_sec: 0 imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: mail/ hidden: yes subscriptions: yes namespace: type: private separator: / prefix: Mail/ hidden: yes subscriptions: yes namespace: type: public separator: / prefix: #shared/decs/ location: maildir:/egr/mail/shared/decs:CONTROL=%h/Maildir/dovecot/public/control/decs:INDEX=%h/Maildir/dovecot/public/indexes/de list: yes subscriptions: yes auth default: passdb: driver: pam userdb: driver: passwd args: system_user= socket: type: listen client: path: /var/spool/postfix/private/auth mode: 384 user: postfix group: postfix plugin: quota: fs acl: vfile:/usr/local/etc/dovecot-acls:cache_secs=10 fts: squat

1 1

Re: [Dovecot] 1.1rc1: assertion failed: (output->offset > uid_list[0])
by Adam McDougall 06 May '08

06 May '08

Timo Sirainen wrote: > On Fri, 2008-03-07 at 00:17 -0500, Adam McDougall wrote: > >> $3 = {offset = 40896, stream_errno = 70, last_failed_errno = 70, overflow >> = 0, closed = 1, >> real_stream = 0x678500} >> > > Ah, 70 = Stale NFS handle in FreeBSD. Linux used something else. Squat > still needs some NFS fixes. > > Were these 'NFS fixes' done? I just put rc5 in production at my site an hour or two ago so I have just begun gathering log data. I may not see anything interesting for days but I will review them daily. (apologies if this gets double posted, I was sending mail and got disconnected)

1 0

[Dovecot] Couldn't init INBOX: Can't sync mailbox: Messages keep getting expunged
by David Jonas 06 May '08

06 May '08

Upon upgrading from 1.0.2 to 1.1rc4 I see this error for many of our users: Getting size of message UID=1 failed Couldn't init INBOX: Can't sync mailbox: Messages keep getting expunged Logging in with IMAP I would see a bunch of messages with no subject or time and blank bodies (usine horde/imp). Removing dovecot.index.log, dovecot.index.log.2, or dovecot-uidlist fixes the problem for the account (I chose dovecot.index.log). I imagine that forces a rebuild of the indexes. Removing other files in the directory didn't seem to make a difference, including dovecot.index or some arbitrary non-dovecot file. Is there a more conventional way around this problem?

3 9

[Dovecot] A previously unreported lsub/list discrepancy in 1.1rc5 and earlier
by Adam McDougall 06 May '08

06 May '08

Not sure about 1.0, I don't run it anymore :) But a few users discovered for a small issue that only affects a very small portion of my userbase where instructional correction will suffice. I guess I am reporting it in the interest of getting it out there, and I can live with it if not fixed but it might be an issue for some people. I'm running through my list of issues. Basically, if a user has a valid namespace prefix set such as mail/ (used to be required on old mail server but discouraged on new mail client setups with dovecot), lsub/list do not show public namespaces that the user has permission to via acl. If the user removes the namespace prefix, they can 'see' the public folders and subscribe. Additionally if the user subscribes to a public folder then puts mail/ back in the prefix, the folders are no longer listed. Not sure if public folders should be affected by the requested prefix in this manner, since they are not in the user's account. With prefix set: 3 lsub "" "mail/*" 4 list "" "mail/%" 5 list "" "mail/%/%" * OK [RAWLOG TIMESTAMP] 2008-05-05 21:07:16 * LSUB () "/" "mail/INBOX" * LSUB () "/" "mail/Sent Items" * LSUB () "/" "mail/Drafts" * LSUB () "/" "mail/Junk E-mail" * LSUB () "/" "mail/Sent" * LSUB () "/" "mail/Trash" 3 OK Lsub completed. * LIST (\HasNoChildren) "/" "mail/Drafts" * LIST (\HasNoChildren) "/" "mail/Sent Items" * LIST (\HasNoChildren) "/" "mail/Junk E-mail" * LIST (\HasNoChildren) "/" "mail/Sent" * LIST (\HasNoChildren) "/" "mail/Trash" 4 OK List completed. 5 OK List completed. Without prefix set: 3 lsub "" "*" 4 list "" "%" 5 list "" "%/%" * OK [RAWLOG TIMESTAMP] 2008-05-05 21:07:49 * LSUB () "/" "INBOX" * LSUB () "/" "Sent Items" * LSUB () "/" "Drafts" * LSUB () "/" "Junk E-mail" * LSUB () "/" "Sent" * LSUB () "/" "Trash" 3 OK Lsub completed. * LIST (\HasNoChildren) "/" "Drafts" * LIST (\HasNoChildren) "/" "Sent Items" * LIST (\HasNoChildren) "/" "Junk E-mail" * LIST (\HasNoChildren) "/" "Sent" * LIST (\HasNoChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "INBOX" 4 OK List completed. * LIST (\Noselect \HasChildren) "/" "#shared/be" * LIST (\Noselect \HasChildren) "/" "#shared/me" * LIST (\Noselect \HasChildren) "/" "#shared/cee" 5 OK List completed.

2 1

[Dovecot] Replication milestone 1
by Timo Sirainen 06 May '08

06 May '08

5 milestones planned currently. I'll start with the always-on multi-master replication, because that's the most difficult one to get working correctly and efficiently. So if during its implementation I find some design problems, less code needs to be fixed. Milestone 0 will hopefully be done within a month. This includes reading and replying to the rest of the mails on this list and getting a v1.1.0 release out. :) There will most likely also be a v1.2.0 release this summer that has some new features on top of v1.1. Several companies have asked for replication within the past year. At least two are willing to contribute some money into its development this summer, but having more wouldn't hurt of course. :) Paying also guarantees (within reasonable limits) that I'll listen to what kind of a installation you're planning and make sure that the replication will work in that kind of a setup. So, below's the milestone 1 fully described with a couple of FIXMEs left. The rest of the milestones are described only briefly. 0. Prerequisites: - Change v1.2 CONDSTORE implementation to allocate modseqs differently. Currently log file sequence + offset determines the modseq. This can't work in a cluster since their log files are different. Instead add a new "UIDs [..] have modseq X" transaction log record that gets updated when needed. UID list can be 0 to update higest-modseq. To avoid adding modseq for all changes, we can be optimistic and assume that usually multiple servers aren't doing changes at the same time. So the next transaction after modseq=5 record will have modseq=6 and the following one modseq=7, etc. - Update v2.0 framework to include v1.2 changes and make it work. Base the replication code on top of v2.0. - Shared mailboxes making all users' all mailboxes available for read/write within the same (replication) process. 1. Incremental replication for existing mailboxes. IMAP, POP3 and deliver use a replication plugin, which connect to a replication process via UNIX socket (or TCP optionally for chroots). The plugin sends the SAVE, EXPUNGE and STORE changes to the replication process, which forwards them to other servers. The other servers receive the commands and store them to local filesystem. The sending and the receiving sides have quite distinct jobs, so they should probably be implemented as separate processes. They could still use the same TCP socket though, replication sending process writes to the socket and replication receiving process reads the socket. The processes still need to share some state though. Most importantly keeping track of the mailbox master servers. This is probably the most cleanly implemented by having a separate master tracking process which the sending/receiving processes talk to via UNIX socket. The rest of the data sharing is about forwarding command replies (SAVE, STORE with CONDSTORE flag) to replication sender, so it can pass them on to the originating mail process. This can be done easily using an extra pipe/socket between the processes. Examples use: - C1 = Client 1 - C2 = Client 2 - S = Replication sending process - R = Remote replication receiving process - Small letter before commands = IMAP-like command tag - * before commands = tag for a command that doesn't expect a reply 1.1. Master tracking process Master tracking process is connected to sending and receiving replication processes. LOCK: (mail process -> replication sender -> master tracker) - User name - Mailbox name Reply: - success LOCK is sent by replication plugin from mail processes when it wants to assign UIDs for new messages. Replication sender proxies this command to master tracker. If server is already the master, the command returns success immediately. Otherwise tracker looks up from its cache who the current master is and requests it using the REQUEST command. Once GIVE command is received, reply success to the mail process. FIXME: handle timeouts (and master disconnections) somehow? UNLOCK: (mail process -> replication sender -> master tracker) - User name - Mailbox name No reply. UNLOCK is sent by mail processes after they've finished assigning UIDs and sending replication SAVEs. If this was the last lock, pending TAKE requests for this mailbox are handled. GIVE: (replication receiver -> master tracker) - User name - Mailbox name No reply. Notification that this server is now the master for the specified mailbox. If there are any pending LOCK requests for this mailbox, they're replied to in here. TAKE ([mail process ->] replication receiver -> master tracker): - User name - Mailbox name - Server ID No reply. Request for giving master state for the specified server. When this mailbox contains no locks, the TAKE command is forwarded to replication sending process which passes it to the requesting server. While waiting for existing locks to be releases, handling new LOCK commands for the mailbox must be delayed to avoid lock starvation. When forwarding TAKE command, the destination server ID is cached as being the mailbox's current master. If we're not the current master for this mailbox, forward the request using REQUEST command. This also happens if there are multiple pending TAKE requests. The first one gets to become the master and the rest of them are handled as REQUEST commands. REQUEST (master tracker -> replication sender): - User name - Mailbox name - Server ID of the current assumed master - Server ID who wants to be the new master (e.g. ourself) Request master status to be moved to the specified server. If server ID isn't ours, cache it as being the mailbox's current master. If we don't have any idea who the master might be currently, use the root server ID. ROOT-SET (replication receiver -> master tracker): - Server ID This command causes all cached master states to be dropped. Any new LOCK requests are delayed. Once all mailboxes are unlocked, drop being a master from all mailboxes and send ROOT-CLEAR command to replication sender, which passes on the information that we've cleared the master states. The given server ID is set to be the new root. ROOT-CLEAR (replication receiver -> master tracker): - Server ID Given server ID has notified that it has cleared its master states. If we're not the current root, this command is forwarded to it. If we're the root and this was the last pending ROOT-CLEAR, start handling the pending REQUEST and LOCK commands. FIXME: How is initial root selection done? How is it decided who's the new one when previous one dies? 1.2. Replication sending 1.2.1. Saving (For now we ignore the possibility of saving as non-master.) When a mail process wants to give UIDs for newly saved messages, it first requests for master lock for the mailbox from the master tracker process. Once UIDs have been assigned for the new messages, the messages are sent to replication sender using SAVE commands. After the last one is sent, the master lock is dropped. Note that this lock duration should be as small as possible, so in Dovecot's code this means doing both locking and unlocking in mailbox_transaction_commit(). If multiple processes are sending SAVEs at the same time, the replication sender may receive the UIDs in wrong order. It must reorder them before forwarding the SAVEs to other servers. Since all master LOCK/UNLOCK commands pass through the replication sender, it can figure out when it has seen all the SAVEs based on them. For example: C1-C3 -> S: a LOCK [1] S -> C1-C3: a OK [Client 1 sends the first mail] C1 -> S: b SAVE uid=5 .. [SAVE uid=5 depends on dropping [1] locks (currently clients 1,2,3)] C1 -> S: * UNLOCK [1] (left 2) [Client 1 starts sending more mails in a separate transaction, lock counter is incremented because of the previous SAVE] C1 -> S: d LOCK [2] (remember lock[2].prev_uid=5) S -> C1: d OK [Client 2 sends its mail] C2 -> S: b SAVE uid=9 .. [SAVE uid=9 depends on dropping [1-2] locks (currently clients 1,2,3)] C2 -> S: * UNLOCK [1] (left 1) [Client 3 sends its mail] C3 -> S: b SAVE uid=3 .. [SAVE uid=3 depends on dropping [1] lock (currently client 3). It doesn't depend on [2] lock, because uid < lock[2].prev_uid (3 < 5)] C3 -> S: * UNLOCK [1] (left 0) [SAVEs depending on [1] locks are ordered and forwarded.] S -> R: x SAVE uid=3 .. S -> R: y SAVE uid=5 .. [Client 1 finishes its second transaction] C1 -> S: f SAVE uid=7 [SAVE uid=7 depends on dropping [2] lock (currently client 1)] C1 -> S: * UNLOCK [2] (left 0) [SAVEs depending on [2] locks are ordered and forwarded] S -> R: x SAVE uid=7 .. S -> R: y SAVE uid=9 .. The idea is that locks have a counter which is incremented if there was a SAVE command sent after the previous LOCK command. The previous SAVE's UID (prev_uid) is also stored to the lock. When the first SAVE after LOCK arrives, it's assigned a dependency on all existing locks which have uid > prev_uid. The lock counter order doesn't guarantee an ascending prev_uid order. (An actual lock counter probably isn't even needed, prev_uid should be enough as the lock ID. Lock counter simplifies the above example though.) All subsequent SAVEs from the client before the next UNLOCK will have the same dependency as the first SAVE. This is because by that time the transaction has been committed and all messages within the transaction have been given UIDs. So in fact it wouldn't really matter in which order the SAVEs are even sent to the replication sender. Although sending them in order allows an extra optimization: If only a single client is holding a lock, the SAVEs can be immediately forwarded as they're being received. After all lock dependencies have been dropped, it's guaranteed that all new SAVEs will have higher UIDs, so the SAVEs can be ordered and forwarded. A further optimization could use some kind of weak locks that are dropped after the client's first SAVE command. After the weak lock count has dropped to zero, the messages can started to be sent. For example assume two clients having the same lock counter. Both clients would be sending 10000 messages within the same transaction. Waiting for and buffering all of them would waste a lot of memory. Instead it would be possible to read the first SAVE from the first client and then block until the first SAVE is read from the second client. The SAVE with a smaller UID can be forwarded to remote servers. The next message is then read from that connection, and this is continued until all messages have been processed. A simpler solution would have been to order and forward SAVEs only when lock counter dropped to zero, but under very high load it's (at least theoretically) possible that the counter never drops to zero. In synchronous setups (recommended whenever possible) the SAVE commands use a tag (not "*"), which requests an ack reply from the remote. After replication sender has sent SAVE to a remote server, the remote server eventually replies back. This reply is forwarded from replication receiver to sender, which in turn forwards it to the mail process. After mail process has finished sending all SAVEs, it waits until it has received at least one ack for each SAVEd message. If the replication sender sent the SAVE to multiple servers, mail process may receive multiple acks for each message. It should just ignore the ones it doesn't care about. 1.2.2. Modseq updating If all mailbox modifications were done only while the server was the mailbox master, there wouldn't be any problems with modseq updates, because only one server could modify the mailbox at a time. This scales badly though, so it's preferrable to move the master only when absolutely required (for SAVEs) and handle modseqs another ways. Modseqs are incremented by each mailbox modification. All modification commands contain a modseq parameter. When applying the modification command make sure the local modseq is at least as high as the modification command's modseq. If the local modseq is higher, broadcast the new modseq to all other servers using MODSEQ command. When receiving a MODSEQ command, update the modseq only if its current value is lower than the received one. Remember that modseqs can also be updated for expunged messages. All this means that eventually everyone's modseq will be the highest assigned modseq for the change in the cluster. It doesn't matter if temporarily some clients saw lower modseqs. The worst that can happen is that some extra FLAG/MODSEQ updates are sent to the client. Although there is a problem if a client can jump from a server where it had higher modseqs to a server that hadn't yet received the incremented modseqs and performed a sync using the higher modseq. If the updated modseqs come after the sync, they're lost from the client. This could be avoided by issuing a cluster-wide sync wait before such syncing commands are run. 1.2.3. Expunging EXPUNGE commands can be replicated without waiting for anything. There are problems with messages getting expunged while COPY is being handled, but this will be resolved later when COPY is implemented. 1.2.4. Flag updates When STORE is received by a master, it checks if it has higher modseqs in messages than the modseq in STORE parameter. Then it applies all the changes and forwards the changes to other servers using possibly updated modseqs. For messages that had higher initial modseqs their current flags are sent back to the originating server to fix a potential desync. If STORE is initiated by the master, there are no flag desynchronization possibilities. The correctness of applying conflicting changes could be improved by including a "highest modseq of messages before this STORE" parameter. The applying server (master) could then find the flags from that point in time and apply changes on top of it. And finally on the top would be applied newer changes (that were already once applied). There could still be conflicting changes, but the result would be better for updates that had been delayed for a long time. Finding these flag changes and old flag values isn't simple though, so this won't be at least in initial implementation. STORE UNCHANGEDSINCE (CONDSTORE extension) is initially implemented by grabbing a master lock. If there are simultaneous STOREs in other servers, they'll temporarily have lower modseqs and different message flags. Eventually when the STOREs reach the master, they will be applied on top of the CONDSTORE modification. So even if normal STOREs were sent slightly earlier than CONDSTORE, they'd eventually be applied on top of the CONDSTORE change. This makes the STORE UNCHANGEDSINCE work correctly (even if with a slight delay), and our multi-master replication should be fully compatible with the CONDSTORE spec. 1.3. Replication receiving Replication receives 3 different types of data from remote sender: 1. Replies to commands this server's replication sender sent 2. Message texts (as part of SAVE) 3. Metadata updates (SAVEs, STORE, EXPUNGE, etc.) Command replies are handled by directly forwarding them to the replication sender process via a pipe/socket. 1.3.1. Receiving SAVEs The message text part of the SAVE is stored in a file. The file format depends on the server's configured default data format. For now we consider only maildir format where the data is written as-is to the file. This file is later hard linked to the destination maildir directory. If multiple partitions are used, the file should be written to the correct partition. The initial code could write the file to the destination mailbox's tmp/ directory to make sure the partition is correct. There may be some permission problems with this approach though, a separate replication drop directory would be nicer. The rest of the SAVE is processed similarly to other metadata updates. The path to the written file is added as new metadata to the SAVE command. 1.3.2. Metadata updates The primary replication receiver process's job is to read data from the network as fast as possible. Processing the actual updates can take a while, so the work is distributed to multiple worker processes. As discussed above, the primary replication receiver process still writes message texts to files. The workers could do this as well, but it would mean that the text needs to be sent via IPC to the workers, which adds extra overhead. If the message writing really becomes the bottleneck, this change could be done. The replication receiver tries to pass the same user's updates to the same workers so they can benefit from keeping mailboxes open longer. Each worker could be limited to e.g. 100 open mailboxes. The worker handles the SAVE/EXPUNGE/STORE commands using the normal mailbox handling functions. After the changes were successfully committed, commands that had tags are replied as having succeeded. If a change failed, a failure reply is sent instead for it. Replication receiver passes this reply to the replication sender (not to be confused by remote command replies which are also forwarded), which in turn passes it to the originating server. ------ 2. Mailbox synchronization for existing mailboxes. - As described in the replication protocol. - IMAP UID conflict resolution. 3. Mailbox list synchronization. - Track creates, deletes, renames. - Add unique global mailbox ID which is preserved across renames and allows replication to perform renaming (and symlinking?) 4. More features 4.1. Global UIDs - Save GUIDs to messages (dbox: metadata, maildir: dovecot-uidlist) - Tracking GUIDs globally - Implement COPY command - Implement SAVEs sending only global UIDs and FETCHing unknown ones 4.2. Support for untrusted user-run replication processes - Make SAVE and work without being a master - Make CONDSTORE's STORE UNCHANGEDSINCE work without being a master 4.3. Transactions - Wrap changes into transactions just like they're in the originating Dovecot's transaction (e.g. TX-BEGIN, TX-END commands) - On receiving side a transaction is handled in a single Dovecot transaction by a single worker. 4.4. Cluster-wide sync - Broadcast a ping packet and wait for a reply from all servers on the cluster. This ensures that all changes before the ping packet was sent have been received. - Then ping replication receiver process and have it ping worker processes to wait until all received changes have been committed. - CHECK command could do it. - CONDSTORE/QRESYNC commands that take modseq parameters could maybe do it? Or would it be too slow? It would at least increase reliability. We could probably also figure out some rules when the sync is needed and when not. 5. dbox support - Message text can't just be written to a file and renamed. At minimum some dbox metadata needs to be written to it. - Files can't be shared between mailboxes by hard linking like they can be with maildir

1 1

[Dovecot] Timeout when using icedove's searching on a large amount of email.
by guillaume.yziquel＠free.fr 05 May '08

05 May '08

Hello list. I'm using dovecot as a local server, where I'm the only user (or so), and I appreciate using icedove searching functionality to roam through the whole inbox in search of some specific string in the body of my emails. Unfortunately, recently, such a search has become impossible, since the search takes too much time, and the connection times out. I've looked throughout the .conf file and the documentation, but I haven't found where I could increase the delay until timeout. If someone knew the right option in the .conf file, it would be really great... Guillaume Yziquel.

2 1

[Dovecot] imapsync + gnupg?
by Neal Becker 05 May '08

05 May '08

I'd like to mirror my dovecot server (which only serves myself). I'm thinking to use gmail. Problem is, I don't want all my mail going to gmail in plain text. I'd like to gpg+mime encrypt each mail using my public key. Any thoughts on how to do this?

2 1

[Dovecot] Inotify instance limit for user exceeded, disabling.
by Anders 05 May '08

05 May '08

Hi. What does the warning "Inotify instance limit for user exceeded, disabling." mean, and how do I get rid of it? I assume that I have to change a limit somewhere? Regards, Anders.

2 4

[Dovecot] mail_chroot problems / dovecot 1.1rc4
by Michal Soltys 05 May '08

05 May '08

Hello I've noticed a little strange behaviour of that option. For example with following settings: system user: admin, with its home directory as /home/admin dovecot options: as reported by dovecot -n (in attachment) dovecot will try to chroot into /home/home/admin with the following message in logs, in my case: Fatal: chdir(/home/home/admin) failed with uid 1999: No such file or directory The same happens if I use per-user chroot= option in userdb, f.e. in passwd-file I've noticed it's just now, as I've always used explicit chroot dirs specified through passwd-file with /./ (which works perfectly fine, except harmless double slashes in logs), and didn't bother with single system user (I made some chroot/lock related bugreports in distant 1.0rcXX past). Cheers Michal # 1.1.rc4: /etc/dovecot.conf base_dir: /var/dovecot/ protocols: imap imaps pop3 pop3s ssl_listen: * ssl_ca_file: /etc/ssl/cert_bundle.pem ssl_cert_file: /etc/ssl/ca_ppgk/certs/fetch_crt.pem ssl_key_file: /etc/ssl/ca_ppgk/private/fetch_key.pem verbose_ssl: yes login_dir: /var/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: Dovecot IMAP server ready. login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_process_size: 32 valid_chroot_dirs: /home mail_chroot: /home verbose_proctitle: yes first_valid_uid: 1999 first_valid_gid: 10 mail_location: maildir:~/mspace/maildir:INDEX=~/mspace/index:INBOX=~/mspace/inbox:CONTROL=~/mspace/control mail_debug: yes fsync_disable: yes lock_method: flock mbox_read_locks: flock mbox_write_locks: flock mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: / inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login verbose: yes debug: yes passdb: driver: passwd-file args: /etc/dovecot.z1.passwd passdb: driver: passwd-file args: /etc/dovecot.passwd passdb: driver: passwd userdb: driver: passwd-file args: /etc/dovecot.z1.passwd userdb: driver: passwd-file args: /etc/dovecot.passwd userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix plugin: quota: maildir

2 4

[Dovecot] libsieve support
by Mateusz Kijowski 05 May '08

05 May '08

Hi, I was wondering - are there any plans on switching the sieve plug-in to use libsieve (http://libsieve.sourceforge.net/)? The rationale of using this library is simple - cmusieve codebase seems stagnant and libsieve promises to implement some new sieve rfc drafts. -- matik

2 1

[Dovecot] v1.1.rc5 released
by Timo Sirainen 05 May '08

05 May '08

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc5.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc5.tar.gz.sig I've finally gone through all my unread mails and fixed most of the reported bugs. There are only a couple ones left that I can't reproduce. Please report if you still have any problems with rc5, even if you already have reported the same bug before. v1.1.rc6 will hopefully be the last RC before v1.1.0. + Support cross-realm Kerberos 5 authentication. Based on patch by Zachary Kotlarek. + Added dict_db_config setting to point to a Berkeley DB config file. + If mail_chroot ends with "/.", remove chroot prefix from home directory. - Fixed several bugs and memory leaks in ACL plugin. LIST and LSUB may have listed mailboxes where user had no 'l' access. STORE could have been used to update any flags without appropriate access. - mbox: Valid-looking From_-lines in message bodies caused the message to be split to two messages (broken since v1.0). - Plugin initialization hooks were called in wrong order, possibly causing problems when multiple plugins were used at the same time. - Expire plugin was broken - LIST-EXTENDED options were ignored. - LDAP: Static attribute names weren't working correctly - deliver: mail_uid and mail_gid settings weren't used. - pop3 + maildir++ quota: maildirsize file wasn't created if it didn't exist already. - dnotify: Waiting for dotlock to be deleted used 100% CPU

2 1

[Dovecot] dovecot 1.1.rc3 assertion failed at index_mailbox_set_recent_uid while deleting message with thunderbird.
by Diego Liziero 05 May '08

05 May '08

To some users happens this assertion failure while deleting a message. dovecot: Mar 10 08:40:44 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists (&ibox->recent_flags, uid)) dovecot: Mar 10 08:40:44 Error: IMAP(user): Raw backtrace: [see bleow] dovecot: Mar 10 08:40:44 Error: child 17683 (imap) killed with signal 6 And the message doesn't get deleted. Here one of the backtraces (gdb) bt #0 0x00ae9402 in __kernel_vsyscall () #1 0x00725ba0 in raise () from /lib/libc.so.6 #2 0x007274b1 in abort () from /lib/libc.so.6 #3 0x080ce02d in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80e1750 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfd8c6a4 "=???\016\b'") at failures.c:424 #4 0x080cdc3c in i_panic (format=0x80e1750 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:187 #5 0x0809bb4a in index_mailbox_set_recent_uid (ibox=0x88ca768, uid=1041) at index-sync.c:39 #6 0x0808085f in mbox_sync_loop (sync_ctx=0xbfd8c8d0, mail_ctx=0xbfd8cac4, partial=true) at mbox-sync.c:457 #7 0x08081361 in mbox_sync (mbox=0x88ca768, flags=18) at mbox-sync.c:1504 #8 0x08079cf9 in mbox_transaction_commit (t=0x88c5550, log_file_seq_r=0xbfd8cbc8, log_file_offset_r=0xbfd8cbc0) at mbox-transaction.c:45 #9 0x0809c69e in index_transaction_commit (_t=0x88cb1c0, uid_validity_r=0xbfd8cc48, first_saved_uid_r=0xbfd8cc44, last_saved_uid_r=0xbfd8cc40) at index-transaction.c:105 #10 0x0805b0cf in cmd_copy (cmd=0x88b75c0) at cmd-copy.c:141 #11 0x0805f079 in cmd_uid (cmd=0x88b75c0) at cmd-uid.c:26 #12 0x0805f9a9 in client_command_input (cmd=0x88b75c0) at client.c:546 #13 0x0805fa3e in client_command_input (cmd=0x88b75c0) at client.c:595 #14 0x080601c5 in client_handle_input (client=0x88b7368) at client.c:636 #15 0x080603de in client_input (client=0x88b7368) at client.c:691 #16 0x080d5ba0 in io_loop_handler_run (ioloop=0x88b59b0) at ioloop-epoll.c:201 #17 0x080d4e28 in io_loop_run (ioloop=0x88b59b0) at ioloop.c:301 #18 0x08067dbc in main (argc=Cannot access memory at address 0x413a ) at main.c:293 (gdb) bt full #0 0x00ae9402 in __kernel_vsyscall () No symbol table info available. #1 0x00725ba0 in raise () from /lib/libc.so.6 No symbol table info available. #2 0x007274b1 in abort () from /lib/libc.so.6 No symbol table info available. #3 0x080ce02d in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80e1750 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfd8c6a4 "=???\016\b'") at failures.c:424 backtrace = 0x88add50 "/usr/libexec/dovecot/imap [0x80ce024] -> /usr/libexec/dovecot/imap [0x80cdc3c] -> /usr/libexec/dovecot/imap [0x809bb4a] -> /usr/libexec/dovecot/imap [0x808085f] -> /usr/libexec/dovecot/imap(mbox_sync+"... #4 0x080cdc3c in i_panic (format=0x80e1750 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:187 args = 0xbfd8c6a4 "=???\016\b'" #5 0x0809bb4a in index_mailbox_set_recent_uid (ibox=0x88ca768, uid=1041) at index-sync.c:39 __PRETTY_FUNCTION__ = "index_mailbox_set_recent_uid" #6 0x0808085f in mbox_sync_loop (sync_ctx=0xbfd8c8d0, mail_ctx=0xbfd8cac4, partial=true) at mbox-sync.c:457 mail = {uid = 268, idx_seq = 133265, keywords = {arr = {buffer = 0x88d3770, element_size = 3218655176}, v = 0x88d3770, v_modifiable = 0x88d3770}, flags = 172 '???', uid_broken = 1, expunged = 0, pseudo = 1, from_offset = 143457960, body_size = 579466361970685888, offset = 143456608, space = 578778797692682360} rec = (const struct mail_index_record *) 0xb7e6f008 uid = 1041 messages_count = 3518 offset = 563 ret = <value optimized out> expunged = false skipped_mails = false uids_broken = false #7 0x08081361 in mbox_sync (mbox=0x88ca768, flags=18) at mbox-sync.c:1504 ret = <value optimized out> #8 0x08079cf9 in mbox_transaction_commit (t=0x88c5550, log_file_seq_r=0xbfd8cbc8, log_file_offset_r=0xbfd8cbc0) at mbox-transaction.c:45 mt = (struct mbox_transaction_context *) 0x88cb1c0 mbox = (struct mbox_mailbox *) 0x88ca768 lock_id = 3 ret = 0 #9 0x0809c69e in index_transaction_commit (_t=0x88cb1c0, uid_validity_r=0xbfd8cc48, first_saved_uid_r=0xbfd8cc44, last_saved_uid_r=0xbfd8cc40) at index-transaction.c:105 itrans = (struct mail_index_transaction *) 0x0 seq = 7 offset = 20544 #10 0x0805b0cf in cmd_copy (cmd=0x88b75c0) at cmd-copy.c:141 client = (struct client *) 0x88b7368 storage = (struct mail_storage *) 0x88b6c80 destbox = (struct mailbox *) 0x88ca768 t = (struct mailbox_transaction_context *) 0x0 search_arg = <value optimized out> messageset = 0x88bb6c0 "224" mailbox = 0x88bb6c8 "Trash" msg = <value optimized out> sync_flags = <value optimized out> imap_flags = <value optimized out> copy_count = 1 uid_validity = <value optimized out> uid1 = <value optimized out> uid2 = <value optimized out> ret = 1 __PRETTY_FUNCTION__ = "cmd_copy" #11 0x0805f079 in cmd_uid (cmd=0x88b75c0) at cmd-uid.c:26 command = (struct command *) 0x6 cmd_name = 0x88bb6b8 "copy" #12 0x0805f9a9 in client_command_input (cmd=0x88b75c0) at client.c:546 client = (struct client *) 0x88b7368 command = <value optimized out> __PRETTY_FUNCTION__ = "client_command_input" #13 0x0805fa3e in client_command_input (cmd=0x88b75c0) at client.c:595 client = (struct client *) 0x88b7368 command = (struct command *) 0x6 __PRETTY_FUNCTION__ = "client_command_input" #14 0x080601c5 in client_handle_input (client=0x88b7368) at client.c:636 _data_stack_cur_id = 3 ret = <value optimized out> remove_io = <value optimized out> handled_commands = false #15 0x080603de in client_input (client=0x88b7368) at client.c:691 cmd = <value optimized out> output = (struct ostream *) 0x88b74ec bytes = 24 __PRETTY_FUNCTION__ = "client_input" #16 0x080d5ba0 in io_loop_handler_run (ioloop=0x88b59b0) at ioloop-epoll.c:201 ctx = <value optimized out> event = (const struct epoll_event *) 0x88b5ae8 list = (struct io_list *) 0x88b7568 io = (struct io_file *) 0x88c0dd0 tv = {tv_sec = 1799, tv_usec = 999737} t_id = 2 msecs = <value optimized out> ret = 1 i = 0 j = 0 call = <value optimized out> #17 0x080d4e28 in io_loop_run (ioloop=0x88b59b0) at ioloop.c:301 No locals. #18 0x08067dbc in main (argc=Cannot access memory at address 0x413a ) at main.c:293 No locals. Regards, Diego.

2 6

[Dovecot] Users w/o acl access appear to be subscribed to public folders (1.1b8)
by Adam McDougall 05 May '08

05 May '08

I noticed this today, I had a user outside of our department test out dovecot. They were using squirrelmail and I noticed that dovecot thinks this user is subscribed to ALL public folders even though a dovecot ACL prevents all access. I'm pretty sure access is still denied. I was able to reproduce this with a guest account I added: l lsub "" "#shared/decs/%" * LSUB (\Noselect) "/" "#shared/decs/linuxadmin" * LSUB (\Noselect) "/" "#shared/decs/jbossadmin" * LSUB () "/" "#shared/decs/support" * LSUB () "/" "#shared/decs/receipts" * LSUB (\Noselect) "/" "#shared/decs/pcadmin" * LSUB () "/" "#shared/decs/network" * LSUB (\Noselect) "/" "#shared/decs/printmaster" * LSUB () "/" "#shared/decs/postmaster" * LSUB (\Noselect) "/" "#shared/decs/unixadmin" * LSUB () "/" "#shared/decs/security" * LSUB (\Noselect) "/" "#shared/decs/webmaster" l OK Lsub completed. This only seems to happen when the acl plugin is enabled. Without the acl plugin, these are not listed as subscriptions. After deleting /egr/mail/shared/decs/dovecot-acl-list and re-enabling the acl plugin, I get this: l lsub "" "#shared/decs/%" * LSUB () "/" "#shared/decs/unixadmin" * LSUB () "/" "#shared/decs/support" * LSUB () "/" "#shared/decs/security" * LSUB () "/" "#shared/decs/printmaster" * LSUB () "/" "#shared/decs/postmaster" * LSUB () "/" "#shared/decs/pcadmin" * LSUB () "/" "#shared/decs/network" * LSUB () "/" "#shared/decs/linuxadmin" * LSUB () "/" "#shared/decs/webmaster" * LSUB () "/" "#shared/decs/jbossadmin" l OK Lsub completed. Is it related, or is it different just because a new dovecot-acl-list got created by another user already (but is mode 700?)

2 3

[Dovecot] Compiling plugins
by Juan Asensio Sánchez 05 May '08

05 May '08

Hi I use Debian Etch 4.0r3. I am trying to compile antispam plugin, but i have no idea about how to do it cause i have never done so. I have compiled source packages for Debian with some instructions in some pages, but i can not compile this plugin separately. Can anyone help me or give some tips to do this (yes, i have google'd it yet, but no good results). This is the result trying to compile antispam plugin: ---------------------------------------------------- pdc-server:~/tmp/antispam# ls -l ../dovecot-1.1.rc5/ total 3508 -rw-r--r-- 1 root root 322488 2008-05-05 00:30 aclocal.m4 -rw-r--r-- 1 root root 551 2008-03-10 23:23 AUTHORS -rw-r--r-- 1 root root 804 2008-05-05 01:01 autogen.sh -rw-r--r-- 1 root root 1470323 2008-05-05 00:31 ChangeLog -rwxr-xr-x 1 root root 3707 2008-03-10 23:23 compile -rwxr-xr-x 1 root root 44892 2008-02-17 21:10 config.guess -rw-r--r-- 1 root root 14778 2008-05-05 00:31 config.h -rw-r--r-- 1 root root 13687 2008-05-05 00:31 config.h.in -rwxr-xr-x 1 root root 18343 2008-05-04 12:13 config.rpath -rwxr-xr-x 1 root root 33387 2008-02-17 21:10 config.sub -rwxr-xr-x 1 root root 1086089 2008-05-05 00:30 configure -rw-r--r-- 1 root root 56429 2008-05-05 00:30 configure.in -rw-r--r-- 1 root root 3980 2008-03-10 23:23 COPYING -rw-r--r-- 1 root root 26536 2008-03-10 23:23 COPYING.LGPL -rw-r--r-- 1 root root 1023 2008-03-10 23:23 COPYING.MIT drwxr-xr-x 4 root root 4096 2008-05-05 01:01 debian -rwxr-xr-x 1 root root 15936 2008-03-10 23:23 depcomp drwxrwxrwx 3 root root 4096 2008-05-05 01:01 doc -rw-r--r-- 1 root root 187 2008-03-10 23:23 dovecot-config.in.in -rw-r--r-- 1 root root 46655 2008-05-05 00:30 dovecot-example.conf drwxr-xr-x 3 root root 4096 2008-05-05 01:01 dovecot-managesieve drwxr-xr-x 3 root root 4096 2008-05-05 01:01 dovecot-sieve -rw-r--r-- 1 root root 1235 2008-03-10 23:23 INSTALL -rwxr-xr-x 1 root root 9233 2008-03-10 23:23 install-sh -rw-r--r-- 1 root root 199984 2008-04-05 19:05 ltmain.sh -rw-r--r-- 1 root root 656 2008-03-10 23:23 Makefile.am -rw-r--r-- 1 root root 24492 2008-05-05 00:30 Makefile.in -rwxr-xr-x 1 root root 11014 2008-03-10 23:23 missing -rw-r--r-- 1 root root 71910 2008-05-05 00:30 NEWS -rw-r--r-- 1 root root 1344 2008-03-16 10:58 README drwxrwxrwx 26 root root 4096 2008-05-05 00:32 src -rw-r--r-- 1 root root 0 2008-03-10 23:23 stamp.h.in -rw-r--r-- 1 root root 14980 2008-05-05 00:30 TODO pdc-server:~/tmp/antispam# ls -l total 144 -rw-r--r-- 1 root root 7359 2008-05-05 00:31 antispam.7 -rw-r--r-- 1 root root 4864 2008-05-05 00:31 antispam-plugin.c -rw-r--r-- 1 root root 2418 2008-05-05 00:31 antispam-plugin.h -rw-r--r-- 1 root root 13279 2008-05-05 00:31 antispam-storage-1.0.c -rwxr-xr-x 1 root root 14026 2008-05-05 00:58 antispam-storage-1.1 -rw-r--r-- 1 root root 14308 2008-05-05 00:31 antispam-storage-1.1.c -rw-r--r-- 1 root root 18101 2008-05-05 00:31 COPYING -rw-r--r-- 1 root root 4351 2008-05-05 00:31 crm114-exec.c -rw-r--r-- 1 root root 547 2008-05-05 00:31 debug.c -rw-r--r-- 1 root root 1854 2008-05-05 00:31 defconfig -rw-r--r-- 1 root root 5087 2008-05-05 00:31 dspam-exec.c -rw-r--r-- 1 root root 7631 2008-05-05 00:31 mailtrain.c -rw-r--r-- 1 root root 2244 2008-05-05 00:31 Makefile -rw-r--r-- 1 root root 372 2008-05-05 00:31 NOTES -rw-r--r-- 1 root root 23 2008-05-05 00:31 README -rw-r--r-- 1 root root 1855 2008-05-05 00:31 signature.c -rw-r--r-- 1 root root 617 2008-05-05 00:31 signature.h -rw-r--r-- 1 root root 3859 2008-05-05 00:31 signature-log.c pdc-server:~/tmp/antispam# grep -v '^ *$#.*$\?$' .config DOVECOT=/root/tmp/dovecot-1.1.rc5 DOVECOT_VERSION=1.1 # CURRENTLY BROKEN BACKEND=dspam-exec INSTALLDIR=/usr/lib/dovecot/modules/imap USER=root GROUP=root PLUGINNAME=antispam pdc-server:~/tmp/antispam# make install cc -o .o cc: no input files make: *** [.o] Error 1 pdc-server:~/tmp/antispam# ---------------------------------------------------- Thanks in advance.

1 1

Re: [Dovecot] Dovecot SASL doesn't seem to be working with Postfix
by Jeremy Gillick 05 May '08

05 May '08

w00t. Thanks everyone for all your input. It works now. The key was to set mydestination to "localhost, localhost.localdomain". From there Postfix started using Dovecot LDA (deliver) and I was able to track the rest of the problems down through the log files. Here's my latest config for anybody interested: ## DOVECOT ## # 1.0.13: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log protocols: imap pop3 imaps pop3s disable_plaintext_auth: no verbose_ssl: yes login_dir: /usr/local/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/local/libexec/dovecot/pop3-login mail_location: maildir:~/Maildir dotlock_use_excl: 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/local/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/local/lib/dovecot/pop3 pop3_uidl_format: %08Xu%08Xv auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=postfix gid=postfix home=/home/vmail/%u socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /usr/local/var/run/dovecot/auth-master mode: 384 user: vmail group: vmail ## POSTFIX main.cf ## broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 default_privs = nobody html_directory = no inet_interfaces = $myhostname, localhost mail_owner = postfix mail_spool_directory = /home/vmail/ mailq_path = /usr/bin/mailq manpage_directory = /usr/local/man mydestination = localhost, localhost.localdomain mydomain = $myhostname myhostname = mixermixer3.com newaliases_path = /usr/bin/newaliases queue_directory = /var/spool/postfix/ readme_directory = no sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail setgid_group = postdrop smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_CAfile = /etc/postfix/ssl/smtpd.pem smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.pem smtpd_tls_key_file = /etc/postfix/ssl/smtpd.pem smtpd_tls_loglevel = 1 smtpd_tls_session_cache_timeout = 3600s unknown_local_recipient_reject_code = 550 virtual_mailbox_domains = $myhostname virtual_transport = dovecot ## POSTFIX (a few lines from 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 # Dovecot LDA dovecot unix - n n - - pipe flags=DRhu user=nobody:mail argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} Thanks Everyone! - Jeremy

1 0

[Dovecot] Dovecot SASL doesn't seem to be working with Postfix
by Jeremy Gillick 05 May '08

05 May '08

I've tried to setup Postfix to use SASL, but it still doesn't seem to be working with Dovecot. I've set things up based on these instructions: http://wiki.dovecot.org/HowTo/SimpleVirtualInstall http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL http://wiki.dovecot.org/LDA I've compiled Postfix with Dovecot SASL and SSL/TLS support. The problems I'm seeing in Postfix are: * Virtual users are not being recognized (it'll only delivers mail for local users) * For mail it does deliver, it uses the local user permissions ( I want it to use the vmail user) * I had to modify 'mail_spool_directory' to get it to use the /home/vmail/ directory * For mail delivered to local users, it still doesn't come up in my email client when I check for new mail. I just keep feeling like the SASL integration is not working. Can anybody shed some light? --- DOVECOT config # 1.0.13: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log protocols: imap pop3 imaps pop3s disable_plaintext_auth: no verbose_ssl: yes login_dir: /usr/local/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/local/libexec/dovecot/pop3-login mail_location: maildir:~/Maildir dotlock_use_excl: 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/local/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/local/lib/dovecot/pop3 pop3_uidl_format: %08Xu%08Xv auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=postfix gid=postfix home=/home/vmail/%u socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /usr/local/var/run/dovecot/auth-master mode: 384 user: vmail ---- POSTFIX main.cf alias_maps = $alias_database broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 default_privs = nobody html_directory = no inet_interfaces = $myhostname, localhost mail_owner = postfix mail_spool_directory = /home/vmail/ mailq_path = /usr/bin/mailq manpage_directory = /usr/local/man mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain mydomain = $myhostname myhostname = mixermixer3.com newaliases_path = /usr/bin/newaliases queue_directory = /var/spool/postfix/ readme_directory = no sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail setgid_group = postdrop smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_CAfile = /etc/postfix/ssl/smtpd.pem smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.pem smtpd_tls_key_file = /etc/postfix/ssl/smtpd.pem smtpd_tls_loglevel = 1 smtpd_tls_session_cache_timeout = 3600s unknown_local_recipient_reject_code = 550 virtual_mailbox_domains = $myhostname virtual_transport = dovecot ---- POSTFIX master.cf (just the important lines) 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 dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} THANKS, Jeremy

1 1

[Dovecot] Segfault when opening a public folder, dovecot 1.1 beta4
by Adam McDougall 04 May '08

04 May '08

I was trying to debug this with gdb, but I'm not sure how to make env MAIL=maildir:~/Maildir MAIL_PLUGINS=acl ACL=vfile gdb /tmp/imap understand the #shared/decs namespace from below so I can SELECT it. I have a number of maildirs under #ahared/decs, I tried opening at least 2 of them but dovecot gives sig 11 without a direct error about the problem. I don't think this was exactly the same problem in 1.1b3, but unfortunately I deleted all the patches I was testing with so it would be a pain to test the same situation with 1.1b3 again (although if needed, I can). If dovecot-shared exists in the folder I try to open, dovecot says: Oct 27 12:57:38 gribble dovecot: IMAP(mcdouga9): fchown() failed with file /home/mcdouga9/Maildir/dovecot11testing/public/indexes/decs/.unixadmin/dovecot.index.log: Operation not permitted Oct 27 12:57:38 gribble dovecot: child 55470 (imap) killed with signal 11 I am used to getting the first message because dovecot tries to apply perms from dovecot-shared to the index files which are elsewhere. If I open a public folder without dovecot-shared, I see no contents but it does not sig11. I am NOT using the acl plugin right now, it didn't seem to make a difference if it was loaded. When I left off with the dovecot 1.1b3 + 8 patches, I believe I was getting an assertion. Please let me know if I goofed up something, I have a strange feeling about that here, or if you need more info. I'd like to go ahead and get a gdb trace. # 1.1.beta4: /usr/local/etc/dovecot.conf ssl_cert_file: /usr/local/etc/apache2/ssl/cert.pem ssl_key_file: /usr/local/etc/apache2/ssl/cert.pem disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 0 mail_location: maildir:%h/Maildir:CONTROL=%h/Maildir/dovecot11testing/private/control:INDEX=%h/Maildir/dovecot11testing/private/indexes mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_log_max_lines_per_sec: 0 imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep namespace: type: public separator: / prefix: #shared/decs/ location: maildir:/egr/mail/shared/decs:CONTROL=%h/Maildir/dovecot11testing/public/control/decs:INDEX=%h/Maildir/dovecot11testing/public/indexes/decs list: yes subscriptions: yes namespace: type: private separator: / prefix: mail/ location: maildir:%h/Maildir:CONTROL=%h/Maildir/dovecot11testing/private/control:INDEX=%h/Maildir/dovecot11testing/private/indexes hidden: yes subscriptions: yes namespace: type: private separator: / inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 384 user: postfix group: postfix plugin: acl: vfile:/usr/local/etc/dovecot-acls

2 18

[Dovecot] FAQ: setting thunderbird to talk to dovecot
by Mauricio Tavares 04 May '08

04 May '08

Let's say I have a postfix box, named mail.thespider.com, which is setup to handle virtual mailbox domains. One of these domains will handle is, thespider.com, and my email address in that domain is boris(a)thespider.com. As I setup dovecot, I can telnet to the pop3 port (110) and test it by logging in as boris(a)thespider.com (I would try the imap port but I do not know how to login to imap from the telnet prompt): [raub@taz ~]$ telnet mail.thespider.com 110 Trying 192.168.1.12... Connected to mail.thespider.com (192.168.1.12). Escape character is '^]'. +OK dovecot ready. user boris(a)thespider.com +OK pass creepycrawly +OK Logged in. quit +OK Logging out. Connection closed by foreign host. [raub@taz ~]$ How would I do the same under thunderbird from a machine in the same lan (taz.thespider.com)? It seems to keep trying to login as boris(a)mail.thespider.com, which will not fly.

7 10

[Dovecot] UID inserted in the middle of mailbox errors
by Dean Brooks 04 May '08

04 May '08

Hi, We are still getting, on a daily basis, users who cannot move messages to Trash or expunge Trash due to these errors: Mar 28 10:43:57 tm2 dovecot: [ID 107833 mail.error] IMAP(kss021): mbox sync: UID inserted in the middle of mailbox /home/kss021/Mail/Trash (3137 > 536, seq=2, idx_msgs=76) Our users have no other access to their mailbox other than Dovecot, and we are using mbox format and 1.1rc3. Deleting the indexes fixes the problem, so it seems to be a problem with index corruption and not something inherently wrong with the mailbox. That is, once I delete the index files, the problem does not come back immediately. I've seen others on the list with the same problem, but I wasn't able to find a workaround. It's happening more and more frequently. I guess what I don't understand is why Dovecot cant just mark the index invalid and purge it instead of failing over and over. I thought the whole point behind Dovecot's indexing is that it was able to detect index inconsistencies and mark the index invalid. Any help is much appreciated. Even a quick stopgap fix would be a lifesaver, short of a cronjob that just purges everyone's index files every 2 hours (which sort of defeats the point of using Dovecot). -- Dean Brooks dean(a)iglou.com

3 4

[Dovecot] Embedded From_ lines breaking Content-Length (and Dovecot)
by Lennart Lövstrand 04 May '08

04 May '08

I feel like I'm going totally crazy. Is it just me, or have embedded From_ lines really been breaking mbox messages since (at least) dovecot 1.0? I found a whole lot of broken messages in an old mailbox of mine and when I looked closer at it, it seemed like Dovecot was ignoring the Content-Length header and truncating the messages at the first embedded From_ line instead. Figuring that this probably just was a fluke / old bug, I erased the index and upgraded Dovecot, first to 1.0.10, then to 1.1.beta14, but I'm still seeing the bug -- and it's even gotten worse! Earlier versions would just quietly split the message at the From_ line, but 1.1.beta14 is more diligent and will complain with: > dovecot[44795]: IMAP(lennart): FETCH for mailbox Drafts UID 196 got > too little data: 590 vs 719 before dropping the connection and exiting... which cause Thunderbird to reopen the connection and reissue the same request... which will cause Dovecot to complain and exit again... etc ad nauseam... It's trivial to reproduce too -- just mail yourself a message with a valid From_ line in it (assuming that your delivery system isn't doing >From-escaping), or put it in a draft plain text message and save it. Then go and look in your Drafts folder... (Like this one: "From someone Tue Jan 29 03:15:52 2008") Just be sure that you can stop your spinning mail client and/or server if you're using 1.1.beta14... --- OK, I am definitely not very familiar with the Dovecot source, but I spent some time trying to track this down today and it looks to me like i_stream_raw_mbox_read is being asked to find the end of the message (at the From_ line) before mbox_sync_parse_next_mail has had a chance to parse the Content-Length header and find out how big it is. Maybe someone who knows the code better can take a look at it and tell me if I'm barking up the totally wrong tree... Thanks, --Lennart

3 5

[Dovecot] Mailbox locking issue?
by Mark Sapiro 04 May '08

04 May '08

Here's my configuration. dovecot -n # 1.0.7: /usr/local/etc/dovecot.conf protocols: pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock The above setting was just added in an attempt to resolve the issue. It was default before. mail_executable: /usr/local/libexec/dovecot/pop3 mail_plugin_dir: /usr/local/lib/dovecot/pop3 pop3_uidl_format: %08Xu%08Xv auth default: mechanisms: plain apop login worker_max_count: 5 passdb: driver: passwd-file args: /usr/local/etc/dovecot.passwd passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix Postfix 2.3.3 mailbox_delivery_lock = fcntl, dotlock The problem is the following. A user uses fetchmail via an ssh tunnel to download mail via pop3 every 5 minutes. This normally works fine. perhaps once a week or so, maillog shows that Postfix delivers a message while fetchmail is retrieving. Here is one such. Apr 8 19:07:20 sbh16 dovecot: pop3-login: Login: user=<xxx>, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Apr 8 19:07:22 sbh16 postfix/local[13745]: D959169046B: to=xxx(a)example.com>, orig_to=<xxx(a)example.org>, relay=local, delay=16, delays=15/0/0/1.1, dsn=2.0.0, status=sent (delivered to mailbox) Apr 8 19:07:22 sbh16 dovecot: POP3(xxx): Disconnected: Logged out top=2/15995, retr=0/0, del=2/2, size=15985 Five minutes later when fetchmail comes back, we see Apr 8 19:12:42 sbh16 dovecot: POP3(xxx): mbox sync: Expunged message reappeared in mailbox /var/spool/mail/xxx (UID 4683 < 4684, seq=2, idx_msgs=0) Apr 8 19:12:42 sbh16 dovecot: pop3-login: Login: user=<xxx>, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Apr 8 19:12:46 sbh16 dovecot: POP3(xxx): mbox sync: UID inserted in the middle of mailbox /var/spool/mail/xxx (4684 > 4683, seq=2, idx_msgs=1) Apr 8 19:12:46 sbh16 dovecot: POP3(xxx): Disconnected: Logged out top=1/46375, retr=0/0, del=1/1, size=46365 >From now on, as messages are added to the mailbox by Postfix, fetchmail keeps retrieving both old and new messages. i.e. even though dovecot's log says del 1/1 (or del n/n) no messages are actually deleted from the mailbox. This situation continues until someone accesses the mailbox locally (e.g. via mutt through a local shell) and deletes the old messages. As noted above, this has been observed a few times with dovecot's default mbox_write_locks. I have since changed that to mbox_write_locks: fcntl dotlock to be consistent with Postfix's mailbox_delivery_lock = fcntl, dotlock I don't know if that will fix the problem or not, but it seems the issue with default dovecot mbox_write_locks should have been deadlock and time out rather than what we see. Also it seems that dovecot should recover from the 'corrupt' mailbox and fix it rather than just continuing to encounter the same problem. Any ideas or advice? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 4

[Dovecot] Sieve 1.1.2 -> special chars
by mikkel＠euro123.dk 04 May '08

04 May '08

I'm unable to use local chars in vacation/auto replies with sieve. .dovecot.sieve.err gives the same error as when there's a parse error. Example of error: line 25: string 'æ ø å ö ä ü é á. ': My dovecot is v. 1.1b5 and sieve is v. 1.1.2. This issue was also present with dovecot 1.0.x Is there a way around this? - Mikkel

3 2

[Dovecot] Quota not showing correctly after conversion (mb2md.pl)
by k bah 04 May '08

04 May '08

-- SCENARIO -- I'm using dovecot-1.0.5-6 on opensuse 10.3. I use the maildir quota plugin, and I'm converting mailboxes from UW IMAP (mbox) to Maildir format using that mb2md.pl script (3.10 I guess). My migration happens like this: - if a user receives mail (before ever using the new mail system), it goes to his/her inbox, dovecot proceeds normally, like when a user exists, but never received mails. Quota is shown ok. - if a user logs in before receiving any new mail, then, /var/spool/data/USER/new is created, and all converted messages are copied to that dir. If that user had deleted messages (some users mark messages as deleted, others delete for real), then a /var/spool/data/USER/.Trash/new dir is created, and messages are put there too. No other files/dirs (dovecot-uidlist maildirsize cur tmp), are created by "me" or the migration scripts. Index files (/var/spool/index/USER) are not created neither. They are created by dovecot itself. I have a problem, when a user has mails that exceed the limit in mb's (I set just size limit, no messages limit), neither "getquotaroot" (via telnet to port 143), neither webmail software (horde) show the quota usage correctly (I'm not talking about new mail, talking about those messages copied, when they exceed the size limit). Just after trying to delete messages it is shown (gives me an error message, quota exceeded, since Trash is not excluded from quota limits, for now, I'll exclude it later). This server has some issues: many old users have lots of mails, in thousands (1000-15000). Some have 50mb to 150mb of mails. The migration is part of the cleanup process. --- MY QUESTIONS --- Is it possible that the migration order (creating dirs in that way) is causing the quota usage to be shown wrong? Is it possible that the amount of messages and the size can be the cause? Misconfiguration? Other causes? How can I manually tell dovecot to recalculate the quota, after copying messages (when a user logs in, and didn't receive new mails on the new mail system, but had messages big enough to exceed the quota limit) from the old system? Should I run any commands to rebuild indexes or any operation to keep information integrity about the mails/mailboxes to dovecot, after copying the converted messages? many thanks = -- Powered by Outblaze

2 1

[Dovecot] Master user and missing folders
by Anders 04 May '08

04 May '08

Hello again. I am trying to use a master user. The login works. However, a LIST command gives me only the INBOX. Is this to be expected? When logging in normally, I do get the full list of folders. (using Dovecot 1.1 rc3.) Anders.

2 7

[Dovecot] Expire plugin isn't working
by Raphael Bittencourt S. Costa 04 May '08

04 May '08

Hello all, I followed the wiki to configured the expire plugin on dovecot-1.1rc4 and it isn't working. No error messages on logs or on the execution of "dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool". mailserver02:~ # dovecot -n # 1.1.rc4: /etc/dovecot//dovecot.conf syslog_facility: local1 protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no shutdown_clients: no login_dir: /usr//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_process_per_connection: no login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_process_size: 128 login_processes_count: 30 login_max_processes_count: 1024 login_max_connections: 512 max_mail_processes: 10240 mail_max_userip_connections(default): 20 mail_max_userip_connections(imap): 20 mail_max_userip_connections(pop3): 10 mail_uid: 1033 mail_gid: 1033 mail_location: maildir:%h/Maildir mail_executable(default): /usr//libexec/dovecot/imap mail_executable(imap): /usr//libexec/dovecot/imap mail_executable(pop3): /usr//libexec/dovecot/pop3 mail_plugins(default): expire quota imap_quota autocreate mail_plugins(imap): expire quota imap_quota autocreate mail_plugins(pop3): quota mail_plugin_dir(default): /usr//lib/dovecot/imap mail_plugin_dir(imap): /usr//lib/dovecot/imap mail_plugin_dir(pop3): /usr//lib/dovecot/pop3 pop3_no_flag_updates(default): no pop3_no_flag_updates(imap): no pop3_no_flag_updates(pop3): yes pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %f pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login cache_size: 20480 cache_ttl: 300 cache_negative_ttl: 0 passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: prefetch userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 438 plugin: quota: maildir quota_rule: *:bytes=10240 quota_rule2: *:messages=30000 autocreate: SPAM.E Spam autocreate2: SPAM.Marcar Spam autocreate3: SPAM autocreate4: SPAM.Desmarcar Spam expire: Trash 1 SPAM 10 SPAM/* 10 Sent 30 expire_dict: proxy::expire auth_socket_path: /var/run/dovecot/auth-master dict: expire: db:/usr/lib/dovecot/expidb/expire.db

3 13

[Dovecot] Fatal: Running as root isn't permitted
by Juan Asensio Sánchez 04 May '08

04 May '08

Hi! It compiles perfect now and works fine without returning the uid in the ldap query. What about the inclusion of the antispam and autocreate plugins in the (source) debian package? Thank you very much. 2008/5/4 Timo Sirainen <tss(a)iki.fi>: > On Sun, 2008-05-04 at 15:19 +0200, Juan Asensio Sánchez wrote: > > mech-gssapi.o: In function `gssapi_krb5_userok': > > /root/tmp/dovecot-1.1.rc4/src/auth/mech-gssapi.c:325: undefined > > reference to `krb5_get_error_message' > > This fixes it: http://hg.dovecot.org/dovecot-1.1/rev/ad0f32abda6d > >

1 0

[Dovecot] The CONTROL problem with fs quotas.
by Jorgen Lundman 04 May '08

04 May '08

dovecot-1.0.10 on Solaris 10 x86, with NFS. We currently have the problem that when customers go over their disk quota, the dovecot-uidlist file stops them from logging in. In the interest of solving it, we considered moving the CONTROL file to a different file system. But: 1: Using CONTROL= with "%u" will quite quickly run into the problem that the directory will fill up, and hit the maximum (around 32k) or so. We have 170k users so far, and more are being imported. You could cull some from crontab or similar, but is generally a poor way to solve a problem. 2: We attempted to use CONTROL= with "%h", which would give us full directory hashing, however, we found that when it creates all the directories, it does so as the uid of the first user. So all following users (that hash in at least one part) will fail. Most likely because dovecot has already setuid()ed. Pre-creating the hashes is not feasible. 3: Using 2, we could change umask to "0000" and hence it does not matter than all directory hash node are owned by a user's id, but this unfortunately includes all other directories, and having all directories at 777 is not an option. Now, naturally, I can easily patch dovecot to call mkdir_parents with 0777 only for CONTROL. But I would rather not have local patches, meaning upgrades will be difficult. It would be preferable if: => Dovecot would call "mkdir_parents" on "%h" _before_ setuid, but create the final directory after. OR, Dovecot support (at least 2 level) directory hashing when specifying CONTROL=%1/%2/%u OR, The ability to disable dovecot-uidlist (in memory is fine). (Setting INDEX=memory does not work for CONTROL=). Are there other solutions out there? -- Jorgen Lundman | <lundman(a)lundman.net> Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work) Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell) Japan | +81 (0)3 -3375-1767 (home)

2 2

[Dovecot] Fatal: Running as root isn't permitted
by Juan Asensio Sánchez 04 May '08

04 May '08

Hi I am running Dovecot 1.1RC4, built from the source packages at the debian repositories (http://xi.rename-it.nl/debian/) When a message is delivered through the LDA, i get this error: deliver(******@*****): May 02 14:43:28 Fatal: Running as root isn't permitted These are my config files: master.cf: ======================================= # Dovecot dovecot unix - n n - - pipe flags=DRhu user=dovecot:mail argv=/usr/lib/dovecot/deliver -d $recipient ======================================= dovecot.conf ======================================= protocols = imap pop3 listen = 0.0.0.0 login_greeting = Servidor de correo para preparado. disable_plaintext_auth = no log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot-info.log mail_uid = mailuser mail_gid = mailgroup # IMAP configuration protocol imap { mail_plugins = quota imap_quota } # POP3 configuration protocol pop3 { pop3_uidl_format = %08Xu%08Xv mail_plugins = quota } # LDA configuration protocol lda { log_path = /var/log/dovecot-lda.log postmaster_address = postmaster auth_socket_path = /var/run/dovecot/auth-master mail_plugins = quota cmusieve global_script_path = /home/vmail/globalsievesrc } # LDAP authentication auth default { mechanisms = plain login passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = dovecot group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } ======================================= dovecot-ldap.conf ======================================= hosts = 127.0.0.1 auth_bind = yes ldap_version = 3 base = dc=*******,dc=local scope = subtree user_attrs = =home=/var/vmail/%d/%n,mailuserquota=quota=maildir:storage,=mail=maildir:/var/vmail/%d/%n/Maildir user_filter = (&(objectClass=mailAccount)(mail=%u)(mailenable=OK)) pass_attrs = mail=user,userPassword=password pass_filter = (&(objectClass=mailAccount)(mail=%u)(mailenable=OK)) default_pass_scheme = CRYPT ======================================= The folder /var/vmail has these permissions: pdc-server:~# ls -la /var/vmail/ total 16 drwxrwx--- 3 mailuser mailgroup 4096 2008-05-02 14:34 . drwxr-xr-x 16 root root 4096 2008-05-02 14:14 .. Any idea? Thanks in advance.

2 4

[Dovecot] used_file_size too large
by Anders 04 May '08

04 May '08

Hi. Just got this error (1.1.rc4), is it something to worry about? Corrupted index cache file /.../Maildir/.Sent/dovecot.index.cache: used_file_size too large This is a shared mailbox with concurrent access. In general, can that usage pattern mess up the index? I am guessing "no", which is why I worry slightly about the warning. Cheers, Anders.

2 5

[Dovecot] Can't receive mail for virtual user
by Jeremy Gillick 04 May '08

04 May '08

I followed the dovecot instructions ( http://wiki.dovecot.org/HowTo/SimpleVirtualInstall) to create a simple virtual user installation with the /etc/dovecot/passwd file. However, whenever I try to send a message to the virtual user, Postfix has a problem delivering it. Postfix is delivering messages to ~/Maildir, but Dovecot is trying to use /home/vmail/. How can I get the 2 apps to work together? I've set up SASL, SSL and Dovecot LDA. Dovecot version: 1.0.13 (from source) Postfix version: 2.5.1 (from source) OS: Fedora Core 4 Here's are my config files: DOVECOT # 1.0.13: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log protocols: imap pop3 imaps pop3s disable_plaintext_auth: no verbose_ssl: yes login_dir: /usr/local/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/local/libexec/dovecot/pop3-login mail_location: maildir:~/Maildir dotlock_use_excl: 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/local/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/local/lib/dovecot/pop3 pop3_uidl_format: %08Xu%08Xv auth default: mechanisms: plain login verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=postfix gid=postfix home=/home/vmail/%u socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /usr/local/var/run/dovecot/auth-master mode: 384 user: vmail ------ POSTFIX (main.cf) alias_maps = $alias_database broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 html_directory = no inet_interfaces = $myhostname, localhost mail_owner = postfix mailq_path = /usr/bin/mailq manpage_directory = /usr/local/man mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain mydomain = mixermixer3.com myhostname = mixermixer3.com newaliases_path = /usr/bin/newaliases queue_directory = /var/spool/postfix/ readme_directory = no relay_domains = $mydestination sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail setgid_group = postdrop smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_CAfile = /etc/postfix/ssl/smtpd.pem smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.pem smtpd_tls_key_file = /etc/postfix/ssl/smtpd.pem smtpd_tls_loglevel = 1 smtpd_tls_session_cache_timeout = 3600s unknown_local_recipient_reject_code = 550 virtual_mailbox_domains = mixermixer3.com virtual_transport = dovecot ------ POSTFIX (a few key lines from 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 # -o milter_macro_daemon_name=ORIGINATING smtp unix - - n - - smtp # Dovecot LDA dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} THANKS, Jeremy

2 1

[Dovecot] Client can't connect to SMTP
by Jeremy Gillick 04 May '08

04 May '08

I've just installed Dovecot and Postfix and my email client (Mac Mail) cannot authenticate with the SMTP server. The error I receive says that "The SMTP server doesn't support SSL (TLS) on port 465" -- yet, I've installed SSL. Is there any good way to test or debug this? Setup: * SSL * Dovecot SASL * Dovecot LDA * Virtual Users (http://wiki.dovecot.org/HowTo/SimpleVirtualInstall) Client SMTP Setup: * Use SSL * Port: 465 * Authentication: Password By the way, I followed these instructions: http://wiki.dovecot.org/HowTo/SimpleVirtualInstall Dovecot version: 1.0.13 (from source) Postfix version: 2.5.1 (from source) OS: Fedora Core 4 Here's are my config files: DOVECOT # 1.0.13: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log protocols: imap pop3 imaps pop3s disable_plaintext_auth: no verbose_ssl: yes login_dir: /usr/local/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/local/libexec/dovecot/pop3-login mail_location: maildir:~/Maildir dotlock_use_excl: 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/local/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/local/lib/dovecot/pop3 pop3_uidl_format: %08Xu%08Xv auth default: mechanisms: plain login verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=postfix gid=postfix home=/home/vmail/%u socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /usr/local/var/run/dovecot/auth-master mode: 384 user: vmail ------ POSTFIX (main.cf) alias_maps = $alias_database broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 html_directory = no inet_interfaces = $myhostname, localhost mail_owner = postfix mailq_path = /usr/bin/mailq manpage_directory = /usr/local/man mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain mydomain = mixermixer3.com myhostname = mixermixer3.com newaliases_path = /usr/bin/newaliases queue_directory = /var/spool/postfix/ readme_directory = no relay_domains = $mydestination sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail setgid_group = postdrop smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_CAfile = /etc/postfix/ssl/smtpd.pem smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.pem smtpd_tls_key_file = /etc/postfix/ssl/smtpd.pem smtpd_tls_loglevel = 1 smtpd_tls_session_cache_timeout = 3600s unknown_local_recipient_reject_code = 550 virtual_mailbox_domains = mixermixer3.com virtual_transport = dovecot ------ POSTFIX (a few key lines from 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 # -o milter_macro_daemon_name=ORIGINATING smtp unix - - n - - smtp # Dovecot LDA dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} THANKS, Jeremy

2 1

[Dovecot] Dovecot 1.1: Ignoring Trash/Junk for maildirsize?
by richs＠whidbey.net 04 May '08

04 May '08

Hi all, We're testing Dovecot 1.1rc3, but have run into a snag with IMAP Quota's and the way Trash and Junk folders can be handled. Our MTA (Exim) quota configuration uses this option: maildir_quota_directory_regex = ^(?:cur|new|\.(?!Junk$)(?!Trash$).*)$ This completely excludes "Junk" and "Trash" from the "maildirsize" file and quota calculations. Dovecot 1.0 could do this using "ignore=Trash" (although only on one folder). Is there any way to duplicate this behavior in Dovecot 1.1? We see that "quota_rule" can be used to set an unlimited quota (storage=0), but for some reason Dovecot still records their tallies in "maildirsize", which breaks the MTA. Thanks! -Rich

2 1

[Dovecot] Cross-Realm Krb5 Patch
by Zachary Kotlarek 04 May '08

04 May '08

I've updated my krb5 cross-realm auth patch for dovecot 1.1-rc4; there are not any (intentional) changes in functionality from the last patch, the diff just didn't apply cleanly anymore. As before the most recent version of the patch is available at: http://zinux.cynicbytrade.com/svn/servers/dovecot/cross-realm.diff.bz2 I see the cross-realm patch for Solaris made it into the mainline. What if anything can I do to encourage the mainline adoption of my non- Solaris patch? Zach

2 1

[Dovecot] Patch for zlib and maildir for 1.0.13
by Richard Platel 04 May '08

04 May '08

When using the zlib plugin with maildir and copying with hardlinks, if a compressed message is copied, the 'Z' suffix on the file isn't copied, so the new message isn't uncompressed when it's fetched. I wasn't smart enough to figure out a clean way to carry a file suffix through a copy, so I changed how the zlib-plugin detects if a message is compressed. This patch peeks at the first two bytes of the message looking for the zlib header. -- Richard Platel Tucows

3 3

[Dovecot] 1.1rc4 problem with maildir++ quota and POP3
by Laurent Papier 04 May '08

04 May '08

Hi, it looks like there is a bug (in dovecot or in my config) with quota on maildir mailboxes when accessed via POP3. The maildirsize is not created when not already present (even after a DELE + QUIT command). The quota limit (the first line of maildirsize) is not updated if values are not in sync with those in the database. If maildirsize is present, DELE commands are correctly reported in maildirsize. maildirsize is correctly updated when the same mailbox is accessed in IMAP or mail is delivered with dovecot LDA. Here is my config. Timo 'dovecot -n' does not show the lda config part... # 1.1.rc4: /etc/dovecot.conf protocols: imap pop3 ssl_disable: yes 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: please to meet you login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_processes_count: 100 login_max_processes_count: 512 max_mail_processes: 3072 mail_uid: 1000 mail_gid: 1000 mail_location: maildir:~/ mmap_disable: yes maildir_stat_dirs: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): imap_quota quota mail_plugins(imap): imap_quota quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls auth default: user: nobody passdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: prefetch socket: type: listen master: path: /var/run/dovecot/auth-master mode: 432 user: mailonly group: mailonly plugin: quota: maildir quota_rule2: Trash:storage=12288:messages=100 --- SQL queries ---- # prefetch auth password_query = SELECT cpasswd as password, home as userdb_home, concat('*:bytes=',quotas,':messages=',quotai) AS userdb_quota_rule FROM `mail` WHERE email='%u' # for delivery user_query = SELECT home, concat('*:bytes=',quotas,':messages=',quotai) AS quota_rule FROM `mail` WHERE email='%u' -- Laurent Papier - 03 88 75 80 50 Admin. système - SdV Plurimedia - <http://www.sdv.fr/>

2 1

[Dovecot] Global and personal sieve scripts
by Juan Asensio Sánchez 04 May '08

04 May '08

Hi According to Dovecot documentation (): # If there is no user-specific Sieve-script, global Sieve script is # executed if set. (v1.0.1 and older used "global_script_path") #sieve_global_path = Then, if one user has its own script, the global script won't be executed? I would like to execute first the global script (for moving SPAM to the Junk folder), and then the user scripts is they exists. Any idea? Thanks in advance.

2 1

[Dovecot] GETQUOTAROOT?
by Ralf Hildebrandt 04 May '08

04 May '08

All over a sudden the getquota plugin in SquirrelMail doesn't work anymore. I activated debugging an got: IMAP command sent: a001 GETQUOTAROOT "INBOX" IMAP response received: Array ( [0] => * QUOTAROOT "INBOX" "" [1] => * QUOTA "" () ) A manual test results in: . GETQUOTAROOT "INBOX" * QUOTAROOT "INBOX" "" * QUOTA "" () . OK Getquotaroot completed. But that mailbox DOES have a quota defined. This is dovecot-1.0.x from the Mercurial repo. I'm using: quota = maildir quota = maildir:ignore=Trash quota_warning = storage=10%% /usr/local/scripts/quota-warning 90 quota_warning2 = storage=5%% /usr/local/scripts/quota-warning 95 quota_warning3 = storage=1%% /usr/local/scripts/quota-warning 99 which works fine otherwise. -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) snickebo(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de In brightest day, in blackest night no evil shall escape my sight!

2 4

[Dovecot] [patch] let valgrind run on login process with GDB=1
by Diego Liziero 04 May '08

04 May '08

Not sure if this should be included in dovecot, just posting if someone feels like using valgrind. Diego. ----- diff -r ba634d2c0ab9 src/master/login-process.c --- a/src/master/login-process.c Wed Apr 30 20:18:37 2008 +0300 +++ b/src/master/login-process.c Thu May 01 00:59:10 2008 +0200 @@ -689,7 +689,8 @@ static pid_t create_login_process(struct fd_limit = 16 + listen_count + ssl_listen_count + 2 * (group->set->login_process_per_connection ? 1 : group->set->login_max_connections); - restrict_fd_limit(fd_limit); + if (getenv("GDB") == NULL) + restrict_fd_limit(fd_limit); /* make sure we don't leak syslog fd, but do it last so that any errors above will be logged */

2 1

[Dovecot] Need Help! (Bug Report)
by 이경준 04 May '08

04 May '08

Need Help!! Server : AIX 5.3 Compile Error Message configure --------------------------------- checking jfs/quota.h usability... no checking jfs/quota.h presence... yes configure: WARNING: jfs/quota.h: present but cannot be compiled configure: WARNING: jfs/quota.h: check for missing prerequisite headers? configure: WARNING: jfs/quota.h: see the Autoconf documentation configure: WARNING: jfs/quota.h: section "Present But Cannot Be Compiled" configure: WARNING: jfs/quota.h: proceeding with the preprocessor's result configure: WARNING: jfs/quota.h: in the future, the compiler will take precedence configure: WARNING: ## ---------------------------------- ## configure: WARNING: ## Report this to dovecot(a)dovecot.org ## configure: WARNING: ## ---------------------------------- ## checking for jfs/quota.h... yes checking mntent.h usability... yes make -------------------------- et/libcharset.a ../../../src/lib/liblib.a -liconv + exec /usr/vacpp/bin/xlc -g -bexpall -brtl -o convert-tool convert-tool.o ./../../src/lib-storage/register/libstorage-register.a ../../../src/lib- storage/index/maildir/libstorage_maildir.a ../../../src/lib- storage/index/mbox/libstorage_mbox.a ../../../src/lib- storage/index/libstorage_index.a ../../../src/lib-index/libindex.a ./../../src/lib-storage/libstorage.a ../../../src/lib-storage/subscription- file/libstorage_subscription_file.a ../../../src/lib-imap/libimap.a ../../.. /src/lib-mail/libmail.a ../../../src/lib-charset/libcharset.a ./../../src/lib/liblib.a -liconv -bE:.libs/libstorage-register.exp - bE:.libs/libstorage_maildir.exp -bE:.libs/libstorage_mbox.exp - bE:.libs/libstorage_index.exp -bE:.libs/libindex.exp - bE:.libs/libstorage.exp -bE:.libs/libstorage_subscription_file.exp - bE:.libs/libimap.exp -bE:.libs/libmail.exp -bE:.libs/libcharset.exp - bE:.libs/liblib.exp Target "all" is up to date. Making all in quota source='quota.c' object='quota.lo' libtool=yes DEPDIR=.deps depmode=aix /bin/sh ../../../depcomp /bin/sh ../../../libtool --tag=CC -- mode=compile /apps1/bea8/domains/eipDomain/handy/down/dovecot/imap/dovecot- 1.0.13/dovecot-cc -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 -g -c -o quota.lo quota.c mkdir .libs /apps1/bea8/domains/eipDomain/handy/down/dovecot/imap/dovecot- 1.0.13/dovecot-cc -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 -g -c -M quota.c -DPIC -o .libs/quota.o + exec /usr/vacpp/bin/xlc -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 -g -c -M quota.c - DPIC -o .libs/quota.o "/usr/include/sys/ras.h", line 273.49: 1506-207 (W) Integer constant 0x5200000000000110ul out of range. "/usr/include/sys/ras.h", line 273.1: 1506-195 (S) Integral constant expression with a value greater than zero is required. "/usr/include/sys/ras.h", line 276.49: 1506-207 (W) Integer constant 0x5200000000000210ul out of range. "/usr/include/sys/ras.h", line 276.1: 1506-195 (S) Integral constant expression with a value greater than zero is required. "/usr/include/sys/ras.h", line 279.49: 1506-207 (W) Integer constant 0x5200000000000310ul out of range. "/usr/include/sys/ras.h", line 279.1: 1506-195 (S) Integral constant expression with a value greater than zero is required. "/usr/include/sys/ras.h", line 283.49: 1506-207 (W) Integer constant 0x5200000000000120ul out of range. "/usr/include/sys/ras.h", line 283.1: 1506-195 (S) Integral constant expression with a value greater than zero is required. "/usr/include/sys/ras.h", line 286.49: 1506-207 (W) Integer constant 0x5200000000000220ul out of range. "/usr/include/sys/ras.h", line 286.1: 1506-195 (S) Integral constant expression with a value greater than zero is required. "/usr/include/sys/ras.h", line 289.49: 1506-207 (W) Integer constant 0x5200000000000320ul out of range. "/usr/include/sys/ras.h", line 289.1: 1506-195 (S) Integral constant expression with a value greater than zero is required. make: 1254-004 The error code from the last command is 1. Stop. make: 1254-004 The error code from the last command is 1. Stop. make: 1254-004 The error code from the last command is 1. Stop. make: 1254-004 The error code from the last command is 1. Stop. make: 1254-004 The error code from the last command is 2.

2 1

[Dovecot] deliver: handling of quota_full_tempfail and -e
by Ulrich Zehl 04 May '08

04 May '08

Hi, while testing out dovecot 1.1, I found that when you set quota_full_tempfail = yes in dovecot.conf and use the deliver -e command line flag, no deferral reason is printed, thus breaking my fancy quota_exceeded_message. This appears to be because of the if() block in lines 1003-1009 in src/deliver/deliver.c, and should be easily fixable (if it is indeed a bug, and not intended behavior). However, I shied away from creating a patch because either there is a mismatch between the documentation and deliver's actual behavior, or I misunderstood the code (likely, since I'm not really a C programmer). The lines in question (in src/deliver/deliver.c) read: | 1003 if (error != MAIL_ERROR_NOSPACE || | 1004 getenv("QUOTA_FULL_TEMPFAIL") != NULL) { Does this mean that the corresponding block gets executed whenever quota_full_tempfail is set? If so, setting it transforms all errors into TEMPFAILs, and not only those relating to quota/space issues. I think dovecot-example.conf should at least mention this it's inteded; otherwise, the code should be changed (I'm not completely sure what Timo's intensions are, so I won't comment on possible solutions). Regards, Ulrich PS: All line numbers are taken from rev 080dd4d2fd94, which was the most recent at the time of writing.

4 3

[Dovecot] Replication protocol design
by Timo Sirainen 03 May '08

03 May '08

I'll probably be implementing multi-master replication this summer. My previous thoughts about it are here: http://dovecot.org/list/dovecot/2007-December/027284.html Below is a description of how the replication protocol will probably work. It should work just as well for master-slave and multi-master setups. Comments welcome. I'll write later a separate mail about how it'll be implemented to Dovecot. Goals ----- 1. If a single (or configurable number of) server dies, no mails must be lost that have been reported to IMAP/SMTP clients as being successfully stored. 2. Must be able to automatically recover from a server desynchronization, such as: - server has been offline for a long time - some mail files have been manually added/deleted - corrupted data/mail files if they're noticed 3. In multi-master setup if the link between servers die, the servers must be able to proceed autonomously (kind of conflicts with goal 1 though). When the link comes back, the changes are replicated as soon as possible. 4. Normal IMAP commands must not be able to cause desynchronization between servers. For example making conflicting flag changes simultaneously in two servers must not result in the servers having different flags. 5. Must perform well with at least 3 servers in a multi-master setup, preferrably still with tens of servers. 6. Latency shouldn't be increased noticeably when using servers distributed into 3 or more data centers. Must be usable over high-latency links (in optimistic async mode). 7. In normal operation send minimal incremental changes. Protocol -------- There are two major parts in the protocol: Handling the normal incremental changes and fixing desynchronization. Originally I thought that maybe the changes could be sent using the same format as Dovecot's transaction logs, but now I'm beginning to think that it's probably not that good idea. The code reuse potential is quite minimal and the format would still have to be extended in several ways so that it won't be directly compatible anyway. So I'm thinking the protocol could be something text-based. The main benefit is that text-based protocols are easier to debug. Stream compression should drop most of the extra overhead if bandwidth is a problem. The exact on-wire protocol anyway doesn't matter in the design that's discussed below. The commands have tags similar to IMAP commands, because some commands may have to be forwarded to other servers and it may take a while to get a reply. During the wait the server may process other commands. Mailbox master -------------- Each mailbox has a single master server selected. In multi-master setups the master server may be moved by having the destination server simply request it from the current master. The current master must then give it up. If link is lost to the current master, one of the remaining servers will become the new master within the remaining servers. Each server must be connected to the current master server. Since each mailbox can have a different master server, this typically means all servers are connected to each others. However it's possible to create setups where server connects to only one other server, which in turn connect to more servers. This is useful if there are bandwidth bottlenecks between some servers. This kind of a situation can also happen if in a network A-B-C the link A-C dies, but A-B and B-C continues to work. Because of this all commands must be able to function in a way that the server proxies them to the current master, instead of failing the command and trying to make it the caller's problem to resend the command to the actual master. When the cluster starts up, a single server is selected as the root master for all mailboxes. If a server doesn't know who the current mailbox master is, it asks from the root. All servers cache the currently known mailbox masters to avoid constant requests to the root. If the root server dies, another server is selected as the root. Because the new root doesn't know what masters have been requested (and asking all of them from all servers would just waste bandwidth), all the servers are expected to flush their master caches and drop their own master status. The new root doesn't respond to any requests before all servers have notified that they've dropped being a master. The master status doesn't have to be at mailbox level granularity. It could just as well be configured to move at user, domain or even global level. Perhaps this could be done dynamically, so that higher granularity is used when the master is beginning to change too often between servers. Mailbox ID ---------- Mailbox IDs are session-specific numbers dynamically assigned for user+mailbox+UIDVALIDITY combinations. All connections have different mailbox IDs. Also send and receive directions have different IDs. This allows the sender to easily replace existing IDs to point to new mailboxes without causing any confusion. MBOX: - Mailbox ID - User name - Mailbox name - Mailbox UIDVALIDITY - Mailbox UIDNEXT - Mailbox message count If the receiver finds out it has a different UIDVALIDITY, the mailbox requires a full resync. Message count and UIDNEXT may also be used to determine if replication servers are out of sync. Requesting master status ------------------------ MASTER-MOVE: - Mailbox ID - [Destination SID] (if forwarding) The command is sent to the last known master for the mailbox. The server will keep forwarding the command until it reaches the current master. During the forwarding other servers may want to request something from the master. These requests must be delayed by the forwarding servers until the move is finished. Saving messages --------------- SAVE: - Mailbox IDs - Received date - [IMAP UID] (only if we're the master) - Global UID (stays the same when copying the message) - Message text Reply: - [IMAP UID] (only if not specified in parameters) - [Current mailbox master SID] (if it was moved) If current server is not the master, the SAVE is sent to the master which gives the message its UID. The master server then replicates the message to other servers with the UID parameter set. The mailbox master may have already changed by the time server receives a save request. If server receives a SAVE without IMAP UID parameter, it's responsible for finding out the new mailbox master and sending a new SAVE request to it. Once the new master replies with the IMAP UID, the server can reply to the original SAVE request, also providing the new master SID so the future requests can be sent there directly. To be sure the message doesn't get lost, the server should not reply OK to the IMAP/SMTP client until it has received a reply from SAVE. Copying messages ---------------- COPY: - Source mailbox ID - Destination mailbox ID - Source IMAP UID - Global UID - [Destination IMAP UID] (only if we're the master) - Destination received date Reply: - [Destination IMAP UID] (only if not specified in parameters) - [Current mailbox master SID] (if it was moved) Source mailbox ID + source IMAP UID identifies the message to be copied. It's expected to contain the given global UID (which is just an extra sanity check). Otherwise it works the same way as SAVE. Since the message already exists, it's probably not necessary to wait for a reply before replying OK to originating IMAP client. Expunging messages ------------------ EXPUNGE: - Mailbox ID - UID range (No reply) Expunges also have to be sent via master server (the same way as SAVE) to avoid COPY command failing in some servers because it was just expunged. Changing message flags ---------------------- STORE: - Mailbox ID - UID range - Added flags/keywords - Removed flags/keywords - [Current modseq] (master sends) - [Highest modseq of the messages before this change] (non-master sends) - [flag: this is a CONDSTORE STORE UNCHANGEDSINCE] (non-master may send) [Reply: - UIDs where STORE was rejected to (if CONDSTORE flag was used) ] Stores also have to be sent via master server to avoid flag desynchronization. Master first checks if it has higher modseqs in the messages. Then it applies all the changes and forwards the changes to other servers. For messages that had higher initial modseqs their flags are sent to the server sending the STORE to fix a potential desync. If CONDSTORE flag is set, the change is rejected for messages that had a higher modseq. Non-masters shouldn't reply to a STORE UNCHANGEDSINCE command before the change has been replicated to master and the rejections have been processed. Mailbox synchronization ----------------------- If a mailbox is determined to have changed externally (e.g. network connection down for too long, causing replication logs to get full) the mailbox state needs to be synchronized between servers. SYNC: - UIDVALIDITY - UIDNEXT - Message count - For each message: - UID - Global UID - Modseq - Flags and keywords - Received date Reply: - (Sync finished) Receiving server compares the parameters with its own mailbox state. If it finds previously unseen global UIDs, their message texts are requested: FETCH: - Mailbox ID - UID Reply: - Message text SAVE, EXPUNGE and STORE commands are used to synchronize the mailbox. A special case is when two servers have been saving messages independently from each others. In this case it's possible that the servers have used the same UIDs for different messages (different global UIDs). These need to be resolved by giving both conflicting UIDs new unused UIDs, otherwise IMAP clients may show them as wrong messages from their caches. FIXME: If the other server had expunged a conflicting UID it still should be given a new UID. How do we find out this has happened?

4 13

[Dovecot] 1.1rc4 file-offset-size unsupported?
by David Jonas 03 May '08

03 May '08

Is --with-file-offset-size no longer supported in 1.1? # ./configure \ --prefix=/usr/local/dovecot-1.1 \ --with-mysql \ --with-file-offset-size=32 \ --with-ioloop=best \ --with-pop3d \ --with-ssl \ --with-deliver \ ... checking for _FILE_OFFSET_BITS value needed for large files... 64 ... Install prefix ...................... : /usr/local/dovecot-1.1 File offsets ........................ : 64bit I/O loop method ..................... : epoll File change notification method ..... : dnotify Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : yes Building with pop3 server ........... : yes Building with mail delivery agent .. : yes Building with GSSAPI support ........ : no Building with user database modules . : static prefetch passwd passwd-file checkpassword sql nss Building with password lookup modules : passwd passwd-file shadow pam checkpassword sql Building with SQL drivers ............: mysql # cat /etc/redhat-release Red Hat Enterprise Linux ES release 4 (Nahant Update 6) # uname -r 2.6.9-42.0.10.ELsmp

2 2

[Dovecot] (no subject)
by Chris Beech 02 May '08

02 May '08

I'm trying to set up a pop3 server for a project for class, but it keeps giving me the following error: Error: Login user doesn't exist: dovecot Fatal: Invalid configuration in /usr/local/etc/dovecot.conf And I have no clue what's wrong. I've look and modifying the dovecot.conffile for days and I am not having any luck. ## Dovecot configuration file # If you're in a hurry, see http://wiki.dovecot.org/QuickConfiguration # "dovecot -n" command gives a clean output of the changed settings. Use it # instead of copy&pasting this file when posting to the Dovecot mailing list. # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown for each setting, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples with # the real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. base_dir = /var/run/dovecot/ # Protocols we want to be serving: imap imaps pop3 pop3s # If you only want to use dovecot-auth, you can set this to "none". protocols = imap imaps pop3 pop3s # A space separated list of IP or host addresses where to listen in for # connections. "*" listens in all IPv4 interfaces. "[::]" listens in all IPv6 # interfaces, but may also listen in all IPv4 interfaces depending on the # operating system. Use "*, [::]" for listening both IPv4 and IPv6. # # If you want to specify ports for each service, you will need to configure # these settings inside the protocol imap/pop3 { ... } section, so you can # specify different ports for IMAP/POP3. For example: # protocol imap { # listen = *:10143 # ssl_listen = *:10943 # .. # } # protocol pop3 { # listen = *:10100 # .. # } listen = *:143 # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that if the remote IP # matches the local IP (ie. you're connecting from the same computer), the # connection is considered secure and plaintext authentication is allowed. disable_plaintext_auth = no # Should all IMAP and POP3 processes be killed when Dovecot master process # shuts down. Setting this to "no" means that Dovecot can be upgraded without # forcing existing client connections to close (although that could also be # a problem if the upgrade is eg. because of a security fix). This however # means that after master process has died, the client processes can't write # to log files anymore. #shutdown_clients = yes ## ## Logging ## # Log file to use for error messages, instead of sending them to syslog. # /dev/stderr can be used to log into stderr. log_path = /var/log/dovecot.log # Log file to use for informational and debug messages. # Default is the same as log_path. info_log_path = /var/log/dovecot-info.log # Prefix for each line written to log file. % codes are in strftime(3) # format. log_timestamp = "%b %d %H:%M:%S " # Syslog facility to use if you're logging to syslog. Usually if you don't # want to use "mail", you'll use local0..local7. Also other standard # facilities are supported. #syslog_facility = mail ## ## SSL settings ## # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. ssl_disable = yes # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # If key file is password protected, give the password here. Alternatively # give it when starting dovecot with -p parameter. #ssl_key_password = # File containing trusted SSL certificate authorities. Set this only if you # intend to use ssl_verify_client_cert=yes. The CAfile should contain the # CA-certificate(s) followed by the matching CRL(s). #ssl_ca_file = # Request client to send a certificate. If you also want to require it, set # ssl_require_client_cert=yes in auth section. #ssl_verify_client_cert = no # Which field from certificate to use for username. commonName and # x500UniqueIdentifier are the usual choices. You'll also need to set # ssl_username_from_cert=yes. #ssl_cert_username_field = commonName # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 168 # SSL ciphers to use #ssl_cipher_list = ALL:!LOW:!SSLv2 # Show protocol level SSL errors. #verbose_ssl = no ## ## Login processes ## # <doc/wiki/LoginProcess.txt> # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = usr/local/var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. <doc/wiki/Rootless.txt> login_chroot = yes # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. <doc/wiki/UserIds.txt> login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 64 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to keep for listening new connections. #login_processes_count = 3 # Maximum number of login processes to create. The listening process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until the limit set by # this setting is reached. #login_max_processes_count = 128 # Maximum number of connections allowed per each login process. This setting # is used only if login_process_per_connection=no. Once the limit is reached, # the process notifies master so that it can create a new login process. #login_max_connections = 256 # Greeting message for clients. #login_greeting = Shall we play a game??? # Space-separated list of elements we want to log. The elements which have # a non-empty variable value are joined together to form a comma-separated # string. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. login_log_format = %$: %s ## ## Mailbox locations and namespaces ## # Location for users' mailboxes. This is the same as the old default_mail_env # setting. The default is empty, which means that Dovecot tries to find the # mailboxes automatically. This won't work if the user doesn't have any mail # yet, so you should explicitly tell Dovecot the full location. # # If you're using mbox, giving a path to the INBOX file (eg. /var/mail/%u) # isn't enough. You'll also need to tell Dovecot where the other mailboxes are # kept. This is called the "root mail directory", and it must be the first # path given in the mail_location setting. # # There are a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if there's no domain # %h - home directory # # See doc/wiki/Variables.txt for full list. Some examples: # # mail_location = maildir:~/Maildir # mail_location = mbox:~/mail:INBOX=/var/mail/%u # mail_location = mbox:/var/mail/%d/%1n/%n:INDEX=/var/indexes/%d/%1n/%n # # <doc/wiki/MailLocation.txt> # mail_location = mbox:/var/empty:INBOX=/var/mail/%u:INDEX=MEMORY # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections. # NOTE: Namespaces currently work ONLY with IMAP! POP3 and LDA currently ignore # namespaces completely, they use only the mail_location setting. # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. mail_location does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. # The default however depends on the underlying mail storage format. #separator = # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # mail_location, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension. You'll most likely also want to set list=no. This is mostly # useful when converting from another server with different namespaces which # you want to deprecate but still keep working. For example you can create # hidden namespaces with prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes # Show the mailboxes under this namespace with LIST command. This makes the # namespace visible for clients that don't support NAMESPACE extension. #list = yes # Namespace handles its own subscriptions. If set to "no", the parent # namespace handles them (empty prefix should always have this as "yes") #subscriptions = yes #} # System user and group used to access mails. If you use multiple, userdb # can override these by returning uid or gid fields. You can use either numbers # or names. <doc/wiki/UserIds> #mail_uid = #mail_gid = # Group to enable temporarily for privileged operations. Currently this is # used only for creating mbox dotlock files when creation fails for INBOX. # Typically this is set to "mail" to give access to /var/mail. mail_privileged_group = mail # Grant access to these supplementary groups for mail processes. Typically # these are used to set up access to shared mailboxes. Note that it may be # dangerous to set these if users can create symlinks (e.g. if "mail" group is # set here, ln -s /var/mail ~/mail/var could allow a user to delete others' # mailboxes, or ln -s /secret/shared/box ~/mail/mybox would allow reading it). #mail_access_groups = # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no ## ## Mail processes ## # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. mail_debug = yes # Log prefix for mail processes. See doc/wiki/Variables.txt for list of # possible variables you can use. mail_log_prefix = "%Us(%u): " # Max. number of lines a mail process is allowed to log per second before it's # throttled. 0 means unlimited. Typically there's no need to change this # unless you're using mail_log plugin, which may log a lot. This setting is # ignored while mail_debug=yes to avoid pointless throttling. #mail_log_max_lines_per_sec = 10 # Don't use mmap() at all. This is required if you store indexes to shared # filesystems (NFS or clustered filesystem). #mmap_disable = no # Rely on O_EXCL to work when creating dotlock files. NFS supports O_EXCL # since version 3, so this should be safe to use nowadays by default. #dotlock_use_excl = yes # Don't use fsync() or fdatasync() calls. This makes the performance better # at the cost of potential data loss if the server (or the file server) # goes down. #fsync_disable = no # Mail storage exists in NFS. Set this to yes to make Dovecot flush NFS caches # whenever needed. If you're using only a single mail server this isn't needed. #mail_nfs_storage = no # Mail index files also exist in NFS. Setting this to yes requires # mmap_disable=yes and fsync_disable=no. #mail_nfs_index = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. NFS users: flock doesn't work, remember to change mmap_disable. #lock_method = fcntl # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). verbose_proctitle = yes # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. first_valid_uid = 1000 last_valid_uid = 5000 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. max_mail_processes = 2048 # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot, mail_chroot or auth chroot # settings. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. <doc/wiki/Chrooting.txt> #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. <doc/wiki/Chrooting.txt> #mail_chroot = ## ## Mailbox handling optimizations ## # The minimum number of mails in a mailbox before updates are done to cache # file. This allows optimizing Dovecot's behavior to do less disk writes at # the cost of more disk reads. #mail_cache_min_mail_count = 0 # When IDLE command is running, mailbox is checked once in a while to see if # there are any new mails or other changes. This setting defines the minimum # time in seconds to wait between those checks. Dovecot can also use dnotify, # inotify and kqueue to find out immediately when changes occur. #mailbox_idle_check_interval = 30 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. # Also note that if other software reads the mboxes/maildirs, they may handle # the extra CRs wrong and cause problems. #mail_save_crlf = no ## ## Maildir-specific settings ## # By default LIST command returns all entries in maildir beginning with a dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # When copying a message, do it with hard links whenever possible. This makes # the performance much better, and it's unlikely to have any side effects. #maildir_copy_with_hardlinks = yes # When copying a message, try to preserve the base filename. Only if the # destination mailbox already contains the same name (ie. the mail is being # copied there twice), a new name is given. The destination filename check is # done only by looking at dovecot-uidlist file, so if something outside # Dovecot does similar filename preserving copies, you may run into problems. # NOTE: This setting requires maildir_copy_with_hardlinks = yes to work. #maildir_copy_preserve_filename = no ## ## mbox-specific settings ## # Which locking methods to use for locking mbox. There are four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # dotlock_try: Same as dotlock, but if it fails because of permissions or # because there isn't enough disk space, just skip it. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 120 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. mbox_very_dirty_syncs = yes # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. mbox_lazy_writes = yes # If mbox size is smaller than this (in kilobytes), don't write index files. # If an index file already exists it's still read, just not updated. #mbox_min_index_size = n ## ## dbox-specific settings ## # Maximum dbox file size in kilobytes until it's rotated. #dbox_rotate_size = 2048 # Minimum dbox file size in kilobytes before it's rotated # (overrides dbox_rotate_days) #dbox_rotate_min_size = 16 # Maximum dbox file age in days until it's rotated. Day always begins from # midnight, so 1 = today, 2 = yesterday, etc. 0 = check disabled. #dbox_rotate_days = 0 ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/libexec/dovecot/imap-login # IMAP executable location. Changing this allows you to execute other # binaries before the imap process is executed. # # This would write rawlogs into ~/dovecot.rawlog/ directory: # mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap # # This would attach gdb into the imap process and write backtraces into # /tmp/gdbhelper.* files: # mail_executable = /usr/libexec/dovecot/gdbhelper /usr/libexec/dovecot/imap # #mail_executable = /usr/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Maximum number of IMAP connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. #mail_max_userip_connections = 10 # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # IMAP logout format string: # %i - total number of bytes read from client # %o - total number of bytes sent to client #imap_logout_format = bytes=%i/%o # Override the IMAP CAPABILITY response. #imap_capability = # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example OSX # Mail (<v2.1). Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. # tb-extra-mailbox-sep: # With mbox storage a mailbox can contain either mails or submailboxes, # but not both. Thunderbird separates these two by forcing server to # accept '/' suffix in mailbox names in subscriptions list. # The list is space-separated. #imap_client_workarounds = } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. login_executable = /usr/local/libexec/dovecot/pop3-login # POP3 executable location. See IMAP's mail_executable above for examples # how this could be changed. mail_executable = /usr/local/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. pop3_enable_last = no # If mail has X-UIDL header, use it as the mail's UIDL. #pop3_reuse_xuidl = no # Keep the mailbox locked for the entire POP3 session. #pop3_lock_session = no # POP3 UIDL (unique mail identifier) format to use. You can use following # variables, along with the variable modifiers described in # doc/wiki/Variables.txt (e.g. %Uf for the filename in uppercase) # # %v - Mailbox's IMAP UIDVALIDITY # %u - Mail's IMAP UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier : %f or %v-%u (both might be used simultaneosly) # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # Dovecot v0.99.x : %v.%u # tpop3d : %Mf # # 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. # pop3_uidl_format = %08Xu%08Xv # POP3 logout format string: # %i - total number of bytes read from client # %o - total number of bytes sent to client # %t - number of TOP commands # %p - number of bytes sent to client as a result of TOP command # %r - number of RETR commands # %b - number of bytes sent to client as a result of RETR command # %d - number of deleted messages # %m - number of messages (before deletion) # %s - mailbox size in bytes (before deletion) #pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s # Maximum number of POP3 connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. #mail_max_userip_connections = 3 # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. # The list is space-separated. #pop3_client_workarounds = } ## ## LDA specific settings ## protocol lda { # Address to use when sending rejection mails. postmaster_address = postmaster(a)example.com # Hostname to use in various parts of sent mails, eg. in Message-Id. # Default is the system's real hostname. #hostname = # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/lda # If user is over quota, return with temporary failure instead of # bouncing the mail. #quota_full_tempfail = no # Format to use for logging mail deliveries. You can use variables: # %$ - Delivery status message (e.g. "saved to INBOX") # %m - Message-ID # %s - Subject # %f - From address #deliver_log_format = msgid=%m: %$ # Binary to use for sending mails. #sendmail_path = /usr/lib/sendmail # Human readable error message for rejection mails. Use can use variables: # %n = CRLF, %r = reason, %s = subject, %t = recipient #rejection_reason = Your message to <%t> was automatically rejected:%n%r # UNIX socket path to master authentication server to find users. #auth_socket_path = /var/run/dovecot/auth-master } ## ## Authentication processes ## # Executable location auth_executable = /usr/local/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. auth_process_size = 256 # Authentication cache size in kilobytes. 0 means it's disabled. # Note that bsdauth, PAM and vpopmail require cache_key to be set for caching # to be used. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds the cached # record is no longer used, *except* if the main database lookup returns # internal failure. We also try to handle password changes automatically: If # user's previous authentication was successful, but this one wasn't, the # cache isn't used. For now this works only with plaintext authentication. auth_cache_ttl = 3600 # TTL for negative hits (user not found). 0 disables caching them completely. #auth_cache_negative_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username formatting before it's looked up from databases. You can use # the standard variables here, eg. %Lu would lowercase the username, %n would # drop away the domain if it was given, or "%n-AT-%d" would change the '@' into # "-AT-". This translation is done after auth_username_translation changes. #auth_username_format = # If you want to allow master users to log in by specifying the master # username within the normal username string (ie. not using SASL mechanism's # support for it), you can specify the separator character here. The format # is then <username><separator><master username>. UW-IMAP uses "*" as the # separator, so that could be a good choice. #auth_master_user_separator = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. #auth_verbose = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no # In case of password mismatches, log the passwords and used scheme so the # problem can be debugged. Requires auth_debug=yes to be set. #auth_debug_passwords = no # Maximum number of dovecot-auth worker processes. They're used to execute # blocking passdb and userdb queries (eg. MySQL and PAM). They're # automatically created and destroyed as needed. #auth_worker_max_count = 30 # Number of auth requests to handle before destroying the process. This may # be useful if PAM plugins leak memory. #auth_worker_max_request_count = 0 # Host name to use in GSSAPI principal names. The default is to use the # name returned by gethostname(). #auth_gssapi_hostname = # Kerberos keytab to use for the GSSAPI mechanism. Will use the system # default (usually /etc/krb5.keytab) if not specified. #auth_krb5_keytab = # Do NTLM authentication using Samba's winbind daemon and ntlm_auth helper. # <doc/wiki/Authentication/Mechanisms/Winbind.txt> #auth_ntlm_use_winbind = no # Path for Samba's ntlm_auth helper binary. #auth_winbind_helper_path = /usr/bin/ntlm_auth # Number of seconds to delay before replying to failed authentications. #auth_failure_delay = 2 auth default { # Space separated list of wanted authentication mechanisms: # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi otp skey # gss-spnego # NOTE: See also disable_plaintext_auth setting. mechanisms = plain # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # <doc/wiki/PasswordDatabase.txt> # # By adding master=yes setting inside a passdb you make the passdb a list # of "master users", who can log in as anyone else. Unless you're using PAM, # you probably still want the destination user to be looked up from passdb # that it really exists. This can be done by adding pass=yes setting to the # master passdb. <doc/wiki/Authentication.MasterUsers.txt> # Users can be temporarily disabled by adding a passdb with deny=yes. # If the user is found from that database, authentication will fail. # The deny passdb should always be specified before others, so it gets # checked first. Here's an example: #passdb passwd-file { # File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. # REMEMBER: You'll need /etc/pam.d/dovecot file created for PAM # authentication to actually work. <doc/wiki/PasswordDatabase.PAM.txt> passdb pam { # [session=yes] [setcred=yes] [failure_show_msg=yes] # [cache_key=<key>] [<service name>] # # session=yes makes Dovecot open and immediately close PAM session. Some # PAM plugins need this to work, such as pam_mkhomedir. # # setcred=yes makes Dovecot establish PAM credentials if some PAM plugins # need that. They aren't ever deleted though, so this isn't enabled by # default. # # cache_key can be used to enable authentication caching for PAM # (auth_cache_size also needs to be set). It isn't enabled by default # because PAM modules can do all kinds of checks besides checking password, # such as checking IP address. Dovecot can't know about these checks # without some help. cache_key is simply a list of variables (see # doc/wiki/Variables.txt) which must match for the cached data to be used. # Here are some examples: # %u - Username must match. Probably sufficient for most uses. # %u%r - Username and remote IP address must match. # %u%s - Username and service (ie. IMAP, POP3) must match. # # The service name can contain variables, for example %Ls expands to # pop3 or imap. # # Some examples: # args = session=yes %Ls # args = cache_key=%u dovecot #args = dovecot } # System users (NSS, /etc/passwd, or similiar) # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. <doc/wiki/AuthDatabase.Passwd.txt> passdb passwd { # [blocking=yes] - See userdb passwd for explanation #args = } # Shadow passwords for system users (NSS, /etc/shadow or similiar). # Deprecated by PAM nowadays. # <doc/wiki/PasswordDatabase.Shadow.txt> passdb shadow { # [blocking=yes] - See userdb passwd for explanation #args = } # PAM-like authentication for OpenBSD. # <doc/wiki/PasswordDatabase.BSDAuth.txt> #passdb bsdauth { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # passwd-like file with specified location # <doc/wiki/AuthDatabase.PasswdFile.txt> passdb passwd-file { # [scheme=<default password scheme>] [username_format=<format>] # <Path for passwd-file> driver = passwd-file args = /usr/local/etc/dovecot.passdb } # checkpassword executable authentication # NOTE: You will probably want to use "userdb prefetch" with this. # <doc/wiki/PasswordDatabase.CheckPassword.txt> #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database <doc/wiki/AuthDatabase.SQL.txt> #passdb sql { # Path for SQL configuration file, see doc/dovecot-sql-example.conf #args = #} # LDAP database <doc/wiki/AuthDatabase.LDAP.txt> #passdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap-example.conf #args = #} # vpopmail authentication <doc/wiki/AuthDatabase.VPopMail.txt> #passdb vpopmail { # [cache_key=<key>] - See cache_key in PAM for explanation. # [quota_template=<template>] - %q expands to Maildir++ quota # (eg. quota_template=quota_rule=*:backend=%q) #args = #} # # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # # <doc/wiki/UserDatabase.txt> # # System users (NSS, /etc/passwd, or similiar). In many systems nowadays this # uses Name Service Switch, which is configured in /etc/nsswitch.conf. # <doc/wiki/AuthDatabase.Passwd.txt> userdb passwd { # [blocking=yes] - By default the lookups are done in the main dovecot-auth # process. This setting causes the lookups to be done in auth worker # proceses. Useful with remote NSS lookups that may block. # NOTE: Be sure to use this setting with nss_ldap or users might get # logged in as each others! #user = root #args = } # passwd-like file with specified location # <doc/wiki/AuthDatabase.PasswdFile.txt> userdb passwd-file { # [username_format=<format>] <Path for passwd-file> driver = passwd-file args = /usr/local/etc/dovecot.passdb } # static settings generated from template <doc/wiki/UserDatabase.Static.txt> #userdb static { # Template for the fields. Can return anything a userdb could normally # return. For example: # # args = uid=500 gid=500 home=/var/mail/%u # # If you use deliver, it needs to look up users only from the userdb. This # of course doesn't work with static because there is no list of users. # Normally static userdb handles this by doing a passdb lookup. This works # with most passdbs, with PAM being the most notable exception. If you do # the user verification another way, you can add allow_all_users=yes to # the args in which case the passdb lookup is skipped. # #args = #} # SQL database <doc/wiki/AuthDatabase.SQL.txt> #userdb sql { # Path for SQL configuration file, see doc/dovecot-sql-example.conf #args = #} # LDAP database <doc/wiki/AuthDatabase.LDAP.txt> #userdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap-example.conf #args = #} # vpopmail <doc/wiki/AuthDatabase.VPopMail.txt> #userdb vpopmail { #} # "prefetch" user database means that the passdb already provided the # needed information and there's no need to do a separate userdb lookup. # This can be made to work with SQL and LDAP databases, see their example # configuration files for more information how to do it. # <doc/wiki/UserDatabase.Prefetch.txt> #userdb prefetch { #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. # Note that valid_chroot_dirs isn't needed to use this setting. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no # Take the username from client's SSL certificate, using # X509_NAME_get_text_by_NID() which returns the subject's DN's # CommonName. #ssl_username_from_cert = no # It's possible to export the authentication interface to other programs: socket listen { master { # Master socket provides access to userdb information. It's typically # used to give Dovecot's local delivery agent access to userdb so it # can find mailbox locations. path = /var/run/dovecot/auth-master mode = 0600 # Default user/group is the one who started dovecot-auth (root) user = dovecot group = mail } #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/run/dovecot/auth-client #mode = 0660 #} } } # If you wish to use another authentication server than dovecot-auth, you can # use connect sockets. They are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than the path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in the login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #} ## ## Dictionary server settings ## # Dictionary can be used by some plugins to store key=value lists. # Currently this is only used by dict quota backend. The dictionary can be # used either directly or though a dictionary server. The following dict block # maps dictionary names to URIs when the server is used. These can then be # referenced using URIs in format "proxy:<name>". dict { #quota = mysql:/etc/dovecot-dict-quota.conf } ## ## Plugin settings ## plugin { # Here you can give some extra environment variables to mail processes. # This is mostly meant for passing parameters to plugins. %variable # expansion is done for all values. # Quota plugin. Multiple backends are supported: # dirsize: Find and sum all the files found from mail directory. # Extremely SLOW with Maildir. It'll eat your CPU and disk I/O. # dict: Keep quota stored in dictionary (eg. SQL) # maildir: Maildir++ quota # fs: Read-only support for filesystem quota # # Quota limits are set using "quota_rule" parameters, either in here or in # userdb. It's also possible to give mailbox-specific limits, for example: # quota_rule = *:storage=1048576 # quota_rule2 = Trash:storage=102400 # User has now 1GB quota, but when saving to Trash mailbox the user gets # additional 100MB. # # Multiple quota roots are also possible, for example: # quota = dict:user::proxy::quota # quota2 = dict:domain:%d:proxy::quota_domain # quota_rule = *:storage=102400 # quota2_rule = *:storage=1048576 # Gives each user their own 100MB quota and one shared 1GB quota within # the domain. # # You can execute a given command when user exceeds a specified quota limit. # Each quota root has separate limits. Only the command for the first # exceeded limit is excecuted, so put the highest limit first. # Note that % needs to be escaped as %%, otherwise "% " expands to empty. # quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95 # quota_warning2 = storage=80%% /usr/local/bin/quota-warning.sh 80 #quota = maildir # ACL plugin. vfile backend reads ACLs from "dovecot-acl" file from maildir # directory. You can also optionally give a global ACL directory path where # ACLs are applied to all users' mailboxes. The global ACL directory contains # one file for each mailbox, eg. INBOX or sub.mailbox. cache_secs parameter # specifies how many seconds to wait between stat()ing dovecot-acl file # to see if it changed. #acl = vfile:/etc/dovecot-acls:cache_secs=300 # Convert plugin. If set, specifies the source storage path which is # converted to destination storage (mail_location) when the user logs in. # The existing mail directory is renamed to <dir>-converted. #convert_mail = mbox:%h/mail # Skip mailboxes which we can't open successfully instead of aborting. #convert_skip_broken_mailboxes = no # Skip directories beginning with '.' #convert_skip_dotdirs = no # If source storage has mailbox names with destination storage's hierarchy # separators, replace them with this character. #convert_alt_hierarchy_char = _ # Trash plugin. When saving a message would make user go over quota, this # plugin automatically deletes the oldest mails from configured mailboxes # until the message can be saved within quota limits. The configuration file # is a text file where each line is in format: <priority> <mailbox name> # Mails are first deleted in lowest -> highest priority number order #trash = /etc/dovecot-trash.conf # Expire plugin. Mails are expunged from mailboxes after being there the # configurable time. The first expiration date for each mailbox is stored in # a dictionary so it can be quickly determined which mailboxes contain # expired mails. The actual expunging is done in a nightly cronjob, which # you must set up: # dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool #expire = Trash 7 Spam 30 #expire_dict = db:/var/lib/dovecot/expire.db # Lazy expunge plugin. Currently works only with maildirs. When a user # expunges mails, the mails are moved to a mailbox in another namespace # (1st). When a mailbox is deleted, the mailbox is moved to another namespace # (2nd) as well. Also if the deleted mailbox had any expunged messages, # they're moved to a 3rd namespace. The mails won't be counted in quota, # and they're not deleted automatically (use a cronjob or something). #lazy_expunge = .EXPUNGED/ .DELETED/ .DELETED/.EXPUNGED/ # Events to log. Default is all. #mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename # 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 } And here's what's in the dovecot.passdb file Yoda:{PLAIN}littlegreenjedi:1001:1001:User 1 Name:/var/mail/folders/Yoda DVader:{PLAIN}DarkMaster:1002:1002: User 2 Name: /var/mail/folders/DVader HSolo:{PLAIN}Gokissawookiee:1003:1003: User 3 Name: /var/mail/folders/HSolo LSkywalker{PLAIN}Jediknight:1004:1004: User 4 Name: /var/mail/folders/LSkywalker Thanks for any help. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

3 2

Re: [Dovecot] FAQ: setting thunderbird to talk to dovecot
by Mauricio Tavares 02 May '08

02 May '08

On Fri, May 2, 2008 at 7:54 AM, Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > Is thunderbird set to use pop3 or imap? It can do both. I'd rather use imap but I am that kind of guy. ;) > Anyway, I don't support thunderbird as I have never used it, but I can tell > you how to connect to imap via telnet: > > telnet mail.thespider.com 143 > 1 login boris(a)mail.thespider.com creepycrawly > 1 logout > > You can see this: > http://www.macgeekery.com/tips/troubleshooting/troubleshooting_imap > This is what happened: [raub@yakko ~]$ telnet mail.thespider.com 143 Trying 192.168.1.12... Connected to mail.thespider.com (192.168.1.12). Escape character is '^]'. * OK dovecot ready. 1 login boris(a)mail.thespider.com creepycrawly 1 NO Authentication failed. 1 login boris(a)thespider.com creepycrawly 1 OK Logged in. 1 logout * BYE Logging out 1 OK Logout completed. Connection closed by foreign host. [raub@yakko ~]$ I wonder if it has to do with the fact the virtual mailbox domain I created in postfix is defined as thespider.com while the machine running postfix/dovecot is mail.thespider.com. > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254733744121/+254722743223 > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > "Oh My God! They killed init! You Bastards!" > --from a /. post

1 0

[Dovecot] [RFC] FreeBSD port for dovecot 1.1 series
by Xin LI 02 May '08

02 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have put together a preliminary patchset for dovecot 1.1 at: http://people.freebsd.org/~delphij/misc/dovecot-1.1-rc4.diff My intention is to repocopy the current dovecot port to dovecot11 and make changes on the latter. In this version of patchset, I have intentionally removed the following chunk of change which by default allows gid=0 users to log in. %%% @@ -333,6 +338,7 @@ ~ # belongs to supplementary groups with non-valid GIDs, those groups are ~ # not set. ~ #first_valid_gid = 1 +first_valid_gid = 0 ~ #last_valid_gid = 0 ~ # Maximum number of running mail processes. When this limit is reached, %%% Please let me know if you want more features, have comments, etc., for the FreeBSD port. I am subscribed to this list but I would appreciate if you could use 'Reply all' which will give me more opportunity to get your e-mail from the thousands I receive :) Cheers, - -- Xin LI <delphij(a)delphij.net> http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgY420ACgkQi+vbBBjt66CKNACfdGlItaGCo88W4ZdlLjkZ+Dlb ug8AoJkp9z9nMzwU3K/LLpzOKwD2KDXK =UzzN -----END PGP SIGNATURE-----

3 2

[Dovecot] Truncated emails in Dovecot (v1.0.13)
by Iain 02 May '08

02 May '08

Odd situation started recently whereby emails that are delivered into a maildir folder are being truncated when read. The emails are delivered via Exim and I can see the emails are complete when I look inside them. However, when viewing the emails via Thunderbird or a webmail client, they are truncated. *** START 'dovecot -n' *** # 1.0.13: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/mail.log info_log_path: /var/log/mail.log protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/server_certs/mail.example.com.crt ssl_key_file: /etc/ssl/server_certs/mail.example.com.key ssl_cipher_list: ALL:!LOW disable_plaintext_auth: no 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: Welcome to the example IMAP server first_valid_uid: 8 mail_access_groups: mail mail_location: maildir:/home/vmail/%d/%n/mail mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep 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: . location: maildir:/home/vmail/%d/%n/mail inbox: yes auth default: passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen master: path: /var/spool/mail/dovecot/auth-master mode: 511 user: root plugin: trash: /etc/dovecot-trash.conf quota: maildir:storage=102400 *** END *** I've deleted the dovecot cache and rebuilt, but there's no change here. This is running on a Gentoo Linux server (Xen) with kernel 2.6.20. Any ideas? Iain.

2 4

[Dovecot] new auth connection (for ever)
by Evaggelos Balaskas 02 May '08

02 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody, I have a little problem, when i am trying to read an email via imap my thunderbird is trying (for ever) to read it. My dovecot tells me : dovecot: Apr 29 22:47:23 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:24 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:24 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:25 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:25 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:25 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:26 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:26 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:27 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:27 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 ... dovecot: Apr 29 22:47:27 Info: IMAP(ebalaskas): Disconnected: Disconnected dovecot: Apr 29 22:47:27 Info: auth(default): new auth connection: pid=19349 dovecot: Apr 29 22:47:27 Info: auth(default): new auth connection: pid=19350 dovecot: Apr 29 22:47:27 Info: auth(default): new auth connection: pid=19351 dovecot: Apr 29 22:47:27 Info: auth(default): new auth connection: pid=19352 dovecot: Apr 29 22:47:27 Info: auth(default): new auth connection: pid=19353 dovecot: Apr 29 22:47:27 Info: auth(default): new auth connection: pid=19354 ... It's seems that the for the specific mail the dovecot tries to reconnect for EVER. But why ? Why i cant read this specific mail ? i have more than 72.000 but in some messages i get problems like that. And there are not corrupted (the messages, it's an oreilly newsletter mail for god shake :p ). Any ideas ? i think this is relative to Authentication Cache options. dovecot 1.0.13 $ dovecot -n base_dir: /usr/local/var/run/ log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.info.log protocols: imap listen: *:143 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run//login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting: Hi buddy, have an account ? max_mail_processes: 512 verbose_proctitle: yes first_valid_uid: 1000 last_valid_uid: 5000 mail_privileged_group: mail mail_location: maildir:/var/mail/folders/%u:INDEX=/var/mail/index/%u:CONTROL=/var/mail/control/%u mbox_read_locks: dotlock fcntl imap_client_workarounds: tb-extra-mailbox-sep auth default: cache_size: 10240 cache_ttl: 18000 verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /usr/local/etc/dovecot.passdb userdb: driver: passwd-file args: /usr/local/etc/dovecot.passdb socket: type: listen master: path: /usr/local/var/run/dovecot-auth-master mode: 432 user: dovecot group: mail PS: Btw timo this is the only one problem i have from the very start with dovecot (almost 2 years) Sorry for bad English ! Evaggelos Balaskas - http://ebalaskas.gr Unix System Engineer Informatics Engineer Technological Education -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIF4GGWIK+Pe9twhoRAvW3AJ9C01bRQkbF7vGdmzc5yorzmSLxEACgo7YE kB2QtWrkf8l+qIWpOKk70C4= =PlnJ -----END PGP SIGNATURE-----

2 2

[Dovecot] Replication protocol design #2
by Timo Sirainen 01 May '08

01 May '08

Changes: - Added goal 8 and rewrote mailbox synchronization plan. - Added new SELECT command to change active mailbox and removed mailbox ID from command parameters Goals ----- 1. If a single (or configurable number of) server dies, no mails must be lost that have been reported to IMAP/SMTP clients as being successfully stored. 2. Must be able to automatically recover from a server desynchronization, such as: - server has been offline for a long time - some mail files have been manually added/deleted - corrupted data/mail files if they're noticed 3. In multi-master setup if the link between servers die, the servers must be able to proceed autonomously (kind of conflicts with goal 1 though). When the link comes back, the changes are replicated as soon as possible. 4. Normal IMAP commands must not be able to cause desynchronization between servers. For example making conflicting flag changes simultaneously in two servers must not result in the servers having different flags. 5. Must perform well with at least 3 servers in a multi-master setup, preferrably still with tens of servers. 6. Latency shouldn't be increased noticeably when using servers distributed into 3 or more data centers. Must be usable over high-latency links (in optimistic async mode). 7. In normal operation send minimal incremental changes. 8. Make non-incremental synchronization fast enough to allow replication with users' untrusted Dovecot servers which may connect only rarely. Support also super high latency replication (e.g. using USB sticks). Protocol -------- There are two major parts in the protocol: Handling the normal incremental changes and fixing desynchronization. Originally I thought that maybe the changes could be sent using the same format as Dovecot's transaction logs, but now I'm beginning to think that it's probably not that good idea. The code reuse potential is quite minimal and the format would still have to be extended in several ways so that it won't be directly compatible anyway. So I'm thinking the protocol could be something text-based. The main benefit is that text-based protocols are easier to debug. Stream compression should drop most of the extra overhead if bandwidth is a problem. The exact on-wire protocol anyway doesn't matter in the design that's discussed below. The commands have tags similar to IMAP commands, because some commands may have to be forwarded to other servers and it may take a while to get a reply. During the wait the server may process other commands. Mailbox master -------------- Each mailbox has a single master server selected. In multi-master setups the master server may be moved by having the destination server simply request it from the current master. The current master must then give it up. If link is lost to the current master, one of the remaining servers will become the new master within the remaining servers. Each server must be connected to the current master server. Since each mailbox can have a different master server, this typically means all servers are connected to each others. However it's possible to create setups where server connects to only one other server, which in turn connect to more servers. This is useful if there are bandwidth bottlenecks between some servers. This kind of a situation can also happen if in a network A-B-C the link A-C dies, but A-B and B-C continues to work. Because of this all commands must be able to function in a way that the server proxies them to the current master, instead of failing the command and trying to make it the caller's problem to resend the command to the actual master. When the cluster starts up, a single server is selected as the root master for all mailboxes. If a server doesn't know who the current mailbox master is, it asks from the root. All servers cache the currently known mailbox masters to avoid constant requests to the root. If the root server dies, another server is selected as the root. Because the new root doesn't know what masters have been requested (and asking all of them from all servers would just waste bandwidth), all the servers are expected to flush their master caches and drop their own master status. The new root doesn't respond to any requests before all servers have notified that they've dropped being a master. The master status doesn't have to be at mailbox level granularity. It could just as well be configured to move at user, domain or even global level. Perhaps this could be done dynamically, so that higher granularity is used when the master is beginning to change too often between servers. Mailbox ID ---------- Mailbox IDs are session-specific numbers dynamically assigned for user+mailbox+UIDVALIDITY combinations. All connections have different mailbox IDs. Also send and receive directions have different IDs. This allows the sender to easily replace existing IDs to point to new mailboxes without causing any confusion. MBOX: - Mailbox ID - User name - Mailbox name - Mailbox UIDVALIDITY Reply: - [Mailbox UIDVALIDITY] (if changed - command failed) - Mailbox UIDNEXT - Highest modseq If the receiver finds out it has a different UIDVALIDITY, the mailbox requires a full resync. UIDNEXT and modseq can be used to determine if replication servers are out of sync. After mailbox ID has been assigned, the active mailbox can be changed using a command: SELECT: - Mailbox ID Requesting master status ------------------------ MASTER-MOVE: - [Destination SID] (if forwarding) The command is sent to the last known master for the selected mailbox. The server will keep forwarding the command until it reaches the current master. During the forwarding other servers may want to request something from the master. These requests must be delayed by the forwarding servers until the move is finished. Saving messages --------------- SAVE: - Received date - [IMAP UID] (only if we're the master) - Global UID (stays the same when copying the message) - Message text Reply: - [IMAP UID] (only if not specified in parameters) - [Current mailbox master SID] (if it was moved) If current server is not the master, the SAVE is sent to the master which gives the message its IMAP UID. The master server then replicates the message to other servers with the IMAP UID parameter set. The mailbox master may have already changed by the time server receives a save request. If server receives a SAVE without IMAP UID parameter, it's responsible for finding out the new mailbox master and sending a new SAVE request to it. Once the new master replies with the IMAP UID, the server can reply to the original SAVE request, also providing the new master SID so the future requests can be sent there directly. To be sure the message doesn't get lost, the server should not reply OK to the IMAP/SMTP client until it has received a reply from SAVE. Copying messages ---------------- FIXME: Source or destination mailbox ID parameter should probably be removed and the selected mailbox's ID used instead. COPY: - Source mailbox ID - Destination mailbox ID - Source IMAP UID - Global UID - [Destination IMAP UID] (only if we're the master) - Destination received date Reply: - [Destination IMAP UID] (only if not specified in parameters) - [Current mailbox master SID] (if it was moved) Source mailbox ID + source IMAP UID identifies the message to be copied. It's expected to contain the given global UID (which is just an extra sanity check). Otherwise it works the same way as SAVE. Since the message already exists, it's probably not necessary to wait for a reply before replying OK to originating IMAP client. Expunging messages ------------------ EXPUNGE: - IMAP UIDs (No reply) Expunges also have to be sent via master server (the same way as SAVE) to avoid COPY command failing in some servers because it was just expunged. Changing message flags ---------------------- STORE: - IMAP UIDs - Added flags/keywords - Removed flags/keywords - [Current modseq] (master sends) - [Highest modseq of the messages before this change] (non-master sends) - [flag: this is a CONDSTORE STORE UNCHANGEDSINCE] (non-master may send) [Reply: - IMAP UIDs where STORE was rejected to (if CONDSTORE flag was used) ] Stores also have to be sent via master server to avoid flag desynchronization. Master first checks if it has higher modseqs in the messages. Then it applies all the changes and forwards the changes to other servers. For messages that had higher initial modseqs their flags are sent to the server sending the STORE to fix a potential desync. If CONDSTORE flag is set, the change is rejected for messages that had a higher modseq. Non-masters shouldn't reply to a STORE UNCHANGEDSINCE command before the change has been replicated to master and the rejections have been processed. Mailbox synchronization ----------------------- Network connections to other servers are always initiated by the same servers. From replication point of view they could be thought of as client/server. The clients keep track of the last seen server state for all mailboxes: - UIDVALIDITY - UIDNEXT - Highest modseq Client requests mailbox ID with MBOX command. If UIDVALIDITY changed, state is reset by setting UIDNEXT=1 and highest modseq=0. MBOX command is then resent using the updated UIDVALIDITY. If server's UIDNEXT (server-UIDNEXT) is higher than last seen UIDNEXT (old-UIDNEXT), it means the server has added new messages and we want to fetch them. If the client's UIDNEXT (client-UIDNEXT) is higher than the old-UIDNEXT, it means the client has added new messages and they need to be sent to the server. All messages with UID >= old-UIDNEXT and UID < min(client-UIDNEXT, server-UIDNEXT) have an UID conflict and they must be given new unused UIDs. The synchronization is done in two batches of commands. Client first selects the mailbox and then starts the sync: SYNC-BEGIN: - server's last highest modseq - client's current highest modseq - QRESYNC-like sequence + IMAP UID lists for optimizing EXPUNGE replies Client then proceeds to send all its changes using SAVE, EXPUNGE and STORE commands. The sync is finished with SYNC-END command. Server replies with: - List of expunged IMAP UIDs (EXPUNGE command): - IMAP UIDs - Added messages (SAVE command?): - IMAP UID - Global UID - Modseq - Flags and keywords - Received date - [Message text] - Changed flags/keywords/modseqs (STORE commands): - IMAP UID - Modseq - Changed flags and keywords (or if not easily determined, their current values) - IMAP UID conflict fixes (UIDFIX command): - Source IMAP UIDs - Destination IMAP UIDs - Sync finish: - Updated UIDNEXT - Updated highest modseq Server may also reply with STORE commands that change nothing except modseqs. This is needed to get the modseqs synchronized. If in high-latency + high-bandwidth mode the message texts are always sent. The message texts are also sent if the server can determine that the client couldn't have previously seen the message (i.e. the message was saved, not copied). Otherwise they have to be requested for the messages with previously unseen global UIDs: FETCH: - IMAP UIDs Reply: - Message texts By the time client receives the reply from server, it may already have done further changes. This means it may have to fix modseqs and IMAP UIDs internally as well.

3 6

[Dovecot] virtual mbox case sensitive?
by Anil 01 May '08

01 May '08

This is on dovecot 1.1.rc4. I have this mail_location: mail_location = maildir:/apps/mail/%d/%n/Maildir When I receve mail to a virtual mailbox, its putting it in different Maildir's depending on what the sender used for the caseness of the recipient's email address: I have these Maildirs: JasonK JuliaM info jasonk juliam JasonK and jasonk should be the same maildir. So should JuliaM and juliam. Now the 2nd question is, how do I "move" the mail from JasonK back to jasonk? Thanks, this is very odd!

2 1

[Dovecot] Where to find 1.1 RPM for CentOS 4?
by Patrick 30 Apr '08

30 Apr '08

Hiya, I'm trying to find an rpm for the 1.1 version, since it appears to work better with NFS. Does anyone have a link to the i386 version? Thanks in advance. - Patrick

4 6

[Dovecot] dovecot-1.0.3: Backtrace:/usr/local/libexec/dovecot/imap
by Ralf Hildebrandt 30 Apr '08

30 Apr '08

GNU gdb 6.7.1-debian Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". Reading symbols from /lib/i686/cmov/libdl.so.2...Reading symbols from /usr/lib/debug/lib/i686/cmov/libdl-2.7.so...done. done. Loaded symbols for /lib/i686/cmov/libdl.so.2 Reading symbols from /lib/i686/cmov/libc.so.6...Reading symbols from /usr/lib/debug/lib/i686/cmov/libc-2.7.so...done. done. Loaded symbols for /lib/i686/cmov/libc.so.6 Reading symbols from /lib/ld-linux.so.2...Reading symbols from /usr/lib/debug/lib/ld-2.7.so...done. done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/local/lib/dovecot/imap/lib10_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib10_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib11_trash_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib11_trash_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib20_mail_log_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib20_mail_log_plugin.so Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Core was generated by `/usr/local/libexec/dovecot/imap'. Program terminated with signal 6, Aborted. #0 0xb7f97424 in __kernel_vsyscall () #0 0xb7f97424 in __kernel_vsyscall () #1 0xb7e64ef5 in raise () from /lib/i686/cmov/libc.so.6 #2 0xb7e66871 in abort () from /lib/i686/cmov/libc.so.6 #3 0x080aebea in i_internal_panic_handler ( fmt=0x80bea9c "file %s: line %d (%s): assertion failed: (%s)", args=0xbfdb2944 "�}\f\bk") at failures.c:403 #4 0x080aeafc in i_panic ( format=0x80bea9c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:183 #5 0x0809d23a in mail_transaction_log_view_set (view=0x929e2a0, min_file_seq=0, min_file_offset=26588, max_file_seq=1, max_file_offset=2280, type_mask=MAIL_TRANSACTION_EXPUNGE) at mail-transaction-log-view.c:107 #6 0x08097ce2 in view_sync_set_log_view_range (view=0x928db88, type_mask=<value optimized out>) at mail-index-view-sync.c:103 #7 0x08098279 in mail_index_view_sync_begin (view=0x0, sync_mask=<value optimized out>, ctx_r=0x929e280) at mail-index-view-sync.c:132 #8 0x08086ec4 in index_mailbox_sync_init (box=0x9287740, flags=<value optimized out>, failed=false) at index-sync.c:156 #9 0x0806af41 in maildir_storage_sync_init (box=0x9287740, flags=<value optimized out>) at maildir-sync.c:1557 #10 0x08063f10 in imap_sync_init (client=0x92872f0, box=0x9287740, imap_flags=0, flags=MAILBOX_SYNC_FLAG_FAST) at imap-sync.c:46 #11 0x0806404b in cmd_sync (cmd=0x9287334, flags=MAILBOX_SYNC_FLAG_FAST, imap_flags=0, tagline=0x80be9b3 "OK Fetch completed.") at imap-sync.c:246 #12 0x0805997f in cmd_fetch_finish (ctx=0x9289fc8) at cmd-fetch.c:103 #13 0x08059cca in cmd_fetch (cmd=0x9287334) at cmd-fetch.c:173 #14 0x0805cbe0 in cmd_uid (cmd=0x9287334) at cmd-uid.c:19 #15 0x0805d16f in client_handle_input (cmd=0x9287334) at client.c:344 #16 0x0805d1fc in client_handle_input (cmd=0x9287334) at client.c:398 #17 0x0805d89f in _client_input (context=0x92872f0) at client.c:441 #18 0x080b4a37 in io_loop_handler_run (ioloop=0x92849b0) at ioloop-epoll.c:203 #19 0x080b3cac in io_loop_run (ioloop=0x92849b0) at ioloop.c:329 #20 0x080658ec in main (argc=) at main.c:290 -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) snickebo(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Windows has detected that a gnat has farted near your computer. Press any key to reboot.

1 0

[Dovecot] How dovecot deal with the request to leave posts on the server?
by Ilan Shalif 30 Apr '08

30 Apr '08

Me just request to direction to the documentation of the mechanism of dovecot. Specificly about the mechanism dovecot deal with the request to leave posts on the server, the duration, and the finishing of this mode. (I know I can mark the approptiate places in the mail client (Thunderbird) Ilan Shalif

2 1

[Dovecot] Avelsieve 1.9.7 and Dovecot/TLS
by Michael Firnau 30 Apr '08

30 Apr '08

Hi, i'm installing a new mail server for our faculty and want to use the squirrelmail plugin 'avelsieve' (1.9.7). As documented on the dovecot wiki there is a problem in the STARTTLS code and i found a solution (that works for my installation): i've traced the server output in 'get_response' and instead of a script list i saw "IMPLEMENTATION". So i took a look at the file 'managesieve.lib.php' and the STARTTLS code: /* If we allow STARTTLS, use it */ if($this->capabilities['starttls'] === true && function_exists('stream_socket_enable_crypto') === true) { fputs($this->fp,"STARTTLS\r\n"); $starttls_response = $this->line=fgets($this->fp,1024); if(stream_socket_enable_crypto($this->fp, true, STREAM_CRYPTO_METHOD_TLS_CLIENT) == false) { $this->error=EC_UNKNOWN; $this->error_raw = "Failed to establish TLS connection."; return false; } else { $this->loggedin = true; // RFC says that we need to ask for the capabilities again $this->sieve_get_capability(); $this->loggedin = false; } } With my limited time and debugging possibilities i've found that the dovecot managesieve server seems to send capability lines 'automagically'. I've added a few "debugging" lines /* If we allow STARTTLS, use it */ if($this->capabilities['starttls'] === true && function_exists('stream_socket_enable_crypto') === true) { fputs($this->fp,"STARTTLS\r\n"); $starttls_response = $this->line=fgets($this->fp,1024); if(stream_socket_enable_crypto($this->fp, true, STREAM_CRYPTO_METHOD_TLS_CLIENT) == false) { $this->error=EC_UNKNOWN; $this->error_raw = "Failed to establish TLS connection."; return false; } else { $this->loggedin = true; $starttls_response = $this->line=fgets($this->fp,1024); $errormsg .= _("MFI fgets ") . $starttls_response . '<br>'; print_errormsg($errormsg); // RFC says that we need to ask for the capabilities again $this->sieve_get_capability(); $this->loggedin = false; } } and could read MFI fgets "IMPLEMENTATION" "dovecot" what will throw the following 'sieve_get_capability' out of sync. Then i've added a second 'fgets' and received: MFI fgets "SASL" "PLAIN" Then i've added a third 'fgets' and received: MFI fgets "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex" Then i've added a fourth 'fgets' and received: MFI fgets OK "TLS negotiation successful." Now the protocol should be in sync again and after removing the lines $errormsg .= _("MFI 1 fgets ") . $starttls_response . '<br>'; print_errormsg($errormsg); i could load my scripts back. So, adding four lines reading $starttls_response = $this->line=fgets($this->fp,1024); $starttls_response = $this->line=fgets($this->fp,1024); $starttls_response = $this->line=fgets($this->fp,1024); $starttls_response = $this->line=fgets($this->fp,1024); solved the problem. I know this is not a sound "fix", but i hope to help you with this. One addendum: a "debugging" using my errormsg-printout of the output from /* If we allow STARTTLS, use it */ if($this->capabilities['starttls'] === true && function_exists('stream_socket_enable_crypto') === true) { fputs($this->fp,"STARTTLS\r\n"); $starttls_response = $this->line=fgets($this->fp,1024); resulted in the response: MFI fgets OK "Begin TLS negotiation now." what looks proper to me, but the negotiation makes the server send the four lines mentioned above. Cheers

2 1

[Dovecot] Broken Header uidvalidity problem after upgrade
by Robert Henjes 30 Apr '08

30 Apr '08

Hi, we use a current Debian etch distribution as basis for our servers, which are running within a vmware server environment. Our current configuration consists of a dovecot server with imap enabled and a ldap based authentication. Mails are stored using the Maildir format on a central nfs store. We do not use any virtual mailboxes. Since upgrading from dovecot version 1.0.rc15 (debian stable) to 1.0.13 (debian etch-backport) we got the following error logs. Excerpt from mail.err: Apr 21 12:04:38 servera deliver(usera): /var/mail/Maildir/usera/dovecot-uidlist: Broken header (uidvalidity = 0, next_uid=9) Apr 21 15:37:50 servera deliver(userb): /var/mail/Maildir/userb/dovecot-uidlist: Broken header (uidvalidity = 0, next_uid=16) Apr 23 10:37:17 servera dovecot: IMAP(userc): /var/mail/Maildir/userc/.Sent/dovecot-uidlist: Broken header (uidvalidity = 0, next_uid=2) Apr 25 17:00:17 servera dovecot: IMAP(userd): /var/mail/Maildir/userd/dovecot-uidlist: Broken header (uidvalidity = 0, next_uid=8) I did already some mailinglist reviews. They confirmed in some way the problem, but there is still no explanation where it comes from, and how it can be solved or if it may affect the proper operation of the system. Here are some links with a short comment, which are related to this problem: http://www.dovecot.org/list/dovecot/2007-September/025541.html This post also uses nfs, but pam for authentication, error message is exactly the same as in our case. http://www.dovecot.org/list/dovecot/2007-July/024001.html Version upgrade from 1.0.0 to one above, also problems with uidvalidity. They described, that it happens only once for each user after upgrading. This is similar to our observations. No user complains as well ;). So it would be only of interest if it is so. http://wiki.dovecot.org/Clients/NegativeUIDs The number for uidvalidity is zero, so it is non-negative. But maybe it is correlated with these hints. From my point of view, there could be some problems with time synchronization as well between nfs server and dovecot server machine. But we checked this and they differ never more than 2 seconds. In total we are running two servers in parallel, each has it's own userspace, all accounts are strictly separated. One server is running the rc15 version, the other (more experimental) is running the backport 1.0.13. The described problem occurs only on the 1.0.13 server, which was previously updated. All other configurations are exaclty the same. Any hints? Best regards, Robert -- Dipl.-Inform. Robert Henjes University of Wuerzburg, Institute of Computer Science, Department of Distributed Systems (Informatik III), Am Hubland, 97074 Wuerzburg, Germany henjes(a)informatik.uni-wuerzburg.de Tel: +49 931 888-6652 Fax: +49 931 888-6632

2 5

[Dovecot] fourat wants to keep up with you on Twitter
by fourat 30 Apr '08

30 Apr '08

To find out more about Twitter, visit the link below: http://twitter.com/i/8859b2431664c01a1adfe2051a644a79b4cc1689 Thanks, -The Twitter Team About Twitter Twitter is a unique approach to communication and networking based on the simple concept of status. What are you doing? What are your friends doing—right now? With Twitter, you may answer this question over SMS, IM, or the Web and the responses are shared between contacts.

1 0

[Dovecot] Quota not showing properly in webmail
by Eden 29 Apr '08

29 Apr '08

Hi I have a virtual users system using postfix / mysql / dovecot. Everything is working like a charm except for the quota display on webmail systems. It is working properly but showing GB instead of MB. For example. If I create a user with 100MB of quota and send him 50MB of mail, squirrelmail and roundcubemail display 50MB of 100GB If I create another user with 20MB quota and send him 10MB of mail, squirrelmail and roundcube dipslay 10MB of 20GB. if I send 50MB more I get the quota error msg I should get. So everything is workign but its displaying incorrectly. At first I though it was squirrelmail`s fault but it happens with roundcube as well, since both get their quota info from the imap server than I think its dovecot. I`m using Debian 4.0 This is the output of the --version and the -n dovecot commands. qgalvao-dns:/# dovecot --version 1.0.rc15 qgalvao-dns:/var/log# dovecot -n # /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3s pop3 listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 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 first_valid_uid: 150 last_valid_uid: 150 mail_privileged_group: mail mail_location: maildir:/vmail/%n@%d 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 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: login plain digest-md5 cram-md5 user: nobody verbose: yes debug: 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

4 12

[Dovecot] Connection problems using dovecot proxy
by Adrian Wojcicki | Unternehmensberatung Wojcicki 29 Apr '08

29 Apr '08

Hi Maybe somebody could help me with the following problem: I have set up a dovecot imap proxy in the dmz and a dovecot imap server in the intranet. Both in version 1.05. Now, while this setup works using Thunderbird, iPhone, etc. I have problems connecting using a Samsung Qbowl. It simply aborts with a connection error. Using the same setup but bypassing the proxy and connecting to the imap server directly does work for the phone. Logs on both servers don't show any errors. There is simply a "Info: IMAP(test): Connection closed" at the end. I enabled the rawlogs on the imap server but they don't long anything (They do log access from other imap clients but nothing from the phone). Could somebody point me into a direction where to look next? LOGS: Dovecot proxy: # 1.0.5: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log ssl_cert_file: <pathToCert> ssl_key_file: <pathToCert> disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_debug: yes auth default: cache_size: 4096 cache_ttl: 7200 debug: yes passdb: driver: sql args: /etc/dovecot/sql.conf userdb: driver: static args: static uid=5000 gid=5000 home=/dev/null dovecot: Apr 23 15:42:45 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=192.168.3.200 rip=80.187.64.167 resp=<hidden> dovecot: Apr 23 15:42:45 Info: auth(default): cache(test,80.187.64.167): hit dovecot: Apr 23 15:42:45 Info: auth(default): cache(test,80.187.64.167): NULL password access dovecot: Apr 23 15:42:45 Info: auth(default): client out: OK 1 user=test host=192.168.0.205 destuser=test nologin proxy pass=<hidden> dovecot: Apr 23 15:42:45 Info: imap-login: proxy(test): started proxying to 192.168.0.205:143: user=<test>, method=PLAIN, rip=80.187.64.167, lip=192.168.3.200 dovecot: Apr 23 15:42:45 Info: imap-login: proxy(test): disconnecting 80.187.64.167 Dovecot server: # 1.0.5: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/lib/dovecot/imap-login mail_location: maildir:/home/%u/.maildir mail_debug: yes mail_executable: /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap auth default: debug: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=1001 gid=100 home=/home/%u dovecot: Apr 23 15:42:45 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=192.168.0.205 rip=192.168.2.1 resp=<hidden> dovecot: Apr 23 15:42:45 Info: auth(default): passwd-file(test,192.168.2.1): lookup: user=test file=/etc/dovecot/passwd dovecot: Apr 23 15:42:45 Info: auth(default): client out: OK 1 user=test dovecot: Apr 23 15:42:45 Info: auth(default): master in: REQUEST 6 11785 1 dovecot: Apr 23 15:42:45 Info: auth(default): master out: USER 6 test uid=1001 gid=100 home=/home/test dovecot: Apr 23 15:42:45 Info: imap-login: Login: user=<test>, method=PLAIN, rip=192.168.2.1, lip=192.168.0.205 dovecot: Apr 23 15:42:45 Info: IMAP(test): Effective uid=1001, gid=100, home=/home/test dovecot: Apr 23 15:42:45 Info: IMAP(test): maildir: data=/home/test/.maildir dovecot: Apr 23 15:42:45 Info: IMAP(test): maildir: root=/home/test/.maildir, index=/home/test/.maildir, control=, inbox= dovecot: Apr 23 15:42:45 Info: IMAP(test): Connection closed

2 3

[Dovecot] reason to switch to 1.1
by Cor Bosman 29 Apr '08

29 Apr '08

We've been running 1.1 on about half of our servers for about a week now. Ive mailed before that I was pleasantly surprised by its better use of resources. Here's a graph showing that fact. Server load in the last 10 days. http://uwimages.smugmug.com/photos/286355874_9FNp2-L.png Cor

5 10

[Dovecot] Imap sent folder sometimes dosen't get updated in dovecot-1.1-rc3(+some current hg patches)
by Diego Liziero 29 Apr '08

29 Apr '08

Yes, again, some sent emails don't get copied to sent folder. This time I get the following error: Error: IMAP(username): UIDs broken with partial sync in mbox file /maildir/username/Sent This happened at least with thunderbird and with evolution. Dovecot is running on vith fcntl locking on Centos5, sendmail should use fcntl, too. Filesystem is ext3 on drbd partition. After a grep vith dovecot.log I see the same error message also with other imap folders as well (mainly Trash imap folder). Should I try to get a rawlog? Regards, Diego.

2 3

[Dovecot] icedove update
by Karl Schmidt 29 Apr '08

29 Apr '08

Something came up that Confounded problems in my move from UW-imap to dovecot. I found a problem with the new icedove update in Debian lenny when moving from 1.5.0.13+1.5.0.14b.dfsg1-0etch1 to 2.0.0.9-3 that could look like a dovecot issue. Icedove runs for a while but eventually quits updating the displayed email, yet appears to be working and busy trying to get messages from the server. I think it is related to message filters, but not sure. The fix was to move .mozilla-thundrebird somewhere and restart icedove and create a new profile. There may be a more elegant fix. ---------------------------------------------------------------- Karl Schmidt EMail Karl(a)xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 "Never let school interfere with your education." - Mark Twain ----------------------------------------------------------------

3 2

[Dovecot] sieve doesn't sift yet
by Colin Brace 28 Apr '08

28 Apr '08

Hi all, I am having difficulty getting sieve working. I created a simple set of rules which I've validated on the sieve-php page at SF. I placed this file, .dovecot.sieve, in the root of my maildir, which I understand is the default location. I also created a logfile in /var/log, but nothing has gotten written to it yet. Here is my configuration: $ sudo dovecot -n # 1.0.13: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot info_log_path: /var/log/dovecot.info ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_gid: 0 mail_access_groups: mail mail_location: maildir:/var/spool/vmail/%n mail_debug: yes pop3_uidl_format: %08Xu%08Xv auth default: verbose: yes passdb: driver: passwd-file args: /usr/local/etc/dovecot-passwd userdb: driver: passwd userdb: driver: static args: uid=vmail gid=vmail home=/var/spool/vmail/%n What piece of the puzzle am I still missing? Running dovecot-sieve-1.0.2, postfix, etc under FreeBSD v7. TIA -- Colin Brace Amsterdam http://lim.nl

5 10

[Dovecot] Public Namespace + ACLs + virtual users
by Fintec 28 Apr '08

28 Apr '08

g'day! I'd just like to share my experience with public namespace and ACLs. I know this has been discussed a number of times in the past, but there were no definite answers. dovecot version i'm using: 1.0.13 Got a public namespace setup in dovecot.conf as follows: namespace public { separator = . prefix = Public_Folders. location = maildir:/home/vmail/domains/% d/Public_Folders:CONTROL=/home/vmail/domains/%d/% n/Public_Folders/support:INDEX=/home/vmail/domains/%d/% n/Public_Folders/index hidden = no } In it's own right this works just fine and it's been in use for some time now. But we need some control over who can access and delete things. So I had a go at configuring ACLs. I configured global ACLs, because as far as I can tell, per directory ACLs seem to be ignored. Once configured global ACLs work fine, except for 1 major issue; users cannot create new folders because ACLs do not get propagated (are not applied to the subfolders). If an user attempts to create a new (sub)folder, the folder is created on the filesystem however email client throws an error and the folder is inaccessible to the user as there is no ACL for it. Any pointers how to get around this? Has this been dealt with in v1.1? Regards Natko Muzina

2 1

[Dovecot] Problems with Public Folders
by Matt Rude 27 Apr '08

27 Apr '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am trying to implement public folders on my Fedora 8 + Postfix 2.5.1 + MySQL + Dovecot 1.0.13. I have Public folder shown in for my users but when they choose the folder "Public" they receive the error "The mail server responded: Mailbox doesn't exist: Public" (in Thunderbird) or just simply "Mailbox doesn't exist: Public" (In SquirrelMail). They are also reciveing the same errors when they try to subscribe to the Public Folder. Thanks - -Matt - ------------------- # /usr/local/sbin/dovecot --version 1.0.13 - ------------------- # /usr/local/sbin/dovecot -n # 1.0.13: /usr/local/etc/dovecot.conf listen: ssl_cert_file: /etc/pki/dovecot/certs/dovecot.pem ssl_key_file: /etc/pki/dovecot/private/dovecot.pem login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: postfix mail_location: maildir:/var/spool/virtualmailboxes/%d/%u/imap/:INBOX=/var/spool/virtualmailboxes/%d/%u/:INDEX=/var/spool/virtualmailboxes/%d/%u/imap/index/ mail_plugins: quota imap_quota namespace: type: public separator: / prefix: Public/ location: maildir:/var/spool/virtualmailboxes/%d/Public/ namespace: type: private separator: / inbox: yes auth default: mechanisms: plain digest-md5 cram-md5 cache_size: 128 cache_ttl: 600 passdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot-mysql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: virtualmail group: virtualmail plugin: quota: maildir:storage=10240 - ------------------- # grep -v '^ *$#.*$\?$' /etc/dovecot-mysql.conf driver = mysql connect = dbname=postfix user=postfix host=localhost password=postfix default_pass_scheme = md5sum password_query = SELECT password FROM mailbox WHERE username = '%u' user_query = SELECT maildir, 1000 AS uid, 1000 AS gid, CONCAT('maildir:storage=', ROUND( mailbox.quota / 1024 ) ) AS quota FROM mailbox WHERE username = '%u' AND active = '1' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIDW+KyxB1nuZfLEYRAmigAJ44kfgX2Nh6Mi6PAukq4pxMBL3SpgCZASJG qmmZr0N1HJPeWsKnQN+qcSs= =xNyb -----END PGP SIGNATURE-----

2 3

[Dovecot] Mail deletion
by Johannes Grimm 26 Apr '08

26 Apr '08

Hi, when im deleting messages with my mail-client thunderbird, those mails dissapear in the client. but they stay on the server dovecot 1.0.13 on reiserfs. is there a special expunge timer or when will those orphaned messages whiped out of the filesystem? -- ============================================================== Hochschule für angewandte Wissenschaften - Fachhochschule Rosenheim University of Applied Sciences Rechenzentrum Johannes Grimm Hochschulstr.1 D-83024 Rosenheim Tel: +49-8031/805-229 Fax: +49-8031/805-223 http://www.fh-rosenheim.de/ johannes.grimm(a)fh-rosenheim.de ==============================================================

2 1

[Dovecot] antispam for Dovecot 1.1
by Anders 26 Apr '08

26 Apr '08

Hi Johannes. I wanted to try out the antispam plugin for a Dovecot 1.1 install, only to learn that 1.1 is actually not supported. Are there any plans to remedy this? If not, is it known how much effort is required? (i.e. could I do it myself?). Thanks, Anders.

3 4

[Dovecot] Does a script exist to fix broken maildir timestamps?
by drbob 26 Apr '08

26 Apr '08

Hello, When I upgraded to dovecot (changing servers at the same time) in November last year I copied the maildirs from my old server without using the -p option to preserve timestamps! Since my mail client displays the email dates based on the Date header rather than the imap "internaldate" I didn't notice the problem until today when I tried to migrate an account to gmail using imapsync and found that all emails prior to November display the wrong date in the web interface (they show the date they were copied in November). I feel very silly. Before I go try to hack together a script which parses all my older email files and changes the timestamps to the time recorded in the "Date:" header, does anyone know if robust, tested version of such a script is alrady available? Would correcting the timestamps in this way cause any problems for dovecot (e.g in the index files)? Thanks in advance for any help. drbob NB In my googling for a solution to this problem I found this hack to imapsync which would rewrite the "internaldate" based on the date header during a sync. Whilst I'd rather fix the timestamps that are the source of the problem, it may be useful for others finding this post in the future, see: http://www.zimbra.com/forums/installation/237-received-date-appears-incorre…

1 1

[Dovecot] permission problems
by Cor Bosman 25 Apr '08

25 Apr '08

Hi, ever since i switched a few servers to 1.1RC4 im finding control dirs with the wrong permissions: 80023615 8 drw------- 2 xxxxxxx user 4096 Apr 23 09:46 ./a/an/xxxxxxx/INBOX/.INBOX.Maatschappijen When dovecot then wants to write a file inside, it gets a permission denied. Cor

2 4

[Dovecot] Mixing LDAP and static
by Anders 25 Apr '08

25 Apr '08

I want to read quota size from LDAP, but I have a static value for home. How can I mix these? Right now, I have this LDAP configuration: user_attrs = uid=home=/var/mail/vhosts/%d/%n,gosaMailQuota=quota_rule=*:bytes=%$M which works fine, but looks up the uid attribute needlessly, and is not scalable: I have to pick a different, always-existing LDAP attribute for each static extra field that I want to set. Is there some LDAP configuration syntax like the SQL "SELECT '/var/...' AS home" ? Thanks, Anders.

2 9

[Dovecot] 1.0.5: many pop3-login processes?
by Alan Ferrency 25 Apr '08

25 Apr '08

Hello, We are running dovecot 1.0.5 on a test server, with FreeBSD 6.2 (though I have noticed the same problem since dovecot versions in the 0.99 range). We don't have very many simultaneous pop/imap users, but we have a proliferation of pop3-login processes. Currently we have 128 such processes. We have 11 imap-login processes, but only a few actual imap processes running. Is this normal? Can we stop it? Is anyone else successfully running dovecot on FreeBSD 6.2? Thanks for your help. Alan Ferrency pair Networks, Inc. alan(a)pair.com

4 14

[Dovecot] Problem with Dovecot Delivery Agent, Extra "From" lines and mbox
by Hokan 25 Apr '08

25 Apr '08

When an mbox email contains a line that looks like a "Mail" header it should be quoted (per RFC 4155). Sendmail's delivery agent does this, as does Procmail delivery agent. Dovecot deliver does not do this. Example line, with ">" quote: >From hokan(a)hokan.org Thu Mar 8 17:28:01 2008 When reading email (IMAP) that contains such an unquoted line, the email abruptly ends before the "Mail" line. There may (or may not) appear another email (visible to the client) that contains the rest of the email. -- Hokan MEnet, a wholly owned subsidiary of Enet System Administrator Department of Mechanical Engineering hokan(a)me.umn.edu Institute of Technology 612.626.9800 University of Minnesota

2 4

[Dovecot] Authentication: Dovecot -> Vpopmail - > MySQL with one table per domain
by James Nordstrom 25 Apr '08

25 Apr '08

Hi All, I am using Dovecot 1.0.13 with Vpopmail (Qmail Toaster current) backed by MySQL with one table per domain (--disable-many-domains) . What I cannot figure out is how to have Dovecot authenticate to Vpopmail when Vpopmail uses one table per domain. Basically I need dynamic SQL in the Dovecot-sql.conf file. Currently I have: password_query = select pw_clear_passwd as password from domainname_com where pw_name = '%n' I need something like password_query = select pw_clear_passwd as password from %d where pw_name = '%n' Where %d is the name of the table. I can't use the exact domain name at it will not match the vpopmail format domainname_com. I would be happy to use some sort of sting builder but and not sure what my options are in the .conf file. Please help Thanks in advance James James Nordstrom Nordstrom Design Inc. E-mail: james(a)nordstromdesign.com US: 908-419-5597 Europe: 001/908-419-5597

2 1

[Dovecot] Index maintenance
by Anders 25 Apr '08

25 Apr '08

Hi. I am unable to find information about what happens to the index file if I use something like the cron script at the bottom of http://wiki.dovecot.org/Plugins/Expire There must be some information in the index that is no longer needed. When and how will Dovecot clean this up? Thanks, Anders.

2 5

[Dovecot] sieve header :matches for multiline header
by Anton Yuzhaninov 25 Apr '08

25 Apr '08

RFC3028 say: Folding of long header lines (as described in [IMAIL] 3.4.8) is removed prior to interpretation of the data. The folding syntax (the CRLF that ends a line plus any leading whitespace at the beginning of the next line that indicates folding) are interpreted as if they were a single space. But it seems to be not true for dovecot-sieve-1.0.2 for header Received: from example.ru (example.ru [192.168.105.14]) by myserver (Postfix) with ESMTP id D4DA5D85927 This sieve test work: header :matches "Received" "from *by myserver (Postfix) with ESMTP id *" But this test not work, while should also work according to RFC: header :matches "Received" "from * by myserver (Postfix) with ESMTP id *" -- WBR, Anton Yuzhaninov

4 3

[Dovecot] ACLs generating plugin problems.
by "Fábio M. Catunda" 25 Apr '08

25 Apr '08

Hi! I'm trying to use an ACL to avoid deletion of messages that are inside .Trash folder, the ACL is already working very well, the problem that I'm facing is that even if the message is not deleted, mail_log logs that it has been deleted. Also, in some cases part of the lazy_expunge code is executed too, but sometimes I just dont know where the message is, thats weird. I erased deleted and expunged folders, then I deleted a message, It hasn't been deleted, but "deleted" and "expunged" folders has been created. Anyway, I would like to know if there is a way to stop plugin execution when an ACL matches. Thanks a lot.

2 3

[Dovecot] alert function, V2
by Stewart Dean 25 Apr '08

25 Apr '08

I guess the alert function is not part of the spec, because it appears to be unimplemented in Dovecot, even though most clients implement it. Timo, I would hope this would be easy to implement, and it's functionality that will be valuable to every installation. Here's why. America recently had the tragedy of a shooting rampage on a large university campus (yes, America should do something about the violence and free access to guns in our culture/society). What was worse was that, due to the lack of an emergency notification process, some 20+ people died needlessly. Now all college and university administration are scrambling to set up emergency notification processes. Our first take on this is a massive all-hands mailing list, but a) best case, it would take 15 minutes (and as much as an hour) to get to everybody's mailbox. b) users would have to read through their mail and stumble on the message What's needed is an "in-your-face" unavoidable alert, and the UWIMAP alert functionality provides this. As I recall, you touch just about anything in your IMAP client and there's a popup message in the middle of the client IMAP window...and it happens repeatedly. We tried it back 3-4 years ago and found it too annoying to use. For this purpose, it's perfect. The wy UWIMAP did it, the presence of the file /etc/imapd.alert triggers it, and the text in that file is transmitted to the client. The message has to be short, a one-liner for a small popup window, but this could be a pointer to a shared system message folder. Of course, DC could sense the activation of the alert in some other fashion that the presence of a file. Ideally, whatever activates the alert function should be able to be turned on remotely; I had in mind to do it using a mail aliases that is a pipe to a executable... What say you? -- ==== 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

6 9

[Dovecot] dovecot-1.1.rc3 assertion failure in index-sync.c
by richs＠whidbey.net 25 Apr '08

25 Apr '08

We just came across a mailbox today that, when accessed via POP3 or IMAP, crashes Dovecot. It seems to be another index-related corruption issue (as removing "dovecot.index" for INBOX fixed it); Using POP3: dovecot: Apr 09 10:28:14 Warning: POP3(USERNAME): Maildir /mail/USERNAME/Maildir: UIDVALIDITY changed (1145576765 -> 1207677483) dovecot: Apr 09 10:28:14 Panic: POP3(USERNAME): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) dovecot: Apr 09 10:28:14 Error: POP3(USERNAME): Raw backtrace: pop3 [0x80c04e4] -> pop3 [0x80c013c] -> pop3 [0x808eb9a] -> pop3(index_mailbox_set_recent_seq+0x3e) [0x808ebde] -> pop3(maildir_sync_index+0x923) [0x8064173] -> pop3 [0x8062e22] -> pop3(maildir_storage_sync_init+0x58) [0x8062f98] -> pop3(mailbox_sync+0x1f) [0x80912af] -> pop3(client_create+0x1de) [0x805968e] -> pop3(main+0x403) [0x805b503] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x707dec] -> pop3 [0x8058e71] dovecot: Apr 09 10:28:14 Error: child 28169 (pop3) killed with signal 6 Using IMAP (after "SELECT INBOX"): dovecot: Apr 09 10:56:31 Warning: IMAP(USERNAME): Maildir /mail/USERNAME/Maildir: UIDVALIDITY changed (1145576765 -> 1207677483) dovecot: Apr 09 10:56:31 Panic: IMAP(USERNAME): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) dovecot: Apr 09 10:56:31 Error: IMAP(USERNAME): Raw backtrace: imap [0x80cd564] -> imap [0x80cd1bc] -> imap [0x809b32a] -> imap(index_mailbox_set_recent_seq+0x3e) [0x809b36e] -> imap(maildir_sync_index+0x923) [0x8070903] -> imap [0x806f5b2] -> imap(maildir_storage_sync_init+0x58) [0x806f728] -> imap(mailbox_sync+0x1f) [0x809da3f] -> imap(cmd_select_full+0xd5) [0x805dec5] -> imap(cmd_select+0x19) [0x805e069] -> imap [0x805f799] -> imap [0x805f827] -> imap [0x805ffb5] -> imap(client_input+0x5e) [0x80601ce] -> imap(io_loop_handler_run+0x100) [0x80d4d50] -> imap(io_loop_run+0x28) [0x80d42e8] -> imap(main+0x4ac) [0x8067bdc] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x125dec] -> imap [0x8059d61] dovecot: Apr 09 10:56:31 Error: child 7057 (imap) killed with signal 6 We made a copy of the mailbox and index in case any further testing would be helpful, -Rich

2 1

[Dovecot] Rare problem with Indexes?
by richs＠whidbey.net 25 Apr '08

25 Apr '08

We've been running 1.1 rc3 now for about a month, and overall it's been very fast and stable. There is however an Index-related problem that keeps cropping up which prevents a user from accessing their mailbox until their Indexes are manually removed. Somehow, an Index becomes problematic, and Dovecot hangs forever when the mailbox is accessed. It manifests when a user logs in and issues a "SELECT INBOX", or "GETQUOTAROOT" when "maildirsize" needs rebuilding. When Dovecot hangs, no data is returned and no further commands are accepted, and the daemon must be killed. We see no errors in the logs, but have yet to catch the problem with "mail_debug" enabled. We're using NFS with Maildir's and these related options: mail_location = maildir:/mail/%Lu/Maildir:INDEX=/mail/%Lu/Cache mmap_disable = yes mail_nfs_storage = yes mail_nfs_index = yes mail_drop_priv_before_exec = yes mail_cache_min_mail_count = 128 mailbox_idle_check_interval = 5 maildir_stat_dirs = yes maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = no Has anyone else run across the need to purge Indexes manually? Could this be unrecoverable Index corruption, or a locking issue? We've made a copy of the mailbox when the problem occurs. However, when we test it later, Dovecot re-builds the "dovecot.index" file itself just fine, and functions normally. We plan to "mail_debug" when this happens next to see if we can get more information. Thanks! -Rich

2 1