From: Daniel Schoepe <daniel.schoepe@googlemail.com>
To: Sebastian Spaeth <Sebastian@sspaeth.de>,
Sander Boer <sanderboer@mauc.nl>
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch Digest, Vol 20, Issue 57
Date: Mon, 11 Jul 2011 15:33:50 +0200 [thread overview]
Message-ID: <87vcv90wn5.fsf@gilead.invalid> (raw)
In-Reply-To: <8762n9x88f.fsf@SSpaeth.de>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
On Mon, 11 Jul 2011 15:22:24 +0200, Sebastian Spaeth <Sebastian@sspaeth.de> wrote:
> > Support for tags is mentioned in the RFC for IMAP, but it's optional. As
> > far as I know, must servers today support them though.
>
> I can't speak for Gmail, but all major servers, ie Cyrus, Dovecot, and
> even Exchange seem to handle tags just fine.
I just realized that this was a quite misleading typo, that should have
read "As far as I know, _most_ servers today support them though".
I'd be very suprised if Gmail didn't support them. And even if not, one
could work around that by having a hypothetical tag synchroniser handle
Gmail differently and use their tagging mechanism:
http://code.google.com/apis/gmail/imap/#x-gm-labels
This would also have the added benefit of notmuch tags showing up in the
other gmail-tag-aware applications, like the web-interface.
Another issue brought up by DraX on IRC is that IMAP keywords don't
handle unicode. (Although the RFC specifies that every character except
some excluded special characters are allowed, so I guess it's
implementation-dependent).
I think the best way to go would be to extend both maildir and
offlineimap somehow to store tags and then store them as IMAP keywords /
gmail-labels in the case of Gmail on the server.
Cheers,
Daniel
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
prev parent reply other threads:[~2011-07-11 13:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1309146869.12973.notmuch@notmuchmail.org>
2011-06-27 7:43 ` notmuch Digest, Vol 20, Issue 57 Sander Boer
2011-06-28 20:22 ` Carl Worth
2011-06-28 21:43 ` Sander Boer
2011-06-28 22:38 ` Mark Anderson
2011-06-28 23:53 ` Carl Worth
2011-06-29 20:21 ` Mark Anderson
2011-06-29 20:54 ` Jameson Graef Rollins
2011-06-29 22:19 ` Mark Anderson
2011-06-30 7:15 ` Pieter Praet
2011-06-28 22:42 ` Mark Anderson
2011-06-30 7:24 ` Sebastian Spaeth
2011-07-06 18:31 ` Sander Boer
2011-07-06 18:46 ` Daniel Schoepe
2011-07-11 13:22 ` Sebastian Spaeth
2011-07-11 13:33 ` Daniel Schoepe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vcv90wn5.fsf@gilead.invalid \
--to=daniel.schoepe@googlemail.com \
--cc=Sebastian@sspaeth.de \
--cc=notmuch@notmuchmail.org \
--cc=sanderboer@mauc.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).