similar to: fts_solr and connection via https://

Op 8-2-2017 om 21:07 schreef Jan Vonde: > Am 07.02.2017 um 12:29 schrieb Stephan Bosch: >> >> Op 31-1-2017 om 6:33 schreef Jan Vonde: >>> Am 31.01.2017 um 00:04 schrieb Stephan Bosch: >>>> Op 1/22/2017 om 12:01 PM schreef Stephan Bosch: >>>>> Op 1/22/2017 om 10:01 AM schreef Jan Vonde: >>>>>> I tried adding the following settings

Op 1/22/2017 om 12:01 PM schreef Stephan Bosch: > Op 1/22/2017 om 10:01 AM schreef Jan Vonde: >> I tried adding the following settings but that didn't help: >> ssl_ca = < /etc/ssl/certs/ca-certificates.crt >> ssl_client_ca_dir = /etc/ssl/certs >> >> Can you give me a hint how I can get the ssl certificate accepted? > That should normally have done the

Op 31-1-2017 om 6:33 schreef Jan Vonde: > Am 31.01.2017 um 00:04 schrieb Stephan Bosch: >> Op 1/22/2017 om 12:01 PM schreef Stephan Bosch: >>> Op 1/22/2017 om 10:01 AM schreef Jan Vonde: >>>> I tried adding the following settings but that didn't help: >>>> ssl_ca = < /etc/ssl/certs/ca-certificates.crt >>>> ssl_client_ca_dir =

Am 17.02.2017 um 17:27 schrieb Jan Vonde: > Am 17.02.2017 um 11:45 schrieb Stephan Bosch: >> Op 8-2-2017 om 21:07 schreef Jan Vonde: >>> Am 07.02.2017 um 12:29 schrieb Stephan Bosch: >>>> Op 31-1-2017 om 6:33 schreef Jan Vonde: >>>>> Am 31.01.2017 um 00:04 schrieb Stephan Bosch: >>>>>> Op 1/22/2017 om 12:01 PM schreef Stephan Bosch:

Am 07.02.2017 um 12:29 schrieb Stephan Bosch: > > > Op 31-1-2017 om 6:33 schreef Jan Vonde: >> Am 31.01.2017 um 00:04 schrieb Stephan Bosch: >>> Op 1/22/2017 om 12:01 PM schreef Stephan Bosch: >>>> Op 1/22/2017 om 10:01 AM schreef Jan Vonde: >>>>> I tried adding the following settings but that didn't help: >>>>> ssl_ca =

Am 17.02.2017 um 11:45 schrieb Stephan Bosch: > Op 8-2-2017 om 21:07 schreef Jan Vonde: >> Am 07.02.2017 um 12:29 schrieb Stephan Bosch: >>> Op 31-1-2017 om 6:33 schreef Jan Vonde: >>>> Am 31.01.2017 um 00:04 schrieb Stephan Bosch: >>>>> Op 1/22/2017 om 12:01 PM schreef Stephan Bosch: >>>>>> Op 1/22/2017 om 10:01 AM schreef Jan Vonde:

Am 31.01.2017 um 00:04 schrieb Stephan Bosch: > Op 1/22/2017 om 12:01 PM schreef Stephan Bosch: >> Op 1/22/2017 om 10:01 AM schreef Jan Vonde: >>> I tried adding the following settings but that didn't help: >>> ssl_ca = < /etc/ssl/certs/ca-certificates.crt >>> ssl_client_ca_dir = /etc/ssl/certs >>> >>> Can you give me a hint how I

Op 1/22/2017 om 10:01 AM schreef Jan Vonde: > I tried adding the following settings but that didn't help: > ssl_ca = < /etc/ssl/certs/ca-certificates.crt > ssl_client_ca_dir = /etc/ssl/certs > > Can you give me a hint how I can get the ssl certificate accepted? That should normally have done the trick. However, the sources tell me that no ssl_client settings are

Op 3/4/2017 om 2:39 PM schreef Jan Vonde: > Am 17.02.2017 um 17:27 schrieb Jan Vonde: >> Am 17.02.2017 um 11:45 schrieb Stephan Bosch: >>> Op 8-2-2017 om 21:07 schreef Jan Vonde: >>> We seem to have found another issue there. More on this will follow. >>> >> Thanks for the update and have a nice weekend, >> > I don't want to push, am just

