- dovecot - dovecot.org

[Dovecot] dovecot + ldap
by aza zel 21 Mar '07

21 Mar '07

hi... i want to know how schema dovecot uses to use with ldap -- Salu2 ;)

3 2

[Dovecot] invalid mbox
by Marc Lucke 21 Mar '07

21 Mar '07

dovecot-1.0-1.1.rc15.fc6 When I attempt to drag spam from one IMAP box to another it tells me that I have an invalid mbox format for some emails. Occasionally too when I click on that email box it gives me the same error. uw-imapd never gave me those problems. I use Thunderbird 1.5.0.10 and have the same problem on Windoze XP and MacOSX. Can I and how do I solve this problem? Marc

3 2

[Dovecot] lock file on embedded device
by burolib 21 Mar '07

21 Mar '07

Hi. That's my first post. it's driving me crazy. I'm trying to get dovecot working with vpopmail on Openwrt, an embedded linux-like OS for some routers . So actually my aim looks like get dovecot working with little hardware resources (32 MB of Ram, 8 MB of disk mem.) I've cross compiled it well(it looks like). the login against vpopmail works. using mmap it cannot even select the inbox, the log says: Error: IMAP(test(a)fabri-fibra.org): file_dotlock_create() failed with file /home/vpopmail/domains/mydomain.org/test/Maildir/dovecot.index.log: No such file or directory And an impressive Kernel page fault: Mar 21 17:38:48 (none) kern.alert kernel: Unable to handle kernel paging request at virtual address 00000008, epc == 8004cce8, ra == 8004cc34 Mar 21 17:38:48 (none) kern.warn kernel: Oops in fault.c::do_page_fault, line 206: etc etc... even this error: Mar 21 17:38:48 (none) kern.crit kernel: ASSERTION FAILED: file->f_dentry != NULL at aux.c:120 (check_mini_fo_file) With mmap disabled i can select the inbox and read/write just the first time since any new attempt get stucked because the file dovecot-uidlist.lock was not removed. more details: dovecot: Mar 21 17:13:34 Warning: IMAP(test(a)fabri-fibra.org): Our dotlock file /home/vpopmail/domains/mydomain.org/test/Maildir/dovecot-uidlist.lock was overridden (kept it 0 secs) By the way my file system is a jffs, and my disk has 500K left. I will appreciate any tips. Fabrizio. ------------------------------------------------------ Con Prometeo prestiti senza spese fino a 31.000 Euro! Clicca qui http://click.libero.it/webnation21m07

3 2

[Dovecot] Adding ", S=size" to new message files when using "dirsize"
by Rich, Whidbey Telecom 21 Mar '07

21 Mar '07

When APPENDing new message files to an IMAP Maildir, Dovecot 1.0 rc27 can be configured to add ",S=size" to the filename. That allows it to be calculated with the "dirsize" quota plugin (and MTA's such as Exim). However, Dovecot only seems to do that when the "maildir" quota plugin is specified (from "quota-maildir.c"): /* For newly generated filenames add ,S=size. */ storage->save_size_in_filename = TRUE; Shouldn't "save_size_in_filename" be included in "quota-dirsize.c", since "dirsize" is the one that actually needs "S="? Maybe I'm missing something? Here're some relevant parts of our test config: -- mail_location = maildir:/var/mail/%u/Maildir:INDEX=MEMORY maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = yes protocol imap { mail_executable = /usr/local/libexec/dovecot/rawlog /usr/local/ libexec/dovecot/imap mail_plugins = quota imap_quota imap_client_workarounds = delay-newmail outlook-idle } plugin { quota = dirsize:storage=10240 } -- Thanks! Rich

2 3

[Dovecot] Thanks!
by Kyle Wheeler 21 Mar '07

21 Mar '07

Hello, I just recently switched my system from a BincIMAP/vpopmail to a Dovecot/vpopmail system, and I have to say: thanks! There were really only two things I had to patch Dovecot to do: first, provide statistics on network usage, and second, to allow folders to be LIST'd/SELECT'd/etc. with a trailing separator (to satisfy my pine users). If anyone's interested, I can generate a patch for that stuff. Other than that, it's been a real breeze. Dovecot is really simple to configure, and is faaaaaaaast! We have a kind of a wonky setup (multiple domains, multiple SSL keys, etc.) and Dovecot hasn't gotten mad even once. Timo, thanks a bunch, it's an excellent piece of software. ~Kyle -- Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. -- Douglas Adams

3 4

[Dovecot] The perfect Courier -> Dovecot conversion tool
by Timo Sirainen 21 Mar '07

21 Mar '07

I've tested this only with a test user. http://dovecot.org/tools/courier-dovecot-migrate.pl http://wiki.dovecot.org/Migration/Courier # Migrate Courier IMAP (any version) and Courier POP3 (v0.43+) to Dovecot v1.0 # by Timo Sirainen. This is public domain. # Usage: [--quiet] [--convert] [--overwrite] [--recursive] [<conversion path>] # --quiet: Print only errors # --convert: Do the actual conversion. Without this it only shows if it works. # --overwrite: Ovewrite dovecot-uidlist file even if it exists already. # --recursive: Recursively find maildirs to convert # <conversion path>: Maildir directory, or with --recursive its parent # directory or its parent's parent # - If courierpop3dsizelist is found, it makes its best effort to keep the # POP3 UIDLs, unless the file is more than 30 days older than # courierimapuiddb (user probably stopped using POP3). # - If courierpop3dsizelist isn't found (or it's old), the dovecot-uidlist # is directly converted keeping all the UIDs. # - Keywords are converted from courierimapkeywords/ to maildir filename # flags and dovecot-keywords file # - Subscriptions from courierimapsubscribed are added to Dovecot's # subscriptions file

2 1

[Dovecot] Anonymous edits enabled again in Wiki
by Timo Sirainen 21 Mar '07

21 Mar '07

With a captcha. You need to write "Dovecot" to the captcha field if you're not registered. Lets see if this is enough to confuse the spam bots. http://dovecot.org/tmp/moin-captcha.diff if someone wants to see the changes it required to MoinMoin.

1 0

Re: [Dovecot] Best way to migrate from Qpopper to Dovecot
by David Robillard 20 Mar '07

20 Mar '07

> we did nearly the same procedure the last time we switched from an old > Qpopper maschine to a new Qpopper maschine. > The last time we had not so much users (maybe 16000), not so much data > (round about 20Gigs) and there was no need of conversion. > This time we have new DNS-Names, new environment (Dovecot) and so on. That should not pose any real problems :) > So David, may I ask you how long did it take to convert the data? We used a cross-link cable between the two machines to transfer the data over their gigabit link. Both systems had three 10k rpm SCSI disks in hardware RAID 5 which pushed data at around 20 mb/s. That took around 20 minutes. Now for the migration script, that took about 1:30 hours to run on a single Intel Xeon 2.80GHz. Cheers, David -- David Robillard UNIX systems administrator & Oracle DBA CISSP, RHCE & Sun Certified Security Administrator Montreal: +1 514 966 0122

2 1

[Dovecot] a <blush> build/install question
by Stewart Dean 20 Mar '07

20 Mar '07

This is probably an idiot (and certainly so basic as to be non-Dovecot) question, but I have been chasing my tail for a day or so on it, so I will, with humiliation, ask for guidance on it. Some time back I had asked if dovecot had to have a whole build tree of stuff to run or if any upgrade could be limited to just the executable and some libraries. I was told the latter, and given this list: dovecot (the executable) dovecot.conf libexec/imap libexec/imap-login libexec/dovecot-auth I had wanted to structure my build and install work so that, when update came out, I could build into a directory that was stamped with the time and version and ssl inclusion status. Every time I built I would create a new directory, and I would be able to everything to fall back with, in the old directories. Being that this is production, I wanted to be able to uplevel (or fall back) quickly. I should say I build on a build machine, since I don't want to have a compiler on the production machines; I specified the stamped unique name of this build directory du jour using the --prefix confiigure parm The configure, make and make install steps all go fine. Now I have to transfer those five files over to the target production machine, where I had planned to reference these essential DC files, dovecot itself, dovecot.conf, etc through links, like this: (while resident in the build directory which has been NFS imported onto the production target machine) > cp -p ./sbin/dovecot /usr/sbin/$buildver.dovecot > ln -sf /usr/sbin/$buildver.dovecot /usr/sbin/dovecot > > cp -p ./etc/dovecot-example.conf /etc/dovecot-example.$buildver.conf > > cp -p ./libexec/dovecot/imap /usr/libexec/$buildver.imap > ln -sf /usr/libexec/$buildver.imap /usr/libexec/imap > > cp -p ./libexec/dovecot/imap-login /usr/libexec/$buildver.imap-login > ln -sf /usr/libexec/$buildver.imap-login /usr/libexec/imap-login > > cp -p ./libexec/dovecot/dovecot-auth /usr/libexec/$buildver.dovecot-auth > ln -sf /usr/libexec/$buildver.dovecot-au Alas, when I actually tried to run dovecot, it was asking for its resource /in the original build tree/ location, which wasn't there. Is there some way I can do what I want? It seems like I could run the configure without the --prefix parm and have these five files end up in the standard place, but then you would always be building in the same place. I would rather have them in a sheaf of unique build trees so there was never any confusion as to where an edition of them came from...one could always reference back to the unique build tree and do a sum on them. -- ==== 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

