summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAge
* Only create one sessionChristian Mollekopf2017-04-26
| | | | And not one for every imap proxy
* Fixed build errorChristian Mollekopf2017-04-26
|
* Make sure we always have a complete hierarchy from the IMAP serverChristian Mollekopf2017-04-21
|
* Apparently this folder can have various names.Christian Mollekopf2017-04-21
|
* Gmail support.Christian Mollekopf2017-04-21
| | | | | For the time being we hardcode a list of folders that we synchronize that we know are not duplicating messages.
* Handle host not foundChristian Mollekopf2017-04-20
|
* Going towards 0.3Christian Mollekopf2017-04-20
|
* Updated spec fileChristian Mollekopf2017-04-19
|
* v0.2.0v0.2.0Christian Mollekopf2017-04-19
|
* Bumped releaseChristian Mollekopf2017-04-12
|
* cleanupChristian Mollekopf2017-04-12
|
* Fixed entity creation in pipelineChristian Mollekopf2017-04-12
|
* Better debug outputChristian Mollekopf2017-04-12
|
* Merge remote-tracking branch 'origin/master' into developChristian Mollekopf2017-04-12
|\
| * handle all enum valuesMarco Martin2017-04-11
| | | | | | | | fix build, add a default handler in the switch
* | Allow the preprocessor to move and use in mailtransportChristian Mollekopf2017-04-12
| |
* | Copy mail back from mailtransportChristian Mollekopf2017-04-11
| |
* | Moved all preprocessing back into the pipelineChristian Mollekopf2017-04-11
| |
* | Move the preprocssing back out of entitystore into the pipeline.Christian Mollekopf2017-04-11
| | | | | | | | | | This is where this really belongs, only the indexing is part of storage. This is necessary so preprocessors can move entities as well.
* | We set the instance identifier in the base classChristian Mollekopf2017-04-11
| |
* | Less noiseChristian Mollekopf2017-04-10
| |
* | Don't continue processing the pipeline until we have appended theChristian Mollekopf2017-04-10
| | | | | | | | | | | | message. Otherwise the processor might think its done before it actually is.
* | Added uid indexChristian Mollekopf2017-04-10
| |
* | Fixed readAllUids and readAllChristian Mollekopf2017-04-10
| |
* | Send an error status messagebefore crashing.Christian Mollekopf2017-04-07
| |
* | Avoid crashing if we fail to resolve the local id.Christian Mollekopf2017-04-07
| |
* | Detect maildir resource errorsChristian Mollekopf2017-04-07
| |
* | Better account status aggregation.Christian Mollekopf2017-04-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Only ever enter error state on non-recoverable errors. Otherwise: * Busy state while busy, then go back to online/offline/error. * If we failed connect during replay/sync we assume we're offline. * If we failed to login but could connect we have a known error condition. * If we succeeded to replay/sync something we are apprently online. At the core we have the problem that we have no way of telling wether we can connect to the server until we actually try (network is not enough: vpns, firewalls, ....). Further the status always reflects the latest status, so even if we were in an error state, once we retry we go out of the error state and either end up back in the error state or not. When aggregating states we have to similarly adjust the state to the most relevant among the resources. The states are ordered like this: * Error * Busy * Connected * Offline
* | Be less verboseChristian Mollekopf2017-04-07
| | | | | | | | We already see the resource exiting.
* | Fixed changereplay guardChristian Mollekopf2017-04-06
| | | | | | | | ...and improved debug output slightly.
* | Bumped releaseChristian Mollekopf2017-04-05
| |
* | Mailtransport notificationsChristian Mollekopf2017-03-30
| |
* | We already print those warnings in the synchronizerChristian Mollekopf2017-03-30
| |
* | Print notification type namesChristian Mollekopf2017-03-29
| |
* | Emit dataChanged without rolesChristian Mollekopf2017-03-29
| |
* | CleanupChristian Mollekopf2017-03-28
| |
* | Added missing property mappersChristian Mollekopf2017-03-28
| |
* | Guard against destructionChristian Mollekopf2017-03-28
| | | | | | | | We really need to guard against this in kasync...
* | Don't filter trash in the standard queryChristian Mollekopf2017-03-28
| | | | | | | | ...we selectively apply the filter in kube instead.
* | Only send notifications about being connected if we did somethingChristian Mollekopf2017-03-28
| | | | | | | | | | | | against the source. We used to replay no changes and then claim the resource was online.
* | Track the entities that this request applies to directly in theChristian Mollekopf2017-03-28
| | | | | | | | | | | | | | | | syncrequest That way we can do the notification emitting in the synchronizer and it keeps working even if the login already fails (so the synchronizing code would never be executed).
* | Emit notifications while a folder is being syncedChristian Mollekopf2017-03-27
| |
* | Don't use 0 as error code and better error codesChristian Mollekopf2017-03-27
| |
* | Pass in days to downloadChristian Mollekopf2017-03-26
| |
* | SinkTraceCtxChristian Mollekopf2017-03-26
| |
* | Fixed notification queringChristian Mollekopf2017-03-26
| |
* | Ignore changereplay notifications in the notificationstestChristian Mollekopf2017-03-26
| | | | | | | | | | They don't get through to the resource consistently, so we have to ignore them for now to make the test reliable.
* | Don't filter notifications too early.Christian Mollekopf2017-03-26
| | | | | | | | | | | | With this it becomes difficult to test notifications, and notifications may contain more interesting information, so we don't want to drop them too early.
* | Test the result of the write operation.Christian Mollekopf2017-03-26
| |
* | Don't store the lockfile inside the main resource folder.Christian Mollekopf2017-03-26
| | | | | | | | | | | | | | | | | | We currently use the folder as the main db folder, meaning we remove the folder when removing the db. This results in the lockfile vanishing with the db, which then confuses QLockFile (resulting in a lot of warnings). We may want to start moving everything into a resource-instance folder, but then we have to do it properly across the board.