- dovecot - dovecot.org

Re: Client Limit reached in Dovecot
by Daniel Tröder 21 Jul '15

21 Jul '15

Hallo :) On mailinglists please reply below the previous post. It's easier to read this way. Am 21.07.2015 um 11:26 schrieb Chandran Manikandan: > Dear Daniel, > Thanks for your kind response. As per your above command got below > result. but i couldn't see below settings are local.conf,10-master.conf > or toaster.conf. Where it's retrieved. > default_process_limit=100 > default_client_limit=1000 > default_vsz_limit=256 M > service/imap/process_limit=1024 > service/imap/client_limit=1 > service/imap/service_count=1 > service/imap/vsz_limit=18446744073709551615 B > service/imap-login/process_limit=0 > service/imap-login/client_limit=0 > service/imap-login/service_count=1 > service/imap-login/vsz_limit=18446744073709551615 B My guess is, that service/imap-login/process_limit=0 disables the setting and then default_process_limit=100 applies. As to where default_process_limit=100 comes from… try: grep -r default_process_limit /etc/dovecot Greeting Daniel > > > > On Tue, Jul 21, 2015 at 4:56 PM, Daniel Tröder <troeder(a)univention.de > <mailto:troeder@univention.de>> wrote: > > Am 21.07.2015 um 10:35 schrieb Chandran Manikandan: > > Dear Friends, > > I have faced below issues since two weeks to till now. Could anyone help me > > to rectify this issue. > > > > Below message retrieve from logs and getting disconnection from Outlook and > > other email clients. > > > > Error Message > > > > Jul 20 10:33:35 master: Warning: service(imap-login): process_limit (100) > > reached, client connections are being dropped > > > > My local.conf from dovecot folder > > > > protocol imap { > > imap_client_workarounds = "delay-newmail" > > mail_max_userip_connections = 20 > > default_process_limit = 300 > > } > This should be just "process_limit" without "default". But it's > unnecessary, as you set globally default_process_limit. > > > 10-master.conf > > > > default_process_limit = 300 > > default_client_limit = 1000 > > > > service imap-login { > > inet_listener imap { > > # process_limit = 15 > > # client_limit = 300 > > #port = 143 > > } > It is the "imap-login" process_limit that is reached. With the set > default_process_limit=300 this shouldn't happen. So maybe there is some > setting somewhere else, that is not shown. Please supply the output of: > > doveconf -S | egrep '(default|imap/|imap-login).*(limit|service_count)' > > Greetings > Daniel Tröder > > > > > -- > *Thanks,* > *Manikandan.C* > *System Administrator*

1 0

Dovecot in UCS
by Daniel Tröder 21 Jul '15

21 Jul '15

Hello :) I hope you can forgive me a little advertisement: The English translation of my blog post on the Dovecot integration I did for the Univention Corporate Server (UCS) is online: https://www.univention.com/2015/07/dovecot-is-the-default-imappop3-mail-ser… UCS is a Debian based Linux Distribution, everything - incl. management bits - is OSS. There is a "Core Edition" that you can download and use (also commercially) for free, that is - despite its name - feature complete: https://www.univention.com/downloads/ucs-download A lot of interesting Dovecot features can be changed without breaking things, so this blog post may be interesting to everyone. The German version can be found here: https://www.univention.de/2015/07/mailserver-dovecot-als-standard-imappop3-… Greetings Daniel Tröder

1 0

[Dovecot] Dovecot FTS using ElasticSearch
by Darvin Denmian 21 Jul '15

21 Jul '15

Hi, I would like to know if is possible to use ElasticSearch instead of Solr for FTS. Regards, Erick Vitor de Barros.

6 6

[Dovecot Antispam] Can't seem to load plugin
by James Lott 21 Jul '15

21 Jul '15

Hello list, I'm hoping there is a user of the antispam plugin out there who might be able to lend a pointer or two. I am running dovecot 2.2.18 on FreeBSD 10 (doveconf -n attached), where I have installed the binary dovecot2-antispam-plugin package. I have put together what should, in my estimation, be a working configuration for the plugin. I have reviewed the man page and the online documentation, and I think at the *very least* I should be seeing errors for something not working correctly. However, what I have is a great deal more troubling. There is no sign on the plugin even attempting to load. No log entries, no errors, nothing. The plugin is definitely in the right place with the right name, since I let the package manager handle all of that for me root@zerolag:~ # ls -l /usr/local/lib/dovecot/lib90_antispam_plugin.so -rwxr-xr-x 1 root wheel 32488 Jul 2 09:41 /usr/local/lib/dovecot/lib90_antispam_plugin.so I am unable to make any sense of this. Thanks in advance for any pointers :) -- James Lott

4 6

Problems with IMAP/POP and dovecot director on backend (director_proxy_maybe)
by dominik 20 Jul '15

20 Jul '15

Hello dovecot community, first of all: dovecot ist great! ;) ...nevertheless I´ve got some problems to get my director scenario running as needed/expected :( My scenario: I´d like to configure two dovecot backends, without the need for multiple dovecot instances. Both backend servers are active/active and act on top of a glusterfs storage, which implies the need for dovecot director. As described in release notes (v2.2.17) this should be possible by setting the extra field "director_proxy_maybe=yes".: "+ director: Implemented director_proxy_maybe passdb extra field to be able to run director and backend in the same Dovecot instance. (LMTP doesn't support mixed proxy/non-proxy destinations currently.)" My setup: * 1 LMTP client (SLES11p3 with postfix) * 1 IMAP/POP3 client (Debian8 with thunderbird 31.6.0): 10.0.0.26. The client connects through a dovecot mailproxy or direct. * 1 dovecot mailproxy: 10.0.1.151 * 2 mailbox backends running dovecot v2.2.18 on SLES11p3 with mail_location pointing to a glusterfs-mountpoint (GlusterFS: v3.6.3) * mailbox01.example.de: 10.0.2.21 * mailbox02.example.de: 10.0.2.22 * mailbox-gluster.example.de points as an A-RR to 10.0.2.21 and 10.0.2.22. My problem: With LMTP everything works fine (thanks for this!). The director sets the "host" field correctly and all delivery attempts work fine to the estimated backend servers. But when I try to connect via IMAP-/POP3-client (through proxy or direct) it fails with following log messages. It seems, that the director doesn´t set the host field within IMAP/POP sessions before proxying!? auth: Debug: auth client connected (pid=46359) imap-login: ID sent: x-session-id=V3iJmU4biAAK/BAa, x-originating-ip=10.0.0.26, x-originating-port=54408, x-connected-ip=10.0.1.151, x-connected-port=143, x-proxy-ttl=4: user=<>, rip=10.0.1.151, lip=10.0.2.21, session=<RVnAm04bzwAK/FCX> auth: Debug: client in: AUTH 1 PLAIN service=imap session=RVnAm04bzwAK/FCX lip=10.0.2.21 rip=10.0.1.151 lport=143 rport=54735 resp=<hidden> auth: Debug: ldap(tester(a)example.de,10.0.1.151,<RVnAm04bzwAK/FCX>): bind search: base=o=example,c=de filter=(&(|(uid=tester@example.de)(mail=tester@example.de))(!(<cut-cut-cut>)) [...] auth: Debug: client passdb out: OK 1 user=tester(a)example.de director_proxy_maybe=yes lip=10.0.2.21 lport=143 proxy pass=<hidden> imap-login: Debug: Ignoring unknown passdb extra field: director_proxy_maybe imap-login: Debug: Ignoring unknown passdb extra field: lip imap-login: Debug: Ignoring unknown passdb extra field: lport imap-login: Error: proxy: host not given: user=<tester(a)example.de>, method=PLAIN, rip=10.0.2.151, lip=10.0.2.21, session=<RVnAm04bzwAK/FCX> imap-login: Disconnected (internal failure, 1 successful auths): user=<tester(a)example.de>, method=PLAIN, rip=10.0.2.151, lip=10.0.2.21, session=<RVnAm04bzwAK/FCX> Finally the output of "doveadm proxy list" is empty! "doveadm director map" output after a successfull LMTP delivery attempt (before: doveadm director flush all): user hash mail server ip expire time tester(a)example.de 856838019 10.0.2.21 2015-07-20 15:49:18 "doveadm director map" output after a failed IMAP session attempt (before: doveadm director flush all): user hash mail server ip expire time tester(a)example.de 856838019 10.0.2.21 2015-07-20 15:50:02 So, director seems to work in this constellation, but only for LMTP and not for IMAP/POP Proxy :( Has anybody configured this before? Thanks in advance and a lot of greetings from Germany, Dominik ############ My config (mailbox01.example.de. mailbox02.example.de is identical, except the hostname): # doveconf -n # 2.2.18: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: Linux 3.0.101-0.46-default x86_64 SUSE Linux Enterprise Server 11 (x86_64) auth_cache_negative_ttl = 0 auth_cache_ttl = 5 mins auth_debug = yes auth_master_user_separator = "#" auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = sha1 director_consistent_hashing = yes director_mail_servers = mailbox-gluster.example.de director_servers = 10.0.2.21:9090 10.0.2.22:9090 disable_plaintext_auth = no imap_metadata = yes listen = mailbox01.example.de lmtp_proxy = yes lmtp_save_to_detail_mailbox = yes lock_method = dotlock login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> %k login_trusted_networks = 10.0.2.0/24 mail_access_groups = dovecot mail_attribute_dict = file:Maildir/dovecot-metadata mail_debug = yes mail_fsync = always mail_location = maildir:~/Maildir/ mail_plugins = quota acl 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 index ihave duplicate mmap_disable = yes namespace { inbox = yes location = mailbox Archiv { special_use = \Archive } mailbox Entwürfe { special_use = \Drafts } mailbox "Gelöschte Objekte" { special_use = \Trash } mailbox "Gesendete Objekte" { special_use = \Sent } mailbox Sent { special_use = \Sent } mailbox Trash { special_use = \Trash } mailbox unerwünscht { special_use = \Junk } prefix = INBOX/ separator = / } namespace { disabled = yes list = children location = maildir:%%h/:INDEXPVT=~/dovecot.index.shared/%%u/ prefix = SHARED/%%u/ separator = / type = shared } passdb { args = /***********/passwd.masterusers driver = passwd-file master = yes } passdb { args = /etc/dovecot/ldap.conf driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db } postmaster_address = postmaster@%d protocols = " imap lmtp pop3" service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/saslauth_via_dovecot { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0666 user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0600 user = $default_login_user } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0666 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 24245 } } service imap-login { executable = imap-login director inet_listener imaps { port = 0 } } service ipc { unix_listener ipc { user = dovecot } } service lmtp { inet_listener lmtp { port = 24 } } service managesieve-login { inet_listener sieve { address = mailbox01.example.de } } service pop3-login { executable = pop3-login director } ssl = no ssl_cipher_list = kEECDH+aRSA+AES256:kEDH+aRSA+AES256:ECDHE-RSA-AES256-SHA:DHE-RSA-AES256-SHA ssl_dh_parameters_length = 4096 ssl_options = no_compression ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 !TLSv1.1 userdb { args = /etc/dovecot/ldap.conf driver = ldap } verbose_proctitle = yes protocol lmtp { auth_socket_path = director-userdb mail_plugins = quota notify mail_log } protocol imap { imap_id_log = * mail_plugins = quota fts fts_squat imap_quota mail_log notify acl imap_acl } protocol pop3 { mail_plugins = quota acl pop3_uidl_format = %fan } ################ My /etc/dovecot/ldap.conf: uris = ldap://ldap.example.de pass_filter = (&(|(uid=%u)(mail=%u))(!(<cut-cut-cut>))) pass_attrs = =proxy_maybe=yes, \ =director_proxy_maybe=yes user_filter = (&(|(uid=%u)(mail=%u)(mailAlternateAddress=%u))(!(<cut-cut-cut>))) user_attrs = =master_user=%u, \ =uid=%{ldap:qmailUID:12345}, \ =gid=%{ldap:qmailGID:12345}, \ =home=/mnt/testvol2/%{ldap:mailMessageStore}/%1{ldap:mail}/%{ldap:mail}/, \ =quota_rule=*:bytes=%{ldap:mailQuotaSize:128M} iterate_attrs = mail=user iterate_filter = (objectClass=qmailuser)

1 0

bug in group permission check
by krzf83＠gmail.com 19 Jul '15

19 Jul '15

Jul 19 01:05:27 sv1 dovecot: auth: Error: passwd-file(aa@ddd,89...24,<>): stat(/usr/dovecot-cfg/dom-home/ddd/etc/ddd/shadow) failed: Permission denied (euid=33454(dovecot) egid=33454(dovecot) missing +x perm: /usr/dovecot-cfg/dom-home/ddd, we're not in group 33795(sysgroup), dir owned by 32072:33795 mode=0710) root@sv1 [~]# sudo -u dovecot groups dovecot sysgroup root@sv1 [~]# sudo -u dovecot cat /usr/dovecot-cfg/dom-home/ddd/etc/ddd/shadow <prints content of the file> It seems that dovecot incorecly checks for group permissions not even trying to access file - probably cant handle that dovecot is part of more than 1 group. When its part of single group problem is not occuring.

2 1

feature suggestion: wildcard in userdb
by krzf83＠gmail.com 19 Jul '15

19 Jul '15

feature suggestion: wildcard in userdb aa:x:32009:32012::/home/usr/mail/bb::userdb_quota_rule=*:bytes=700M *:x:32009:32012::/home/usr/mail/bb: That would be usefull in many situation, for example to set default values per domain (userdb per domain) userdb { driver = passwd-file args = /usr/dovecot-cfg/userdb/%d }

1 0

Dovecot - Telnet error
by Sachin Kulkarni1 18 Jul '15

18 Jul '15

Hello All, I have installed dovecot and started it. However when I try to telnet getting below error means dovecot starting is not successful. telnet localhost 10110 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Connection to localhost closed by foreign host. Please advise. Thanks and Regards, Sachin Kulkarni ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================

4 3

Helper to open "/doc/wiki/.." paths; suggestions
by Christian Jaeger 18 Jul '15

18 Jul '15

I wrote this script to have an easier time looking at the doc paths referenced from the default configuration files (currently using dovecot in Debian oldstable). Feel free to include in the distribution or wherever. Probably a better solution would be to publish the config files with the paths already expanded to the online URL, or a local filesystem path that works (in the latter case, I'd wish the docs would be bundled in html format). I wonder whether to approach the debian maintainer about this or the Dovecot team? Definitely something for the maintainer is to put the bundled docs in a place where I would have expected it (/usr/share/docs/dovecot/wiki/ instead of /usr/share/docs/dovecot-core/dovecot/wiki/, or a dovecot-doc package, also, links or mentions from the doc dirs of all dovecot packages to the docs). Also, I think there should be a README document that serves as the first introduction of the user to how to configure the system: how are the config files split up, what does "!include" mean (why the "!"? Is it a comment char?), other rules on the config file format. I.e. the basics to enable the new user to go about reading the current config and where to find further docs/help. Thanks & Cheers, Christian.

1 1

Getting duplicated mails while using imapc and dsync
by Michael 17 Jul '15

17 Jul '15

Hello list, currently I'm migrating our old mailserver to a new mail architecture that is based on a master-master dovecot setup (two machines). The replication actually works but I'm also syncing our mails from the current mailserver via imapc on a regular schedule. For some reason I've in most (but not all) imapc-synced mailboxes duplicated emails that I also can't deduplicate with doveadm. I've also set up test-mailboxes that I don't sync with imapc and in those I don't have any duplicated mails. My command to sync the mails from the old host to the master-master system looks as follows: doveadm -o imapc_user=$i*dovemig -o imapc_password=<password> -o imapc_host=<oldhost> -o imapc_features="rfc822.size fetch-headers" -o mail_prefetch_count=20 -v -D sync -R -u$EMAIL imapc: &> $LOGS/$i.log So, is this actually the wrong approach to sync mails from the old host to the new one or is it just not recommended to sync them over-and-over again in such a setup via imapc or is it better to sync them only once? Any hint/pointing me to the right solution is greatly appreciated. Michael

1 0