5 7

Re: [Dovecot] Best way to migrate from Qpopper to Dovecot
by David Robillard 20 Mar '07

20 Mar '07

> Hi List, > > what do you think is the best way to migrate (to a new maschine) round about > 30000 mboxes (Qpopper) with an amount of 43Gigs data, to maildir format > (Dovecot). > I think there are two ways: > > 1. > - stop services (smtp and pop3) on the old maschine > - copy the mboxes to the new maschine > - run a conversion script (for excample: "Perfect_maildir" > http://perfectmaildir.home-dn.net/) > - start the services on the new maschine (smtp and Dovecot) > > 2. > - tell the users to use the new server (from the day X) with the new feature > (imap) > - stop the smtp on the old maschine on day X > - leave the old maschine active for a month or so (let users get their "old" > mail) > > With the first alternative we have a high downtime, because of copying the > mboxes and converting the stuff. > > What do you think? Hello Torsten, We switched our 3500+ users from Qpopper to Dovecot last week-end. We had around 27Gb of data to migrate. We had a maintenance window in which we could stop the POP services, so it was quite easy to do. Even if we changed hardware, we kept the old name and IP so that we had no DNS changes to do. Clean and simple. Here's how we've done things on FreeBSD 6.2-RELEASE-p2 -- Shutdown qpopper POP services on the old machine. -- Create a tar and transfered it to the new machine. Acutally, this was a single step in which we used a pipe to send that tar STDOUT into ssh's STDIN. -- Import /etc/master.passwd and /etc/group from the old system into the new machine. -- Run a simple shell script to change from mbox format to Maildir using mb2md and set permissions. -- Exchange FQDN and IP between to old machine and the new one in order to prevent any DNS changes. -- Start Dovecot and your MTA on the new machine. Concerning your desire to move your user's Maildir into /var/mail/first_letter_of_username/username. It should be trivial to do using a simple /bin/sh script. Have fun ! David -- David Robillard UNIX systems administrator & Oracle DBA CISSP, RHCE & Sun Certified Security Administrator Montreal: +1 514 966 0122

2 1

[Dovecot] Sieve: Conversion script for procmail recipes.
by Stephen Usher 20 Mar '07

20 Mar '07

Seeing as many on this list are in the process of migrating their mailsystems not only to dovecot's IMAP/POP3 server but also using dovecot's deliver for delivering e-mail into users' folders I thought that it might be a good idea to share with you the perl script I've been labouring upon for the last few days which will translate a simple(ish) procmail recipe to an equivalent Dovecot-Sieve script. (It handles vacation pipes as well, by the way.) It may even be useful as a basis for a more fully featured translator, who knows. Whatever, if it could be put on the Wiki no doubt it will prevent the wheel being re-invented time and again. The script can be found at the following URL: http://www.earth.ox.ac.uk/~steve/sieve/procmail2sieve.pl It might be worth putting it in a contrib directory in the dovecot-sieve distribution. Steve -- --------------------------------------------------------------------------- Computer Systems Administrator, E-Mail:-steve@earth.ox.ac.uk Department of Earth Sciences, Tel:- +44 (0)1865 282110 University of Oxford, Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072

1 0

[Dovecot] Outlook client timeouts on sending mail
by J Moore 20 Mar '07

20 Mar '07

This may be a sendmail question, but I thought I'd ask here first: I set up an Outlook client to use secure IMAP and secure SMTP. When sending a message, the client typically times out once or twice and presents an error message indicating the server isn't configured for secure delivery. With a little persistence, Outlook eventually makes a successful connection, and the message goes on its way (2-3 tries). Any pointers as to where to look for the problem? Thanks, Jay

2 1

[Dovecot] Best way to migrate from Qpopper to Dovecot
by Torsten 20 Mar '07

20 Mar '07

Hi List, what do you think is the best way to migrate (to a new maschine) round about 30000 mboxes (Qpopper) with an amount of 43Gigs data, to maildir format (Dovecot). I think there are two ways: 1. - stop services (smtp and pop3) on the old maschine - copy the mboxes to the new maschine - run a conversion script (for excample: "Perfect_maildir" http://perfectmaildir.home-dn.net/) - start the services on the new maschine (smtp and Dovecot) 2. - tell the users to use the new server (from the day X) with the new feature (imap) - stop the smtp on the old maschine on day X - leave the old maschine active for a month or so (let users get their "old" mail) With the first alternative we have a high downtime, because of copying the mboxes and converting the stuff. What do you think? Thanks Torsten

3 5

[Dovecot] RHEL5 and dovecot version
by Oliver Schulze L. 20 Mar '07

20 Mar '07

RedHat Enterprise 5 is released! And dovecot 1.0rc15 is included! :) http://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/os/SRPMS/dovec… I wonder what the RH patches are, downloading ... HTH Oliver -- Oliver Schulze L. | Get my e-mail after a captcha in: Asuncion - Paraguay | http://tinymailto.com/oliver

1 0

[Dovecot] userdb static and doubled homedir problem
by Michal Soltys 20 Mar '07

20 Mar '07

With following configuration: userdb static { args = uid=10000 gid=10000 home=/home/vmail/domain.tld/%u/./ mail=maildir:~/maildirs } and accompanying passdb passwd-file consisting of only user and password, for example test:{PLAIN}test: dovecot will access home=/home/vmail/domain.tld/test/home/vmail/domain.tld/test/maildirs instead of home=/home/vmail/domain.tld/test/maildirs dovecot 1.0rc27 (+ flock and convert plugin diffs), openbsd 3.9, i386 any extra info (ktrace, etc.) - if needed dovecot -n: 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 valid_chroot_dirs: /var/mail:/home/regular:/home/vmail verbose_proctitle: yes first_valid_uid: 1999 first_valid_gid: 10 mail_location: mbox:~/Mail:INBOX=/var/mail/%u mail_debug: yes fsync_disable: yes lock_method: flock maildir_copy_with_hardlinks: yes 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_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 imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login verbose: yes debug: yes passdb: driver: passwd-file args: /etc/dovecot.passwd passdb: driver: bsdauth userdb: driver: static args: uid=10000 gid=10000 home=/home/vmail/domain.tld/%u/./ mail=maildir:~/maildirs userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master:

1 1

[Dovecot] Courier's courierpop3dsizelist - uid convert
by Marcin Gryszkalis 19 Mar '07

19 Mar '07

Hi Migration page [1] on wiki says "Courier version 3 (younger versions) Here everything has changed: Courier's UID data are now stored in courierpop3dsizelistand in a completely new format. But it's still possible to convert it to the format dovecot needs (link to perlscript and further configuration details will follow later). " but there's nothing more. I couldn't find any ready to use script for the conversion. Maybe somebody has it ready or could help me, I can write perl oneliner but I don't understand the format of index files. dovecot's is like this 1 1174291188 518 1 1174181234.P58178Q0M660793.sas.xxx.xxx.xx:2, 2 1174286738.P16096Q0M408737.sas.xxx.xxx.xx:2, courierpop3dsizelistand is like this /2 703 1105349624 1135668673.V41dI2c3c85.sas.xxx.xxx.xx:2,S 12176 184:1105349624 1135766433.V41dI2c3c95.sas.xxx.xxx.xx:2,S 170450 185:1105349624 I understand every line starts with mail filename, but I don't understand latter values. I'm also not sure about first line of dovecot's file. Any help would be appreciated :) greetings marcin [1] http://wiki.dovecot.org/Migration -- Marcin Gryszkalis, PGP 0x9F183FA3 jabber jid:mg@fork.pl, gg:2532994 http://the.fork.pl

1 0

[Dovecot] Dovecot 'suicide'
by Luigi Rosa 19 Mar '07

19 Mar '07

I have a Dovecot installation on a Fedora 4. With the last update from Dovecot RC10 to Dovecot RC27, the daemon kills itself every night with this error: Mar 17 05:23:11 mail dovecot: Time just moved backwards by 6 seconds. This might cause a lot of problems, so I'll just kill m yself now. The error appears just after the night maintenance script executes a ntpdate syncronization ntpdate is version 4.2.0a(a)1.1196-r Well, 6 seconds are little more than a blink in human perspective, even if it is a long time for a computer point of view. Couldn't be possible to add a configuration option to avoid the suicide? Any other option other than suicide is better, because there could be situations of really unattended servers. Ciao, luigi -- / +--[Luigi Rosa]-- \ She was a lovely girl. Our courtship was fast and furious. I was fast and she was furious. --Max Kauffmann

6 6

[Dovecot] Changed CONTROL= path causes POP3 to fail, whereas IMAP is working (rc25 & rc26)
by Steffen Kaiser 19 Mar '07

19 Mar '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'm testing some configurations, in the process I used a wrong user setting causing POP3 (get new messages) to fail, whereas IMAP was still working. An easy fix was to remove the entire /var/cache/dovecot/1012/ directory, both index and index/control were re-created and do work. So my guess is that the existance of the indexes causes some trouble when just the control information is missing. Here is what I had done: The mailbox of "dvtest" was fully working with the correct setting from the config file: mail=maildir:/home/dvtest/MailDir:INDEX=/var/cache/dovecot/1012/index:CONTROL=/var/cache/dovecot/1012/control (no "/index" in the CONTROL= part). Then I created a LDAP entry for the user dvtest wrongly: mail=maildir:/home/dvtestMAIL/MailDir:INDEX=/var/cache/dovecot/1012/index:CONTROL=/var/cache/dovecot/1012/index/control The CONTROL= ended in "/index/control" rather than just "/control". (Note: I also mv'ed /home/dvtest to /home/dvtestMAIL in order to see, whether the LDAP attribute is getting used.) Afterwards IMAP is working, but POP3 returns "Couldn't init INBOX: Unknown error"; Thunderbird displays the error: "The STAT command did not succeed. Error getting message number and sizes. Mail server ux-2s11-9 responded: Couldn't sync mailbox." When I correct the LDAP attribute, hence the CONTROL= path ends in "1012/control" again. The mailbox is working with POP3 again. The INBOX of the erroreous control path does not contain any dovecot-* files? The message I deleted and expunged (see logs) were from the INBOX. /var/cache/dovecot/1012/index/control# lr .: total 16 drwx------ 4 dvtest Debian-exim 4096 2007-03-07 09:36 ./ drwx------ 12 dvtest dvtest 4096 2007-03-07 09:34 ../ drwx------ 2 dvtest Debian-exim 4096 2007-03-07 09:36 .Addresses/ drwx------ 2 dvtest Debian-exim 4096 2007-03-07 09:35 .INBOX/ ./.Addresses: total 24 drwx------ 2 dvtest Debian-exim 4096 2007-03-07 09:36 ./ drwx------ 4 dvtest Debian-exim 4096 2007-03-07 09:36 ../ - -rw------- 1 dvtest Debian-exim 12756 2007-03-07 09:36 dovecot-uidlist ./.INBOX: total 8 drwx------ 2 dvtest Debian-exim 4096 2007-03-07 09:35 ./ drwx------ 4 dvtest Debian-exim 4096 2007-03-07 09:36 ../ The attached file contains the full log of a session POP3 (get new messages), IMAP, expunge in INBOX, POP3 again. I also selected the mailbox Adresses once, to see if it is working. === # dovecot --version 1.0.rc26 # dovecot -n # /usr/local/dovecot.rc26/etc/dovecot.conf log_path: /var/log/dovecot/dovecot.log protocols: imap imaps pop3 pop3s ssl_ca_file: /etc/ssl/certs/ca.crt ssl_cert_file(default): /etc/ssl/certs/imap.pem ssl_cert_file(imap): /etc/ssl/certs/imap.pem ssl_cert_file(pop3): /etc/ssl/certs/pop3.pem ssl_key_file(default): /etc/ssl/private/imap.key ssl_key_file(imap): /etc/ssl/private/imap.key ssl_key_file(pop3): /etc/ssl/private/pop3.key disable_plaintext_auth: no verbose_ssl: yes login_dir: /usr/local/dovecot.rc26/var/run/dovecot/login login_executable(default): /usr/local/dovecot.rc26/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot.rc26/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot.rc26/libexec/dovecot/pop3-login login_log_format_elements: %p: user=<%u> method=%m rip=%r lip=%l %c verbose_proctitle: yes first_valid_uid: 1000 mail_location: maildir:%h/MailDir:CONTROL=/var/cache/dovecot/%i/control:INDEX=/var/cache/dovecot/%i/index mail_debug: yes dotlock_use_excl: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/dovecot.rc26/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot.rc26/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot.rc26/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_log zlib mail_plugins(imap): quota imap_quota mail_log zlib mail_plugins(pop3): quota mail_log mail_plugin_dir(default): /usr/local/dovecot.rc26/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot.rc26/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot.rc26/lib/dovecot/pop3 mail_log_prefix: %Us(%u) [%p]: mail_log_max_lines_per_sec: 30 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %u pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): oe-ns-eoh namespace: type: private separator: . inbox: yes hidden: yes auth default: mechanisms: plain login cache_size: 10 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890 verbose: yes debug: yes debug_passwords: yes passdb: driver: ldap args: /usr/local/dovecot.rc25/etc/dovecot-ldap.conf passdb: driver: pam args: cache_key=%u session=yes dovecot userdb: driver: prefetch userdb: driver: ldap args: /usr/local/dovecot.rc25/etc/dovecot-ldap.conf userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 432 group: mail plugin: quota: fs Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRe6BIS9SORjhbDpvAQJY0wf/YCDC/Np8RRcOOgm36NZDT0PpS28u17QK TDHsbrZqgeA6iPV0IXpIrAV3fficnCQLJ25saIpl5BQyD18Lsbw15SJiFSs9Igko LCuiQwX4JzybXfga4m9rf6pMR9be/yREsbBsAu8KagMYVUxzN1H01cJfNb86XKNw 7GeKahpYVIVR3y9PZf13x8gW16REeRt0andWHa9Dmqt//ygv+sSqngfN9tzp6keo CW13FLIZufnP6TeFwcBQF4KNh6HeZn3B7AYL4BRAqrMIVRgIIkgDD3TzfNIUHCwq GwqvTE/dquW2HEwtG00S/ZnG6WAf6WKzl9p32F1mihRMpYjsQj2uyg== =8cA5 -----END PGP SIGNATURE-----

2 1

[Dovecot] Convert UW folders to Dovecot folders ?
by Frank Bonnet 19 Mar '07

19 Mar '07

Hello IMAP users here have a *lot* of folders living in their mailhub home directory Converting the INBOX doesn't seems to be a problem I've found scripts that do the job :-) But How to convert IMAP folders from UW format ( one file / folder ) to dovecot format which seems much more sophisticated. Does anyone has written such ( nice) utility ? Thanks a lot Frank

2 2

[Dovecot] Dovecot - with LDAP auth backend
by Shahmat Dahlan 19 Mar '07

19 Mar '07

I have the following installed (1) CentOS 2.6.9-42.ELsmp (2) dovecot-1.0-3_50.rc27.el4.at, (3) openldap-2.2.13-6.4E (A) I have added the following schema into /etc/openldap/schema attributetype ( 1.3.6.1.4.1.14237.1.1.1.1 NAME 'mailquota' DESC 'The size of space the user can have until further messages get bounced.' EQUALITY integerMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE ) objectclass ( 1.3.6.1.4.1.14237.1.1.2.1 NAME 'DovecotUser' DESC 'Dovecot-LDAP User' SUP top AUXILIARY MUST ( cn $ uid $ mail $ mailquota $ userPassword ) MAY ( sn ) ) (B) and added this into my /etc/openldap/slapd.conf include /etc/openldap/schema/dovecot.schema (C) And in my /etc/dovecot.conf, this is what I have protocol imap { mail_plugins = quota imap_quota mail_plugin_dir = /usr/lib/dovecot/imap } (D) also in my /etc/dovecot.conf plugin { quota = maildir:storage=10240 } (E) in my /etc/dovecot-ldap.conf user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailquota=quota user_filter = (&(objectClass=DovecotUser)(uid=%u)) pass_attrs = uid=user,userPassword=password Scenario 1 I have (D) set to quota = maildir:storage=10240, did a telnet localhost 143, and logged in, this is what I get Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. * OK Mail ready a1 login ldapuser password a1 OK Logged in. a2 getquota "" * QUOTA "" (STORAGE 0 10240) a2 OK Getquota completed. if I were to change (D) to quota = maildir And added in an attribute called "mailquota" in the entry uid=ldapuser,dc=mydomain,dc=com, give it a value 10240000 (is this correct? should it by in bytes or in kilobytes?), then reinitialize the mailbox by deleting the ~/Maildir directory (or in this case /home/ldapuser/Maildir) Did the telnet localhost 143, this is what I get instead Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. * OK Mail ready a1 login ldapuser password a1 OK Logged in. a2 getquota "" * QUOTA "" () a2 OK Getquota completed. Even after I've added the attribute mailquota in the ldap for the entry uid=ldapuser it still does not look like its taking any effect at all. Regards and thanks in advance.

2 1

[Dovecot] using sieve plugin
by Kendall Shaw 19 Mar '07

19 Mar '07

Hi, I have installed dovecot on ubuntu edgy linux by retrieving the source debian package, building and installing the package and then building and installing the sieve plugin. However, I get no log messages indicating errors and as far as I can tell, my .dovecot.sieve script is not being used. I have introduced a syntax error in the script and see no error message. In dovecot.conf I have: log_path = /var/log/dovecot.log invo_log_path = /var/log/dovecot.log protocol lda { module_dir = /usr/lib/dovecot/modules/lda mail_plugins = cmusieve log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log } I am using exim with dovecot. I've tried using a .forward file (I'm the one user on the computer). Alternately, I've tried creating the dovecot_deliver "transport" in exim and changing the localuser router to use it. Still, I get no messages from deliver and no error messages from dovecot or exim. The file dovecot-deliver.log is not created. Do you have any suggestions that can help me get it working or to see why it is not working? Kendall

