- dovecot - dovecot.org

Ask for little change :)
by kjonca＠o2.pl 12 Oct '18

12 Oct '18

Is it possible, that dovecot-lmtp, has in inserted "Received:" header something about its version ie. instead: --8<---------------cut here---------------start------------->8--- Received: from alfa.kjonca by alfa.kjonca with LMTP id n1O7D5Q3v1toSQAApvcrCQ (envelope-from <envelope@from>) for <kjonca@localhost>; Thu, 11 Oct 2018 13:44:20 +0200 --8<---------------cut here---------------end--------------->8--- would be: --8<---------------cut here---------------start------------->8--- Received: from alfa.kjonca (Dovecot version) by alfa.kjonca with LMTP id n1O7D5Q3v1toSQAApvcrCQ (envelope-from <envelope@from>) for <kjonca@localhost>; Thu, 11 Oct 2018 13:44:20 +0200 --8<---------------cut here---------------end--------------->8--- KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html można nie mieć nawet żadnego sensownego argumentu, a dzięki odpowiedniej gestykulacji stworzyć poczucie wiarygodności. Puls Biznesu

2 1

Struggling to get dovecot working with postfix auth
by Laura Smith 11 Oct '18

11 Oct '18

Hi, I am trying to create an authenticated relay server using Postfix and Dovecot. However I am having two problems : (a) If I create a dovecot config entry as follows : unix_listener /var/spool/postfix-authrelay/private/dovecot-auth { group = postfix mode = 0666 user = postfix } Dovecot is unable to create the socket ? I thought surely if dovecot is started as root it should create the socket before dropping privileges ? (b) The alternative method of TCP SASL is not working either: 250 DSN ehlo localhost 250-foobar.example.com 250-PIPELINING 250-SIZE 20480000 250-ETRN 250-AUTH PLAIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN AUTH PLAIN <none_of_your_business> 535 5.7.8 Error: authentication failed: and in the logs... 2018-10-11T10:17:40.491483+01:00 X postfix-authrelay/smtpd[18312]: warning: X[X]: SASL PLAIN authentication failed: #### #### postconf #### >postconf -a cyrus dovecot > postconf -c /etc/postfix-authrelay | fgrep sasl broken_sasl_auth_clients = no cyrus_sasl_config_path = lmtp_sasl_auth_cache_name = lmtp_sasl_auth_cache_time = 90d lmtp_sasl_auth_enable = no lmtp_sasl_auth_soft_bounce = yes lmtp_sasl_mechanism_filter = lmtp_sasl_password_maps = lmtp_sasl_path = lmtp_sasl_security_options = noplaintext, noanonymous lmtp_sasl_tls_security_options = $lmtp_sasl_security_options lmtp_sasl_tls_verified_security_options = $lmtp_sasl_tls_security_options lmtp_sasl_type = cyrus proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $smtpd_sender_login_maps $sender_bcc_maps $recipient_bcc_maps $smtp_generic_maps $lmtp_generic_maps $alias_maps $smtpd_client_restrictions $smtpd_helo_restrictions $smtpd_sender_restrictions $smtpd_relay_restrictions $smtpd_recipient_restrictions $address_verify_sender_dependent_default_transport_maps $address_verify_sender_dependent_relayhost_maps $address_verify_transport_maps $fallback_transport_maps $lmtp_discard_lhlo_keyword_address_maps $lmtp_pix_workaround_maps $lmtp_sasl_password_maps $lmtp_tls_policy_maps $mailbox_command_maps $mailbox_transport_maps $postscreen_discard_ehlo_keyword_address_maps $rbl_reply_maps $sender_dependent_default_transport_maps $sender_dependent_relayhost_maps $smtp_discard_ehlo_keyword_address_maps $smtp_pix_workaround_maps $smtp_sasl_password_maps $smtp_tls_policy_maps $smtpd_discard_ehlo_keyword_address_maps $smtpd_milter_maps $virtual_gid_maps $virtual_uid_maps proxy_write_maps = $smtp_sasl_auth_cache_name $lmtp_sasl_auth_cache_name $address_verify_map $postscreen_cache_map send_cyrus_sasl_authzid = no smtp_sasl_auth_cache_name = smtp_sasl_auth_cache_time = 90d smtp_sasl_auth_enable = no smtp_sasl_auth_soft_bounce = yes smtp_sasl_mechanism_filter = smtp_sasl_password_maps = smtp_sasl_path = smtp_sasl_security_options = noplaintext, noanonymous smtp_sasl_tls_security_options = $smtp_sasl_security_options smtp_sasl_tls_verified_security_options = $smtp_sasl_tls_security_options smtp_sasl_type = cyrus smtpd_recipient_restrictions = permit_mynetworks,permit_sasl_authenticated,reject_unauth_destination smtpd_relay_restrictions = permit_mynetworks,permit_sasl_authenticated,reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = no smtpd_sasl_exceptions_networks = smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = inet:localhost:7425 smtpd_sasl_security_options = noanonymous smtpd_sasl_service = smtp smtpd_sasl_tls_security_options = $smtpd_sasl_security_options smtpd_sasl_type = dovecot #### #### DOVECONF #### > doveconf -n # 2.3.1 (8e2f634): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.1 (d9bc6dfe) # OS: Linux 4.12.14-lp150.12.19-default x86_64 # Hostname: test.example.com 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 mime foreverypart extracttext 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 { driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } service auth { inet_listener { address = 127.0.0.1 port = 7425 } inet_listener { address = ::1 port = 7425 } # If I disable this, dovecot loads fine, but the tcp auth is unusable ? # If I enable this, dovecot is unable to create the socket ? # unix_listener /var/spool/postfix-authrelay/private/dovecot-auth { # group = postfix # mode = 0666 # user = postfix # } } ssl = no ssl_cipher_list = ALL:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH ssl_options = no_compression ssl_prefer_server_ciphers = yes userdb { driver = passwd }

5 11

Renewal of Let's Encrypt Certificates in Dovecot
by Ignacio Garcia 11 Oct '18

11 Oct '18

Hi there. I've been using Dovecot for quite some time now but I just started using Let's Encrypt certs. Since LE certs are renewed automatically without user intervention I'm wondering if I will need to restart dovecot after that renewal... Has anybody had any experience with that? Thanks so much for your help! Ignacio

5 5

index corruption weirdness
by William Taylor 10 Oct '18

10 Oct '18

We have started seeing index corruption ever since we upgraded (we believe) our imap servers from SL6 to Centos 7. Mail/Indexes are stored on Netapps mounted via NFS. We have 2 lvs servers running surealived in dr/wlc, 2 directors and 6 backend imap/pop servers. Most of the core dumps I've looked at for different users are like "Backtrace 2" with some variations on folder path. This latest crash (Backtrace 1) is different from others I've seen. It is also leaving 0byte files in the users .Drafts/tmp folder. # ls -s /var/spool/mail/15/00/user1/.Drafts/tmp | awk '{print $1}' |sort | uniq -c 9692 0 1 218600 I believe the number of cores here is different from the number of tmp files because this is when we moved the user to our debug server so we could get the core dumps. # ls -la /home/u/user1/core.* |wc -l 8437 Any help/insight would be greatly appreciated. Thanks, William OS Info: CentOS Linux release 7.5.1804 (Core) 3.10.0-862.14.4.el7.x86_64 NFS: # mount -t nfs |grep mail/15 172.16.255.14:/vol/vol1/mail/15 on /var/spool/mail/15 type nfs (rw,nosuid,nodev,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.16.255.14,mountvers=3,mountport=4046,mountproto=udp,local_lock=none,addr=172.16.255.14) Dovecot Info: dovecot -n # 2.1.17: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-862.14.4.el7.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) auth_failure_delay = 0 auth_master_user_separator = * auth_username_format = %Ln auth_verbose = yes auth_verbose_passwords = sha1 auth_worker_max_count = 64 login_log_format_elements = user=<%u> session=%{session} method=%m rip=%r lip=%l mpid=%e %c login_trusted_networks = 172.16.0/24 mail_debug = yes mail_fsync = always mail_log_prefix = "%s(%u): session=%{session} " mail_plugins = zlib maildir_very_dirty_syncs = yes mmap_disable = yes passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = imap driver = pam } plugin { lazy_expunge = DELETED_MESSAGES. mail_log_events = delete expunge flag_change mail_log_fields = uid box msgid from flags size quota = fs:User quota stats_refresh = 30 secs stats_track_cmds = yes } protocols = imap pop3 service anvil { client_limit = 10000 } service auth { client_limit = 10000 vsz_limit = 1 G } service doveadm { inet_listener { port = 1842 } unix_listener doveadm-server { mode = 0666 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 7000 process_min_avail = 32 vsz_limit = 256 M } service imap-postlogin { executable = script-login -d /etc/dovecot/bin/foo-imap-postlogin user = $default_internal_user } service imap { executable = imap imap-postlogin process_limit = 7000 vsz_limit = 1492 M } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } process_limit = 2000 process_min_avail = 32 vsz_limit = 256 M } service pop3-postlogin { executable = script-login -d /etc/dovecot/bin/foo-pop3-postlogin user = $default_internal_user } service pop3 { executable = pop3 pop3-postlogin process_limit = 2000 } shutdown_clients = no ssl = required ssl_ca = </etc/dovecot/ssl/imap.foo.com.ca-bundle ssl_cert = </etc/dovecot/ssl/imap.foo.com.crt ssl_key = </etc/dovecot/ssl/imap.foo.com.key ssl_parameters_regenerate = 1 days ssl_protocols = !SSLv2 !SSLv3 syslog_facility = local0 userdb { driver = passwd } verbose_proctitle = yes protocol imap { imap_id_send = support-url support-email imap_max_line_length = 128 k mail_max_userip_connections = 20 mail_plugins = zlib mail_log notify imap_zlib ssl_ca = </etc/dovecot/ssl/imap.foo.com.ca-bundle ssl_cert = </etc/dovecot/ssl/imap.foo.com.crt ssl_key = </etc/dovecot/ssl/imap.foo.com.key } protocol pop3 { mail_plugins = zlib lazy_expunge pop3_fast_size_lookups = yes pop3_uidl_format = %f ssl_ca = </etc/dovecot/ssl/pop.foo.com.ca-bundle ssl_cert = </etc/dovecot/ssl/pop.foo.com.crt ssl_key = </etc/dovecot/ssl/pop.foo.com.key } Backtrace 1: Reading symbols from /usr/libexec/dovecot/imap...Reading symbols from /usr/lib/debug/usr/libexec/dovecot/imap.debug...done. Program terminated with signal 6, Aborted. #0 0x00007fbee47e0277 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); Thread 1 (Thread 0x7fbee532f840 (LWP 9449)): #0 0x00007fbee47e0277 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 resultvar = 0 pid = 9449 selftid = 9449 #1 0x00007fbee47e1968 in __GI_abort () at abort.c:90 save_stage = 2 act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0}, sa_mask = {__val = {0 <repeats 11 times>, 31683224, 140725444114256, 31908720, 140457858143945, 31683224}}, sa_flags = -457466710, sa_restorer = 0x0} sigs = {__val = {32, 0 <repeats 15 times>}} #2 0x00007fbee4bbdb65 in default_fatal_finish (type=<optimized out>, status=status@entry=0) at failures.c:191 backtrace = 0x1e372d0 "/usr/lib64/dovecot/libdovecot.so.0(+0x46b55) [0x7fbee4bbdb55] -> /usr/lib64/dovecot/libdovecot.so.0(+0x46c1e) [0x7fbee4bbdc1e] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fbee4b90dda] -> /usr"... #3 0x00007fbee4bbdc1e in i_internal_fatal_handler (ctx=0x7ffd321b77a0, format=<optimized out>, args=<optimized out>) at failures.c:649 status = 0 #4 0x00007fbee4b90dda in i_panic (format=format@entry=0x7fbee4ee0588 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:263 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0} args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7ffd321b7890, reg_save_area = 0x7ffd321b77d0}} #5 0x00007fbee4ea96ad in index_mail_parse_body_finish (mail=0x1e69570, field=field@entry=MAIL_CACHE_FLAGS) at index-mail.c:769 parser_input = 0x1e6e370 ret = 1 __FUNCTION__ = "index_mail_parse_body_finish" #6 0x00007fbee4eaaa2b in index_mail_cache_parse_deinit (_mail=<optimized out>, received_date=<optimized out>, success=<optimized out>) at index-mail.c:1624 mail = <optimized out> #7 0x00007fbee4e5dce3 in maildir_save_finish_real (_ctx=0x1e68560) at maildir-save.c:551 ctx = 0x1e68560 e = 0x1e574d0 output_errno = <optimized out> path = 0x1e37218 "/var/spool/mail/15/00/user1/.Drafts/tmp/1539107164.M157986P9449.debug.imapd.foo.com" real_size = <optimized out> size = 1539107194 #8 maildir_save_finish (ctx=0x1e68560) at maildir-save.c:630 _data_stack_cur_id = 3 #9 0x00007fbee4e90ce6 in mailbox_save_cancel (_ctx=_ctx@entry=0x1e58d58) at mail-storage.c:1697 ctx = 0x1e68560 keywords = 0x1e65860 mail = <optimized out> #10 0x0000000000409459 in cmd_append_continue_message (cmd=0x1e58c10) at cmd-append.c:420 client = 0x1e58070 ctx = 0x1e58d10 size = 31819840 ret = 3920 #11 0x000000000041186c in command_exec (cmd=0x1e58c10) at imap-commands.c:148 hook = 0x1e40d00 ret = <optimized out> #12 0x0000000000408d21 in client_input_append (cmd=0x1e58c10) at cmd-append.c:101 ctx = 0x1e58d10 client = 0x1e58070 finished = <optimized out> __FUNCTION__ = "client_input_append" #13 0x00007fbee4bcaaa7 in io_loop_call_io (io=0x1e58b10) at ioloop.c:379 ioloop = 0x1e3f6a0 t_id = 2 #14 0x00007fbee4bcb857 in io_loop_handler_run (ioloop=ioloop@entry=0x1e3f6a0) at ioloop-epoll.c:213 ctx = 0x1e3fa10 events = <optimized out> list = 0x1e58b60 io = <optimized out> tv = {tv_sec = 1799, tv_usec = 999445} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 call = <optimized out> #15 0x00007fbee4bca628 in io_loop_run (ioloop=0x1e3f6a0) at ioloop.c:398 No locals. #16 0x00007fbee4bb6213 in master_service_run (service=0x1e3f550, callback=callback@entry=0x418fb0 <client_connected>) at master-service.c:544 No locals. #17 0x0000000000408933 in main (argc=2, argv=0x1e3f390) at main.c:389 set_roots = {0x41c320 <imap_setting_parser_info>, 0x0} login_set = {auth_socket_path = 0x1e37090 "/run/dovecot/auth-master", postlogin_socket_path = 0x1e370c0 "/run/dovecot/imap-postlogin", postlogin_timeout_secs = 60, callback = 0x419440 <login_client_connected>, failure_callback = 0x419150 <login_client_failed>} service_flags = <optimized out> storage_service_flags = <optimized out> username = 0x0 c = <optimized out> Backtrace 2: Reading symbols from /usr/libexec/dovecot/imap...Reading symbols from /usr/lib/debug/usr/libexec/dovecot/imap.debug...done. Program terminated with signal 6, Aborted. #0 0x00007f437288c277 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); Thread 1 (Thread 0x7f43733d3840 (LWP 6725)): #0 0x00007f437288c277 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 resultvar = 0 pid = 6725 selftid = 6725 #1 0x00007f437288d968 in __GI_abort () at abort.c:90 save_stage = 2 act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0}, sa_mask = {__val = {0 <repeats 11 times>, 19630744, 140729812750864, 1, 139927665268057, 19630744}}, sa_flags = 1925602218, sa_restorer = 0x0} sigs = {__val = {32, 0 <repeats 15 times>}} #2 0x00007f4372c69a25 in default_fatal_finish (type=<optimized out>, status=status@entry=0) at failures.c:191 backtrace = 0x12b8ad0 "/usr/lib64/dovecot/libdovecot.so.0(+0x46a15) [0x7f4372c69a15] -> /usr/lib64/dovecot/libdovecot.so.0(+0x46ade) [0x7f4372c69ade] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4372c3cdaa] -> /usr"... #3 0x00007f4372c69ade in i_internal_fatal_handler (ctx=0x7ffe367f9260, format=<optimized out>, args=<optimized out>) at failures.c:649 status = 0 #4 0x00007f4372c3cdaa in i_panic (format=format@entry=0x7f4372f83cc8 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:263 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0} args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7ffe367f9350, reg_save_area = 0x7ffe367f9290}} #5 0x00007f4372f77eb8 in keywords_update_records (ext=0x13827e8, ext=0x13827e8, uid2=<optimized out>, uid1=<optimized out>, type=MODIFY_ADD, keyword_idx=0, ctx=0x7ffe367f94e0) at mail-index-sync-keywords.c:228 data = <optimized out> data_mask = 1 '\001' seq1 = 346 view = 0x134c110 rec = <optimized out> data_offset = <optimized out> seq2 = 346 #6 mail_index_sync_keywords (ctx=ctx@entry=0x7ffe367f94e0, hdr=hdr@entry=0x1345bb8, rec=rec@entry=0x13a54e4) at mail-index-sync-keywords.c:304 view = <optimized out> keyword_name = <optimized out> ext = 0x13827e8 uid = <optimized out> end = 0x13a54fc seqset_offset = <optimized out> ext_map_idx = 2 keyword_idx = 0 __FUNCTION__ = "mail_index_sync_keywords" #7 0x00007f4372f78822 in mail_index_sync_record_real (data=0x13a54e4, hdr=0x1345bb8, ctx=0x7ffe367f94e0) at mail-index-sync-update.c:779 rec = 0x13a54e4 ret = 0 #8 mail_index_sync_record (ctx=ctx@entry=0x7ffe367f94e0, hdr=0x1345bb8, data=0x13a54e4) at mail-index-sync-update.c:824 _data_stack_cur_id = 7 ret = 0 #9 0x00007f4372f79866 in mail_index_sync_map (_map=_map@entry=0x1346498, type=type@entry=MAIL_INDEX_SYNC_HANDLER_HEAD, force=force@entry=true) at mail-index-sync-update.c:1036 map = <optimized out> index = 0x1346410 view = 0x134c110 sync_map_ctx = {view = 0x134c110, modseq_ctx = 0x138d330, cur_ext_map_idx = 0, ext_intro_seq = 105, ext_intro_offset = 13792, ext_intro_end_offset = 13820, expunge_handlers = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}, extra_contexts = { arr = {buffer = 0x134d8c0, element_size = 8}, v = 0x134d8c0, v_modifiable = 0x134d8c0}, unknown_extensions = 0x0, type = MAIL_INDEX_SYNC_HANDLER_HEAD, sync_handlers_initialized = 0, expunge_handlers_set = 0, expunge_handlers_used = 0, cur_ext_ignore = 0, internal_update = 0, errors = 0} thdr = 0x1345bb8 tdata = 0x13a54e4 prev_seq = 105 start_offset = <optimized out> prev_offset = 14084 ret = <optimized out> had_dirty = <optimized out> reset = false __FUNCTION__ = "mail_index_sync_map" #10 0x00007f4372f6a6e4 in mail_index_map (index=index@entry=0x1346410, type=type@entry=MAIL_INDEX_SYNC_HANDLER_HEAD) at mail-index-map-read.c:433 ret = <optimized out> __FUNCTION__ = "mail_index_map" #11 0x00007f4372f65a90 in mail_index_try_open (index=index@entry=0x1346410) at mail-index.c:426 ret = <optimized out> __FUNCTION__ = "mail_index_try_open" #12 0x00007f4372f66130 in mail_index_open_files (index=index@entry=0x1346410, flags=flags@entry=(MAIL_INDEX_OPEN_FLAG_CREATE | MAIL_INDEX_OPEN_FLAG_MMAP_DISABLE | MAIL_INDEX_OPEN_FLAG_DOTLOCK_USE_EXCL)) at mail-index.c:504 ret = <optimized out> created = false #13 0x00007f4372f66230 in mail_index_open (index=0x1346410, flags=flags@entry=(MAIL_INDEX_OPEN_FLAG_CREATE | MAIL_INDEX_OPEN_FLAG_MMAP_DISABLE | MAIL_INDEX_OPEN_FLAG_DOTLOCK_USE_EXCL)) at mail-index.c:594 ret = <optimized out> __FUNCTION__ = "mail_index_open" #14 0x00007f4372f57a17 in index_storage_mailbox_open (box=box@entry=0x1388750, move_to_memory=move_to_memory@entry=false) at index-storage.c:231 ibox = 0x1388b48 index_flags = (MAIL_INDEX_OPEN_FLAG_CREATE | MAIL_INDEX_OPEN_FLAG_MMAP_DISABLE | MAIL_INDEX_OPEN_FLAG_DOTLOCK_USE_EXCL) ret = <optimized out> __FUNCTION__ = "index_storage_mailbox_open" #15 0x00007f4372f03212 in maildir_mailbox_open_existing (box=box@entry=0x1388750) at maildir-storage.c:305 mbox = 0x1388750 #16 0x00007f4372f03960 in maildir_mailbox_open (box=0x1388750) at maildir-storage.c:365 box_path = 0x1388f68 "/var/spool/mail/16/47/user2/DELETED_MESSAGES/.INBOX" root_dir = <optimized out> st = {st_dev = 140729812752383, st_ino = 140729812752416, st_nlink = 19629048, st_mode = 914331680, st_uid = 32766, st_gid = 4300439, __pad0 = 0, st_rdev = 140729812752896, st_size = 1, st_blksize = 133, st_blocks = 19629048, st_atim = {tv_sec = 139927662018357, tv_nsec = 4222451713}, st_mtim = {tv_sec = 139927664838496, tv_nsec = 139927664838496}, st_ctim = {tv_sec = 344592, tv_nsec = -140729812752575}, __unused = {129, 32, 4}} ret = <optimized out> #17 0x00007f436fd13942 in zlib_mailbox_open (box=0x1388750) at zlib-plugin.c:346 zbox = 0x1388e30 #18 0x00007f4372f34cc7 in mailbox_open_full (box=0x1388750, input=0x0) at mail-storage.c:907 _data_stack_cur_id = 6 ret = <optimized out> input = 0x0 box = 0x1388750 #19 0x00007f4372f35070 in mailbox_open (box=box@entry=0x1388750) at mail-storage.c:942 No locals. #20 0x00007f4372f56b2b in index_storage_get_status (box=0x1388750, items=STATUS_UNSEEN, status_r=0x7ffe367f9b40) at index-status.c:41 hdr = <optimized out> __FUNCTION__ = "index_storage_get_status" #21 0x00000000004175f5 in imap_status_get (cmd=0x12d99b0, ns=0x12d8590, mailbox=mailbox@entry=0x13883e0 "DELETED_MESSAGES.INBOX", items=items@entry=0x12d9aec, result_r=result_r@entry=0x7ffe367f9b40, error_r=error_r@entry=0x7ffe367f9b38) at imap-status.c:84 client = 0x12d8e60 box = 0x1388750 error = MAIL_ERROR_NONE ret = 0 #22 0x000000000040bee7 in list_send_status (flags=<optimized out>, mutf7_name=0x12b8548 "DELETED_MESSAGES.INBOX", name=0x13883e0 "DELETED_MESSAGES.INBOX", ctx=0x12d9ad0) at cmd-list.c:466 result = {status = {messages = 0, recent = 0, unseen = 0, uidvalidity = 0, uidnext = 0, first_unseen_seq = 0, first_recent_uid = 0, last_cached_seq = 0, highest_modseq = 0, keywords = 0x0, permanent_flags = 0, nonpermanent_modseqs = 0, permanent_keywords = 0, allow_new_keywords = 0}, metadata = {guid = '\000' <repeats 15 times>, virtual_size = 0, cache_fields = 0x0, precache_fields = (MAIL_FETCH_DATE | MAIL_FETCH_RECEIVED_DATE | MAIL_FETCH_SAVE_DATE | MAIL_FETCH_VIRTUAL_SIZE | MAIL_FETCH_NUL_STATE | MAIL_FETCH_IMAP_BODY | MAIL_FETCH_FROM_ENVELOPE | MAIL_FETCH_HEADER_MD5 | MAIL_FETCH_UIDL_BACKEND | MAIL_FETCH_MAILBOX_NAME | MAIL_FETCH_GUID | unknown: 16779264)}} ns = <optimized out> error = 0x12b8360 "*" #23 list_namespace_mailboxes (ctx=0x12d9ad0) at cmd-list.c:566 _data_stack_cur_id = 5 info = <optimized out> flags = <optimized out> str = 0x12b83c0 ret = 1 ns = 0x0 mutf7_name = 0x12b8510 name = 0x13883e0 "DELETED_MESSAGES.INBOX" #24 cmd_list_continue (cmd=cmd@entry=0x12d99b0) at cmd-list.c:912 _data_stack_cur_id = 4 ctx = 0x12d9ad0 #25 0x000000000040cb27 in cmd_list_full (cmd=0x12d99b0, lsub=<optimized out>) at cmd-list.c:1092 client = 0x12d8e60 args = 0x12c3968 list_args = 0x12c3a40 arg_count = 0 ctx = 0x12d9ad0 patterns = {arr = {buffer = <optimized out>, element_size = 8}, v = <optimized out>, v_modifiable = <optimized out>} pattern = 0x12b8360 "*" patterns_strarr = <optimized out> str = <optimized out> #26 0x00000000004117fc in command_exec (cmd=cmd@entry=0x12d99b0) at imap-commands.c:148 hook = 0x12c1d00 ret = <optimized out> #27 0x000000000041079b in client_command_input (cmd=cmd@entry=0x12d99b0) at imap-client.c:682 client = 0x12d8e60 command = <optimized out> __FUNCTION__ = "client_command_input" #28 0x0000000000410885 in client_command_input (cmd=0x12d99b0) at imap-client.c:733 client = 0x12d8e60 command = <optimized out> __FUNCTION__ = "client_command_input" #29 0x0000000000410aed in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x12d8e60) at imap-client.c:774 size = 52 #30 client_handle_input (client=client@entry=0x12d8e60) at imap-client.c:786 _data_stack_cur_id = 3 remove_io = false handled_commands = false __FUNCTION__ = "client_handle_input" #31 0x0000000000411302 in client_input (client=0x12d8e60) at imap-client.c:825 cmd = 0x7f4372c69eae <i_set_failure_prefix+46> output = 0x12dde18 bytes = 52 __FUNCTION__ = "client_input" #32 0x00007f4372c76937 in io_loop_call_io (io=0x12d1150) at ioloop.c:379 ioloop = 0x12c06a0 t_id = 2 #33 0x00007f4372c776e7 in io_loop_handler_run (ioloop=ioloop@entry=0x12c06a0) at ioloop-epoll.c:213 ctx = 0x12c0a10 events = <optimized out> list = 0x12d9900 io = <optimized out> tv = {tv_sec = 1799, tv_usec = 999765} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 call = <optimized out> #34 0x00007f4372c764b8 in io_loop_run (ioloop=0x12c06a0) at ioloop.c:398 No locals. #35 0x00007f4372c62113 in master_service_run (service=0x12c0550, callback=callback@entry=0x418f40 <client_connected>) at master-service.c:544 No locals. #36 0x00000000004088e3 in main (argc=2, argv=0x12c0390) at main.c:389 set_roots = {0x41c2a0 <imap_setting_parser_info>, 0x0} login_set = {auth_socket_path = 0x12b8090 "/run/dovecot/auth-master", postlogin_socket_path = 0x12b80c0 "/run/dovecot/imap-postlogin", postlogin_timeout_secs = 60, callback = 0x4193d0 <login_client_connected>, failure_callback = 0x4190e0 <login_client_failed>} service_flags = <optimized out> storage_service_flags = <optimized out> username = 0x0 c = <optimized out>

