Hello Denniss, I have backported imap4flags to 2.4.17. I backported 6 other patches to make backporting imap4flags easier. There has been no code review of these patch backports.
The code is available here: https://github.com/cyberpear/cyrus-imapd/commits/imap4flags-2.4 I tried to make sure the bytecode generated on 2.4 would be readable by 2.5, though not the other way around. I haven't tested this yet. I'd appreciate any reviews of the backported code. I'll probably send a pull request in a week or so for this code. V/r, James Cassell On Sat, Oct 25, 2014, at 10:40 AM, Deniss wrote: > hello James, > > thanks for implementing imap4flags sieve extension. > I'm looking to use the extension in production-ready 2.4 branch - > "hasflag" test allows to add some logic while the "variables" extension > is missed from cyrus. > Are there any caveats to backport imap4flags from master to 2.4 ? > > Best, > Deniss