November 2020 - dovecot

Dovecot cannot access mailcrypt decryption key
by Daniel Niewerth 30 Nov '20

30 Nov '20

2 1

A probably dumb question, but I'm stumped
by Christy S 30 Nov '20

30 Nov '20

Hi folks, I'm stumped on an error we're getting in dovecot after upgrading ubuntu. I will say up front that I'm far from a linux expert. I'm helping my husband by managing a virtual private server to handle his domain, including its email. We set this up two years ago and once I finally got the mail working, it's been humming along just fine since, until two days ago when I performed the ubuntu upgrade. Now, when we try to send mail through his domain thunderbird gives this error: Your message was sent but a copy was not placed in your sent folder (Sent) due to network or file access errors. Note that it says this, but the mail isn't actually sent at all. We are using SSL and have been since the beginning which might be part of our problem, but I'm not positive. A google search suggested adding two lines to the 10-ssl.conf file. ssl_dh = </usr/share/dovecot/dh.pem ssl_cipher_list = HIGH:!DH:!aNULL I did both of these things and restarted the server completely, but no luck. looking in /var/log/mail.err I see this. Nov 29 14:08:56 kylesmith-music dovecot: imap-login: Error: Failed to initialize SSL server context: Can't load SSL cert ificate: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small: user=<>, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, session=<t4qrdkS1kPNLFhL4> What's interesting is that last line only showed up after I added the two lines to the config file. My guess is I need to do something with SSL, update it maybe? But I don't want to go fiddling around purely on a guess and potentially break things even more. So, any of you much more linux familiar types want to point me in the right direction? Thanks! Christy

4 3

Repo for ubuntu focal 20.04 LTS
by Sébastien Riccio 27 Nov '20

27 Nov '20

Hello Dovecot, As the new ubuntu LTS 20.04 seems to be out, I would like to ask if there are any plans to add a repo like it already exists for 18.04 LTS. We planned to upgrade our 18.04 LTS boxes to 20.04. It has it’s own dovecot packages (2.3.7 at the time of writing this), but I would prefer we use your repositories like we do with 18.04. Kind regards, Sébastien

4 4

Panic: file message-parser.c
by Urban Loesch 27 Nov '20

27 Nov '20

Hi, I'm running Dovecot 2.3.11 from Dovet Repository on Debian 9.13. I get the following error when some of our users are doing searches in mailboxes. My error log: ... Nov 25 17:32:13 dcot-mydomain-1 dovecot: imap-login: ID sent: x-session-id=Dh04+PC0+O9t+MsP, x-originating-ip=109.248.203.15, x-originating-port=61432, x-connected-ip=10.10.10.10206, x-connected-port=993, x-proxy-ttl=4: user=<>, rip=109.248.203.15, lip=10.10.10.10206, secured, session=<Dh04+PC0+O9t+MsP> Nov 25 17:32:13 dcot-mydomain-1 dovecot: imap-login: Login: user=<user(a)domain.com>, method=PLAIN, rip=109.248.203.15, lip=10.10.10.10206, mpid=110860, secured, session=<Dh04+PC0+O9t+MsP> Nov 25 17:32:18 dcot-mydomain-1 dovecot: imap(user(a)domain.com pid:110860 session:<Dh04+PC0+O9t+MsP>): Panic: file message-parser.c: line 174 (message_part_finish): assertion failed: (ctx->nested_parts_count > 0) Nov 25 17:32:18 dcot-mydomain-1 dovecot: imap(user(a)domain.com pid:110860 session:<Dh04+PC0+O9t+MsP>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fd61a26c0e2] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fd61a26c1ee] -> /usr/lib/dovecot/libdovecot.so.0(+0xe9c81) [0x7fd61a276c81] -> /usr/lib/dovecot/libdovecot.so.0(+0xe9d21) [0x7fd61a276d21] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fd61a1cbfa4] -> /usr/lib/dovecot/libdovecot.so.0(+0xc990e) [0x7fd61a25690e] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0xdc) [0x7fd61a257f8c] -> /usr/lib/dovecot/libdovecot.so.0(message_search_msg+0xa0) [0x7fd61a25a810] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc4c5f) [0x7fd61a5fbc5f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45) [0x7fd61a577575] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc5a5e) [0x7fd61a5fca5e] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc6f63) [0x7fd61a5fdf63] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x10c) [0x7fd61a5fe68c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x22) [0x7fd61a580fb2] -> dovecot/imap(+0x257f0) [0x55be0929f7f0] -> dovecot/imap(command_exec+0x64) [0x55be09297ff4] -> dovecot/imap(+0x24a32) [0x55be0929ea32] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x137) [0x7fd61a28f707] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xc1) [0x7fd61a291211] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x59) [0x7fd61a28fa69] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fd61a28fc98] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fd61a1fd2f3] -> dovecot/imap(main+0x338) [0x55be09287f68] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7fd619e0e2e1] -> dovecot/imap(_start+0x2a) [0x55be0928816a] Nov 25 17:32:18 dcot-mydomain-1 dovecot: imap(user(a)domain.com pid:110860 session:<Dh04+PC0+O9t+MsP>): Fatal: master: service(imap): child 110860 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) ... I searched the archives and found this patch which seems to fix it: https://github.com/dovecot/core/commit/a668d767a710ca18ab6e7177d8e8be22a6b0… Have you planned to release new Debian 9 packages in dovecot repository where this patch will be applied? My current Dovecot version is: ii dovecot-core 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - core files ii dovecot-dbg 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - debug symbols ii dovecot-imapd 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-lmtpd 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - LMTP server ii dovecot-managesieved 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - ManageSieve server ii dovecot-mysql 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - MySQL support ii dovecot-pop3d 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - POP3 daemon ii dovecot-sieve 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - Sieve filters support ... Many thanks Urban

