Re: [sup-devel] Query for largest msg_id?

From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Query for largest msg_id?
Date: Wed, 18 May 2011 23:14:00 -0400	[thread overview]
Message-ID: <1305774610-sup-7867@alvh.no-ip.org> (raw)
In-Reply-To: <1305748878-sup-7940@xo15-sascha.sascha.silbe.org>

Excerpts from Sascha Silbe's message of mié may 18 16:09:26 -0400 2011:
> Excerpts from William Morgan's message of Wed May 18 06:59:05 +0200 2011:
> > Reformatted excerpts from Horacio Sanson's message of 2011-05-16:
> > > When UIDVALIDITY differs I will simply re-scan the whole mailbox and
> > > feed it to Heliotrope. I trust Heliotrope won't add duplicates.
> > 
> 
> > The REST api will ignore duplicates based on the Message-Id header.
> 
> This is something I don't like about sup: There's no way to access the
> "duplicate" messages, e.g. to check whether an outgoing message was
> received back fine from the ML or to check the headers.
> 
> If heliotrope permanently erases the copies (instead of just not
> exposing UI to access them), that would be a major step backwards.

Same here.  I have this in detailed-headers.rb:

headers["Message Id"] = message.id
message.locations.each_with_index { |location, idx|
  headers["Location#{idx}"] = "#{location.source} #{location.info}"
}

So I can immediately see all locations of a message; particularly useful
for messages that I send.  I don't have easy access to the headers
within the sup UI, but the one or two times I've wanted to do that, I
simply pasted the path to the file to "less" (which works fine because I
use Maildirs; on mboxes it would be a lot more complex).

-- 
Álvaro Herrera <alvherre@alvh.no-ip.org>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel