Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: alec@thened.net (Alec Berryman)
Subject: [sup-talk] Initial import does not preserve read/unread status
Date: Sun, 17 Aug 2008 14:59:15 -0400	[thread overview]
Message-ID: <20080817185915.GA17717@thened.net> (raw)
In-Reply-To: <1218597196-sup-3699@entry>

William Morgan on 2008-08-12 20:14:09 -0700:

> Reformatted excerpts from Alec Berryman's message of 2008-08-10:
> > When I imported a new maildir source with a mix of read and unread
> > messages (in the cur or new subfolder, respectively), all of the
> > messages were marked unread.  Is the documentation wrong or is this a
> > bug?  I hope it's a bug.
>
> Weird. Can you provide some sample filenames for read and unread
> messages? (Since that's how Maildir keeps state---it might be there's
> some naming variant that Sup doesn't know about.)

Sure (ls -R output; maildir attached; samples from sup-talk):

sup-does-not-import-read-messages-as-read/:
cur/
new/
tmp/

sup-does-not-import-read-messages-as-read/cur:
1218394528_0.8381.barry,U=23205,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
1218397749_0.16026.barry,U=23207,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
1218405160_1.1978.barry,U=23211,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
1218413059_0.23982.barry,U=23215,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,RS
1218413717_1.26111.barry,U=23216,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
1218626652_4.3870.barry,U=23368,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
1218626652_5.3870.barry,U=23369,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S

sup-does-not-import-read-messages-as-read/new:
1218626652_2.3870.barry,U=23366,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe

sup-does-not-import-read-messages-as-read/tmp:


When I import this folder with sup, I see all messages marked as new,
but I only expect to see 1.  The maildir names are generated by
offlineimap.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sup-does-not-import-read-messages-as-read.tar.bz2
Type: application/octet-stream
Size: 6635 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080817/485a2391/attachment-0001.obj>


      reply	other threads:[~2008-08-17 18:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-10 23:53 Alec Berryman
2008-08-11  0:13 ` Alec Berryman
2008-08-13  3:14 ` William Morgan
2008-08-17 18:59   ` Alec Berryman [this message]

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=20080817185915.GA17717@thened.net \
    --to=alec@thened.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