From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.142.241.17 with SMTP id o17cs37114wfh; Tue, 17 May 2011 22:28:48 -0700 (PDT) Received: by 10.52.73.232 with SMTP id o8mr2108277vdv.228.1305696527418; Tue, 17 May 2011 22:28:47 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id z34si843731vbl.88.2011.05.17.22.28.46; Tue, 17 May 2011 22:28:46 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id E62EF3C808D for ; Wed, 18 May 2011 01:28:45 -0400 (EDT) Received: from masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id EF64E18583AF for ; Wed, 18 May 2011 00:58:02 -0400 (EDT) Received: from w by masanjin.net with local (Exim 4.71) (envelope-from ) id 1QMYwp-0007lG-MO for sup-devel@rubyforge.org; Wed, 18 May 2011 05:05:27 +0000 From: William Morgan To: sup-devel In-reply-to: References: <1305471101-sup-6655@masanjin.net> Date: Wed, 18 May 2011 05:05:27 +0000 Message-Id: <1305694759-sup-7483@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-devel] Query for largest msg_id? X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org 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 _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel