From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] problems with Maildir and IMAP offline
Date: Tue, 14 Jul 2009 11:07:46 -0400 [thread overview]
Message-ID: <1247584002-sup-504@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <20090714150034.GA393@d228.scdc1.swarthmore.edu>
Excerpts from Tim Gray's message of Tue Jul 14 11:00:34 -0400 2009:
> > Again, see sup-sync-back -- it does indeed have _some_ ability to write
> > its state back to the source.
>
> To me, this is a vital feature of any mail client. I'll look into it, but I
> would really like this to be fully integrated into my mail client. And from
> I've read, this isn't something that's going to happen.
There was some talk a while back about modifying the behaviour of
Maildir sources. The issue was that there is an odd scanning bug with
Maildir that sometimes sees messages get skipped. A proposed solution
was to have sup start 'playing nice' with Maildir so that when new
messages were found in new/, they'd be indexed and recorded with a
filename in cur/, presumably with the S (seen) flag appended properly.
I _think_ William was looking at that, but I'm not sure. It's
something I'd like too (not to play nice with other clients, but
because it's "just better"). I haven't had much time lately, but if
William confirms he's not working on it, I'd be interested in
implementing it.
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090714/e30a5b14/attachment.bin>
next prev parent reply other threads:[~2009-07-14 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 21:20 Luis Cañas Díaz
2009-07-14 13:24 ` Andrei Thorp
[not found] ` <20090714134544.GD90157@d228.scdc1.swarthmore.edu>
2009-07-14 14:02 ` Andrei Thorp
2009-07-14 15:00 ` Tim Gray
2009-07-14 15:07 ` Ben Walton [this message]
2009-07-14 15:28 ` Tim Gray
2009-07-14 15:39 ` Andrei Thorp
2009-07-14 15:59 ` Tim Gray
2009-07-14 15:14 ` Andrei Thorp
2009-07-14 15:45 ` Tim Gray
2009-07-14 16:21 ` Israel Herraiz
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=1247584002-sup-504@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/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