2 1

[Dovecot] One user having reproducible IMAP issues
by Alex Boster 19 Mar '07

19 Mar '07

Dovecot version upgraded to 1.0r26 (did not fix problem). The server is a CentOS 4 x86 box. Using ext3 filesystem. Previous attempts to fix the issue have included simply moving aside the user's INBOX to recreating a new account from scratch. Sometimes the email behaves for a while, but within a day is not working again. In Mail.app (the user's usual mail client) the INBOX folder simply appears empty. mutt (run locally on the server) shows the messages there correctly. The problem is easily reproducible. Move /var/spool/mail/[username] to a backup file and remove all .imap directories for that user. Mail may work for a while, but will stop within 24 hours. The SquirrelMail message is: ERROR: The server couldn't find the message you requested. Most probably your message list was out of date and the message has been moved away or deleted (perhaps by another program accessing the same mailbox). Click here to return to INBOX dovecot -n : # /etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.debug.log login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u mail_full_filesystem_access: yes mail_executable(default): /usr/libexec/dovecot/rawlog /usr/libexec/ dovecot/imap mail_executable(imap): /usr/libexec/dovecot/rawlog /usr/libexec/ dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: mechanisms: plain login passdb: driver: pam args: dovecot userdb: driver: passwd Thanks! Alex

