- dovecot - dovecot.org

[Dovecot] dict quota not being updated for all users when receiving a multi-recipient message
by Justin McAleer 15 Feb '07

15 Feb '07

I've set up a mysql quota dictionary using the proxy setup as described in the wiki (using Dovecot lda). When I send a single message to multiple users, only the first recipient is getting their usage updated. This behavior occurs if I manually send to more than one user via the To: line, or via aliases set up in postfix. I do have dovecot_destination_recipient_limit set to 1. I don't even have a guess as to what might be going on here, since each instance of the lda is a separate process. But, let me know if anybody has any ideas or requests for more info.

2 2

[Dovecot] sieve plugin
by pod 15 Feb '07

15 Feb '07

I'm currently looking at dovecot for a large-scale deployment. The requirements will almost certainly mean we would use the dovecot lda with the sieve plugin. The current method of distribution causes (binary distro) packaging to be slightly awkward IMHO. The dovecot-sieve code needs to be told where an in-tree build of dovecot lives. The fact that it _must_ be an in-tree build I was considering as a bug; the dovecot-sieve build wants to access both '.a' and '.h' files from the dovecot build but in an out-of-tree build these are in different places. My first thoughts were to simply move the dovecot-sieve code into the dovecot tree (I imagine under src/plugins/cmusieve or similar) and rework the autoconf setup as appropriate. This sidesteps the problem for this case but does not help other 'third party' dovecot plugins. If however a simple plugin build environment were to exist as part of a dovecot install then plugins could be distributed and built as independent packages. I quite understand that this additionally burdens dovecot development with 'stable API' concerns which may not be considered worth the effort. Timo: have you thought about any of the above and if so which direction have your thoughts taken you? I can justify spending a small amount of time to develop this into real code but it would be a waste to fight against or duplicate existing effort that has gone into this area. All comments welcome.

2 1

[Dovecot] leaking file descriptors? imap-login: inotify_init() failed
by Dale Bewley 15 Feb '07

15 Feb '07

Even though the system is configured to allow a large number of open files, and tools such as lsof tell me dovecot is within that limit; I am seeing errors like this pretty frequently. dovecot: imap-login: inotify_init() failed: Too many open files I'm running Fedora Core 5 (2.6.18-1.2257.fc5 SMP x86_64) with dovecot-1.0-1.rc15 built from the FC6 SRPM, but I was seeing the same thing with 1.0-0.beta8.3.fc5 (one of the reasons for the jump to the FC6 ver). # system default limit is very high, and we aren't approaching it [root@mail 2496]# cat /proc/sys/fs/file-max 738223 [root@mail fs]# cat file-nr 8704 0 738223 # the limit per user is 1024 [root@mail 2496]# su -c 'ulimit -n' dlbewley 1024 # But dovecot doesn't appear to be above that. # it looks like the master process is well below that [root@mail 2496]# lsof -p `cat /var/run/dovecot/master.pid` | wc -l 280 # but overall, this user has way more than that [root@mail fs]# lsof -nu dovecot |wc -l 3145 So, I raised the limit for dovecot to 5000 soft and 10000 hard to see if it would make a difference. Even after a reboot, the next day the errors returned. Today login_process_per_connection is set to 'no' rather than the default to see if it makes a difference. So far today, no errors. Config looks like this: protocols = imap imaps pop3 pop3s ssl_cert_file = /usr/share/ssl/certs/mail.cert ssl_key_file = /usr/share/ssl/private/mail.key disable_plaintext_auth = no login_process_per_connection = no max_mail_processes = 2048 protocol imap { } protocol pop3 { } auth_username_chars = auth_master_user_separator = * auth default { mechanisms = plain passdb passwd-file { args = /etc/dovecot/dovecot.masterusers master = yes pass = no } passdb pam { } userdb passwd { } user = root } plugin { } -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3

2 1

[Dovecot] POP3-Proxy error
by Christian Froemmel 15 Feb '07

15 Feb '07

Hi, as mentioned in another thread I discovered a crash in the pop3-proxy. It occurs when the remote-pop3-server just drops the connection (in my case courier was hitting the MAXPERIP-Limit). I don't have a corefile yet, but will try to get one. Here the message from the dovecot.log: dovecot: Feb 02 09:30:00 Error: pop3-login: file pop3-proxy.c: line 20 (proxy_input): assertion failed: (!client->destroyed) dovecot: Feb 02 09:30:00 Error: pop3-login: Raw backtrace: pop3-login [0x8052fe0] -> pop3-login [0x8052ab4] -> pop3-login(vfprintf+0x2324) [0x804c6fc] -> pop3-login(vfprintf+0x2c9a) [0x804d072] -> pop3-login(vfprintf+0x1086) [0x804b45e] -> pop3-login(vfprintf+0x29d0) [0x804cda8] -> pop3-login [0x8056346] -> pop3-login [0x8055849] -> pop3-login(vfprintf+0x39d6) [0x804ddae] -> /lib/i686/libc.so.6(__libc_start_main+0xc7) [0x4015bd17] -> pop3-login(SSL_write+0x49) [0x804a931] dovecot: Feb 02 09:30:00 Error: child 5985 (login) killed with signal 6 It seems that the unexpected shutdown of the connection confuses dovecot. When I increased the MAXPERIP-limit in courier the crashes went away. regards, Christian -- SYSTEM CONCEPT GmbH

2 1

[Dovecot] master user
by Tom Bombadil 15 Feb '07

15 Feb '07

Greetings all... We are thinking about using the master DB, so a few admins can impersonate an ordinary user. So, we want to define one master for a set of users. And this administrator cannot be master of the other users? Can this be done somehow? Reading the docs, it seems that if a user is defined as master, it can login as everyone. Thanks for any hint.

4 3

[Dovecot] Startup errors
by Steven F Siirila 15 Feb '07

15 Feb '07

I just finished setting up a test Dovecot server (1.0-rc15, Solaris 10) and noticed upon start of Dovecot (after rebooting the server) that the imap-login and pop3-login processes spew errors as follows, which I can only assume is due to the fact that dovecot-auth has not fully initialized yet... it seems to me that these login processes are getting started too early, or should at least be waiting for dovecot-auth to get started. Jan 31 15:55:06 hostname dovecot: Dovecot v1.0.rc15 starting up Jan 31 15:55:07 hostname dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname dovecot: pop3-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname last message repeated 1 time Jan 31 15:55:07 hostname dovecot: pop3-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname last message repeated 1 time Jan 31 15:55:07 hostname dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname last message repeated 9 times Jan 31 15:55:07 hostname dovecot: pop3-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname last message repeated 9 times -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

2 1

[Dovecot] Q on configuring shared mboxes
by Mikhail Teterin 15 Feb '07

15 Feb '07

Hello! I have the following three types of mailboxes on my server: 1) Regular user mail /var/mail/<user> in mbox format 2) Suspected spam in /var/tmp/spamprobe in mbox format 3) Archived mailing list in /home/mks/mksarch in mbox format I want the 1) to be only accessible to the respective <user>, obviously (POP3 and/or IMAP4). I wanted the 2) to be accessible to all users -- and I want them to be able to move stuff out of it into their own mboxes (IMAP4 is enough). I want the 3) to be accessible _read only_ to anyone, who enters the correct username/password (preferably -- without creating a special Unix account). (IMAP4 or POP3) So far, I have only been able to achieve 1). Could someone, please, help me configure dovecot for the 2) and the 3)? Thanks! -mi

2 1

[Dovecot] Dovecot ACL
by Barry Kwok 15 Feb '07

15 Feb '07

I am using 1.0-rc19 version. I made a global ACL file in /etc/dovecot-acls/Public as: owner lrsi user=manager rl The owner cannot delete/move mail inside his Public folder as I want. But the user "manager" cannot subscribe/view to other's Public folder. What I have missed?

2 1

[Dovecot] lda sieve broken after upgrade
by lenny＠edpausa.com 15 Feb '07

15 Feb '07

