From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Query for largest msg_id?
Date: Wed, 18 May 2011 05:05:27 +0000 [thread overview]
Message-ID: <1305694759-sup-7483@masanjin.net> (raw)
In-Reply-To: <BANLkTinBWgd2NYZqT+y8oHt9-_aiRjdcNA@mail.gmail.com>
Reformatted excerpts from Horacio Sanson's message of 2011-05-17:
> I implemented a new version of the GMail -> Heliotrope sync script and
> attach it here in hopes someone will test it and provide some
> feedback/comments.
Great! This is very exciting.
> - I am seeing some negative thread_id's in the response. Need to check
> if this is normal or a bug in Heliotrope or my script.
This is normal. It indicates a thread in which the root message can't be
found (so Heliotrope must construct a pseudo-message to hold the tree
together). Nothing to worry about, except as an indicator that you're
missing email refefred to by something else in the thread.
> - GMail inbox is with a capital "I" (e.g. Inbox) while heliotrope
> uses a small "i".
> Shall I down case all labels? or make a special treatment for Inbox?
I suggest special-casing inbox.
> To use this script I had to modify heliotrope-server.rb to allow
> setting labels and states when posting new messages (see attached
> patch).
I apologize for the confusion in this, but this is actually the wrong
endpoint to use. POST "/message" (no .json) is for adding new emails.
This endpoint was introduced temporarily for outgoing emails, i.e. when
you compose or reply via turnsole. But I'm going to rename it as well as
implement it.
Anyways, I've added the relevant code to /message, so your script should
work against that.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-05-18 5:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 15:17 Horacio Sanson
2011-05-15 15:01 ` William Morgan
2011-05-16 15:02 ` Horacio Sanson
2011-05-17 14:59 ` Horacio Sanson
2011-05-17 15:15 ` Horacio Sanson
2011-05-18 5:05 ` William Morgan [this message]
2011-05-20 15:38 ` Horacio Sanson
2011-05-22 22:00 ` William Morgan
2011-05-23 21:22 ` Hamish
2011-05-24 3:16 ` Horacio Sanson
2011-05-18 4:59 ` William Morgan
2011-05-18 20:09 ` Sascha Silbe
2011-05-19 3:14 ` Alvaro Herrera
2011-05-22 22:05 ` William Morgan
2011-05-23 7:52 ` Gaudenz Steinlin
2011-05-23 16:14 ` William Morgan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1305694759-sup-7483@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox