From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup-sync & missing message-ids
Date: Tue, 24 Jul 2007 10:56:01 -0700 [thread overview]
Message-ID: <1185299593-sup-1596@south> (raw)
In-Reply-To: <20070723174809.GA6866@electricrain.com>
Excerpts from Dan Sully's message of Mon Jul 23 10:48:09 -0700 2007:
> For whatever reason, there are messages in my Maildir that don't have
> message-ids in their headers. sup-sync bitches about that rather
> loudly.. would it be better to artificially construct a message-id?
If this really is a prevalent thing, then yes, I'm happy to fake a
message-id.
> Also, in the playing well with others category - sup doesn't seem to
> handle the case where a message gets moved from Maildir/new/ to
> Maildir/cur/ if that folder is read via IMAP from another client.. is
> this fixable in sup, or part of the rubymail library?
This has nothing to do with RubyMail; Sup simply doesn't play well with
other clients. Part of the tradeoff I made with Sup was to assume by
default that the source never changes except through Sup. If that
assumption fails, Sup should detect it and ask you to run sup-sync
--changed, which should bring everything back in sync.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-07-24 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 17:48 Dan Sully
2007-07-24 17:56 ` William Morgan [this message]
2007-07-24 18:13 ` Dan Sully
2007-07-25 0:05 ` 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=1185299593-sup-1596@south \
--to=wmorgan-sup@masanjin.net \
/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