Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))

On 04/03/18 08:08, A.L.E.C wrote: > On 03/02/2018 03:32 PM, Ralf Hildebrandt wrote: >> The address causing the error is: >> >> From: =?utf-8?Q?Dorit_M=C3=BCller?= >> >> Note the "umlaut" in the email address... :) > This is about SMTPUTF8 (RFC6531). Looks like your only option is to disable > smtp

Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))

On 03/03/18 22:10, Stephan Bosch wrote: > > Clearly, the relevant specifications don't allow UTF-8 in the local part > without email address internationalization (EAI), which Dovecot does not > support nor announce yet (although that should be mended somewhat soon). > My preferred fix for now would

Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))

On 04/03/18 09:55, Stephan Bosch wrote: > Op 3/4/2018 om 9:07 AM schreef John Fawcett: >> On 03/03/18 22:10, Stephan Bosch wrote: >>> Clearly, the relevant specifications don't allow UTF-8 in the local part >>> without email address internationalization (EAI), wh

Re: Coredump: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))

On 05/03/18 15:14, Ralf Hildebrandt wrote: > Got a coredump: > > Mar 5 15:09:42 mail-cbf dovecot: > lmtp(backup@backup.invalid)<15425><2B+kCaZPnVpBPAAAplP5LA>: Fatal: master: > service(lmtp): child 15425 killed with signal 6 (core dumped) > > > #0 0x7fea19977428 in __GI_raise (sig=sig@entry

Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))

On 05/03/18 14:03, Ralf Hildebrandt wrote: > * A.L.E.C : >> On 03/02/2018 03:32 PM, Ralf Hildebrandt wrote: >>> The address causing the error is: >>> >>> From: =?utf-8?Q?Dorit_M=C3=BCller?= >>> >>> Note the "umlaut" in the email address... :) >> This is about SMTPUTF8 (RFC6531). Looks like your on

Re: Extra intermediate certificate when using ssl_alt_cert

