unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Rainer M Krug <R.M.Krug@gmail.com>, notmuch@notmuchmail.org
Subject: Re: gmail label support patch available for oflineimap
Date: Mon, 26 Nov 2012 10:44:23 -0400	[thread overview]
Message-ID: <87zk24ctko.fsf@convex-new.cs.unb.ca> (raw)
In-Reply-To: <k8vn08$62g$2@ger.gmane.org>

Rainer M Krug <R.M.Krug@gmail.com> writes:

> there is a patch available for synching gmail labels to X-Keywords in
> the message (full thread see
> http://article.gmane.org/gmane.mail.imap.offlineimap.general/5943 ).
>
> Would notmuch be able to translate these X-Keywords into tags, so that
> one could use notmuch and it's tags as gmail uses the labels?

Reading tags from X-Keywords would be a Simple Matter of Programming
(TM), although you'd have to be sure you could trust that header as
injected by you and not some evil adversary.  There would also be some
questions about forwarding such messages (e.g. should the X-Labels be
stripped when forwarding).  

I expect there would be some resistance to writing X-Labels back to
message files, since having read-only message files is more or less a
design goal. 

In summary, it could probably be done, but I'm not sure it would be a
better approach than interfacing directly with gmail via their extended
IMAP interface.  Personally, if I was interested in solving this
problem, I'd be more interested in a solution that didn't wed me to
offline imap, if the two solutions were in the same rough ballpark of
effort. The direct method would also not modify mail messages. Still,
others might feel differently.

The notion of storing labels in messages has been mooted before as a
general synching solution. That might make it more interesting to me.

d

  reply	other threads:[~2012-11-26 14:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 12:23 gmail label support patch available for oflineimap Rainer M Krug
2012-11-26 14:44 ` David Bremner [this message]
2012-11-26 15:13   ` Rainer M Krug
2012-11-26 17:49     ` David Bremner
2012-11-27  9:21       ` Rainer M Krug
2012-11-27 17:00         ` Michal Nazarewicz
2012-11-27 19:07           ` Rainer M Krug
2012-11-27 19:24             ` Michal Nazarewicz
2012-11-27 19:32               ` Rainer M Krug
2012-11-27 20:01                 ` Michal Nazarewicz
2012-11-28  7:32                   ` Rainer M Krug
2012-11-28 10:10                     ` Felipe Contreras
2012-11-28 11:29                       ` Jani Nikula
2012-11-28 23:33                         ` Felipe Contreras
2012-11-29  5:01                           ` Jeremy Nickurak
2012-11-29  7:18                             ` Felipe Contreras
2012-11-29  9:02                               ` Rainer M Krug
2012-11-29 13:26                           ` Michal Nazarewicz
2012-11-28 12:53                       ` Michal Nazarewicz
2012-11-28 23:34                         ` Felipe Contreras
2012-11-29 13:24                           ` Michal Nazarewicz
2012-11-28 11:11               ` Tomi Ollila
2012-11-28 12:56                 ` Michal Nazarewicz
2012-11-28 16:45                   ` David Bremner
2012-11-28 18:39                     ` Michal Nazarewicz
2012-11-29  9:06                       ` Rainer M Krug

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=87zk24ctko.fsf@convex-new.cs.unb.ca \
    --to=david@tethera.net \
    --cc=R.M.Krug@gmail.com \
    --cc=notmuch@notmuchmail.org \
    /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).