2 1

Dovecot alternatives with good i18n support?
by David Bürgin 26 Nov '20

26 Nov '20

Hello! I’m interested in exploring alternative IMAP servers that have good support for internationalised email, such as support for SMTPUTF8, IDN mail domains, Unicode local-part, etc. etc. If you used to use Dovecot, and found an alternative that does such things well, I would very much like to hear it. Thank you, -- David

2 2

Dovecot+Samba AD - authentication failure
by Odhiambo Washington 26 Nov '20

26 Nov '20

Hi, I have setup samba4 as AD and hoping to have dovecot authenticate users against it. I am facing challenges though and I am unable to figure it out. I could do with a third eye to help me spot what is wrong. root@adc0:/etc# doveadm auth test -x service=imap odhiambo(a)newideatest.local Password: passdb: odhiambo(a)newideatest.local auth failed extra fields: temp Warning: auth-client: conn unix:/var/run/dovecot/auth-client: Auth connection closed with 1 pending requests (max 0 secs, pid=10537, EOF) Fatal: Couldn't connect to auth socket A test against IMAP gives the following debug information: Nov 22 14:31:01 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Nov 22 14:31:01 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so Nov 22 14:31:01 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Nov 22 14:31:01 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Nov 22 14:31:01 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libauthdb_ldap.so Nov 22 14:31:01 auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat Nov 22 14:31:01 auth: Debug: auth client connected (pid=10979) Nov 22 14:31:08 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=uPLvabC0RIh/AAAB lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=34884 resp=<hidden> Nov 22 14:31:08 auth: Debug: ldap(odhiambo(a)newideatest.local,127.0.0.1,<uPLvabC0RIh/AAAB>): Performing passdb lookup Nov 22 14:31:08 auth: Debug: ldap(odhiambo(a)newideatest.local,127.0.0.1,<uPLvabC0RIh/AAAB>): bind search: base=cn=Users,dc=NEWIDEATEST,dc=LOCAL filter=(&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(sAMAccountName=odhiambo@newideatest.local )) Nov 22 14:31:08 auth: Debug: ldap(odhiambo(a)newideatest.local,127.0.0.1,<uPLvabC0RIh/AAAB>): no fields returned by the server *< ====================* Nov 22 14:31:08 auth: Debug: ldap(odhiambo(a)newideatest.local,127.0.0.1,<uPLvabC0RIh/AAAB>): Finished passdb lookup Nov 22 14:31:08 auth: Debug: auth(odhiambo(a)newideatest.local,127.0.0.1,<uPLvabC0RIh/AAAB>): Auth request finished Nov 22 14:31:10 auth: Debug: client passdb out: FAIL 1 user=odhiambo(a)newideatest.local info.log: Nov 22 14:31:08 auth: Info: ldap(odhiambo(a)newideatest.local ,127.0.0.1,<uPLvabC0RIh/AAAB>):* unknown user* (given password: XXXXXXX) Nov 22 14:31:15 imap-login: Info: Aborted login (auth failed, 1 attempts in 7 secs): user=<odhiambo(a)newideatest.local>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=<uPLvabC0RIh/AAAB> Here is my doveconf -n: https://paste.ubuntu.com/p/SPmrxZxHPx/ My dovecot-ldap.cont.ext: uris = ldap://localhost/ dn = "dovecot(a)newideatest.local" dnpass = "XXXXXXXX" sasl_bind = no tls = no ldap_version = 3 deref = never scope = subtree base = cn=Users,dc=NEWIDEATEST,dc=LOCAL auth_bind = yes user_filter = (&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(|(mail=%u)(sAMAccountName=%u)(otherMailbox=%u))) user_attrs = sAMAccountName=user,userPassword=password,=mail=maildir:/home/%n/Maildir/ pass_filter = (&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(sAMAccountName=%u)) pass_attrs = sAMAccountName=user,userPassword=password The use exists in the database: *root@adc0:/var/log/dovecot# samba-tool user show odhiambo* ldb_wrap open of secrets.ldb dn: CN=Odhiambo Washington,CN=Users,DC=newideatest,DC=local objectClass: top objectClass: person objectClass: organizationalPerson objectClass: user cn: Odhiambo Washington sn: Washington givenName: Odhiambo instanceType: 4 whenCreated: 20201120101420.0Z displayName: Odhiambo Washington uSNCreated: 4086 name: Odhiambo Washington objectGUID: e6969596-8b28-41af-b5d8-cea63cc97f98 badPwdCount: 0 codePage: 0 countryCode: 0 badPasswordTime: 0 lastLogoff: 0 lastLogon: 0 primaryGroupID: 513 objectSid: S-1-5-21-701866827-3355127779-3787685610-1106 accountExpires: 9223372036854775807 logonCount: 0 sAMAccountName: odhiambo sAMAccountType: 805306368 userPrincipalName: odhiambo(a)newideatest.local objectCategory: CN=Person,CN=Schema,CN=Configuration,DC=newideatest,DC=local mail: odhiambo(a)newideatest.local loginShell: /bin/bash userAccountControl: 512 pwdLastSet: 132505181852397220 whenChanged: 20201122112945.0Z uSNChanged: 4104 distinguishedName: CN=Odhiambo Washington,CN=Users,DC=newideatest,DC=local -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