4 8

[Dovecot] authenticating with LDAP and SSL
by Nathan Fiedler 19 Mar '07

19 Mar '07

I managed to configure Dovecot to use a local OpenLDAP server to authenticate clients, without using SSL. However, I would rather that LDAP is accessed using SSL, but I cannot get Dovecot to connect. All that I did was change "uris" to "ldaps://localhost", and this appears in the maillog: Mar 18 12:53:00 server dovecot: Dovecot v1.0.rc15 starting up Mar 18 12:53:01 server dovecot: auth(default): ldap_bind((null)) failed: Can't contact LDAP server Is there additional configuration that is needed for SSL? Note that I altered the slapd.conf file from not requiring SSL to requiring SSL when I changed the "uris" parameter. And, of course, accessing the directory using ldapsearch works just fine. It seems that there's only a problem when using SSL, but I don't know how to debug it. Thanks n

4 3

[Dovecot] Kerberos
by forum 18 Mar '07

18 Mar '07

Hey all new to this crack Ok so i have setup kerosene on my server i run mutt and it goes off and gets kerberos key from server I have added teh gssapi to config file but when the key seams to want to authenticate off dovecot it fail anyone help me? Mutt is returning No authentication available Dovecot logs are returning: Mar 18 01:34:31 bandicoot dovecot: auth(default): gssapi(?,MYIPADDRESS): While acquiring service credentials: Miscellaneous failure Mar 18 01:34:31 bandicoot dovecot: auth(default): gssapi(?,MYIPADDRESS): While acquiring service credentials: No principal in keytab matches desired name Mar 18 01:34:34 bandicoot dovecot: imap-login: Aborted login: method=GSSAPI, rip=MYIPADDRESS, lip=MYIPADDRESS, TLS Thanks

3 5

[Dovecot] 1.0.rc27 released
by Timo Sirainen 18 Mar '07

18 Mar '07

http://dovecot.org/releases/dovecot-1.0.rc27.tar.gz http://dovecot.org/releases/dovecot-1.0.rc27.tar.gz.sig A few new small features and lots of index/mbox fixes. I've been heavily stress testing this release, so I think it should be about perfect. :) I think the only thing still missing from v1.0 is documentation. There are some unwritten pages in the wiki, and I still haven't bothered to write the wiki -> doc/*.txt conversion script. The script will probably be pretty easy, but writing the docs can take a while. + mbox and index file code handles silently out of quota/disk space errors (maildir still has problems). They will give the user a "Not enough disk space" error instead of flooding the log file. + Added fsync_disable setting. + mail-log plugin: Log the mailbox name, except if it's INBOX + dovecot-auth: Added a lot more debug logging to passdbs and userdbs + dovecot-auth: Added %c variable which expands to "secured" with SSL/TLS/localhost. + dovecot-auth: Added %m variable which expands to auth mechanism name - maildir++ quota: With ignore=box setting the quota was still updated for the mailbox even though it was allowed to go over quota (but quota recalculation ignored the box). - Index file handling fixes - mbox syncing fixes - Wrong endianess index files still weren't silently rebuilt - IMAP quota plugin: GETQUOTAROOT returned the mailbox name wrong the namespace had a prefix or if its separator was non-default - IMAP: If client was appending multiple messages with MULTIAPPEND and LITERAL+ extensions and one of the appends failed, Dovecot treated the rest of the mail data as IMAP commands. - If mail was sent to client with sendfile() call, we could have hanged the connection. This could happen only if mails were saved with CR+LF linefeeds.

5 7

Re: [Dovecot] Login processes and a new performance/security compromise [was: Re: pre-1.0.rc27: Index and mbox fixes]
by Bill Boebel 18 Mar '07

18 Mar '07

On Sat, March 17, 2007 10:51 pm, Timo Sirainen <tss(a)iki.fi> said: > Oh, and as for when the rewrite is in CVS, I'm not really sure. I'm > still wondering if I should put it there soon and make the release after > v1.0 be v2.0, or if I should first stabilize the current new CVS HEAD > features (which shouldn't take too long), do a v1.2 release and only > then put this code to CVS and make it v2.0.. I vote for first stabilizing the current new CVS HEAD, do a v1.1 release, and then put the ssl rewrite into CVS and plan to make that either v1.2 or v2.0. That way people will start banging on the new features in current CVS HEAD sooner. Bill

2 1

[Dovecot] Connection closed by foreign host.
by tubauwe＠gmx.de 18 Mar '07

18 Mar '07

I installed dovecot on my system using the following configuration (in dovecot.conf): protocols = imap listen = * ssl_disable = yes login_user = nobody login_processes_count = 3 mail_extra_groups = nobody default_mail_env = maildir:/home/%u/Maildir auth default { mechanisms = plain passdb shadow { } userdb passwd { } user = root } After that I tested via telnet an got the message: Connection closed by foreign host. In the log-file I found the following lines: dovecot: Mar 12 22:49:18 Info: Dovecot v1.0.rc15 starting up dovecot: Mar 12 22:51:12 Info: imap-login: Login: user=<username>, method=PLAIN, rip=192.168.??.20, lip=192.168.??.3 dovecot: Mar 12 22:51:12 Error: setmntent(/etc/mtab) failed: No such file or directory dovecot: Mar 12 22:51:12 Error: child 616 (imap) killed with signal 11 Because I'm quite a newbie, I don't know what to do. Therefore I ask here for help. Thank you! -- "Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ... Jetzt GMX ProMail testen: www.gmx.net/de/go/mailfooter/promail-out

4 4

[Dovecot] M-Box benchmark
by Maykel Moya 18 Mar '07

18 Mar '07

A friend of mine passed me this[1] cause I'm recommending him Dovecot. My personal experience is very different to the one in that benchmark. I will appreciate similar links from those of you who had benchmarked Dovecot against other IMAP servers. I'm conscious that my personal experience is far to be a objetive comparison. I switched from UW-Imap/Mbox to Dovecot/Maildir a box with 45k local users, 3.5MB/s sustained IMAP/POP traffic in work hours. The main performance gain is from mbox -> maildir switching. Anyway the users (and myself) "perceive" a good performance with the new setup. Regards, maykel [1] http://www.isode.com/whitepapers/mbox-benchmark.html

8 13

[Dovecot] pre-1.0.rc27: Index and mbox fixes
by Timo Sirainen 18 Mar '07

18 Mar '07

I've been doing some stress testing in the last few days and fixing all the errors I saw. I'm hoping that I've finally really fixed all the index/mbox problems. So, again I think the only thing left for v1.0 is the documentation. Please test this nightly snapshot before I'll release rc27 tomorrow: http://dovecot.org/nightly/dovecot-latest.tar.gz If you've seen any of the following error messages in log files, these should all be fixed now: - index: Append with UID 56297, but next_uid = 56298 - mbox: UID inserted in the middle of mailbox /home/tss/mail/inbox (45769 > 45768, seq=28, idx_msgs=30) - mbox: Expunged message reappeared in mailbox /home/tss/mail/inbox (UID 86957 < 86958, seq=28, idx_msgs=27) These should be fixed for most cases, but they can still rarely happen: - index: Extension reset without intro prefix There's a really tiny possibility of it still happening with mmap_disable=no, but I think it's practically fixed now. A proper fix would require more changes than I want to do for v1.0 (either support for marking transaction start/end positions or getting rid of the stupid intro prefix completely). - Cached message offset 38340 is invalid for mbox file /home/tss/mail/inbox This should happen only if you're using in-memory indexes or mbox_min_index_size isn't 0. This happens if the mbox file's timestamp and file size are the exact same after some expunges+appends, so the only way to properly fix it would be to wait a second and update the mtime before unlocking the mbox file after expunges. This sleep is actually already done when Dovecot notices that a) mtime and size really are the same after modification and b) mails have been moved around inside the file (ie. flag changes were done but there weren't enough empty space in the mail's own headers so mails had to be moved to get the needed space). Should be pretty rare. Anyway, this error is completely invisible to users and it doesn't have any other side effects that mbox_dirty_syncs doesn't already have. The whole error message could even be removed if it's going to become a problem.. Other changes in the snapshot: + mail-log plugin: Log the mailbox name, except if it's INBOX + dovecot-auth: Added a lot more debug logging passdbs and userdbs + dovecot-auth: Added %c variable which expands to "secured" with SSL/TLS/localhost. + dovecot-auth: Added %m variable which expands to auth mechanism name - Wrong endianess index files still weren't silently rebuilt - IMAP quota plugin: GETQUOTAROOT returned the mailbox name wrong the namespace had a prefix or if its separator was non-default

5 24

[Dovecot] Lazy expunge
by meka＠ns-linux.org 17 Mar '07

17 Mar '07

When I try to use it i get undefined symbol: dlopen(/usr/lib/dovecot/pop3/lib02_lazy_expunge_plugin.so) failed: /usr/lib/dovecot/pop3/lib02_lazy_expunge_plugin.so: undefined symbol: namespace_find_prefix Does anyone has this problem or I've compiled it with too agresive flags? Thanx! PS. I've folowed http://wiki.dovecot.org/Plugins/Lazyexpunge word to word. -- FreeB(eer)S(ex)D(rugs) are the real daemons

3 2

[Dovecot] deliver to subfolder with dovecot's LDA
by Tom Bombadil 17 Mar '07

17 Mar '07

Hi all... How can deliver messages to a subfolder using the LDA? For example, I want a message to joe+spam(a)abc.com to be placed inside the 'spam' subfolder. Any hint is appreciated. Thanks ;)

