130664b622
as opposed to earlier threats, BerkDB was not entirely dropped; i suppose the isync 0.7 -> 0.8 change had a reason, so i added an alternative UID storage scheme. note that BDB 4.0 is not sufficient, as the db->open function changed in an incompatible way ... i updated the debian packaging except for a changelog entry. note that i removed the upgrade blurb, as upstream now has a smooth upgrade path down to at least isync 0.4.
52 lines
2.2 KiB
Plaintext
52 lines
2.2 KiB
Plaintext
make SSL certificate validation more automatic.
|
|
|
|
add asynchronous operation to remote mailbox drivers. this is actually
|
|
what prevents us from simply using c-client and thus becoming mailsync.
|
|
|
|
handle custom flags (keywords).
|
|
|
|
fix maildir_{open_store,list} to handle partial names (last char not slash).
|
|
|
|
add a way to automatically create and sync subfolders.
|
|
|
|
could store TUID even when UIDPLUS is supported. would avoid duplicated
|
|
messages after abort before new UID arrives.
|
|
|
|
decouple TUID search from append. that's a prerequisite for usable
|
|
MULTIAPPEND, and is generally good for async. should be way faster, too,
|
|
as it saves repeated mailbox rescans with single-file formats.
|
|
|
|
use MULTIAPPEND and FETCH with multiple messages.
|
|
|
|
create dummies describing MIME structure of messages bigger than MaxSize.
|
|
flagging the dummy would fetch the real message. possibly remove --renew.
|
|
|
|
don't SELECT boxes unless really needed; in particular not for appending,
|
|
and in write-only mode not before changes are made.
|
|
|
|
possibly request message attributes on a per-message basis from the drivers.
|
|
considerations:
|
|
- record non-existing UID ranges in the sync database, so IMAP FETCHes needn't
|
|
to exclude anyway non-existing messages explicitly.
|
|
- when detect unborn pairs and orphaned messages being gone? implied by expunge:
|
|
with trashing, by local driver, or of messages we deleted in this run. the
|
|
remaining cases could be handled by automatic periodical cleanup passes, an
|
|
explicit --cleanup action, or be implied by one of the other actions.
|
|
- the benefit of this is questionable, as fine-grained requests will result
|
|
in sending huge amounts of data, and upstream is often way slower than
|
|
downstream.
|
|
|
|
maildir: possibly timestamp mails with remote arrival date.
|
|
|
|
maybe throw out the ctx->recent stuff - it's used only for one info message.
|
|
|
|
possibly use ^[[1m to highlight error messages.
|
|
|
|
consider alternative trash implementation: trash only messages we delete,
|
|
and trash before marking them deleted in the mailbox. downside: all other
|
|
programs have to do the same. and what if the deleted flag is unset?
|
|
|
|
items out of scope of purely UID based approach:
|
|
- detect message moves between folders
|
|
- recovering from UIDVALIDITY change (uw-imap does this a lot)
|