R: Dovecot 2.3 shared namespace issues

Hello, My bad, the OS was ubuntu 20.04 and not 22.04 . After further tinkering\testing, it seems that removing the " acl_ignore_namespace = shared/* " setting did the trick, now we're getting the correct ACL on client side . Without it we can see the folder with the right permissions : Logging

Dovecot 2.3 shared namespace issues

Hello, We're trying to configure the shared mailbox feature\namespace on a dovecot 2.3 installation . OS : Ubuntu 22.04 x64 Dovecot : 2:2.3.19.1-2+ubuntu20.04 Our test enviroment is based on a dovecot frontend ( director + proxy ) and a dovecot backend ( auth and storage ), later we

Re: dovecot-2.3-pigeonhole-0.5.18 : Freebsd Will not build

You need to upgrade dovecot to 2.3.18. On Sun, Feb 20, 2022 at 10:43 PM Paul Kudla (Scom.ca Internet Services Inc.) wrote: > dovecot version : dovecot-2.3.14 > > > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com US

Re: Support of INDEXPVT in Dovecot 2.3 with replication

Thanks Aki :) Am 29.10.20 um 13:47 schrieb Aki Tuomi: > At the moment the correct way to use shared folders in a replication pair is > to access them with imapc from the other pair. Can you please elaborate a bit more? In 2.2 I could understand how that works, as INDEXPVT was not replicated,

Re: Support of INDEXPVT in Dovecot 2.3 with replication

At the moment the correct way to use shared folders in a replication pair is to access them with imapc from the other pair. Aki > On 29/10/2020 14:43 Ralf Becker wrote: > > > In reference to an earlier mail from me, I'd like to ask: > > Have there been any changes in regard to INDEXPVT and

Support of INDEXPVT in Dovecot 2.3 with replication

In reference to an earlier mail from me, I'd like to ask: Have there been any changes in regard to INDEXPVT and replication or are there any plans in that direction? Thanks :) Ralf On 03.08.20 at 11:20 Ralf Becker wrote: > So far the only thing we noticed: private seen flags on shared user >

Re: Best prometheus exporter for Dovecot 2.3 with the new metrics/stats module

> On 22/10/2020 12:18 Sidsel Jensen wrote: > > > Hi ppl. > > I am trying to locate the best prometheus exporter for use with Dovecot 2.3 > in connection with the new metrics/stats module. > Any pointers in the right direction will be appreciated - seems like

Best prometheus exporter for Dovecot 2.3 with the new metrics/stats module

Hi ppl. I am trying to locate the best prometheus exporter for use with Dovecot 2.3 in connection with the new metrics/stats module. Any pointers in the right direction will be appreciated - seems like there is a bunch out there which all works with the old stats module. Anybody have something

Re: Apple Mail Since upgrade to dovecot 2.3.x unable to connect

On Mon, 17 Aug 2020, Johannes Rohr wrote: You need to set ssl_min_protocol = TLSv1.2 # or TLSv1 Thanks, tried both, but unsuccessfully. Don't give up too easily/early on this. I said this before, but MacOSX Mail behaves weirdly. I've more than once changed a server setting, without

Re: Apple Mail Since upgrade to dovecot 2.3.x unable to connect

On 17 Aug 2020, at 05:10, Gerald Galster wrote: > I don't know how detailed this is in older Apple Mail versions I don't think the detail has changed in many many years, if at all. I remember using the logs to troubleshoot security issues 15 years ago. Mac OS 10.11 El Capitan was released in

Re: Apple Mail Since upgrade to dovecot 2.3.x unable to connect

Am 17.08.20 um 13:10 schrieb Gerald Galster: >>> You need to set >>> >>> ssl_min_protocol = TLSv1.2 # or TLSv1 >> Thanks, tried both, but unsuccessfully. Again, is there any debug >> setting that allows me to see what SSL version was requested? Without >> this, this is fumbling in the dark. > In

Re: Apple Mail Since upgrade to dovecot 2.3.x unable to connect

ssl_cert = This is wrong, it should be: ssl_cert = The address idaweb-mail.rooot.de does not resolve. There is a webmail.rooot.de , but its certificate is for mail.rooot.de , which is wrong. There is also a mail.rooot.de , whose certificate is also for mail.rooot.de , which is okay.

Re: Apple Mail Since upgrade to dovecot 2.3.x unable to connect