2 3

Panic: file istream-seekable.c: line 226
by Eric Mauger 26 Nov '20

26 Nov '20

Hi, I have a lot of Panic in my logs. They happen almost every day and never on the same user. When it happens, the mail is not distributed (it's always lda). I discovered it because my Sympa server had a lot of users in error. The last error (below) was a local user sending a mail to 10 users : 3 of them never get the email. I've looked into my logs and discovered it started after the upgrade from 2.2.27 to 2.3.4 in february. I'm on Debian. This week, I installed the dovecot repo and upgraded to the very last and same thing. The error below happened after the latest upgrade. An example : Nov 25 11:33:07 mx.igf.cnrs.fr dovecot: lda(username_hidden)<4653><A3S4MuIyvl8tEgAAmSH/vg>: Panic: file istream-seekable.c: line 230 (read_from_buffer): assertion failed: (*ret_r > 0) Nov 25 11:33:07 mx.igf.cnrs.fr dovecot: lda(sebastien.granier)<4653><A3S4MuIyvl8tEgAAmSH/vg>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x3d) [0x7f49a56d4eed] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f49a56d500e] -> /usr/lib/dovecot/libdovecot.so.0(+0xf465b) [0x7f49a56de65b] -> /usr/lib/dovecot/libdovecot.so.0(+0xf46c1) [0x7f49a56de6c1] -> /usr/lib/dovecot/libdovecot.so.0(+0x514a6) [0x7f49a563b4a6] -> /usr/lib/dovecot/libdovecot.so.0(+0x53cfb) [0x7f49a563dcfb] -> /usr/lib/dovecot/libdovecot.so.0(+0x1074a1) [0x7f49a56f14a1] -> /usr/lib/dovecot/libdovecot.so.0(+0x1078f6) [0x7f49a56f18f6] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_stat+0x34) [0x7f49a56eaab4] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb1396) [0x7f49a5852396] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb1472) [0x7f49a5852472] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_physical_size+0x38) [0x7f49a57ef0c8] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x4005) [0x7f49a5907005] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver_init+0x141) [0x7f49a5908101] -> /usr/lib/dovecot/deliver(main+0x879) [0x562d1c0e6f99] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f49a543e09b] -> /usr/lib/dovecot/deliver(_start+0x2a) [0x562d1c0e76ea] My configuration : dovecot -n # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (6c69c917) # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.6 # Hostname: mx.igf.cnrs.fr auth_username_format = disable_plaintext_auth = no lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_location = maildir:~/maildir mail_plugins = fts 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 index ihave duplicate mime foreverypart extracttext namespace inbox { inbox = yes location = mailbox Ads { auto = subscribe } 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 { driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /etc/dovecot/sieve.d } protocols = " imap sieve pop3 sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { process_min_avail = 16 service_count = 0 } service managesieve-login { inet_listener sieve { port = 4190 } } service stats { unix_listener stats-reader { group = dovecot mode = 0666 user = root } unix_listener stats-writer { group = dovecot mode = 0666 user = root } } ssl_cert = </etc/dovecot/ssl/certs/mx_igf_cnrs_fr_with_CA.crt ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local2 userdb { driver = passwd } verbose_proctitle = yes protocol lda { mail_plugins = fts sieve syslog_facility = local2 } Thanks, -- Eric Mauger | Administrateur système et réseau IGF UMR5203 | https://www.igf.cnrs.fr

1 0

Dovecot+Solr+Tika segmentation fault
by Manuel Josupeit-Walter 25 Nov '20

25 Nov '20

Hi all, I am running a mail server for family and friends based on Dovecot and Docker. Today I made a weird observation which I must have overlooked for a long time so far because they logs were written to the journal. However, I am usually only investigating the Docker logs. It seems that some e-mail indexing leads to segfaults and it seems to be related only with Solr and Tika. I have auto-indexing turned on so sometimes the indexer-worker crashes when moving mails from one folder to the other or searching for mails otherwise. Also, if I try to manually reindex using doveadm index, the doveadm process quits with a segfault. I am always running the most recent Dovecot version, in this case 2.3.11.3, but I am not neccessarily up-to-date with Solr or Tika. I am on Solr Version 7.4 and Tika 1.24.1. On the console I am receiving Tika errors and on the Solr Webinterface I see a couple of Ealry EOFs as well. I am not a Linux expert from a dev perspective, but it seems to me that the client (Dovecot) closes the connection prematurely. Does anyone have a hint? I am happy to provide more information if required. I need to know how to collect them, though. Best, Manuel The following can be found in the journald logs during the attempt to reindex my Sent mailbox with doveadm index: Nov 24 16:59:49 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:49 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name kernel: doveadm[400]: segfault at 0 ip 00007fb9f4fa2b64 sp 00007ffc927694f0 error 4 in libdovecot.so.0.0.0[7fb9f4f58000+db000] Nov 24 16:59:50 server.name kernel: Code: 89 f5 48 8d b8 f0 01 00 00 48 8b 52 08 4c 8b 62 48 e8 90 89 fb ff 48 8b 44 24 08 be 00 20 00 00 4c 89 ef 48 8b 80 10 01 00 00 <4c> 8b 38 e8 64 b2 fb ff 48 8b 44 24 08 4c 89 ef 48 8b b0 10 01 00 Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: WARN tika/: Text extraction failed (null) Nov 24 16:59:50 server.name tika[988]: org.apache.tika.exception.TikaException: TIKA-198: Illegal IOException from org.apache.tika.parser.DefaultParser@4dcc5b82 Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:286) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:143) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.server.resource.TikaResource.parse(TikaResource.java:409) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.server.resource.TikaResource$4.write(TikaResource.java:521) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.jaxrs.provider.BinaryDataProvider.writeTo(BinaryDataProvider.java:177) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.jaxrs.utils.JAXRSUtils.writeMessageBody(JAXRSUtils.java:1472) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.serializeMessage(JAXRSOutInterceptor.java:249) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.processResponse(JAXRSOutInterceptor.java:122) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.handleMessage(JAXRSOutInterceptor.java:84) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingChainInterceptor.java:90) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:247) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:79) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1300) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:190) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1215) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:221) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.Server.handle(Server.java:500) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:383) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:547) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:375) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:273) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938) Nov 24 16:59:50 server.name tika[988]: at java.lang.Thread.run(Thread.java:748) Nov 24 16:59:50 server.name tika[988]: Caused by: org.eclipse.jetty.io.EofException: Early EOF Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpInput$3.getError(HttpInput.java:1141) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpInput$3.noContent(HttpInput.java:1129) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpInput.read(HttpInput.java:321) Nov 24 16:59:50 server.name tika[988]: at java.io.FilterInputStream.read(FilterInputStream.java:133) Nov 24 16:59:50 server.name tika[988]: at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) Nov 24 16:59:50 server.name tika[988]: at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) Nov 24 16:59:50 server.name tika[988]: at java.io.BufferedInputStream.read(BufferedInputStream.java:345) Nov 24 16:59:50 server.name tika[988]: at java.io.FilterInputStream.read(FilterInputStream.java:107) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.io.ProxyInputStream.read(ProxyInputStream.java:78) Nov 24 16:59:50 server.name tika[988]: at org.apache.commons.io.input.ProxyInputStream.read(ProxyInputStream.java:78) Nov 24 16:59:50 server.name tika[988]: at org.apache.pdfbox.io.ScratchFile.createBuffer(ScratchFile.java:443) Nov 24 16:59:50 server.name tika[988]: at org.apache.pdfbox.pdmodel.PDDocument.load(PDDocument.java:1220) Nov 24 16:59:50 server.name tika[988]: at org.apache.pdfbox.pdmodel.PDDocument.load(PDDocument.java:1196) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.parser.pdf.PDFParser.getPDDocument(PDFParser.java:190) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.parser.pdf.PDFParser.parse(PDFParser.java:149) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) Nov 24 16:59:50 server.name tika[988]: ... 39 more Nov 24 16:59:50 server.name tika[988]: ERROR Problem with writing the data, class org.apache.tika.server.resource.TikaResource$4, ContentType: text/plain