3 2

[Dovecot] flock problems with index files and passwd-file
by Michal Soltys 17 Mar '07

17 Mar '07

While experimenting a bit, I found that for some reason, locking indexes with flock is problematic, but only if user is taken from passwd-file. The host system is openbsd 3.9, dovecot's configuration is added at the bottom. Authentication is from two places - first from mentioned passwd-file, then from passwd file using bsdauth (in this case, there're no problems with flock). So, if a user is i.e.: test@domain.tld:{plain}test:20000:10::/home/regular/test::userdb_mail=maildir:~/Maildir Then the mail client will timeout (thunderbird in this case), and dovecot will leave following info in the logs: Mar 15 11:13:38 rasengan dovecot: IMAP(test(a)domain.tld): Effective uid=20000, gid=10, home=/home/regular/test Mar 15 11:13:38 rasengan dovecot: IMAP(test(a)domain.tld): maildir: data=~/Maildir Mar 15 11:13:38 rasengan dovecot: IMAP(test(a)domain.tld): maildir: root=~/Maildir, index=~/Maildir, control=, inbox= Mar 15 11:15:38 rasengan dovecot: IMAP(test(a)domain.tld): Timeout while waiting for lock for transaction log file /home/regular/test/Maildir/dovecot.index.log Happens both if in maildir and mbox (userdb_mail=mbox:~/mail:INBOX=/home/regular/test/mbx) cases. Locking through dotlocks or fcntl works well in all situations (passwd-file or not). Dovecot 1.0 rc27 OpenBSD 3.9 (stable), i386 Dovecot config (dovecot -n): # /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 valid_chroot_dirs: /var/mail:/home/regular verbose_proctitle: yes first_valid_uid: 1999 first_valid_gid: 10 mail_location: mbox:~/Mail:INBOX=/var/mail/%u mail_debug: yes lock_method: flock maildir_copy_with_hardlinks: yes 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_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 imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: verbose: yes debug: yes passdb: driver: passwd-file args: /etc/dovecot.passwd passdb: driver: bsdauth userdb: driver: passwd-file args: /etc/dovecot.passwd userdb: driver: passwd /etc/dovecot.passwd is just a single line: test@domain.tld:{plain}test:20000:10::/home/regular/test::userdb_mail=maildir:~/Maildir

2 5

[Dovecot] LOCKD errors
by Jay Chandler 16 Mar '07

16 Mar '07

Running the nightly from two days ago. The Dovecot log shows no errors, but I keep getting login errors for a few users. top shows: 71486 user1 1 96 0 4552K 2408K lockd 0 0:00 0.00% imap 11170 user2 1 96 0 4440K 2480K lockd 0 0:00 0.00% imap And a ps aux shows that these processes have been open for hours. If I move the mbox that contains their mail, the same error still shows up. The mboxes reside on our NetApp which is NFS mounted-- does anyone have any wisdom regarding this? As best I can tell this hasn't been a problem before the last few RCs, though I could be mistaken on this. -- Jay Chandler Network Administrator Chapman University

3 4

[Dovecot] wiki -> txt
by Timo Sirainen 16 Mar '07

16 Mar '07

I've been trying to fix MoinMoin's text_plain formatter to produce readable output. It's almost correct, except I don't understand why I can't get the LF-adding rules correct. Either there are too many LFs or too few. And whenever I change something, something else breaks.. It's getting pretty annoying. So if anyone else wants to try getting it fixed that'd be great. :) Attached the current version that I have. For testing you'll need your own MoinMoin installation. Then replace the included text_plain.py with the attached version. Then test it with for example: http://localhost/wiki/SomePage?action=format;mimetype=text/plain

3 5

Re: [Dovecot] I keep getting password mismatches
by Mark 16 Mar '07

16 Mar '07

