Gnus development mailing list
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: ding@gnus.org
Subject: Re: nnmaildir vs offlineimap: patch to use flags properly
Date: Sun, 26 Aug 2012 17:53:12 +0200	[thread overview]
Message-ID: <871uitbqfr.fsf@toke.dk> (raw)
In-Reply-To: <m2wr0pyzui.fsf@gmail.com>

Magnus Henoch <magnus.henoch@gmail.com> writes:

> But it seems like nobody saw it, so I'm making some noise here.  What do
> you think about the patch?

I've tried it out, and from my initial testing it appears to work quite
well. I've been using a script to sync the flags back and forth on every
run of offlineimap, which is sort of hit and miss. As in, there have
been a few mails that are not updated. I think this has to do with the
renaming of filenames that offlineimap does to keep track of files. So I
had a bunch of mails that were not marked with the S flag, but which
gnus considered to be seen. When enabling your patch, those turned up
again, and I did not seem to be able to mark them as read. Marking them
externally (in this case using Mutt) did seem to clear everything up
though, and new mails are marked correctly. Moving mails around between
folders also seems to work. I'll keep using this for a few days and see
if anything odd turns up.

Other than that, many thanks for writing this patch; I've been bothered
by this for a while, but not enough to do something about it. I don't
suppose there's any way to sync/store expired flags in the same way? I
seem to be able to add an E flag to mails in my maildir, and offlineimap
syncs it to the server, but then it seems to be discarded; at least it's
removed by offlineimap on the next sync. I'm afraid I don't know enough
about the imap protocol to know whether this is just because my imap
server is rubbish, or whether it's expected protocol behaviour...

-Toke

-- 
Toke Høiland-Jørgensen
toke@toke.dk




  parent reply	other threads:[~2012-08-26 15:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 23:04 Magnus Henoch
2012-08-25 12:53 ` poirier
2012-08-26 15:53 ` Toke Høiland-Jørgensen [this message]
2012-08-27 11:38   ` Toke Høiland-Jørgensen
2012-08-28  8:55     ` Magnus Henoch
2012-08-28  9:35       ` Toke Høiland-Jørgensen
2012-08-30  0:08         ` Toke Høiland-Jørgensen
2012-09-02 23:39           ` Toke Høiland-Jørgensen
2012-08-28  8:33   ` Magnus Henoch
2012-08-28  9:34     ` Toke Høiland-Jørgensen
2012-09-04 19:52 ` Lars Ingebrigtsen
2012-09-05  8:20   ` Magnus Henoch

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=871uitbqfr.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).