January 2018 - dovecot

Error in virtual mailbox dovecot 2.3-devel maybe in mailcount
by Jakobus Schürz 01 Feb '18

01 Feb '18

Hi there! I splitted my Mailarchiv to an extra namespace. Because i have some Problems with the Archiv. I can open all Folders from Mailarchiv with dovecot. But i want to have a "all archives" Mailbox to search in all messages in only one virtual mailbox. Trying to open this virtual folder from thunderbird, I get in a big archiv this error in logs from dovecot: Jän 12 10:54:41 aldebaran dovecot[839]: imap(jakob)<11302><9ILYQJFipPlcPAkS>: Error: virtual index /var/mail/virtual/ARCHIV: Broken mailbox_count header Jän 12 10:54:41 aldebaran dovecot[839]: imap(jakob)<11302><9ILYQJFipPlcPAkS>: Error: virtual index /var/mail/virtual/ARCHIV: Broken mailbox_count header Jän 12 10:54:41 aldebaran dovecot[839]: imap(jakob)<11302><9ILYQJFipPlcPAkS>: Panic: Leaked view for index /var/lib/dovecot/db/indexes/archiv/jakob/Archiv/2016/Mailinglisten/stvkr-a/dovecot.index: Opened in index-storage.c:336 Jän 12 10:54:41 aldebaran dovecot[839]: imap(jakob)<11302><9ILYQJFipPlcPAkS>: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0xc6021) [0x7f391bf02021] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xc60ed) [0x7f391bf020ed] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f391be74481] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xf3942) [0x7f391c2a1942] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_close+0x72) [0x7f391c278ec2] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_close+0x1a) [0x7f391c1f8c0a] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0xa7e0) [0x7f39174637e0] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_backend_box_open+0x2b) [0x7f391746397b] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_storage_sync_init+0x1026) [0x7f3917466926] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x4d) [0x7f391c1fb05d] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7f391c1fb117] -> dovecot/imap [jakob 92.60.9.18 select](cmd_select_full+0x171) [0x55759e0911a1] -> dovecot/imap [jakob 92.60.9.18 select](command_exec+0x64) [0x55759e098ca4] -> dovecot/imap [jakob 92.60.9.18 select](+0x1b0b2) [0x55759e0970b2] -> dovecot/imap [jakob 92.60.9.18 select](+0x1b13c) [0x55759e09713c] -> dovecot/imap [jakob 92.60.9.18 select](client_handle_input+0x1a5) [0x55759e097565] -> dovecot/imap [jakob 92.60.9.18 select](client_input+0x82) [0x55759e097be2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f391bf19c09] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x109) [0x7f391bf1b4a9] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7f391bf19d12] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f391bf19f28] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f391be971e3] -> dovecot/imap [jakob 92.60.9.18 select](main+0x328) [0x55759e089768] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f391babd2b1] -> dovecot/imap [jakob 92.60.9.18 select](_start+0x2a) [0x55759e08994a] Jän 12 10:54:41 aldebaran dovecot[839]: imap(jakob)<11302><9ILYQJFipPlcPAkS>: Fatal: master: service(imap): child 11302 killed with signal 6 (core not dumped) and if i search the virtual mailbox with doveadm i get almost the same error. The "Broken mailbox_count_header" is missing there. The full amount of emails in archiv is about 28000 # ulimit -n 256000 # doveadm search -u jakob mailbox Real/Archiv all doveadm(jakob): Panic: Leaked view for index /var/lib/dovecot/db/indexes/archiv/jakob/Archiv/2016/Diverses/Standard-foren/dovecot.index: Opened in index-storage.c:336 doveadm(jakob): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0xc6021) [0x7f8259fe6021] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xc6079) [0x7f8259fe6079] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f8259f58481] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xf3942) [0x7f825a385942] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_close+0x72) [0x7f825a35cec2] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_close+0x1a) [0x7f825a2dcc0a] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0xa7e0) [0x7f82559507e0] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_backend_box_open+0x2b) [0x7f825595097b] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_storage_sync_init+0x1026) [0x7f8255953926] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x4d) [0x7f825a2df05d] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7f825a2df117] -> doveadm(doveadm_mail_iter_init+0x94) [0x56303334be94] -> doveadm(+0x33715) [0x56303334f715] -> doveadm(+0x29a88) [0x563033345a88] -> doveadm(+0x2a702) [0x563033346702] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x230) [0x563033347570] -> doveadm(doveadm_cmd_run_ver2+0x575) [0x563033357155] -> doveadm(doveadm_cmd_try_run_ver2+0x37) [0x5630333571a7] -> doveadm(main+0x1d2) [0x5630333360c2] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f8259ba12b1] -> doveadm(_start+0x2a) [0x5630333364ca] Abgebrochen Thanks Jakob

1 1

test-net.c failure
by Rupert Gallagher 31 Jan '18

31 Jan '18

