- dovecot - dovecot.org

Iteration for ldap userdb does not work
by Holger A. Brinkhaus 20 Oct '17

20 Oct '17

Hi, I have a working ldap authentification for dovecot (with ldap based userdb query) for my Active Directory but iterations by doveadm -A runs in timeout. I tried now for three days and get it not to work. Best regards Holger /etc/dovecot/dovecot-ldap-userdb.conf is symlink to /etc/doveconf/doveconf-ldap.conf debug_level = 0 uris = ldaps://server1.office.hb-os.de:636 dn = cn=BINDUSER,cn=Users,dc=SUBDOM,dc=DOM,dc=de dnpass = MYPASSWORD auth_bind = yes ldap_version = 3 deref = never base = cn=Users,dc=SUBDOM,dc=DOM,dc=de scope = subtree user_attrs = =home=/usr/data/vmail/%d/%n, =mail=maildir:/usr/data/vmail/%d/%n/Maildir user_filter = (&(objectClass=person)(mail=%u)) pass_filter = (&(objectClass=person)(mail=%u)) iterate_attrs = mail=user iterate_filter = (objectClass=person) doveconf -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.9 auth_mechanisms = plain login base_dir = /var/run/dovecot/ default_vsz_limit = 512 M dict { expire = mysql:/etc/dovecot/dovecot-dict-expire.conf.ext } first_valid_uid = 100 imap_idle_notify_interval = 16 mins lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_gid = vmail mail_home = /usr/data/vmail/%d/ mail_location = maildir:~/Maildir:LAYOUT=fs mail_plugins = expire mail_privileged_group = vmail mail_uid = vmail 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 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 = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /usr/data/vmail/spampipe.sh antispam_pipe_program_notspam_arg = --ham antispam_pipe_program_spam_arg = --spam antispam_pipe_tmp_dir = /tmp antispam_spam = Junk;SPAM;Spam antispam_trash = Trash expire = Trash expire2 = Trash/* expire3 = Junk expire_dict = proxy::expire sieve = /usr/data/vmail/%u/sieve/active-script.sieve sieve_before = /usr/data/vmail/sieve/spam-global.sieve sieve_dir = /usr/data/vmail/%d/%n/sieve/scripts/ sieve_max_redirects = 4 sieve_max_script_size = 1M sieve_quota_max_scripts = 128 } postmaster_address = ME(a)DOMAIN.de protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = postfix mode = 0600 user = postfix } user = vmail } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 10 service_count = 1 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/ssl/certs/MY_CERT.crt ssl_key = </etc/ssl/private/MY_CERT.key userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } protocol lmtp { mail_plugins = expire sieve } protocol lda { mail_plugins = expire sieve } protocol imap { mail_max_userip_connections = 10 mail_plugins = expire antispam }

2 2

Dovecot >=2.2.29 + Filesystem quota = incorrect storage information
by Macka 18 Oct '17

18 Oct '17

Hi, I have problem with quota storage information in dovecot-2.2.29 (and newer versions, too - 2.2.30.2). I use FS quota backend. ............................ # 2.2.29.1 (e0b76e3): /etc/dovecot/dovecot.conf # OS: Linux 4.4.68-1 x86_64 mail_plugins = quota plugin { quota = fs:User quota:mount=/poczta:user quota2 = fs:Group quota:mount=/poczta:group } protocol imap { mail_max_userip_connections = 10 mail_plugins = "imap_quota mail_log notify antispam" } ................................. After upgrade from 2.2.27 to 2.2.29 (newest 2.2.30.2 too), dovecot returns incorrect informations about quota storage: # doveadm quota get -u myusername Quota name Type Value Limit % User quota STORAGE 10960896 100000 10960 or # ( echo "A1 GETQUOTAROOT INBOX"; echo "A2 logout" ) | /usr/lib64/dovecot/imap -u myusername * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE NOTIFY SPECIAL-USE QUOTA] Logged in as myusername imap(myusername): Info: Logged out in=31 out=588 * QUOTAROOT INBOX "User quota" * QUOTA "User quota" (STORAGE 10960896 100000) A1 OK Getquotaroot completed (0.001 + 0.000 secs). * BYE Logging out A2 OK Logout completed (0.001 + 0.000 secs). Values are in BYTES and Limit in BLOCKS which gives insane information in % Other server with older version 2.2.27 returns correct numbers (both in BLOCKS) # doveadm quota get -u username2 Quota name Type Value Limit % user STORAGE 558336 614400 90 Is this a bug in new versions? How can I fix this? -- macka

3 6

Re: Last Login example
by Siarhei Chystsiakou 18 Oct '17

18 Oct '17