>> You need to set >> >> ssl_min_protocol = TLSv1.2 # or TLSv1 > > Thanks, tried both, but unsuccessfully. Again, is there any debug > setting that allows me to see what SSL version was requested? Without > this, this is fumbling in the dark. In the german version of Apple Mail go to menu

Re: Apple Mail Since upgrade to dovecot 2.3.x unable to connect

Am 17.08.20 um 12:16 schrieb Aki Tuomi: > You need to set > > ssl_min_protocol = TLSv1.2 # or TLSv1 Thanks, tried both, but unsuccessfully. Again, is there any debug setting that allows me to see what SSL version was requested? Without this, this is fumbling in the dark. Cheers, Johannes

Apple Mail Since upgrade to dovecot 2.3.x unable to connect

|Dear all,| |a couple of days ago I upgraded our server from Ubuntu 18.04 to 20.04, thereby upgrading dovecot from 2.2.x to 2.3.x. | |Since then, some older versions of apple's mail.app (bundled with el Capitano, released in 2016) no longer connect. When I turn on SSL debugging, I see:| |Debug:

Apple Mail Since upgrade to dovecot 2.3.x unable to connect

|Dear all,| |a couple of days ago I upgraded our server from Ubuntu 18.04 to 20.04, thereby upgrading dovecot from 2.2.x to 2.3.x. | |Since then, some older versions of apple's mail.app (bundled with el Capitano, released in 2016) no longer connect. When I turn on SSL debugging, I see:| |Debug:

Re: Director with dovecot 2.3 and Panic/Fatal error