1 0

Dovecot authentication hangs when ldap_start_tls_s() fails for invalid certificate
by sebastiano degan 19 Nov '20

19 Nov '20

On a Debian10 I've installed postfix 3.4.14 and dovecot 2.3.4.1. I've configured multiple passdb sources and I expect that if one fails the other ones are tested. This is usually the case, except when the failure is due to an invalid certificate from the ldap server. In that case all authentication attempts from that moment on will fail. I've trimmed down the configuration as much as possible (see below), and this is the syslog output of my tests: TEST 1 - Everything is configured correctly: No output on syslog TEST 2 - Wrong hostname as a ldap server: Auth attempt 1: Nov 19 11:25:29 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Nov 19 11:25:29 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-userdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Nov 19 11:25:29 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Nov 19 11:25:35 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Auth attempt 2: Nov 19 11:25:57 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Nov 19 11:25:59 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Auth attempt 3: Nov 19 11:26:28 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Nov 19 11:26:30 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server TEST 3 - Invalid certificate: Attempt 1: Nov 19 11:21:20 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Connect error Nov 19 11:21:20 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-userdb.conf.ext: ldap_start_tls_s() failed: Connect error No output on other attempts... CONFIGURATION FILES: ______________________________________________________ auth.conf: auth_mechanisms = plain login passdb { driver = ldap args = /etc/dovecot/dovecot-ldap-passdb.conf.ext } userdb { driver = ldap args = /etc/dovecot/dovecot-ldap-userdb.conf.ext default_fields = uid=vmail gid=vmail home=/var/mail/vmail/%d/%n } ______________________________________________________ ______________________________________________________ dovecot-ldap-passdb.conf.ext: tls = yes hosts = DC1.fv.lan base = ou=Frigoveneta,dc=fv,dc=lan auth_bind = yes auth_bind_userdn = %u ______________________________________________________ ______________________________________________________ dovecot-ldap-userdb.conf.ext: tls = yes hosts = DC1.fv.lan base = ou=Frigoveneta,dc=fv,dc=lan dn = ##removed## dnpass = ##removed## user_filter = (&(userPrincipalName=%u)) ______________________________________________________

