From: Sascha Silbe <sascha-ml-reply-to-2011-2@silbe.org>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Query for largest msg_id?
Date: Wed, 18 May 2011 22:09:26 +0200 [thread overview]
Message-ID: <1305748878-sup-7940@xo15-sascha.sascha.silbe.org> (raw)
In-Reply-To: <1305693289-sup-4896@masanjin.net>
[-- Attachment #1.1: Type: text/plain, Size: 771 bytes --]
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.
Sascha
--
http://sascha.silbe.org/
http://www.infra-silbe.de/
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-05-18 21:05 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
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 [this message]
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=1305748878-sup-7940@xo15-sascha.sascha.silbe.org \
--to=sascha-ml-reply-to-2011-2@silbe.org \
--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