upgraded to rc19. using maildirs. solaris 9/cc. removed all modules from pop/imap/lda subdirs and first upgraded dovecot to rc19 and then used dovecot-sieve-1.0.1 sources to build against the dovecot source directory ( everything now builds nicely on Solaris, thank you Timo ). added "cmusieve" to the list of plugins used by lda. ail_plugins = cmusieve now getting this: deliver(lenny): Error: dlopen(/usr/local/dovecot/lib/dovecot/lda//lib90_cmusieve_plugin.so) failed: ld.so.1: deliver: fatal: relocation error: file /usr/local/dovecot/lib/dovecot/lda//lib90_cmusieve_plugin.so: symbol deliver_mail: referenced symbol not found anyone ? on the same machine, mbox based dovecot rc19 with dovecot ( sieve ) lda, works and upgraded without any issues, although the prior version must have been different, since the cmusieve statement was already present.

2 2

[Dovecot] Hello, new to the list
by Vikram Goyal 15 Feb '07

15 Feb '07

Hello Guys! I have just joined the list as I needed some clarifications, help etc. I am not sure what I want is possible and I have been unable to do it myself, read lots of dovecot wiki pages, debian lists, dovecot archives, experimented myself and so on. I have a mail dir ~/Mail where all my mails get distributed to their respective folders through procmail filters. The heirarchy is as follows: ~/Mail/ /inbox --> maildir /trash --> trash maildir /newsletter --> mbox lists/ --> normal dir /dovecot --> dovecot list maildir /some other list maildirs I wanted to access them through dovecot. I have tried namespaces etc but have been unable to accomplish till now. Kindly help. Thanks! -- vikram... |||||||| |||||||| ^^'''''^^||root||^^^'''''''^^ // \\ )) //(( \\// \\ // /\\ || \\ || / )) (( \\ -- o ~|~ = Registered Linux User #285795

3 3

[Dovecot] sieve question
by Xueron Nee 15 Feb '07

15 Feb '07

hi, I am testing deliver with sieve support, and want to use it to filter chinese. But I found it doesn't work. an encoded subject: =?GB2312?B?aSBhbSBhIGNoaW5lc2U=?= decoded content is: i am a chinese and i have such rules: require "fileinto"; if header :contains "Subject" "GB2312" { fileinto "Hello"; } if header :contains "Subject" "chinese" { fileinto "Trush"; } but the first one acts. if a delete the first rule, like this: require "fileinto"; if header :contains "Subject" "chinese" { fileinto "Trush"; } message was delived to INBOX. so, any help? Thanks! -- Xueron Nee <xueron(a)gmail.com>

2 1

[Dovecot] auto-detection of user mailbox type - followup
by John Harper 15 Feb '07

15 Feb '07

In http://www.dovecot.org/list/dovecot/2006-December/018253.html Timo Sirainen wrote > > You can still change NAMESPACE_* environments. I don't remember how > exactly now, but you can do eg. "set > /tmp/sets" in the script, see > what it has set and modify them in the script. in response to my query regarding setting the mail_location in namespaces from a mail_executable script. The purpose of this is to be able to select on a per-user basis whether they're using Maildir or mbox format (I don't want to convert 12000 users all at once, and some users have no need or desire to change formats - they still use mail/elm etc) and also have the UW-IMAP compatibility namespaces to take care of all the clients currently configured with imap server directory = mail/. This all works, with one small bug left. For reference, here's the gist: In the dovecot.conf file place the usual namespace directives following the Namespaces wiki: namespace private { separator = / prefix = inbox = yes } #for UW backwards compatibility: namespace private { separator = / prefix = mail/ hidden = yes } namespace private { separator = / prefix = ~/mail/ hidden = yes } namespace private { separator = / prefix = ~%u/mail/ hidden = yes } define the mail_executable under protocol imap: mail_executable = /usr/local/dovecot/lbin/imap.sh and write the imap.sh script: ------start imap.sh--------------------------------------------------- #!/bin/sh # determine if user is in mbox or Maildir mode # Maildir takes precedence and is identified by the existence of # both a .procmailrc recipe and the Maildir directory. # Without a .procmailrc file, there's no recipe to force delivery in # Maildir format, so any existing Maildir is spurious # The .procmailrc should contain DEFAULT=Maildir/ # Set the absolute path to this script as the mail_executable for # the imap protocol in dovecot.conf. # It appears that this script is run as the user in their home dir if [ -f .procmailrc -a -d Maildir ]; then MAIL='maildir:~/Maildir'; export MAIL else MAIL='mbox:~/mail:INBOX=~/.mail'; export MAIL fi # each namespace defined in the conf file needs to have the mail # location defined which is set in environment vars # NAMESPACE_1 etc NAMESPACE_1=$MAIL; export NAMESPACE_1 NAMESPACE_2=$MAIL; export NAMESPACE_2 NAMESPACE_3=$MAIL; export NAMESPACE_3 NAMESPACE_4=$MAIL; export NAMESPACE_4 #debugging to see what else we can play with #set >> /tmp/d exec /usr/local/dovecot/libexec/dovecot/imap ------end imap.sh----------------------------------------------------- However, it appears that the root dir '~/mail' string is used at some point before the tilde-expansion takes place. I see a literal ~ directory in the users home, with an empty mail directory inside. After that it picks up the proper location and works correctly. I tried a %h and got a literal %h directory. So for now I made a simple workaround by using the absolute path to the home directory: # use home variable (depends on this script running in users home) # During startup it seems like ~/mail is interpreted as a string and # a spurious ~ folder is created, before the ~ is expanded home=`/bin/pwd` if [ -f .procmailrc -a -d Maildir ]; then MAIL="maildir:$home/Maildir"; export MAIL else MAIL="mbox:$home/mail:INBOX=$home/.mail"; export MAIL fi Thanks, John Harper ------------------------------------------------- Senior Systems Administrator Information and Instructional Technology Services University of Toronto Scarborough harper(a)utsc.utoronto.ca

2 1

[Dovecot] dovecot and libnss-ldap
by Nicolas Boullis 15 Feb '07

15 Feb '07

Hi, I've been using dovecot 0.99.14 for a few years, with libpam-ldap and libnss-ldap, and never experienced any problem with those. I expect to soon switch to dovecot 1.0rc15 (or whatever gets available in Debian Etch, hopefuly dovecot 1.0), but I've seen some warnings against dovecot+libnss-ldap... Is the problem with libnss-ldap a recent problem (I mean it was not a problem with older dovecot such as my 0.99.14)? Is it still a problem even with 1.0rc22? Is there any hope to have it fixed before 1.0? Note that while most of the users I have to deal with are in my LDAP directory, a few ones are not and are in /etc/passwd. Hence, "userdb ldap" is probably not an option for me (and I'm quite happy with configuring all my servers with PAM and NSS). Cheers, Nicolas

2 6

[Dovecot] who limit the process deliver number?
by Antonio Casado Rodríguez 15 Feb '07

15 Feb '07

Hi, i have postfix-2.3.6, dovecot-1.0-rc19 and dovecot-lda Where i limit the process number deliver, in postfix or dovecot.conf Thanks.

2 1

[Dovecot] DoveCot compression to save HDD space
by Host Expert 15 Feb '07

15 Feb '07

Hello, I am wondering if there are any possibilities to save HDD space used by emails by compressing content (not just attachements). It would be many 1000s email boxes and probably each using lot of space so would be easier if we can just compress emails somehow. Thanks, Cristian

12 28

[Dovecot] Last login fields
by Dean Manners 15 Feb '07

15 Feb '07

Hey guys, Wondering if anyone has tried to do this before - a last login timestamp field. Using mysql for auth, I figured it would be easy enough to add a timestamp field and then tack an UPDATE statement on the end of the password_query. But of course, dovecot sees this as only one statement to pass to MySQL - of which MySQL barfs at.. Any ideas on how to achieve this ? Regards __________________________________________ Dean Manners

2 2

[Dovecot] Dovecot not responding
by Andrew Hoag 15 Feb '07

15 Feb '07

Hi all, I'm pulling my hair out on this problem and wanted to throw it out there to see if anyone else had run across it. I recently restarted my server. There were some network config issues that caused the interfaces not to come back up, but my colo company got those resolved. However, after restart, my IMAPS server has stopped responding to outside requests. I can successfully access IMAP from localhost, as well as via SSH tunnelling, so I know it is working. I've tried all sorts of "listen=" configurations, and checked lsof & tcpdump to rule out other problems, but it just seems as though dovecot isn't responding. TCPDUMP (notice the TCP SYN but no response): /var/log 89# tcpdump -vvs 192 port 993 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 192 bytes 17:37:54.101518 IP (tos 0x0, ttl 112, id 56543, offset 0, flags [DF], length: 48) c-24-9-151-115.hsd1.co.comcast.net.3132 > mail.server.com.imaps: S [tcp sum ok] 1828791628:1828791628(0) win 16384 <mss 1460,nop,nop,sackOK> 17:37:58.282840 IP (tos 0x0, ttl 59, id 54721, offset 0, flags [DF], length: 60) dsl001-148-165.sfo1.dsl.speakeasy.net.39250 > mail.server.com.imaps: S [tcp sum ok] 3827175783:3827175783(0) win 5840 <mss 1460,sackOK,timestamp 1555809446 0,nop,wscale 2> 17:38:00.130267 IP (tos 0x0, ttl 112, id 56548, offset 0, flags [DF], length: 48) c-24-9-151-115.hsd1.co.comcast.net.3132 > mail.server.com.imaps: S [tcp sum ok] 1828791628:1828791628(0) win 16384 <mss 1460,nop,nop,sackOK> 17:38:01.283013 IP (tos 0x0, ttl 59, id 54722, offset 0, flags [DF], length: 60) dsl001-148-165.sfo1.dsl.speakeasy.net.39250 > mail.server.com.imaps: S [tcp sum ok] 3827175783:3827175783(0) win 5840 <mss 1460,sackOK,timestamp 1555810196 0,nop,wscale 2> LSOF: /var/log 91# lsof -i | grep imap sshd 4475 andrew 11u IPv4 39601 TCP localhost:34661->localhost:imaps (ESTABLISHED) dovecot 6540 root 5u IPv4 38988 TCP *:imaps (LISTEN) imap-logi 6599 dovecot 9u IPv4 39602 TCP localhost:imaps->localhost:34661 (ESTABLISHED) imap-logi 6629 dovecot 1u IPv4 38988 TCP *:imaps (LISTEN) imap-logi 6630 dovecot 1u IPv4 38988 TCP *:imaps (LISTEN) NETSTAT: /var/log 92# netstat -an | grep 993 tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:993 127.0.0.1:34661 ESTABLISHED tcp 0 0 127.0.0.1:34661 127.0.0.1:993 ESTABLISHED STRACE: 17:00:33.225030 gettimeofday({1171501233, 225048}, {480, 0}) = 0 17:00:33.225072 gettimeofday({1171501233, 225090}, NULL) = 0 17:00:33.225113 poll([{fd=7, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=1, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 4, 0) = 0 17:00:33.225163 gettimeofday({1171501233, 225182}, {480, 0}) = 0 17:00:33.225212 gettimeofday({1171501233, 225230}, NULL) = 0 17:00:33.225260 poll([{fd=7, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=1, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 4, 999) = 0 17:00:34.225145 gettimeofday({1171501234, 225179}, {480, 0}) = 0 17:00:34.225204 gettimeofday({1171501234, 225222}, NULL) = 0 17:00:34.225246 poll([{fd=7, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=1, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 4, 0) = 0 17:00:34.225297 gettimeofday({1171501234, 225315}, {480, 0}) = 0 Has anyone seen this behavior? What's the obvious thing I'm missing here? My host has some weird VLAN thing installed by the colo company so I have IP aliases, but given I'm not even seeing a response to the SYN, it doesn't seem to be a routing issue, and I can connect to my local interface on port 993 (NOT localhost) without problems. Suggestions much appreciated, I'm stuck. I'm sure this is something obvious and simple, but I'm looking past it right now. Andrew -- Email: andrew(a)50degreescorp.com <mailto:andrew@50degreescorp.com>

2 1

[Dovecot] OT: looking for plugin developer
by Tom Bombadil 15 Feb '07

15 Feb '07

Greetings all, We are looking for a developer to write a plugin that copies the message to a specific hidden folder called "spam_copy" when a message inside a folder called "spam" is viewed for the first time. And when we move the message from the "spam" folder to any other folder, and if the message hasn't been seen, we should send a copy of it to "spam_copy" hidden folder, in addition to the move. If anybody is up for it, please send me a private message, so we can arrange all the details, payment, etc... Thanks in advance.

1 0

[Dovecot] Changing the Seen Flags
by Amardeep Singh 15 Feb '07

15 Feb '07

Hi , Can we change the setting on dovecot so that the Seen mail flag S should be saved where everybody can see that and not in the dovecot.index file As we are facing problems with public folder read/unread mails. Any help is appreciated Thanks, Amardeep

3 5

[Dovecot] incorrect quota reporting with dict quota
by Marshal Newrock 14 Feb '07

14 Feb '07

Using the dict quota with dovecot-1.0.rc21, quota reporting was incorrect. It wasn't just that the stored quota was different than the disk usage, but also that each time the quota was checked, it was greater than before, even if no mail was received. I tested this by using telnet to log into an imap account, and issuing multiple "getquotaroot inbox" commands. I have changed to just using maildir quotas, and everything seems correct now. Thanks to dovecot's flexible authentication methods, I'll be able to set an individual account to use the dict quota backend for testing. -- Marshal Newrock, Ideal Solution LLC http://www.idealso.com

2 1

[Dovecot] lda quota in sql works but is ignored
by Robert Schetterer 14 Feb '07

14 Feb '07

Hi, (dovecot latest vers) i have lda deliver up with quota and sql, but it seems that deliver simply ignores it, normally it should bounce the message deliver(tester(a)example.de): Feb 13 15:31:32 Info: auth input: gid=1001 deliver(tester(a)example.de): Feb 13 15:31:32 Info: auth input: quota=dirsize:storage=3072000 deliver(tester(a)example.de): Feb 13 15:31:32 Info: Home dir not found: /usr/local/virtual/tester(a)example.de/ deliver(tester(a)example.de): Feb 13 15:31:32 Info: Loading modules from directory: /usr/lib64/dovecot/modules/lda deliver(tester(a)example.de): Feb 13 15:31:32 Info: Module loaded: /usr/lib64/dovecot/modules/lda/lib10_quota_plugin.so deliver(tester(a)example.de): Feb 13 15:31:32 Info: Module loaded: /usr/lib64/dovecot/modules/lda/lib90_cmusieve_plugin.so deliver(tester(a)example.de): Feb 13 15:31:32 Info: maildir: data=/usr/local/virtual/tester(a)example.de/ deliver(tester(a)example.de): Feb 13 15:31:32 Info: maildir: root=/usr/local/virtual/tester(a)example.de, index=/usr/local/virtual/tester(a)example.de, control=, inbox= deliver(tester(a)example.de): Feb 13 15:31:32 Info: dirsize quota limit = 3072000kB deliver(tester(a)example.de): Feb 13 15:31:32 Info: msgid=<20070213143132.012C982EF(a)mail.example.de>: saved mail to INBOX /usr/local/virtual/tester(a)example.de # du -h 4,0K ./tmp 4,0K ./cur 5,3M ./new 5,3M . any idea? -- Mit freundlichen Gruessen Best Regards Robert Schetterer https://www.schetterer.org Munich/Bavaria/Germany

3 4

[Dovecot] environment variables required for startup
by Marshal Newrock 14 Feb '07

14 Feb '07

Using dovecot-1.0-rc19 (quotas are working good, btw) on Gentoo, I have a strange problem. On boot, dovecot doesn't start, the init script just times out. From the command line, it starts instantly without problem. Also, using a program called 'monit' to make sure processes stay running and restart them if they stop, if I manually stop dovecot, it is then unable to start it (calling the init script). Nothing gets logged. In all cases, it's "/etc/init.d/dovecot start". The only thing I can think of is that there's some environment variable required which isn't being set. monit specifically says it unsets everything except for a basic path before running the start program. Do any environment variables need to be set in order for dovecot to start successfully? -- Marshal Newrock Ideal Solution, LLC - http://www.idealso.com

4 8

[Dovecot] migration question: "imap server directory"
by Dan Price 14 Feb '07

14 Feb '07

In prepping our IMAP migration to Dovecot, I've hit upon a small issue: the "IMAP server directory" which Thunderbird users have set in the "advanced" prefs. Our old IMAP server seems to set your current directory to ~. This wound up causing users to set their IMAP server directory to "/home/<user>/mail/" so that their mailboxes would be found: --> A104 LIST "/home/dp/mail/" "%" * LIST (\NoSelect) "/" /home/dp/mail/ * LIST (\NoInferiors \UnMarked) "/" /home/dp/mail/sent-mail-Jul-2006 * LIST (\NoInferiors \UnMarked) "/" /home/dp/mail/sent-mail-Dec-2004 ... A104 OK LIST completed Of course, relative paths also work, but it seems that not many users are using them: --> A105 LIST "mail/" "%" * LIST (\NoSelect) "/" mail/ * LIST (\NoInferiors \UnMarked) "/" mail/sent-mail-Jul-2006 * LIST (\NoInferiors \UnMarked) "/" mail/sent-mail-Dec-2004 ... A105 OK LIST completed Also, it turns out that some users have mail in "mail" and some in "Mail". So for now, with Dovecot, I've set: mail_location = mbox:~:INBOX=/var/mail/%u:INDEX=%h/Mail/imapd-indices But users with absolute paths are having issues: A102 LIST "/home/dp/mail/" "%" A102 OK List completed. Versus: A103 LIST "mail/" "%" * LIST (\Noselect \HasChildren) "/" "mail/" * LIST (\NoInferiors \UnMarked) "/" "mail/sent-mail-Jul-2006" * LIST (\NoInferiors \UnMarked) "/" "mail/sent-mail-Dec-2004" A103 OK List completed. I've read the MailboxLocation page on the Wiki, but I'm not sure of the best way to proceed and have things stay compatible for my users. It is possible to ask all users to change, but I'm going to have to field a lot of questions if I ask users for that :/ Thanks! -dp -- Daniel Price - Solaris Kernel Engineering - dp(a)eng.sun.com - blogs.sun.com/dp

3 2

[Dovecot] quota interferes with dovecot
by jepoy 14 Feb '07

14 Feb '07

hi guys, im having some trouble on my quota.whenever my client reaches the quota, they cant download their mails anymore. +OK Dovecot 1.0 ready. user test +OK pass testd -ERR [IN-USE] Couldn't sync mailbox. +OK Logged in. Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity. Account: , Protocol: POP3, Port: 110, Secure(SSL): No, Socket Error: 10053, Error Number: 0x800CCC0F -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

3 2

[Dovecot] info deleted messages imap
by Hola 14 Feb '07

14 Feb '07

Hi! I want to know the number of messages deleted when the mail user connect by IMAP protocol. When the user uses POP, we got this directive in the configuration file: pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s This is the log: dovecot: Feb 09 02:31:02 Info: pop3-login: Login: user=<xxxxxx>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Feb 09 02:31:02 Info: POP3(xxxxx): Disconnected: Logged out top=2/3756, retr=0/0, del=0/7, size=17392 If you look at "del=0/7" we know that user deleted 0 messages. When the user log in the account by IMAP protocol, appears the following: dovecot: Feb 09 02:02:36 Info: imap-login: Login: user=<xxxxx>, method=PLAIN, rip=82.xxx.xxx.xxx, lip=82.xxx.xxx.xxx dovecot: Feb 09 02:03:02 Info: IMAP(xxxxx): Disconnected: Logged out And we donÂ´t know the number of messages deleted, the question is: there is any directive like "pop3_logout_format" applied to IMAP?? Something like "imap_logout_format" ?? Dovecot version: 1.0.rc17.

2 1

[Dovecot] Rawlogs in freebsd?
by Francisco Reyes 14 Feb '07

14 Feb '07

I am trying to enable rawlogs. I made a directory /home/dovecot/dovecot.rawlog/, changed dovecot.conf to have mail_executable = /usr/local/libexec/dovecot/rawlog /usr/local/libexec/dovecot/imap Made sure the /home/dovecot/dovecot.rawlog/ could be written to. Even made it 1777 as a test. Made sure the FreeBSD user database points /home/dovecot as the dovecot user's directory (left shell as nologin). Compiled dovecot from ports and using Dovecot 1.0.r21. Still no rawlog. Any pointers?

2 1

[Dovecot] Question about migration from tpop3d mbox -> Dovecot maildir
by Vladimir Koshelenko 14 Feb '07

14 Feb '07

Yes, again! :) I googled this issue but found no solution. Then, simple question - on this moment, it is possible without losing UIDLs or not?

2 1

[Dovecot] Some users cannot login
by Frank Bonnet 14 Feb '07

14 Feb '07

Hello I am in trouble with certain logins that cannot log in through Dovecot IMAP ... I've tried both with flat passwd or NIS It is possible to login with ssh ou to su - xxxx on the machine but it seems that the dovecot imap refuse to authenticate some users ... the dovecot version is the latest

3 2

[Dovecot] Problems to put dovecot-ldap.conf working
by Venilton Junior 14 Feb '07

14 Feb '07

Hi Folks, I'm having a little trouble to put dovecot authenticating in ldap. My postfix and saslauthd are authenticating fine. Here is what I have in my main.cf: # Accounts accounts_server_host = $ldap_server_host accounts_search_base = $ldap_search_base accounts_query_filter = (&(&(objectClass=VirtualMailAccount)(mail=%s))(forwardActive=FALSE)(acco untActive=TRUE)(delete=FALSE)) accounts_result_attribute = mailbox accounts_cache = no # aliases aliases_server_host = $ldap_server_host aliases_search_base = $ldap_search_base aliases_query_filter = (&(&(objectClass=VirtualMailAlias)(mail=%s))(accountActive=TRUE)) aliases_result_attribute = maildrop aliases_cache = no accountsmap_server_host = $ldap_server_host accountsmap_search_base = $ldap_search_base accountsmap_query_filter = (&(&(objectClass=VirtualMailAccount)(mail=%s))(forwardActive=FALSE)(acco untActive=TRUE)(delete=FALSE)) accountsmap_result_attribute = mail accountsmap_cache = no # VirtualForward virtualforward_server_host = $ldap_server_host virtualforward_search_base = $ldap_search_base virtualforward_query_filter = (&(&(objectClass=VirtualMailAccount)(mail=%s))(forwardActive=TRUE)(accou ntActive=TRUE)(delete=FALSE)) virtualforward_result_attribute = maildrop virtualforward_cache = no My saslauthd.conf follows as: ldap_servers: ldap://myldapserver/ ldap_version: 3 ldap_auth_method: bind ldap_bind_dn: uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot ldap_bind_pw: xxxx ldap_search_base: dc=domain,dc=com #ldap_filter: (|(mail=%u)(cn=%U)) ldap_filter: (&(|(mail=%u)(cn=%U)(mail=%U@%d))(accountActive=TRUE)(delete=FALSE)) PS: Removed my real server and search_base. Here is the test with saslauthd configuration: testsaslauthd -u novoemail01 -p teste123 0: OK "Success." And here is my dovecot-ldap.conf: hosts = myldapserver dn = uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot dnpass = xxxx ldap_version = 3 base = dc=domain,dc=com user_attrs = mail,,,,, user_filter = (&(objectClass=VirtualMailAccount)(mail=%u)(accountActive=TRUE)(delete=F ALSE)) pass_attrs = mail,userPassword pass_filter = (&(objectClass=VirtualMailAccount)(mail=%u)(accountActive=TRUE)(delete=F ALSE)) default_pass_scheme = SSHA When I try to authenticate, my mail.info get this: dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=200.155.34.10 rip=200.155.63.82 resp=AG5vdm9lbWFpbDAxAHRlc3RlMTIz dovecot: auth(default): ldap(novoemail01,200.155.63.82): pass search: base=dc=sercomtel,dc=com,dc=br scope=subtree filter=(&(objectClass=VirtualMailAccount)(mail=novoemail01)(accountActiv e=TRUE)(delete=FALSE)) fields=mail,userPassword dovecot: auth(default): ldap(novoemail01,200.155.63.82): unknown user dovecot: auth(default): client out: FAIL 1 user=novoemail01 Does anyone have an idea where I'm failing to configure this or find a misconfiguration? Tnx for any help. Best Regards, Venilton C. Junior

2 1

[Dovecot] resilience suggestion
by David Lee 14 Feb '07

14 Feb '07

On the whole we are pleased with our trials of dovecot to replace UW-IMAP. But (ah!) we have hit one particular problem, in which we think dovecot could probably benefit from a resilience improvement. We're running dovecot on Fedora Core 5 (FC5), with passwd map details supplied by NIS. We have found that "nscd" sometimes thinks that a username is invalid, even though it is valid. So when "deliver" attempts a delivery to the INBOX of that username, it receives "user unknown" from the name service, and then does a 5xx permanent failure of valid email. >From the user perspective "The System" has incorrectly rejected perfectly valid incoming email. It is rare, but it does occasionally happen on large, busy systems. Clearly it is fundamentally an "nscd" bug. But that bug is nevertheless out there, in the wild, on such systems, potentially affecting dovecot's delivery of valid user email. We have had a source code hack since October (in "deliver.c", simply replacing a "return ret" occurence with "return EX_TEMPFAIL") and it has worked nicely (ported forward from rc8 towards rc22). Mail re-queues and a later delivery attempt then succeeds. So it would be both helpful, and good for resilience against such real OS/nscd bugs (and similar), if there were a configuration option in dovecot to allow a site admin to tell deliver to use a temporary, 4xx, failure instead (if the circumstances were appropriate for the site). Could this be considered please, Timo? -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : UNIX Team Leader Durham University : : South Road : : http://www.dur.ac.uk/t.d.lee/ Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. :

9 15

[Dovecot] Ubuntu, Exim, deliver: permissions/setgid problem
by Sam Hathaway 14 Feb '07

14 Feb '07

Hello all, I have a little problem. I'm trying to set up Dovecot deliver (1.0 beta 3) as the LDA for Exim4 on Ubuntu 6.06 with MBOX, and I'm running into permissions problems. Exim typically wants to run pipes as the user to whom the mail is being delivered (as per the "check_local_user"). deliver needs access to the auth socket and needs to be able to create files in /var/mail. In Ubuntu, /var/mail is writeable by group mail, but not by others. So I thought I'd make deliver run as the user to whom the mail is being delivered (as per default) and with group "mail" (so it can create files in /var/mail). I also set the auth socket to be group-writeable and gave it the group mail. So theoretically, deliver should be able to: - connect to the socket - create dotfiles in /var/mail - write to the user's mailbox The problem I'm running into is that deliver tries to setgid to the primary group of the target user, and dies when it can't. I specifically do NOT want it to do this, because regular users don't have permission to write to /var/mail. I've also tried making deliver SUID root (as recommended on this list) or SGID mail (like procmail is) but I get the same error. If I also disable the "group = mail" line in the dovecot_deliver_user router in exim4.conf, I still get the same error. If I disable the "group = mail" line without making deliver SUID or SGID, then it can no longer connect to the auth socket. In this case it runs with the group of the user for whom the mail is being delivered, i.e. sam-adm (#10000). I've also tried adding "user = mail" to the transport, to no avail. The ONE way I've been able to make it work is to remove "group = mail" from exim4.conf and set the socket's mode to 0666, but I've seen warnings that allowing world-access to the socket is dangerous. I'm actually not sure why this works, since in this case it's running with both the UID and GID of the target user, and therefore shouldn't be able to create files in /var/mail. Can anyone untangle this for me? From what I've read, in Debian delivery agents should run with group "mail" (procmail is SGID mail). It seems to me that the way to go is to spawn it with group mail, allow group mail access to the auth socket, and be done with it. But this is prevented from working since it insists on resetting back to the user's primary group. Thanks, Sam Hathaway The relevent section of my dovecot.conf looks like this: protocol lda { postmaster_address = postmaster(a)uofr.net log_path = /var/log/dovecot-lda.log } auth default { mechanisms = plain socket listen { master { path = /var/run/dovecot-auth-master mode = 0660 group = mail } } # ... (other auth config directives here) } And the relevent parts of my exim4.conf are as follows: # in router section: local_user: debug_print = "R: local_user for $local_part@$domain" driver = accept domains = +local_domains check_local_user local_part_suffix = +* local_part_suffix_optional local_parts = ! root transport = dovecot_deliver_user # in transport section: dovecot_deliver_user: debug_print = "T: pipe for $local_part@$domain" driver = pipe command = /usr/lib/dovecot/deliver -d $local_part message_prefix = message_suffix = log_output delivery_date_add envelope_to_add return_path_add group = mail Here are the permissions on some interesting files/dirs: -rwxr-xr-x 1 root mail 551424 2006-11-22 21:59 /usr/lib/dovecot/deliver drwxrwsr-t 2 root mail 1024 2007-01-25 14:14 /var/mail -rw-rw---- 1 sam-adm mail 544 2007-01-25 15:58 /var/mail/sam-adm srw-rw---- 1 root mail 0 2007-01-25 15:39 /var/run/dovecot-auth-master And here's how I've been testing: echo "test" | mail -s "deliver test" sam-adm When I execute the above command, exim says: 2007-01-25 15:55:01 1HABcb-0006h4-N8 <= sam-adm(a)vps.uofr.net U=sam-adm P=local S=334 2007-01-25 15:55:02 1HABcb-0006h4-N8 ** sam-adm(a)vps.uofr.net R=local_user T=dovecot_deliver_user: Child process of dovecot_deliver_user transport returned 89 from command: /usr/lib/dovecot/deliver 2007-01-25 15:55:02 1HABcb-0006h4-N8 Completed And deliver says: deliver: "2007-01-25 15:55:02 "Fatal: setgid(10000) failed: Operation not permitted

3 6

[Dovecot] http://wiki.dovecot.org/VirtualhostingWithExim
by Marc Haber 14 Feb '07

14 Feb '07

Hi, Here is a new wording for the "Exim4 on Debian" part of the web page on http://wiki.dovecot.org/VirtualhostingWithExim. It's immutable, so I cannot directly change it. I e-mailed Florian, but he cannot log in to the wiki any more. Can somebody with appropriate privileges change the page? --------------------- If you are using the exim4 packages on Debian, you need to pay attention whether you are using the split or non-split configuration method that the packages offer. If you are using split-configuration, you need to apply the configuration changes to the router and transport directories inside /etc/exim4/conf.d; if you are using non-split configuration, you need to edit /etc/exim4/exim4.conf.template. A restart of the exim daemon with /etc/init.d/exim4 reload will activate your changes. You can find more information about the way Debian configures the exim4 packages in /usr/share/doc/exim4-base/README.Debian or at http://pkg-exim4.alioth.debian.org/README/README.Debian.html or at the Debian wiki (http://wiki.debian.org/PkgExim4) --------------------- Additionally, I would appreciate if the instructions for exim 3 could be removed. exim 3 is obsolete five years now, and new users of exim 4 are constantly finding old exim 3 documentation and fail in applying that docs to exim 4. Greetings Marc, Maintainer for Debian exim4 packages -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835

1 0

[Dovecot] .bz2 plugin?
by David McBride 14 Feb '07

14 Feb '07

Hello all, Is anyone working on a .bz2 plugin similar to the existing zlib plugin? Cheers, David -- David McBride <dwm(a)tastycake.net>

2 1

[Dovecot] dead bodies stacking up in Drafts folder
by Charles Bueche 14 Feb '07

14 Feb '07

Hi, Setup : Apple Mail 2.1.1 (752.3) on Intel MacBook Pro and Dovecot 1.0rc22 on Solaris 9/SPARC. I use IMAP/TLS. Problem : mails are stacking up in the Drafts folder. When I start writing a mail, it appears in the drafts folder, and usually disappear as desired when I hit "Send". It then appear in the "Sent" folder. Sometimes, a draft versions stays in "Drafts", I have 21 of them since 1.1.2007. In this period, I have written about 400 emails, so only about 5 % stick in "Drafts". I can of course periodically select and delete them, but I don't like such glitches. Never sure if emails are really sent. Advice welcome. I'm the Solaris packager and admin so I can test things if needed. Sorry if it's a known Apple Mail issue, I would be the one to beat for using closed-source stuff :-) Charles -- Charles Bueche <charles(a)bueche.ch> sand, snow, wave, wind and net -surfer A-Cat SUI 192

7 9

[Dovecot] [Fwd: Re: Is it 1.0 yet?]
by Gavin Henry 14 Feb '07

14 Feb '07

---------------------------- Original Message ---------------------------- Subject: Re: [Dovecot] Is it 1.0 yet? From: "Raymond Lillard" <ryl(a)plasmaequip.com> Date: Tue, February 13, 2007 11:16 pm To: "Gavin Henry" <ghenry(a)suretecsystems.com> -------------------------------------------------------------------------- -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gavin Henry wrote: > <quote who="Marc Perkel"> >> OK - my last main bug was fixed a few releases ago. I know that there's >> no end to getting things right but there comes a point when you need to >> call it done. No one trusts a 1.0 to be perfect but Dovecot is already >> better that most 2.0 versions of other software. >> >> I vote (as if my vote counted) to call it done, declare victory, and >> move on to 1.01, 1.02 etc. No one is going to trus it till it gets to >> 1.02 so I say lets bless it and move on. >> >> > > +1 > > +2 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF0kbLW6j0KQLSyTQRAhbZAJ0SAJDaNES4wV+UajiKJ0ByObbP5gCfXfdv CU2v+W+diqDAnarYRncXj2s= =XTcI -----END PGP SIGNATURE-----

1 0

[Dovecot] Chdir Permission Denied
by Jamie Heinzel 13 Feb '07

13 Feb '07

Here are the error messages I get when anyone tries to login. Feb 13 11:22:17 mail dovecot: chdir(/home/don150) failed with uid 776: Permission denied Feb 13 11:22:17 mail imap-login: Login: don150 [::ffff:192.168.146.10] Feb 13 11:22:17 mail dovecot: child 12101 (imap) returned error 89 I am not running SELinux so I'm not sure what is happening here. All was working fine this morning, then at about 9:30 am nobody could log in. Any help would be great. Thanks!

2 2

Re: [Dovecot] [Fwd: Disable a User's email account]
by Steffen Kaiser 13 Feb '07

13 Feb '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 13 Feb 2007, Michael Surette wrote: Hello, I'm not sure why you'd not mail this info the one, who had created the thread. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRdHa9y9SORjhbDpvAQLFoQf+PZUZZ6bHwhcKIh+8eTK3h4wEuF0lAqjE zuOjOC5D08bOgY86qt84vWqA+MYt9QTCXTPlTFxQYQESf5IgqgwKbPbl0PHxoc/1 GOddQ+Hd7I9lt42iWukqYtd6LGAV6CTIhZIFRm6uVnZYm1Or+3kiyFhiwMwkxSKF NfcsUYVenAhtfNSXOEALaBhvzdD/uUsZX/G/whq6y9A2xPOE25zdVxLPLP+F+mk3 enShwoGa1AMV6snOOEJIRkJ4QwuCacjuQjduyBKpn72rQukZBrHoJes8DOGdIKSx 3BrFz6ck+H+7hHt+vH6ukk2fRO7nkheltrMiCc22Uf97UIychHNrOA== =NWw9 -----END PGP SIGNATURE-----

1 0

[Dovecot] Apple mail
by Аркадий Володин 13 Feb '07

13 Feb '07

I have strange situation with Appe mail and latest (rc22) Dovecot. I using "mbox" POP3 (not IMAP) type of message box on server (exim: driver=appendfile) I also using MySQL authentification and SSL. Server - Linux Slackware 11.0 Linux/Thunderbird, WinXP/Thunderbird, WinXP/Outlook clients are working fine with their message boxes. But Apple mail doesn't delete messages in user's mbox, so client gets a lot of duplicate messages. As I see in such a mbox, there isn't system message like: >From MAILER_DAEMON Tue Feb 13 14:41:08 2007 Date: Tue, 13 Feb 2007 14:41:08 +0000 From: Mail System Internal Data <MAILER-DAEMON@mail> Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA Message-ID: <1171377668@mail> X-IMAP: 1169824263 0000000019 Status: RO But every message in such a box marked as "Status: RO" Please, help me to solve this trouble.

1 0

[Dovecot] error message after migration UW --> DOVECOT
by Frank Bonnet 13 Feb '07

13 Feb '07

Hello I get a lot of messages looking as above since I migrate from UW dovecot: Feb 13 10:27:44 Error: IMAP(xxxxxxxx): mbox sync: UID inserted in the middle of mailbox /user/xxxxxxxx/Trash (7 > 5, seq=2, idx_msgs=2) What would be the impact for my users ? Thanks a lot Frank

2 1

[Dovecot] [Fwd: Disable a User's email account]
by edwardspl＠ita.org.mo 13 Feb '07

13 Feb '07

Dear All, The System is FC6... So, how to disbale a User's mail service ? eg : Sendmail ( SMTP ) + Dovecot ( pop3 /imap ). Edward. -- fedora-list mailing list fedora-list(a)redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

6 12

[Dovecot] PAM, NSS, and a new blocking=yes setting
by Timo Sirainen 13 Feb '07

13 Feb '07

I wondered for a while if I should do this before v1.0, but since there seem to be problems with some PAM/NSS users and this was way easier to implement than I realized, here it is: passdb pam and userdb passwd now support blocking=yes setting in their args. For PAM the default has been to fork the dovecot-auth process and talk via a pipe to the main dovecot-auth. I've never really liked this approach, but didn't bother fixing it before. However it is also what has caused the bugs with nss_ldap, and maybe with other NSS backends too. NSS lookups then have been done all in the same dovecot-auth process without any forking. This meant that if it got stuck (or delayed a bit in LDAP queries and such), the whole dovecot-auth got stuck and all authentication attempts got stuck. With blocking=yes the lookups are handled in dovecot-auth worker processes. Earlier these workers have been used only with MySQL. Initially there is only a single worker process, but whenever dovecot-auth notices that there are no free workers while a new auth request comes, a new worker is created. auth_worker_max_count specifies the maximum number of those processes. This blocking=yes will probably work great with NSS. With PAM I'm not so sure. Mostly because the worker never exits, it just does one PAM auth after another. I think usually PAM is used only once in a process, so there might be memory leaks and maybe other bugs.. Then again, maybe not. I'll add some auth_worker_max_requests setting which can be set to 1 if this is a problem. Also for blocking=no case I added code to send KILL signal to PAM child processes which haven't replied for 2 minutes. With blocking=yes this condition can't be checked currently. http://dovecot.org/list/dovecot-cvs/2007-February/007639.html http://dovecot.org/list/dovecot-cvs/2007-February/007642.html http://dovecot.org/list/dovecot-cvs/2007-February/007646.html

2 2

[Dovecot] MD5-CRYPT passwords in a MySQL Database
by David Mills 13 Feb '07

13 Feb '07

First of all, hello to the list. I'm currently migrating from a /etc/passwd and /etc/shadow based configuration to a MySQL based one using dovecot 99.14 on debian sarge. The problem is that the /etc/shadow containes both DES encoded (Crypt) and md5 based passwords. I've set the default system to be Crypt, and have added {MD5-CRYPT} in front of the md5 passwords in place of the $1$ header found in /etc/shadow. But I can only log in on accounts that have DES based passwords. I've included my dovecot configuration, and below are 2 examples of encoded password, one crypt and one MD5: XalGYN3cy1crA {MD5-CRYPT}RL$Bvv.TF2XJkyVI6JOUO8tx/ If anyone has any ideas I'd really appreciate them since 80 odd accounts have this problem, so changing them one by one will be difficult. David -- David Mills Enki Technologies 01 76 00 71 20 *De nouvelles offres d'emploi...* *...pour bien démarrer 2007 !* Consulter la news <http://www.enki.fr/detail_actualite.htm?ACTU=13> - enki.fr <http://www.enki.fr> ## Dovecot 1.0 configuration file # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc/dovecot # --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 protocols = imaps pop3 pop3s # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port". #imap_listen = * #pop3_listen = * # IP or host address where to listen in for SSL connections. Defaults # to above non-SSL equilevants if not specified. #imaps_listen = #pop3s_listen = # Disable SSL/TLS support. #ssl_disable = no # 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. #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # 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 = 24 # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # 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 = /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. # http://wiki.dovecot.org/Rootless #login_chroot = yes ## ## IMAP login process ## login = imap # Executable location. #login_executable = /usr/lib/dovecot/imap-login # 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. # http://wiki.dovecot.org/UserIds #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 = 32 # 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 create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra 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 limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 ## ## POP3 login process ## # Settings default to same as above, so you don't have to set anything # unless you want to override them. login = pop3 # Exception to above rule being the executable location. #login_executable = /usr/lib/dovecot/pop3-login ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # 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 = no # Show protocol level SSL errors. #verbose_ssl = no # 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 = 106 #last_valid_uid = 0 # 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 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. mail_extra_groups = mail # ':' 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 or auth_chroot variables. # 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. See # /usr/share/doc/dovecot-common/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden by # giving /./ in user's home directory (eg. /home/./user chroots into /home). #mail_chroot = # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # /usr/share/doc/dovecot-common/mail-storages.txt. There's a few special # variables you can use: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain # %h - home directory # # You can also limit a width of string by giving the number of max. characters # after the '%' character. For example %1u gives the first character of # username. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # Space-separated list of fields to cache for all mails. Currently these # fields are allowed followed by a list of commands they speed up: # # Envelope - FETCH ENVELOPE and SEARCH FROM, TO, CC, BCC, SUBJECT, # SENTBEFORE, SENTON, SENTSINCE, HEADER MESSAGE-ID, # HEADER IN-REPLY-TO # Body - FETCH BODY # Bodystructure - FETCH BODY, BODYSTRUCTURE # MessagePart - FETCH BODY[1.2.3] (ie. body parts), RFC822.SIZE, # SEARCH SMALLER, LARGER, also speeds up BODY/BODYSTRUCTURE # generation. This is always set with mbox mailboxes, and # also default with Maildir. # # Different IMAP clients work in different ways, that's why Dovecot by default # only caches MessagePart which speeds up most operations. Whenever client # does something where caching could be used, the field is automatically marked # to be cached later. For example after FETCH BODY the BODY will be cached # for all new messages. Normally you should leave this alone, unless you know # what most of your IMAP clients are. Caching more fields than needed makes # the index files larger and generate useless I/O. # # With maildir there's one extra optimization - if nothing is cached, indexing # the maildir becomes much faster since it's not opening any of the mail files. # This could be useful if your IMAP clients access only new mails. #mail_cache_fields = MessagePart # Space-separated list of fields that Dovecot should never set to be cached. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. Note that OE6 still breaks even with this workaround # if synchronization is set to "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # outlook-pop3-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. #client_workarounds = # Dovecot can notify client of new mail in selected mailbox soon after it's # received. This setting specifies the minimum interval in seconds between # new mail notifications to client - internally they may be checked more or # less often. Setting this to 0 disables the checking. # NOTE: Evolution client breaks with this option when it's trying to APPEND. #mailbox_check_interval = 0 # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # 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 # Maximum allowed length for custom flag name. It's only forced when trying # to create new flags. #mail_max_flag_length = 50 # 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. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. #mail_read_mmaped = no # By default LIST command returns all entries in maildir beginning with 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 # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing messages are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three 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. # 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. # # You can use both fcntl and flock too; if you do the order they're declared # with is important to avoid deadlocks if other MTAs/MUAs are using both fcntl # and flock. Some operating systems don't allow using both of them # simultaneously, eg. BSDs. If dotlock is used, it's always created first. #mbox_locks = dotlock fcntl # Should we create dotlock file even when we want only a read-lock? Setting # this to yes hurts the performance when the mailbox is accessed simultaneously # by multiple processes, but it's needed for reliable reading if no other # locking methods are available. #mbox_read_dotlock = no # 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 = 30 # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. Note that setting # this to yes means that log file is opened as the logged in user, which # might not work. It could also 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 ## ## IMAP process ## # Executable location #imap_executable = /usr/lib/dovecot/imap # 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. #imap_process_size = 256 # Support for dynamically loadable modules. #imap_use_modules = no #imap_modules = /usr/lib/dovecot/imap ## ## POP3 process ## # Executable location #pop3_executable = /usr/lib/dovecot/pop3 # 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. #pop3_process_size = 256 # Support for dynamically loadable modules. #pop3_use_modules = no #pop3_modules = /usr/lib/dovecot/pop3 ## ## Authentication processes ## # An Authentication process is a child process used by Dovecot that # handles the authentication steps. The steps cover an authentication # mechanism (auth_mechanisms, how the client authenticates in the IMAP or # POP3 protocol), which password database should be queried (auth_passdb), # and which user database should be queried (auth_userdb, to obtain # UID, GID, and location of the user's mailbox/home directory). # # You can have multiple processes, though a typical configuration will # have only one. Each time "auth = xx" is seen, a new process # definition is started. The point of multiple processes is to be able # to set stricter permissions. (See auth_user below.) # # Just remember that only one Authentication process is asked for the # password, so you can't have different passwords accessible through # different process definitions (unless they have different # auth_mechanisms, and you're ok with having different password for # each mechanisms). # Authentication process name. auth = default # Specifies how the client authenticates in the IMAP protocol. # Space separated list of permitted authentication mechanisms: # anonymous plain digest-md5 cram-md5 # # anonymous - No authentication required. # plain - The password is sent as plain text. All IMAP/POP3 clients # support this, and the password can be encrypted by Dovecot to match # any of the encryption schemes used in password databases. # digest-md5 and cram-md5 - both encrypt the password so it is more # secure in transit, but are not well supported by clients, and # require that the password database use a matching encryption # scheme (or be in plaintext). # # See auth.txt for more details. # # If you are using SSL there is less benefit to digest-md5 and # cram-md5 as the communication is already encrypted. auth_mechanisms = plain # 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 = # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see /etc/dovecot/dovecot-ldap.conf # mysql <config path>: a MySQL database, see /etc/dovecot/dovecot-mysql.conf # pgsql <config path>: a PostgreSQL database, see # /etc/dovecot/dovecot-pgsql.conf auth_userdb = passwd #auth_userdb = static uid=139 gid=139 home=/home/users/%u/ # Password database specifies only the passwords for users. # http://wiki.dovecot.org/Authentication # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see /etc/dovecot/dovecot-ldap.conf # mysql <config path>: a MySQL database, see /etc/dovecot/dovecot-mysql.conf # pgsql <config path>: a PostgreSQL database, see # /etc/dovecot/dovecot-pgsql.conf #auth_passdb = shadow auth_passdb = mysql /etc/dovecot/dovecot-mysql.conf #auth_executable = /usr/lib/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # 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 auth_userdb above. auth_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. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # 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 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 # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_mechanisms = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-md5" # For the mysql passdb module, you'll need a database with a table that # contains fields for at least the userid and password. If you want to # use the user@domain syntax, you might want to have a separate domain # field as well. # # If your users all have the same uig/gid, and have predictable home # directories, you can use the static userdb module to generate the home # dir based on the userid and domain. In this case, you won't need fields # for home, uid, or gid in the database. # # If you prefer to use the mysql userdb module, you'll want to add fields # for home, uid, and gid. Here is an example table: # # CREATE TABLE users ( # userid VARCHAR(128) NOT NULL, # password VARCHAR(64) NOT NULL, # home VARCHAR(256) NOT NULL, # uid INTEGER NOT NULL, # gid INTEGER NOT NULL, # active CHAR(1) DEFAULT 'Y' NOT NULL # ); db_host = localhost db_port = 3306 db_unix_socket = /var/run/mysqld/mysqld.sock db = mail db_user = dovecot db_passwd = 3eDcVb db_client_flags = 0 # Default password scheme. # # Currently supported schemes include PLAIN, PLAIN-MD5, DIGEST-MD5, and CRYPT. # default_pass_scheme = CRYPT # Query to retrieve the password. # # The query should return one row, one column. If more than one row or column # is returned, authentication will automatically fail. # # Available substitutions: # %u = entire userid # %n = user part of user@domain # %d = domain part of user@domain # # Example: # password_query = SELECT password FROM users WHERE userid = '%n' AND domain = '%d' # password_query = SELECT password FROM users WHERE userid = '%u' AND active = 'Y' # password_query = SELECT password FROM enki_users WHERE username = '%u' # Query to retrieve the user information. # # The query must return only one row. The columns to return are: # home - Home directory # mail - MAIL environment # system_user - System user name (for initgroups()) # uid - System UID # gid - System GID # # Either home or mail is required. uid and gid are required. If more than one # row is returned or there's missing fields, login will automatically fail. # # Examples # user_query = SELECT home, uid, gid FROM users WHERE userid = '%n' AND domain = '%d' # user_query = SELECT dir AS home, user AS uid, group AS gid FROM users where userid = '%u' # user_query = SELECT home, 501 AS uid, 501 AS gid FROM users WHERE userid = '%u' # #user_query = SELECT home, uid, gid FROM users WHERE userid = '%u'

2 1

[Dovecot] pop3 via tls
by jepoy 13 Feb '07

13 Feb '07

hi guys, i want to try pop3 using tls, just like smtp. is it possible ? i want to first create a secure tunnel before donwloading the mails. tnx -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 1

[Dovecot] Problems with HUP'ing dovecot
by Javier Henderson 13 Feb '07

13 Feb '07

Hi, I'm running dovecot 1.0.rc7 on FreeBSD 6.1, so far with great success. Earlier today I tried to HUP the main process, the following was logged: dovecot: Feb 12 15:10:19 Warning: SIGHUP received - reloading configuration dovecot: Feb 12 15:10:19 Panic: file ioloop-poll.c: line 105 (io_loop_handle_remove): assertion failed: (index >= 0 && (unsigned int) index < ctx->fds_count) Of possible interest: just prior to issuing the HUP I had edited the / etc/resolv.conf file to take out the first entry since that particular DNS server went off line. I noticed that login attempts to the POP and IMAP services were timing out and that's when I sent the HUP to dovecot. Any ideas? Thanks, -jav

2 1

[Dovecot] mail_location and storage type
by Jürgen Herz 13 Feb '07

13 Feb '07

Hi, I was setting up a new system for testing Dovecot 1.0. My old one is using 0.99 and was set up quite a time ago, so I had to consult the documentation. I needed several attempts until it worked and that was because the designated maildir directory /server/mail/jrg/Maildir was completely empty. Upon login the server exited and wrote the following to the log: POP3(jrg): Ambiguous mail location setting, don't know what to do with it: /server/mail/jrg/Maildir (try prefixing it with mbox: or maildir:) POP3(jrg): Failed to create storage with data: /server/mail/jrg/Maildir That thing was the main cause of my confusion since the config wasn't ambiguous at all at already contained a prefix: mail_location = maildir:/server/mail/%u/Maildir The wiki article MailLocation doesn't contain any hint maildirs have to contain at least a cur subdirectory. That information I eventually got from mail-storages.txt - that file must be one for which the wiki isn't an alternative. So what is this mail about? 1. The log message is wrong or at least missleading. Would be fine if it could get improved. 2. Is there any reason at all to have a storage prefix but still require some special format for the directory in order to recognize it? 3. At least if the behaviour will stay, shouldn't the text from mail-storages.txt converted to a wiki article or incorporated into MailLocation? Regards, Juergen

2 3

[Dovecot] Compiler warnings
by Stephen Lee 12 Feb '07

12 Feb '07

Hi, I'm trying to install Dovecot 1.0RC22 on an old Trustix 1.5 box and am getting the compiler warnings: quota-storage.c:275: warning: pointer of type `void *' used in arithmetic convert-storage.c:50: warning: pointer of type `void *' used in arithmetic acl-backend-vfile.c:212: warning: pointer of type `void *' used in arithmetic There are many more of these pointer warnings in the various modules when compiling. Is this a problem? Thanks, Stephen

2 1

[Dovecot] Differences between IDLE when Maildir vs. wel the "mail" folder is used
by Philip Van Hoof 12 Feb '07

12 Feb '07

Are there any differences with how both IDLE and "UID FETCH n:n+x (FLAGS UID...)" are handled when Dovecot is using a "mail" vs. a "Maildir" user? I have recently implemented support for IDLE (Push E-mail) in a client infrastructure that I'm building. I haven't in depth checked out what the problem might be, but when Dovecot was using the "mail" dir in $HOME something about the implementation wasn't working. When I switched to "Maildir" everything worked. I only tested to the point of seeing the "* EXISTS n" response during the idle. I saw this response. It's for example possible that the n is wrong or that a bit later the "UID FETCH ..." ain't returning the right information. It's also possible that my implementation is wrong (of course) and I haven't yet had the time to really figure out what goes wrong. I did so far, however, test with Cyrus, Exchange, Courier and Isode's M-Box. All these tests where successful. SO if it indeed is a discrepancy in my implementation .. it's going to be something very specialised or specific I fear :-) I also setup testing infrastructure http://tinymail.org/trac/tinymail/wiki/TestImapServers Also take a careful look at this manual test. "tnytest" is a user on imap2.tinymail.org that uses Maildir. The "tnytest2" user doesn't have a Maildir configured. By that I mean that "Dovecot" has created the folder for E-mail using whatever it uses by default. Dovecot's IDLE (the EXISTS) responses also take a lot longer on tnytest2 than on tnytest. Another question. Why not simply "always" use the Maildir solution if that one works better? ;-) (really, honest question. Hehe). Take a look at the "UID FETCH" response: It's incorrect on tnytest2. The first attempt I asked for 1:1 and I got none. The second I asked for 1:4 and I got 3 of them, while IDLE clearly stated that there where 4 messages available. In reality 4 where indeed available (or copied in total). Well, I'm not saying something is or isn't wrong, just wondering and testing a little bit and seeing some strange results... Feel free to use imap2.tinymail.org for testing. And if you need root on that virtual machine, so that you can install a new version, go ahead. On http://imap2.tinymail.org you van find things like version information (it's a CVS snapshot). pvanhoof@lort:~$ telnet imap2.tinymail.org Trying 86.39.154.77... telnet: Unable to connect to remote host: Connection refused pvanhoof@lort:~$ telnet imap2.tinymail.org 143 Trying 86.39.154.77... Connected to imap2.tinymail.org. Escape character is '^]'. * OK Dovecot ready. ao1 login tnytest tnytest ao1 OK Logged in. a01 select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 0 RECENT * OK [UIDVALIDITY 1171049606] UIDs valid * OK [UIDNEXT 2] Predicted next UID a01 OK [READ-WRITE] Select completed. a04 IDLE + idling * 2 EXISTS DONE a04 OK Idle completed. UID FETCH 1:2 (FLAGS UID) * 1 FETCH (FLAGS (\Seen) UID 1) * 2 FETCH (FLAGS (\Seen) UID 2) UID OK Fetch completed. ^] telnet> quit Connection closed. pvanhoof@lort:~$ telnet imap2.tinymail.org 143 Trying 86.39.154.77... Connected to imap2.tinymail.org. Escape character is '^]'. * OK Dovecot ready. a01 login tnytest2 tnytest a01 OK Logged in. a01 select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1171107413] UIDs valid * OK [UIDNEXT 1] Predicted next UID a01 OK [READ-WRITE] Select completed. a04 IDLE + idling * 1 EXISTS DONE a04 OK Idle completed. a05 UID FETCH 1:1 (FLAGS UID) a05 OK Fetch completed. a04 IDLE + idling * 4 EXISTS DONE a04 OK Idle completed. a06 UID FETCH 1:4 (FLAGS UID) * 1 FETCH (FLAGS (\Seen) UID 2) * 2 FETCH (FLAGS (\Seen) UID 3) * 3 FETCH (FLAGS (\Seen) UID 4) a06 OK Fetch completed. -- Philip Van Hoof, software developer home: me at pvanhoof dot be gnome: pvanhoof at gnome dot org http://www.pvanhoof.be/blog

2 1

[Dovecot] PLAIN-MD5 password scheme with salt?
by Steffen Weber 12 Feb '07

12 Feb '07

Hello! I'm storing passwords as MD5 hashes in a MySQL database and have specified "default_pass_scheme = PLAIN-MD5" in dovecot-sql.conf. Can Dovecot append or prepend a salt to a password before hashing them? Because without salt the plaintext passwords can be restored from the MD5 hashes using rainbow tables. Greetings Steffen Weber

2 3

[Dovecot] mbox and dual-use folders?
by John Robinson 12 Feb '07

12 Feb '07

Feature request: please can we have support for messages stored in mbox files, but folders containing both messages and folders. I think this could be done for a folder called e.g. dovecot-list by having an mbox file called dovecot-list and a directory called dovecot-list.folder (or whatever, says he handwaving away name clashes which can be worked around like they are in maildirs). This may be a subset or variant of http://wiki.dovecot.org/FeatMboxMaildir Cheers, John.

2 1

[Dovecot] IMAP/POP3 server with proxy feature
by Jasper Bryant-Greene 12 Feb '07

12 Feb '07

We are currently evaluating the migration from a proprietary, legacy mail server onto Dovecot for 20,000+ virtual domains. This is a big job and we intend to do it by initially proxying connections through to the legacy server, and moving customers over in batches by turning off the proxy feature for them. In the manual it states "This model is still a bit unfinished in current code" [1]. What is needed to get this production-quality? I'm happy to help out with any work required. [1] http://wiki.dovecot.org/ImapProxy -- Jasper Bryant-Greene Director Album Limited jasper(a)albumltd.co.nz +64 21 708 334 / 0800 425 286 http://www.albumltd.co.nz/

5 4