My config: config plugins: # cat /etc/dovecot/conf.d/90-last_login.conf > dict { > lastlogin = mysql:/etc/dovecot/dict.conf.d/90-lastlogin.conf > } > plugin { > last_login_dict = proxy::lastlogin > } config db connector: # cat /etc/dovecot/dict.conf.d/90-lastlogin.conf > connect=host=localhost dbname=mail_user user=userDB password=Pa$$w0rd > map { > pattern = shared/last-login/$user > table = mailbox > username_field = username > value_field = lastlogin > value_type = uint > fields { > username = $user > } > } config imap and pop3 # cat /etc/dovecot/dict.conf.d/20-imap.conf > protocol imap { > mail_plugins = $mail_plugins quota imap_quota imap_acl last_login > } > # cat /etc/dovecot/dict.conf.d/20-pop3.conf > protocol imap { > mail_plugins = $mail_plugins last_login > } In the database in the table with users to add a column. If you have questions, I'll try to answer 2017-10-14 20:20 GMT+02:00 Jorge Bastos <mysql.jorge(a)decimal.pt>: > Howdy, > > > > Where can i find a configuration example for the last login plugin, that > fits for latest dovecot version? > > Thanks in advanced! > > > > Jorge, >

1 0

Re: Last Login example
by Aki Tuomi 18 Oct '17

18 Oct '17

On 14.10.2017 21:20, Jorge Bastos wrote: > Howdy, > > > > Where can i find a configuration example for the last login plugin, that > fits for latest dovecot version? > > Thanks in advanced! > > > > Jorge, https://wiki.dovecot.org/Plugins/LastLogin Is there some problem you are experiencing? Aki

1 0

Replication between different versions of dovecot
by Dmitry Nezhevenko 18 Oct '17

18 Oct '17

Hi, Can't find any notes about this in documentation. Is replication supposed to work between different versions of dovecot? I've just found that dovecot 2.2.33.1 was uploaded to debian unstable and it crashes on every replication with older dovecot 2.2.27. (version 2.2.32.1 was probably ok) Summary: - 2.2.33.1 crashes when replicating from/to 2.2.27 - 2.2.32.1 probably ok when replicating from/to 2.2.27 I was able to capture backtrace of crashed doveadm-server: Program terminated with signal SIGSEGV, Segmentation fault. #0 i_stream_next_line (stream=stream@entry=0x0) at istream.c:428 428 istream.c: No such file or directory. (gdb) bt #0 i_stream_next_line (stream=stream@entry=0x0) at istream.c:428 #1 0x00007f60244306df in i_stream_read_next_line (stream=0x0) at istream.c:449 #2 0x0000560304f22e79 in server_connection_print_log (conn=0x560305e930f8) at server-connection.c:305 #3 0x0000560304f238af in server_connection_input_one (conn=<optimized out>) at server-connection.c:405 #4 server_connection_input (conn=<optimized out>) at server-connection.c:390 #5 0x00007f602443a572 in io_loop_call_io (io=0x560305e81e30) at ioloop.c:600 #6 0x00007f602443bc1e in io_loop_handler_run_internal (ioloop=ioloop@entry=0x560305e59ad0) at ioloop-epoll.c:223 #7 0x00007f602443a606 in io_loop_handler_run (ioloop=ioloop@entry=0x560305e59ad0) at ioloop.c:649 #8 0x00007f602443a7b8 in io_loop_run (ioloop=0x560305e59ad0) at ioloop.c:624 #9 0x0000560304f0de5a in dsync_connect_tcp (ctx=ctx@entry=0x560305e7e9e8, mail_set=mail_set@entry=0x560305e8ad50, target=0x560305e8b94c "inhex.vpn.local:9993", ssl=ssl@entry=false, error_r=error_r@entry=0x7fff8e40b9e8) at doveadm-dsync.c:850 #10 0x0000560304f0fbe3 in parse_location (error_r=0x7fff8e40b9e8, remote_cmd_args_r=0x7fff8e40b858, location=<optimized out>, mail_set=0x560305e8ad50, ctx=0x560305e7e9e8) at doveadm-dsync.c:875 #11 cmd_dsync_prerun (_ctx=0x560305e7e9e8, service_user=<optimized out>, error_r=0x7fff8e40b9e8) at doveadm-dsync.c:947 #12 0x0000560304f10891 in doveadm_mail_next_user (ctx=ctx@entry=0x560305e7e9e8, cctx=cctx@entry=0x7fff8e40b9f0, error_r=error_r@entry=0x7fff8e40b9e8) at doveadm-mail.c:414 #13 0x0000560304f11473 in doveadm_mail_single_user (ctx=ctx@entry=0x560305e7e9e8, cctx=cctx@entry=0x7fff8e40b9f0, error_r=error_r@entry=0x7fff8e40b9e8) at doveadm-mail.c:460 #14 0x0000560304f262fb in doveadm_mail_cmd_server_run (cctx=0x7fff8e40b9f0, mctx=0x560305e7e9e8, conn=0x560305e7a878) at client-connection.c:246 #15 doveadm_cmd_handle (cctx=0x7fff8e40b9f0, argv=<optimized out>, argc=<optimized out>, cmd_name=<optimized out>, conn=0x560305e7a878) at client-connection.c:329 #16 client_handle_command (args=<optimized out>, conn=0x560305e7a878) at client-connection.c:399 #17 client_connection_input (conn=<optimized out>) at client-connection.c:541 #18 0x00007f602443a572 in io_loop_call_io (io=0x560305e58c40) at ioloop.c:600 #19 0x00007f602443bc1e in io_loop_handler_run_internal (ioloop=ioloop@entry=0x560305e529a0) at ioloop-epoll.c:223 #20 0x00007f602443a606 in io_loop_handler_run (ioloop=ioloop@entry=0x560305e529a0) at ioloop.c:649 #21 0x00007f602443a7b8 in io_loop_run (ioloop=0x560305e529a0) at ioloop.c:624 #22 0x00007f60243bf893 in master_service_run (service=0x560305e52840, callback=<optimized out>) at master-service.c:719 #23 0x0000560304f011d5 in main (argc=<optimized out>, argv=<optimized out>) at main.c:143 -- WBR, Dmitry

