From: bdwalton@gmail.com (Ben Walton)
Subject: [sup-talk] Sup with Microsoft Exchange 2007
Date: Mon, 4 May 2009 09:41:17 -0400 [thread overview]
Message-ID: <f96e0240905040641y5e2a5efetfacee48b8e4260d2@mail.gmail.com> (raw)
In-Reply-To: <1241441484-sup-8964@entry>
On Mon, May 4, 2009 at 8:59 AM, William Morgan <wmorgan-sup at masanjin.net> wrote:
> Reformatted excerpts from Ben Walton's message of 2009-04-30:
>> Since I'm back into mucking with this bit, are you open to having the
>> maildir scanning code move messages from new/ to cur/? This could
>> help with the unique id vs directory scanning issue.
>
> Would it really help? I'd be willing if so, but I don't see how. Maybe
> I'm missing something.
Scan both folders (cur/, new/) on startup or sup-sync. After that,
scan only new. Since mail is moved out of new/ into cur/ after
detection, the time stamp stuff could be dropped since it would be
redundant anyway. I think I'd confused myself about the id generation
issue, so it wouldn't likely be of benefit there.
> I've avoided moving new/ to cur/ because I didn't see any benefit to
> Sup, and it conflicts with the hands-off philosophy, so it just seemed
> like one more thing we could screw up. But if there is a real reason to
> do it, I'd probably be willing.
Sup would be a better Maildir citizen, since this is the intended way
to access/use a maildir source.
-Ben
--
---------------------------------------------------------------------------------------------------------------------------
Ben Walton <bdwalton at gmail.com>
"With or without religion, good people can behave well and bad people
can do evil; but for good people to do evil?that takes religion. "
-Steven Weinberg
---------------------------------------------------------------------------------------------------------------------------
next prev parent reply other threads:[~2009-05-04 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3f81a4240904140559ubd286a5x2f026d6b875dd091@mail.gmail.com>
2009-04-20 21:52 ` Bryan Richardson
2009-04-20 22:54 ` Mark Alexander
[not found] ` <3f81a4240904201638v94a7dbdpce0d865cd83d8873@mail.gmail.com>
2009-04-21 13:02 ` William Morgan
[not found] ` <3f81a4240904210642o9c74049o27e164e317d0842e@mail.gmail.com>
2009-04-21 13:48 ` Andrew Pimlott
2009-04-21 14:13 ` William Morgan
[not found] ` <3f81a4240904210729h74ac436bn9e1140cf7021c5ad@mail.gmail.com>
[not found] ` <3f81a4240904210732k11366cf7naec562af54ecabac@mail.gmail.com>
2009-04-21 14:37 ` Ben Walton
2009-04-29 22:45 ` William Morgan
2009-04-30 14:07 ` Ben Walton
2009-05-04 12:59 ` William Morgan
2009-05-04 13:41 ` Ben Walton [this message]
2009-05-04 16:22 ` 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=f96e0240905040641y5e2a5efetfacee48b8e4260d2@mail.gmail.com \
--to=bdwalton@gmail.com \
/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