On 08/03/18 18:43, Peter Linss wrote: > I just added an ECDSA certificate to my mail server using ssl_alt_cert (the > RSA certificate is specified by ssl_cert), both certificate files contain the > certificate and a single intermediate (which currently happens to be the same > intermediate from

Re: Extra intermediate certificate when using ssl_alt_cert

On 10/03/18 14:06, Aki Tuomi wrote: > >> On 10 March 2018 at 14:49 John Fawcett < j...@voipsupport.it >> <mailto:j...@voipsupport.it>> wrote: >> >> >> On 08/03/18 18:43, Peter Linss wrote: >>> I just added an ECDSA certificate to my mail

Re: Extra intermediate certificate when using ssl_alt_cert

On 10/03/18 14:20, John Fawcett wrote: > On 10/03/18 14:06, Aki Tuomi wrote: >> >>> On 10 March 2018 at 14:49 John Fawcett < j...@voipsupport.it >>> <mailto:j...@voipsupport.it>> wrote: >>> >>> >>> On 08/03/18 18:43, Peter Linss wro

Feature request: client bind address for replication

Hi would it be possible to consider a new parameter for replication: doveadm_local_ip which allows the source ip address to be set when connection to a remote dovecot for replication? It could be useful when the network interface has multiple ips and a specific one is used for mail services. See

Re: IMAP preauth and stats-writer

On 05/01/2019 15:49, Mark Hills wrote: > I use IMAP preauth; I connect with Alpine over SSH which is very useful. > > The last few upgrades this has become more difficult to to. Last time > (moving 2.2 -> 2.3, I think) I had to put in a workaround: > > stats_writer_socket_path = > > It prevented

Re: IMAP preauth and stats-writer

On 06/01/2019 02:26, John Fawcett wrote: > On 05/01/2019 15:49, Mark Hills wrote: >> I use IMAP preauth; I connect with Alpine over SSH which is very useful. >> >> The last few upgrades this has become more difficult to to. Last time >> (moving 2.2 -> 2.3, I think

Re: IMAP preauth and stats-writer

On 06/01/2019 11:37, Stephan Bosch wrote: > > Op 06/01/2019 om 03:35 schreef John Fawcett: >> On 06/01/2019 02:26, John Fawcett wrote: >> >>> Can't see anything in the Dovecot 2.3.4 code that would give this >>> problem, setting >>> >>> st

Re: Problem reading SSL key

On 17/10/2020 19:13, Tech Support wrote: > > All; > >     I’m trying to setup dovecot to use SSL, but I’m getting an error > message in the logs. I’m getting the error imap-login: Fatal: Couldn't > parse private ssl_key. I’m using a commercial cert so I know that the > .crt and .key files themselve

Re: Newbie question about replication

On 16/10/2020 14:23, Piotr Auksztulewicz wrote: > Hi, > > I am a long-time dovecot user/admin for my family mail server, but > I had ventured into configuring replication only recently and I am not > sure about how it should work and what are the good practices. My intent > for replication was to h

Re: Strange permissions error - Failed to stat sieve storage path

On 14/10/2020 16:31, Graham Leggett wrote: > Hi all > > I have dovecot-lda set up to run as vmail:vmail, with some sieve scripts in > /var/lib/dovecot/sieve. > > The sieve scripts fail to be found with the following (detailed and very > helpful) error message: > > Oct 14 16:13:33 gatekeeper dovec

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

On 12/10/2020 00:27, PGNet Dev wrote: > for _un_accented "tambien", match is correctly -- and quickly -- returned. > > in logs, > > ==> /var/log/dovecot/dovecot-info.log <== > 2020-10-11 14:57:05 imap-login: Info: Login: user=, > method=PLAIN, rip=10.0.1.7, lip=10.0.1.50, mpid=67743,

Re: Newbie question about replication

On 18/10/2020 22:53, Piotr Auksztulewicz wrote: > On Sat, Oct 17, 2020 at 11:17:34PM +0200, John Fawcett wrote: >>> I have observed my mail storage directories on both instances and have >>> noticed that they diverge a little over time - the instance B not having >>>

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

gt; Except for this accented-character search mystery.  I've got a _lot_ > of mail with various languages in bodies, so _do_ need to get this > sorted. > >> On 10/18/20 2:58 PM, John Fawcett wrote: > ... >> silly question > ... > > hardly! > > > cre

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

On 19/10/2020 17:00, PGNet Dev wrote: > On 10/19/20 1:18 AM, John Fawcett wrote: >> I would recommend you to redo the tests after correcting the >> configuration. To be doubly sure you can include accented and unique non >> accented text in the same email and search for both

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

On 19/10/2020 16:20, PGNet Dev wrote: > On 10/18/20 10:28 PM, Aki Tuomi wrote: >> Dovecot FTS tokenization is not done, unless you have `use_libfts` in >> fts_solr setting, in your case >> >> fts_solr = url=https://solr.example.com:8984/solr/dovecot/ use_libfts > > changing > > -    fts_solr = url=

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

On 19/10/2020 17:56, PGNet Dev wrote: > On 10/19/20 8:24 AM, John Fawcett wrote: > >> Depending how solr has been setup you could see the logging in the web >> server access log. My access log is where I configured it in >> /var/log/httpd/servername.access_log, yours ma

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

On 19/10/2020 19:02, PGNet Dev wrote: > On 10/19/20 9:48 AM, John Fawcett wrote: >> --with-icu should be sufficient, actually on centos 7 I got libuci >> compiled in without setting the explicit flag. > >> Here's my ldd, which is under /usr/local/lib/dovecot >

Re: Indexer error after upgrade to 2.3.11.3

On 21/10/2020 16:44, Patrik Peng wrote: > On 16.10.20 18:34, Patrik Peng wrote: >> On 16.10.20 18:00, Scott Q. wrote: >>> This reminds me, the way I was able to reproduce this consistently >>> was by having large headers ( 100+ lines ). >>> >>> >>> On Friday, 16/10/2020 at 11:49 Patrik Peng wrote:

Re: Indexer error after upgrade to 2.3.11.3

On 21/10/2020 19:00, John Fawcett wrote: > On 21/10/2020 16:44, Patrik Peng wrote: >> On 16.10.20 18:34, Patrik Peng wrote: >>> On 16.10.20 18:00, Scott Q. wrote: >>>> This reminds me, the way I was able to reproduce this consistently >>>>

Re: Dovecot replication not picking up new mail in maildir

On 25/10/2020 17:19, jayare~d...@videocoding.org wrote: > I've got a basic dovecot master-master replication setup between two > servers (imap1 and imap2). Actions such as deleting messages or moving > them between folders are replicated correctly and quickly. > > However, when new mail is delivere

Re: Indexer error after upgrade to 2.3.11.3 [trial patch]

On 22/10/2020 10:23, John Fawcett wrote: > On 21/10/2020 19:00, John Fawcett wrote: >> On 21/10/2020 16:44, Patrik Peng wrote: >>> On 16.10.20 18:34, Patrik Peng wrote: >>>> On 16.10.20 18:00, Scott Q. wrote: >>>>> This reminds me, the way I was abl

Re: Indexer error after upgrade to 2.3.11.3 [trial patch]

On 31/10/2020 00:18, Scott Q. wrote: > I have implemented this change and the core dumps went away. > > It appears so far that it's indeed the right fix. > > Has this change been introduced in 2.3.11.3 ?  > > Thanks! I've also been running it for 4 days without any further panics / segfaults and n

Re: Indexer error after upgrade to 2.3.11.3 [trial patch]

On 31/10/2020 15:15, Scott Q. wrote: > But do you know how this bug was introduced ? > > I checked the history of that file and don't see anything introduced > recently that might cause > this:  > https://github.com/dovecot/core/commits/master/src/lib-http/http-client-request.c >

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]

On 31/10/2020 04:57, PGNet Dev wrote: > On 10/18/20 10:28 PM, Aki Tuomi wrote: >>> doveadm(myu...@example.com): Panic: file mail-storage.c: line >>> 2112 (mailbox_get_open_status): assertion failed: (box->opened) > ... > >> I can reproduce your problem with the `fts lookup` command. Luckily >>

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]