Hi, Dovecot 2.2.32-34 FreeBSD 10.4 Solr 7.2.1(Centos 6) When I try to use https to connect to solr, I get error when a self-signed certificate: Mar 3 05:15:47 server dovecot: indexer-worker(email at domain.com): Received invalid SSL certificate: self signed certificate: /C=Country/ ST=State/L=Location/O=Organization/OU=Organizational Unit/CN=solr.domain.com Mar 3 05:15:47 server dovecot:

When using Auth policy server it doesn?t currently doesn?t support https. In version 2.2.27: Policy server HTTP error: 9002 Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) and in version 2.3.devel Policy server HTTP error: 9002 Requested https connection, but no SSL settings given dovecot.conf does have

Hello, Excuse me, Is dovecot really unable to work with solr through https ? I tried to change ssl_client_ca_dir and ssl_client_ca_file, but nothing. Alex 2018-03-05 21:56: > Hi, > > Dovecot 2.2.32-34 > FreeBSD 10.4 > > Solr 7.2.1(Centos 6) > > > When I try to use https to connect to solr, I get error when a > self-signed certificate: > > Mar 3

Hi, Dovecot wiki says the solr url is something like 'solr/dovecot/' but this gives a 404, if I install solr as per the docs I have a 'solr/#/dovecot/' url: https://wiki.dovecot.org/Plugins/FTS/Solr I have installed dovecot 2.3 from https://repo.dovecot.org/ and solr 8.3 as per the wiki on a Ubuntu 18.04. The problem and the guess work I did: fts_solr =

I'm seeing the following: Jun 5 11:10:52 thebighonker dovecot: imap(ler): Error: fts_solr: received invalid uid '0' Is there something I can get for you to debug? doveconf -n: # 2.2.30.1 (eebd877): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.18 (29cc74d) # OS: FreeBSD 11.1-PRERELEASE amd64 auth_debug_passwords = yes auth_default_realm = lerctr.org auth_mechanisms

I'm getting a lot of: Jun 16 11:40:40 thebighonker dovecot: imap(ler/58755): Error: fts_solr: received invalid uid '0' Jun 16 11:40:40 thebighonker dovecot: imap(ler/58755): Error: fts_solr: received invalid uid '0' in my logs. What can I supply to help get to the bottom of it? doveconf -n: # 2.2.30.2 (c0c463e): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version

I'm getting lots of: Jun 30 14:41:34 thebighonker dovecot: imap(ler/14135): Error: fts_solr: received invalid uid '0' in my logs. Ideas? doveconf -n: # 2.2.31 (65cde28): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: FreeBSD 11.1-BETA2 amd64 auth_default_realm = lerctr.org auth_mechanisms = plain login auth_realms = lerctr.org

?I've a dovecot instance setup with submission proxy, protocols = imap lmtp submission sieve hostname = internal.mx.example.com submission_relay_host = internal.mx.example.com submission_relay_port = 465 submission_relay_trusted = yes submission_relay_ssl = smtps submission_relay_ssl_verify = yes service submission-login { inet_listener submission { address = 10.2.2.10,

Hello, The documentation says imapsieve_url "has no effect on the administrator-controlled Sieve scripts". However, when setting this item, I get lines such as: Error: imapsieve: mailbox INBOX: Failed to read /shared/imapsieve/script mailbox attribute: Mailbox attributes not enabled and that's it. imapsieve_mailboxXXX_* settings are completely ignored. Unsetting imapsieve_url

Hi, > Am 23.09.2019 um 09:36 schrieb Filip Hanes <filip.hanes at ringier.sk>: > > > ?t 19. 9. 2019 o 15:30 Fabian via dovecot <dovecot at dovecot.org <mailto:dovecot at dovecot.org>> nap?sal(a): > Are there any other hints or tips regarding this ?invalid uid ?0?"-message? > from fts-solr source: > case SOLR_XML_CONTENT_STATE_UID: > if

On 08/10/2019 02:52, Stephan Bosch via dovecot wrote: > > > On 07/10/2019 15:13, Fabian Kuran via dovecot wrote: >> Hi, >> >>> Am 23.09.2019 um 09:36 schrieb Filip Hanes <filip.hanes at ringier.sk >>> <mailto:filip.hanes at ringier.sk>>: >>> >>> >>> ?t 19. 9. 2019 o?15:30 Fabian via dovecot <dovecot at dovecot.org