April 2013 - dovecot - dovecot.org

[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

[Dovecot] Running LMTP as a user other than the root user
by Axel Luttgens 23 Apr '13

23 Apr '13

Hello, With this one in Postfix' main.cf: virtual_transport = lmtp:unix:/_ROOT/var/run/dovecot/lmtp and Dovecot settings reproduced at the end of this message, there is no problem for having mail delivered into a user's INBOX. But as soon as I try the security improvement suggested in the docs: service lmtp { user = dovemailer } this is what I get in the logs: postfix/smtpd[52588]: connect from localhost[127.0.0.1] postfix/smtpd[52588]: E86B5BD2BA0: client=localhost[127.0.0.1] postfix/cleanup[52594]: E86B5BD2BA0: message-id=<20130416171203.E86B5BD2BA0(a)ALMba.local> postfix/qmgr[88232]: E86B5BD2BA0: from=<test(a)example.com>, size=315, nrcpt=1 (queue active) dovecot[52568]: lmtp(52596): Debug: none: root=, index=, control=, inbox=, alt= dovecot[52568]: lmtp(52596): Connect from local dovecot[52568]: lmtp(52596): Debug: Loading modules from directory: /_ROOT/dovecot-2.1.16-0.3.4/lib/dovecot dovecot[52568]: lmtp(52596): Debug: Module loaded: /_ROOT/dovecot-2.1.16-0.3.4/lib/dovecot/lib10_quota_plugin.so dovecot[52568]: auth: Error: userdb(test(a)example.com): client doesn't have lookup permissions for this user: userdb reply doesn't contain uid (to bypass this check, set: service auth { unix_listener /_ROOT/var/run/dovecot/auth-userdb { mode=0777 } }) dovecot[52568]: lmtp(52596): Error: user test(a)example.com: Auth USER lookup failed dovecot[52568]: lmtp(52596): Debug: auth input: postfix/lmtp[52595]: E86B5BD2BA0: to=<test(a)example.com>, relay=ALMba.local[/_ROOT/var/run/dovecot/lmtp], delay=19, delays=19/0.02/0.17/0.06, dsn=4.3.0, status=deferred (host ALMba.local[/_ROOT/var/run/dovecot/lmtp] said: 451 4.3.0 <test(a)example.com> Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command)) dovecot[52568]: lmtp(52596): Disconnect from local: Client quit (in reset) postfix/smtpd[52588]: disconnect from localhost[127.0.0.1] and the message of course remains in Postfix' queue. I understand that the +x workaround suggested for the auth-userdb socket (so as to have 0777 permissions instead of 0666) relies on provisions made in Dovecot's code in order to relax some requirements. But I still need help for a correct interpretation... The socket receives 0666 permissions by default; any process should thus be able to read from/write to that socket. So, why set such a default, since it is anyway going to yield un-intuitive results? And, as far as the log messages are concerned: "client doesn't have lookup permissions...". Who's the client here? Still from the log: "client doesn't have lookup permissions for this user:". Which user? "userdb reply doesn't contain uid" The userdb query seems to have failed; but does it mean that is should explicitly return a uid? TIA, Axel $ doveconf -n # 2.1.16: /_ROOT/etc/dovecot/dovecot.conf # OS: Darwin 12.3.0 x86_64 auth_verbose = yes disable_plaintext_auth = no mail_debug = yes mail_gid = dovemailer mail_location = mbox:~/mboxes:INBOX=~/mboxes/inbox mail_uid = dovemailer 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 ihave mbox_write_locks = fcntl passdb { args = /_ROOT/etc/dovecot/db.conf driver = sql } plugin { quota = dirsize:User quota quota_rule = *:storage=1M } ssl = no userdb { driver = prefetch } userdb { args = /_ROOT/etc/dovecot/db.conf driver = sql } protocol lmtp { mail_plugins = quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xv%08Xu } protocol imap { mail_plugins = quota } With above settings, the permissions on socket auth-userdb are: srw-rw-rw- 1 dovecot wheel 0 16 avr 16:05 auth-userdb and the full config for service lmtp is: $ doveconf service/lmtp service lmtp { chroot = client_limit = 1 drop_priv_before_exec = no executable = lmtp extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 type = unix_listener lmtp { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B }

