On 8.7.2019 14.54, Tom Sommer via dovecot wrote:
>
> On 2019-07-08 13:36, Tom Sommer via dovecot wrote:
>> I rotate logs every night on my Director, running "doveadm log reopen"
>
> It happens on "/etc/init.d/dovecot restart", not "doveadm log reopen"
> - sorry
>
> So it happens when you run
No ETA yet.
Aki
On 7.7.2019 1.12, Martynas Bendorius via dovecot wrote:
> Hello,
>
> Is there any ETA set for JMAP support?
>
> Thank you!
>
>>> On 11/27/2016 5:28 AM, Aki Tuomi wrote:
>>> Hi!
>>> We are working on including JMAP support to Dovecot. At this moment I
>>> cannot give any promise
On 9.7.2019 3.02, Joseph Tam via dovecot wrote:
>
> Hopefully, there is some fix for issue 3 which is beyond my
> skill to fix.
>
> Issue 1) Need recent gcc version
>
> Building Dovecot versions <=2.2.x using gcc 3.4.4 worked,
> but this gcc version fails to build 2.3.x properly:
Hopefully, there is some fix for issue 3 which is beyond my
skill to fix.
Issue 1) Need recent gcc version
Building Dovecot versions <=2.2.x using gcc 3.4.4 worked,
but this gcc version fails to build 2.3.x properly: symptoms
include compile failures and executable
Hello Aki,
Thanks for looking into these.
I will as requested attempt the relevant procedures under Dovecot
2.3.6.
To make the test fair, I will need to fork the relevant production
groupware stack (which is now stable and in operation, with our
enterprise (email) data successfully migrated
On 2019-07-08 13:36, Tom Sommer via dovecot wrote:
I rotate logs every night on my Director, running "doveadm log reopen"
It happens on "/etc/init.d/dovecot restart", not "doveadm log reopen" -
sorry
So it happens when you run killproc on dovecot
---
Tom
On 2019-07-08 13:36, Tom Sommer via dovecot wrote:
I rotate logs every night on my Director, running "doveadm log reopen"
I've noticed a problem with processes not closing correctly, they can
be open for days and cause corrupt index files because they are
connected to different backends (so
I rotate logs every night on my Director, running "doveadm log reopen"
I've noticed a problem with processes not closing correctly, they can be
open for days and cause corrupt index files because they are connected
to different backends (so it writes to the wrong server when the process
