131298c2b1
Remove a level of wrapper abstraction that is not needed. Just use IMAPserver and be done with it. We do this by passing in the IMAPRepository() instance rather than a long list of single paramters to the IMAPServer instanciation. This way we can retrieve all repository parameters ourselves, rather than passing a dozen paramters into IMAPServer. Also, this enables us to pass the repository() object into our WrappedIMAP4() instance, so that it can query, e.g. the SSL fingerprint configuration. Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de> Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
36 lines
807 B
ReStructuredText
36 lines
807 B
ReStructuredText
=========
|
|
ChangeLog
|
|
=========
|
|
|
|
Users should ignore this content: **it is draft**.
|
|
|
|
Contributors should add entries here in the following section, on top of the
|
|
others.
|
|
|
|
`WIP (coming releases)`
|
|
=======================
|
|
|
|
New Features
|
|
------------
|
|
|
|
* When a message upload/download fails, we do not abort the whole folder
|
|
synchronization, but only skip that message, informing the user at the
|
|
end of the sync run.
|
|
|
|
Changes
|
|
-------
|
|
|
|
* Refactor our IMAPServer class. Background work without user-visible
|
|
changes.
|
|
|
|
Bug Fixes
|
|
---------
|
|
|
|
* We protect more robustly against asking for inexistent messages from the
|
|
IMAP server, when someone else deletes or moves messages while we sync.
|
|
|
|
Pending for the next major release
|
|
==================================
|
|
|
|
* UIs get shorter and nicer names. (API changing)
|