- dovecot - dovecot.org

[Dovecot] Managesieve Automatic Homedir Creation: File not Found Error
by linuxer＠netsteps.ch 31 Mar '13

31 Mar '13

Hi all, I'm running dovecot version 2.0.19 (Ubuntu 12.04) and I discovered some unexpected behaviour related to the Dovecot managesieve module. When connecting to the managesieve service from a client for the first time (e.g. roundcube webmail), I get an application error. This is logged by Dovecot: Error: sieve-storage: opendir(/var/.../exampledomain/exampleuser@exampledomain//sieve) failed: No such file or directory. At first glance I thought the problem was caused by the "//" in the directory path. I assume this is just a concatenation of the user virtual home directory (in my case "/var/.../exampledomain/exampleuser@exampledomain/" and the default sieve folder (~/sieve). While this looks wrong it seems not to be the actual problem (should be fixed though?) Then I noticed that the user home directory and sieve data were actually properly created despite the error. When connecting again, it worked without error. The problem can be reproduced by deleting the users virtual home directory and connecting again. A guess would be that the automatic creation of the virtual users homedir folder structure is some asychronous process not being completed in time. I also found this older thread with a similar issue: http://osdir.com/ml/dovecot-development/2010-05/msg00018.html Could also be worth mentioning that I'm running Dovecot on a virtualized host with possibly relatively poor I/O performance (maybe faster environments don't have this problem). Thanks for looking into this, and thx for the really neat dovecot software package! Cheers, L.

2 1

[Dovecot] ACL for root-level mailboxes
by Bradley Rintoul 31 Mar '13

31 Mar '13

Hello: I see in the documentation where it says that if mailboxes are created at the root level it will use the namespace's default ACL. I'm using Dovecot 2.0.9 so there is no default namespace defined, so I'm a bit handicapped here... Anyway, assuming I can figure out how to define a default namespace, how do I specify its ACL? Where would the file describing the access go? Sorry if this is a bit broad, but any help would be appreciated. Thanks, B. Rintoul

2 1

[Dovecot] Please help to make decision
by Tigran Petrosyan 30 Mar '13

30 Mar '13

Hi We are going to implement the "Dovecot" for 1 million users. We are going to use more than 100T storage space. Now we examine 2 solutions NFS or GFS2 via (Fibre Channel storage). Can someone help to make decision? What kind of storage solution we can use to achieve good performance and scalability.

8 9

[Dovecot] 3 node setup without cluster filesystem
by Michael 30 Mar '13

30 Mar '13

Hi everyone, short version: Is there any 3 host (two MX and one frontend IMAP) that can use a shared (iSCSI) ext4 volume? Long version: I am running a very complex setup right now with two MX, two proxies(lmtp/imap)/imap-frontends and two backends mounting an ocfs2 volume. I would like to reduce the complexity (and the number of hosts) and get rid of ocfs2. I ask myself if I can use an ext4 iSCSI-LUN using this setup: MX01 -> lmtp:unix:private/dovecot-lmtp -> mail_home: /var/mail MX02 -> lmtp:unix:private/dovecot-lmtp -> mail_home: /var/mail IMAP01 (imap) -> mail_home: /var/mail Regards Michael

4 3

[Dovecot] Restoring Mails via DSync
by Asai 29 Mar '13

29 Mar '13

Greetings, Can anyone give me a quick pointer to the right command to use for restoring backups made by dsync? I have our whole mail server backed up with it, but not sure how to restore... Any help would be greatly appreciated. -- --Asai

2 2

[Dovecot] changing flags automatically
by Lutz Preßler 28 Mar '13

28 Mar '13

Hello, (2.2:) there is no doveadm subcommand to change flags of messages, is it? The following should work reliably? # mark messages with subject $SUBJECT in mailbox $MAILBOX of user $USERID as read ( i=2 echo "1 SELECT "$MAILBOX doveadm search -u $USERID mailbox $MAILBOX subject "$SUBJECT" \ | while read g u do echo $i" UID STORE "$u" flags (\Seen)" i=$((i+1)); done echo "0 LOGOUT" ) | /usr/lib/dovecot/imap -u $USERID Greetings, Lutz

2 1

[Dovecot] Gmail like labels, three years later
by Pablo Vieira 27 Mar '13

27 Mar '13

On this post http://www.dovecot.org/list/dovecot/2011-June/059605.html I was asking about the possibility of using arbitrary labels on messages, much like Gmail does. On following replies, I was told about few tricks that might be used, that the IMAP protocol was being considering UTF-8 labels and ways to integrate them into the current system, etc., etc., etc. That sounds nice and all. I'm chiming in three years later only to know if things have changed, both at Dovecot and at the IMAP protocol. Are we closer to have proper labels on IMAP? Labels that help sorting messages in virtual folders where a message can belong in several of them? I consider "label vs folder" a done discussion (since labels can always include folders; a labels system can always be implemented as a folders system, but not viceversa; etc), so what's stopping development in that direction? Have any new energies being devoted to that cause? I just seen Dovecot is number 1 among IMAP servers by a large margin. Congratulations to the devs. Aleve.

3 6

Re: [Dovecot] Migrating password scheme
by Joseph Tam 27 Mar '13

27 Mar '13

Andreas wrote: > > I tried the userdb prefetch / postlogin script method to do some password > > manipulation, but it doesn't appear to work for me. In particular, I > > don't think this method works with > > > > userdb { > > driver = passwd-file > > args = /path/to/passwd-file userdb_pw=%w > > } > > > > From what i understand you have to set a userdb_<something> variable > with passdb and userdb prefetch set. The %w variable seems to be > already empty (again?) at userdb stage. Did all of that. The problem is not prefetching, but that you can't pass arguments via the args=.... Dovecot parses the entire line as a password file pathname. Timo Sirainen definitively writes: > With v2.1 try: > > userdb { > driver = passwd-file > args = /path/to/passwd-file > default_fields = pw=%w > } Thanks, Timo. This works beautifully. Furthermore, it doesn't need the userdb prefetch. Summarizing, the minimal incantation for passing dovecot variables to the post-login script is userdb { driver = passwd-file args = /var/dovecot/test/passwd default_fields = pw=%w } service imap { executable = imap postlogin ... } service pop3 { executable = imap postlogin ... } service postlogin { executable = script-login /path/to/postlogin-exec # Careful -- defaults to root user = $default_internal_user unix_listener postlogin { } } I've updated the Dovecot2 wiki, but I am unsure which userdb's "default_fields" applies to, and whether it just applies to postlogin scripts, so I documented it at http://wiki2.dovecot.org/AuthDatabase/PasswdFile Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] Authentication failure messages in logs
by Nicolas Mora 27 Mar '13

27 Mar '13

Hello, I'm currently running dovecot on a debian stable and every day, I see this message dozens of time in my logs : Mar 16 11:27:57 hector dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=nicolas rhost=72.53.129.223 user=nicolas on the list archive, this message for example tells to comment out the pam section. http://www.dovecot.org/list/dovecot/2008-July/031966.html Except that my authentication needs pam... Is there any way to solve this without migrating to virtual users ? Thanks in advance Here is my dovecot -n output : # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 3.2.13-grsec-xxxx-grs-ipv6-64 x86_64 Debian 6.0.7 protocols: imap imaps managesieve sieve ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(managesieve): ssl_cert_file: /etc/ssl/localcerts/dovecot.pem ssl_key_file: /etc/ssl/localcerts/dovecot.key login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:~/Maildir mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve lda: postmaster_address: postmaster(a)babelouest.org mail_plugins: sieve mail_plugin_dir: /usr/lib/dovecot/modules/lda sieve_dir: ~/ auth default: mechanisms: plain login passdb: driver: pam args: dovecot userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 plugin: sieve: ~/.dovecot.sieve

2 2

[Dovecot] Error Building v2.2
by Nikolaos Milas 27 Mar '13

27 Mar '13

Hello, I am trying to build Dovecot v2.2 (nightly version 20130326, which I have renamed and use as 2.2.0) on CentOS 6.4 x86_64 and I am having a problem: ... + ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info 'INSTALL_DATA=install -c -p -m644' --docdir=/usr/share/doc/dovecot-2.2.0 --disable-static --disable-rpath --with-nss --with-shadow --with-pam --with-gssapi=plugin --with-ldap=plugin --with-sql=plugin --with-pgsql --with-mysql --with-sqlite --with-zlib --with-libcap --with-ssl=openssl --with-ssldir=/etc/pki/dovecot --with-solr --with-docs --with-bzlib configure: error: unrecognized option: --docdir=/usr/share/doc/dovecot-2.2.0 I found here: http://www.dovecot.org/list/dovecot/2011-April/058420.html that --docdir option exists when autoconf version > 2.60. Yet: $ rpm -qa | grep autoconf autoconf-2.63-5.1.el6.noarch So, what may be wrong? Please help. Thanks, Nick

2 12