> On 19/03/2020 17:02 Alessio Cecchi wrote: > > > > Hi, > > after the upgrade to Dovecot 2.3 for our director ring we found some times > in the log errors like this: > > Mar 18 14:22:51 Panic: imap-login: file iostream-openssl.c: line 599 > (openssl_

Director with dovecot 2.3 and Panic/Fatal error

Hi, after the upgrade to Dovecot 2.3 for our director ring we found some times in the log errors like this: Mar 18 14:22:51 Panic: imap-login: file iostream-openssl.c: line 599 (openssl_iostream_handle_error): assertion failed: (errno != 0) Mar 18 14:22:51 Fatal: imap-login: master: service

Re: Dovecot 2.3 repo for CentOS 8.

On 14 Feb 2020, at 10:59, Peter wrote: On 14/02/20 10:10 pm, Tobias Kirchhofer wrote: would it be useful/advisable to use this repo for productive operation? An official repo is still not available for CentOS 8 https://repo.dovecot.org/ We would like to set up our new mail server on

Re: Dovecot 2.3 repo for CentOS 8.

On 14/02/20 10:10 pm, Tobias Kirchhofer wrote: would it be useful/advisable to use this repo for productive operation? An official repo is still not available for CentOS 8 https://repo.dovecot.org/ We would like to set up our new mail server on CentOS 8 and are waiting… :) What is your

Re: Dovecot 2.3 repo for CentOS 8.

Hi Filip, On 12 Dec 2019, at 12:01, fil...@centrum.cz wrote: > Hello, > I have builded some dovecot packages for CentOS 8 in my personal > repository: > http://repo.joomhosting.eu/centos/8/x86_64/ > and SRPMS are in > http://repo.joomhosting.eu/centos/8/SRPMS/ > > I you want you can try it. > >

Re: Dovecot 2.3 repo for CentOS 8.

Agree > Il giorno 12 dic 2019, alle ore 10:47, Alexander Dalloz > ha scritto: > > Am 12.12.2019 um 11:31 schrieb Reio Remma: >> On 09/12/2019 17:25, Aki Tuomi via dovecot wrote: > On 09/12/2019 17:20 Reio Remma via dovecot wrote: >> >> [ ... ] >> >> I tried rebuilding the RPM for

Re: Dovecot 2.3 repo for CentOS 8.

Am 12.12.2019 um 11:31 schrieb Reio Remma: On 09/12/2019 17:25, Aki Tuomi via dovecot wrote: On 09/12/2019 17:20 Reio Remma via dovecot wrote: [ ... ] I tried rebuilding the RPM for CentOS 8 but I see it's missing some notable required packages like tcp wrappers and quota-devel. Managed to

Re: Dovecot 2.3 repo for CentOS 8.

On 12/12/2019 13:01, fil...@centrum.cz wrote: Hello, I have builded some dovecot packages for CentOS 8 in my personal repository: http://repo.joomhosting.eu/centos/8/x86_64/ and SRPMS are in http://repo.joomhosting.eu/centos/8/SRPMS/ I you want you can try it. With best regards, Filip Bartmann

Re: Dovecot 2.3 repo for CentOS 8.

Hello, I have builded some dovecot packages for CentOS 8 in my personal repository: http://repo.joomhosting.eu/centos/8/x86_64/ and SRPMS are in http://repo.joomhosting.eu/centos/8/SRPMS/ I you want you can try it. With best regards, Filip Bartmann On Thu, 12 Dec 2019 12:31:45 +0200 Reio Remma

Re: Dovecot 2.3 repo for CentOS 8.

On 09/12/2019 17:25, Aki Tuomi via dovecot wrote: On 09/12/2019 17:20 Reio Remma via dovecot wrote: Hello! Are there any plans for an official Dovecot repo for CentOS 8? Thanks, Reio (sorry for duplicate, user error in earlier one...) Yes. There are plans for the repo, unfortunately

Re: Dovecot 2.3 repo for CentOS 8.

> On 09/12/2019 17:20 Reio Remma via dovecot wrote: > > > Hello! > > Are there any plans for an official Dovecot repo for CentOS 8? > > Thanks, > Reio (sorry for duplicate, user error in earlier one...) Yes. There are plans for the repo, unfortunately there are still technical problems

Re: Dovecot 2.3 repo for CentOS 8.

> On 09/12/2019 17:20 Reio Remma via dovecot wrote: > > > Hello! > > Are there any plans for an official Dovecot repo for CentOS 8? > > Thanks, > Reio

Dovecot 2.3 repo for CentOS 8.

Hello! Are there any plans for an official Dovecot repo for CentOS 8? Thanks, Reio

Re: lmtp with non ASCII Parameters changed in dovecot 2.3

> mail from: > 500 5.5.2 Invalid command syntax this was a bad example. the problem is more common on rcpt to: if you deliver to usernames or special folders rcpt to:<üser> or rcpt to:

lmtp with non ASCII Parameters changed in dovecot 2.3

Hi, I updated from 2.2 to 2.3 and noticed lmtp rejects parameters containing non ASCII now. this worked with dovecot-2.2 lmtp. the string is already denied after reading in "smtp_command_parse_parameters()" mail from: 500 5.5.2 Invalid command syntax is there a plan to change this

Re: Dovecot 2.3 error, FreeBSD 12 in a jail

On Sat, 15 Jun 2019 at 07:12, David Mehler via dovecot wrote: > Hello, > > I'm trying to get Dovecot going on my system. It's a FreeBSD > 12.0-RELEASE system and it's running dovecot 2.3 via ports in a jail. > I'm getting the same error message(s) as in this bug report, which ha

Dovecot 2.3 error, FreeBSD 12 in a jail

Hello, I'm trying to get Dovecot going on my system. It's a FreeBSD 12.0-RELEASE system and it's running dovecot 2.3 via ports in a jail. I'm getting the same error message(s) as in this bug report, which has been marked as closed: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225078

CVE-2019-10691: JSON encoder in Dovecot 2.3 incorrecty assert-crashes when encountering invalid UTF-8 characters.

encoder in Dovecot 2.3 incorrecty assert-crashes when encountering invalid UTF-8 characters. This can be used to crash dovecot in two ways. Attacker can repeatedly crash Dovecot authentication process by logging in using invalid UTF-8 sequence in username. This requires that auth policy is enabled

Re: Dovecot 2.3 no longer accepts ssl_key_password

Op 15/01/2019 om 08:08 schreef Aki Tuomi: On 10.1.2019 6.53, Chris Kiakas wrote: Hit a little problem when I upgraded a system from FreeBSD 10.3 to 11.2. I did not receive any errors in the upgrade. The system is running 4 jails and everything seems to work except in Dovecot

Re: Dovecot 2.3 no longer accepts ssl_key_password

On 10.1.2019 6.53, Chris Kiakas wrote: > Hit a little problem when I upgraded a system from FreeBSD 10.3 to 11.2. I > did not receive any errors in the upgrade. The system is running 4 jails and > everything seems to work except in Dovecot dovecot-2.3.4_5 where when using > the exact same

Dovecot 2.3 no longer accepts ssl_key_password

Hit a little problem when I upgraded a system from FreeBSD 10.3 to 11.2. I did not receive any errors in the upgrade. The system is running 4 jails and everything seems to work except in Dovecot dovecot-2.3.4_5 where when using the exact same configuration which worked in 10.3 with the same

Re: dovecot 2.2/openssl 1.0 vs dovecot 2.3/openssl 1.1.1 ssl regression

h openssl 1.1.1. > >> > >> Currently I have both variants running with identical configs and certs > >> (the only differences are due to config syntax changes in dovecot 2.3), > >> so for example on both I have: > >> > >> ssl_ca = >> (this

Re: dovecot 2.2/openssl 1.0 vs dovecot 2.3/openssl 1.1.1 ssl regression

differences are due to config syntax changes in dovecot 2.3), so for example on both I have: ssl_ca = [dovecot 2.3+ does not provide intermediate CA cert to clients any more] 2.3.x announcements and upgrade wiki mention no such behaviour change, so I assume it is a regression. Now doing cat

Re: dovecot 2.2/openssl 1.0 vs dovecot 2.3/openssl 1.1.1 ssl regression

1.1.1. Currently I have both variants running with identical configs and certs (the only differences are due to config syntax changes in dovecot 2.3), so for example on both I have: ssl_ca = (this file contains

dovecot 2.2/openssl 1.0 vs dovecot 2.3/openssl 1.1.1 ssl regression

Hi. I'm considering dovecot migration from 2.2.36 run with openssl 1.0.2o to dovecot 2.3.3 run with openssl 1.1.1. Currently I have both variants running with identical configs and certs (the only differences are due to config syntax changes in dovecot 2.3), so for example on both I have

Re: Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

On 08.08.2018 10:55, Reuben Farrelly wrote: > > On 8/08/2018 5:29 pm, Thore Bödecker wrote: >> Hey, >> >> you mentioned that dovecot builds fine, but does "make check" also >> complete successfully with a glibc-2.28 build on a glibc-2.28 system? >> >> We have been seeing segfaults during "make

Re: Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

On 8/08/2018 5:29 pm, Thore Bödecker wrote: Hey, you mentioned that dovecot builds fine, but does "make check" also complete successfully with a glibc-2.28 build on a glibc-2.28 system? We have been seeing segfaults during "make check" and it seems the following patch was able to make the

Re: Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

Hey, you mentioned that dovecot builds fine, but does "make check" also complete successfully with a glibc-2.28 build on a glibc-2.28 system? We have been seeing segfaults during "make check" and it seems the following patch was able to make the testsuite run successfully. Just out of

Re: Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

On 08.08.2018 09:42, Reuben Farrelly wrote: > Hi, > > The link to the release notes seems should have an 'l' on the end: > > Try: https://www.sourceware.org/ml/libc-alpha/2018-08/msg3.html > > This with gdb: > > thunderstorm /usr/src/dovecot/dovecot-2.3/src/auth # gdb > /root

Re: Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

Hi, The link to the release notes seems should have an 'l' on the end: Try: https://www.sourceware.org/ml/libc-alpha/2018-08/msg3.html This with gdb: thunderstorm /usr/src/dovecot/dovecot-2.3/src/auth # gdb /root/dovecot-auth-crash/auth /root/dovecot-auth-crash/core.auth.29667 GNU gdb

Re: Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

out what was passed to crypt p sample[i].key p sample[i].salt the return value is, for some reason, an invalid pointer, which it really should not be. So you probably might want to raise this up with glibc developers too. Aki On 08.08.2018 06:54, Reuben Farrelly wrote: > Hi, > > Do

Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

Hi, Dovecot 2.3 (release and current -git) versions compile, but fail to run when compiled against glibc-2.28. This is what is logged on startup: Aug 8 08:24:39 thunderstorm.reub.net dovecot[569]: master: Dovecot v2.3.2.1 (0719df592) starting up for imap, lmtp, sieve, submission, sieve Aug

Re: dovecot 2.3.x, ECC and wildcard certificates, any issues

>> That is one of the reasons I do not bother since long with public CAs >> but rather deploy my own, including own OSCP responder. > May I ask, how you create a CA which is valid for clients without them > having to install your root cert? > > and CA trust in clients. Latter though could be

Re: dovecot 2.3.x, ECC and wildcard certificates, any issues

On 2018-07-30 19:45, ѽ҉ᶬḳ℠ wrote: > That is one of the reasons I do not bother since long with public CAs > but rather deploy my own, including own OSCP responder. May I ask, how you create a CA which is valid for clients without them having to install your root cert? Cheers, K. C. -- regards

Re: dovecot 2.3.x, ECC and wildcard certificates, any issues

t; >>>>> Aki >>>>> >>>>>> On 30 July 2018 at 20:05 David Mehler wrote: >>>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> Thanks, good news is that worked. Bad news is it all lo

Re: dovecot 2.3.x, ECC and wildcard certificates, any issues

18 at 20:05 David Mehler wrote: >>>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> Thanks, good news is that worked. Bad news is it all looks good which >>>>>> means I do not know hwhy my remote

Re: dovecot 2.3.x, ECC and wildcard certificates, any issues

; >> >>> Thanks, good news is that worked. Bad news is it all looks good which >> >>> means I do not know hwhy my remote clients can't get their email, >> >>> looked like from the logs it was that. >> >>> >> >>> Would 143 be b

Re: dovecot 2.3.x, ECC and wildcard certificates, any issues

wrote: >>>>> >>>>> >>>>> Hi, >>>>> >>>>> Thanks, good news is that worked. Bad news is it all looks good which >>>>> means I do not know hwhy my remote clients can't get their email, >>>>> looke

Re: dovecot 2.3.x, ECC and wildcard certificates, any issues

od news is that worked. Bad news is it all looks good which > >>> means I do not know hwhy my remote clients can't get their email, > >>> looked like from the logs it was that. > >>> > >>> Would 143 be better or 993 for the external clients? > >>&g

Re: dovecot 2.3.x, ECC and wildcard certificates, any issues

t worked. Bad news is it all looks good which >>> means I do not know hwhy my remote clients can't get their email, >>> looked like from the logs it was that. >>> >>> Would 143 be better or 993 for the external clients? >>> >>> Thanks. >>

Re: dovecot 2.3.x, ECC and wildcard certificates, any issues

clients can't get their email, >> looked like from the logs it was that. >> >> Would 143 be better or 993 for the external clients? >> >> Thanks. >> Dave. >> >> >> On 7/30/18, Aki Tuomi wrote: >> > >> >> On 30 July 2018 at 19:16 David Mehl

Re: dovecot 2.3.x, ECC and wildcard certificates, any issues

Aki Tuomi wrote: > > > >> On 30 July 2018 at 19:16 David Mehler wrote: > >> > >> > >> Hello, > >> > >> Does dovecot 2.3.x have any issues recognizing or using certificates > >> that are ECC and wildcard? I'm trying to switch my

Re: dovecot 2.3.x, ECC and wildcard certificates, any issues

n 30 July 2018 at 19:16 David Mehler wrote: >> >> >> Hello, >> >> Does dovecot 2.3.x have any issues recognizing or using certificates >> that are ECC and wildcard? I'm trying to switch my letsencrypt >> implementation from acme-client which does not suppo

Re: dovecot 2.3.x, ECC and wildcard certificates, any issues

> On 30 July 2018 at 19:16 David Mehler wrote: > > > Hello, > > Does dovecot 2.3.x have any issues recognizing or using certificates > that are ECC and wildcard? I'm trying to switch my letsencrypt > implementation from acme-client which does not support either

dovecot 2.3.x, ECC and wildcard certificates, any issues

Hello, Does dovecot 2.3.x have any issues recognizing or using certificates that are ECC and wildcard? I'm trying to switch my letsencrypt implementation from acme-client which does not support either of those capabilities to acme.sh which does. Since then external clients checking their email

Re: Lmtp issues on dovecot 2.3.x with big messages

) for LMTP. Stephan, I’m having the same issue with LMTP and large messages with dovecot 2.3.x. Can you tell me which commit fixes this issue? I looked through the GitHub commits, but it’s not clear to me which commit fixes this issue. I’d like to apply the patch and re-compile dovecot for my

Re: Lmtp issues on dovecot 2.3.x with big messages

issue with LMTP and large messages with dovecot 2.3.x. Can you tell me which commit fixes this issue? I looked through the GitHub commits, but it’s not clear to me which commit fixes this issue. I’d like to apply the patch and re-compile dovecot for my machines instead of having to downgrade

dovecot 2.3 on Ubuntu 18.04 LTS

Hello, I'm running dovecot 2.3 from repo.dovecot.org <http://repo.dovecot.org/> on ubuntu 16.04 LTS, and I'm wondering if there is a scheduled date for the release of the bionic package in that repository. The Ubuntu mainstream version is based on the 2.2 branch, which prevent us t

Re: Lmtp issues on dovecot 2.3.x with big messages

with dovecot 2.3.x. Can you tell me which commit fixes this issue? I looked through the GitHub commits, but it’s not clear to me which commit fixes this issue. I’d like to apply the patch and re-compile dovecot for my machines instead of having to downgrade to 2.2.35. This fix is currently pending

Re: Lmtp issues on dovecot 2.3.x with big messages

; > Working on a fix... > > Problem found. It is an explicit limit of 40Mb (for the 30Mb I saw in my > tests, there was also a base64 encoding I forgot about). > > Will fix both the unhelpful error and the fact that there should be no > limit (currently) for LMTP. > Stephan, I’m hav

Re: Lmtp issues on dovecot 2.3.x with big messages

Op 4/4/2018 om 11:38 PM schreef Stephan Bosch: > Op 4/4/2018 om 8:26 PM schreef Ricardo Machini Barbosa: >> Hello, >> >> After update dovecot to version 2.3.x, LMTP stopped to receive big messages >> ( > 45 MB ). >> Messages are being sent to dovecot LMTP by postfix. If I change this email >> to

Re: Lmtp issues on dovecot 2.3.x with big messages

Op 4/4/2018 om 8:26 PM schreef Ricardo Machini Barbosa: > Hello, > > After update dovecot to version 2.3.x, LMTP stopped to receive big messages > ( > 45 MB ). > Messages are being sent to dovecot LMTP by postfix. If I change this email > to another server with dovecot 2.2.x the same message are

Lmtp issues on dovecot 2.3.x with big messages

Hello, After update dovecot to version 2.3.x, LMTP stopped to receive big messages ( > 45 MB ). Messages are being sent to dovecot LMTP by postfix. If I change this email to another server with dovecot 2.2.x the same message are delivered immediately. Log with mail_debug = yes: Apr  4 13:36:13

Re: Dovecot 2.3 panic

Hi! Can you install debugging symbols and try get core? A backtrace would help a lot! https://dovecot.org/bugreport.html Aki On 29.03.2018 00:50, Martynas Bendorius wrote: > Dovecot version: 2.3.1 (happens with 2.3.x too) > OS: CentOS 7 64-bit > > Mar 28 16:29:24 lmtp(30383): Panic: file

Dovecot 2.3 panic

Dovecot version: 2.3.1 (happens with 2.3.x too) OS: CentOS 7 64-bit Mar 28 16:29:24 lmtp(30383): Panic: file lib-event.c: line 182 (event_pop_global): assertion failed: (event != NULL) Mar 28 16:29:24 lmtp(30383): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xcc7a4) [0x7fac7f5177a4]

