Can you please be sure? There has been some LDAP compilation fixes with 2.4.2
I sent another message yesterday evening, in French - brain fart.
I checked the problem arises by compiling 2.4.2 tag on pigeonhole
project against the 2.4.2 tag on the core one.
I tried 2.4.2 after being unable to build 2.4.1, which is the version I
am involved with.
My problem is, the instance I am trying to solve the problem on is
running the Debian stable package, still on 2.4.1.
The facts that 2.4.1 contains such a bug, and that *both* 2.4.1 & 2.4.2
tags are not buildable in their current state are serious obstacles.
What I am seeking for is a fix, backportable to v2.4.1, which could end
up in an update to said package.
At the moment I am getting emails ending up being rejected on accounts
impacted by this bug, as a consequence to their processing constantly
failing.
I tried cherry-picking some commits, without having reached a buildable
state.
After many attempts on different directions, and overall a lot of time
spent into this, I am still facing dead ends.
Here are the questions I am left with:
1. Would it be possible to fix 2.4.1 so it is buildable?
2. Is a 2.4.1 fix regarding default sieve storage envisioned?
Bernard Rosset
_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