i`m still not getting in.. i now have this error:Feb 17 23:48:42 School-Mail dovecot: Dovecot v1.0.rc15 starting upFeb 17 23:49:04 School-Mail dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AG1hcmsAbWFyaw==Feb 17 23:49:04 School-Mail dovecot: auth(default): pam(mark,127.0.0.1): pam_authenticate() failed: Authentication failureFeb 17 23:49:05 School-Mail dovecot: imap-login: Disconnected: user=<mark>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, securedFeb 17 23:49:05 School-Mail dovecot: auth(default): client out: FAIL 1 user=markand just to be sure.. here is my dovecot.conf file:## Dovecot configuration file# If you're in a hurry, see http://wiki.dovecot.org/QuickConfiguration# '#' 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.# 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 pop3sprotocols = imap pop3# 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.## 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 = [::]listen =# 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### 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 "# 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 =ssl_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. 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/pki/dovecot/certs/dovecot.pem#ssl_key_file = /etc/pki/dovecot/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. Usually not needed.# The CAfile should contain the CA-certificate(s) followed by the matching# CRL(s). CRL checking is new in dovecot .rc1#ssl_ca_file =# Request client to send a certificate.#ssl_verify_client_cert = no# 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# Show protocol level SSL errors.#verbose_ssl = no#### 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# 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 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.# You should make sure that the process has at least# 16 + login_max_connections * 2 available file descriptors.#login_max_connections = 256# Greeting message for clients.#login_greeting = Dovecot ready.# 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# and where Dovecot can place its index files. 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/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## http://wiki.dovecot.org/MailLocation##mail_location =# If you need to set multiple mailbox locations or want to change default# namespace settings, you can do it by defining namespace sections:## 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 or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes#}# 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 =# 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 = no# Log prefix for mail processes. See doc/variables.txt for list of possible# variables you can use.#mail_log_prefix = "%Us(%u): "# 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.# Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes.#mail_read_mmaped = no# Don't use mmap() at all. This is required if you store indexes to shared# filesystems (NFS or clustered filesystem).#mmap_disable = no# Don't write() to mmaped files. This is required for some operating systems# which use separate caches for them, such as OpenBSD.#mmap_no_write = 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. NOTE: If you use NFS, remember to change also mmap_disable setting!#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 = 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 = 500#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# Maximum number of running mail processes. When this limit is reached,# new users aren't allowed to log in.#max_mail_processes = 1024# 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# Default umask to use for mail files and directories.#umask = 0077# ':' 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 doc/configuration.txt for more information.#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.#mail_chroot =#### Mailbox handling optimizations### Space-separated list of fields to initially save into cache file. Currently# these fields are allowed:## flags, date.sent, date.received, size.virtual, size.physical# mime.parts, imap.body, imap.bodystructure## Different IMAP clients work in different ways, so they benefit from# different cached fields. Some do not benefit from them at all. Caching more# than necessary generates useless disk I/O, so you don't want to do that# either.## Dovecot attempts to automatically figure out what client wants and it keeps# only that. However the first few times a mailbox is opened, Dovecot hasn't# yet figured out what client needs, so it may not perform optimally. If you# know what fields the majority of your clients need, it may be useful to set# these fields by hand. If client doesn't actually use them, Dovecot will# eventually drop them.## Usually you should just leave this field alone. The potential benefits are# typically unnoticeable.#mail_cache_fields =# Space-separated list of fields that Dovecot should never save to cache file.# Useful if you want to save disk space at the cost of more I/O when the fields# needed.#mail_never_cache_fields =# 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 to wait between those checks. Dovecot is however able to use dnotify# and inotify with Linux to reply immediately after the change occurs.#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 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#### 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.# 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 = 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 = no# 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 = 0#### 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 # 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 # 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. 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". # 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. # 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 = outlook-idle}#### POP3 specific settings##protocol pop3 { # Login executable location. #login_executable = /usr/libexec/dovecot/pop3-login # POP3 executable location. See IMAP's mail_executable above for examples # how this could be changed. #mail_executable = /usr/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 format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail 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 version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # Older Dovecots : %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. # # NOTE: Nowadays this is required to be set explicitly, since the old # default was bad but it couldn't be changed without breaking existing # installations. %08Xu%08Xv will be the new default, so use it for new # installations. # #pop3_uidl_format = %08Xu%08Xv # POP3 logout format string: # %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 # 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 # Binary to use for sending mails. #sendmail_path = /usr/lib/sendmail # 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/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. Also note that currently auth cache doesn't work very well if# you're using multiple passdbs with same usernames in them.#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# 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 = yes# Even more verbose logging for debugging purposes. Shows for example SQL# queries.auth_debug = yes# 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 = yes# 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# Kerberos keytab to use for the GSSAPI mechanism. Will use the system# default (usually /etc/krb5.keytab) if not specified.#auth_krb5_keytab =auth default { # Space separated list of wanted authentication mechanisms: # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi 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. # # http://wiki.dovecot.org/PasswordDatabase # # 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. # # http://wiki.dovecot.org/MasterPassword # 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. # http://wiki.dovecot.org/PasswordDatabase/PAMpassdb pam { # use /etc/pam.d/imap and /etc/pam.d/pop3 args = *} # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. # http://wiki.dovecot.org/AuthDatabase/Passwd #passdb passwd { #} # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays. # http://wiki.dovecot.org/PasswordDatabase/Shadow #passdb shadow { #} # PAM-like authentication for OpenBSD. # http://wiki.dovecot.org/PasswordDatabase/BSDAuth #passdb bsdauth { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # passwd-like file with specified location # http://wiki.dovecot.org/AuthDatabase/PasswdFile #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication # NOTE: You will probably want to use "userdb prefetch" with this. # http://wiki.dovecot.org/PasswordDatabase/CheckPassword #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database # http://wiki.dovecot.org/AuthDatabase/SQL #passdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example #args = #} # LDAP database # http://wiki.dovecot.org/AuthDatabase/LDAP #passdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail authentication # http://wiki.dovecot.org/AuthDatabase/VPopMail #passdb vpopmail { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # # http://wiki.dovecot.org/UserDatabase # # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. WARNING: nss_ldap is known to be broken # with Dovecot. Don't use it, or users might log in as each others! # http://wiki.dovecot.org/AuthDatabase/Passwd userdb passwd { } # passwd-like file with specified location # http://wiki.dovecot.org/AuthDatabase/PasswdFile #userdb passwd-file { # Path for passwd-file #args = #} # static settings generated from template # http://wiki.dovecot.org/UserDatabase/Static #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 # #args = #} # SQL database # http://wiki.dovecot.org/AuthDatabase/SQL #userdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example #args = #} # LDAP database # http://wiki.dovecot.org/AuthDatabase/LDAP #userdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail # http://wiki.dovecot.org/AuthDatabase/VPopMail #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. # http://wiki.dovecot.org/UserDatabase/Prefetch #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 # 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 is typically used to give Dovecot's local delivery # agent access to userdb so it can find mailbox locations. It can # however also be used to disturb regular user authentications. # WARNING: Giving untrusted users access to master socket may be a # security risk, don't give too wide permissions to it! #path = /var/run/dovecot/auth-master #mode = 0600 # Default user/group is the one who started dovecot-auth (root) #user = #group = #} #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 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 # dict: Keep quota stored in dictionary (eg. SQL) # maildir: Maildir++ quota # fs: Read-only support for filesystem quota #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. #acl = vfile:/etc/dovecot-acls # Convert plugin. If set, specifies the source storage path which is # converted to destination storage (mail_location). #convert_mail = mbox:%h/mail # 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}----------------and that is my dovecot.conf that comes with my dovecot installation automatically when i type: yum install dovecotif anyone is willing to share his dovecot.conf file.. ?? (a working one ofcause ;))Thanx.Mark. _________________________________________________________________ Probeer Live.com: jouw leven online met nieuws, sport, weer en nog veel meer. http://www.live.com/getstarted

3 3

[Dovecot] unable to connect to auth server
by Steven F Siirila 16 Mar '07

16 Mar '07

Upon rebooting our Dovecot server, I got these: Mar 16 09:49:16 peridot.tc.umn.edu dovecot: [ID 195972 local6.info] Dovecot v1.0.rc27 starting up Mar 16 09:49:18 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 16 09:49:18 myhost.mydomain last message repeated 1 time Mar 16 09:49:18 myhost.mydomain dovecot: pop3-login: Can't connect to auth server at default: Connection refused Mar 16 09:49:18 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 16 09:49:18 myhost.mydomain last message repeated 2 times Mar 16 09:49:18 myhost.mydomain dovecot: pop3-login: Can't connect to auth server at default: Connection refused Mar 16 09:49:18 myhost.mydomain last message repeated 2 times Mar 16 09:49:18 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 16 09:49:18 myhost.mydomain last message repeated 1 time Mar 16 09:49:18 myhost.mydomain dovecot: pop3-login: Can't connect to auth server at default: Connection refused Mar 16 09:49:18 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused However, everything does work okay. I believe we ran into this once before and reported it and I had thought Timo fixed it. It seems that imap-login and pop3-login attempt to connect to the auth server before it is fully operational. I don't recall what the fix was supposed to change, but it doesn't seem to have fully fixed it. (We are running RC27 on Solaris 10) # /opt/dovecot/sbin/dovecot -n # /etc/opt/dovecot/dovecot.conf syslog_facility: local6 protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/opt/openssl/certs/dovecot.pem ssl_key_file: /etc/opt/openssl/private/dovecot.pem shutdown_clients: no login_dir: /var/opt/dovecot/run/dovecot/login login_executable(default): /opt/dovecot/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot/libexec/dovecot/pop3-login login_processes_count: 32 login_max_processes_count: 4096 max_mail_processes: 8192 first_valid_uid: 100 default_mail_env: mbox:~/:INBOX=/var/mail/%u mail_location: mbox:~/:INBOX=/var/mail/%u mail_full_filesystem_access: yes mbox_lazy_writes: no 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 imap_client_workarounds(default): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv namespace: type: private separator: / location: mbox:~/:INBOX=/var/mail/%u inbox: yes hidden: yes auth default: username_format: %Lu verbose: yes debug: yes passdb: driver: pam args: session=yes * userdb: driver: passwd -- 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] crypt missing (configure problem)
by Fabio Busatto 16 Mar '07

16 Mar '07

Hi, I need some feedback for the following problem I encountered compiling dovecot. It seems to be a wrong check in configure, that comes out in a fatal error (crypt symbol not found because the -lcrypt is omitted). With these configure parameters no crypt module is recognized (and so the need_crypt variable is still off), but at compile time gcc fails to create executables. I solve the issue forcing the need_crypt variable to on in configure, but maybe it can be solved clearly adding the right checks. Here is some info: Dovecot: tested on 1.0.rc17 and 1.0.rc27 OS: linux Configuration parameters: ./configure --without-passwd \ --without-passwd-file \ --without-shadow \ --without-pam \ --without-bsdauth \ --without-gssapi \ --without-sia \ --without-ldap \ --without-vpopmail \ --without-static-userdb \ --without-sql \ --without-pgsql \ --without-mysql \ --without-sqlite \ --without-deliver \ --without-sql-drivers \ --with-storages=maildir \ --disable-ipv6 Here there are the errors: Making all in auth make[3]: Entering directory `/usr/src/dovecot-1.0.rc27/src/auth' /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -export-dynamic -o dovecot-auth auth.o auth-cache.o auth-client-connection.o auth-master-connection.o auth-master-listener.o auth-module.o auth-request.o auth-request-handler.o auth-stream.o auth-worker-client.o auth-worker-server.o db-ldap.o db-sql.o db-passwd-file.o main.o mech.o mech-anonymous.o mech-plain.o mech-login.o mech-cram-md5.o mech-digest-md5.o mech-ntlm.o mech-gssapi.o mech-rpa.o mech-apop.o passdb.o passdb-blocking.o passdb-bsdauth.o passdb-cache.o passdb-ldap.o passdb-passwd.o passdb-passwd-file.o passdb-pam.o passdb-checkpassword.o passdb-shadow.o passdb-sia.o passdb-vpopmail.o passdb-sql.o userdb.o userdb-blocking.o userdb-ldap.o userdb-passwd.o userdb-passwd-file.o userdb-prefetch.o userdb-static.o userdb-vpopmail.o userdb-sql.o libpassword.a ../lib-settings/libsettings.a ../lib-ntlm/libntlm.a ../lib-sql/libsql.a ../lib/liblib.a -export-dynamic -ldl gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -o dovecot-auth auth.o auth-cache.o auth-client-connection.o auth-master-connection.o auth-master-listener.o auth-module.o auth-request.o auth-request-handler.o auth-stream.o auth-worker-client.o auth-worker-server.o db-ldap.o db-sql.o db-passwd-file.o main.o mech.o mech-anonymous.o mech-plain.o mech-login.o mech-cram-md5.o mech-digest-md5.o mech-ntlm.o mech-gssapi.o mech-rpa.o mech-apop.o passdb.o passdb-blocking.o passdb-bsdauth.o passdb-cache.o passdb-ldap.o passdb-passwd.o passdb-passwd-file.o passdb-pam.o passdb-checkpassword.o passdb-shadow.o passdb-sia.o passdb-vpopmail.o passdb-sql.o userdb.o userdb-blocking.o userdb-ldap.o userdb-passwd.o userdb-passwd-file.o userdb-prefetch.o userdb-static.o userdb-vpopmail.o userdb-sql.o -Wl,--export-dynamic libpassword.a ../lib-settings/libsettings.a ../lib-ntlm/libntlm.a ../lib-sql/libsql.a ../lib/liblib.a -ldl libpassword.a(mycrypt.o)(.text+0x5): In function `mycrypt': /usr/src/dovecot-1.0.rc27/src/auth/mycrypt.c:20: undefined reference to `crypt' collect2: ld returned 1 exit status make[3]: *** [dovecot-auth] Error 1 Making all in util make[3]: Entering directory `/usr/src/dovecot-1.0.rc27/src/util' /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -o dovecotpw dovecotpw.o ../auth/libpassword.a ../lib-ntlm/libntlm.a ../lib/liblib.a -export-dynamic -ldl gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -o dovecotpw dovecotpw.o -Wl,--export-dynamic ../auth/libpassword.a ../lib-ntlm/libntlm.a ../lib/liblib.a -ldl ../auth/libpassword.a(mycrypt.o)(.text+0x5): In function `mycrypt': /usr/src/dovecot-1.0.rc27/src/auth/mycrypt.c:20: undefined reference to `crypt' collect2: ld returned 1 exit status make[3]: *** [dovecotpw] Error 1 Bye Fabio -- Fabio Busatto <fabio.busatto(a)sikurezza.org>

2 3

[Dovecot] BUG: Unexpected input from auth master:
by Justin McAleer 16 Mar '07

16 Mar '07

deliver logs the error in the subject whenever the userdb lookup fails. I had a query discrepancy between postfix and dovecot, so messages were accepted that shouldn't have been, but I figured deliver should probably handle that a bit more gracefully :)

2 1

[Dovecot] Bug in dovecot 1.0 rc27
by Adrian P. van Bloois 16 Mar '07

16 Mar '07

Hi, My compiler AIX 5.2, complained about the following: cc -qlanglvl=ansi -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 -I/usr/local/include -O2 -c mbox-file.c "mbox-sync-private.h", line 50.17: 1506-009 (S) Bit-field uid_broken must be of type signed int, unsigned int or int. "mbox-sync-private.h", line 51.17: 1506-009 (S) Bit-field expunged must be of type signed int, unsigned int or int. "mbox-sync-private.h", line 52.17: 1506-009 (S) Bit-field pseudo must be of type signed int, unsigned int or int. After changing these variables to uint32_t everything went fine, AND workts fine too. Adrian -- Adrian P. van Bloois Postbus 2575 email: adrian(a)accu.uu.nl 3500 GN Utrecht voice: +31-(0)-30-68-94649 The Netherlands fax: +31-30-68-94649 The whole point of cooking is to get as much flavour out of the ingredients as possible. -- Delia Smith

2 1

[Dovecot] sasl authentication via dovecot
by Frank Church 16 Mar '07

16 Mar '07

I am setting up a Postfix/Dovecot/Virtual Domains system, with virtual tables using Postfixadmin and MySQL. Incoming mail is accepted for the virtual mailboxes, but when I try to retrieve mail from Outlook or Thunderbird I get errors You cannot log in to abc.server.net because the server has disabled login. You may need to connect via SSL or TLS. Please check the account settings for your mail server As Dovecot is handling the auth I suspect that it is where the problem lies. Are they any faults in the settings below that could be the cause? As I understand it because Dovecot is handling the login and monitoring the IMAP and POP ports. All the initial authentication is supposed to be handled there before Postfix gets involved. Running lsof -i:port on ports 110, 143, 993 and 995 shows that dovecot is handling all those inbound connections. I am also seeing messages in the log as follows dovecot: imap-login: Aborted login: rip:81.150.x.x, lip=66.90.x.x my auth section in Dovecot is as follows auth default { mechanisms = plain login passdb sql { args = /etc/dovecot/sql.conf } userdb sql { args = /etc/dovecot/sql.conf } userdb prefetch { } user = nobody socket listen { master { # path = /var/run/dovecot/auth-master path = /usr/local/var/run/dovecot/auth-master mode = 0660 user = vmail group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = mail } } } My sql.conf is as follows driver = mysql connect = host=localhost dbname=postfix user=dovecot password=password user_query = SELECT concat('/var/vmail/', maildir) as home, concat('maildir:/var/vmail/', maildir) as mail, 601 AS uid, 12 AS gid, concat('dirsize:storage=', quota) AS quota FROM mailbox WHERE username = '%u' AND active = '1' password_query = SELECT username as user, password, concat('/var/vmail/', maildir) as userdb_home, concat('maildir:/var/vmail/', maildir) as userdb_mail, 601 as userdb_uid, 12 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' this is the smtpd section from main.cn # ---------------------- SASL PART START ---------------------- smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth 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 # ---------------------- SASL PART END ----------------------

2 1

Re: [Dovecot] rc22 segv when over quota
by Steffen Kaiser 16 Mar '07

16 Mar '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 20 Feb 2007, Steffen Kaiser wrote: I have rebuilt rc23 to use "poll" instead of epoll, the same problem: warning: Can't read pathname for load map: Input/output error. Reading symbols from /lib/tls/i686/cmov/libdl.so.2...done. Loaded symbols for /lib/tls/i686/cmov/libdl.so.2 Reading symbols from /lib/tls/i686/cmov/libc.so.6...done. Loaded symbols for /lib/tls/i686/cmov/libc.so.6 Reading symbols from /lib/ld-linux.so.2...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 Core was generated by `imap [dvtest 10.20.10.63]'. Program terminated with signal 11, Segmentation fault. #0 mailbox_save_continue (ctx=0x80df574) at mail-storage.c:530 530 return ctx->transaction->box->v.save_continue(ctx); (gdb) bt full #0 mailbox_save_continue (ctx=0x80df574) at mail-storage.c:530 No locals. #1 0x08057193 in client_input (context=0x80df530) at cmd-append.c:67 client = (struct client *) 0x32c cmd = (struct client_command_context *) 0x80e27c0 #2 0x080ba522 in io_loop_handler_run (ioloop=0x80dd9b0) at ioloop-poll.c:199 ctx = (struct ioloop_handler_context *) 0x80dd9d8 pollfd = <value optimized out> tv = {tv_sec = 4, tv_usec = 762810} io = (struct io *) 0x80df610 t_id = 2 msecs = <value optimized out> ret = 135132464 call = <value optimized out> #3 0x080b9868 in io_loop_run (ioloop=0x80dd9b0) at ioloop.c:284 No locals. #4 0x08063910 in main (argc=Cannot access memory at address 0x8d4 ) at main.c:285 No locals. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRdr7NS9SORjhbDpvAQKXQQf/VHx/LEaC5zvz3C17iPuCSjro1Q9jznw2 GQA3FStiWhP3NsckSSQ+RxB8ih+lf+A8o2+nhF+pJ7N6qcBK3BVkum+WjQW5ddDv IEiAeo+dtFaP+7sO+qJeuq4ImXpiMDGpUVRt+PJYC1cAxWx+HYQ8im5UXEP4eTz7 uMu7MAX9vjwsWHmrfKMJf/36VQpTajMsfrfYbbTPPva++kuuNI33RIDvCeOsSmVF Vu38mRzP+wvwi/4YRV6UciVfrXV7sBl9Tk3oJjdEkn3gbxWPMfBYENxNRhAsj158 m+Zqz/bTJuThWlUFFM6uM/HDNrO39N3oWcHAJb7+zt8ULVMbD2WuVA== =9Ba1 -----END PGP SIGNATURE-----

