I was able to find some time to debug this more, and I found the change that
breaks it was introduced in 2.2.25:
If I revert 18856082d632ac60996637547098688148826b5a from release-2.2.25
branch, the test works again.
John
-Original Message-
From: dovecot [mailto:dovecot-boun...@dovecot.o
On 26.10.2016 15:30, Arkadiusz Miśkiewicz wrote:
On Wednesday 26 of October 2016, Arkadiusz Miśkiewicz wrote:
What can be done to make it work and how?
Don't know internals - but could dovecot do similar job as exim. I mean keep
big config, store things as strings just like now:
local_nam
On Wednesday 26 of October 2016, Arkadiusz Miśkiewicz wrote:
> What can be done to make it work and how?
Don't know internals - but could dovecot do similar job as exim. I mean keep
big config, store things as strings just like now:
local_name imap.example.com {
ssl_cert =
On 26.10.2016 13:48, Christian Ehrhardt wrote:
Hi,
I was wondering about a crash when building dovecot 2.2.25 on latest
Ubuntu.
I wondered as I've had the same source building on Debian just fine.
Some debugging led me to this weird behavior:
Using this gdb command file called autoreportissu
Hi.
Little story :-)
I'm playing with dovecot 2.2.25 and multiple SSL certificates. ~7000
certificates
which are loaded twice, so my dovecot has ~14 000 certificate pairs
(14k key + 14k cert) in config.
14 000 local_name entries. Like these:
local_name imap.example.com {
ssl_cert =
On 26 Oct 2016, at 11:14, Luis Ugalde wrote:
>
> Hi,
>
> Could you please have a look at https://lkml.org/lkml/2016/2/2/538 and see
> if this makes any sense to you? I've been checking kernel changes
> between linux_3.16.7 and linux_3.16.36, and this has popped out. Could this
> be the reason f
Hello,
- Set up a pair of servers according to http://wiki2.dovecot.org/Replication
-Enabled SSL for both servers
- Dovecot version: 2.2.13 (Debian 8.6)
I couldn't find an option to specify the certificate that doveadm should
use when connecting to the other server. Both servers have hostnames
Hi,
Could you please have a look at https://lkml.org/lkml/2016/2/2/538 and see
if this makes any sense to you? I've been checking kernel changes
between linux_3.16.7 and linux_3.16.36, and this has popped out. Could this
be the reason for the "too many references" errors?
Regards,
Luis Ugalde.
2016-10-26 8:57 GMT+02:00 Aki Tuomi :
> If you are moving from 1.x to 2.x, I think you should make some trials
> first, and preferably move the user one at a time, blocking access to
> old server/new server during move. It is very forklift upgrade, much danger.
Yes, I'll do some test migration bef