Re: Bug in dovecot 2.3 virtual plugin

Hi there! I compiled dovecot from git on 5.2.2018. The id of the last commit is: $ git log --format="%H" -n 1 83b1300b96e753206f9226e3738a7ad9f5428a75 From https://github.com/dovecot/core.git There is a new error,  when i try to open a virtual folder for my archiv (almost 30.000 mails) in

Re: Bug in dovecot 2.3 virtual plugin

file? This >> should not have occured ofc but would be nice to know how it ended up >> here. >> >> Aki >> >>> On January 3, 2018 at 5:35 PM Jakobus Schürz >>> <wertsto...@nurfuerspam.de> wrote: >>> >>> >>> Hi ther

Re: Re: Bug in dovecot 2.3 virtual plugin

unicode sequence somehow. Can you send me a core file? This should not have occured ofc but would be nice to know how it ended up here. Aki On January 3, 2018 at 5:35 PM Jakobus Schürz <wertsto...@nurfuerspam.de> wrote: Hi there! I compiled dovecot 2.3 from git. Because there is already

Re: Dovecot 2.3 on CentOS 7.

On Fri, February 2, 2018 8:58 am, Reio Remma wrote: > What would be the preferred directory for storing all virtual mail > without modification to system files? on my Centos 7 Dovecit 2.2.32, as well as prior versions, I've always used /var/vmail/vmail1/dom.tld don't know about 'preferred',