2 4

Re: Limit the nuumber of mails POPped at a time
by Joseph Tam 18 Oct '17

18 Oct '17

> I have a piece of software with a mailclient that has problems when it > POP's large amounts of mail. Unfortunately the system can't be updated > or fixed.So I'm trying to figure out if I can limit the number of mails > that can be seen via Dovecot. > ... > So it would be a question of always presenting a maximum of 300 mails > via the POP3.Is it doable? You're probably solving the wrong problem -- the mail client really ought to be able to process 300+ messages. It may be a better use of time to fix that than to torture dovecot to give you what you want. You can try using a plugin to define a virtual INBOX https://wiki.dovecot.org/Plugins/Virtual with search/selection criteria to limit the number of messages. You can also try some LDA script (e.g. procmail) hackery to create INBOX volumes of 300 messages, then do some shuffling around when the INBOX gets emptied. Joseph Tam <jtam.home(a)gmail.com>

1 0

mdbox + director + nfs
by Raymond Sellars 17 Oct '17

17 Oct '17

Hi Matt We've been running this configuration for the past couple of years. Not noticed any locking issues. As I understand it that's the objective of using Director. As Aki notes make sure you have the appropriate NFS settings. Other lessons we encountered. Important to ensure NFS is NTP sync'd and aligned with your hosts, we hit some issues with file timestamps leading to problems. Replication, e.g. for perhaps a backup or DR site. Seems to work but we've had the odd occasion of the indexes drifting. Never tracked the reason down and believe its unrelated to the NFS. Just something to monitor. Regards Raymond ------------------------------ Message: 5 Date: Tue, 17 Oct 2017 08:50:18 +0300 From: Aki Tuomi <aki.tuomi(a)dovecot.fi> To: dovecot(a)dovecot.org Subject: Re: mdbox + director + nfs Message-ID: <70b54e75-14fe-2caa-eccb-1ffc05c2a1e5(a)dovecot.fi> Content-Type: text/plain; charset=utf-8 NFS with mdbox should work just fine, locking should not be an issue, but please read https://wiki.dovecot.org/NFS Aki On 17.10.2017 02:32, Matt Bryant wrote: > Anyone had any experience they can share using a director setup with > NFS and using the mdbox format instead of maildir. Is locking an issue > on index files ?? > > rgds > > Matt

1 0

Dovecot 2.2.31 Incorrect Search
by Siarhei Chystsiakou 17 Oct '17

17 Oct '17

Hi. I have installed dovecot 2.2.31 and fts plugin with Apache Solr 6.6.1. I have found that imap search is not correct in my dovecot. For example, I want to find email from user s.chistiakov(a)example.com. I run IMAP command "SEARCH FROM s.chi" and result is null. But if I run IMAP command "SEARCH FROM s.chistiakov" I get list of emails from this user. Why does this happen and how to fix it? Help me please ) Thanks. Result of my actions in telnet: https://hastebin.com/fewanacafu.md Dovecot config: https://hastebin.com/noqehimaxu.makefile

2 2

Re: Disable PAM
by Aki Tuomi 17 Oct '17

17 Oct '17

Yep. Just remove any passdb/userdb pam blocks ---Aki TuomiDovecot oy -------- Original message --------From: Travis Dolan <travis.dolan(a)gmail.com> Date: 17/10/2017 17:40 (GMT+02:00) To: dovecot(a)dovecot.org Subject: Disable PAM Can I disable PAM auth if all my username/password lookups are via a database connection? I would love to get rid of the following lines in my logs... Oct 17 14:32:14 auth-worker(7809): Info: pam(xxx-xxx-xxx,111.111.111.111,<sdfhgsdfgsd>): pam_authenticate() failed: Authentication failure (password mismatch?) Cheers.

1 0

Disable PAM
by Travis Dolan 17 Oct '17

17 Oct '17

Can I disable PAM auth if all my username/password lookups are via a database connection? I would love to get rid of the following lines in my logs... Oct 17 14:32:14 auth-worker(7809): Info: pam(xxx-xxx-xxx,111.111.111.111,<sdfhgsdfgsd>): pam_authenticate() failed: Authentication failure (password mismatch?) Cheers.

1 0