- dovecot - dovecot.org

[Dovecot] dovecot-sql.conf - Unknown setting: driver
by jeep＠rahul.net 27 Apr '13

27 Apr '13

Im upgrading my dovecot from 2.1.14 to dovecot 2.2.1 on linux. Im using the same configuration file against my MySQL db and getting the following error: doveconf -n # 2.2.1: /opt/dovecot221/etc/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /opt/dovecot221/etc/dovecot/conf.d/dovecot-sql.conf line 2: Unknown setting: driver dovecot-sql.conf: # The mysqld.sock socket may be in different locations in different systems driver = mysql # Use "host= ... pass=foo#bar" if your password has '#' character connect = host=/var/run/mysqld/mysqld.sock dbname=mydb user=username password=pass password_query = SELECT userid AS username, domain, password \ FROM users WHERE userid = '%n' AND domain = '%d' user_query = SELECT home, uid, gid FROM users WHERE userid = '%n' AND domain = '%d' home=/opt/ii/%1n/%n/INBOX # For using doveadm -A: iterate_query = SELECT userid AS username, domain FROM users That file worked fine in the last version. Looking at the docs 'driver' is still a valid setting. Can someone help me figure out why its complaining? Ive even Im lost as to why this error is occuring unless the error itself is actually another problem and the wrong error is popping up. Been working on this for a day and cant figure it out. Thanks in advance! /mf/home/jeep/shell/.signature

2 3

[Dovecot] Replication fails with "Remote dsync doesn't use compatible protocol"
by Rich Wales 27 Apr '13

27 Apr '13

I can't get replication to work in Dovecot 2.2.1. I'm getting the following error on the machine where I'm initiating the replication: richatwork dovecot: doveadm: Error: dsync-remote(richatwork): Error: dsync(local): Remote dsync doesn't use compatible protocol Both the local and remote servers are running identical versions of Dovecot (2.2.1), so I don't understand why I would be having any sort of "compatible protocol" problem. Any ideas? I posted the "dovecot -n" output for both servers in my earlier e-mail on this issue, which I sent about 24 hours ago (and which I assume was too long for people to be willing to read). Rich Wales richw(a)richw.org

1 1

[Dovecot] ios clients and namespace trouble
by Kelsey Cummings 27 Apr '13

27 Apr '13

We migrated to dovecot from courier and maintained a courier compatible namespace configuration. This resulted in ios clients needing to be manually configured in order to use the special folders correctly (delete messages, save drafts, etc) either by being given the correct "Path Prefix" or by manually selecting the special folders. I can't fathom why apple has chosen not to support or can't detect namespace correctly and require manual configuration but if they haven't done it by now they must have some reason for it and aren't going to fix it any time soon. Are there any creative solutions to fixing the i-clients and preventing them from needing manual configuration? -K

2 3

[Dovecot] .dovecot.sieve/tmp)failed: Not a directory
by JC Putter 25 Apr '13

25 Apr '13

stat(/var/spool/vmail/example.com/user/.dovecot.sieve/tmp)failed: Not a directory auth_mechanisms = plain login disable_plaintext_auth = no first_valid_uid = 2000 last_valid_uid = 2000 mail_gid = 2000 mail_location = maildir:/var/spool/vmail/%d/%n mail_uid = 2000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mbox_write_locks = fcntl passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } service auth { unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } According to the Wiki "It is not wise to place this link inside your mail store, as it may be mistaken for a mail folder. Inside a maildir for instance, the default .dovecot.sieve would show up as phantom folder */dovecot/sieve* in your IMAP tree." Sorry i am a bit of a noob, the docs don't explain clearly what to do...

3 2

[Dovecot] Replication -- multiple users, three or more servers?
by Rich Wales 24 Apr '13

24 Apr '13

