- dovecot - dovecot.org

[Dovecot] best way something thinks to upgrade dovecot to 1.2.* 2.0.*
by fakessh 26 Aug '10

26 Aug '10

hello all hello dovecot network hello timo What are your tips for successful migration for dovecot (atrpms , atrpms-testing depot for centos ) the page of wiki http://wiki2.dovecot.org/Upgrading/2.0 explains the method to upgrade I tried on my personal machine and the command cites wiki returns errors on the terminal what to do with errors: correct the error in the configuration file ? the question may seem simple but it is not pointless many returns are welcome something thinks are welcome thanks

2 10

[Dovecot] dovecot 1 to 2 migration FreeBSD
by Frank Bonnet 26 Aug '10

26 Aug '10

Hello is there some specials recommentations to migrate from dovecot 1.1.x to 2.0.1 with FreeBSD boxes ? Thanks

5 11

[Dovecot] Home directories
by Timo Sirainen 26 Aug '10

26 Aug '10

I've noticed that a lot of people are using e.g.: mail_location = maildir:/var/vmail/%d/%n Then either they don't have home directory set, or their home directory is the same as the maildir. http://wiki.dovecot.org/VirtualUsers/Home explains all the problems of not separate home and mail directories. Also whenever I try to suggest using a separate home and mail directory, the answer is way too often: "But I'm using virtual users. (They don't have home directories.)" So I started wondering. Maybe simply renaming the "home" to something else would help here at least some. Make all of the documentation use only the new word, and add alias for userdb so that the new name and the "home" both work (I guess docs would need to keep using the "home" as field name for some more years). So far I've only come up with "vhome" as the replacement name. Other ideas?

12 19

[Dovecot] DSYNC needs a lot more documentation
by Marc Perkel 26 Aug '10

26 Aug '10

Started looking into the dsync utility and the doc are seriously incomplete. I can of course scour the internet looking for the missing information but that doesn't fix the problem with the docs. I might try to rewrite the docs myself once I figure it out.

9 15

[Dovecot] Pure virtual user and RT3.x
by Egbert 25 Aug '10

25 Aug '10

Hi, I have mailsystem with virtual users only (/home/vmail/domain/user). I need to integrate RT3.x (a ticketing system). I have installed the client but I need to send mail to a pipe. Rt wants me to insert: |/usr/bin/rt-mailgate --queue bla --action bla --url http://bla.bal/ In /etc/postfix/aliases. That does not work for me. What is the right way to achieve that mail to rt@mydomain is sent to the pipe? Should I install, configure and use a Sieve filter? I have none installed at the moment. Or are there other (simpler?) ways? TIA Egbert Jan

2 2

Re: [Dovecot] Live Mirror dovecot / OS X 10.6.4 (Timo Sirainen)
by Eric Boltz (MMI / UPC) 25 Aug '10

25 Aug '10

Timo Sirainen <tss(a)iki.fi> wrote: > Two potential problems I see with this: > 1. If users can do any changes on the secondary server (flag changes, > saving new mails, etc), you're going to have problems syncing the > changes back (without losing any changes or causing other problems). > > 2. If users can access the secondary server via IMAP clients, the > clients could become confused if the secondary server isn't completely > up-to-date. > > With v2.0 dsync would help with the first problem. Change in strategy. Primary rsyncs regularly to the secondary which keeps all mail services off. When primary fails email services are started manually until primary back online. Then I (or another ITer) manually stop the backup, rsycn and restart services on the primary. A bit labor intensive, but it should work.

4 5

[Dovecot] Problems compiling Dovecot 2.0.0 on Solaris 10 x86
by Drew Schatt 25 Aug '10

25 Aug '10

