lobo/isync
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
isync/TODO

91 lines
3.9 KiB
Plaintext
Raw Permalink Normal View History

add option to control amount of fsync()ing
2012-09-15 13:15:22 +00:00
f{,data}sync() usage could be optimized by batching the calls.
update TODO
2017-10-01 12:37:36 +00:00
automatically resume upon transient errors, e.g. "connection reset by peer"
or timeout after some data was already transmitted.
possibly also try to handle Exchange's "glitches" somehow.
add socket timeout handling
2015-04-06 14:49:33 +00:00
uidvalidity lock timeout handling would be a good idea.
pre-release doc updates
2013-12-08 21:29:15 +00:00
update TODO
2017-10-01 12:37:36 +00:00
should complain when multiple Channels match the same folders.
update TODO remove items: - the "Unidentified socket error" should be gone since 7ba7be111 - imap_commit_cmds() is implemented since cfaa4848d - we will never use MULTIAPPEND and FETCH BODY with multiple messages, as that would significantly complicate matters for no tangible benefit ... and add some new thoughts. the idea to use strings of colons for quoting patterns doesn't work, as colons in "regular" patterns could not be quoted.
2021-12-24 11:56:02 +00:00
should complain about nonsensical combinations like Sync Pull + Create Both.
update TODO
2017-10-01 12:37:36 +00:00
propagate folder deletions even when the folders are non-empty.
- verify that "most" of the folders in the Channel are still there.
- refuse to delete unpropagated messages when trashing on the remote side.
deprecate master/slave terminology the underlying metaphor refers to an inhumane practice, so using it casually is rightfully offensive to many people. it isn't even a particularly apt metaphor, as it suggests a strict hierarchy that is counter to mbsync's highly symmetrical mode of operation. the far/near terminology has been chosen as the replacement, as it is a natural fit for the push/pull terminology. on the downside, due to these not being nouns, a few uses are a bit awkward, and several others had to be amended to include 'side'. also, it's conceptually quite close to remote/local, which matches the typical use case, but is maybe a bit too suggestive of actually non-existing limitations. the new f/n suffixes of the -C/-R/-X options clash with pre-existing options, so direct concatenation of short options is even less practical than before (some suffixes of -D already clashed), but doing that leads to unreadable command lines anyway. as with previous deprecations, all pre-existing command line and config options keep working, but yield a warning. the state files are silently upgraded.
2020-07-22 17:44:26 +00:00
- refuse to delete far side if it has unpropagated messages. symmetry?
update TODO
2017-10-01 12:37:36 +00:00
update TODO remove items: - the "Unidentified socket error" should be gone since 7ba7be111 - imap_commit_cmds() is implemented since cfaa4848d - we will never use MULTIAPPEND and FETCH BODY with multiple messages, as that would significantly complicate matters for no tangible benefit ... and add some new thoughts. the idea to use strings of colons for quoting patterns doesn't work, as colons in "regular" patterns could not be quoted.
2021-12-24 11:56:02 +00:00
add option to suppress complaints about folders that would need creation
(but not deleted ones).
pre-release doc updates
2013-12-08 21:29:15 +00:00
add message expiration based on arrival date (message date would be too
unreliable). MaxAge; probably mutually exclusive to MaxMessages.
add alternative treatments of expired messages. ExpiredMessageMode: Prune
(delete messages like now), Keep (just don't sync) and Archive (move to
separate folder - ArchiveSuffix, default .archive).
more to do
2010-02-06 09:48:11 +00:00
update TODO
2017-10-01 12:37:36 +00:00
add support for event notification callbacks.
deprecate master/slave terminology the underlying metaphor refers to an inhumane practice, so using it casually is rightfully offensive to many people. it isn't even a particularly apt metaphor, as it suggests a strict hierarchy that is counter to mbsync's highly symmetrical mode of operation. the far/near terminology has been chosen as the replacement, as it is a natural fit for the push/pull terminology. on the downside, due to these not being nouns, a few uses are a bit awkward, and several others had to be amended to include 'side'. also, it's conceptually quite close to remote/local, which matches the typical use case, but is maybe a bit too suggestive of actually non-existing limitations. the new f/n suffixes of the -C/-R/-X options clash with pre-existing options, so direct concatenation of short options is even less practical than before (some suffixes of -D already clashed), but doing that leads to unreadable command lines anyway. as with previous deprecations, all pre-existing command line and config options keep working, but yield a warning. the state files are silently upgraded.
2020-07-22 17:44:26 +00:00
make it possible to have different mailbox names for far and near side in
update TODO
2017-10-01 12:37:36 +00:00
Patterns.
deprecate master/slave terminology the underlying metaphor refers to an inhumane practice, so using it casually is rightfully offensive to many people. it isn't even a particularly apt metaphor, as it suggests a strict hierarchy that is counter to mbsync's highly symmetrical mode of operation. the far/near terminology has been chosen as the replacement, as it is a natural fit for the push/pull terminology. on the downside, due to these not being nouns, a few uses are a bit awkward, and several others had to be amended to include 'side'. also, it's conceptually quite close to remote/local, which matches the typical use case, but is maybe a bit too suggestive of actually non-existing limitations. the new f/n suffixes of the -C/-R/-X options clash with pre-existing options, so direct concatenation of short options is even less practical than before (some suffixes of -D already clashed), but doing that leads to unreadable command lines anyway. as with previous deprecations, all pre-existing command line and config options keep working, but yield a warning. the state files are silently upgraded.
2020-07-22 17:44:26 +00:00
- use far:near for the pattern
update TODO remove items: - the "Unidentified socket error" should be gone since 7ba7be111 - imap_commit_cmds() is implemented since cfaa4848d - we will never use MULTIAPPEND and FETCH BODY with multiple messages, as that would significantly complicate matters for no tangible benefit ... and add some new thoughts. the idea to use strings of colons for quoting patterns doesn't work, as colons in "regular" patterns could not be quoted.
2021-12-24 11:56:02 +00:00
- supporting names with colons requires and extension of the parser to
report which parts of an argument were quoted
update TODO
2017-10-01 12:37:36 +00:00
- this makes Groups mostly useless, as they are mostly a workaround for this
function being missing so far
- this is needed for move detection, which would work only within one Channel
update TODO remove items: - the "Unidentified socket error" should be gone since 7ba7be111 - imap_commit_cmds() is implemented since cfaa4848d - we will never use MULTIAPPEND and FETCH BODY with multiple messages, as that would significantly complicate matters for no tangible benefit ... and add some new thoughts. the idea to use strings of colons for quoting patterns doesn't work, as colons in "regular" patterns could not be quoted.
2021-12-24 11:56:02 +00:00
- this supersedes MapInbox
update TODO
2017-10-01 12:37:36 +00:00
pre-release doc updates
2013-12-08 21:29:15 +00:00
add regexp-based mailbox path rewriting to the drivers. user would provide
expressions for both directions. every transformation would be immediately
verified with the inverse transform. PathDelimiter and Flatten would become
special cases of this.
more to do
2010-02-06 09:48:11 +00:00
add daemon mode. primary goal: keep imap password in memory.
also: idling mode.
update
2004-09-08 16:37:36 +00:00
more to do
2010-02-06 09:48:11 +00:00
parallel fetching of multiple mailboxes.
update TODO
2017-10-01 12:37:36 +00:00
TLS session resumption becomes interesting then as well.
more to do
2010-02-06 09:48:11 +00:00
update TODO remove items: - the "Unidentified socket error" should be gone since 7ba7be111 - imap_commit_cmds() is implemented since cfaa4848d - we will never use MULTIAPPEND and FETCH BODY with multiple messages, as that would significantly complicate matters for no tangible benefit ... and add some new thoughts. the idea to use strings of colons for quoting patterns doesn't work, as colons in "regular" patterns could not be quoted.
2021-12-24 11:56:02 +00:00
imap_set_msg_flags() & imap_trash_msg(): group commands for efficiency.
more to do
2010-02-06 09:48:11 +00:00
add streaming from fetching to storing.
update TODO remove items: - the "Unidentified socket error" should be gone since 7ba7be111 - imap_commit_cmds() is implemented since cfaa4848d - we will never use MULTIAPPEND and FETCH BODY with multiple messages, as that would significantly complicate matters for no tangible benefit ... and add some new thoughts. the idea to use strings of colons for quoting patterns doesn't work, as colons in "regular" patterns could not be quoted.
2021-12-24 11:56:02 +00:00
this is complicated by the IMAP target needing the final size in advance,
which we can't know in a single pass when newline translation is necessary.
more to do
2010-02-06 09:48:11 +00:00
The Big Rewrite. too many change to list them all. 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.
2004-03-27 16:07:20 +00:00
handle custom flags (keywords).
update TODO remove items: - the "Unidentified socket error" should be gone since 7ba7be111 - imap_commit_cmds() is implemented since cfaa4848d - we will never use MULTIAPPEND and FETCH BODY with multiple messages, as that would significantly complicate matters for no tangible benefit ... and add some new thoughts. the idea to use strings of colons for quoting patterns doesn't work, as colons in "regular" patterns could not be quoted.
2021-12-24 11:56:02 +00:00
this is impeded by there being no Maildir-side standard.
more to do ...
2003-02-27 18:41:54 +00:00
pre-release doc updates
2013-12-08 21:29:15 +00:00
make use of IMAP CONDSTORE extension (rfc4551; CHANGEDSINCE FETCH Modifier);
make use of IMAP QRESYNC extension (rfc5162) to avoid SEARCH to find vanished
messages.
more to do ...
2003-02-27 18:41:54 +00:00
update TODO remove items: - the "Unidentified socket error" should be gone since 7ba7be111 - imap_commit_cmds() is implemented since cfaa4848d - we will never use MULTIAPPEND and FETCH BODY with multiple messages, as that would significantly complicate matters for no tangible benefit ... and add some new thoughts. the idea to use strings of colons for quoting patterns doesn't work, as colons in "regular" patterns could not be quoted.
2021-12-24 11:56:02 +00:00
make use of IMAP CAPABILITY APPENDLIMIT= extension (rfc7889; fastmail & gmail).
this is really useful only for IMAP <=> IMAP syncs: saves FETCH BODY.
the message could still become oversized due to conversion.
added support for tilde (~) expansion in the `Mailbox' and `CertificateFile' configuration directives added `Maildir' configuration command to specify the default location of the user's mailboxes. If a relative path is used in a `Mailbox' command, this path is used as a prefix.
2001-01-16 19:45:08 +00:00
create placeholders for messages over MaxSize this is vastly more useful than just omitting the messages with no indication at all.
2019-12-29 13:37:53 +00:00
dummy messages resulting from MaxSize should contain a dump of the original
message's MIME structure and its (reasonably sized) text parts.
updated year in copyright notice the uid for each message in the maildir is now stored in a dbm database rather than the filename. this change was necessary because isync became confused if you copied a message to another folder, in which case the uid was invalid. as a result of the above change, isync now acquires a mutex on the mailbox to protect the dbm database from concurrent access. main() was reworked to continue gracefully when an error is encountered, and to always call maildir_close() so that the lock can be disabled, and the database closed.
2002-01-16 19:47:28 +00:00
The Big Rewrite. too many change to list them all. 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.
2004-03-27 16:07:20 +00:00
don't SELECT boxes unless really needed; in particular not for appending,
and in write-only mode not before changes are made.
more to do
2010-02-06 09:48:11 +00:00
problem: UIDVALIDITY change detection is delayed, significantly complicating
matters.
check for dbm_open() in libc and libdb
2002-01-28 19:34:22 +00:00
update TODO
2017-10-01 12:37:36 +00:00
some error messages are unhelpful in non-verbose mode due to missing context.
more to do ...
2003-02-27 18:41:54 +00:00
possibly use ^[[1m to highlight error messages.
The Big Rewrite. too many change to list them all. 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.
2004-03-27 16:07:20 +00:00
pre-release doc updates
2013-12-08 21:29:15 +00:00
consider alternative approach to trashing: instead of the current trash-before-
expunge done by mbsync, let MUAs do the trashing (as modern ones typically do).
mbsync wouldn't do any trashing by itself, but should track the moves for
optimization. additionally, there should be a mode to move trashed messages to
the remote store. TrashMode Internal|External, AbsorbRemoteTrash.
a yet different approach to trashing is treating the trash like a normal mailbox.
however, this implies a huge working set.
consider optional use of messages-id (and X-GM-MSGID):
- detection of message moves between folders
update TODO
2017-10-01 12:37:36 +00:00
- recovery from loss of sync state, migration from other tools
Reference in New Issue Copy Permalink