- dovecot - dovecot.org

[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

[Dovecot] Sieve - BCC
by iliusha 21 Apr '13

21 Apr '13

Hi ! Can you help me please with sieve plugin for dovecot I have this rule: /require ["variables", "envelope", "fileinto", "subaddress", "imap4flags"]; if anyof ( address :is [ "to", "cc", "bcc" ] "test(a)example.com", envelope :contains "to" "test(a)example.com" ) { fileinto "Test"; stop; }/ and if somebody sends me an email with "test(a)example.com" in "TO" or "CC" - then sieve works properly and put this email in Test folder, but i can't understand why if it sends e-mail to "test(a)example.com" in BCC - sieve don't move it to Test but leave it in Inbox? If i run sieve-test -faD .dovecot.sieve "Message-ID" i get: /Performed actions: * store message in folder: Test Implicit keep: (none) sieve-test(root): Info: final result: success/ but in dovecot log i get: /Info: sieve: msgid=<20130421074437.570EA2BA1C1F(a)mail.com>: stored mail into mailbox 'INBOX'/ and email is going to Inbox folder, instead Test. Please tell me what i am doing wrong and how i can make sieve to work properly with BCC. Thank You. -- View this message in context: http://dovecot.2317879.n4.nabble.com/Sieve-BCC-tp41757.html Sent from the Dovecot mailing list archive at Nabble.com.

4 10

[Dovecot] imap Fatal: bzlib.read(~/mdbox/storage/m.317): Out of memory
by Pascal Volk 20 Apr '13

20 Apr '13

Hi Timo, today I found a raw backtrace after the bzlib.read() out of memory message. Regards, Pascal

1 1

[Dovecot] listen directive changed?
by Nick Edwards 20 Apr '13

20 Apr '13

Timo, Is the global listen directive supposed to be a governing directive, like in apache? or is it there just in case you dont use it in protocols? I set a specific ipv6 address in global listen, but use [::] in proto Testing to a secondary IP, not in the global listen, it still connects, so can I ask has the original use of global listen been deprecated? ciao

3 6

[Dovecot] Moving mail servers, moving mailboxes
by Gregory Sloop 19 Apr '13

19 Apr '13

So, I've done some searching - but search terms are hard to come by, that work, for this query. In short, migrating a RHEL 5.9 server running the back-ported Dovecot 1.0.7 To: Ububtu 12.04 with 2.0.19, I believe. [I'm not against compiling a more recent version if there's some real advantage to doing so. But I'd certainly prefer to stay with the packaged version.] Most users are POP3, with some leaving messages on the server for a while. Other users are IMAP - whole mail repository on server. --- In an ideal world, I'd like to simply copy all the mailboxes/dirs from one server to the other. [Local/LAN file copies are possible] It would be great if the message ID's wouldn't change, so the read/unread/new etc status all all the messages wouldn't change between the two servers for POP/IMAP. --- So, does anyone have a reasonable walk-through for doing so? Is this a poor idea? Should I simply set myself on fire now and save everyone a lot of hassle? :) Would you suggest an alternative, and tell me if it might achieve the objectives above? I'm more than glad to take pointers to threads on this topic. I just haven't been able to dredge this up with my Google-foo. TIA -Greg

5 6