I'm running Dovecot 2.2.1 on an Ubuntu 12.04.2 server, with half a dozen accounts for various family members. I want to set up replication involving at least three Ubuntu servers, with different users replicated on different sets of servers. For example, I might have mail for "user1" replicated on "server1", "server2", and "server3"... while mail for "user2" would be on "server1" and "server2"... and mail for "user3" would be on "server1" and "server3". I've read the wiki page (http://wiki2.dovecot.org/Replication) but I'm still confused. I'd love to see an example that clearly shows how to set up specific individual mail users to be replicated on a different set of servers for each user, like what I described above. Rich Wales richw(a)richw.org

2 3

[Dovecot] login crashes - maybe too many simultan connections
by Frank Leonhardt 24 Apr '13

24 Apr '13

Hallo, since a few days, users sometimes have problems connecting to our mailserver, in the mail.err are many lines like this: Apr 23 11:14:25 psy2 dovecot: dovecot: child 17607 (login) killed with signal 11 (core dumps disabled) (ip=xx.xx.146.84) Users who are already logged in keep connected, but new connections are not possible.This happens only between 10 am and 3 pm, never in the early morning or at night, so i assume, maybe this is caused by too many simultaneous connections? After restarting dovecot the problem is temporary solved, new users may connect, but after one or a few days, this may happen again. # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.1 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: alle mail_location: maildir:~/Maildir fsync_disable: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 auth default: passdb: driver: pam args: dovecot userdb: driver: passwd May anybody help? Thanks in advance! Greetings from Frank.

2 1

[Dovecot] Strange issue with doveadm user
by Antoine Nguyen 24 Apr '13

24 Apr '13

Dear all, I encounter a strange issue with the *doveadm user* command. (dovecot 2.1.16) I try to retrieve information about a specific user but dovecot says it doesn't exist (whereas I just created it). The following command fails: $ sudo -u vmail doveadm user pouet(a)domain.tld userdb lookup: user pouet(a)domain.tld doesn't exist If I try a more global lookup, the user is properly found: $ sudo -u vmail doveadm user *(a)domain.tld user1(a)domain.tld *pouet(a)domain.tld* Sending a query for another user works well. For example : $ sudo -u vmail doveadm user user1(a)domain.tld userdb: user1(a)domain.tld home : /var/vmail/domain.tld/user1 uid : 500 gid : 500 quota_rule: *:bytes=100M I really don't understand what's happening... The only difference I see between the users is that user1 was created when I was using dovecot 1.2... Thanks for your help.

1 1

Re: [Dovecot] Using dsync to export mail to remote IMAP account
by Joseph Tam 24 Apr '13

24 Apr '13

Timo Sirainen writes: >> I've read the web/man pages on dsync, but it's not clear to me whether >> dsync can be used to export (rather than import) a user's mailbox to a >> remote non-dovecot IMAP account. > > It should be possible at some point, but currently probably won't work > very well. Ah, thanks for the clarification. >> dsync(localuser): Error: user localuser: Initialization failed: >> Namespace '': Unknown mail storage driver imapc >> dsync(localuser): Fatal: User init failed > > But this looks like you simply haven't compiled Dovecot with imapc > support. See if > > dovecot --build-options|grep storage > > returns imapc. Right you are. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Feature request: Configure CONFIG_MODULE_DIR and AUTH_MODULE_DIR at runtime
by Rickard Nilsson 23 Apr '13

23 Apr '13

Hi! I am running dovecot 2.1.16 on NixOS (http://nixos.org) and I have been fighting the dynamically loaded dovecot modules/plugins a bit. The problem is that in Nix/NixOS all packages are completely isolated from each other (each package has a separate /lib, /libexec, /bin etc, with only its own files in it). So dovecot has all its modules under /nix/store/xxx-dovecot/{lib,libexec}/dovecot, and the Pigeonhole modules are under /nix/store/yyy-pidgeonhole/{lib,libexec}/dovecot. Now, dovecot wants to load modules only from one directory, so I created a "virtual" package that unifies all modules in /nix/store/zzz-dovecot-plugins/{lib,libexec}/dovecot. I can then use this directory as the "mail_plugin_dir" setting in dovecot.conf. This works fine, dovecot can then find the "sieve" mail plugin. The problem is the service and auth modules, that dovecot tries to load from the compile-time set MODULE_DIR/{settings,auth}. This is a problem for me, because I can't set the module path during compilation since that introduces a circular dependency between the dovecot package and the virtual dovecot-plugins package. I have solved this by hacking dovecot to read an environment variable, DOVECOT_CONFIG_MODULE_DIR, in the config_parse_load_modules function. This way I can inject my module path during runtime. But this only works for the master process, not the config process which seems to reset its environment (I assume it does this when dropping privileges). So I did another hack which lets me pass an argument to the config process which contains the module path. I can then set this argument in dovecot.conf by "service config { executable = config /my/module/path }". These hacks work, and I can now use both the sieve mail plugin and the sieve service. I have attached the patch, but this is not a request to add it to the source. My hack is a hack because I don't know enough about the inner workings of dovecot to solve it in a good way. Rather, I'm asking for some way to configure the module path in dovecot, either as an argument to the master process or as a setting in dovecot.conf. A bonus would be the ability to specify several paths that dovecot would search, then I can do away with my virtual module package. Best regards, Rickard Nilsson

3 3

[Dovecot] imap Panic: file istream-seekable.c: line 253 (i_stream_seekable_read): assertion failed: (stream->istream.v_offset + stream->pos <= sstream->write_peak)
by Pascal Volk 23 Apr '13

23 Apr '13

Hi Timo, just another crash - using 2.2.1 (c95cea6e1389). Regards, Pascal

2 1