similar to: Dovecot 2.3.7 - char "-" missing

Hi, i have a problem with libclucene-core.so.2.3.3.4. I See segfault error to messages log, when dovecot store mail to INBOX. set 12 13:41:21 box02.par-tec.it kernel: doveadm-server[20285]: segfault at 38 ip 00007f575b68fc42 sp 00007ffc0272e750 error 4 in libclucene-core.so.2.3.3.4[7f575b569000+188000] set 12 13:41:22 box02.par-tec.it kernel: doveadm-server[18871]: segfault at 38 ip

Hi, I have other information. I analyzed the core dump: (gdb) core 22534 [New LWP 22534] Reading symbols from /usr/libexec/dovecot/doveadm-server...Reading symbols from /usr/lib/debug/usr/libexec/dovecot/doveadm-server.debug...done. done. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by

Hi Stephan, thanks for your replay. This is bt full output: (gdb) bt full #0 clear (this=0x0) at /usr/src/debug/clucene-core-2.3.3.4/src/core/CLucene/util/VoidMap.h:123 No locals. #1 lucene::search::FieldSortedHitQueue::_shutdown () at /usr/src/debug/clucene-core-2.3.3.4/src/core/CLucene/search/FieldSortedHitQueue.cpp:60 No locals. #2 0x00007f7dc5eabe96 in _lucene_shutdown () at