On 31/10/2020 22:01, PGNet Dev wrote: > On 10/31/20 9:55 AM, John Fawcett wrote: >> I can contribute a patch that solves the segfault. Unfortunately though >> fts search may be more broken than this. It does not give me search >> results, even though I see it querying

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]

On 01/11/2020 15:20, PGNet Dev wrote: > On 11/1/20 1:56 AM, John Fawcett wrote: >> At the moment I don't see other corrections needed in dovecot apart from >> command line doveadm fts which is not a show stopper. Via doveadm search >> I confirm - on my simple config - t

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]

On 31/10/2020 17:55, John Fawcett wrote: > On 31/10/2020 04:57, PGNet Dev wrote: >> On 10/18/20 10:28 PM, Aki Tuomi wrote: >>>> doveadm(myu...@example.com): Panic: file mail-storage.c: line >>>> 2112 (mailbox_get_open_status): assertion failed: (box->opened

Re: Delivering locally through the Submission Server

On 02/11/2020 20:17, R. Diez wrote: > Hi all: > > I am learning Dovecot step by step. I have enabled the Submission > Server, in the hope that I would not need to learn other MTAs like > Postfix. the submission server is a proxy in front of an MTA. You can't avoid having an MTA somewhere in your so

Re: Delivering locally through the Submission Server

On 02/11/2020 21:33, R. Diez wrote: > >> what should it do with the non local messages or local messages directly >> at aliases? > > OK, so I gather that the Submission Server cannot do that (yet). > > My suggestion for a future version would then be: How about running > dovecot-lda, if the user ha

Re: HIGHESTMODSEQ replication issue

On 09/10/2020 21:17, Gustavo Ajeitos [Office365] wrote: > Hello, > > I'm using dovecot 2.3.10 in OpenSUSE and I have configured a > master/master replication between two backends, it works well but I > have found an issue with the replication of the HIGHESTMODSEQ. > When I move a set of message fro

Re: HIGHESTMODSEQ replication issue

On 04/11/2020 18:33, Gustavo Ajeitos [Office365] wrote: > Hi John, > >     Thank you for your answer! > > I agree with you, I think you recommendation should solve the problem, > it seems the only possible workaround. > I have to investigate if it possible and how to accomplish that with > the load

Re: dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?

On 13/11/2020 14:56, PGNet Dev wrote: > I've built a new dovecot + fts-solr instance; I've now picked up & am > running the recently released solr 8.7.0. > > In a test account, I've one message -- in the 'Drafts' folder. > > On exec of fts 'index' > > doveadm index -u testu...@example.com -q '*

Re: dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?

On 13/11/2020 19:55, PGNet Dev wrote: > On 11/13/20 9:56 AM, PGNet Dev wrote: >>> (2) see here: https://wiki.dovecot.org/Plugins/FTS/Solr >>> >>> two useful settings are debug and rawlog_dir=whatever to be added in >>> the same line as fts_solr > > with > > fts_solr = ... debug > > line #35 @ h

Re: dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?

On 13/11/2020 21:32, PGNet Dev wrote: > On 11/13/20 11:37 AM, John Fawcett wrote: >>> still dunno why the 401. :-/ >> >> So I just did a quick check of running dovecot with a standalone >> solr-8.7.0 instance and I'm not seeing any issues. > > +1 > &g

Re: dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?

On 13/11/2020 22:04, PGNet Dev wrote: >> I guess you didn't need to enclose username and password in quotes, i.e. >> >> fts_solr = >> url=https://myuser:my%40p...@solr.example.com:8984/solr/dovecot/ >> use_libfts soft_commit=yes batch_size=250 > > On 11/1

Re: dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?

On 13/11/2020 22:30, John Fawcett wrote: > On 13/11/2020 22:04, PGNet Dev wrote: >>> I guess you didn't need to enclose username and password in quotes, i.e. >>> >>> fts_solr = >>> url=https://myuser:my%40p...@solr.example.com:8984/solr/dovecot/ >>

[patch] enhancement for tika server protected by user/password basic auth

Hi The existing code is designed for a tika server on local host, or on a remote host that is either accessable to all or for example taht is protected by ip restrictions via a proxy in front of it. I've configured a tika server behind an apache proxy which enforces basic auth, but sending basic

Re: [patch] enhancement for tika server protected by user/password basic auth

On 15/11/2020 15:49, PGNet Dev wrote: > On 11/15/20 6:33 AM, John Fawcett wrote: >> I've configured a tika server behind an apache proxy which enforces >> basic auth, but sending basic auth credentials for a tika server is not >> currently supported by Dovecot. > >

Re: [patch] enhancement for tika server protected by user/password basic auth

On 15/11/2020 18:10, John Fawcett wrote: > On 15/11/2020 15:49, PGNet Dev wrote: >> On 11/15/20 6:33 AM, John Fawcett wrote: >>> I've configured a tika server behind an apache proxy which enforces >>> basic auth, but sending basic auth credentials for a tika serve

Re: [patch] enhancement for tika server protected by user/password basic auth

On 15/11/2020 20:48, PGNet Dev wrote: > 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 t

Re: [patch] enhancement for tika server protected by user/password basic auth

On 15/11/2020 21:54, PGNet Dev wrote: > 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.

Re: [patch] enhancement for tika server protected by user/password basic auth

On 16/11/2020 01:14, PGNet Dev wrote: > On 11/15/20 1:29 PM, John Fawcett wrote: >>> atm, listening on localhost, with Dovecot -> Tika direct, no proxy. >>> >>> similarly fragile under load.  throwing ~10 messages with .5-5MB >>> attachments at

Re: last-login Plugin

On 16/11/2020 11:55, Andrea Gabellini wrote: > Hello, > > i'm using last_login plugin and store data into a MySql DB. I'm using > version 2.3.10.1 and the config is at the end of the email. > > I would like to store also the remote IP and the session name. The > config is working but other informat

Re: Dovecot+Solr+Tika segmentation fault

On 30/11/2020 09:45, Manuel Josupeit-Walter wrote: > 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 usu

Re: Dovecot+Solr+Tika segmentation fault

On 04/12/2020 09:29, Manuel Josupeit-Walter wrote: A fix was posted on this list which seems to avoid segfaults when using solr+tika. I reposted it not long ago in response to another question. Before exploring the other segfaults it would be worthwhile getting that fix. If othe

Re: quota-status for outgoing mail (Dovecot/Postfix)

On 06/12/2020 21:13, Peter Folta wrote: > [Dovecot version 2.3.11.3 (502c39af9)] > > Hi all, > > I’m using Dovecot’s quota-status service to let Postfix check the > recipient’s quota before accepting emails following the guide > here: https://blog.sys4.de/postfix-dovecot-mailbox-quota-en.html >

Re: Fts solr add fields message-id, date, in-reply-to

On 07/12/2020 00:22, michael1970 wrote: > Hi, > > how can I add fields message-id, date, in-reply-to to fts solr index like > hdr,body,subject or to? > > Thanks, Michael > > > > -- > Sent from: http://dovecot.2317879.n4.nabble.com/ Hi Michael I don't think you have to do anything specific. I did

Re: Fts solr add fields message-id, date, in-reply-to

On 07/12/2020 02:32, michael1970 wrote: > Hi John, > > I have the standard Dovecot Solr, like in documentation. > > When I query in solr backend > http://127.0.0.1:8983/solr/dovecot/select?q=*%3A* > I see as json: > > "uid":[1075], > "box":["202ab12237483a5e6c139a2345"], >

Re: Fts solr add fields message-id, date, in-reply-to

On 07/12/2020 02:21, peacecop kalmer: wrote: > > I remember to have written a message to the list but maybe, it wasn't > to the list but just the sender. Anyway, here it is: > > "Can't you start using an environment where we can separate different > topics and lessen mail traffic? I subscribed to t

[patch] enhancement for adding limits to solr and tika parsing

Hi As mentioned in a previous thread, the solr + tika combination has caused me some issues due to attachment size. While tika seems to be able to parse large attachments, the resulting volume of text can overwhelm the solr server. One solution would be to throw resources at the problem, but in m

Re: logging in to postfixadmin failed probably because of a dovecot error

On 02/12/2020 02:25, peacecop kalmer: wrote: > > I can’t log in to postfixadmin anymore. It says that the username or > password is incorrect. It can’t be incorrect as I’ve stored them in > Google and “Chrome”. I have two admin accounts and none of them can’t > be used for logging in. So I changed

Re: dovecot/imap killed with signal 6 after SEARCH in specific mailbox

On 07/12/2020 16:58, Jiri wrote: > Hi All, > on my older production server (Deb9 dovecot version 2.2.27-3+deb9u6) a > client reported that searching text in one mailbox failed while other > mailboxes do search ok. > He is using Rouddcube webmail and is searching the whole messages > including the b

Re: Question about login_log_format_elements in a proxy environment

On 07/12/2020 06:02, Adi Pircalabu wrote: > Hi, > > I have a Dovecot proxy setup with several proxy machines (currently > running 2.3.11.3) in front of the real Dovecot servers (2.3.10.1) > storing the mailboxes. "doveconf -a | egrep lip" returns: > login_log_format_elements = user=<%u> method=%m r

Re: Question about login_log_format_elements in a proxy environment

On 07/12/2020 23:09, Adi Pircalabu wrote: > On 08-12-2020 3:13, John Fawcett wrote: >> On 07/12/2020 06:02, Adi Pircalabu wrote: >>> Hi, >>> >>> I have a Dovecot proxy setup with several proxy machines (currently >>> running 2.3.11.3) in front of the re

Re: Question about login_log_format_elements in a proxy environment

On 07/12/2020 23:22, John Fawcett wrote: > On 07/12/2020 23:09, Adi Pircalabu wrote: >> On 08-12-2020 3:13, John Fawcett wrote: >>> On 07/12/2020 06:02, Adi Pircalabu wrote: >>>> Hi, >>>> >>>> I have a Dovecot proxy setup with several proxy

Re: Question about login_log_format_elements in a proxy environment

On 08/12/2020 01:01, Adi Pircalabu wrote: > On 08-12-2020 10:33, Adi Pircalabu wrote: >> On 08-12-2020 9:41, John Fawcett wrote: >>> On 07/12/2020 23:22, John Fawcett wrote: >>>> On 07/12/2020 23:09, Adi Pircalabu wrote: >>>>> On 08-12-2020 3:13, John F

Re: Dovecot 2.3.11.3 LMTP dropping connection after first part of multipart message received

On 10/12/2020 14:58, Steve Akerman wrote: > Good afternoon > > I have been using Dovecot with great success for several months now > with one problem: > > I have received several messages (3 to date out of a much larger > number) which cause Dovecot LMTP to drop the connection with sendmail > after

Potential issue with lmtp_rawlog_dir when using TLS

Hi not sure why this happens, but looks like lmtp_rawlog_dir blocks the successful negotiation of an lmtp starttls connection. Reproducible with openssl s_client.  Two runs with only difference the presence of lmtp_rawlog_dir setting in dovecot config. Failed connection with lmtp_rawlog_dir Dec

Re: Unexpected behavior of doveadm mailbox delete -e -s

On 13/12/2020 05:59, Mar Alegre wrote: > Hello, > > I have encountered what I believe to be a bug, or at least inaccurate > documentation. I am running version 2.3.4.1 of Dovecot (installed via > the default repo for Debian 10), so my apologies if this has been > fixed in a more recent version. I t

Re: AUTH command behaviour when authentication process failed or aborted by user is changed

On 24/12/2020 08:42, Михаил Сандаков wrote: > Hi all, > > . > > Also seems like new behaviour is not fully accorded to rfc1734 > (https://tools.ietf.org/html/rfc1734 > ). Based on this part of rfc: > "If an AUTH >  command fails with a negative response, the

Re: Solr and FTS - assertion failure

On 30/12/2020 16:04, Antonino Esposito wrote: > Hi, > > in the latest weeks i'm working on the Solr integration and > immediately i've faced the assertion failure errors, on 2.0.19, 2.2.9 > and 2.3.11.3 servers in our network. > Reading the thread on debian ML, I realize this issue is related to >

Re: Solr and FTS - assertion failure [proposed patch for upper bound on rows in solr search]

On 30/12/2020 16:04, Antonino Esposito wrote: > Hi, > > in the latest weeks i'm working on the Solr integration and > immediately i've faced the assertion failure errors, on 2.0.19, 2.2.9 > and 2.3.11.3 servers in our network. > Reading the thread on debian ML, I realize this issue is related to >

Re: fts_solr: Indexing failed (fails on particular messages/mailboxes by timeout)

On 15/01/2021 11:39, Alexey Panov wrote: > I guess I was indeed correct. As message body is the part of mail > index dovecot indeed sends all those binary messages as a part of > message body: > >> doveadm fetch -u test.u...@interpont.com >> "body" mailbox KS2 uid 2

Re: [BUG REPORT] In some cases dovecot sends (huge) binary data to solr for indexing

t; <https://filebin.ca/5oy6yqLSCr3H/rawlog.obfuscated.txt> > > (Both files were processed with perl doveadm-obfuscate.pl > <https://www.dovecot.org/tools/doveadm-obfuscate.pl>; the script > doesn’t replace non-latin characters so they were replaced with ‘R’ > manually) > > Wo

Re: Getting panic in http-client-request.c: line 1240 during indexing on Ubuntu 20.04

On 05/02/2021 15:04, Dean Carpenter wrote: > > Is there anything I can do here ?  This makes Tika unusable :(  That > really sucks because we have a *lot* of attachments. > > Thanks - > > On 2021-02-03 2:07 pm, Dean Carpenter wrote: > >> Just noticed this in the logs >> >> doveadm(har...@exampl

Re: Getting panic in http-client-request.c: line 1240 during indexing on Ubuntu 20.04

On 07/02/2021 20:15, @lbutlr wrote: > On 07 Feb 2021, at 02:07, @lbutlr wrote: >> On 06 Feb 2021, at 11:06, John Fawcett wrote: >>> 19.08.20 >> Is that a malformed ISO date 2019-08-20 or a truncated europeans style >> 19-08-2020? > Either way, I cannot find

Re: fts_encoder

On 07/02/2021 18:51, Joan Moreau wrote: > > more info : the function fts_parser_script_more in > plugins/fts/fts-parser.c properly read the output of the script > > still, the data is not sent to the FTS pligins (xapian or any other) > > > > On 2021-02-07 17:37, Joan Moreau wrote: > >> more info :

Re: fts_encoder

On 08/02/2021 15:22, Joan Moreau wrote: > > Well, thank you for the answer, but the actual issue is that data sent > by the decoder (stipulated in the conf file) is properly collected by > dovecot core, but /not/ sent to the plugin : the plugin receives the > original data. > > This is not linke

Re: Getting panic in http-client-request.c: line 1240 during indexing on Ubuntu 20.04

On 08/02/2021 18:40, deano-dove...@areyes.com wrote: > > On 2021-02-07 7:32 pm, John Fawcett wrote: > >> On 07/02/2021 20:15, @lbutlr wrote: >>> On 07 Feb 2021, at 02:07, @lbutlr >> <mailto:krem...@kreme.com>> wrote: >>>> On 06 Feb 2021, at

Re: fts_encoder

On 08/02/2021 21:35, Joan Moreau wrote: > > Well, in the function xxx_build_more of FTS plugin, the data received > in the original PDF, not the output of pdftotext > > Can you clarify where do you put your log in the solr plugin , so I > can check the situation in the xapian plugin ? > I used the

Re: fts_encoder

On 08/02/2021 23:05, Stuart Henderson wrote: > On 2021/02/08 21:33, Joan Moreau wrote: >> Yes , once again : output of the decoder is fine, I also put log inide the >> dovecot core to >> check whether data is properly transmitted, and result is that it is (i.e. >> dovecot core >> receives the pro

Re: fts_encoder

On 09/02/2021 15:33, Joan Moreau wrote: > > If I place the following code in the plugin > fts_backend_xxx_update_build_more function (lucene, squat and xapian, > as solr refuses to work properly on my setup) > >         { >                 char * s = i_strdup("EMPTY"); >                 if(data !=

Re: fts_encoder

On 11/02/2021 14:25, Joan Moreau wrote: > > Hello > > Checking further, and putting logs a bit every where in the dovecot > code, the core is sending FIRST the initial document (not decoded) > then SECOND the decoded version > > Thisi is really weird, and the indexer then indexes a lot of binary cr

Re: Incorrect value sent to solr

On 07/04/2021 13:36, Łukasz Szczepański wrote: > I'm not as familiar with C, but I don't see in solr backed in dovecot > any  clue of subsequent queries for single mailbox lookup (which most > mail client uses). There is a hard limit of 10 rows for multiple > mailbox lookup. This was reported

Re: Incorrect value sent to solr

On 08/04/2021 08:02, Aki Tuomi wrote: > Hi! > Thanks for reminding us, I'll make a ticket about this to avoid forgetting it > again. > > Aki Thanks to you and the team for taking it into consideration! PS is this list the best way to post patch proposals or is it easier for you to get code from

Re: Can dovecot be leveraged to exploit Solr/Log4shell?

On 13/12/2021 23:43, Joseph Tam wrote: I'm surprised I haven't seen this mentioned yet. An internet red alert went out Friday on a new zero-day exploit. It is an input validation problem where Java's Log4j module can be instructed via a specially crafted string to fetch and execute code from a

Re: Can dovecot be leveraged to exploit Solr/Log4shell?

On 14/12/2021 03:23, Scott wrote: Is this assuming you log at some verbose level ? What if you log at WARN or higher ? For production it seems kind of silly to log search queries anyways. Scott It's a pretty much standard install where most things are at INFO level. Probably could turn it d

Re: Can dovecot be leveraged to exploit Solr/Log4shell?

On 15/12/2021 08:52, Aki Tuomi wrote: The suggested configuration is good, and although we did some checking to ensure that dovecot escapes the search queries and usernames sent to solr, so it is not trivial to send the JNDI expansion strings to be logged by solr, it is still good idea to set

Re: Error: fts_solr: received invalid uid

On 30/12/2021 19:14, oliver.kr...@snoog.ch wrote: I'm using dovecot 2.3.13,  solr 8.x. and roundcube 1.5.1. However when I do a search I get the the Error: fts_solr: received invalid uid, search results are ok. Thanks Presumably one of the uid returned from solr could not be decoded (i.e.

Re: Error: fts_solr: received invalid uid

On 02/01/2022 12:13, oliver.kr...@snoog.ch wrote: Here is what solr sends to dovecot, the offending uid in this exmaple is '21' {   "responseHeader":{     "status":0,     "QTime":1,     "params":{   "q":"body:Zeitserver"}},   "response":{"numFound":1,"start":0,"numFoundExact":true,"docs":[  

Re: Error: fts_solr: received invalid uid (John Fawcett)

On 03/01/2022 01:18, oliver.kr...@snoog.ch wrote: Hi John, You are right this was not a dovecot solr query. It is really strange everything seems to work with Dovecot 2.3.4. E.g. search and  rebuilding index from scratch using doveadm. As soon as I use version  2.3.13 things are getting wild:

Re: GDPR/sender-ip (was: make received-header on submission optional or at least drop the ip in it)

On 05/01/2022 14:41, dc...@dvl.werbittewas.de wrote: Am 04.01.22 um 08:39 schrieb Aki Tuomi: We'll take a look at your patch. Can you please point out to some legal information about the Received header's GDPR incompliance, I would be interested to see it. thanks for doing so. the GDPR sa

Re: GDPR/sender-ip (was: make received-header on submission optional or at least drop the ip in it)

On 05/01/2022 17:44, Marc wrote: Where people are sending email to public mailing lists, there is no presumption of privacy. I think the legislation is like this: the privacy is legislation is always applicable, there are no conditions under which there is 'no presumption of privacy' Marc

Re: GDPR/sender-ip

On 05/01/2022 18:27, dc...@dvl.werbittewas.de wrote: Am 05.01.22 um 18:00 schrieb John Fawcett: my understanding of the GDPR legislation is that it defines what is considered lawful processing. One of those items that makes the processing lawful is consent. If I send an email to a public

Re: GDPR/sender-ip (was: make received-header on submission optional or at least drop the ip in it)

On 05/01/2022 18:36, Sam Kuper wrote: On Wed, Jan 05, 2022 at 06:00:31PM +0100, John Fawcett wrote: my understanding of the GDPR legislation is that it defines what is considered lawful processing. One of those items that makes the processing lawful is consent. Not necessarily. An action that

Re: Doveadm auth test fails

On 06/01/2022 01:16, Ken Wright wrote: I've been having trouble logging into my email server (postfix 3.4.13, dovecot 2.3.7.2, postfixadmin 3.3.8). I decided to try the doveadm auth test, and got the following result: kwright@grace:~$ sudo doveadm auth test m...@mydomain.com Password: passdb: m

Re: Doveadm auth test fails

On 06/01/2022 04:20, Ken Wright wrote: On Thu, 2022-01-06 at 03:44 +0100, John Fawcett wrote: On 06/01/2022 01:16, Ken Wright wrote: I've been having trouble logging into my email server (postfix 3.4.13, dovecot 2.3.7.2, postfixadmin 3.3.8).  I decided to try the doveadm auth test, and go

Re: GDPR/sender-ip (was: make received-header on submission optional or at least drop the ip in it)

On 07/01/2022 14:01, Sam Kuper wrote: You say you cannot see it, but I gave an example below, in my previous email: Secondly, a person sending an email to a mailing list might very well consent for the mailing list's recipients to receive the content, subject, and reply address of that email

Re: TLS connection closed unexpectedly

On 07/01/2022 18:31, Ken Wright wrote: On Fri, 2022-01-07 at 10:02 +0100, Christian Kivalo wrote: On January 7, 2022 9:51:20 AM GMT+01:00, Ken Wright wrote: I reinstalled Dovecot this evening, because I haven't been able to receive emails recently.  After configuring and adjusting for the use

Re: TLS connection closed unexpectedly

On 07/01/2022 21:03, Ken Wright wrote: On Fri, 2022-01-07 at 18:50 +0100, John Fawcett wrote: it may or may not be related to the tls issue, but I think you will want to investigate that message about the SQL query syntax error. You are not going to be able to login if the query is giving

Re: Non-user logins?

On 08/01/2022 14:26, dc...@dvl.werbittewas.de wrote: Am 08.01.22 um 05:27 schrieb Dave McGuire: trying to mess with other peoples' stuff.  I run fail2ban to catch those log entries and block the source IP address for a month on the first failed login.  At any one time I have between 12,000 and

Re: banning, was Re: Non-user logins?

On 08/01/2022 17:22, Dave McGuire wrote: On 1/8/22 8:57 AM, John Fawcett wrote: yes, blocking on the first wrong password sounds like overkill. But it does depend on user base. For a small mail server with few known users it could be workable.   It may be overkill for your network, but it&#

Patch: assertion failed in doveadm fts lookup

Hi I'm reposting this patch, which I have been applying locally since I originally posted it. Hopefully it can be considered for inclusion in the official release. It was tested on dovecot 2.3.16 but applies against the latest version 2.3.17.1. This is the "assertion failed" that it addresse

Patch: safeguard against too large value for uid being sent to solr for single mailbox searches

Hi I'm reposting a patch for solr integration which I have been applying locally. It applies against 2.3.17.1. Dovecot already has a mechanism when doing solr fts searches on multiple mailboxes that prevents a too large value for maximum rows being sent to solr. #define SOLR_MAX_MULTI_ROWS

Patch: enhancements for solr/tika integration

Hi here's a patch with some enhancements that I am applying locally for solr/tika integration. Hopefully this can be considered for inclusion. I've tested up to 2.3.16 and this patch applies against latest version 2.3.17.1. The contents are: 1. Allow username and password in tika configurati

  1   2   3   >