2 10

[Dovecot] Warn before overquota
by Joan 16 Mar '07

16 Mar '07

Looking in the archives I found a message from dominik.saar(a)1und1.de on the 16/08/06, that is asking for a system to control the overquota warnings from within dovecot or dovecot LDA. The proposed solution is to use exim as MTA, since it has build in support. In my case I'm using postfix, what would be the recommended approach in that case? I was thinking of something like the cyrus LDA that you can with deliverquota [ -w percent ], something like that in a quota aware LDA would be quite useful for me. Any proposed solution would be welcome. Thanks

2 3

[Dovecot] running DC and UWIMAP on the same box
by Stewart Dean 15 Mar '07

15 Mar '07

It never hurts to ask...... I am bringing up DC on my production mailserver (which runs UWIMAP for production IMAP service) to learn and test it, much as I did when I introduced SSL protected IMAP, using an unpublicized non-standard port. The folder and mailbox location and format will remain the same. Questions: 1) Will DC be building indices for everything or just for the userid that I use to request client service for? 2) Are there any pitfalls others have experience doing this? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

3 2

[Dovecot] Postfix+Dovecot+LDAP
by Ejay Hire 15 Mar '07

15 Mar '07

This message does not contain a bug report or any issues. It is a summary of my experiences with Postfix, Dovecot, and Ldap. 1. Do not use Dovecot 0.99, even if it's what your vendor has packaged. 1a. ... When you upgrade past 0.99, you'll get some double mail because of UIDL's. 2. Do not use PAM and Ldap and then let dovecot talk to pam. It is bad. Don't do it. 2a. Unless you like users digging around in random mailboxes. 2b. NSCD is broken and should not be trusted. 3. Dovecot+Ldap works, and works well. 3a. If you don't do "Auth Binds", it cuts the work on the ldap server in half. 3b. User Prefetch cuts that in half again. 4. Postfix+Ldap works, and works well. 4a. If your server is underspec'd, you may get the occassional "Temporary lookup failure" 400 error during periods of heavy load, specifically when backups are running. 5. OpenLdap works. 5a. When you run as ldap, the config files need to be owned by ldap. 5b. ... And the database 5c. ... And the schema 5d. Adding slapd_db_recover to the init script isn't a bad idea. 6. Don't be dumb. 6a. ... Like me. 6b. If you are using ldap to lookup the attribute mail, index the mail attribute. 6c. If you add an index to Openldap, you have to reindex the database with slapindex 6d. ... Or you bounce a lot of mail before you figure it out. 6e. Make sure you can login to the console and/or ssh if the ldap server dies. 6f. ... Be Really sure. 6g. The convert plugin can switch users between maildirs and mboxes. Ejay Hire IT Manager, Confidential Business Resources 615-665-5555 (office) 615-456-9813 (mobile)