test-net.c:79: Assert failed: strcmp(net_ip2addr(&ip), "::5") == 0 test-net.c:83: Assert failed: strcmp(net_ip2addr(&ip), "::5") == 0 net_ip2addr() ........................................................ : FAILED Hello, Is it possible to disable DOVECOT_IPV6? We do not use IPv6 (and hope we shall never do on e-mails).

3 3

2.3.0 on 10.13.3 (macos): all testing errors
by Rupert Gallagher 30 Jan '18

30 Jan '18

Enclosed.

1 0

send specific NDR message for users in certain OU
by lists 30 Jan '18

30 Jan '18

Hi, The question can perhaps be made more generic like this: Can dovecot generate a *specific* NDR (or an autoreply) for accounts that meet a specific criterium, such as: - user account was found under OU=to-delete,CN=company... contrary to the regular location CN=Users,CN=company... We would like to move to-be-deleted users to this container, before actually deleting them. That gives us an easy way to revert, if the deletion turns out to be erroneous. We could do that with via a sieve config for those accounts, but if dovecot could send a "delivery failure"-type specific for those accounts (with instructions who to contact to revert the situation) it would be very easy: only move the user to the specific OU, and have the system do the rest. Can this be done? (dovecot 2.1.17 on wheezy, yes we know we should upgrade, and we also will, but it runs rock solid...) MJ

2 2

2 panics, 1 segmentation fault in dovecot 2.3.0 (fts)
by Infoomatic 30 Jan '18

30 Jan '18

Hi, While testing our migration to dovecot 2.3.0, we encountered 2 panics, 1 segmentation fault while we wanted to rebuild the solr indizes. Problem [1] was encountered while rebuilding the indizes, and now I don't know how many mails/documents are indexed or where it got stuck. [2] and [3] encountered while just playing around, since I did not know of "tokenize" and did not find a lot of information about it. This is a ubuntu 16.04 machine, dovecot 2.3.0 compiled from source ( + the patch for the recent zlib problem). "doveadm index" runs on a ~ 4GB mdbox-zipped-mailbox for about 3-4 minutes before aborting with the message above, beforehand I did a "/opt/dovecot/bin/doveadm fts rescan -A". When I repeat "doveadm index" it aborts after about 4 seconds, after a "/opt/dovecot/bin/doveadm fts rescan -A" it runs again for 3-4 minutes. Apache tika logs, but those are probably not related to the problem, however, the devs might want investigate the last line: WARN Parse exception Expected ';', got "," determining content disposition javax.mail.internet.ParseException: Expected ';', got "," and org.apache.tika.exception.ZeroByteFileException: InputStream must have > 0 bytes I would be happy if you could have a look at this, please, and of course just tell me what further information you need. Thanks, infoomatic [1] /opt/dovecot/bin/doveadm index -u user1 '*' doveadm(user1): Panic: file unichar.c: line 160 (uni_ucs4_to_utf8_c): assertion failed: (uni_is_valid_ucs4(chr)) doveadm(user1): Error: Raw backtrace: /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5eea) [0x7ff27755beea] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5f59) [0x7ff27755bf59] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff2774ce5e1] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(uni_ucs4_to_utf8_c+0xa0) [0x7ff277593300] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xa74f9) [0x7ff27753d4f9] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(mail_html2text_more+0xc5) [0x7ff27753d705] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0xcf5c) [0x7ff276460f5c] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(fts_parser_more+0x27) [0x7ff276460c37] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(fts_build_mail+0x511) [0x7ff27645eb51] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0x110a6) [0x7ff2764650a6] -> /opt/dovecot/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x2e) [0x7ff27784618e] -> /opt/dovecot/bin/doveadm(+0x2f697) [0x55dd2f912697] -> /opt/dovecot/bin/doveadm(+0x29827) [0x55dd2f90c827] -> /opt/dovecot/bin/doveadm(+0x2a4bb) [0x55dd2f90d4bb] -> /opt/dovecot/bin/doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x21d) [0x55dd2f90e2cd] -> /opt/dovecot/bin/doveadm(doveadm_cmd_run_ver2+0x575) [0x55dd2f91deb5] -> /opt/dovecot/bin/doveadm(doveadm_cmd_try_run_ver2+0x37) [0x55dd2f91df07] -> /opt/dovecot/bin/doveadm(main+0x1d2) [0x55dd2f8fd032] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7ff2770ec830] -> /opt/dovecot/bin/doveadm(_start+0x29) [0x55dd2f8fd439] Aborted (core dumped) [2] This was just about my curiosity since I haven't used "tokenize" and did not find too much info about it: /opt/dovecot/bin/doveadm fts tokenize -A '*' Panic: file doveadm-print.c: line 142: unreached Error: Raw backtrace: /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5eea) [0x7f38ac5c2eea] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5f59) [0x7f38ac5c2f59] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f38ac5355e1] -> /opt/dovecot/bin/doveadm(+0x3b3d3) [0x55c728e8b3d3] -> /opt/dovecot/bin/doveadm(+0x2a63a) [0x55c728e7a63a] -> /opt/dovecot/bin/doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x21d) [0x55c728e7b2cd] -> /opt/dovecot/bin/doveadm(doveadm_cmd_run_ver2+0x575) [0x55c728e8aeb5] -> /opt/dovecot/bin/doveadm(doveadm_cmd_try_run_ver2+0x37) [0x55c728e8af07] -> /opt/dovecot/bin/doveadm(main+0x1d2) [0x55c728e6a032] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f38ac153830] -> /opt/dovecot/bin/doveadm(_start+0x29) [0x55c728e6a439] Aborted (core dumped) [3] /opt/dovecot/bin/doveadm fts tokenize -u user1 "@" Segmentation fault (core dumped)