5 6

Problem getting quota-warning script to function.
by Ted 10 Oct '18

10 Oct '18

Hello, I'm trying to implement quota enforcement in our mailservers, and it is all working properly except that the quota warnings are not firing when the quota levels are passed. the server stops accepting email when the quota is reached, and you can see tyhe quota usage through the email client connected through, but as the quota passes the set levels the /usr/local/bin/quota-warning.sh script is not called. I checked from the appropriate user and the script executes from the command line with no problem, but dovecot does not invoke it when the quota levels are crossed. The relevant configs are below, any ideas about what the problem may be or how I should approach this? /etc/dovecot/dovecot.conf ## Dovecot configuration file # Protocols we want to be serving. protocols = imap pop3 lmtp sieve mailbox_list_index = yes # Avoid spending excessive time waiting for the quota calculation to finish when # mails' vsizes aren't already cached. If this many mails are opened, finish the # quota calculation on background in indexer-worker process. Mail deliveries will # be assumed to succeed, and explicit quota lookups will return internal error. # (v2.2.28+) # mail_vsize_bg_after_count = 100 plugin { quota_grace = 10%% # 10% is the default # quota_status_success = DUNNO # quota_status_nouser = DUNNO quota_status_overquota = "552 5.2.2 Mailbox is full" quota_vsizes = yes } service quota-status { executable = quota-status -p postfix inet_listener { port = 10070 # You can choose any port you want } client_limit = 1 } mail_plugins = $mail_plugins quota mail_log notify protocol imap { # Space separated list of plugins to load (default is global mail_plugins). mail_plugins = $mail_plugins imap_quota } # Greeting message for clients. login_greeting = Welcome to easyMail. # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). verbose_proctitle = yes # Should all processes be killed when Dovecot master process shuts down. # Setting this to "no" means that Dovecot can be upgraded without # forcing existing client connections to close (although that could also be # a problem if the upgrade is e.g. because of a security fix). shutdown_clients = yes # A config file can also tried to be included without giving an error if # it's not found: !include_try local.conf service auth { unix_listener auth-master { mode = 0600 user = vmail } } /etc/dovecot/dovecot-sql.conf.ext # Database driver: mysql, pgsql, sqlite driver = mysql connect = host=redacted dbname=redacted user=redacted password=reallyredacted # Default password scheme. # # List of supported schemes is in # http://wiki2.dovecot.org/Authentication/PasswordSchemes # default_pass_scheme = CRYPT password_query = select email as user, crypt_password as password, CONCAT('/',volume,'/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1)) AS home, 5000 AS uid, 5000 AS gid, concat('*:storage=', volume_limit ,'G') AS quota_rule from easymail_users where email = '%u' and banned = '0' and active = '1' user_query = SELECT CONCAT('maildir:/',volume,'/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/Maildir') AS mail, CONCAT('/',volume,'/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1)) AS home, 5000 AS uid, 5000 AS gid, concat('*:storage=', volume_limit ,'G') AS quota_rule from easymail_users where email = '%u' and banned = '0' and active = '1' /etc/dovecot/conf.d/90-quota.conf ## ## Quota configuration. ## ## ## Quota warnings ## # You can execute a given command when user exceeds a specified quota limit. # Each quota root has separate limits. Only the command for the first # exceeded limit is excecuted, so put the highest limit first. # The commands are executed via script service by connecting to the named # UNIX socket (quota-warning below). # Note that % needs to be escaped as %%, otherwise "% " expands to empty. plugin { quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=90%% quota-warning 90 %u quota_warning3 = storage=80%% quota-warning 80 %u } # Example quota-warning service. The unix listener's permissions should be # set in a way that mail processes can connect to it. Below example assumes # that mail processes run as vmail user. If you use mode=0666, all system users # can generate quota warnings to anyone. service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = dovecot unix_listener quota-warning { user = dovecot mode = 0666 } } ## ## Quota backends ## # Multiple backends are supported: # dirsize: Find and sum all the files found from mail directory. # Extremely SLOW with Maildir. It'll eat your CPU and disk I/O. # dict: Keep quota stored in dictionary (eg. SQL) # maildir: Maildir++ quota # fs: Read-only support for filesystem quota plugin { #quota = dirsize:User quota #quota = maildir:User quota #quota = dict:User quota::proxy::quota quota = count:User quota #quota = fs:User quota } /usr/local/bin/quota-warning.sh #!/bin/sh # warning email for approaching their quota usage=$1 email=$2 /usr/bin/mailx -r "support(a)easydns.com" -s "Quota Usager Notification" "${email:?}" < /home/vmail/quota"${usage:?}".txt echo "$(date) ${usage} : ${email}" >> /var/log/quotatest.log Thank you Ted easyDNS Technologies

3 9

immediate delete of mails
by tselmeci＠486.hu 10 Oct '18

10 Oct '18

Hello all! I've got a home server running on an ARM Cortex-A7 with my custom Linux distribution. It's also responsible for handling incoming and outgoing mails. The SMTP server is OpenSMTPD-6.0.3p1. I'm using Dovecot-2.3.2.1 to export the mails (mailbox storage format) using IMAP. My old server used to have Dovecot-1.2.0 and honestly, it was absolutely sufficient for me. However, I've decided to use the latest Dovecot on my new system, since all other software components of my system are up-to-date. With my simple IMAP-configuration Dovecot is running fine, expect for one thing: when I press DEL in the mailer client, the mails don't get deleted. They simple reside in the mailbox file. It annoys me a lot, since the mailer client regularly makes them appear with a different (grey) color. The mailer client is Sylpheed and I'm not willing to use another one. I've already tried Thunderbird, Evolution, Claws-mail, Sylpheed, and Sylpheed suits best to my needs. The funny thing is that with the same Sylpheed the old Dovecot was willing to physically remove the mails from mailbox file, but the new Dovecot isn't willing to do so. I've tried to search for an appropriate configuration option, but didn't find what I exactly need. Auto expunge, command-line expunging are nice, but I do want immediate mail delete from mailbox file when I press DEL in the mailer client. I know this can be dangerous and degrades performance. Is there any option to configure Dovecot to behave like this? If it needs to recompile Dovecot I'm also in ;) Thanks a lot! ----------------------------------------------- dovecot -n output: # 2.3.2.1 (0719df592): /etc/dovecot.conf # OS: Linux 4.18.9 armv7l # Hostname: 486 auth_mechanisms = plain login base_dir = /var/run/dovecot/ default_client_limit = 30 default_process_limit = 10 disable_plaintext_auth = no listen = * log_path = /var/log/dovecot.txt mail_gid = 0 mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u mail_uid = 0 namespace { hidden = no inbox = yes list = yes location = mailbox { auto = create special_use = \Drafts name = Drafts } mailbox { auto = create special_use = \Sent name = Sent } mailbox { auto = create special_use = \Trash name = Trash } prefix = type = private name = inbox } passdb { driver = passwd } passdb { driver = shadow } protocols = imap service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service old-stats-mail { name = old-stats } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service stats-reader { name = stats } service submission { name = submission-login } service login/submission { name = submission } ssl = no submission_max_mail_size = 0 userdb { driver = passwd } verbose_proctitle = yes -- Selmeci, Tamás http://www.486.hu/

9 16

Submission / Postfix / XCLIENT
by Anton Dollmaier 09 Oct '18

09 Oct '18

Hi all, while testing the new Dovecot Submission Proxy feature, which we greatly appreciate and have been anticipating for a long time, some issues occured. Dovecot is unable to submit mails via XCLIENT: < XCLIENT ADDR=185.115.176.12PORT=39074 > 501 5.5.4 Bad ADDR syntax: 185.115.176.12PORT=39074 Postfix is unable to parse the XCLIENT command from Dovecot submission proxy, as a space seems to be missing. After checking the source code, the issue looks easy to fix - at least to me as a non-Developer. I created my first pull request for that: > https://github.com/dovecot/core/pull/90 Would be great to see this merged. Any additional comments are also appreciated. Best, Anton

2 1

iterate query and dsync replication 2.2.33.2
by Matt Bryant 08 Oct '18

08 Oct '18

All, According to doco replication gets its list of users to replicate from the iterate query but this doesn't seem to be the case or its just being totally ignored .. Have ldap passbd and sql userdb, with the iterate query in the userdb sql file. -The query itself returns the handful of users I want to replicate BUT if I run the command dovecot replicator status '*' it shows pretty much all users in the system .. is there a bug here or is documentation just completely wrong when it comes to what is/is not replicated. rgds Matt

1 0

VOLATILEDIR not really used?
by Tom Sommer 08 Oct '18

08 Oct '18

Hi According to the docs, setting VOLATILEDIR will improve I/O performance when using NFS - but as far as I can see, only vsize lock-files are put here, and little else? Is this correct, and if so are there any plans to move dotlocks etc. to this directory? Thanks. -- Tom

2 7

Dovecot -v 2.2.27 (c0f36b0): Outgoing mail server fails
by Tommy Lane 07 Oct '18

07 Oct '18

Hello Everyone, I'm having an issue with a recent install of postfix and Dovecot. I can authenticate without any issues for "incoming" mail server, but when I attempt to send an email from the account my client gives an auth error. the server shows that I was authed using plain-auth, which I would also like to change as these machines are accross the open internet. Any help would be greatly appreciated. -Tommy

3 3

TLS handshake failure - Client Helo rejected
by VB 07 Oct '18

07 Oct '18