5 13

[Dovecot] tb-negative-fetch workaround
by bofh list 15 Mar '07

15 Mar '07

Hi, I notice in the Changelog that the tb-negative-fetch workaround shouldn't be needed any longer. We have a user running Thunderbird 1.5.0.8 that is experiencing the same problem described in https://bugzilla.mozilla.org/show_bug.cgi?id=263904 The current command did not succeed. the mail server responded: error in imap command uid: invalid body[..] parameter. Missing '>' in '<12288.-7215>' Any ideas? Thanks!

4 12

[Dovecot] pop3 uidl when migrating from mbox to maildir
by Giuseppe Giacomini 15 Mar '07

15 Mar '07

Thank you for the reply of my previous post (http://www.dovecot.org/list/dovecot/2007-March/020716.html) now it works, but I have another question about migrating pop3 account (with leave mail on server) to maildir. On this post -> http://www.dovecot.org/list/dovecot/2006-February/011464.html you explain how to create dovecot-uidlist preserving UIDVALIDITY. Is there someone that have build a script to generate such dovecot-uidlist? thank you all

2 1

[Dovecot] [PATCH 0/5] fix gcc warnings in CVS HEAD
by Max Kellermann 15 Mar '07

15 Mar '07

Hi, I have rewritten the patches I submitted earlier today for the CVS HEAD. Some of the changes were already committed months ago. On 2007/03/15 12:30, Timo Sirainen <tss(a)iki.fi> wrote: > That's ok, but I'm not sure about bsearch_insert_pos(). It's the way it > is mostly because I wanted to keep bsearch() API. If it can't return > void * then maybe it could be easier to just change the whole API to > something like: One of the patches changes exactly that. Timo, please review this patch carefully, because I havn't tested them yet. Max

2 6

[Dovecot] Alerts and pre-authenticated connections
by Mike Brudenell 15 Mar '07

15 Mar '07

Greetings - Work moves onward here at setting up our Dovecot IMAP service and I've got a couple more questions, I'm afraid... :-} ============================================== Q1. The UW IMAP Server supports "pre-authenticated connections" -- does Dovecot? Specifically, it is possible to create a symlink from /etc/rimapd to the UW IMAP server binary and then use rsh or ssh from within the Pine mail client to execute that on the server to establish the IMAP connection: rsh imap.york.ac.uk /etc/rimapd Pine uses this to open a "pre-authenticated" connection to the UW IMAP server to avoid the user having to enter their username and password -- the rsh/ssh mechanism provides the IMAP server with the user's login name. I've grepped the Dovecot source but it looks like it doesn't support this. Am I right in thinking this? ============================================== Q2. The UW IMAP Server can issue "IMAP Alerts" The UW IMAP server can issue a sequence of one-line notices to mail clients using IMAP's ALERT mechanism. The notices are formed formed from each line in a systemwide file (if non-empty) and a per-user file (~/.imapalert). Many, but by no means all, mail clients display these notices to the user -- currently we use this mechanism to advise people who have totally run out of mail quota. I've grepped the Dovecot source for "alert" but it looks like the IMAP Alert mechanism isn't supported. Am I right in thinking this? ============================================== Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

2 7

[Dovecot] imap connection problems
by Ivan Pesin 15 Mar '07

15 Mar '07

Hi, Have encountered some strange behavior of dovecot: after few days of work (5-7 days, ~50 users, imap over ssl or tls) dovecot stops respond with "* OK Dovecot ready.". I.e. connection gets accepted, but no response from dovecot: [ivan@dyn-226 bin]$ telnet imap 143 Trying 192.168.100.9... Connected to imap.n-ix.com.ua (192.168.100.9). Escape character is '^]'. while obvious should be [ivan@dyn-226 bin]$ telnet imap 143 Trying 192.168.100.9... Connected to imap.n-ix.com.ua (192.168.100.9). Escape character is '^]'. * OK Dovecot ready. After dovecot restart everything works OK. This behavior we started to observe since rc24, before that on rc9 we didn't see that problem. Currently running on rc26. Any ideas? Thanks, Iv

2 2

[Dovecot] convert_mail plugin doesn't work
by Giuseppe Giacomini 15 Mar '07

15 Mar '07

Hi I'm trying to use convert_mail plugin to convert wu-imap mailbox to maildir. I'm using dovecot rc 27 on Centos 4.4 linux. I have user INBOX in /var/spool/mail/ and mbox file in mail ~/mail When I do the first login with a test user (test1), the plugin convert all the mbox under ~mail, but doesn't do any conversion on the INBOX (/var/spool/mail/test1). After conversion those are file in MailDir where .testmail is converted from ~mail all other folder (cur,new) are empty rwx------ 2 test1 persone 4096 Mar 15 11:59 cur drwx------ 2 test1 persone 4096 Mar 15 11:59 new drwx------ 5 test1 persone 4096 Mar 15 11:59 .testmail drwx------ 2 test1 persone 4096 Mar 15 11:59 tmp Why doesn't mail in /var/spool/mail/test1 be converted? Thanks This is my dovecot -n protocols: imap imaps pop3 pop3s ssl_cert_file: /usr/share/ssl/certs/dovecot.pem ssl_key_file: /usr/share/ssl/private/dovecot.pem 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 first_valid_uid: 200 mail_location: maildir:%h/MailDir:INDEX=%h/.index/%u:CONTROL=%h/.control/%u 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: convert 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_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xv%08Xu pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam userdb: driver: passwd plugin: convert_mail: mbox:%h/mail:INBOX=/var/spool/mail/%u convert_skip_broken_mailboxes: yes and this is maillog dovecot: POP3(test1): Loading modules from directory: /usr/lib/dovecot/pop3 dovecot: POP3(test1): Module loaded: /usr/lib/dovecot/pop3/lib20_convert_plugin.so dovecot: POP3(test1): Effective uid=10400, gid=502 dovecot: POP3(test1): mbox: data=/homeH2/t/test1/mail:INBOX=/var/spool/mail/test1 dovecot: POP3(test1): mbox: root=/homeH2/t/test1/mail, index=/homeH2/t/test1/mail, inbox=/var/spool/mail/test1 dovecot: POP3(test1): mbox: data=/homeH2/t/test1/mail:INBOX=/var/spool/mail/test1 dovecot: POP3(test1): mbox: root=/homeH2/t/test1/mail, index=/homeH2/t/test1/mail, inbox=/var/spool/mail/test1 dovecot: POP3(test1): maildir: data=/homeH2/t/test1/MailDir:INDEX=/homeH2/t/test1/.index/test1:CONTROL=/homeH2/t/test1/.control/ test1 dovecot: POP3(test1): maildir: root=/homeH2/t/test1/MailDir, index=/homeH2/t/test1/.index/test1, control=/homeH2/t/test1/.contro l/test1, inbox= dovecot: POP3(test1): maildir: data=/homeH2/t/test1/MailDir:INDEX=/homeH2/t/test1/.index/test1:CONTROL=/homeH2/t/test1/.control/ test1 dovecot: POP3(test1): maildir: root=/homeH2/t/test1/MailDir, index=/homeH2/t/test1/.index/test1, control=/homeH2/t/test1/.contro l/test1, inbox= dovecot: POP3(test1): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0

2 1