1 0

RE: about imap-login: Error and imap: Error after Version-UP
by 'Aki Tuomi' 18 Nov '20

18 Nov '20

Hi.. there is supposed to be only at most one (1) stats process. Having multiple stats processes breaks stats. Aki > On 18/11/2020 01:48 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp> wrote: > > > Aki-san > > Last night We adjusted the "process_limit" in the stats service to get rid of the error. > > "client_limit" is in the blank (default) state. > > Thank you very much. > > morikawa > -----Original Message----- > From: 'Aki Tuomi' [mailto:aki.tuomi@open-xchange.com] > Sent: Tuesday, November 17, 2020 2:35 PM > To: 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp>; dovecot(a)dovecot.org > Subject: RE: about imap-login: Error and imap: Error after Version-UP > > You need to configure stats service client limit and imap service client limit. Those are different services than imap-login service. > > Aki > > > On 17/11/2020 01:28 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp> wrote: > > > > > > Aki-san > > > > I have already seen that page. > > Is the setting method wrong? > > > > Is there any other tuning point? > > > > morikawa > > -----Original Message----- > > From: Aki Tuomi [mailto:aki.tuomi@open-xchange.com] > > Sent: Monday, November 16, 2020 8:52 PM > > To: 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp>; dovecot(a)dovecot.org > > Subject: Re: about imap-login: Error and imap: Error after Version-UP > > > > > > > On 16/11/2020 13:44 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp> wrote: > > > > > > > > > We have upgraded dovecot from 2.0.9 (centos6) to 2.2.36 (centos8). > > > > > > If more than 1000 users log in, the following error will occur. > > > ------------------------- > > > Nov 16 11:33:00 xxxxxxxx dovecot[1361]: imap-login: Error: master(imap): > > > net_connect_unix(imap) failed: Resource temporarily unavailable - > > > http://wiki2.dovecot.org/SocketUnavailable (client-pid=1362, > > > client-id=129834, rip=10.10.10.10, created 551 msecs ago, received > > > 0/4 > > > bytes) > > > Nov 16 11:30:26 xxxxxxxx dovecot[1361]: imap: Error: > > > net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource > > > temporarily unavailable > > > ------------------------- > > > > > > I set the following because I thought it was a problem with the > > > number of connections, but I get an error. > > > > > > service imap-login { > > > service_count=0 > > > client_limit = $default_client_limit > > > process_min_avail = 4 > > > process_limit = $default_process_limit > > > vsz_limit = 1G > > > } > > > > > > limits.conf > > > ------------------------- > > > * soft nofile 4096 > > > * hard nofile 4096 > > > ------------------------- > > > > > > cat /proc/sys/net/core/somaxconn > > > ------------------------- > > > 4096 > > > ------------------------- > > > > > > Is there any other tuning point? > > > Where should I look? > > > > https://wiki.dovecot.org/SocketUnavailable > > > > Aki

1 0