[PATCH/FEATURE] Per-user XLIST support for cyrus-imapd

[Bron Gondwana]

On Tue, Apr 30, 2013, at 05:20 PM, Thomas Jarosch wrote:
> Hi Bron,
> 
> On Tuesday, 30. April 2013 08:53:24 Bron Gondwana wrote:
> > Hi - have you looked at all at the special-use support in mainline Cyrus?
> > 
> > The xlist-* behaviour is planned to be removed, in favour of using the RFC
> > 6154 mandated annotation.
> > 
> > The implementation in git at the moment doesn't quite match the standard,
> > because I wrote it before the RFC was released, but I have a branch which
> > makes it fully compatible.  I wrote to this list just the other day asking
> > about it!
> 
> Eduardo is innocent, we (=Intra2net) needed support for this :)
> We didn't upgrade to 2.4.x yet, so we needed to develop
> this for 2.3.16 anyway.

Fair enough!  Hopefully you'll be interested in moving to 2.5 once that's out.

What are your main blockers to moving to 2.4?  I suspect the reindexing IO
his is a major factor, and something I'd like to solve (by delaying the
inevitable really... there are enough cache format changes that reindexing
will be necessary at some point - but stopping the storm is important)

> As far as I understood it, Outlook 2013 does not implement the RFC properly.
> Or did I miss something? That's the thing we are trying to solve here.
> Problem is you can't configure the sent mail folders manually anymore. Grrr.

I'm not certain actually - I'd have to have a look at your patches.  I know
some clients expect to see flags in response to normal LIST commands as well,
which is annoying - but we added an option to always return them, even to
regular LIST.

> > Do you have any other interesting patches you're working on that would be
> > good to include?  I don't want to get people too hooked on the xlist-*
> > hack, because it was only a stopgap before the RFC came out.
> 
> That's it for the moment.

Fair enough.  Honestly, I'm really not complaining at all - just sorry to see
duplicate work :)  I can see why you needed it though.

I have no problem with people doing their own things.  We had our own separate
notifications framework which we were running at FastMail for over a year
before the eventsource stuff got merged upstream and we dropped our patches
in favour of rewriting our notifdy to be an eventsource listener instead.
Competing development is good.

In this particular case, the only reason I'm not interested in your patches
instead of my own work is that I really want to allow the /shared/specialuse
annotation to work rather than hard coding folder names in imapd.conf - and
the reason I want THAT is because we need to support localisation of folder
names pretty soon, and hence the xlist-* trick won't work any more.

Besides, standards are good if they provide everything you need.

Thanks for your contributions, and for making them available.  Maybe they'll
be useful to other people who aren't ready for 2.4/2.5 yet :)

Regards,

Bron.

-- 
  Bron Gondwana
  brong at fastmail.fm