I'm having issues getting Dovecot 2.0.0 to compile - I get the following error: cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-settings -I../../src/lib-master -DPKG_RUNDIR=\""/usr/local/var/run/dovecot"\" -DPKG_LIBEXECDIR=\""/usr/local/libexec/dovecot"\" -DEXAMPLE_CONFIG_DIR=\""/usr/local/share/doc/dovecot/example-config"\" -DMODULEDIR=\""/usr/local/lib/dovecot"\" -DSSLDIR=\""/etc/ssl\"" -I/usr/local/include -I/usr/local/ssl/include -D_XPG6 -L/usr/local/lib -L/usr/local/ssl/lib -KPIC -lm -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -xc99 -I/usr/local/include -I/usr/local/ssl/include -L/usr/local/lib -L/usr/local/ssl/lib -D_XPG6 -xstrconst -KPIC -lm -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -c doveconf.c "config-request.h", line 6: warning: useless declaration "doveconf.c", line 554: undefined symbol: optarg "doveconf.c", line 554: warning: improper pointer/integer combination: arg #2 "doveconf.c", line 560: warning: improper pointer/integer combination: op "=" "doveconf.c", line 581: undefined symbol: optind "doveconf.c", line 583: undefined symbol: optind "doveconf.c", line 584: undefined symbol: optind cc: acomp failed for doveconf.c gmake[3]: *** [doveconf.o] Error 2 gmake[3]: Leaving directory `/home/schatt/code/evaluation_src/dovecot-2.0.0/src/config' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/home/schatt/code/evaluation_src/dovecot-2.0.0/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/home/schatt/code/evaluation_src/dovecot-2.0.0' gmake: *** [all] Error 2 Anyone have any idea on how to resolve this one? -Drew

2 1

[Dovecot] Signal 11 - can't get core dump?
by Marty Anstey 25 Aug '10

25 Aug '10

Hi all, We have been running Dovecot for over a year now in our moderate volume mail environment (>4000 mailboxes) and it's been running great. However, over the past month or so we've begun to experience issues where IMAP clients will appear to "hang" for a period of time, we then see a sig 11, and afterwards mailflow returns to normal. This usually happens a few times a day. Naturally, our first instinct was to try and get a core dump, but after following the instructions at http://www.dovecot.org/bugreport.html we now recieve this warning: 2010-08-24T13:33:56-07:00 mail dovecot: child 9728 (login) killed with signal 11 (core not dumped - add -D to login_executable) (ip=208.98.210.13) Adding -D to the login_executable lines didn't seem to have any effect, we are still receiving the same message. Did we perhaps misinterpret the hint? As we've been trying for over a week now to find a way to get a dump without any success, we figured posing this to the list might help us shed some light on the issue. Any suggestions would be appreciated! dovecot -n -- # 1.1.20: /etc/dovecot.conf # OS: Linux 2.6.18-164.15.1.el5xen i686 CentOS release 5.5 (Final) nfs base_dir: /var/run/dovecot/ listen: 208.98.210.10 ssl_ca_file: /etc/ssl/gd_bundle.crt ssl_cert_file: /etc/ssl/sunwave.net.crt ssl_key_file: /etc/ssl/sunwave.net.key ssl_parameters_regenerate: 1 ssl_cipher_list: ALL:!LOW verbose_ssl: yes login_dir: /var/run/dovecot//login login_executable(default): /usr/libexec/dovecot/imap-login -D login_executable(imap): /usr/libexec/dovecot/imap-login -D login_executable(pop3): /usr/libexec/dovecot/pop3-login -D mail_max_userip_connections(default): 50 mail_max_userip_connections(imap): 50 mail_max_userip_connections(pop3): 10 first_valid_uid: 200 last_valid_uid: 200 first_valid_gid: 200 last_valid_gid: 200 mail_location: maildir:/var/spool/mail/%Ld/%1Lu/%Ln/Maildir mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_executable(default): /usr/local/bin/mailtools/mail_imap.sh mail_executable(imap): /usr/local/bin/mailtools/mail_imap.sh mail_executable(pop3): /usr/local/bin/mailtools/mail_pop3.sh mail_plugins(default): quota imap_quota trash mail_plugins(imap): quota imap_quota trash mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes lda: postmaster_address: do_not_reply(a)sunwave.net mail_plugins: quota cmusieve auth default: mechanisms: plain login default_realm: sunwave.net verbose: yes passdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 511 user: vmail plugin: sieve: /var/spool/mail/%Ld/%1Lu/%Ln/Maildir/.sieve quota: maildir:Quota quota_rule2: Trash:storage=10%% quota_warning: storage=70%% /usr/local/bin/mailtools/quota-warning.sh 70 quota_warning2: storage=80%% /usr/local/bin/mailtools/quota-warning.sh 80 quota_warning3: storage=90%% /usr/local/bin/mailtools/quota-warning.sh 90 trash: /etc/dovecot-trash.conf Thanks, Marty

