- dovecot - dovecot.org

Re: Re: auth: Warning: DNS lookup took 1.550 s
by Joseph Tam 06 Feb '15

06 Feb '15

ML mail writes: > My fault here, I should have precised that the DNS query it tries to > resolve is simply the DNS name of my mailbox server > (mailboxserver.domain.com) So domain.com is hosted locally on DNS > servers on that very same network as the dovecot servers are located. > Furthermore all the resolvers I use in /etc/resolv.conf are also local > DNS resolvers on that same LAN. All the DNS servers (authoritative and > recursive) are using PowerDNS. That's why I was really puzzled to see > that it can take up to 1.5 seconds to query my own local DNS servers > which are in no way overloaded. That really doesn't change my answer, but since you control the entire DNS chain of query and response, you can further debug it at the server end via logs or network tracing. And you should still run a comprehesive DNS trace (e.g. http://dns.squish.net/) since a misconfiguration could still cause your DNS resolver to go on wild goose chases. In either case, it's probably not Dovecot related. If you want to triage it, just enter static entries into your proxy's /etc/hosts file. Or use bare IPs in your configurations. Joseph Tam <jtam.home(a)gmail.com>

1 0

Block folder names in IMAP
by André Peters 05 Feb '15

05 Feb '15

Hi, I just merged to Maildir "/" as separator with a fs layout. So I am afraid of running into problems when someone creates a folder named "new", "cur", etc. ... I know I could work this around, but isn't there a way to block folders by their name from being created? Thank you! -- André Peters

1 0

Bug when using METADATA and ACLs
by Sergio Talens-Oliag 05 Feb '15

05 Feb '15

Hi, I'm trying to use the current version of dovecot as the IMAP server for Kolab and things seem to be working more or less OK, but while working on it I've found a dovecot bug that can probably be fixed quickly by someone familiar with the code. I've found the problem using shared folders, but it is related to ACLs and METADATA. The problem appears when a user only has the 'l' (lookup) permission on a folder and later tries to get METADATA from all his or her folders; a sample session to ilustrate the problem: A1 GETACL "foo" * ACL foo admin akxeilprwtscd -admin "" sto(a)iti.es lrwstipekxacd A1 OK Getacl completed. A2 SETACL "foo" sto(a)iti.es l A2 OK Setacl complete. A3 GETACL "foo" * ACL foo admin akxeilprwtscd -admin "" sto(a)iti.es al A3 OK Getacl completed. A4 GETMETADATA "foo" (/private/vendor/kolab/folder-type /shared/vendor/kolab/folder-type) A4 NO [NOPERM] Permission denied A5 GETMETADATA "*" (/private/vendor/kolab/folder-type /shared/vendor/kolab/folder-type) <CORE DUMPED> The dovecot.log messages are: Feb 05 13:59:12 imap(sto(a)iti.es): Panic: file imap-client.c: line 636 (client_command_free): assertion failed: (client->output_cmd_lock == NULL) Feb 05 13:59:12 imap(sto(a)iti.es): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x756cf) [0x7f55ab3da6cf] -> /usr/lib/dovecot/libdovecot.so.0(+0x7572e) [0x7f55ab3da72e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f55ab38c575] -> dovecot/imap [sto(a)iti.es 127.0.0.1 GETMETADATA](+0x18c9e) [0x7f55abba5c9e] -> dovecot/imap [sto(a)iti.es 127.0.0.1 GETMETADATA](+0x18e9a) [0x7f55abba5e9a] -> dovecot/imap [sto(a)iti.es 127.0.0.1 GETMETADATA](+0x18ef4) [0x7f55abba5ef4] -> dovecot/imap [sto(a)iti.es 127.0.0.1 GETMETADATA](client_handle_input+0x115) [0x7f55abba61e5] -> dovecot/imap [sto(a)iti.es 127.0.0.1 GETMETADATA](client_input+0x75) [0x7f55abba65b5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7f55ab3ec51b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xbb) [0x7f55ab3ed59b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7f55ab3ec5a9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f55ab3ec628] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f55ab391a43] -> dovecot/imap [sto(a)iti.es 127.0.0.1 GETMETADATA](main+0x2b7) [0x7f55abb9a717] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f55aaff7ead] -> dovecot/imap [sto(a)iti.es 127.0.0.1 GETMETADATA](+0xd889) [0x7f55abb9a889] Feb 05 13:59:12 imap(sto(a)iti.es): Fatal: master: service(imap): child 32404 killed with signal 6 (core dumped) And the gdb output is (my binary has no debug symbols, so I guess it is not really useful): (gdb) bt full #0 0x00007f55ab00b165 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007f55ab00e3e0 in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x00007f55ab3da6c5 in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #3 0x00007f55ab3da72e in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #4 0x00007f55ab38c575 in i_panic () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #5 0x00007f55abba5c9e in client_command_free () No symbol table info available. #6 0x00007f55abba5e9a in ?? () No symbol table info available. #7 0x00007f55abba5ef4 in ?? () No symbol table info available. #8 0x00007f55abba61e5 in client_handle_input () No symbol table info available. #9 0x00007f55abba65b5 in client_input () No symbol table info available. #10 0x00007f55ab3ec51b in io_loop_call_io () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #11 0x00007f55ab3ed59b in io_loop_handler_run_internal () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #12 0x00007f55ab3ec5a9 in io_loop_handler_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #13 0x00007f55ab3ec628 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #14 0x00007f55ab391a43 in master_service_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #15 0x00007f55abb9a717 in main () No symbol table info available. If someone can look into it I will be grateful; of course if more info is needed I'm available to help as much as I can. Thanks in advance, Sergio. -- Sergio Talens-Oliag <sto(a)iti.es> <http://www.iti.es/> Key fingerprint = FF77 A16B 9D09 FC7B 6656 CFAD 261D E19A 578A 36F2

1 0

auth: Warning: DNS lookup took 1.550 s
by ML mail 05 Feb '15

05 Feb '15

Hello, I am running a dovecot and proxy server on two different virtual machines and on the dovecot proxy server I see around 5-6 times per day the following warning: Feb 03 16:15:12 auth: Warning: proxy(email(a)domain.com,xxx.xxx.xxx.xxx,<ABC123456789>): DNS lookup for mailboxserver.domain.com took 1.550 s I do not really understand how from time to time DNS queries are slow, I tried replicate this issue using dig to resolve the same DNS entry and it was always very fast. Is there any way I can debug better this issue? or is this nothing to worry about really? Regards ML

4 5

lazy_expunge + mdbox
by fernando.figaro＠uol.com.br 05 Feb '15

05 Feb '15

Hi, I'm studying an issue related to mdbox and lazy_expunge. If it is active in the imap configuration, when you delete a message (copy to new folder + expunge old folder), a copy is also sent to the expunge namespace. I realize that is something related to mdbox and lazy_expunge_only_last_instance and found almost no references except this one (http://hg.dovecot.org/dovecot-2.2/file/24d6708cea76/TODO) lazy_expunge_only_last_instance=yes + mdbox doesn't work, because refcounts don't update immediately One other suggestion I found was to disable 'move' capability. Does anyone has other news regarding this issue ? Thanks, Fernando

1 0

Re: auth: Warning: DNS lookup took 1.550 s
by Joseph Tam 04 Feb '15

04 Feb '15

ML mail writes: > I am not running a local DNS cache on the server. As suggested using a > local DNS cache would simply fix this issue but I am more interested to > know what is generating these slow DNS queries... As another poster has commented, a slow DNS response may not be anything related to your setup, but caused by upstream DNS service. Slow DNS response or timeouts is not uncommon, and if you're only getting 6 per day, you should count yourself lucky. If it's the same FDQN that's being delayed, you can maybe run an online DNS diagnostic -- they're may be some bum delegation or unsync'd data you can report, but it will probably not be worth your time to chase this to ground unless it's causing your client to get hung. Joseph Tam <jtam.home(a)gmail.com>

1 0

Hitting wall at 2048 IMAP connections
by Ron Cleven 04 Feb '15

04 Feb '15

We are gradually rolling out Dovecot (IMAP only, no POP3) to our customer base. We are replicating between a pair of CentOS 7 boxes. All has been working wonderfully. However, to be sure our rollout continues to go smoothly, we put together a simple benchmark client program to fire up X persistent IMAP connections (using hundreds of mailboxes) that login, list the folders, select the INBOX, periodically FETCH an email from the INBOX, and otherwise sit in an IDLE loop. As long as we keep the number of concurrent IMAP connections under 2k, everything works fine. 2,000 processes generate a minimal load on the server. However, 2048 is a "hard limit" for number of IMAP processes on a box the way things are configured right now. The number (2048) is a bit too magical to be anything but a misconfiguration of either some kernel limit or a dovecot configuration limit. I have been unable to figure out where else to look. I have pasted in my dovecot config below along with the kernel setting for max_user_instances. Hoping someone can tell me what stupid mistake I have made or what else to check. Just an aside, we front-end this with a separate set of proxy servers that provide an SSL front-end, hence, no SSL in the dovecot config. /proc/sys/fs/inotify/max_user_instances = 4096 # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-123.13.1.el7.x86_64 x86_64 CentOS Linux release 7.0.1406 (Cor e) auth_master_user_separator = * auth_mechanisms = plain login default_internal_user = sysadm default_login_user = sysadm default_vsz_limit = 512 M disable_plaintext_auth = no doveadm_password = ************** doveadm_port = 12345 imap_max_line_length = 128 k listen = * mail_gid = 2001 mail_location = maildir:~/Maildir mail_plugins = notify replication mail_uid = 2001 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 namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = scheme=PLAIN /z/imap/usr/master-users driver = passwd-file master = yes pass = yes } passdb { args = scheme=PLAIN username_format=%u /z/imap/usr/users driver = passwd-file } plugin { mail_replica = tcp:imap0s sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_max_actions = 32 sieve_max_redirects = 4 sieve_max_script_size = 1M } protocols = imap pop3 sieve service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = sysadm } unix_listener replication-notify { mode = 0666 user = sysadm } } service auth { unix_listener auth-userdb { mode = 0777 } } service doveadm { inet_listener { port = 12345 } user = sysadm } service imap { process_limit = 4096 } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { process_limit = 4096 } service replicator { process_min_avail = 1 } ssl = no userdb { args = username_format=%u /z/imap/usr/users driver = passwd-file } protocol lda { mail_plugins = sieve notify replication } protocol imap { mail_max_userip_connections = 40 } protocol sieve { managesieve_max_line_length = 65536 }

5 4

Corruption of index files
by Oliver Welter 04 Feb '15

04 Feb '15

Hi All, after upgrading my mail server (dovecot 1.1.7 -> 2.2.13) I get tons of messages about corrupted index files in the syslog ("Error: Corrupted transaction log" and "Warning: fscking index file .. dovecot.index". I tried flock and even dotlock, but the problems persist. The system is a VPS with an overlay filesystem which did work flawlessly with the old dovecot install and is not reporting any errors in the host machine. From time to time I get warnings about an exceeded inotify limit for the dovecot user - might this be a problem? Anybody has an idea what might be the cause those problems and how to track them down. Oliver -- Protect your environment - close windows and adopt a penguin!

2 4

Upstart script for Poolmon
by Listas＠Adminlinux 03 Feb '15

03 Feb '15

Hi My servers are Ubuntu 14.04 and I'm needing to make a Upstart script for Poolmon. Does someone already made this and could to share with us ? Thanks! -- Thiago henrique

1 1

Master user without pass=yes error
by Thomas HUMMEL 03 Feb '15

03 Feb '15

Hello Timo, I just tried the master user feature with a very simple setup (Dovecot v2.2.15) : !include auth-master.conf.ext -> passwd-file passdb !include auth-ldap.conf.ext -> ldap passdb (userdb prefetched) without auth_bind=yes without pass=yes I get this userdb lookup error : dovecot: auth: passwd-file(masteruser,157.99.64.42,master,<4Pgesh0OygCdY0Aq>): Master user logging in as normaluser dovecot: auth: Error: prefetch(normaluser,157.99.64.42,<4Pgesh0OygCdY0Aq>): userdb lookup not possible with only userdb prefetch dovecot: imap: Error: Internal auth failure (client-pid=10449 client-id=1) dovecot: imap-login: Internal login failure (pid=10449 id=1) (internal failure, 1 successful auths): user=<normaluser>, method=PLAIN, rip=157.99.64.42, lip=157.99.64.81, mpid=10570, TLS, session=<4Pgesh0OygCdY0Aq> with pass=yes, it works. Feb 2 17:51:24 langres dovecot: auth: passwd-file(masteruser,157.99.64.42,master,<YmjAwx0O0gCdY0Aq>): Master user logging in as normaluser Feb 2 17:51:24 langres dovecot: imap-login: Login: user=<normaluser>, method=PLAIN, rip=157.99.64.42, lip=157.99.64.81, mpid=11647, TLS, session=<YmjAwx0O0gCdY0Aq> I dont quite understand why because the documentation states that 'pass=yes' "means that Dovecot verifies that the login user really exists before allowing the master user to log in. Without the setting if a nonexistent login username is given,[...]" Here, 'normaluser' exists in the ldap passdb so, even with pass=no, I'm not supposed to be in the 'nonesxistent login username' case. Can you help ? thanks. -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Groupe Exploitation et Infrastructure

1 2