- dovecot - dovecot.org

[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