Thanks for letting me know!
On 8/12/2021 5:29 AM, Aki Tuomi wrote:
And now it's fixed. See
https://github.com/dovecot/core/commit/13830767a0e3bf29ad421ed656a89345346d6c8d
Aki
On 09/08/2021 07:53 Aki Tuomi wrote:
Yes, it's a bug. It's being tracked by us.
Aki
On 28/07/2021 07:56 ean3
Hey,
I have MariaDB 10.5.10 and Dovecot 2.3.14.1 right now but it's broken
since a few months already. I don't remember when it started and what
versions I had running of both.
As stated in the subject, the Dovecot auth-worker looses connection
during a MySQL/MariaDB restart, which is ok so fa
Hey Christian,
This resolves the issue, thank you. You are also correct in that it is stated
here:
https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/#different-certificates-per-ip-and-protocol
I didn't realize it was also applicable to TLS SNI, but I should have tested.
Reg
On August 16, 2021 3:03:22 AM GMT+02:00, sil...@datavenia.nl wrote:
>Hello,
>
>
>
>I’ve tried implementing TLS SNI for my Postfix/Dovecot setup. I have it
>working in Postfix, but this example for Dovecot:
>https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/#with-client-tl
Hello,
I’ve tried implementing TLS SNI for my Postfix/Dovecot setup. I have it working
in Postfix, but this example for Dovecot:
https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/#with-client-tls-sni-server-name-indication-support
doesn’t seem to work for me.
I’m usi
On 2021/08/16 13:32, Timo Sirainen wrote:
> On 13. Aug 2021, at 19.10, Stuart Henderson wrote:
> > I get "i_stream_read_memarea: assertion failed: (!stream->blocking)" when
> > accessing some messages. Backtrace and doveconf -n below.
>
> Does the attached patch fix it?
It does - thank you.
On 13. Aug 2021, at 19.10, Stuart Henderson wrote:
> I get "i_stream_read_memarea: assertion failed: (!stream->blocking)" when
> accessing some messages. Backtrace and doveconf -n below.
Does the attached patch fix it?
diff
Description: Binary data
Hi everyone. I have global sieve rules that can create mailboxes
automatically by using "fileinto :create
some/mailbox/that/does/not/exist".
The emails are delivered to dovecot using lmtp and I can see the
mailboxes created just fine.
Is there a way to configure all new mailboxes created by those s
On 14.08.21 20:37, @lbutlr wrote:
> On 2021 Aug 13, at 11:11, dove...@ptld.com wrote:
>> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.ch;
>> s=protonmail; t=1628873196;
>> bh=HCYF6+sDiqNN6f9T2srf/HEjnr5eJacuoNxBWXk1XJA=;
>> h=Date:To:From:Cc:Reply-To:Subject:In-