similar to: [Bug] FTS double escaping

Displaying 20 results from an estimated 9000 matches similar to: "[Bug] FTS double escaping"

2017 Apr 09
1
[Bug] FTS double escaping
Cit?t Timo Sirainen <tss at iki.fi>: > On 6 Apr 2017, at 14.58, azurit at pobox.sk wrote: >> >> Hi, >> >> i'm trying to resolve few problems with indexing 'From' headers >> using FTS/Solr. I was tcpdumping the communication between Dovecot >> and Jetty/Solr and noticed that 'From' headers, which includes also >>
2017 Apr 06
0
[Bug] FTS double escaping
On 06.04.2017 14:58, azurit at pobox.sk wrote: > Hi, > > i'm trying to resolve few problems with indexing 'From' headers using > FTS/Solr. I was tcpdumping the communication between Dovecot and > Jetty/Solr and noticed that 'From' headers, which includes also > sender's name, are double escaped. This is what was Dovecot sending to > Solr: > >
2017 Apr 09
0
[Bug] FTS double escaping
On 6 Apr 2017, at 14.58, azurit at pobox.sk wrote: > > Hi, > > i'm trying to resolve few problems with indexing 'From' headers using FTS/Solr. I was tcpdumping the communication between Dovecot and Jetty/Solr and noticed that 'From' headers, which includes also sender's name, are double escaped. This is what was Dovecot sending to Solr: > >
2017 Apr 09
2
[Bug] FTS invalid address parsing
Hi, i found another bug in FTS while parsing quoted-printable/base64-encoded sender's name inside 'From' header (again, i was figuring out why some of messages cannot be searched). Header: From: =?UTF-8?Q?A=2CB?= <test at example.com> Data send to Solr by Dovecot: <field name="from">A@, B &amp;lt;test at example.com&amp;gt;</field> Header:
2018 Mar 05
1
Re: [enhancement] fts-solr low performance
>Hi, > >we have activated fts-solr about a week ago and immediately started to >experience really *low* performance with MOVE and EXPUNGE commands. >After several days of googling, tcpdumping and straceing i was able to >find and resolve the problem. > >We are using Dovecot 2.2.27 from Debian Jessie (jessie-backports), >which is doing a soft commit in solr after
2006 Jan 28
7
Setting up FSTAB
I am setting up Xen for the first time and have run into a problem. My system was initially setup with Fedora Core 4. I was able to successfully create a File-backed VBD. When I boot the domain,I get an error message that is listed at the end of the below boot messages. I suspect the problem is casued by my fstab. However, I am not sure how it should be configured. Fstab listed also. Any pointers
2015 Mar 05
2
Dovecot Full Text Search: HTTP 500 : Unknown fieldType 'text_general' specified on field text. [SERIOUS]
Hi Muzzafer, I get the error as specified below when i try to added it in as a field:- I dont think text_general is a valid field? HTTP ERROR 500 Problem accessing /solr/. Reason: {msg=SolrCore 'collection1' is not available due to init failure: Could not load conf for core collection1: Unknown fieldType 'text_general' specified on field text. Schema file is
2020 Jul 26
2
Trying to use solr
__ Francis Augusto Medeiros-Logeay francis at francisaugusto.com Mobile: +47 45 17 14 91 Oslo, Norway Sent from a mobile device / Enviado a partir de dispositivo m?vel > On 24 Jul 2020, at 19:34, Shawn Heisey <elyograg at elyograg.org> wrote: > > ?On 7/22/2020 11:13 AM, Francis Augusto Medeiros-Logeay wrote: >> On Solr I get this error: >>
2013 Apr 28
3
Dovecot Solr Panic
Hello Everyone, I have a small base of users (30), but a lot of emails. I have an error again when I am indexing a virtual folder with a large number of folders. I appreciate this is a special case, but I am using dovecot and solr as it is, according to the documentation, the favourite way. One user is using a large number of archives sub folders, by years, months and subfolders, since 5 years.
2020 Nov 15
2
[patch] enhancement for tika server protected by user/password basic auth
On 11/15/20 12:21 PM, John Fawcett wrote: > I'm using tika-server.jar installed as a service yup. same here. atm, listening on localhost, with Dovecot -> Tika direct, no proxy. similarly fragile under load. throwing ~10 messages with .5-5MB attachments at it at once causes all sorts of complaints. one at a time seems OK ... > Dovecot currently implements separate integrations,
2019 Dec 15
1
Solr commit and optimize: which user?
Hi, I have Solr FTR working with dovecot, and need to do the commit and optimize recommended here: https://wiki.dovecot.org/Plugins/FTS/Solr Should this run as root, or as each mail user. The documentation above implies, but doesn't state, that it is root. The docs here are similar: http://grimore.org/networking/dovecot/full_text_search But the docs here say it has to be done for each
2020 Jun 23
2
Re: virt-builder problem
On Tue, Jun 23, 2020 at 06:14:06PM +0800, 雁渡寒潭 wrote: > hello: I yum install libguestfs-tools,when I run virt-builder -l > error: > curl: (56) Recv failure: Connection reset by peer > virt-builder: error: external command ‘'curl' -q --config > '/tmp/virt-builder.sVjrSV/guestfscurl53f9ac.conf'’ exited with error 56 Possibly a problem reaching
2014 Oct 09
3
arsh840@gmail.com has indicated you're a friend. Accept?
Hi, arsh840 at gmail.com wants to follow you. ****** Is arsh840 at gmail.com you friend? ****** If Yes please follow the link below: http://invites.infoaxe.net/signup_e.html?fullname=&amp;email=centos at centos.org&amp;invitername=arsh840 at
2019 Apr 13
3
Solr connection timeout hardwired to 60s
On 4/13/2019 4:29 AM, John Fawcett via dovecot wrote: > If this value was made configurable people could set it to what they > want. However the underlying problem is likely on solr configuration. The Jetty that is included in Solr has its idle timeout set to 50 seconds. But in practice, I have not seen this timeout trigger ... and if the OP is seeing a 60 second timeout, then the 50
2017 Jul 21
1
FTS error Unknown user
Hi, sorry for previous message, i accidentaly send it before it was complete. Recently, i was configuring a setup with one proxy, which is doing authentication and multiple backends, which doesn't have access to user database (see https://www.mail-archive.com/dovecot at dovecot.org/msg70123.html ). Now i wanted to use FTS (solr) on backends but i'm getting this error everytime
2019 Apr 12
2
Solr connection timeout hardwired to 60s
Looking further at tcpdumps of the Dovecot->Solr traffic and Solr metrics it doesn't seem like there's anything suspicious apart from the TCP windows running full and Dovecot backing of ... until it times out and close the connection. >From my understanding of how Dovecot operates towards Solr it will flush ~1000 documents towards Solr in /update request until it has traversed the
2019 Apr 14
1
[PATCH] Re: Solr connection timeout hardwired to 60s
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 14 April 2019 16:59 John Fawcett via dovecot < <a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote: </div>
2012 Dec 31
5
2.1.12: Panic: file solr-connection.c: line 547 (solr_connection_post_more)
Hi all, I am having a problem indexing one of my mailboxes using the solr fts backend in dovecot 2.1.12 For many mailboxes it works just fine, but on one mailbox I currently always get a panic. solr setup: Java: icedtea 6.1.11.5 Solr: 3.6.2 running in tomcat 7.0.32 Command to reproduce error: doveadm index -u my at user badmailbox I already noticed that there have been some solr backend fixes
2019 Nov 20
4
Tablegen PAT limitation?
Hi, The full trace stack: Type set is empty for each HW mode: possible type contradiction in the pattern below (use -print-records with llvm-tblgen to see all expanded records). vtInt: (vt:{ *:[Other] }) UNREACHABLE executed at /home/nancy/work/rpp_clang/llvm/utils/TableGen/CodeGenDAGPatterns.cpp:824! [ 85%] Building X86GenEVEX2VEXTables.inc... &nbsp;#0 0x000000000081b9b5
2020 Nov 15
2
[patch] enhancement for tika server protected by user/password basic auth
On 11/15/20 11:13 AM, John Fawcett wrote: > Just a couple of updates about Tika and Solr together. > > 1. On mass reindexing I'm seeing panics - see below. These are present > with Dovecot 2.3.10 and 2.3.11.3. Seem to go away with the fix which was > previously posted on this list by Josef 'Jeff' Sipek, which I repeat > below for easy of reference. > > 2. On