similar to: Email blocking emails

Hello, running dovecot 2.3.2.1 on Arch Linux, and installed solr 7.4.0. According to the wiki, there should be doc/solr-schema.xml, but I cannot find it. Tried "whereis dovecot": dovecot: /usr/bin/dovecot /usr/lib/dovecot /etc/dovecot /usr/include/dovecot /usr/share/dovecot /usr/share/man/man1/dovecot.1.gz But I cannot find any xml files using find /usr/{lib,share}/dovecot -name

Hello, cannot fetch mails from an IMAP folder because of the error in the subject - fetching always stops with SIGABRT. Could anybody help me, please? Kind regards Peter

Hello, from time to time I keep getting problems with some emails causing signal 6. I've already reported those, but it seems not to be easy to find the cause. From the logs, it seems to occur in sieve implementation. I've checked the email envelopes tody by accident, probably this part of my telnet session might help: a11 fetch 1 all * 1 FETCH (RFC822.SIZE 16750 INTERNALDATE

> On December 29, 2017 at 2:56 AM Gao <gao at pztop.com> wrote: > > > On 2017-12-27 07:00, aki.tuomi at dovecot.fi wrote: > > Dovecot now has package repository for Debian, CentOS and Ubuntu > > available at https://repo.dovecot.org/ > > > > Packages are provided for 2.3 series and forward. Please let us know > > if you run into any trouble with

Am 30.10.18 um 13:37 schrieb Stephan Bosch: > > > Op 28-10-2018 om 23:28 schreef Peter Nabbefeld: >> Hello, >> >> cannot fetch mails from an IMAP folder because of the error in the >> subject - fetching always stops with SIGABRT. >> >> Could anybody help me, please? > > We need more information than that: > > - Your configuration and

Hello, I've got a problem fetching my emails using getmail. First question is, of course, what's causing the problems. I'm going to think that getmail get's an error code from dovecot when trying to connect and just signals the most common error, so it seems to be a problem with dovecot. Sorry but I cannot upload any files with the silly web interface of my provider, so I cannot

On 8 May 2017, at 17.14, Reuben Farrelly <reuben-dovecot at reub.net> wrote: > >>>>> On 28/04/2017 7:27 PM, Reuben Farrelly wrote: >>>>>> This has been broken for the last few days: >>>>>> >>>>>> libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s

> On 15/08/2019 00:34 Eugene via dovecot <dovecot at dovecot.org> wrote: > > > The next combination of parameters makes 100% LDAP connections unsuccessful (the log snippet form the previous mail). > sasl_bind = yes > sasl_mech = gssapi > tls = yes > > Looks like this combination is utterly incorrect and should be prohibited (tls must not be used when mech is

Hello, I've never used gdb, so I don't know why I'm running into problems using "gdb bt". Usually, I'm fetching my mail using "sudo -E getmail", but this doesn't seem to work with backtrace. :-/ Output from "dovecot -n" attached. Kind regards, Peter -------------- next part -------------- # 2.3.6 (7eab80676): /etc/dovecot/dovecot.conf #

Thank You, Jakub. As there's no link in the wiki, I just expected to find the file in the installation. Kind regards Peter Am 27.07.2018 um 16:13 schrieb Jakub L?nsk?: > Here? > https://github.com/dovecot/core/blob/master-2.3/doc/solr-schema.xml

Am 17.02.19 um 18:27 schrieb Sami Ketola: > > >> On 17 Feb 2019, at 11.47, Peter Nabbefeld via dovecot >> <dovecot at dovecot.org> wrote: >> >> >> Is there any tool displaying an "effective" config tree (i.e., a tool >> displaying the resulting configuration from every file, displaying >> the original file and line number)?

I suspect the problem is that dovecot tries to report LDAP error over GSSAPI. So the best fix is to make sure your LDAP server does not return error. =) Aki On 15.8.2019 14.56, Eugene Bright wrote: > That's right. > GSS-API is not used anywhere else. > Do you like to inspect my full configuration? > I can dump connection session and send pcap file here. > > On August 15,

Am 18.02.19 um 11:34 schrieb Sami Ketola: > >> On 18 Feb 2019, at 12.15, Peter Nabbefeld <peter.nabbefeld at gmx.de> wrote: >> >> >> >> Am 17.02.19 um 18:27 schrieb Sami Ketola: >>> Easy way is to use just one config file. That is what I have done for years. >>> >>> Sami >>> >>> >> I'd preferred that,

Hello, I've got a very strange problem: When I try to configure the stats-writer socket, I'm told the configuration is a duplicate, though none exists in the configuration files. So I'd guess the configuration is set either built-in or implicitly. I've put the following into conf.d/10-master.conf: service auth { ? unix_listener auth-userdb { ? } ? unix_listener stats-writer

On 25/05/2020 12:06, Aki Tuomi wrote: >> On 25/05/2020 13:00 Peter Nabbefeld <peter.nabbefeld at gmx.de> wrote: >> >> >> Hello, >> >> from time to time I keep getting problems with some emails causing >> signal 6. I've already reported those, but it seems not to be easy to >> find the cause. From the logs, it seems to occur in sieve

Hello, When I look at email files on my server (mdbox format), they contain random LZ4 stuff. I have now changed the compression to gzip and new mails look cleaner. But older ones have problems. A mail file looks like this: 2 M1e C5655b6a8 ^A^BN 00000000000006F4 Dovecot-LZ4^M*<9B><C5>^@^A^@^@^@^@^F<DD><FF><83>Return-path: <nobody at

Am 17.02.19 um 14:45 schrieb Aki Tuomi: >> On 17 February 2019 at 11:47 Peter Nabbefeld via dovecot <dovecot at dovecot.org> wrote: >> >> >> >> Hello, >> >> I've got a very strange problem: >> When I try to configure the stats-writer socket, I'm told the >> configuration is a duplicate, though none exists in the configuration

On Sun, May 10, 2015 at 08:16:54PM -0400, Darik Horn wrote: > > LZ4 is supposed > > to be a very fast compression algorithm, especially when it comes to > > decompression. I did a quick benchmark with zlib, LZO and LZ4. Now, > > there are many benchmarks you can find online, but most of them deal > > with compressing large files. Tinc on the other hand has to

Hi, In continuation to the issue I had posted about long back: http://www.dovecot.org/list/dovecot/2014-August/097362.html I did further testing today on a fresh new Debian & latest Dovecot and observed a undesired behavior. I am using fts_lucene & following sequence of commands on a empty test account me at myself.com: doveadm expunge -u 'my at myself.com' mailbox

Good Morning, I tried using gdb, but that doesn't work for me: $ ulimit -c unlimited $ sudo systemctl restart dovecot $ sudo -E getmail getmail version 5.13 Copyright (C) 1998-2019 Charles Cazabon.? Licensed under the GNU GPL version 2. SimpleIMAPSSLRetriever:peter.nabbefeld at gmx.de@imap.gmx.net:993: getmailrc: operation error (child pid 19702 killed by signal 6) ? 1 messages (12551