3 3

[Dovecot] Help needed with plugin - Read Only access to IMAP mailbox
by Chris Moules 25 Aug '10

25 Aug '10

System info: # 1.2.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686-bigmem i686 Debian squeeze/sid .. mail_plugins: readonly .. I have a requirement to have read-only to a mailbox. I have been researching through the wiki, the mailing list archives and good old Google. There was a number of similar questions with no real definitive answer. Option 1: ACL This can work, but not if the mailbox(s) can change without you knowing how. I.E. a online read-only archive of someone else's mailbox. There is no wild-card or recursive ACL options. Rsync style backups don't allow for easy creation of custom ACL files per mailbox. Option 2: Read-only filesystem (Linux) This seems easy, but it's not. 1) how do you update your archive? I tried with a bind mount, this does not let you set the 'ro' option *directly*. You must then use "-o remount,ro" to get your read-only bind mount. This is a little messy (needs custom init scripts for mounting on boot), but do-able. 2) Dovecot needs write access to CONTROL and INDEX files. This lead me to using the "CONTROL" and "INDEX" options on the mail_locaiton. Setting these to the original 'rw' mount and the rest to my 'ro' bind mount. Again, messy but do-able. 3) Clients try to move messages from 'new' to 'cur' for Maildir. Every time I opened a maildir I got an error per mail (dovecot log) about read-only filesysem as the client was trying to set the Seen flag and dovecot was trying to move the 'new' mail to the 'cur' folder. My test client, mutt, has a 'read_only' option when connecting. This eliminates this issue, but I cannot get everyone to use this archive with a correctly configured mutt. This sent me looking for 'read only' options in other clients. I could hardly find any. I noted that mutt send an EXAMINE and not a SELECT to open the mailbox when in read_only mode and this set me thinking about doing this in another way. Option 3: Dovecot Plugin I started looking into the dovecot plugins. Being more a systems administrator than developer I have cobbled together a working plugin. It nearly does what I want, but not quite, and I don't know why. NOTE: I no longer use the setup that I had to test Options 1 and 2. I thought that this plugin can either be used server-wide or with the 'mail_plugins' userdb option. The plugin forces the MAILBOX_OPEN_READONLY flag in a mailbox_open() call. The plugin returns an error for all mailbox_create() calls. Testing in mutt: - I am unable to delete a mail - I am unable to create a new folder So far so good. However: - I am able to move/copy a mail to an *existing* mailbox (note, the move operation makes the copy but fails to set the 'delete' flag) I do not understand why this works. I have been grep-ing through the source of dovecot and the plugins to find some answer, but without luck. Attached is the full source to my plugin and the Makefile (adapted from Johannes Berg's antispam plugin Makefile) When finished, I will be happy to release this to the dovecot community under the GPL/LGPL or whatever. Regards Chris

3 10

[Dovecot] v2.0.1 released
by Timo Sirainen 24 Aug '10

24 Aug '10

http://dovecot.org/releases/2.0/dovecot-2.0.1.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.1.tar.gz.sig Some small fixes mainly, but since people aren't reporting much bugs for v2.0.0 anymore maybe v2.0.1 release will change that. :) Some of the more important changes since v2.0.0 are: * When dsync is started as root, remote dsync command is now also executed as root instead of with dropped privileges. - IMAP: QRESYNC parameters for SELECT weren't handled correctly. - UTF-8 string validity checking wasn't done correctly (e.g. mailbox names in Sieve fileinto) - dsync: Fixed a random assert-crash with remote dsyncing

1 0