1 1

[Dovecot] Dovecot 2.2.1: typo in src/lib-http/Makefile.in
by Piper Andreas 23 Apr '13

23 Apr '13

Hello, there seems to be a typo in the dovecot-2.2.1-sources: in dovecot-2.2.1/src/lib-http/Makefile.in at line 758 the two lines ../lib-test/libtest.la \ ../lib/liblib.la do not fit into the Makefile-syntax. At compile-time they produce the error make: Fatal error in reader: Makefile, line 725: Unexpected end of line seen If I remove these two lines, everything compiles fine. Could you please check this. Thanks, Andreas -- ________________________________________________________________________ Dr. Andreas Piper, Hochschulrechenzentrum der Philipps-Univ. Marburg Hans-Meerwein-Straße, 35032 Marburg, Germany Phone: +49 6421 28-23521 Fax: -26994 E-Mail: piper(a)HRZ.Uni-Marburg.DE

2 1

[Dovecot] Dovecot 2.1.16: "default_client_count" written to the logs
by Axel Luttgens 23 Apr '13

23 Apr '13

Hello, As to be expected with low system limits, a warning may be written to the logs: master: Warning: fd limit (ulimit -n) is lower than required under max. load (256 < 1000), because of default_client_count Shouldn't it read "default_client_limit" instead of "default_client_count"? It seems that the warning is written only when reloading Dovecot, not upon Dovecot's startup. Is this deliberate? Thanks, Axel

2 2

[Dovecot] Integrate mbox into mdbox
by lutz.niederer＠gmx.net 23 Apr '13

23 Apr '13

Hi! I have several mbox files (unstructured, only the big plain mbox files) and I would like to integrate/read these mbox files into mdbox subfolders of specific users. This is a production system and I don't want to disturb running services and I am a bit afraid of not using the right command and maybe destroying (or whatever) their mailboxes. I am sure it is pretty easy. Can someone please tell me the correct dsync command line that I should use to read each mbox file (one-way) into the specific folder of the mdbox folder structure of a specific user? Thanks a lot, -lutzn

3 4

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

23 Apr '13

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. (The intention is to use it whenever a user leaves and wants to copy their local mail to Google or whatever. I currently use uw-imapd's mailutil -- it works, but it's dreadfully slow.) As a first crack at it, I tried (on the dovecot server) dsync -o imapc_user=remoteuser -o imapc_password=remotepassword -o imapc_host=remote-imap-server -o imapc_port=993 -o imapc_ssl=imaps -o imapc_features=rfc822.size -o imapc_list_prefix=remoteprefix -o mailbox_list_index=no backup -f -u localuser imapc: I got this error: dsync(localuser): Error: user localuser: Initialization failed: Namespace '': Unknown mail storage driver imapc dsync(localuser): Fatal: User init failed Is exporting mail to a remote (non-dovecot) IMAP account even doable with dsync, or am I completely off-track? Joseph Tam <jtam.home(a)gmail.com>

3 2

[Dovecot] Dovecot Failover
by Nikolaos Milas 22 Apr '13

22 Apr '13

Hello, Assuming we have two (low traffic) servers (on different data centers) replicated using dsync, what is the best way to automatically direct users to the main server when it is up and to the redundant one when the main server is down? Using DNS? I've seen that DNS-based failover has generally issues (for example: http://serverfault.com/questions/60553/why-is-dns-failover-not-recommended, which is informative although it refers to web servers). What is the suggested approach? HAProxy? Heartbeat/Pacemaker? Any advice will be appreciated. Thanks and regards, Nick

5 5