Re: Dovecot 2.3 on CentOS 7.

--On Thursday, February 01, 2018 11:58 PM +0200 Reio Remma wrote: What would be the preferred directory for storing all virtual mail without modification to system files? I would guess something under /var/lib. If you plan to host multiple virtual servers, /srv might be

Re: Dovecot 2.3 on CentOS 7.

/system/dovecot.service.d/writable-home.conf [Service] ProtectHome=false maybe this helps? --- Aki Tuomi Dovecot oy Original message From: Reio Remma <r...@mrstuudio.ee> Date: 01/02/2018 21:44 (GMT+02:00) To: dovecot@dovecot.org Subject: Dovecot 2.3 on CentOS 7. Greetings

Re: Dovecot 2.3 on CentOS 7.

/etc/systemd/system/dovecot.service.d/writable-home.conf [Service]ProtectHome=false maybe this helps? ---Aki TuomiDovecot oy Original message From: Reio Remma <r...@mrstuudio.ee> Date: 01/02/2018 21:44 (GMT+02:00) To: dovecot@dovecot.org Subject: Dovecot 2.3 on Ce

Dovecot 2.3 on CentOS 7.

Greetings! I'm having a bit of trouble trying out Dovecot 2.3 on CentOS 7. Dovecot 2.2.33 works fine on the same system (same config as well, minus the SSL changes) but after upgrading to 2.3 I'm getting the following errors: Feb  1 21:30:18 localhost dovecot: imap(r...@bwo.mrstuudio.ee

Re: Error in virtual mailbox dovecot 2.3-devel maybe in mailcount

Hi! I didn't hear anything about this issue... the problem still persists (last build was 27.1.2018 from git ressources) Do you need more informations? jakob Am 12.01.2018 um 11:04 schrieb Jakobus Schürz: Hi there! I splitted my Mailarchiv to an extra namespace. Because i have some

Error in virtual mailbox dovecot 2.3-devel maybe in mailcount

Hi there! I splitted my Mailarchiv to an extra namespace. Because i have some Problems with the Archiv. I can open all Folders from Mailarchiv with dovecot. But i want to have a "all archives" Mailbox to search in all messages in only one virtual mailbox. Trying to open this virtual folder

Re: Bug in dovecot 2.3 virtual plugin

Hi! Now an error is back. I didn't change my configuration and get now this error, whily i try to refresh my thunderbird. I think it happens in a virtual folder again. Jän 11 01:29:19 aldebaran dovecot[11597]: imap-login: Login: user=, method=CRAM-MD5, rip=127.0.0.1, lip=127.0.0.1, mpid=5008,

Re: Bug in dovecot 2.3 virtual plugin

So hello back again! Am 05.01.2018 um 14:31 schrieb Jakobus Schürz: Am 05.01.2018 um 10:25 schrieb Aki Tuomi: This is a different bug, and I suspect it might be caused by virtual plugin. We'll look into it. Aki It was a problem with selfhealing the index... I deleted all my emails

Re: Bug in dovecot 2.3 virtual plugin

Good morning! I did more research on this error. The virtual mailboxes are working in two other accounts. The big difference to my account is, i have a lot (sub)mailboxes (about 430) and a lot emails in my account. The other accounts only have a few emails and mailboxes (5 or 6 standard,

Re: Dovecot 2.3 - using doveadm as non-root?

On Wed, 3 Jan 2018 13:37:07 -0500 Timo Sirainen wrote: > On 3 Jan 2018, at 11.38, Rob Hoelz wrote: > > > > Hi dovecot developers and users, > > > > I recently upgraded my server running Arch Linux to dovecot 2.3.0, > > and I noticed some of my cron jobs

Re: Bug in dovecot 2.3 virtual plugin

Am 05.01.2018 um 10:25 schrieb Aki Tuomi: This is a different bug, and I suspect it might be caused by virtual plugin. We'll look into it. Aki Ok! So the subject for this bug is (now) correct... I found out, that the count of mailboxes is not the problem. But the count of emails!! So i

Re: Bug in dovecot 2.3 virtual plugin

Does it always happen with 2.2 and 2.3? I was not immediately able to reproduce your problem. Aki On 05.01.2018 12:26, Jakobus Schürz wrote: > Ok! > So the subject for this bug is correct... > > Do you need some configs and deeper descriptions from me? > > I have two namespaces with virtual

Re: Bug in dovecot 2.3 virtual plugin

Ok! So the subject for this bug is correct... Do you need some configs and deeper descriptions from me? I have two namespaces with virtual mailboxes: The first "Real" is normally hidden. It's not hidden now for debug-purpose. namespace Real { hidden = no ignore_on_failure = yes list =

Re: Bug in dovecot 2.3 virtual plugin

This is a different bug, and I suspect it might be caused by virtual plugin. We'll look into it. Aki On 04.01.2018 23:41, Jakob Schürz wrote: > Hi! > > This is very strange... > This error affects only one mailaccount, and it happend not yesterday. > The file > >

Re: Bug in dovecot 2.3 virtual plugin

Hi! This is very strange... This error affects only one mailaccount, and it happend not yesterday. The file /var/lib/dovecot/db/indexes/Maildir/jakob/INBOX/dovecot.index which hat "Panic: Leaked view for index" does not exist. only dovecot.index.log and .cache exists in this mailbox. (which is

Re: Bug in dovecot 2.3 virtual plugin

Hi! Is this a bug according to the other one? When i try to open a real or virtual mailbox, i often (not on every mailbox) get this error-message: Jän 04 11:03:32 aldebaran dovecot[24534]: imap(jakob)<24705>: Panic: Leaked view for index

Re: Dovecot 2.3 - using doveadm as non-root?

On 3 Jan 2018, at 11.38, Rob Hoelz wrote: > > Hi dovecot developers and users, > > I recently upgraded my server running Arch Linux to dovecot 2.3.0, and I > noticed some of my cron jobs started issuing me error messages. These > cron jobs run as a non-root user

Dovecot 2.3 - using doveadm as non-root?

Hi dovecot developers and users, I recently upgraded my server running Arch Linux to dovecot 2.3.0, and I noticed some of my cron jobs started issuing me error messages. These cron jobs run as a non-root user associated with my mail account, and they use doveadm to tidy things up (ex. purging

Re: Bug in dovecot 2.3 virtual plugin

pam.de> > wrote: > > > Hi there! > > I compiled dovecot 2.3 from git. Because there is already a bug in > virtual-plugin, and i hoped, it get fixed... but it doesn't. So this > is the error-message from the log > > Jän 03 16:27:08 aldebaran dovecot[26460]:

Bug in dovecot 2.3 virtual plugin

Hi there! I compiled dovecot 2.3 from git. Because there is already a bug in virtual-plugin, and i hoped, it get fixed... but it doesn't. So this is the error-message from the log Jän 03 16:27:08 aldebaran dovecot[26460]: indexer-worker(jakob)<26476>

ssl_curve_list seems to be ignored with Dovecot 2.3

Hi all, after upgrading to Dovecot 2.3, I've noticed the new "ssl_curve_list" TLS option in 10-ssl.conf. Setting it to "ssl_curve_list = X25519:P-256" or leaving it blank (auto) does not change anything, Dovecot keeps on negotiating P-384: Server Temp Key: ECDH, P-384,

Re: Dovecot 2.3-rc Logging Format

Op 12/21/2017 om 8:57 AM schreef Thomas Leuxner: > Hi, > > the release candidate defaults to a log format with session IDs. > > mail_log_prefix = "%s(%u)<%{pid}><%{session}>: " > > As the LMTP service seems to have the session ID hardcoded, the IDs get > duplicated in the logs: > > Dec 21

Re: Dovecot 2.3-rc1 SMTP submission proxy always gives TLS required error even when already using TLS

On 2017-12-22 11:22, Michael Marley wrote: > On 2017-12-21 16:48, Stephan Bosch wrote: > > Op 12/18/2017 om 9:44 PM schreef Michael Marley: > > First of all, I apologize for my accidental empty message earlier. > > I just set up the SMTP submission proxy in Dovecot 2.3,

Re: Dovecot 2.3-rc1 SMTP submission proxy always gives TLS required error even when already using TLS

On 2017-12-21 16:48, Stephan Bosch wrote: > Op 12/18/2017 om 9:44 PM schreef Michael Marley: > >> First of all, I apologize for my accidental empty message earlier. >> >> I just set up the SMTP submission proxy in Dovecot 2.3, but whenever I >> try to connect

Re: Dovecot 2.3-rc Logging Format

> On December 21, 2017 at 9:57 AM Thomas Leuxner wrote: > > > Hi, > > the release candidate defaults to a log format with session IDs. > > mail_log_prefix = "%s(%u)<%{pid}><%{session}>: " > > As the LMTP service seems to have the session ID hardcoded, the IDs get >

  1   2   >