Hi, I can no longer connect to Dovecot (IMAP). The connection is terminated by Dovecot after Client Helo. My server: Dovecot 2.3.3 Debian buster/sid Architecture: ppc My problems started in late August after upgrading Dovecot. SSL settings: ssl_dh = </etc/ssl/dh2048.pem ssl_min_protocol = TLSv1.2 ssl_cipher_list = ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256 ssl_prefer_server_ciphers = yes Client: OS Android 6.0.1 Aquamail Log from Dovecot: Sep 15 23:19:02 debian2 dovecot: imap-login: Debug: SSL: where=0x10, ret=1: before SSL initialization Sep 15 23:19:02 debian2 dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization Sep 15 23:19:02 debian2 dovecot: imap-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization Sep 15 23:19:02 debian2 dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization Sep 15 23:19:02 debian2 dovecot: imap-login: Debug: SSL alert: where=0x4008, ret=598: fatal unknown Sep 15 23:19:02 debian2 dovecot: imap-login: Debug: SSL: where=0x2002, ret=-1: error Sep 15 23:19:02 debian2 dovecot: imap-login: Debug: SSL error: SSL_accept() failed: error:14209175:SSL routines:tls_early_post_process_client_hello:inappropriate fallback Sep 15 23:19:02 debian2 dovecot: imap-login: Debug: SSL error: SSL_accept() syscall failed: Invalid argument Sep 15 23:19:02 debian2 dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=XXX.XXX.XXX.XXX, lip=XXX.XXX.XXX.XXX,TLS handshaking: SSL_accept() syscall failed: Invalid argument, session=<XXXXXXXXXXX> Log from client (Aquamail) is a bit longer (see attachment). I have also listened to the communication using Wireshark. The last piece of communication is Client Helo. After the client sends Client Helo, there is no reply from Dovecot and the server closes the communication. This is the Client Helo, in the "structured view" iin Wireshark: |Secure Sockets Layer TLSv1 Record Layer: Handshake Protocol: Client Hello Content Type: Handshake (22) Version: TLS 1.0 (0x0301) Length: 176 Handshake Protocol: Client Hello Handshake Type: Client Hello (1) Length: 172 Version: TLS 1.2 (0x0303) Random: 2b7af5ba92040f081a5a3621e9d9cbab2d50b829b7fe755f... Session ID Length: 0 Cipher Suites Length: 62 Cipher Suites (31 suites) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e) Cipher Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d) Cipher Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a) Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d) Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x006b) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x0067) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033) Cipher Suite: TLS_ECDHE_RSA_WITH_RC4_128_SHA (0xc011) Cipher Suite: TLS_ECDHE_ECDSA_WITH_RC4_128_SHA (0xc007) Cipher Suite: TLS_RSA_WITH_RC4_128_SHA (0x0005) Cipher Suite: TLS_RSA_WITH_RC4_128_MD5 (0x0004) Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a) Cipher Suite: TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff) Cipher Suite: TLS_FALLBACK_SCSV (0x5600) Compression Methods Length: 1 Compression Methods (1 method) Extensions Length: 69 Extension: server_name (len=17) Extension: extended_master_secret (len=0) Extension: signature_algorithms (len=22) Type: signature_algorithms (13) Length: 22 Signature Hash Algorithms Length: 20 Signature Hash Algorithms (10 algorithms) Signature Algorithm: rsa_pkcs1_sha512 (0x0601) Signature Algorithm: ecdsa_secp521r1_sha512 (0x0603) Signature Algorithm: rsa_pkcs1_sha384 (0x0501) Signature Algorithm: ecdsa_secp384r1_sha384 (0x0503) Signature Algorithm: rsa_pkcs1_sha256 (0x0401) Signature Algorithm: ecdsa_secp256r1_sha256 (0x0403) Signature Algorithm: SHA224 RSA (0x0301) Signature Algorithm: SHA224 ECDSA (0x0303) Signature Algorithm: rsa_pkcs1_sha1 (0x0201) Signature Algorithm: ecdsa_sha1 (0x0203) | |What I tried: | * |change all possible settings in Dovecot (ssl_min_protocol, ssl_cipher_list ...)| * |change certificate I use| |I also got in touch with the developer of Aquamail (see our discussion here: https://www.aqua-mail.com/forum/index.php?topic=6824.0 ).| |The developer was able to reproduce the handshake error. We believe that the problem is that Dovecot rejects ClientHello as long as it is wrapped in the TLSv1 Record Layer (see the second lilne in the Wireshark log). According to the developer, Dovecot should accept Client Helo wrapped in the TLSv1 Record Layer.| |Thank you very much for your help. Best regards VB |

2 1

doveadm quota error output in some cases
by Kai Schaetzl 05 Oct '18

05 Oct '18

I am testing a special setup on one machine where I want to put some local users that get mail locally to /home user directories via postfix transport map local: for historical and practical reasons. Other users are setup as virtual users. The local users are *also* setup as virtual users for dovecot so that I can retrieve the mail via dovecot. I changed the SQL for dovecot user_query, so that it gets the local uid and gid (and doesn't use vmail) and also gets the home directory in /home for only those users. After a bit of experimenting this works fine and I can retrieve mail via dovecot. However, there are two problems with quota and one of them has "doveadm get quota" spew out a lot of garbage that I think should actually go to a log and not to the program output. When I run a doveadm quota get -A or -u user I get four errors of this kind (for user/domain storage and message limit) for each special user: doveadm(user): Error: Failed to get quota resource STORAGE: quota-dict: dict_lookup(priv/quota/storage) failed: net_connect_unix (/var/run/dovecot/dict) failed: Permission denied (euid=500(user) egid=200(vmail) missing +r perm: /var/run/dovecot/dict, dir owned by 0:0 mode=0755) (reply took 0.000 secs (0.000 in dict wait, 0.000 in other ioloops, 0.000 in locks)) Then the normal program output follows, with error lines for these special users, of course: user STORAGE error error error The reason is that /var/run/dovecot/dict is owned by vmail:vmail (not root:root as the 0:0 suggests). I don't see a way to change this without blocking the "real" virtual users that use vmail:vmail. Shouldn't this massive error output rather go to a log? (dovecot/error.log) Or: is there a way to avoid this? /var/run/dovecot/dict is a socket. I didn't want to fiddle with it. Can I change the permissions so that it can also be accessed by other system users? Probably only to make it world-readable? If so, what are the implications of doing that? Thanks, Kai

1 1

Username aliases
by Eirik Rye 05 Oct '18

05 Oct '18

Hi, Our organization is currently using a passwd-file user database for our Dovecot installs. However, we now want to provide simple username aliases. We currently use usernames that are -not- equal to the email address, but due to the fact that many major email clients/providers do not even allow you to specifiy a username, we now want to provide aliases where the username is equal to the email address. A simple solution would be to duplicate the lines in the passwd-file, with the email address as the username, but this does not seem be ideal due to data duplication. Ideally, there would be a secondary 'alias' userdb, which on a match would then restart the search in the primary passwd-file userdb using the new username. Is this possible? What would be the best way to go about this?

4 6

vpopmail
by Eric Broch 04 Oct '18

04 Oct '18

Hello list, I run Dovecot with the vpopmail driver and have found that it authenticates against the clear text password in the vpopmail database. Is there a configuration option either at compile time, link time, or a setting in one of the configuration files that tells the program to authenticate against the hash instead of the clear text? -- Eric Broch White Horse Technical Consulting (WHTC)

3 9

Re: [ceph-users] dovecot + cephfs - sdbox vs mdbox
by Webert de Souza Lima 04 Oct '18

04 Oct '18

Thanks Jack. That's good to know. It is definitely something to consider. In a distributed storage scenario we might build a dedicated pool for that and tune the pool as more capacity or performance is needed. Regards, Webert Lima DevOps Engineer at MAV Tecnologia *Belo Horizonte - Brasil* *IRC NICK - WebertRLZ* On Wed, May 16, 2018 at 4:45 PM Jack <ceph(a)jack.fr.eu.org> wrote: > On 05/16/2018 09:35 PM, Webert de Souza Lima wrote: > > We'll soon do benchmarks of sdbox vs mdbox over cephfs with bluestore > > backend. > > We'll have to do some some work on how to simulate user traffic, for > writes > > and readings. That seems troublesome. > I would appreciate seeing these results ! > > > Thanks for the plugins recommendations. I'll take the change and ask you > > how is the SIS status? We have used it in the past and we've had some > > problems with it. > > I am using it since Dec 2016 with mdbox, with no issue at all (I am > currently using Dovecot 2.2.27-3 from Debian Stretch) > The only config I use is mail_attachment_dir, the rest lies as default > (mail_attachment_min_size = 128k, mail_attachment_fs = sis posix, > ail_attachment_hash = %{sha1}) > The backend storage is a local filesystem, and there is only one Dovecot > instance > > > > > Regards, > > > > Webert Lima > > DevOps Engineer at MAV Tecnologia > > *Belo Horizonte - Brasil* > > *IRC NICK - WebertRLZ* > > > > > > On Wed, May 16, 2018 at 4:19 PM Jack <ceph(a)jack.fr.eu.org> wrote: > > > >> Hi, > >> > >> Many (most ?) filesystems does not store multiple files on the same > block > >> > >> Thus, with sdbox, every single mail (you know, that kind of mail with 10 > >> lines in it) will eat an inode, and a block (4k here) > >> mdbox is more compact on this way > >> > >> Another difference: sdbox removes the message, mdbox does not : a single > >> metadata update is performed, which may be packed with others if many > >> files are deleted at once > >> > >> That said, I do not have experience with dovecot + cephfs, nor have made > >> tests for sdbox vs mdbox > >> > >> However, and this is a bit out of topic, I recommend you look at the > >> following dovecot's features (if not already done), as they are awesome > >> and will help you a lot: > >> - Compression (classic, https://wiki.dovecot.org/Plugins/Zlib) > >> - Single-Instance-Storage (aka sis, aka "attachment deduplication" : > >> https://www.dovecot.org/list/dovecot/2013-December/094276.html) > >> > >> Regards, > >> On 05/16/2018 08:37 PM, Webert de Souza Lima wrote: > >>> I'm sending this message to both dovecot and ceph-users ML so please > >> don't > >>> mind if something seems too obvious for you. > >>> > >>> Hi, > >>> > >>> I have a question for both dovecot and ceph lists and below I'll > explain > >>> what's going on. > >>> > >>> Regarding dbox format (https://wiki2.dovecot.org/MailboxFormat/dbox) > >> when > >>> using sdbox, a new file is stored for each email message. > >>> When using mdbox, multiple messages are appended to a single file until > >> it > >>> reaches/passes the rotate limit. > >>> > >>> I would like to understand better how the mdbox format impacts on IO > >>> performance. > >>> I think it's generally expected that fewer larger file translate to > less > >> IO > >>> and more troughput when compared to more small files, but how does > >> dovecot > >>> handle that with mdbox? > >>> If dovecot does flush data to storage upon each and every new email is > >>> arrived and appended to the corresponding file, would that mean that it > >>> generate the same ammount of IO as it would do with one file per > message? > >>> Also, if using mdbox many messages will be appended to a said file > >> before a > >>> new file is created. That should mean that a file descriptor is kept > open > >>> for sometime by dovecot process. > >>> Using cephfs as backend, how would this impact cluster performance > >>> regarding MDS caps and inodes cached when files from thousands of users > >> are > >>> opened and appended all over? > >>> > >>> I would like to understand this better. > >>> > >>> Why? > >>> We are a small Business Email Hosting provider with bare metal, self > >> hosted > >>> systems, using dovecot for servicing mailboxes and cephfs for email > >> storage. > >>> > >>> We are currently working on dovecot and storage redesign to be in > >>> production ASAP. The main objective is to serve more users with better > >>> performance, high availability and scalability. > >>> * high availability and load balancing is extremely important to us * > >>> > >>> On our current model, we're using mdbox format with dovecot, having > >>> dovecot's INDEXes stored in a replicated pool of SSDs, and messages > >> stored > >>> in a replicated pool of HDDs (under a Cache Tier with a pool of SSDs). > >>> All using cephfs / filestore backend. > >>> > >>> Currently there are 3 clusters running dovecot 2.2.34 and ceph Jewel > >>> (10.2.9-4). > >>> - ~25K users from a few thousands of domains per cluster > >>> - ~25TB of email data per cluster > >>> - ~70GB of dovecot INDEX [meta]data per cluster > >>> - ~100MB of cephfs metadata per cluster > >>> > >>> Our goal is to build a single ceph cluster for storage that could > expand > >> in > >>> capacity, be highly available and perform well enough. I know, that's > >> what > >>> everyone wants. > >>> > >>> Cephfs is an important choise because: > >>> - there can be multiple mountpoints, thus multiple dovecot instances > on > >>> different hosts > >>> - the same storage backend is used for all dovecot instances > >>> - no need of sharding domains > >>> - dovecot is easily load balanced (with director sticking users to the > >>> same dovecot backend) > >>> > >>> On the upcoming upgrade we intent to: > >>> - upgrade ceph to 12.X (Luminous) > >>> - drop the SSD Cache Tier (because it's deprecated) > >>> - use bluestore engine > >>> > >>> I was said on freenode/#dovecot that there are many cases where SDBOX > >> would > >>> perform better with NFS sharing. > >>> In case of cephfs, at first, I wouldn't think that would be true > because > >>> more files == more generated IO, but thinking about what I said in the > >>> beginning regarding sdbox vs mdbox that could be wrong. > >>> > >>> Any thoughts will be highlt appreciated. > >>> > >>> Regards, > >>> > >>> Webert Lima > >>> DevOps Engineer at MAV Tecnologia > >>> *Belo Horizonte - Brasil* > >>> *IRC NICK - WebertRLZ* > >>> > >>> > >>> > >>> _______________________________________________ > >>> ceph-users mailing list > >>> ceph-users(a)lists.ceph.com > >>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > >>> > >> > >> _______________________________________________ > >> ceph-users mailing list > >> ceph-users(a)lists.ceph.com > >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > >> > > > >

1 1

Re: Bug reports - auth is broken in Dovecot 2.3.3
by Berindeie Avram-Teodor 04 Oct '18

04 Oct '18

> > I do not have downloaded the source from GitHub. > > On Wed, Oct 3, 2018 at 1:53 PM Timo Sirainen <tss(a)iki.fi> wrote: > >> On 3 Oct 2018, at 13.22, Berindeie Avram-Teodor <berindeie.teo(a)gmail.com> >> wrote: >> > >> > I applied the patch and recompiled but nothing resolved. >> > What else can I do? >> >> You also need to run autogen.sh & configure again. >> >>

4 5

Re: Dovecot User Listing Error - getpwent() failed: Invalid Argument
by Reuben Farrelly 04 Oct '18

04 Oct '18

Sure: https://www.reub.net/files/dovecot/lightning-dovecot.conf https://www.reub.net/files/dovecot/thunderstorm-dovecot.conf Updated nightly. Reuben On 1/09/2018 12:26 am, Aki Tuomi wrote: > Can you provide doveconf -n? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Reuben Farrelly <reuben-dovecot(a)reub.net> > Date: 31/08/2018 17:12 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi>, Dovecot Mailing List > <dovecot(a)dovecot.org> > Subject: Re: Dovecot User Listing Error - getpwent() failed: Invalid > Argument > > No. Neither of those are installed on either system. > > Reuben > > On 1/09/2018 12:09 am, Aki Tuomi wrote: > > Could apparmor or selinux be causing this! > > > > > > > > --- > > Aki Tuomi > > Dovecot oy > > > > -------- Original message -------- > > From: Reuben Farrelly <reuben-dovecot(a)reub.net> > > Date: 31/08/2018 16:50 (GMT+02:00) > > To: Dovecot Mailing List <dovecot(a)dovecot.org> > > Subject: Dovecot User Listing Error - getpwent() failed: Invalid Argument > > > > Hi, > > > > I'm running dovecot-2.3 git and seeing on 2 of my Dovecot installations, > > the following message logged quite frequently: > > > > Aug 31 16:55:53 lightning.reub.net dovecot[7698]: auth-worker(7707): > > Error: getpwent() failed: Invalid argument > > Aug 31 16:55:53 lightning.reub.net dovecot[7698]: replicator: Error: > > User listing returned failure > > Aug 31 16:55:53 lightning.reub.net dovecot[7698]: replicator: Error: > > listing users failed, can't replicate existing data > > > > It appears that this could be having an effect on replication, but it's > > unclear because the secondary/replica doesn't see much traffic. > > > > Authentication is via PAM and the system is Gentoo Linux x86_64. passb > > driver = pam, userdb driver = static . > > > > doveadm user -u '*' shows the system users listed twice like this (is > > this a problem?) and then prints: > > > > ---- > > reuben > > liam > > reuben > > liam > > <some other users> > > Error: User listing returned failure > > Fatal: user listing failed > > ---- > > > > To me that doesn't look right. > > > > Can anyone suggest what could be causing this? I don't recall seeing > > this message some time ago so I suspect it's a recent change in either > > dovecot, or pam or glibc etc.. > > > > Thanks, > > Reuben

2 10

Authenticate users using their firstname
by Fady AL HAYALI 04 Oct '18

04 Oct '18

Hi, I'm setting up a Postfic and Dovecot with LDAP email server. My users in LDAP is like this: dn: uid=firstname,ou=People,dc=domain,dc=com uid: firstname uidNumber: 4025 gidNumber: 4025 givenName: firstname objectClass: top objectClass: person objectClass: posixAccount objectClass: shadowAccount objectClass: organizationalPerson objectClass: inetOrgPerson loginShell: /bin/bash homeDirectory: /home/firstname cn: firstname lastname mail: firstname.lastname(a)domain.com<mailto:firstname.lastname@domain.com> This is how I connect Dovecot with LDAP hosts = ldapserver ldap_version = 3 base = ou=People,dc=domain,dc=com deref = never scope = subtree user_attrs = user_filter = (&(objectclass=inetOrgPerson)(uid=%n) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectclass=inetOrgPerson)(uid=%n)) default_pass_scheme = SSHA When I enter a user's email address and password as the following: email: firstname.lastname(a)domain.com<mailto:firstname.lastname@domain.com> password: password and according to my setting which I used "%n" as you see above, the username used to authenticate is "firstname.lastname". I checked the Dovecot variables but I couldn't find something useful in this case to manipulate the "%n" variable. I would like to keep using email addresses as "firstname.lastname(a)domain.com"<mailto:firstname.lastname@domain.com> but authenticate users using their first name. I really hit a wall here and any help will be much appreciated.

6 6

Possible architecture ?
by Alexandre Ellert 03 Oct '18

03 Oct '18

Hi, I'd like to achieve the following setup whit dovecot using multiple servers : - one server dedicated to all client IMAP (TLS) connections (i <http://mail.numeezy.com>map.mymaindomain.com, see below ) - each backend server has it's own local storage. no replication - each backend server responsible of a few domains - each backend server has it's own Mysql local database for user's passwords. ===> Server 1 : domains A, B and C ====> i <http://mail.numeezy.com>map.mymaindomain.com ===> Server 2 : domains D, E and F (143 TLS / 993 SSL) ===> Server 3 : domains G, H For example, if a user connects from domain E to i <http://mail.numeezy.com> map.mymaindomain.com, will Dovecot be able to use password database hosted on Server 2 ? Thank you ! Alex

3 3

Delete vs. Expunge in Public Namespace
by Chris 03 Oct '18

03 Oct '18

All, my IMAP client [1] marks messages as deleted, but doesn't expunge. Dovecot (2.2.27-3+deb9u2) expunges them. Is this because the mailbox is part of public namespace? .... ::1.38247-::1.00143: MALP6 STORE 48,49,50,51,52,53,54,55,56,57,58,59,60,61 +FLAGS (\Deleted) ::1.00143-::1.38247: * 48 FETCH (FLAGS (\Deleted \Seen)) * 49 FETCH (FLAGS (\Deleted \Seen)) * 50 FETCH (FLAGS (\Deleted \Seen)) * 51 FETCH (FLAGS (\Deleted \Seen)) * 52 FETCH (FLAGS (\Deleted \Seen)) * 53 FETCH (FLAGS (\Deleted \Seen)) * 54 FETCH (FLAGS (\Deleted \Seen)) * 55 FETCH (FLAGS (\Deleted \Seen)) * 56 FETCH (FLAGS (\Deleted \Seen)) * 57 FETCH (FLAGS (\Deleted \Seen)) * 58 FETCH (FLAGS (\Deleted \Seen)) * 59 FETCH (FLAGS (\Deleted \Seen)) * 60 FETCH (FLAGS (\Deleted \Seen)) * 61 FETCH (FLAGS (\Deleted \Seen)) MALP6 OK Store completed. ::1.38247-::1.00143: MALP7 SEARCH DELETED .... Oct 2 10:18:03 hyptest dovecot: imap(chris): delete: box=MailingListen/test125, uid=180, msgid=<740a9ba3-d637-3fa0-1b87-ff8d79491bf0@ hyp.postbox.xyz>, size=1509 Oct 2 10:18:03 hyptest dovecot: imap(chris): expunge: box=MailingListen/test125, uid=167, msgid=<740a9ba3-d637-3fa0-1b87-ff8d79491bf0 @hyp.postbox.xyz>, size=1509 namespace { list = yes location = maildir:/var/vmail/public/:LAYOUT=fs:INDEXPVT=%h/.public-indexes prefix = MailingListen/ separator = / subscriptions = no type = public } - Chris [1] https://raw.githubusercontent.com/quentinsf/IMAPdedup/master/imapdedup.py

2 3

Bug reports - auth is broken in Dovecot 2.3.3
by Berindeie Avram-Teodor 03 Oct '18

03 Oct '18

I applied the patch and recompiled but nothing resolved. What else can I do?

3 3

Bug reports - auth is broken in Dovecot 2.3.3
by Berindeie Avram-Teodor 03 Oct '18

03 Oct '18

Hello, I have compiled Dovecot 2.3.3 from sources but I have problems with authentication. I tried to rebuild Dovecot 2.3.2.1 but the error persists. I attach a .txt file with the information requested to report a bug. My main mail server is fallen, (the same for the test server) I will send the report from a Gmail address. If you need additional information I will be at your disposal.

2 1

Need to convert mbox to Maildir
by Mark Foley 02 Oct '18

02 Oct '18

I have a mbox file of emails. I want to convert this to Maildir giving me individual message files per email. I've looked at dsync, but as far as I can tell this wants a specific target user and it appears that it will "distribute" the converted messages into that user's INBOX. I don't want to put these mbox messages into any particular user's Maildir hierarchy, just export to file-per-message format to a destination directory of my choosing. Is this possible? THX --Mark

2 2

Help for UID THREAD and SORT optimization
by Alessio Cecchi 02 Oct '18

02 Oct '18

Hello, we are developing a library to show last arrived messages of all threads in a folder with more than 300k messages. As per the RFC 5256, the IMAP thread command has only the option to specify the grouping criteria (REFERENCES vs ORDEREDSUBJECT). So we implemented an algorithm which gets the full UID SORT ordered by date in reverse order then gets all thread relations and then post process all outputs to obtain the final result. Once we have both output we loop through the first uids set (which is ordered) and for every item of it we loop through the other uids set with all the thread relations. If the uid of the first set is contained in one of the elements of the thread messages, we pick it up and push it in the resulting array. This is a pseudo-code that shows what we are doing: array_of_latest_messages_in_thread = [] array_of_sorted_uids = [n,n,n,n,...] // UID SORT (REVERSE DATE) UTF-8 ALL array_of_thread_uids = [n,[n,n],n,[n,n,n],[n,n],n,n,...] // UID THREAD (REFERENCES) UTF-8 ALL foreach(array_of_sorted_uids as s_uid){ foreach(array_of_thread_uids as t_uids){ if(t_uids contains s_uid){ // or a function to loop recursively t_uids to search if a leaf is equal to s_uid array_of_latest_messages_in_thread.push(s_uid) break } } } We have also made some little optimizations in the above code like for example skipping from the outer loop the uids already processed in the inner loop that have not being selected. Anyway, the loop is very expensive in term of computation and we are wondering if there is a better approach to this issue directly using IMAP instead of post processing the output of the two commands at application level. Thanks. -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

2 2

Bug in conditionals to assign values to variables?
by Angel L. Mateo 02 Oct '18

02 Oct '18

Hi, According to https://wiki2.dovecot.org/Variables you could use conditionals to assign values to a varible. The syntax is: %{if;value1;operator;value2;value-if-true;value-if-false} where any of the fields can refer to another field using %v or %{value} syntax. The problem is that when I use a config like: user_attrs = ...,=relpath=%{if;%u;eq;somevalue;valuetrue;valuefalse} it works without any problem. But when I use: user_attrs = ...,=relpath=%{if;%{user};eq;somevalue;valuetrue;valuefalse} then it reports in logs: Sep 28 14:23:22 myotis60 dovecot: auth: Error: var_expand_long(if;%{user}) failed: if: requires four or five parameters, got 1 anyway, the variable is correctly initialized, but I get the log. Is this a bug? PS: I'm running dovecot 2.2.33 -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

2 3

split auth from other logging
by Kai Schaetzl 02 Oct '18

02 Oct '18

Is there a way to split the auth logging (logins and failed logins) from the other logging that goes to info_log_path = /var/log/dovecot/dovecot.log ? This log gets a lot of other info as well, most notably the lmtp notifications about every filed mail (with no level stamping, btw). This makes it really hard to find authentication errors quickly and comfortably. It would be nice to be able to split at least the lmtp messages away. Kai

4 9

Released Pigeonhole v0.5.3 for Dovecot v2.3.3.
by Stephan Bosch 02 Oct '18

02 Oct '18

Hello Dovecot users, Here's the Pigeonhole release that goes with Dovecot v2.3.3. Only two insignificant memory leak fixes were added since the release candidate (not mentioned in the changelog). Changelog v0.5.3: - Fix assertion panic occurring when managesieve service fails to open INBOX while saving a Sieve script. This was caused by a lack of cleanup after failure. - Fix specific messages causing an assert panic with actions that compose a reply (e.g. vacation). With some rather weird input from the original message, the header folding algorithm (as used for composing the References header for the reply) got confused, causing the panic. - IMAP FILTER=SIEVE capability: Fix FILTER SIEVE SCRIPT command parsing. After finishing reading the Sieve script, the command parsing sometimes didn't continue with the search arguments. This is a time- critical bug that likely only occurs when the Sieve script is sent in the next TCP frame. The release is available as follows: https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.3.ta… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.3.ta… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

v2.3.3 rc1 - Error: sieve: !!BUG!!: Binary compiled from dovecot.sieve is still corrupt
by James 01 Oct '18

01 Oct '18

I have a sieve problem with dovecot v2.3.3 rc1 with either of pigeonhole 0.5.2 or 0.5.3.rc1. The the change that triggers this is in dovecot not pigeonhole. Sieve filtering has been working with v2.3.2 and many earlier versions. Log report: Sep 24 10:36:13 mailhost dovecot: [ID 702911 mail.error] lmtp(user(a)domain.tld)<15816><RnikKw2wqFvIPQAAs831Jw>: Error: sieve: !!BUG!!: Binary compiled from /path/to/domain/user/dovecot.sieve is still corrupt; bailing out and reverting to default delivery This is a sieve script with a vacation handler. My other sieve filters are working. My actual sieve filter worked before and was written by Roundcube web mail. My failing test script is cut-n-paste from the sieve examples https://wiki2.dovecot.org/Pigeonhole/Sieve/Examples so should not be in doubt. The text script compiles to dovecot.svbin and newly compiled files are identical to older versions, the compilation has not changed. James.

5 21

v2.3.3 released
by Timo Sirainen 01 Oct '18

01 Oct '18

https://dovecot.org/releases/2.3/dovecot-2.3.3.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.3.tar.gz.sig * doveconf hides more secrets now in the default output. * ssl_dh setting is no longer enforced at startup. If it's not set and non-ECC DH key exchange happens, error is logged and client is disconnected. + Added log_debug=<filter> setting. + Added log_core_filter=<log filter> setting. + quota-clone: Write to dict asynchronously + --enable-hardening attempts to use retpoline Spectre 2 mitigations + lmtp proxy: Support source_ip passdb extra field. + doveadm stats dump: Support more fields and output stddev by default. + push-notification: Add SSL support for OX backend. - NUL bytes in mail headers can cause truncated replies when fetched. - director: Conflicting host up/down state changes may in some rare situations ended up in a loop of two directors constantly overwriting each others' changes. - director: Fix hang/crash when multiple doveadm commands are being handled concurrently. - director: Fix assert-crash if doveadm disconnects too early - virtual plugin: Some searches used 100% CPU for many seconds - dsync assert-crashed with acl plugin in some situations. - mail_attachment_detection_options=add-flags-on-save assert-crashed with some specific Sieve scripts. - Mail snippet generation crashed with mails containing invalid Content-Type:multipart header. - Log prefix ordering was different for some log lines. - quota: With noenforcing option current quota usage wasn't updated. - auth: Kerberos authentication against Samba assert-crashed. - stats clients were unnecessarily chatty with the stats server. - imapc: Fixed various assert-crashes when reconnecting to server. - lmtp, submission: Fix potential crash if client disconnects while handling a command. - quota: Fixed compiling with glibc-2.26 / support libtirpc. - fts-solr: Empty search values resulted in 400 Bad Request errors - fts-solr: default_ns parameter couldn't be used - submission server crashed if relay server returned over 7 lines in a reply (e.g. to EHLO)

1 0

doveadm backup abort in imapc-client.c
by Evan Klitzke 01 Oct '18

01 Oct '18

I am using Dovecot 2.2.36 and I am trying to use doveadm backup to migrate email from Gmail to Dovecot. When I run doveadm backup, it goes for a while and then eventually hits an assertion error (I've tried this a few times now and it happens reliably). The assertion failure looks like this: dsync(evan(a)eklitzke.org): Panic: file imapc-client.c: line 179 (imapc_client_run_pre): assertion failed: (client->ioloop == NULL) The last few lines of log output before the crash look like this: https://gist.github.com/eklitzke/9a0dd77c44a6ee33e812f85d5773c24c The GDB backtrace when the program panics looks like this: https://gist.github.com/eklitzke/6b311474b08b546c462e0444c5cf479b The output of "dovecot --version" prints "2.2.36 (1f10bfa63)" and I'm using the version provided by Fedora's dovecot-2.2.36-1.fc28.src.rpm package. Is there any other information I can provide to assist in debugging? I could provide a core dump provided there was a way to scrub my IMAP credentials. -- Evan Klitzke pgp: 0x157EFCACBC648422 e: evan(a)eklitzke.org w: https://eklitzke.org

3 3

dsync replication
by Matt Bryant 01 Oct '18

01 Oct '18

We have a setup with ldap and sql passdbs and sql userdb, from my understanding of the documentation dsync repliction picks up the users to replicate via the iterate query. This query returns 646 users in sql (not everyone gets replicated) but when i run a doveadm replicator status Total number of known users 92236 seriously that kinda lot more than 646 Does iterate_query belong in user_db or passdb? Is it the fact I have ldap and sql passdb and its picking up dome default ldap query as well the specified sql iterate query ? rgds Matt

1 0

Local access to IMAP mailboxes
by Victor Sudakov 29 Sep '18

29 Sep '18

Dear Colleagues, I have made mailboxes in ~/Mail available via IMAP (Dovecot 2.3.2.1), that is: "mail_location = mbox:~/Mail:INBOX=/var/mail/%u" However, I often read and modify the mailboxes locally with mutt (e.g. append and delete mails). Should I expect any problems wit Dovecot indexes etc? What if I even do "rm ~/Mail/some/mailbox", will Dovecot be mad at me? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/

6 19

having problems with Argon
by Adam Gold 28 Sep '18

28 Sep '18

Hello everyone. I'm close to completing my first build of a mail server - Postfix, Dovecot, Postgres (I know, sounds like overkill), Rspamd with Redis and Unbound (please infer a mega lack of experience disclaimer). The model is standalone internet with remoted sasl-authenticated clients. Throughout the process I've been having consistent problems with user password authentication. Both when I began when I was only using flat files and now with pgsql, more often than not my username (full email address) and password combo have been rejected. The postfix logs started with fairly innocent 'failed login' messages and eventually reached the "you don't own this email address, you're a spammer" level. Dovecot has been consistent with "auth: Debug: client passdb out: FAIL" messages. Before I looked at this issue specifically, my guess was it came from a Postfix restriction but having spent quite a while going through it today, I don't think that's where it lies. Finally I went back to basics and changed an account password to {PLAIN}12345 and what do you know - effortless success! Previously I'd been using mainly argon, ssha512 sha512-crypt and a few others. My passwords are strong (well in excess of 20 characters, 'randomly' generated). I spent this afternoon narrowing down the hashes and while I haven't finished, the only one I couldn't get to work with 12345 was argon. I also noticed that the wiki says the 2I and 2ID versions of Argon are available, doveadm pw always returned a "does not exist" error when I tried to use 2ID. I'm using Dovecot version 2.3.2.1 (0719df592)

2 1

Collecting S/MIME Certs from (incoming signed) E-Mails
by Jochen Bern 28 Sep '18

28 Sep '18

Two quick questions, if I may: We've been asked to change an existing application (whose builtin S/MIME capabilities are quite unclear) so that the e-mails it sends will be S/MIME encrypted, if possible. I have some experience in getting an MTA to encrypt e-mails in transit, but the trick is, of course, to maintain a list of addressees' (current) certs. Ideally, users send e-mails *to* the application beforehand, and with a bit of luck, they might even *sign* them (which, in the case of S/MIME, IIUC implies that their cert is attached). 1. Are there features in a) the IMAP protocol and/or b) dovecot in particular that would allow me to extract the certs from incoming e-mails before the application retrieves them from the mailbox? (I know that IMAP allows me to download only a MIME part of an e-mail, but I'ld need to somehow determine *which* MIME part to download, I guess?) 2. Assuming that the incoming e-mail is S/MIME signed *and encrypted*, is it actually possible to extract the sender cert *without* having the application's keypair to *decrypt* the e-mail in the process? Kind regards, -- Jochen Bern Systemingenieur www.binect.de www.facebook.de/binect

1 0

Custom variable
by Ángel L. Mateo 27 Sep '18

27 Sep '18

Hi, I know that there are some variables (as user or username) I could use inside dovecot. They are at https://wiki2.dovecot.org/Variables. My question is if I can create my own variables from attributes at my pass/user db and then use it inside dovecot configuration. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

2 5

Connection and login scripts callback
by Stanislav Humplík 27 Sep '18

27 Sep '18

Hello, currently there is very handy post-login scripting already implemented but it naturally executes only when successful login happens. I would like to have another two script callbacks which runs: 1. immediately after client connects to server - dovecot should run script with connection IP and wait for result and then reject/accept connection with return message accordingly. 2. after failed login - dovecot should exec script with connection IP, login params without waiting for result The main reason behind this idea is to use some logic, database (redis...) or indicators like GeoIP, p0f as bruteforce prevention. It might be also usable for IP based ACLs. AFAIK the only way to create something similar is to proxy whole authentication to some external process, which is not desirable when dovecot manages user database. SH

2 1

Can't authenticate using ARGON2ID crypt scheme from doveadm pw w/rounds != default
by Keith Amidon 27 Sep '18

27 Sep '18

I'm using dovecot version 2.3.2.1 (0719df592) and trying to use the ARGON2ID crypt scheme for authentication using the passdb passwd-file driver. My passdb config is very simple: passdb { driver = passwd-file args = username_format=%u <path-to-file-here> } If I generate a password this way: doveadm pw -s ARGON2ID -p 'This is a test' I get a crypt value for the password that I can place in the password file like: testuser:{ARGON2ID}$argon2id$v=19$m=65536,t=3,p=1$UuqF25QtumNBe9R2FmUZvA$5avvHY5TIaj5Wl5C4k8BOI4bcmNei7BwPLlXYQVybMc And if I test authentication with this command: doveadm auth login testuser 'This is a test' It works as shown by the (lightly redacted) log: Sep 25 22:46:01 myhost dovecot[17538]: auth: Debug: auth client connected (pid=55417) Sep 25 22:46:01 myhost dovecot[17538]: auth: Debug: client in: AUTH 1 PLAIN service=doveadm debug resp=<hidden> Sep 25 22:46:01 myhost dovecot[17538]: auth: Debug: passwd-file(testuser): lookup: user=testuser file=<path-to-passwd-file> Sep 25 22:46:01 myhost dovecot[17538]: auth: Debug: client passdb out: OK 1 user=testuser However, if I instead specify a non-default number of rounds this way: doveadm pw -s ARGON2ID -p 'This is a test' -r 7 and place the result in an entry in the password file like: testuser:{ARGON2ID}$argon2id$v=19$m=1048576,t=7,p=1$kIhnUR13GrtOvvpbJNJmnQ$o7O6Whxs3s8IE09yY9S2dPkJjJyEVc78GRFilYVS9fU Then testing authentication using the same command (repeated here): doveadm auth login testuser 'This is a test' then authentication fails, as shown by this (lightly redacted) log: Sep 25 22:52:05 myhost dovecot[17538]: auth: Debug: auth client connected (pid=55557) Sep 25 22:52:05 myhost dovecot[17538]: auth: Debug: client in: AUTH 1 PLAIN service=doveadm debug resp=<hidden> Sep 25 22:52:05 myhost dovecot[17538]: auth: Debug: passwd-file <path-to-passwd-file>: Read 3 users in 0 secs Sep 25 22:52:05 myhost dovecot[17538]: auth: Debug: passwd-file(testuser): lookup: user=testuser file=<path-to-passwd-file> Sep 25 22:52:05 myhost dovecot[17538]: auth: passwd-file(testuser): Password mismatch Sep 25 22:52:07 myhost dovecot[17538]: auth: Debug: client passdb out: FAIL 1 user=testuser Experimentation with other values for the -r option has not produced a value that works for me. Using the exact same procedure but the BLF-CRYPT scheme, with varying number of rounds, does work. Am I doing something wrong or is there a bug in either the doveadm pw generation or the auth evaluation of the password? I'd like to use ARGON2ID with ~6 rounds if I can make this work. Any help would be greatly appreciated. Thanks, Keith

2 2

What causes folders to be reported as noselect?
by Daniel Miller 27 Sep '18

27 Sep '18

As the subject says. This may be a bit open-ended - but it would really help troubleshooting some obscure folder issues. In my case, I happen to have both some "real" folders and also some "virtual" folders that respond to IMAP LIST commands with the "\NoSelect" flag - and I don't know why. Via telnet, I can manually issue SELECT, SEARCH, and FETCH for such folders without errors. -- Daniel

2 2

Possible bug - otherwise a public admission of oops
by Daniel Miller 27 Sep '18

27 Sep '18

While trying to identify possible causes of wrong mail folder creation I did something...bad. Normally, I would recognize that deleting a mail folder would naturally delete all the contained mails. However...somehow my imaginative self decided that deleting a virtual folder via IMAP would only delete the virtual folder...and not proceed to delete every referenced email via the virtual mapping. So note to self, and possible reminder to others, deleting a virtual folder via a filesystem command is just tiny bit different than via IMAP... Fortunately I keep my feathers numbered for just such an emergency... -- Daniel

1 0

dovecot/FreeBSD and Android IMAP clients
by Victor Sudakov 25 Sep '18

25 Sep '18

Dear Colleagues, I have a fairly vanilla setup of dovecot on FreeBSD, serving IMAP and POP3. Thunderbird/IMAP works fine, and so does mutt/IMAP. However, Android clients (Gmail/IMAP and K-9 Mail) have problems accessing folders other than the INBOX. They either show them empty with no mails (K-9) or just wait forever to view the contents (Gmail app). Do I need to set up some workarounds or hacks in dovecot for Android IMAP clients to work correctly? Any advice is appreciated. My config is below: # 2.3.2.1 (0719df592): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 11.2-RELEASE-p3 amd64 # Hostname: admin.sibptus.ru mail_location = mbox:~/Mail:INBOX=/var/mail/%u mail_privileged_group = mail 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 { driver = pam } protocols = imap pop3 ssl_cert = </usr/local/etc/exim/mail.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/

2 2

Nightly builds of Debian packages
by Christoph Pleger 24 Sep '18

24 Sep '18

Hello, how is the future of the automatically built nightly debian packages of dovecot? Has that project been ceased? The current auto-built version is still 2.2.28 from April 28, though 2.2.29 (with a security patch) of dovecot is out now for a while. Regards Christoph

4 3

Last_login plugin and mysql
by Thomas Hooge 24 Sep '18

24 Sep '18

Hello, i have problems configuring the last_login plugin with mysql. I have extended the postfixadmin database with a new field, configured the plugin as described in the wiki. Finally i got errors: table is not writable, INSERT failed. Why is the insert required? The plugin should only UPDATE the column for existing rows. Or am i missing some configuration options? Here is my dictionary config: map { pattern = shared/last-login/$user table = mailbox value_field = x_last_login value_type = uint fields { username = $user } } Dovecot: 2.2.27 (c0f36b0) Kind regards, Thomas

2 2

Error using dsync to convert really old mboxes to Maildir and workaround
by faginbagin 24 Sep '18

24 Sep '18

I ran across what I think may be a bug in dsync when trying to convert from mbox to Maildir format. My first attempt failed with a runaway dsync process spewing out thousands of identical lines of the form: dsync(buus): Error: Duplicate mailbox GUID 00fe691ff60da85b090d0000c8119523 for mailboxes Archive/Personal and Work/VendorInfo - giving a new GUID 00fe691ff60da85b090d0000c8119523 to Archive/Personal These two mail folders happen to be among a number of folders I've had for many years, but also haven't looked at in many years. I used to use UW-IMAP, but switched to dovecot about two years ago, and I'm sure I've never used dovecot to look at those folders. So I suspect the root cause of the above error message was that dovecot had never generated GUIDs for these and some other really old folders. After killing dsync with SIGKILL, which couldn't be killed with SIGTERM, I restored my mbox format Mail folder from backup, restored the mail_location and then coerced dovecot to generate unique GUIDs for all my mail folders with this command: doveadm mailbox status guid `doveadm mailbox list` After the above command, I was able to convert my mail from mbox to Maildir format. Maybe this will help someone else somewhere down the road.

2 2

Released Pigeonhole v0.5.3.rc1 for Dovecot v2.3.3.rc1.
by Stephan Bosch 23 Sep '18

23 Sep '18

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3.3 release candidate. It consists only of bugfixes. Changelog v0.5.3: - Fix assertion panic occurring when managesieve service fails to open INBOX while saving a Sieve script. This was caused by a lack of cleanup after failure. - Fix specific messages causing an assert panic with actions that compose a reply (e.g. vacation). With some rather weird input from the original message, the header folding algorithm (as used for composing the References header for the reply) got confused, causing the panic. - IMAP FILTER=SIEVE capability: Fix FILTER SIEVE SCRIPT command parsing. After finishing reading the Sieve script, the command parsing sometimes didn't continue with the search arguments. This is a time- critical bug that likely only occurs when the Sieve script is sent in the next TCP frame. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.3/rc/dovecot-2.3-pigeonhole-0.5.3.… http://pigeonhole.dovecot.org/releases/2.3/rc/dovecot-2.3-pigeonhole-0.5.3.… Refer to http://pigeonhole.dovecot.org and the Dovecot wiki for more information. Have fun testing this release candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Global sieve doesn't run and I don't know why
by Ranbir 21 Sep '18

21 Sep '18

Hi Everyone, I have dovecot, postfix, roundcube and piegeonhole managesieve all working nicely together. Personal scripts defined in roundcube run without issue. I have configured the global sieve dir defined in 90-sieve.conf: sieve_global_dir = /var/lib/dovecot/sieve/global/ I pre-compiled the script in there: # ls -l /var/lib/dovecot/sieve/global/ total 8 -rw-r--r--. 1 root root 118 Sep 19 16:52 global.sieve -rw-r--r--. 1 root root 197 Sep 19 16:56 global.svbin But, in the logs for dovecot, I never see the script being run: https://www.pastiebin.com/5ba3faa8628c2 Users are from freeipa. Their home directories are symlinks to where the mail really lives. For example: lrwxrwxrwx. 1 ranbir virtual 42 May 25 2017 ranbir -> /var/spool/mail/domain.tld/ranbir/ And the contents of that dir: [root@mailhost conf.d]# ls -al /home/DOMAIN/ranbir/ total 64 drwxrwx---. 4 ranbir virtual 4096 Sep 18 17:40 . drwxrwx---+ 13 virtual virtual 4096 Jul 8 12:06 .. -rw-------. 1 ranbir ranbir 17808 Sep 20 01:13 .bash_history -rw-------. 1 ranbir ranbir 18 Dec 14 2015 .bash_logout -rw-------. 1 ranbir ranbir 193 Dec 14 2015 .bash_profile -rw-------. 1 ranbir ranbir 231 Dec 14 2015 .bashrc lrwxrwxrwx. 1 virtual virtual 23 Feb 11 2018 .dovecot.sieve -> sieve/managesieve.sieve lrwxrwxrwx. 1 virtual virtual 23 Sep 18 16:53 .dovecot.sieve.log -> sieve/dovecot.sieve.log -rw-rw----. 1 virtual virtual 322 Sep 18 17:40 .dovecot.svbin -rw-------. 1 ranbir ranbir 59 Jun 7 2016 .lesshst drwx------. 56 virtual virtual 4096 Sep 20 15:02 Maildir drwxrwx---. 3 ranbir virtual 89 Sep 18 17:16 sieve -rw-------. 1 ranbir ranbir 6415 Feb 11 2018 .viminfo Did I miss something in the configuration? Dovecot isn't throwing any errors. I can only conclude I haven't completed the setup for global sieve to work or that I've misunderstood what the "sieve_global_dir" paramater is for. Thanks! -- Ranbir

4 11

Re: v2.3.3 release candidate released
by Tuomi, Aki 21 Sep '18

21 Sep '18

It should work if you add it to apt. Directory listing is denied, which causes 403 if you access with browser. Aki -------- Original message --------From: Michael Marley <michael(a)michaelmarley.com> Date: 21/09/2018 18:00 (GMT+02:00) To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: Re: v2.3.3 release candidate released On 2018-09-21 09:45, Timo Sirainen wrote: > https://dovecot.org/releases/2.3/rc/dovecot-2.3.3.rc1.tar.gz > https://dovecot.org/releases/2.3/rc/dovecot-2.3.3.rc1.tar.gz.sig > > Binary packages are also available in https://repo.dovecot.org/ in > ce-2.3.3 repository (not ce-2.3-latest). > > * doveconf hides more secrets now in the default output. > * ssl_dh setting is no longer enforced at startup. If it's not set and > non-ECC DH key exchange happens, error is logged and client is > disconnected. > > + Added log_debug=<filter> setting. > + Added log_core_filter=<log filter> setting. > + quota-clone: Write to dict asynchronously > + --enable-hardening attempts to use retpoline Spectre 2 mitigations > + lmtp proxy: Support source_ip passdb extra field. > + doveadm stats dump: Support more fields and output stddev by > default. > + push-notification: Add SSL support for OX backend. > - NUL bytes in mail headers can cause truncated replies when fetched. > - director: Conflicting host up/down state changes may in some rare > situations ended up in a loop of two directors constantly > overwriting > each others' changes. > - virtual plugin: Some searches used 100% CPU for many seconds > - dsync assert-crashed with acl plugin in some situations. > - mail_attachment_detection_options=add-flags-on-save assert-crashed > with some specific Sieve scripts. > - Mail snippet generation crashed with mails containing invalid > Content-Type:multipart header. > - Log prefix ordering was different for some log lines. > - quota: With noenforcing option current quota usage wasn't updated. > - auth: Kerberos authentication against Samba assert-crashed. > - stats clients were unnecessarily chatty with the stats server. > - imapc: Fixed various assert-crashes when reconnecting to server. > - lmtp, submission: Fix potential crash if client disconnects while > handling a command. > - quota: Fixed compiling with glibc-2.26 / support libtirpc. > - fts-solr: Empty search values resulted in 400 Bad Request errors > - fts-solr: default_ns parameter couldn't be used > - submission server crashed if relay server returned over 7 lines in > a reply (e.g. to EHLO) It looks like the ce-2.3.3 repository (or at least https://repo.dovecot.org/ce-2.3.3/ubuntu/xenial/) is returning a 403. Michael

1 0

v2.3.3 release candidate released
by Timo Sirainen 21 Sep '18

21 Sep '18

https://dovecot.org/releases/2.3/rc/dovecot-2.3.3.rc1.tar.gz https://dovecot.org/releases/2.3/rc/dovecot-2.3.3.rc1.tar.gz.sig Binary packages are also available in https://repo.dovecot.org/ in ce-2.3.3 repository (not ce-2.3-latest). * doveconf hides more secrets now in the default output. * ssl_dh setting is no longer enforced at startup. If it's not set and non-ECC DH key exchange happens, error is logged and client is disconnected. + Added log_debug=<filter> setting. + Added log_core_filter=<log filter> setting. + quota-clone: Write to dict asynchronously + --enable-hardening attempts to use retpoline Spectre 2 mitigations + lmtp proxy: Support source_ip passdb extra field. + doveadm stats dump: Support more fields and output stddev by default. + push-notification: Add SSL support for OX backend. - NUL bytes in mail headers can cause truncated replies when fetched. - director: Conflicting host up/down state changes may in some rare situations ended up in a loop of two directors constantly overwriting each others' changes. - virtual plugin: Some searches used 100% CPU for many seconds - dsync assert-crashed with acl plugin in some situations. - mail_attachment_detection_options=add-flags-on-save assert-crashed with some specific Sieve scripts. - Mail snippet generation crashed with mails containing invalid Content-Type:multipart header. - Log prefix ordering was different for some log lines. - quota: With noenforcing option current quota usage wasn't updated. - auth: Kerberos authentication against Samba assert-crashed. - stats clients were unnecessarily chatty with the stats server. - imapc: Fixed various assert-crashes when reconnecting to server. - lmtp, submission: Fix potential crash if client disconnects while handling a command. - quota: Fixed compiling with glibc-2.26 / support libtirpc. - fts-solr: Empty search values resulted in 400 Bad Request errors - fts-solr: default_ns parameter couldn't be used - submission server crashed if relay server returned over 7 lines in a reply (e.g. to EHLO)

2 1

Re: Duplicate mails on pop3 expunge with dsync replication on 2.2.35 (2.2.33.2 works)
by Gerald Galster 21 Sep '18

21 Sep '18

Hi Tim, > Do you have any new insights on the problem with reappearing mail using dovecot replication + pop3? > > It's driving me mad. I'm running dovecot 2.2.34 (874deae) on OpenBSD and it looks like I have the same problem as you have. unfortunately there has been no response, I'm stuck with 2.2.33.2 for the time being. I can only suspect it has something to do with mailbox locking which was introduced in 2.2.34 (int dsync_mailbox_lock) or maybe with some cached values (drop_older_timestamp) as it just happens when the mail is deleted on the node that it has been synced to but not if it's deleted on the node where it has originally been received. Best regards, Gerald diff -Nru dovecot-2.2.33.2/src/doveadm/dsync/dsync-brain-mailbox.c dovecot-2.2.34/src/doveadm/dsync/dsync-brain-mailbox.c --- dovecot-2.2.33.2/src/doveadm/dsync/dsync-brain-mailbox.c 2017-10-05 19:10:44.000000000 +0200 +++ dovecot-2.2.34/src/doveadm/dsync/dsync-brain-mailbox.c 2018-02-28 15:45:34.000000000 +0100 @@ -522,25 +529,33 @@ } /* mailbox appears to have changed. do a full sync here and get the - state again */ + state again. Lock before syncing. */ + if (dsync_mailbox_lock(brain, box, &lock) < 0) { + brain->failed = TRUE; + mailbox_free(&box); + return -1; + } if (mailbox_sync(box, MAILBOX_SYNC_FLAG_FULL_READ) < 0) { i_error("Can't sync mailbox %s: %s", mailbox_get_vname(box), mailbox_get_last_internal_error(box, &brain->mail_error)); ... @@ -599,6 +615,7 @@ static void dsync_cache_fields_update(const struct dsync_mailbox *local_box, const struct dsync_mailbox *remote_box, + struct mailbox *box, struct mailbox_update *update) { ARRAY_TYPE(mailbox_cache_field) local_sorted, remote_sorted, changes; @@ -630,7 +647,8 @@ local_fields = array_get(&local_sorted, &local_count); remote_fields = array_get(&remote_sorted, &remote_count); t_array_init(&changes, local_count + remote_count); - drop_older_timestamp = ioloop_time - MAIL_CACHE_FIELD_DROP_SECS; + drop_older_timestamp = ioloop_time - + box->index->optimization_set.cache.unaccessed_field_drop_secs; diff -Nru dovecot-2.2.33.2/src/doveadm/dsync/dsync-mailbox.c dovecot-2.2.34/src/doveadm/dsync/dsync-mailbox.c --- dovecot-2.2.33.2/src/doveadm/dsync/dsync-mailbox.c 2017-06-23 13:18:28.000000000 +0200 +++ dovecot-2.2.34/src/doveadm/dsync/dsync-mailbox.c 2018-02-28 15:45:34.000000000 +0100 @@ -1,7 +1,9 @@ -/* Copyright (c) 2013-2017 Dovecot authors, see the included COPYING file */ +/* Copyright (c) 2013-2018 Dovecot authors, see the included COPYING file */ #include "lib.h" #include "istream.h" +#include "mail-storage-private.h" +#include "dsync-brain-private.h" #include "dsync-mailbox.h" void dsync_mailbox_attribute_dup(pool_t pool, @@ -20,3 +22,40 @@ dest_r->last_change = src->last_change; dest_r->modseq = src->modseq; } + +int dsync_mailbox_lock(struct dsync_brain *brain, struct mailbox *box, + struct file_lock **lock_r) +{ + const char *path, *error; + int ret; + + /* Make sure the mailbox is open - locking requires it */ + if (mailbox_open(box) < 0) { + i_error("Can't open mailbox %s: %s", mailbox_get_vname(box), + mailbox_get_last_internal_error(box, &brain->mail_error)); + return -1; + } + + ret = mailbox_get_path_to(box, MAILBOX_LIST_PATH_TYPE_INDEX, &path); + if (ret < 0) { + i_error("Can't get mailbox %s path: %s", mailbox_get_vname(box), + mailbox_get_last_internal_error(box, &brain->mail_error)); + return -1; + } + if (ret == 0) { + /* No index files - don't do any locking. In theory we still + could, but this lock is mainly meant to prevent replication + problems, and replication wouldn't work without indexes. */ + *lock_r = NULL; + return 0; + } + + if (mailbox_lock_file_create(box, DSYNC_MAILBOX_LOCK_FILENAME, + brain->mailbox_lock_timeout_secs, + lock_r, &error) <= 0) { + i_error("Failed to lock mailbox %s for dsyncing: %s", + box->vname, error); + return -1; + } + return 0; +}

2 2

Sieve and output variable for execute
by Adam Raszkiewicz 20 Sep '18

20 Sep '18

I'm trying to get blow Sieve filter to work require ["fileinto", "imap4flags", "mailbox", "body", "envelope", "vnd.dovecot.pipe", "variables", "vnd.dovecot.execute"]; if envelope :matches "To" "*@*" { set "recipient" "${0}"; set "user" "${1}"; set "recip_domain" "${2}"; } if envelope :matches "From" "*" { set "sender" "${0}"; } #Check if recipient is valid user if execute :output "valid_user" "user-verification" "${recipient}" { if string :matches "${valid_user}" "True" { if body :raw :contains ["message/notification"] { setflag "\\Seen"; fileinto :create "Notifications"; stop; } } } Where user-verification is an extprogram which calls API and verify user based on email address then returns boolean (as an output to the console). Everything works fine when I will remove if string :matches "${valid_user}" "True"statement other way it looks like is not recognizing valid_uservariable. When I pipe valid_user to some script just to capture value for that variable it throws an error: error: specified :args item `True?' is invalid. Why question mark was added to the variable in this case? Thoughts?

2 1

[Sieve] Matches on body content - looking for working example
by Adam Raszkiewicz 20 Sep '18

20 Sep '18

I have tried to do something like if body :content ["multipart"] :matches ["Original-Message-ID" “*”] { set "Original_Message_ID" "${0}"; } but instead getting Original Message ID I’m getting value from previous match which was if envelope :matches "From" "*" { set "sender" "${0}"; } Is there any example of working :matches matching-type with body? Thanks

3 3

Fatal: Support not compiled in for passdb driver 'pam'
by Evandro Holderbach 20 Sep '18

20 Sep '18

Hi Guys, Can anyone help me, I'm having trouble halting caching authentication for the PAM module. I follow this procedure: https://wiki.dovecot.org/PasswordDatabase/PAM I got this error Sep 20 10:05:58 pop3-login: Info: Disconnected: Auth process broken (disconnected before auth was ready, waited 0 secs): user=<>, rip=, lip=, session=<QmW2BU52TACsFBTt> Sep 20 10:06:00 auth: Fatal: Support not compiled in for passdb driver 'pam' Sep 20 10:06:00 master: Error: service(auth): command startup failed, throttling for 4 secs Sep 20 10:06:00 auth: Fatal: Support not compiled in for passdb driver 'pam' dovecot -n # 2.2.4: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-754.3.5.el6.x86_64 x86_64 CentOS release 6.10 (Final) ext4 auth_cache_negative_ttl = 1 days auth_cache_size = 10 M auth_cache_ttl = 1 days auth_verbose = yes disable_plaintext_auth = no instance_name = Mail Popper 1 listen = 172.20.20.222 login_greeting = Mail Popper 1 Ready mail_location = mbox:/var/empty:INBOX=/var/mail/%u:INDEX=MEMORY mail_privileged_group = mail 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 = session=yes cache_key=%n dovecot driver = pam } passdb { driver = shadow } protocols = pop3 ssl = no userdb { args = blocking=yes driver = passwd } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } Thank you -- Evandro

1 0

dovecot.index.pvt reset
by Chris 20 Sep '18

20 Sep '18

All, maybe that's a similar issue like the one mentioned in [1], nevertheless I started a new thread. Using public folders: location = maildir:/var/vmail/public/:LAYOUT=fs:INDEXPVT=%h/.public-indexes When deleting a public maildir in filesystem (rm -rf ...) and copying back from backup, it's older than the users' dovecot.index.pvt files. (%h is in another directory). Then the following error appears: Sep 19 07:27:00 mail1 dovecot: imap(dr): Error: /var/vmail/users/dr/.public-indexes/folder1/folder2/dovecot.index.pvt reset, view is now inconsistent Sometimes even a panic: Sep 19 07:27:00 mail1 dovecot: imap(dr): Panic: file mail-index-map.c: line 548 (mail_index_map_lookup _seq_range): assertion failed: (first_uid <= last_uid) When deleting such a maildir via IMAP or doveadm, the error isn't appearing. Is there anything else, one has to consider, when restoring public maildirs from rsync backup? TIA! Chris [1] 5e26fce3-5f9f-219e-55fb-48981027dca5(a)shift.agency

2 1

dovecot.index.pvt view is inconsistent
by collect＠shift.agency 20 Sep '18

20 Sep '18

Hi, we currently work on a fresh setup coming from 2.2.13 going to 2.3.2.1 (0719df592) (Debian Dovecot Repo). We make heavily use of Public Folder with Per-user \Seen flag and Subscription. namespace { type = public separator = / prefix = Verteiler/ location = maildir:/var/vmail/public/example.com/verteiler:SUBSCRIPTIONS=subscriptions… subscriptions = yes hidden = no list = children } With our current version 2.2.13 this setup works. With version 2.3.2.1 we experience errors in the logfile: Sep 8 23:12:27 mail dovecot: Error: imap(user(a)example.com)<11328><e6jPlGJ1IxBOXnhS>: /var/vmail/mailboxes/example.com/user/public/example.com/verteiler/.info/dovecot.index.pvt view is inconsistent dovecot.index.pvt.log is beeing created. We found some appearance of this issue in forums but without any sufficient solution. Is the information provided in this email enough? What else would be relevant? Thank you! Tobias

2 1

blacklistd support for dovecot
by Kurt Lidl 20 Sep '18

20 Sep '18

Greetings all! I ported the NetBSD blacklistd support into FreeBSD a while ago (FreeBSD 11.x timeframe). I also added support to several of the system daemons there, so they could all talk to a centralized daemon (blacklistd). One of the third party apps that I added support to was sendmail - that works pretty well. So I'm now finally turning my attention adding blacklistd support to dovecot (which is the imap daemon that I use). I did an implementation to an earlier version, and that worked OK, at least for non-encrypted access to the imap server. However, the encrypted access (TLS) doesn't work right. To authenticate a network connection, the daemon must pass the fd of the remote connection over a unix domain socket to the actual blacklistd daemon. The blacklistd daemon will then call getpeername() on the connection, so it can determine the remote connection endpoint, rather than just having to believe some made-up set of data that is passed to it from process on the local machine. Christos Zoulas' talk on blacklistd is here: https://www.youtube.com/watch?v=fuuf8G28mjs Anyhow -- the problem I've run into is that there doesn't seem to be any way to get access to the fd of the socket that holds the raw connection to the client when TLS encryption is active. It looks like the only connection I get is to the proxy process. Is there any guidance that someone can give with how to implement this? Thank you. -Kurt

2 1

[Sieve] How to retrieve part of message as a variable
by Adam Raszkiewicz 19 Sep '18

19 Sep '18

I need to retrieve some parts of a message which looks like Subject: Test message Message-Id: <2788db2f-b5c3-4b8c-881e-362c3df4f915(a)server.local> Mime-Version: 1.0 Content-Type: multipart/report; boundary="----=_Part_fba0c199dfcd4d60ae506b37a6320a84"; report-type=disposition-notification To: adam(a)test.local Date: Mon, 17 Sep 2018 16:21:45 -0400 (EDT) From: postmaster(a)server.local ------=_Part_fba0c199dfcd4d60ae506b37a6320a84 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit BTW, this is the correct notification ... it should be "failed" not "failure". ------=_Part_fba0c199dfcd4d60ae506b37a6320a84 Content-Type: message/notification Content-Transfer-Encoding: 7bit Final-Recipient: rfc822; eve(a)test.local Original-Message-ID: <06dbfc12-57a5-49bd-84bd-a24bc3ba1e42(a)fake.cernerasp> ------=_Part_fba0c199dfcd4d60ae506b37a6320a84— for an example I need to grab what is after “Final-Recipient: rfc822;” and “Original-Message-ID:” and store them as variables Thanks

1 0

Re: Auth process sometimes stop responding after upgrade
by Simone Lazzaris 19 Sep '18

19 Sep '18

In data martedì 18 settembre 2018 14:07:26 CEST, Aki Tuomi ha scritto: > If you are using systemd, create > /etc/systemd/system/dovecot.service.d/limits.conf and put > [Service]LimitCORE=infinity > > and run > systemctl daemon-reloadsystemctl restart dovecot Nope, I'm on a debian 7, without systemd. Anyway, I've resolved the issue: I had to set fs.suid_dumpable BEFORE starting dovecot. I've got a core dump, and here is the backtrace. Let me know if you want the core file. gdb) bt #0 0xb76e4428 in __kernel_vsyscall () #1 0xb74636c1 in raise () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #2 0xb7466af2 in abort () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #3 0xb76485ae in default_fatal_finish (type=<optimized out>, status=status@entry=0) at failures.c:201 #4 0xb7648641 in i_internal_fatal_handler (ctx=0xbf839cc0, format=0x805c274 "file %s: line %d (%s): assertion failed: (%s)", args=0xbf839ce4 "4\370\005\bI\004") at failures.c:670 #5 0xb75ce35e in i_panic (format=format@entry=0x805c274 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 #6 0x080574f7 in doveadm_connection_deinit (_conn=_conn@entry=0xbf839d60) at doveadm-connection.c:1097 #7 0x08057f03 in doveadm_connection_input (conn=0x0) at doveadm-connection.c:1051 #8 0xb76613db in io_loop_call_io (io=0x82fb780) at ioloop.c:600 #9 0xb7662e1e in io_loop_handler_run_internal (ioloop=ioloop@entry=0x82bd648) at ioloop-epoll.c:223 #10 0xb7661496 in io_loop_handler_run (ioloop=ioloop@entry=0x82bd648) at ioloop.c:649 #11 0xb7661658 in io_loop_run (ioloop=0x82bd648) at ioloop.c:624 #12 0xb75da45e in master_service_run (service=0x82bd578, callback=callback@entry=0x804d360 <client_connected>) at master-service.c:719 #13 0x0804cf5e in main (argc=1, argv=0x82bd300) at main.c:366 *Simone Lazzaris* *Qcom S.p.A.* simone.lazzaris(a)qcom.it[1] | www.qcom.it[2] * LinkedIn[3]* | *Facebook*[4] [5] -------- [1] mailto:simone.lazzaris@qcom.it [2] https://www.qcom.it [3] https://www.linkedin.com/company/qcom-spa [4] http://www.facebook.com/qcomspa [5] https://www.qcom.it/includes/email-banner.gif

3 8

HTTP DoveAdm API - Possible bug?
by Chris Malton 19 Sep '18

19 Sep '18

Hi all, It seems that setting userMask in the doveadm http api's "user" command to anything involving wildcards ?s or *s causes the API to fail. When using the API with a userMask set to the fully qualified email address, I get the expected fields back. From a python shell, with an asterisk causes the following behaviour (note that doveadm is a python module that wrappers the dovecot API into Python's requests module). >>> doveadm.do_query("http://[xxxx:xxxx:xxxx:xxxx::ffff]:24280", "API_KEY_HERE", [ ["user", { "userMask": ["*"] }, "c01"] ]) '[["doveadmResponse",,"c01"]]' If I run the same command with a valid mailbox in the userMask Field, I get the response I expect: >>> doveadm.do_query("http://[[xxxx:xxxx:xxxx:xxxx::ffff]:24280", "API_KEY_HERE", [ ["user", { "userMask": ["test(a)test.mydomain.com"] }, "c01"] ]) '[["doveadmResponse",{"test(a)test.mydomain.com":{"uid":"x","gid":"y","home":"/mail/test.mydomain.com/users/test","mail":"maildir:/mail/test.mydomain.com/users/test/Maildir/:INDEX=/indexes/test.myd…","nice":"10"}},"c01"]]' Chatting with people in #dovecot revealed similar behaviour elsewhere so it doesn't appear to be just me. I've also selectively edited the above to avoid leaking data. We're running on the following # 2.2.34 (874deae): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.22 (22940fb7) # OS: Linux 4.9.0-7-amd64 x86_64 Debian 9.5 ext4 If you need a full copy of the config, please let me know and I'll talk to my client, however, I don't think this is config related. Thanks in advance. Regards, Chris Malton -- Delta V Technologies Limited 03333 402 402 www.deltav-tech.co.uk Office: 17 Elm Close, Southampton, SO16 7DT Company No. 11006104 Registered in England and Wales

2 2

Re: dovecot (2.2.13) panic on imap-login from iphone se
by Andre Hoepner - i.based: Systemhaus GmbH + Co. KG 18 Sep '18

18 Sep '18

here is our config: (doveconf -n) # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.6.11-gentoo x86_64 Gentoo Base System release 2.2 auth_cache_size = 10 M auth_mechanisms = plain login default_client_limit = 1024 default_process_limit = 256 hostname = HOSTNAME imap_client_workarounds = delay-newmail tb-extra-mailbox-sep info_log_path = /var/log/dovecot.log listen = * mail_location = maildir:~/Maildir mail_plugins = quota acl zlib mail_privileged_group = mail 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 duplicate namespace { list = yes location = maildir:/home/shared/Maildir:CONTROL=~/Maildir/control/shared:INDEX=~/Maildir/index/shared prefix = Shared separator = / subscriptions = no type = public } 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 = separator = / type = private } passdb { args = * driver = pam } passdb { driver = passwd } passdb { driver = shadow } plugin { acl = vfile autocreate = Trash autocreate2 = Junk autocreate3 = Sent autocreate4 = Drafts quota = maildir:User quota quota_rule = *:storage=3800M quota_rule2 = Trash:storage=+500M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=85%% quota-warning 85 %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = ADMIN-EMAIL protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service imap-login { inet_listener imaps { ssl = yes } } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-warning { executable = script /usr/bin/dovecot-quota-warning.sh user = dovecot } ssl_ca = </etc/ssl/ssl.pem ssl_cert = </etc/ssl/ssl.crt ssl_key = </etc/ssl/ssl.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } protocol lmtp { mail_fsync = optimized } protocol lda { mail_fsync = optimized mail_plugins = sieve quota } protocol imap { mail_plugins = quota acl zlib imap_quota imap_acl } ############## # doveadm user USERNAME field value uid 950 gid 501 home /home/USERNAME mail maildir:~/Maildir system_groups_user USERNAME ############### Hope this helps. Andre Am 18.09.2018 um 18:49 schrieb Aki Tuomi: > Please keep replies on list. Can you provide doveconf -n and output of > doveadm user victim ? > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: "Andre Hoepner - i.based: Systemhaus GmbH + Co. KG" > <a.hoepner(a)ibased.de> > Date: 18/09/2018 19:13 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi> > Subject: Re: dovecot (2.2.13) panic on imap-login from iphone se > > > Sorry. I think upgrade is not possible because it is a very outdated > gentoo installation and im not abe to compile without compiling the > whole source stack of glibc and all other dependencies. > > It is planned to replace the server in the next 8 weeks with a new > system, but this 8 weeks the server must do the work. > > Andre > > > Am 18.09.2018 um 17:09 schrieb Aki Tuomi: >> Can you upgrade to 2.2.36 or 2.3.2.1 and reproduce this issue? 2.2.13 is >> quite old. >> >> >> >> --- >> Aki Tuomi >> Dovecot oy >> >> -------- Original message -------- >> From: "Andre Hoepner - i.based: Systemhaus GmbH + Co. KG" >> <a.hoepner(a)ibased.de> >> Date: 18/09/2018 16:17 (GMT+02:00) >> To: dovecot(a)dovecot.org >> Subject: dovecot (2.2.13) panic on imap-login from iphone se >> >> >> Hi to all, >> >> we have trouble with one user account, when using imap-login with iphone >> se. The user can login and use the account from webmail (roundcube) and >> from thunderbird without any errors and without any restrictions. >> >> But if we use the account on an iphone se and try to use imap based >> emails, there comes the following error (look at the end of the mail). >> I have no idea, what for an error it is. Same account on an iphone 5 >> works without any trouble. >> >> We have delete the homedir of the user and also recreated the user with >> new uid and new password. Webmail and thunderbird are fine, but if we >> use the iphone se we got this error. >> >> Are there any known issues with this combination? >> Thanks for your help. >> >> best regardings >> Andre Hoepner >> >> ---8<---- >> # HOST = hostname of the system; USER = username that gets this error >> >> Sep 18 12:46:02 HOST dovecot: imap(USER): Panic: file mailbox-list.c: >> line 1125 >> (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, >> path, strlen(root_dir)) == 0) >> >> Sep 18 12:46:02 HOST dovecot: imap(USER): Error: Raw backtrace: >> /usr/lib64/dovecot/libdovecot.so.0(+0x6552e) [0x7f4333e0452e] >> -> /usr/lib64/dovecot/libdovecot.so.0(+0x65596) [0x7f4333e04596] >> -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4333dc423e] >> -> >> > /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_try_mkdir_root+0x469) >> [0x7f43340d3a5a] >> -> >> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_mkdir_root+0x15) >> [0x7f43340d3ac0] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x570cb) [0x7f43340c40cb] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_set_deleted+0x11a) >> [0x7f43340c465c] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x563d5) [0x7f43340c33d5] >> -> >> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_uidlist_sync_init+0x33) >> [0x7f43340c34f7] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x517ac) [0x7f43340be7ac] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x51c59) [0x7f43340bec59] >> -> >> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xb5) >> [0x7f43340bef35] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x2b) >> [0x7f43340cc405] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) >> [0x7f43340cc4f1] >> -> >> /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x2f) >> [0x7f43340f1f6a] >> -> /usr/lib64/dovecot/lib01_acl_plugin.so(+0xdff9) [0x7f43335ffff9] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) >> [0x7f43340cd36c] >> -> dovecot/imap(imap_status_get+0x5f) [0x41dc1d] >> -> dovecot/imap() [0x410cf9] >> -> dovecot/imap(cmd_list_full+0x49d) [0x411297] >> -> dovecot/imap(command_exec+0x37) [0x417f20] >> -> dovecot/imap() [0x4170c9] >> -> dovecot/imap() [0x417174] >> -> dovecot/imap(client_handle_input+0x106) [0x417400] >> -> dovecot/imap(client_input+0x72) [0x417768] >> -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x3f) > [0x7f4333e13536] >> -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd1) >> [0x7f4333e142e6] >> -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) >> [0x7f4333e13598] >> >> Sep 18 12:46:02 HOST dovecot: imap(USER): Fatal: master: service(imap): >> child 32253 >> killed with signal 6 (core dumps disabled) >> ---8<---- > > -- > > Sie möchten wissen, warum wir die Richtigen für Ihr > Unternehmen sind? Lesen Sie hier ... > http://www.11-gute-gruende.de > > > i.based: Systemhaus GmbH & Co. KG > Langenstrasse 38 > 18439 Stralsund > Deutschland > > http://www.ibased.de > a.hoepner(a)ibased.de > > fon: 03831-28944-0 > fax: 03831-28944-29 > > Registergericht: > HRA 2072 Amtsgericht Stralsund > > Geschäftsführung: > i.based: Systemhaus Verwaltungs GmbH > > Steuer-Nr: 082/187/38401 > USt.-ID: DE254322988 > > persönlich haftend: > i.based: Systemhaus Verwaltungs- > GmbH, Stralsund > HRB 7189 Amtsgericht Stralsund > > vertreten durch: > André Höpner, Mathias Waldeck > > https://www.linkedin.com/in/andre-hoepner/ > https://www.xing.com/hp/andre_hoepner -- Sie möchten wissen, warum wir die Richtigen für Ihr Unternehmen sind? Lesen Sie hier ... http://www.11-gute-gruende.de i.based: Systemhaus GmbH & Co. KG Langenstrasse 38 18439 Stralsund Deutschland http://www.ibased.de a.hoepner(a)ibased.de fon: 03831-28944-0 fax: 03831-28944-29 Registergericht: HRA 2072 Amtsgericht Stralsund Geschäftsführung: i.based: Systemhaus Verwaltungs GmbH Steuer-Nr: 082/187/38401 USt.-ID: DE254322988 persönlich haftend: i.based: Systemhaus Verwaltungs- GmbH, Stralsund HRB 7189 Amtsgericht Stralsund vertreten durch: André Höpner, Mathias Waldeck https://www.linkedin.com/in/andre-hoepner/ https://www.xing.com/hp/andre_hoepner

2 1

Re: dovecot (2.2.13) panic on imap-login from iphone se
by Aki Tuomi 18 Sep '18

18 Sep '18

Please keep replies on list. Can you provide doveconf -n and output of doveadm user victim ? ---Aki TuomiDovecot oy -------- Original message --------From: "Andre Hoepner - i.based: Systemhaus GmbH + Co. KG" <a.hoepner(a)ibased.de> Date: 18/09/2018 19:13 (GMT+02:00) To: Aki Tuomi <aki.tuomi(a)dovecot.fi> Subject: Re: dovecot (2.2.13) panic on imap-login from iphone se Sorry. I think upgrade is not possible because it is a very outdated gentoo installation and im not abe to compile without compiling the whole source stack of glibc and all other dependencies. It is planned to replace the server in the next 8 weeks with a new system, but this 8 weeks the server must do the work. Andre Am 18.09.2018 um 17:09 schrieb Aki Tuomi: > Can you upgrade to 2.2.36 or 2.3.2.1 and reproduce this issue? 2.2.13 is > quite old. > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: "Andre Hoepner - i.based: Systemhaus GmbH + Co. KG" > <a.hoepner(a)ibased.de> > Date: 18/09/2018 16:17 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: dovecot (2.2.13) panic on imap-login from iphone se > > > Hi to all, > > we have trouble with one user account, when using imap-login with iphone > se. The user can login and use the account from webmail (roundcube) and > from thunderbird without any errors and without any restrictions. > > But if we use the account on an iphone se and try to use imap based > emails, there comes the following error (look at the end of the mail). > I have no idea, what for an error it is. Same account on an iphone 5 > works without any trouble. > > We have delete the homedir of the user and also recreated the user with > new uid and new password. Webmail and thunderbird are fine, but if we > use the iphone se we got this error. > > Are there any known issues with this combination? > Thanks for your help. > > best regardings > Andre Hoepner > > ---8<---- > # HOST = hostname of the system; USER = username that gets this error > > Sep 18 12:46:02 HOST dovecot: imap(USER): Panic: file mailbox-list.c: > line 1125 > (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, > path, strlen(root_dir)) == 0) > > Sep 18 12:46:02 HOST dovecot: imap(USER): Error: Raw backtrace: > /usr/lib64/dovecot/libdovecot.so.0(+0x6552e) [0x7f4333e0452e] > -> /usr/lib64/dovecot/libdovecot.so.0(+0x65596) [0x7f4333e04596] > -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4333dc423e] > -> > /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_try_mkdir_root+0x469) > [0x7f43340d3a5a] > -> > /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_mkdir_root+0x15) > [0x7f43340d3ac0] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x570cb) [0x7f43340c40cb] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_set_deleted+0x11a) > [0x7f43340c465c] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x563d5) [0x7f43340c33d5] > -> > /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_uidlist_sync_init+0x33) > [0x7f43340c34f7] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x517ac) [0x7f43340be7ac] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x51c59) [0x7f43340bec59] > -> > /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xb5) > [0x7f43340bef35] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x2b) > [0x7f43340cc405] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) > [0x7f43340cc4f1] > -> > /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x2f) > [0x7f43340f1f6a] > -> /usr/lib64/dovecot/lib01_acl_plugin.so(+0xdff9) [0x7f43335ffff9] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) > [0x7f43340cd36c] > -> dovecot/imap(imap_status_get+0x5f) [0x41dc1d] > -> dovecot/imap() [0x410cf9] > -> dovecot/imap(cmd_list_full+0x49d) [0x411297] > -> dovecot/imap(command_exec+0x37) [0x417f20] > -> dovecot/imap() [0x4170c9] > -> dovecot/imap() [0x417174] > -> dovecot/imap(client_handle_input+0x106) [0x417400] > -> dovecot/imap(client_input+0x72) [0x417768] > -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x3f) [0x7f4333e13536] > -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd1) > [0x7f4333e142e6] > -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) > [0x7f4333e13598] > > Sep 18 12:46:02 HOST dovecot: imap(USER): Fatal: master: service(imap): > child 32253 > killed with signal 6 (core dumps disabled) > ---8<---- -- Sie möchten wissen, warum wir die Richtigen für Ihr Unternehmen sind? Lesen Sie hier ... http://www.11-gute-gruende.de i.based: Systemhaus GmbH & Co. KG Langenstrasse 38 18439 Stralsund Deutschland http://www.ibased.de a.hoepner(a)ibased.de fon: 03831-28944-0 fax: 03831-28944-29 Registergericht: HRA 2072 Amtsgericht Stralsund Geschäftsführung: i.based: Systemhaus Verwaltungs GmbH Steuer-Nr: 082/187/38401 USt.-ID: DE254322988 persönlich haftend: i.based: Systemhaus Verwaltungs- GmbH, Stralsund HRB 7189 Amtsgericht Stralsund vertreten durch: André Höpner, Mathias Waldeck https://www.linkedin.com/in/andre-hoepner/ https://www.xing.com/hp/andre_hoepner

1 0

dovecot (2.2.13) panic on imap-login from iphone se
by Andre Hoepner - i.based: Systemhaus GmbH + Co. KG 18 Sep '18

18 Sep '18

Hi to all, we have trouble with one user account, when using imap-login with iphone se. The user can login and use the account from webmail (roundcube) and from thunderbird without any errors and without any restrictions. But if we use the account on an iphone se and try to use imap based emails, there comes the following error (look at the end of the mail). I have no idea, what for an error it is. Same account on an iphone 5 works without any trouble. We have delete the homedir of the user and also recreated the user with new uid and new password. Webmail and thunderbird are fine, but if we use the iphone se we got this error. Are there any known issues with this combination? Thanks for your help. best regardings Andre Hoepner ---8<---- # HOST = hostname of the system; USER = username that gets this error Sep 18 12:46:02 HOST dovecot: imap(USER): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Sep 18 12:46:02 HOST dovecot: imap(USER): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x6552e) [0x7f4333e0452e] -> /usr/lib64/dovecot/libdovecot.so.0(+0x65596) [0x7f4333e04596] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4333dc423e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_try_mkdir_root+0x469) [0x7f43340d3a5a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_mkdir_root+0x15) [0x7f43340d3ac0] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x570cb) [0x7f43340c40cb] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_set_deleted+0x11a) [0x7f43340c465c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x563d5) [0x7f43340c33d5] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_uidlist_sync_init+0x33) [0x7f43340c34f7] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x517ac) [0x7f43340be7ac] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x51c59) [0x7f43340bec59] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xb5) [0x7f43340bef35] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x2b) [0x7f43340cc405] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7f43340cc4f1] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x2f) [0x7f43340f1f6a] -> /usr/lib64/dovecot/lib01_acl_plugin.so(+0xdff9) [0x7f43335ffff9] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7f43340cd36c] -> dovecot/imap(imap_status_get+0x5f) [0x41dc1d] -> dovecot/imap() [0x410cf9] -> dovecot/imap(cmd_list_full+0x49d) [0x411297] -> dovecot/imap(command_exec+0x37) [0x417f20] -> dovecot/imap() [0x4170c9] -> dovecot/imap() [0x417174] -> dovecot/imap(client_handle_input+0x106) [0x417400] -> dovecot/imap(client_input+0x72) [0x417768] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x3f) [0x7f4333e13536] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd1) [0x7f4333e142e6] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7f4333e13598] Sep 18 12:46:02 HOST dovecot: imap(USER): Fatal: master: service(imap): child 32253 killed with signal 6 (core dumps disabled) ---8<----

2 1

Re: Auth process sometimes stop responding after upgrade
by Timo Sirainen 18 Sep '18

18 Sep '18

On 8 Sep 2018, at 15.18, Simone Lazzaris <simone.lazzaris(a)qcom.it> wrote: > > Timo, unfortunately the patch doesn't compile; I've moved the declaration of > "conn" one line up to make it work. Oops, I guess I was too much in a hurry to even compile it. Here's a new patch that compiles and passes our director CI tests.

4 9

Using both starttls and ssl in passdb on proxy results in timeouts
by Filias Heidt 18 Sep '18

18 Sep '18

Hi List, I have a dovecot which proxies to different backends depending on an entry in a mysql-database. The mysql-query sets ‚ssl‘ to ‚any-cert‘ and this works fine. But this causes me a problem: sieve-backends only support STARTTLS and if I set ‚ssl‘ to ‚any-cert‘ (or yes), it will attempt a TLS-connection to the sieve-backends, which fails. My attempt was to alter the query to include %{real_lport} and return ‚ssl=no‘ and ‚starttls=any-cert‘ if the port matches the sieve-port. It works as expected in that it returns the correct values and proxies to the correct backend. However it seems that TLS is no longer working and I get timeouts from the backends. Debug: client passdb out: OK 1 user=someuser(a)example.com proxy proxy_nopipelining=y host=backend1.example.com nodelay=y nologin starttls=no ssl=any-cert hostip=so.me.i.p pass=<hidden> results in: Sep 17 11:08:47 imapproxy1 dovecot: imap-login: Error: proxy(someuser(a)example.com): Login for so.me.i.p:993 timed out in state=/none (after 30 secs, local=lo.cal.i.p:60524): user=<someuser(a)example.com>, method=PLAIN, rip=re.mo.te.ip, lip=lo.cal.i.p, TLS, session=<OySXgw12auwgARYIAAYABwAAAAAAAwAU> My query looks like this: password_query = SELECT host from proxy_domain, NULL as password, 'y' as nopassword, 'y' as proxy, NULL as destuser, 'y' as proxy_nopipelining, 'y' as nodelay, 'y' as nologin, IF(%{real_lport}=4190, 'any-cert', 'no') as 'starttls', IF(%{real_lport}<>4190, 'any-cert', 'no') as 'ssl‘; As soon as I remove the starttls-part and the passdb only returns ssl=any-cert (without starttls=no) it works flawlessly. Is it possible that I am attacking the problem the wrong way? Or is it not possible to set both starttls and ssl to some values in passdb and enable/disable them as needed? Thanks for any input :) Cheers, Filias

2 2

How to send mail to mailbox with disabled domain?
by Kai Schaetzl 17 Sep '18

17 Sep '18

Given the following: mailboxes: user1(a)example1.com user2(a)example1.com user3(a)example1.com etc. aliases: whatever(a)example1.com -> user1(a)example1.com whatever(a)example2.com -> user1(a)example1.com whatever(a)example3.com -> user1(a)example1.com Now the problem: example1.com MX goes elsewhere (doesn't point to this server anymore). Domains example2.com and example3.com still point to that server and should be able to accept mail. I have to disable mail acceptance for example1.com. If not, mail sent *from* that server (e.g. from a web form) to that domain will not leave the server. However, if I disable example1.com for mail dovecot lmtp will not deliver mail to this mail box anymore, although the mailbox still exists. How can I solve this? Is there a way of solving this, but keeping the domain example1.com in the name for these mailboxes? Or is there a way to tell dovecot to ignore domains for mailbox names? e.g. deliver to "user1"? (All user localparts are unique.) Thanks for any hints. Kai

4 6

Re: Proxy secured incoming POP3/IMAP4 to unsecure backend?
by Alexander Chekalin 17 Sep '18

17 Sep '18

Thank you! Ok, so I can omit ssl=no and startssl=no, and this results in default settings for ssl which is 'off'? Or the defaults are 'on' anyway? Can I somehow specify ports on remote hosts that proxy will use to connect to? Like (just image): 'proxy host_imap=10.1.1.1:143 host_pop=10.1.1.1:110' or somehow? On Mon, Sep 17, 2018 at 4:33 PM Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > Due to certain design issues, the ssl=no is actually same as ssl=yes, same > goes for starttls=no. So there is no support actually for "ssl=no" at this > moment. > > Aki > > > On 17 September 2018 at 15:32 Alexander Chekalin < > alexander.chekalin(a)gmail.com> wrote: > > > > > > Surely. > > > > Here it is: > > > > # doveadm auth user(a)domain.com > > Password: > > passdb: chekalin_krg(a)ascon.ru auth succeeded > > extra fields: > > user=user(a)domain.com > > proxy > > host=10.10.14.131 > > ssl=no > > startssl=no > > source_ip=10.10.14.2 > > proxy > > proxy > > pass=password > > > > Two "proxy" are from two "proxy" and "proxy=yes" settings passed from > > passdb. > > > > On Mon, Sep 17, 2018 at 3:03 PM Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > > > > > Can you provide output of > > > > > > doveadm auth test some-user > > > Aki > > > > > > On 17.09.2018 14:58, Alexander Chekalin wrote: > > > > > > Dear Aki, > > > > > > we keep our users in LDAP so I when I even return 'proxy > host=backend_ip > > > tls=no' it won't use non-TLS connection. The same is when I remove > 'tls=no' > > > part. May there be any extra things I need to pass when I use LDAP? > > > > > > On Mon, Sep 17, 2018 at 2:07 PM Aki Tuomi <aki.tuomi(a)dovecot.fi> > wrote: > > > > > >> > > >> > > >> On 17.09.2018 13:59, Alexander Chekalin wrote: > > >> > Hi, > > >> > > > >> > I try to set up dovecot as a proxy server, to proxy requests to > > >> > several dovecot-based backend servers. I wand external clients who > > >> > connects to this proxy Dovecot to use TLS (this is easy to set up) > > >> > while want to have unsecured (plain IMAP/POP) connections to > backends. > > >> > > > >> > You see, links to backends are over LAN so no TLS needed, and these > > >> > backends are poor old machines (with old Docecots like 2.0.6) this > is > > >> > why I don't want to use TLS to acces backends. > > >> > > > >> > But as I did the test setup I can see proxy Dovecot uses TLS to > > >> > connect to backends. Is there any way I can specify this aspect of > > >> > Dovecot proxy? > > >> > > > >> > Please advice! > > >> > > > >> > Yours, > > >> > Alexander > > >> > > >> Dovecot does not use TLS/SSL when connecting to a backend server by > > >> default, you are probably specifying this in your proxy config or > > >> password database. > > >> > > >> Aki > > >> > > > > > > >

2 5

Proxy secured incoming POP3/IMAP4 to unsecure backend?
by Alexander Chekalin 17 Sep '18

17 Sep '18

Hi, I try to set up dovecot as a proxy server, to proxy requests to several dovecot-based backend servers. I wand external clients who connects to this proxy Dovecot to use TLS (this is easy to set up) while want to have unsecured (plain IMAP/POP) connections to backends. You see, links to backends are over LAN so no TLS needed, and these backends are poor old machines (with old Docecots like 2.0.6) this is why I don't want to use TLS to acces backends. But as I did the test setup I can see proxy Dovecot uses TLS to connect to backends. Is there any way I can specify this aspect of Dovecot proxy? Please advice! Yours, Alexander

3 2

Problem with envelope from in Pigeonhole after upgrade
by David Dodd 17 Sep '18

17 Sep '18

On our FreeBSD 11.2 servers, we recently upgraded from: dovecot2-2.2.26.0_1 dovecot-pigeonhole-0.4.16_1 to: dovecot-2.3.2.1 dovecot-pigeonhole-0.5.2_3 Prior to the upgrade the envelope sender was as expected. After the upgrade, the envelope sender for a user with a sieve script configured is now being set to: >From MAILER-DAEMON Tue Sep 04 13:31:39 2018 The same user without a sieve script in place gets: >From someone(a)gmail.com Tue Sep 04 11:06:04 2018 This happens when manually testing by directly executing: /usr/local/libexec/dovecot/dovecot-lda -d dgdtst -f someone(a)gmail.com It happens with an empty sieve script i.e. just using the implicit keep functionality. I have groped around looking for a configuration setting that might fix the behaviour but nothing I have tried helps. Can anyone suggest what to set to correct the problem ? -- Dave

2 7

Quotas not working with roundcube
by Mik J 17 Sep '18

17 Sep '18

Hello, I'm trying to have quotas working with roundcube. When I'm logged into roundcube I see 0% quota which seems to correspond to disabled. However I did everything that I could to enable quotas https://wiki.dovecot.org/Quota # doveconf -n auth_mechanisms = cram-md5 loginauth_verbose = yes debug_log_path = /tmp/dovecot.log first_valid_uid = 1000 log_path = /var/log/dovecot.log mail_gid = vmail mail_location = maildir:/home/mail/%d/%n/Maildir mail_plugins = notify replication quota mail_uid = vmail mbox_write_locks = fcntl mmap_disable = yes 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 { driver = bsdauth } passdb { args = /etc/dovecot/dovecot.passwd driver = passwd-file } plugin { quota_grace = 10%% quota_rule = *:storage=2G quota_rule2 = Trash:storage=+200M quota_rule3 = SPAM:ignore quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u } ssl_ca = /etc/ssl/certs/CA_Intermed_Lets_Encrypt.crt ssl_cert = </etc/ssl/certs/imap.mydomain.org.crt ssl_key = # hidden, use -P to show it ssl_key_password = # hidden, use -P to show it userdb { driver = passwd } userdb { driver = static } protocol lda { mail_plugins = notify replication quota } protocol imap { mail_plugins = notify replication quota imap_quota }

3 5

Dsync deleting mailboxes due to duplicate UIDs
by Andreas Thienemann 16 Sep '18

16 Sep '18

Hi, I am attempting to migrate a mailspool from a cyrus server to a dovecot server using the dsync backup approach as described in the wiki at <https://wiki.dovecot.org/Migration/Dsync>. The first attempt works great. Everything copies over and a quick glance over the spool looks good. Running doveadm backup again though results in the following error: dsync(eggs): Warning: Deleting mailbox 'INBOX.MailRestore': UID=39 already exists locally for a different mail: Headers hashes don't match (18d567fc7e258a67e47b629c8bb16500 vs 230354b2d5cad21ebbb4a7440b977adb) As promised, the folder MailRestore is gone after dsync finishes. Running doveadm backup again for the third time copies the folder again. Running it a fourth time gives the same error and the folder is gone. Trying to figure this out I initially had a few mails where the header hashes were 68b329da9893e34099c7d8ad5cb9c940, the md5sum of an empty string. Turns out that the source mailspool had a few broken emails and cleaning these out fixed most my issues. But in this case, I am stumped. UID 39 on the server is a valid mail with correct headers and everything. Is there a good way of identifying the two mails that seem to clash? I had a quick look at the dovecot code but did not see how the header_stream gets hashed into the hdr_hash used for comparing mails. Thanks, Andreas

3 5

dovecot_deleted_to_trash no longer compiles with dovecot 2.3.2.1
by Robert S 16 Sep '18

16 Sep '18

I have just upgraded to the latest version of dovecot (Gentoo amd64). When I try to compile the dovecot_deleted_to_trash plugin it won't compile. Is this plugin going to be updated (from https://github.com/lexbrugman/dovecot_deleted_to_trash - same error from https://github.com/NethServer/dovecot-deleted-to-trash)? # make cc \ -fPIC -shared -Wall \ -I/usr/include/dovecot \ -I/usr/include/dovecot/src \ -I/usr/include/dovecot/src/lib \ -I/usr/include/dovecot/src/lib-storage \ -I/usr/include/dovecot/src/lib-mail \ -I/usr/include/dovecot/src/lib-imap \ -I/usr/include/dovecot/src/lib-index \ -DHAVE_CONFIG_H \ src/deleted-to-trash-plugin.c -o lib_deleted_to_trash_plugin.so src/deleted-to-trash-plugin.c: In function ‘copy_deleted_mail_to_trash’: src/deleted-to-trash-plugin.c:117:16: error: too few arguments to function ‘mail box_transaction_begin’ dest_trans = mailbox_transaction_begin(trash_box, MAILBOX_TRANSACTION_FLAG_EX TERNAL); ^~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /usr/include/dovecot/mail-storage-private.h:7:0, from src/deleted-to-trash-plugin.h:5, from src/deleted-to-trash-plugin.c:4: /usr/include/dovecot/mail-storage.h:656:1: note: declared here mailbox_transaction_begin(struct mailbox *box, ^~~~~~~~~~~~~~~~~~~~~~~~~ make: *** [Makefile:32: lib_deleted_to_trash_plugin.so] Error 1 Some further info: # dovecot -n # 2.3.2.1 (0719df592): /etc/dovecot/dovecot.conf # OS: Linux 4.14.8-gentoo-r1 x86_64 Gentoo Base System release 2.4.1 # Hostname: basement-vm.schmidli.com.au doveconf: Warning: please set ssl_dh=</etc/dovecot/dh.pem doveconf: Warning: You can generate it with: dd if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der > /etc/dovecot/dh.pem dict { expire = db:/var/lib/dovecot/expire.db } disable_plaintext_auth = no listen = * mail_location = maildir:~/.maildir mail_plugins = deleted_to_trash mailbox_alias 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 = * driver = pam } plugin { deleted_to_trash_folder = Trash expire = Trash 7 Spam 30 expire_dict = proxy::expire

1 0

Re: auth_policy in a non-authenticating proxy chain
by Peter Mogensen 15 Sep '18

15 Sep '18

On 09/15/2018 10:41 AM, Aki Tuomi wrote: > Point of sending the success ones is to maintain whitelist as well as > blacklist so you know which ones you should not tarpit anymore. We > know it does scale as we have very large deployments using the whole > three request per login model. > > "Success" in a proxy which is not it self authenticating is only whether it know where to proxy the requested username to. I'm not sure whether this would be input to a whitelist. I'm not doubting that 3 req/login scales. /Peter

2 1

auth_policy in a non-authenticating proxy chain
by Peter Mogensen 15 Sep '18

15 Sep '18

Hi, I was looking into the new Authentication Policy feature: https://wiki2.dovecot.org/Authentication/Policy I had kinda hoped that I would be able to enfore this in a proxy running in front of several backends. This proxy does not authenticate. It use "nopassword". But I realize that the "succes" reported in the final authpolicy req. (command=report) is not what is actaully happening on the IMAP protocol level, but rather the result of the passdb chain in the proxy. (I should probably have predicted this, it's kinda reasonable). However... since the proxy use "nopassword", ALL passdb lookups result in "success", so the proxy will never report an authentication failure to the authpolicy server. This, of course, forces me to do the authpolicy check on the backend with a shared state, but It would still have been nice to have the proxy being able to do the first "command=allow" req. and reject attemps already there even though the backend does "command=report". /Peter

3 4

encryption issue in outlook 2016
by ChandranManikandan 14 Sep '18

14 Sep '18

Hi Friends, Am facing the serious issue in outlook 2016. When i tried to configure the email in outlook 2016 it's asking encrypted connection and checked automatically and if not available then it showing unencrypted. but finally unable to configure the email account in outlook 2016 and not permitted. Do i need to update any in the server. Am using COS 6 32 and 64 bit servers with qmailtoaster + dovecot 2.2.7. Currently configured in outlook 2010 it's working without any issue. And always showing in outlook 2010 when i open the account. Do you want to continue yes or no for the certification. Because i have configured in advanced selected Auto in outlook 2010. If i select none it was not working the email. Anyone facing the same issue. How do i rectify it in outlook 2016 and how can i stop the certificate warning message in outlook. If possible to use without encryption and what's the configuration. Please advice and let me know the process. Am seriously cannot access the email from outlook. I have attached the message while open outlook. If i click yes then it will open Is the certificate expired. How do renew it or reload it with the fresh certificate. -- *Thanks & Best Regards,Manikandan.C*

4 4

Occasional crash in db-auth.c (Valgrind: Invalid read of size 4 et al.), Dovecot 2.2.27+
by Jonas Wielicki 14 Sep '18

14 Sep '18

Dear list, We are encountering troubles with dovecot using LDAP userdbs on Debian stretch (but if I’m reading valgrind correctly, we can reproduce this with vanilla dovecot master). Minimal reproducer below. While testing an upgrade to Debian stretch (dovecot-core=1:2.2.27-3+deb9u1), auth-worker has stopped working. We are using two LDAP user databases; one which is iterable, and one which is not (for reasons; I think this is not relevant; if it is, we’re happy to elaborate). The issue seems to be present in any LDAP userdb iteration handling, but it only seems to cause a crash in certain conditions which seem to be reproducibly caused by our setup for some reason. We’re seeing one of two errors. Variant A: Jan 27 13:40:05 up2 dovecot: auth-worker: Error: *** Error in `dovecot/auth': free(): corrupted unsorted chunks: 0x000056553f0fcfa0 *** Jan 27 13:40:05 up2 dovecot: auth-worker: Error: ======= Backtrace: ========= Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/ libc.so.6(+0x70bcb)[0x7f78426adbcb] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/ libc.so.6(+0x76f96)[0x7f78426b3f96] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/ libc.so.6(+0x777de)[0x7f78426b47de] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/modules/ auth/libauthdb_ldap.so(+0x5bde)[0x7f7842008bde] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(io_loop_call_io+0x52)[0x7f78430cfdd2] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(io_loop_handler_run_internal+0x109)[0x7f78430d1409] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(io_loop_handler_run+0x3c)[0x7f78430cfe6c] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(io_loop_run+0x38)[0x7f78430d0018] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(master_service_run+0x13)[0x7f7843057e93] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: dovecot/auth(main+0x398) [0x56553da45f98] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/ libc.so.6(__libc_start_main+0xf1)[0x7f784265d2b1] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: dovecot/auth(_start+0x2a) [0x56553da461aa] Variant B: Jan 27 13:06:56 up2 dovecot: auth-worker(27495): Panic: file db-ldap.c: line 840 (db_ldap_result_unref): assertion failed: (res->refcount > 0) Jan 27 13:06:56 up2 dovecot: auth-worker(27495): Error: Raw backtrace: /usr/ lib/dovecot/libdovecot.so.0(+0x95272) [0x7f027a4fc272] -> /usr/lib/dovecot/ libdovecot.so.0(+0x9536d) [0x7f027a4fc36d] -> /usr/lib/dovecot/libdovecot.so. 0(i_fatal+0) [0x7f027a492951] -> /usr/lib/dovecot/modules/auth/ libauthdb_ldap.so(+0x3868) [0x7f0279447868] -> /usr/lib/dovecot/modules/auth/ libauthdb_ldap.so(+0x5d7c) [0x7f0279449d7c] -> /usr/lib/dovecot/libdovecot.so. 0(io_loop_call_io+0x52) [0x7f027a510dd2] -> /usr/lib/dovecot/libdovecot.so. 0(io_loop_handler_run_internal+0x109) [0x7f027a512409] -> /usr/lib/dovecot/ libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f027a510e6c] -> /usr/lib/ dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f027a511018] -> /usr/lib/ dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f027a498e93] -> dovecot/ auth(main+0x398) [0x55b981cd2f98] -> /lib/x86_64-linux-gnu/libc.so. 6(__libc_start_main+0xf1) [0x7f0279a9e2b1] -> dovecot/auth(_start+0x2a) [0x55b981cd31aa] When running auth-worker within valgrind, we get more information (valgrind extract from mail.log attached for two versions of dovecot). We have attached mail.log contents for the respective valgrind runs. This seems to affect at least 2.2.27 onwards. We can reproduce the crash with our production data 100% of the time. The valgrind error is present even with very minimal setups (see below). Unfortunately, I haven’t been able so far to create an LDAP database which produces the crash as reliable as our production database does (which we cannot share for obvious reasons). Minimal Reproducer of Valgrind error: - Install dovecot 2.2.27 from debian stretch, or compile from master. - Install valgrind - In conf.d/10-auth.conf, disable auth-system.conf.ext - In conf.d/10-auth.conf, enable auth-ldap.conf.ext - Set contents of dovecot-ldap.conf.ext to: hosts = localhost base = dc=nodomain - In conf.d/10-master.conf, in section "service auth-worker", set executable = /usr/bin/valgrind /usr/lib/dovecot/auth -w (path may differ on your system) - Install an LDAP server with a database for dc=nodomain; this is trivial to do with debian: Simply install slapd and systemctl start slapd. - Start dovecot - Run doveadm user '*' - You should find the error in the mail.log. I hope this is somehow useful to fix our crash issue. We’ll be happy to provide more information as needed. kind regards, Jonas

4 4

Status of SMTPUTF8?
by Noah Tilton 14 Sep '18

14 Sep '18

I was wondering whether there is a roadmap for adding SMTPUTF8 support to Dovecot? My delivery pattern is Postfix -> Dovecot LMTP and it is choking on utf8 messages. I might be able to volunteer some of my time as a developer. Another thread about this seemed to go unanswered: http://dovecot.org/list/dovecot/2016-September/105474.html http://unix.stackexchange.com/questions/320091/configure-postfix-and-doveco… -Noah

4 3

LMTP tcp listener with auth?
by Andreas Thienemann 14 Sep '18

14 Sep '18

I am wondering if it's possible to have a tcp listener for LMTP do authentication and not accept any unauthenticated mail. My configuration looks like the following: service lmtp { inet_listener lmtp { address = 192.168.0.1 127.0.0.1 port = 24 } } This gives me a network reachable lmtp socket, but of course no autentication. When reading the docs, it seems though that only userdb lookup and no actual authentication is supported? Is that understanding correct? cheers, Andreas

4 3

Server certificate verification error with Dovecot 2.3.2.1
by Robert Gill 13 Sep '18

13 Sep '18

I'm attempting to upgrade my Dovecot installation to 2.3.2.1. My SSL certificate authority provides a bundle containing their CA, plus intermediate CAs, which I configure using the 'ssl_ca' option. The comments in the configuration file say to only set this when you're requiring client certificates, which I'm not, but fetchmail complains with a "Server certificate verification error, Broken certificate chain" error if that setting is not set. This works fine with Dovecot 2.2.34. After upgrading to 2.3.2.1, fetchmail throws that error whether 'ssl_ca' is set or not. Dovecot 2.3.2.1 reports the error SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca: SSL alert number 48 in the logs when attempting the TLS handshake. The permissions on the CA bundle haven't changed and should still be readable by Dovecot. I'm running Gentoo Linux on x86_64 and mail is stored on an ext4 file system. I'm attaching my config files for both Dovecot 2.2.34 and Dovecot 2.3.2.1.

3 3

dovecot + centos 7 + internal ca + hostname change
by Matt Bryant 13 Sep '18

13 Sep '18

Not sure if this is dovecot or not but can find very little ie no info around on this ... and added the pem file into /etc/pki/ca-trust/source/anchors and run udpate-ca-trust .. all works ok .. (this is on centos 7 btw) So wanted to change the hostname away from ip-x-x-x-x to something a little bit more descriptive .. but then kaboom .. doesnt work any more and the following errors are seen. Have created and internal CA for domain and added it to Sep 13 10:42:04 ip-10-0-40-230 dovecot: master: Dovecot v2.2.33.2 (d6601f4ec) starting up for imap, pop3, lmtp, sieve (core dumps disabled) Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'attr->pValue != NULL' not true at attrs_build Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'lexer->tok.field.name && lexer->tok.field.value' not true at p11_lexer_next Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:04 ip-10-0-40-230 dovecot: message repeated 16 times: [ auth: Error: p11-kit: 'attrs != NULL' not true at attrs_build] Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'new_memory != NULL' not true at maybe_expand_array Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at p11_array_push Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at sink_object Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'new_memory != NULL' not true at maybe_expand_array Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at p11_array_push Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at sink_object ... ... Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'new_memory != NULL' not true at maybe_expand_array Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at p11_array_push Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at sink_object Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'attr->pValue != NULL' not true at attrs_build Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'new_memory != NULL' not true at maybe_expand_array Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at p11_array_push Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at sink_object Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: no CKA_CLASS attribute found Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: couldn't load file into objects: /usr/share/pki/ca-trust-source/ca-bundle.trust.p11-kit Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Fatal: master: service(auth-worker): child 14389 killed with signal 11 (core dumps disabled) Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Fatal: master: service(auth-worker): child 14391 killed with signal 11 (core dumps disabled) Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Fatal: master: service(auth-worker): child 14393 killed with signal 11 (core dumps disabled) why would a hostname change make any difference here .. the certs specified in dovecot config are all complete in their chain so not sure what its trying to do ... set hostname back to original works find .. so something is obviously tied or keyed to hostname though cant find anything specific anyone seen anything like this at all ?? rgds Matt

1 1

Re: make check (pigeonhole)
by Eric Broch 12 Sep '18

12 Sep '18

Must be non root user as well On 9/12/2018 1:05 PM, Aki Tuomi wrote: > Ok. We have that fix as well but for other reasons. Good to know this. > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Eric Broch <ebroch(a)whitehorsetc.com> > Date: 12/09/2018 21:36 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi>, dovecot(a)dovecot.org > Subject: Re: make check (pigeonhole) > > Hi Aki, > > I needed this patch > <https://src.fedoraproject.org/cgit/rpms/dovecot.git/tree/dovecot-2.3.0.1-li…> > (fedora): > > |diff -up dovecot-2.3.0.1/src/auth/mycrypt.c.libxcrypt > dovecot-2.3.0.1/src/auth/mycrypt.c --- > dovecot-2.3.0.1/src/auth/mycrypt.c.libxcrypt 2018-02-28 > 15:28:58.000000000 +0100 +++ dovecot-2.3.0.1/src/auth/mycrypt.c > 2018-03-27 10:57:38.447769201 +0200 @@ -14,6 +14,7 @@ # define _XPG6 > /* Some Solaris versions require this, some break with this */ #endif > #include <unistd.h> +#include <crypt.h> #include "mycrypt.h" All works > well now. Thanks for your help Eric | > > On 9/12/2018 12:35 AM, Aki Tuomi wrote: >> >> I tried reproducing your problem and I only can make it happen if I >> run the test suite as root, which is not supported. >> >> Aki >> >> >> On 12.09.2018 06:49, Eric Broch wrote: >>> >>> I'll give those a look and make change accordingly. >>> >>> >>> On 9/11/2018 9:26 PM, Aki Tuomi wrote: >>>> You know we have rpm packages for 2.3.2.1 available at >>>> https://repo.dovecot.org if you are in a hurry? >>>> >>>> >>>> >>>> --- >>>> Aki Tuomi >>>> Dovecot oy >>>> >>>> -------- Original message -------- >>>> From: Eric Broch <ebroch(a)whitehorsetc.com> >>>> Date: 12/09/2018 00:35 (GMT+02:00) >>>> To: dovecot(a)dovecot.org >>>> Subject: Re: make check (pigeonhole) >>>> >>>> Any news on this error on CentOS 7 ? >>>> >>>> Help! >>>> >>>> >>>> On 9/10/2018 9:32 AM, Eric Broch wrote: >>>>> >>>>> I attempted as non-root user and got the exact same error. >>>>> >>>>> >>>>> On 9/10/2018 9:10 AM, Aki Tuomi wrote: >>>>>> Have you attempted this as non-root user? >>>>>> >>>>>> >>>>>> >>>>>> --- >>>>>> Aki Tuomi >>>>>> Dovecot oy >>>>> >>>>> -- >>>>> Eric Broch >>>>> White Horse Technical Consulting (WHTC) >>>> >>>> -- >>>> Eric Broch >>>> White Horse Technical Consulting (WHTC) >>> >>> -- >>> Eric Broch >>> White Horse Technical Consulting (WHTC) >> > > -- > Eric Broch > White Horse Technical Consulting (WHTC) -- Eric Broch White Horse Technical Consulting (WHTC)

1 0

Re: make check (pigeonhole)
by Eric Broch 12 Sep '18

12 Sep '18

I'll give those a look and make change accordingly. On 9/11/2018 9:26 PM, Aki Tuomi wrote: > You know we have rpm packages for 2.3.2.1 available at > https://repo.dovecot.org if you are in a hurry? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Eric Broch <ebroch(a)whitehorsetc.com> > Date: 12/09/2018 00:35 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: Re: make check (pigeonhole) > > Any news on this error on CentOS 7 ? > > Help! > > > On 9/10/2018 9:32 AM, Eric Broch wrote: >> >> I attempted as non-root user and got the exact same error. >> >> >> On 9/10/2018 9:10 AM, Aki Tuomi wrote: >>> Have you attempted this as non-root user? >>> >>> >>> >>> --- >>> Aki Tuomi >>> Dovecot oy >> >> -- >> Eric Broch >> White Horse Technical Consulting (WHTC) > > -- > Eric Broch > White Horse Technical Consulting (WHTC) -- Eric Broch White Horse Technical Consulting (WHTC)

2 3

Adding namespace alias_for causes index resync?
by Tom Sommer 12 Sep '18

12 Sep '18

I just added a new namespace-alias with alias_for. Apparently this causes all mailbox indexes to be resynced? Is this intentional and/or is there some way to avoid this? My NFS storage pretty much kills its elf when hundreds of thausands of users needs to resync indexes :) Thanks -- Tom

1 1

Re: LMTP tcp listener with auth?
by Andreas Thienemann 12 Sep '18

12 Sep '18

Hi Stephan, On Wed, 12 Sep 2018, Stephan Bosch wrote: > LMTP currently does not support AUTH. Bummer. Thought so. > What is your use case? Most people hide LMTP behind a firewall, or don't > expose it through TCP/IP in the first place. The port is currently only available to a few trusted machines, but having auth available would have been a nice benefit in case the firewall gets misconfigured. Cyrus for example will expose the LMTP port via TCP if configured, but expects valid user credentials. The larger use-case is a migration from cyrus to dovecot. As it's not just the MDA but also the MTA installation that is being migrated I need a way to deliver mail from the old MTA to the new MDA. LMTP comes in handy. https://github.com/ixs/lmtp_proxy/blob/master/README.md#minmal-downtime-mig… has a rough invocation of the steps needed for that. As I said, LMTP auth isn't critical for this, but would have been a nice addition. cheers, Andreas

1 0

Letsencrypt certificate for repo.dovecot.org expired May 14th..
by B. Reino 12 Sep '18

12 Sep '18

Dear all, Just in case you've missed it, the certificate for repo.dovecot.org just expired yesterday. This causes errors in e.g. apt-get update. Thanks in advance for fixing it, -- B. Reino

2 6

Re: make check (pigeonhole)
by Eric Broch 12 Sep '18

12 Sep '18

I attempted as non-root user and got the exact same error. On 9/10/2018 9:10 AM, Aki Tuomi wrote: > Have you attempted this as non-root user? > > > > --- > Aki Tuomi > Dovecot oy -- Eric Broch White Horse Technical Consulting (WHTC)

2 2

Log sync error
by Jakobus Schürz 11 Sep '18

11 Sep '18

Hi there! I get a lot of errormessages. My dovecot is: dovecot-core 2:2.3.2.1-1~stretch from Debian stable. I found this: https://www.dovecot.org/list/dovecot/2013-July/091648.html So the bug came back... The Log is attached Thanks Jakob

1 0

Re: make check (pigeonhole)
by Eric Broch 10 Sep '18

10 Sep '18

I did so as non-root user and got the same error. On 9/10/2018 9:10 AM, Aki Tuomi wrote: > Have you attempted this as non-root user? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Eric Broch <ebroch(a)whitehorsetc.com> > Date: 10/09/2018 18:03 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: Re: make check (pigeonhole) > > Dovecot list, > > 1) I downloaded latest dovecot and pigeonhole tar balls and extracted on > latest updated CentOS 7 : dovecot-2.3.2.1.tar.gz and > dovecot-2.3-pigeonhole-0.5.2.tar.gz > > 2) I moved pigeonhole (dovecot-2.3-pigeonhole-0.5.2) directory into > dovecot (dovecot-2.3.2.1) directory > > 3) built dovecot with following config and paramerters: > > patch -p1 < ../../SOURCES/dovecot-2.0-defaultconfig.patch > patch -p1 < ../../SOURCES/dovecot-1.0.beta2-mkcert-permissions.patch > patch -p1 < ../../SOURCES/dovecot-2.2.27-mkcert-paths.patch > > sed -i '/DEFAULT_INCLUDES *=/s|$| '"$(pkg-config --cflags > libclucene-core)|" src/plugins/fts-lucene/Makefile.in > > #export CFLAGS="-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions > -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches > -fno-strict-aliasing" > #export LDFLAGS="-Wl,-z,now -Wl,-z,relro -Wl,-z,relro" > aclocal --install -I m4 > autoreconf -I . -fiv > > ./configure \ > INSTALL_DATA="install -c -p -m644" \ > --docdir=/usr/share/doc/dovecot-2.3.2.1 \ > --disable-static \ > --disable-rpath \ > --with-nss \ > --with-shadow \ > --with-pam \ > --with-gssapi=plugin \ > --with-ldap=plugin \ > --with-sql=plugin \ > --with-lua=plugin \ > --with-pgsql \ > --with-mysql \ > --with-sqlite \ > --with-vpopmail=/etc/libvpopmail \ > --with-zlib \ > --with-libcap \ > --with-libwrap \ > --with-lucene \ > --with-ssl=openssl \ > --with-ssldir=/etc/pki/dovecot \ > --with-solr \ > --with-systemdsystemunitdir=/usr/lib/systemd/system \ > --with-docs > > sed -i 's|/etc/ssl|/etc/pki/dovecot|' doc/mkcert.sh > doc/example-config/conf.d/10-ssl.conf > > make -j3 > > 4) built pigeon hole with the following paramters: > > # required for snapshot > [ -f configure ] || autoreconf -fiv > [ -f ChangeLog ] || echo "Pigeonhole ChangeLog is not available, yet" > >ChangeLog > > ./configure \ > INSTALL_DATA="install -c -p -m644" \ > --disable-static \ > --with-dovecot=../ \ > --with-ldap=plugin \ > --without-unfinished-features > > make -j3 > > 5) during 'make check' of pigeonhole got the following error: > > make[3]: Entering directory > `/root/rpmbuild/SRPMS/dovecot-2.3.2.1/dovecot-2.3-pigeonhole-0.5.2/src/lib-sieve/util' > for bin in test-edit-mail; do \ > if ! /bin/sh ../../../run-test.sh ../../.. ./$bin; then exit 1; fi; \ > done > test-edit-header(root): Error: Cannot lookup test user: Mail access for > users with UID 89 not permitted (see first_valid_uid in config file, uid > from mail_uid setting). > ../../../run-test.sh: line 27: 29930 Segmentation fault (core > dumped) valgrind -q --trace-children=yes --leak-check=full > --log-file=test.out.$$ $noundef $* > ==29930== Invalid read of size 8 > ==29930== at 0x404699: mail_raw_user_create (mail-raw.c:142) > ==29930== by 0x40325B: test_init (test-edit-mail.c:105) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== Address 0xb8 is not stack'd, malloc'd or (recently) free'd > ==29930== > ==29930== > ==29930== Process terminating with default action of signal 11 (SIGSEGV) > ==29930== Access not within mapped region at address 0xB8 > ==29930== at 0x404699: mail_raw_user_create (mail-raw.c:142) > ==29930== by 0x40325B: test_init (test-edit-mail.c:105) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== If you believe this happened as a result of a stack > ==29930== overflow in your program's main thread (unlikely but > ==29930== possible), you can try to increase the size of the > ==29930== main thread stack using the --main-stacksize= flag. > ==29930== The main thread stack size used in this run was 8388608. > ==29930== 64 bytes in 1 blocks are possibly lost in loss record 35 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277AB5: pool_system_malloc (mempool-system.c:75) > ==29930== by 0x525D2FD: p_malloc (mempool.h:99) > ==29930== by 0x525D2FD: hash_table_create (hash.c:70) > ==29930== by 0x51F377C: settings_parser_init_list > (settings-parser.c:215) > ==29930== by 0x51ED102: master_service_settings_read > (master-service-settings.c:595) > ==29930== by 0x51EE3A9: master_service_settings_cache_read > (master-service-settings-cache.c:387) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== > ==29930== 64 bytes in 1 blocks are possibly lost in loss record 36 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277AB5: pool_system_malloc (mempool-system.c:75) > ==29930== by 0x525D2FD: p_malloc (mempool.h:99) > ==29930== by 0x525D2FD: hash_table_create (hash.c:70) > ==29930== by 0x51F2EA3: settings_parser_dup (settings-parser.c:1957) > ==29930== by 0x51EE844: cache_add (master-service-settings-cache.c:291) > ==29930== by 0x51EE844: master_service_settings_cache_read > (master-service-settings-cache.c:409) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== > ==29930== 64 bytes in 1 blocks are possibly lost in loss record 37 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277AB5: pool_system_malloc (mempool-system.c:75) > ==29930== by 0x525D2FD: p_malloc (mempool.h:99) > ==29930== by 0x525D2FD: hash_table_create (hash.c:70) > ==29930== by 0x51F2EA3: settings_parser_dup (settings-parser.c:1957) > ==29930== by 0x4E8792F: mail_storage_service_lookup_real > (mail-storage-service.c:1324) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 128 bytes in 1 blocks are possibly lost in loss record 48 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x403159: test_init (test-edit-mail.c:101) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 256 bytes in 1 blocks are possibly lost in loss record 52 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527751D: pool_alloconly_malloc (mempool-alloconly.c:283) > ==29930== by 0x528A74E: p_malloc (mempool.h:99) > ==29930== by 0x528A74E: p_strdup_vprintf (strfuncs.c:167) > ==29930== by 0x528A833: p_strdup_printf (strfuncs.c:111) > ==29930== by 0x40318E: test_init_mail_user (test-edit-mail.c:52) > ==29930== by 0x40318E: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 256 bytes in 1 blocks are possibly lost in loss record 53 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x5272941: event_create (lib-event.c:54) > ==29930== by 0x4E8797C: mail_storage_service_lookup_real > (mail-storage-service.c:1334) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 512 bytes in 1 blocks are possibly lost in loss record 56 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527751D: pool_alloconly_malloc (mempool-alloconly.c:283) > ==29930== by 0x5272952: p_malloc (mempool.h:99) > ==29930== by 0x5272952: event_create (lib-event.c:56) > ==29930== by 0x4E8797C: mail_storage_service_lookup_real > (mail-storage-service.c:1334) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 1,024 bytes in 1 blocks are possibly lost in loss record 59 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x51F3741: settings_parser_init_list > (settings-parser.c:204) > ==29930== by 0x51ED102: master_service_settings_read > (master-service-settings.c:595) > ==29930== by 0x51EE3A9: master_service_settings_cache_read > (master-service-settings-cache.c:387) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== > ==29930== 1,024 bytes in 1 blocks are possibly lost in loss record 60 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x51F2D14: settings_parser_dup (settings-parser.c:1924) > ==29930== by 0x51EE844: cache_add (master-service-settings-cache.c:291) > ==29930== by 0x51EE844: master_service_settings_cache_read > (master-service-settings-cache.c:409) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== > ==29930== 1,024 bytes in 1 blocks are possibly lost in loss record 61 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x51F2D14: settings_parser_dup (settings-parser.c:1924) > ==29930== by 0x4E8792F: mail_storage_service_lookup_real > (mail-storage-service.c:1324) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 1,024 bytes in 1 blocks are possibly lost in loss record 62 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527751D: pool_alloconly_malloc (mempool-alloconly.c:283) > ==29930== by 0x5250ED5: p_malloc (mempool.h:99) > ==29930== by 0x5250ED5: buffer_alloc (buffer.c:34) > ==29930== by 0x525110C: buffer_create_dynamic (buffer.c:143) > ==29930== by 0x5272805: array_create_i (array.h:129) > ==29930== by 0x5272805: event_get_field (lib-event.c:383) > ==29930== by 0x5273283: event_add_str (lib-event.c:400) > ==29930== by 0x5273437: event_add_fields (lib-event.c:438) > ==29930== by 0x4E879FD: mail_storage_service_lookup_real > (mail-storage-service.c:1335) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== > ==29930== 1,608 bytes in 1 blocks are possibly lost in loss record 67 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277AB5: pool_system_malloc (mempool-system.c:75) > ==29930== by 0x525D33D: p_malloc (mempool.h:99) > ==29930== by 0x525D33D: hash_table_create (hash.c:79) > ==29930== by 0x51F377C: settings_parser_init_list > (settings-parser.c:215) > ==29930== by 0x51ED102: master_service_settings_read > (master-service-settings.c:595) > ==29930== by 0x51EE3A9: master_service_settings_cache_read > (master-service-settings-cache.c:387) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== > ==29930== 1,608 bytes in 1 blocks are possibly lost in loss record 68 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277AB5: pool_system_malloc (mempool-system.c:75) > ==29930== by 0x525D33D: p_malloc (mempool.h:99) > ==29930== by 0x525D33D: hash_table_create (hash.c:79) > ==29930== by 0x51F2EA3: settings_parser_dup (settings-parser.c:1957) > ==29930== by 0x51EE844: cache_add (master-service-settings-cache.c:291) > ==29930== by 0x51EE844: master_service_settings_cache_read > (master-service-settings-cache.c:409) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== > ==29930== 1,608 bytes in 1 blocks are possibly lost in loss record 69 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277AB5: pool_system_malloc (mempool-system.c:75) > ==29930== by 0x525D33D: p_malloc (mempool.h:99) > ==29930== by 0x525D33D: hash_table_create (hash.c:79) > ==29930== by 0x51F2EA3: settings_parser_dup (settings-parser.c:1957) > ==29930== by 0x4E8792F: mail_storage_service_lookup_real > (mail-storage-service.c:1324) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 2,048 bytes in 1 blocks are possibly lost in loss record 70 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x4E8C454: mailbox_attributes_init > (mailbox-attribute.c:17) > ==29930== by 0x4E7F2F5: mail_storage_init (mail-storage.c:70) > ==29930== by 0x4E87139: mail_storage_service_init > (mail-storage-service.c:975) > ==29930== by 0x403205: test_init_mail_user (test-edit-mail.c:66) > ==29930== by 0x403205: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 2,048 bytes in 1 blocks are possibly lost in loss record 71 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x4E8714A: mail_storage_service_init > (mail-storage-service.c:977) > ==29930== by 0x403205: test_init_mail_user (test-edit-mail.c:66) > ==29930== by 0x403205: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 2,048 bytes in 1 blocks are possibly lost in loss record 72 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527751D: pool_alloconly_malloc (mempool-alloconly.c:283) > ==29930== by 0x528AA66: p_malloc (mempool.h:99) > ==29930== by 0x528AA66: p_strconcat (strfuncs.c:223) > ==29930== by 0x51F40ED: settings_parse_keyvalue (settings-parser.c:845) > ==29930== by 0x51F50E0: settings_parse_environ (settings-parser.c:1103) > ==29930== by 0x51ED247: master_service_settings_read > (master-service-settings.c:648) > ==29930== by 0x51EE3A9: master_service_settings_cache_read > (master-service-settings-cache.c:387) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== > ==29930== 6,144 bytes in 1 blocks are possibly lost in loss record 74 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x4E876FA: mail_storage_service_lookup_real > (mail-storage-service.c:1238) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 12,288 bytes in 1 blocks are possibly lost in loss record 75 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x51EDD31: master_service_settings_cache_init > (master-service-settings-cache.c:75) > ==29930== by 0x4E87541: mail_storage_service_read_settings > (mail-storage-service.c:1073) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 16,384 bytes in 1 blocks are possibly lost in loss record 76 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x51ED84C: master_service_settings_read > (master-service-settings.c:580) > ==29930== by 0x51EE3A9: master_service_settings_cache_read > (master-service-settings-cache.c:387) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== > Failed to run: ./test-edit-mail > > *Note: Previous versions of pigeonhole did a 'make check' successfully > even the first version of 2.3 (CE). Pigeonhole v0.5.1 and v0.5.2 fail on > CentOS 7 > > Help would be appreciated. > > > On 9/9/2018 3:11 PM, Eric Broch wrote: > > Anyone? > > > > > > On 9/8/2018 7:36 PM, Eric Broch wrote: > >> Hello list, > >> > >> During the 'make check' (pigeonhole) portion of a building (rpmbuild) > >> a dovecot.spec file I'm getting the following error: > >> > >> testsuite(root): Fatal: Couldn't drop privileges: User is missing UID > >> (see mail_uid setting) > >> > >> I'm not sure how to resolve this, and any help would be appreciated > >> to help me finish the creating the rpm > >> > > > > -- > Eric Broch > White Horse Technical Consulting (WHTC) > -- Eric Broch White Horse Technical Consulting (WHTC)

1 0

make check (pigeonhole)
by Eric Broch 10 Sep '18

10 Sep '18

Hello list, During the 'make check' (pigeonhole) portion of a building (rpmbuild) a dovecot.spec file I'm getting the following error: testsuite(root): Fatal: Couldn't drop privileges: User is missing UID (see mail_uid setting) I'm not sure how to resolve this, and any help would be appreciated to help me finish the creating the rpm -- Eric Broch White Horse Technical Consulting (WHTC)

2 4

dsync mail from a remote server
by Kai Schaetzl 10 Sep '18

10 Sep '18

I would like to transfer mail for some users from an old dovecot (with no doveadm) to a modern dovecot (2.3.2). I've read up on https://wiki2.dovecot.org/Tools/Doveadm/Sync https://wiki2.dovecot.org/Migration/Dsync and I'm not sure if I can use doveadm for this purpose. I need doveadm to login to the remote server (source) with a username/password via IMAP, fetch all mail and deliver it to a local user (target), preferrably with the same folder structure that exists on the source account. Is this possible? I don't understand this page completely: https://wiki2.dovecot.org/Migration/Dsync For some testing (that's why I used pop3, to keep it simple) I put a file for pop3c in conf.d (mostly identical with the file shown on that page) and restarted dovecot. Then I tried a command line like this: doveadm -o pop3c_user=user -o pop3c_password=password backup -R -u user@domain pop3c: This creates an error: dsync(user@domain): Error: Mail locations must use the same virtual mailbox hierarchy separator (specify separator for the default namespace) I'm not sure what this exactly means. Does it refer to the account naming structure of user@domain? The source server does not have such usernames, only the target server I run the command on. Or does it refer to structure within the mailbox? (which can't really be the case as it doesn't login to the source and can't know the structure yet). So, if it indeed refers to the user naming structure, can I tell it to use the "simple" account names on the source machine? Am I correct in assuming that I can override any pop3c_ setting in the conf file with -o? For instance also using -o pop3c_host= and that if there is -o pop3c_user=user on the command line I don't need a pop3c_user in the conf file? (no master-user). Thanks for any help on this. (If it doesn't work I can use fetchmail, but that is much less preferrable as it "delivers" all mail, so it's all "new" and in the INBOX. Kai

1 0

Disconnects on Director
by Tom Sommer 10 Sep '18

10 Sep '18

Hi I am seeing a lot of clients time out on my Director. I'm wondering if this is "normal" or there is some opportunity to tweak something? Log line: imap-login: Info: proxy(user(a)example.com): disconnecting 1.2.3.4 (Disconnected by client: read(size=433) failed: Connection timed out(37s idle, in=939, out=3083)): user=<user(a)example.com>, method=CRAM-MD5, rip=1.2.3.4, lip=172.0.0.0, TLS: read(size=433) failed: Connection timed out, session=<P2kq7H91H4dZF/2O> Any hints? Nothing is logged by the kernel. 2.3.2.1 -- Tom

2 1

Dovecot - being dropped
by Maurizio Caloro 10 Sep '18

10 Sep '18

Hello Yesterday, I could not receive an email anymore when I looked in the logs found the following errors: * Sep 7 06:04:44 mail dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped * Sep 7 06:06:41 mail dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped If show the config i dont see any process_limits Dovecot 2.2.13 root@mail:/var/log# dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-6-amd64 x86_64 Debian 8.11 auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no info_log_path = /var/log/mail.log log_timestamp = %b %d %H:%M:%S Dovecot/ mail_access_groups = vmail mail_location = maildir:~/Maildir 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 vironment 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-sql.conf.ext driver = sql } plugin { sieve = ~/sieve/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = admin@ protocols = imap pop3 lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-client { mode = 0660 user = mail } } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota" } root@mail:/var/log#

3 3

Re: Dsync deleting mailboxes due to duplicate UIDs
by Andreas Thienemann 10 Sep '18

10 Sep '18

Hi Sami, On Sun, 9 Sep 2018, Sami Ketola wrote: > Is it possible to get imapc rawlogs to analyze? create a directory that is > writeable and add -o imapc_rawlog_dir=/path/to/directory to command line. Tried that. Thanks for the suggestion, that is actually really helpful. If anyone wants to play along at home, the files in that directory are created with the permissions of mail_uid/mail_gid. The dir should be world-writable to make it easy. > Also with recent dovecot release you can tell dsync which header fields to > hash when matching mails. Add dsync_hashed_headers=Message-ID to config and > dovecot will only mach mails using Message-ID header fileld. I had seen that parameter but thought it would be prudent to not _just_ rely on the Message-ID but instead keep the default "Date Message-ID". I _think_ I might have found an issue when looking at the log: 1536525811.026071 * 39 FETCH (UID 39 BODY[HEADER.FIELDS (Date Message-ID)] {159} 1536525811.026071 Message-ID: <Pine.LNX.4.30.0207091925420.433-100000(a)trinity.knopfdruck.org> 1536525811.026071 Date: Tue, 9 Jul 2002 19:26:04 +0200 (MEST) 1536525811.026071 Date: Tue, 9 Jul 2002 12:36:13 +0200 1536525811.026071 1536525811.026071 ) A duplicate Date header is certainly unexpected. Having a look at the original mail on disk on the Cyrus server shows the following Mail: >From [redacted] Tue Jul 9 19:26:04 2002 X-Sieve: cmu-sieve 1.3 Return-Path: [redacted] Received: from bender.bawue.de (localhost [127.0.0.1]) by bender.bawue.de (Postfix) with ESMTP id C79CE48CBC; Tue, 9 Jul 2002 19:29:08 +0200 (CEST) Delivered-To: [redacted] Received: from [redacted] by bender.bawue.de (Postfix) with ESMTP id CFA4848CAA for [redacted]; Tue, 9 Jul 2002 19:28:43 +0200 (CEST) From: [redacted] X-Sender: [redacted] To: [redacted] Message-ID: <Pine.LNX.4.30.0207091925420.433-100000(a)trinity.knopfdruck.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Subject: [redacted] Date: Tue, 9 Jul 2002 19:26:04 +0200 (MEST) Status: RO X-Status: X-Keywords: X-UID: 38 ---------- Forwarded message ---------- Date: Tue, 9 Jul 2002 12:36:13 +0200 Subject: Gewinn [redacted] So it looks like the Cyrus imapd is incorrectly parsing the mail and returning the body content as a header. Comparing the content of UID 39 on the remote server will then hash differently than the UID 39 on the local dovecot server, which behaves better and only returns a single date header. Following the robustness principle it feels to me that it would make sense for dsync to disregard a duplicate header from a remote server and only use the first occurence. Would that be a good approach to the problem? Now that I understand the problem I am having, I can just workaround it but it seems to me that dsync should handle this case better. Anyway, thanks a lot for the imapc_rawlog_dir hint, that helped a lot. cheers, Andreas

1 0

Re: Auth process sometimes stop responding after upgrade
by Simone Lazzaris 08 Sep '18

08 Sep '18

In data venerdì 7 settembre 2018 09:39:23 CEST, Aki Tuomi ha scritto: > Do you see anything else in logs? > Just the usual proxy messages, like these: Sep 6 14:45:41 imap-front13 dovecot: imap-login: proxy(alessandro(a)soldinicarrelli.it): disconnecting 5.169.233.224 (Disconnected by server(0s idle, in=451, out=3556)): user=<alessandro(a)soldinicarrelli.it>, method=PLAIN, rip=5.169.233.224, lip=80.76.81.92, TLS, session=<uqVq2TJ1VbkFqeng> Sep 6 14:45:51 imap-front13 dovecot: pop3-login: proxy(prg(a)pedrini.it): started proxying to 192.168.1.144:110: user=<prg(a)pedrini.it>, method=DIGEST- MD5, rip=5.34.191.10, lip=80.76.81.92, TLS, session=<WqhRRDN1qw0FIr8K> The only suspect thing is this: Sep 6 14:45:41 imap-front13 dovecot: director: doveadm: Host 192.168.1.142 vhost count changed from 100 to 0 Sep 6 14:45:41 imap-front13 dovecot: director: doveadm: Host 192.168.1.143 vhost count changed from 100 to 0 Sep 6 14:45:41 imap-front13 dovecot: director: doveadm: Host 192.168.1.219 vhost count changed from 100 to 0 Nothing on the other system logs (e.g. kernel, daemon, syslog, messages ....). -- *Simone Lazzaris* *Qcom S.p.A.*

5 11

Sievescript in database
by Harald Leithner 07 Sep '18

07 Sep '18

Hi, is it possible to save sieve scripts to a mysql database? I know its possible to read them with the dict sql plugin but iirc it wasn't possible to save it with sievemanaged. thx Harald -- Harald Leithner ITronic Wiedner Hauptstraße 120/5.1, 1050 Wien, Austria Tel: +43-1-545 0 604 Mobil: +43-699-123 78 4 78 Mail: leithner(a)itronic.at | itronic.at

1 0

Auth process sometimes stop responding after upgrade
by Simone Lazzaris 07 Sep '18

07 Sep '18

Hi all; I've upgraded a ring of dovecot directors from 2.2.15 to 2.2.36. After the upgrade I've got some instability: a few time per day per server, seemly at random, the auth process stop responding and the clients cannot authenticate any more: Sep 6 14:45:51 imap-front13 dovecot: pop3-login: Warning: Auth process not responding, delayed sending initial response (greeting): user=<>, rip=xx.xx.xx.xx, lip=xx.xx.xx.xx, TLS, session=<1HVqRTN10MNTie+S> I can't figure it out.... Any hints? This is my configuration: # 2.2.36 (1f10bfa63): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.11 # Hostname: imap-front13.mailfarm.interac.it auth_mechanisms = plain login digest-md5 cram-md5 apop scram-sha-1 auth_verbose = yes auth_verbose_passwords = plain auth_worker_max_count = 50 base_dir = /var/run/dovecot/ default_login_user = nobody director_doveadm_port = 9091 director_mail_servers = 192.168.1.142 192.168.1.143 192.168.1.144 192.168.1.145 192.168.1.216 192.168.1.217 192.168.1.218 192.168.1.219 director_servers = 212.183.164.157 212.183.164.158 212.183.164.159 212.183.164.160 listen = * passdb { args = /usr/local/etc/dovecot/sql.conf driver = sql } protocols = imap pop3 service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director service_count = 0 vsz_limit = 128 M } service pop3-login { executable = pop3-login director service_count = 0 vsz_limit = 128 M } ssl_cert = </usr/local/etc/dovecot/qcom.wildcard.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM- SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA- AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128- SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128- SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256- SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS- AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256- SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128- SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:! MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_parameters_regenerate = 1 weeks ssl_prefer_server_ciphers = yes ssl_protocols = !SSlv2 !SSLv3 syslog_facility = local5 userdb { driver = prefetch } -- *Simone Lazzaris* *Qcom S.p.A.*

2 1

Virtual Maildir as subfolder
by Duncan Bellamy 07 Sep '18

07 Sep '18

I have a setup where google fetches mail from dovecot with pop3s and deletes mail downloaded, so to do this I currently forward a copy of the email to user-fetch@localhost which is the google login and it downloads from that maildir. But it means creating extra folders and I was looking at better ways of doing it. So I have an entry in my user DB file which ends with userdb_mail=maildir:/var/mail/virtual/adomain.com/user/Maildir/.Gfetch, and if I do a "doveadm auth test user(a)adomain.xn--com-9o0a it shows the correct mail location of the .Gfetch folder. But even though it has 6 messages in the folder a doveadm search and google both see zero messages. I think this is because the index file is only in the root of the maildir, is there a way to have a ‘virtual root’ inside a maildir like this? Thanks, Duncan

1 0

Auth process sometimes stop responding after upgrade
by Simone Lazzaris 06 Sep '18

06 Sep '18

Hi all; I've upgraded a ring of dovecot directors from 2.2.15 to 2.2.36. After the upgrade I've got some instability: a few time per day per server, seemly at random, the auth process stop responding and the clients cannot authenticate any more: Sep 6 14:45:51 imap-front13 dovecot: pop3-login: Warning: Auth process not responding, delayed sending initial response (greeting): user=<>, rip=xx.xx.xx.xx, lip=xx.xx.xx.xx, TLS, session=<1HVqRTN10MNTie+S> I can't figure it out.... Any hints? This is my configuration: # 2.2.36 (1f10bfa63): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.11 # Hostname: imap-front13.mailfarm.interac.it auth_mechanisms = plain login digest-md5 cram-md5 apop scram-sha-1 auth_verbose = yes auth_verbose_passwords = plain auth_worker_max_count = 50 base_dir = /var/run/dovecot/ default_login_user = nobody director_doveadm_port = 9091 director_mail_servers = 192.168.1.142 192.168.1.143 192.168.1.144 192.168.1.145 192.168.1.216 192.168.1.217 192.168.1.218 192.168.1.219 director_servers = 212.183.164.157 212.183.164.158 212.183.164.159 212.183.164.160 listen = * passdb { args = /usr/local/etc/dovecot/sql.conf driver = sql } protocols = imap pop3 service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director service_count = 0 vsz_limit = 128 M } service pop3-login { executable = pop3-login director service_count = 0 vsz_limit = 128 M } ssl_cert = </usr/local/etc/dovecot/qcom.wildcard.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM- SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA- AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128- SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128- SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256- SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS- AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256- SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128- SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:! PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_parameters_regenerate = 1 weeks ssl_prefer_server_ciphers = yes ssl_protocols = !SSlv2 !SSLv3 syslog_facility = local5 userdb { driver = prefetch } *Simone Lazzaris* *Qcom S.p.A.* simone.lazzaris(a)qcom.it[1] | www.qcom.it[2] * LinkedIn[3]* | *Facebook[4]* [5] -------- [1] mailto:simone.lazzaris@qcom.it [2] https://www.qcom.it [3] https://www.linkedin.com/company/qcom-spa [4] http://www.facebook.com/qcomspa [5] https://www.qcom.it/includes/email-banner.gif

1 0

Global duplicate filtering via Sieve
by Hanno Stock 06 Sep '18

06 Sep '18

Hi everybody, I have the following problem: Our mail users are receiving mails from externally defined mail forwardings and lists which sometimes leads to duplicate messages. As far as I understand, a single user can use the Sieve duplicate extension for filtering out such duplicate messages. Would it be feasible to add a script with sieve_before that does this for all users? Do scripts that run from sieve_before store persistent data also on a per-user basis, i.e. in the user's home dir? Thanks for your help! Best regards Hanno

2 1

Specifying other mail_attachment_dir for namespace
by Pedro Ribeiro 04 Sep '18

04 Sep '18

Hello, I have a Dovecot setup where I need to allow users to access a snapshot of their messages (when they complain about missing messages/folders deleted by mistake). From time to time the system does a LVM snapshot of the volume holding the mailboxes and sis storage and that messages are available via a "special" namespace. The problem is the messages that references attachments in the single attachment storage cause the file in some cases (when all the references were delete), the attachment itself is missing from the current SIS. Is there any option to reference a specific SIS folder for the namespace like I do for the messages as below? > namespace arquivo { > type = private > separator = / > prefix = "@ARQUIVO/" > subscriptions = yes > list = yes > inbox = no > hidden = no > ignore_on_failure = yes > location = mdbox:/mail-snap/domains/%d/%-2.2n/%n > } TIA. -- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro Politécnico de Lisboa, Serviços da Presidência Departamento de Sistemas de Informação e Comunicações Phone: +351 210 464 700 (general) / VoIP: 80100 Helpdesk: helpdesk(a)net.ipl.pt / https://www.net.ipl.pt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

1 0

Re: online conversion using replication?
by Daniel Miller 04 Sep '18

04 Sep '18

That works for a one-time migration, or perhaps via a cron-job, but what I want is basically a constant one-way backup and it seems replication could do it more elegantly & efficiently. -- Daniel On 9/1/2018 11:14 PM, Aki Tuomi wrote: > You don't need to setup replication for that. See > https://wiki2.dovecot.org/Migration/MailFormat > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Daniel Miller <dmiller(a)amfes.com> > Date: 02/09/2018 04:14 (GMT+02:00) > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: online conversion using replication? > > With a single server - and no intent to have a second server online at > this time - is it possible to use the replication service to keep a > "live" backup? Or otherwise perform a storage format conversion? > > I'm presently using sdbox - and considering going back to mdbox though > without SIS. My intent now is ONLY a 1-way backup, to be kept current, > and no clients will utilize the converted storage (unless/until I change). > > I've successfully executed: > > doveadm backup -u <username> -n inbox > mdbox:/var/mail/<domain>/<user>/mdbox > > For a few users - but reading the docs leads me to believe I can > automate this. But there's no explicit example for this - so I'm not > sure what to set. > > Initially I'm thinking of: > > dsync_remote_cmd = doveadm backup -u %u -n inbox > mdbox:/var/mail/%d/%n/mdbox > > and if that's right - which other services/listeners do I need to setup? > > -- > Daniel >

5 5

Re: dying on osx
by Mike Makuch 04 Sep '18

04 Sep '18

I found and tried this work around on the man page: https://www.unix.com/man-page/all/5/ngroups_max/ but I still get the same "Too many extra groups" error even when I start dovecot with the above program to limit the # of groups. I suspect that dovecot is adding a number of groups when it starts up. I've hacked a work around to get it working for me on my laptop: diff --git a/src/lib/restrict-access.c b/src/lib/restrict-access.c @@ -224,7 +224,12 @@ static void fix_groups_list(const struct restrict_access_settings *set, - if (setgroups(gid_count, gid_list) < 0) { + if (setgroups(gid_count > NGROUPS_MAX ? 16 : gid_count, gid_list) < 0) { if (errno == EINVAL) { i_fatal("setgroups(%s) failed: Too many extra groups", set->extra_groups == NULL ? "" : and this works. I'm not sure what the right solution is for a PR. Any suggestions? Thanks Mike On 8/10/18 11:04, Aki Tuomi wrote: > Is the user member of mail group? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Mike Makuch <1mikemakuch(a)gmail.com> > Date: 10/08/2018 19:02 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi> > Cc: dovecot(a)dovecot.org > Subject: Re: dying on osx > > Maybe an old problem that has resurfaced??? > > https://bugzilla.samba.org/show_bug.cgi?id=8773 > > Mike > > > > On 8/10/18 10:54, Aki Tuomi wrote: >> I have to see if this is reproducible outside mac. >> >> >> >> --- >> Aki Tuomi >> Dovecot oy >> >> -------- Original message -------- >> From: Mike Makuch <1mikemakuch(a)gmail.com> >> Date: 10/08/2018 18:46 (GMT+02:00) >> To: Aki Tuomi <aki.tuomi(a)dovecot.fi> >> Subject: Re: dying on osx >> >> I did find that page and tried a few things there. My config has all of >> the settings there except 3: >> >> mail_access_groups = mail >> mbox_read_locks = fcntl >> mbox_write_locks = fcntl >> >> I add them to my config, restart and get the same abort >> >> 20180810-103849 imap(mkm)<79213><MkA5ihZzmdh/AAAB>: Fatal: >> setgroups(mail,505) failed: Too many extra groups >> >> I've tried numerous other settings as well. >> >> Thanks for any further advice >> >> Mike >> >> >> On 8/10/18 08:45, Aki Tuomi wrote: >> > Can you try this config and report back? >> > >> > >> https://superuser.com/questions/957272/dotlock-permissions-problems-with-do… >> > >> > Aki >> > >> >> On 10 August 2018 at 16:39 Mike Makuch <1mikemakuch(a)gmail.com> wrote: >> >> >> >> >> >> OSX 10.13.6 High Sierra, dovecot 2.3.2.1 >> >> >> >> dovecot starts up and runs but dies as soon as my mail client makes a >> >> request with log and config below. >> >> >> >> And advice appreciated. >> >> >> >> Thanks >> >> >> >> Mike >> >> >> >> >> >> >> >> 20180810-083730 auth: Debug: auth client connected (pid=77432) >> >> >> >> 20180810-083730 auth: Debug: client in: AUTH 1 PLAIN >> >> service=imap secured session=xo1p2BRzZNd/AAAB lip=127.0.0.1 >> >> rip=127.0.0.1 lport=143 rport=55140 >> >> 20180810-083730 auth: Debug: client passdb out: CONT 1 >> >> 20180810-083730 auth: Debug: client in: CONT 1 AG1rbQBta20xMjM= >> >> (previous base64 data may contain sensitive data) >> >> 20180810-083730 auth: Debug: static(mkm,127.0.0.1,<xo1p2BRzZNd/AAAB>): >> >> lookup >> >> 20180810-083730 auth: Debug: client passdb out: OK 1 user=mkm >> >> host=localhost nopasswd=y >> >> 20180810-083730 auth: Debug: master in: REQUEST 4201906177 77432 >> >> 1 b8126b4b71be2959fc7716888eccc566 session_pid=77433 >> >> request_auth_token >> >> 20180810-083730 auth-worker(77426): Debug: >> >> passwd(mkm,127.0.0.1,<xo1p2BRzZNd/AAAB>): lookup >> >> 20180810-083730 auth: Debug: master userdb out: USER 4201906177 >> >> mkm system_groups_user=mkm uid=503 gid=20 home=/Users/mkm >> >> auth_token=4d2bb44168df3d63e4e1bb352e59de632bc7da49 >> >> 20180810-083730 imap-login: Info: Login: user=<mkm>, method=PLAIN, >> >> rip=127.0.0.1, lip=127.0.0.1, mpid=77433, secured, >> >> session=<xo1p2BRzZNd/AAAB> >> >> 20180810-083730 imap(mkm)<77433><xo1p2BRzZNd/AAAB>: Fatal: >> >> setgroups(505) failed: Too many extra groups >> >> >> >> # doveconf -n >> >> # 2.3.2.1 (0719df592): /usr/local/etc/dovecot/dovecot.conf >> >> # OS: Darwin 17.7.0 x86_64 >> >> # Hostname: pine >> >> auth_debug = yes >> >> auth_debug_passwords = yes >> >> default_internal_user = _dovecot >> >> default_login_user = _dovenull >> >> disable_plaintext_auth = no >> >> listen = 127.0.0.1 >> >> log_path = /var/log/dovecot >> >> log_timestamp = "%Y%m%d-%H%M%S " >> >> mail_debug = yes >> >> mail_gid = staff >> >> mail_location = mbox:~/Mail:INBOX=/var/mail/%u >> >> mail_privileged_group = mail >> >> mail_uid = _dovecot >> >> passdb { >> >> args = password=*** host=localhost nopasswd=y >> >> driver = static >> >> } >> >> passdb { >> >> args = login >> >> driver = pam >> >> } >> >> protocols = imap >> >> service auth { >> >> user = root >> >> } >> >> service imap-login { >> >> inet_listener imap { >> >> address = * >> >> port = 143 >> >> } >> >> } >> >> ssl = no >> >> userdb { >> >> driver = passwd >> >> } >> >> >> >> >> >

2 1

doveadm variables
by Daniel Miller 04 Sep '18

04 Sep '18

Are variables such as %d and %n available to doveadm when executed from the command line? Either when explicitly declaring the user via -u or when using all users with -A? -- Daniel

1 0