Op 16-9-2019 om 11:53 schreef Domenico Pastore via dovecot: > > Hi, > > I have other information. > > I analyzed the core dump: > > (gdb) core 22534 > [New LWP 22534] > Reading symbols from /usr/libexec/dovecot/doveadm-server...Reading > symbols from > /usr/lib/debug/usr/libexec/dovecot/doveadm-server.debug...done. > done. > [Thread debugging using

Hi, do you have the same problem with lucene? I collected a strace on the dovecot process during indexing: [pid 31339] execve("/usr/libexec/dovecot/doveadm-server", ["dovecot-devel01/doveadm-server"], [/* 18 vars */] <unfinished ...> [pid 30711] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=30932, si_uid=0, si_status=SIGSEGV, si_utime=3, si_stime=1} ---

Hi, I have an issue with dovecot 2.3.7.2. When lmtp stores a message into INBOX, I get this error: 2019-10-29 16:32:53 lmtp(?test at XXXX?)<28874><4IPiEytbuF3KcAAAioI89A>: Error: sieve: Execution of script /config/dovecot/common/default.sieve was aborted due to temporary failure 2019-10-29 16:32:53 lmtp(?test at XXXX?)<23470>: Error: sieve:

Hello, I have Dovecot configured with Solr for the indexes. I have need your support for upgrade solr 7.7.2 to 8.4.1. Solr 7.7.2 has a security issue CVE-2019-12409. It's possible upgrade of Solr? Dovecot work correctly with Solr 8.x? The Solr documentation recommended after updating: "It is always strongly recommended that you fully reindex your documents after a major version

Hi, thanks for your answer. I confirm, mitigate this issue is very very easy. There are other issues with high severity for example CVE-2019-17558. Description: Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter I think for this issue there is only a solution, upgrade Solr to 8.4. It's Correct? So, with Dovecot is it possible

Hi, during the store of the messages, I find the following doveadm errors: 2019-10-02 09:22:19 auth: Debug: ldap(test.pop at test.xxx.it,10.11.47.60<mailto:test.pop at test.xxx.it,10.11.47.60>): result: mailMessageStore=1/1/2/0/8/7/2/1120872_91093 mailQuota=52428800; mailQuota,mailMessageStore unused 2019-10-02 09:22:19 auth: Debug: ldap(test.pop at

On Wed, Aug 22, 2018 at 09:54:44AM -0400, Felipe Gasper wrote: > If you don?t want to use the HTTP API, you can use the raw doveadm protocol. > > https://wiki.dovecot.org/Design/DoveadmProtocol > > -FG Thanks, I didn't know about that. I suppose testing the HTTP API and then switching to the raw doveadm protocol over TCP if it turns out "crashy" wouldn't mean

In future release we will add master authentication too. Now you can use api key or doveadm password which are essentially same thing. ---Aki TuomiDovecot oy-------- Alkuper?inen viesti --------L?hett?j?: Peter Chiochetti <pch at myzel.net> P?iv?m??r?: 4.3.2016 20.20 (GMT+02:00) Saaja: dovecot at dovecot.org Aihe: Re: v2.2.22 release candidate released Am 2016-03-04 um 14:33 schrieb Timo

Hi, I'm doing quota checks from a remote machine (the real setup is a bit more complex, if necessary I can explain it in more detail, but I just extracted the bits that are easily reproduceable) # nc backend1 24245 VERSION doveadm-server 1 0 PLAIN agrVMDvHgz0ya2HHzax5svwB2ZHS? + heiko quota get But since the backend is upgraded to 2.2.22 it's not

Hello, I?m sending doveadm ?kick? commands to doveadm-server via the doveadm protocol. When ?kick? sends back a NOTFOUND error, though, it?s sending back additional output. strace shows: write(3<UNIX:[3158354->3156665]>, "\t\tkick\tmyssltest\n", 17) = 17 ... read(3<UNIX:[3158354->3156665]>, "\n-NOTFOUND\n\n-\n", 8192) = 14 Going by the protocol

Hi, I'm running 2.2.34 in production (installed from Debian stretch backports) and want to rework some scripts. Can the HTTP API be considered stable in 2.2.34 please? The wiki says it is "considered experimental in v2.2.22" so I thought I'd check before writing API calls rather than a wrapper around doveadm! -- James Beck Andrews & Arnold Ltd Tel: 03333 400999

On 12/3/2016 2:53 PM, Aki Tuomi wrote: > >> On December 3, 2016 at 11:16 PM Vijay Sarvepalli <vijay at ericavijay.net> wrote: >> >> >> Is there a simple way to get each mailbox size using dovecot's IMAP >> interface? The GETQUOTAROOT and GETQUOTA seems to work with the full >> maildir size and not the individual folders. >> >> I am

Hi all! We are bringing out HTTP API for doveadm-server in master HEAD. This feature is experimental, and can be expected to have bugs in it and might not always work. If you feel like trying it out though, you can enable it in your configuration file: doveadm_api_key = some-string service doveadm { inet_listener http { port = 8080 } } To use the API, you can go to

On 23.08.18 15:35, Felipe Gasper wrote: > >> On Aug 23, 2018, at 8:14 AM, James Beck <james.beck at aa.net.uk> wrote: >> >>> On Wed, Aug 22, 2018 at 09:54:44AM -0400, Felipe Gasper wrote: >>> If you don?t want to use the HTTP API, you can use the raw doveadm protocol. >>> >>> https://wiki.dovecot.org/Design/DoveadmProtocol >>>

Hi, Thanks for the reply. I guess RHEL choose v2.2.10 <http://dovecot.org/list/dovecot-news/2013-December/000268.html> as it is a good release with all the things working. My source of confusion are from 1) http://dovecot.org/oldnews.html I have gone through each release update news. Lots of work and bug fix after v2.2.10

http://dovecot.org/releases/2.2/dovecot-2.2.22.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.22.tar.gz.sig + Added doveadm HTTP API: See http://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP + virtual plugin: Mailbox filtering can now be done based on the mailbox metadata. See http://wiki2.dovecot.org/Plugins/Virtual + stats: Added doveadm stats reset to reset global stats. + stats:

http://dovecot.org/releases/2.2/dovecot-2.2.22.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.22.tar.gz.sig + Added doveadm HTTP API: See http://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP + virtual plugin: Mailbox filtering can now be done based on the mailbox metadata. See http://wiki2.dovecot.org/Plugins/Virtual + stats: Added doveadm stats reset to reset global stats. + stats: