On Mon, 2011-06-27 at 13:22 +0100, David Woodhouse wrote:
> On Mon, 2011-05-23 at 16:55 +0400, James Bottomley wrote:
> > 
> > I kid you not.
> > 
> > You can see this just by going to your own outlook web server (when you
> > highlight a message, you'll see an empty tall oblong, click and it will
> > bring up the categories).
> > 
> > Exchange allows arbitrary labels (like we do), but the default ones are
> > Blue, Green, Orange, Purple, Red and Yellow.  Evolution has label
> > mappings for everything apart from Yellow.  I figured we should map
> > default to default.
> I don't really like mapping 'Red' to 'Important', etc.

I was just doing a mapping of what seems to be intended.  This is also
what the imap camel plugin does (except it maps $label1 <-> important

> Given that we support arbitrary labels on both sides, I think the best
> solution is to synchronise the set of labels. If we see a label on an
> Exchange message which isn't already known in Evolution, *add* it to
> Evolution's list. And if we're trying to add a label to an Exchange item
> which isn't already known on the Exchange side, add it there too.

I don't think we can ... at least it's an invasive change.  There
doesn't seem to be a way to show arbitrary labels.  The plugins have a
label map, which is partly provider supplied and partly user supplied
(if the provider allows user labels).  If the imap server comes across a
label it doesn't have a map for, it just ignores it ... This keeps
biting me because I use a custom patch label in my mailboxes for my git
workflow.  When I move to a new machine, I always have a "WTF where are
my patches" moment ... until I remember to add the label mapping.


evolution-hackers mailing list
To change your list options or unsubscribe, visit ...

Reply via email to