2 2

Dovecot 2.2.33.2 doveadm log reopen don't work
by Айхэд 30 Jan '18

30 Jan '18

dovecot -n # 2.2.33.2 (d6601f4ec): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: FreeBSD 11.1-RELEASE-p1 amd64 zfs from logrotate.conf: /var/log/dovecot/dovecot.log { rotate 180 missingok nomail noolddir compress create 0600 nobody nobody postrotate # /usr/local/bin/doveadm log reopen /usr/sbin/service dovecot reload endscript } After upgrade to 2.2.33.2 (prev version was 2.2.29.1) there are only messages from sieve in /var/log/dovecot/dovecot.log like this: Jan 29 00:00:12 lda(***): Info: sieve: msgid=<20180128210012.3A9A11138B8E@***>: stored mail into mailbox 'INBOX.' (INBOX) Messages from pop3, pop3-login, imap, imap-login are absent. If i replace /usr/local/bin/doveadm log reopen with /usr/sbin/service dovecot reload all works fine. Before upgrade all worked fine.

1 0

Change destination of dsync
by Sergio Belkin 29 Jan '18

29 Jan '18

Hi, I have the following command for retrieving mails from another IMAP mail server dsync -D -v backup -R -u jon.doe imapc: I't ok and works, but I'd want to copy messages outside of /var directory, is there a way to do that? Thanks in advance! -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org

2 1

problem with lda
by Infoomatic 27 Jan '18

27 Jan '18

Hello, I am currently testing the upgrade from our dovecot v2.2.23 to 2.3.0. I have a strange problem with lda. We use bounce mails for internal users if they try to send virus/spammails. The exact same config works with 2.2.23, but not with 2.3.0. The relevant postfix/master.cf part: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/opt/dovecot/libexec/dovecot/deliver -d ${recipient} -f ${sender} On the same machine, with 2.2.23 I get a bounce mail when trying to send a virus, with the subject "VIRUS in message apparently from you (Eicar-Test-Signature)", to both the users inbox as well as to the mailbox of virusalert(a)ourdomain.internal With 2.3.0, in the logs I get an error: relay=dovecot, delay=0.01, delays=0/0/0/0, dsn=5.3.0, status=bounced (command line usage error. Command output: lda: Fatal: Invalid -f parameter: Missing domain and the alert message is only sent to virusalert(a)ourdomain.internal, but not to the user who tried to send the mail. The relevant part of our dovecot.conf: protocol lda { mail_plugins = " quota zlib sieve acl mail_log notify" postmaster_address = postmaster(a)ourdomain.internal } Does anyone know how to solve this problem? Or is there a workaround via postfix/amavis/spamassassin? Any hints are highly appreciated, thanks! Regards, infoomatic

3 6

Send full X.509 client certificate to custom authentication policy server
by Jaime Hablutzel Egoavil 26 Jan '18

26 Jan '18

I'm working with Dovecot 2.3 and I'm wondering if I could send the full X.509 client certificate to my custom authentication policy server. I'm actually aware that I can send the client certificate validity status with something like: auth_policy_request_attributes = ... cert=%{cert} But I want the full X.509 certificate to be able to decide over the basis of certificate extensions, e.g. Certificate Policies extension. Is it currently possible?, what about Lua based authentication?, does Lua currently receive the full client certificate?. -- Jaime Hablutzel - RPC 994690880

2 1

exited on signal 6 (core dumped) when searching folder
by Kristjan Eentsalu 26 Jan '18

26 Jan '18

Hey, I'm getting messages exited on signal 6 (core dumped) when doing imap command "a UID SORT (DATE) UTF-8 BODY someword" message log file Jan 26 13:57:20 mail dovecot: imap(kristjan.eentsalu(a)yyy.yy): Panic: file charset-iconv.c: line 87 (charset_to_utf8_try): assertion failed: (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE) Jan 26 13:57:20 mail dovecot: imap(kristjan.eentsalu(a)yyy.yy): Fatal: master: service(imap): child 6410 killed with signal 6 (core dumped) Problem seems to to be with one old mail. OS: FreeBSD 11.1-RELEASE-p4 Dovecot 2.2.33.2 , pigenhole 0.4.21 trace, conf and email available https://pastebin.com/7X6fZPPd Kristjan

2 1