On Thu, 26 Oct 2017 13:18:05 -0700, Bakul Shah said:
The trickier aspect, and the real issue for me, is proper synchronization when email is accessed from multiple machines, and which may not be connected all the time. On reconnection a client has to upload its changes and resync its local cache with the imap server so that changes made elsewhere are properly reflected.
AIUI, the big issue has always been that nmh has expected message numbers to remain static until explicitly changed (i.e. message 35 *stays* message 35 until 'folder -pack' or something changes it), while IMAP message numbers can change even during a connection, so UUID's need to be used instead, which means keeping a message<->uuid mapping someplace. And making that robust under concurrent access sounds even worse... (If this is already a solved problem, somebody whack me with a clue-by-four.. :)
pgpiL0gSwtb2I.pgp
Description: PGP signature
_______________________________________________ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers