- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 25 2024
perhaps Domain based issue?
see end of your logs.
In D4950#61803, @machniak wrote:I see that MoveItems has a global Status (that we do not use) and per-item Status. https://learn.microsoft.com/en-us/openspecs/exchange_server_protocols/ms-ascmd/acae4033-b4f9-4f2a-8d83-51e097eb3b90
I thought that the common status codes can be used everywhere, but the documentation is not clear. https://learn.microsoft.com/en-us/openspecs/exchange_server_protocols/ms-ascmd/95cb9d7c-d33d-4b94-9366-d59911c7a060
As for 110 (server error), it looks like in general it might not be the best default error state as it means "the device SHOULD NOT retry later.". 111 (ServerErrorRetryLater) might be better for most generic error cases.
Addressed comments
Sep 23 2024
Any further ideas how to debug this? What error causes INVALIDARGUMENT? Or is this a sign for an uncaught error?
Sep 22 2024
Fixed the undefined $clientModifications
Sep 20 2024
Closing as duplicate of T8337.
Proposed fix in D4959.
Maybe looking at syncroton_content.creation_synckey value would sometimes be useful. Maybe list uids of messages synced in the last batch (SyncKey).
This works for the INBOX case I'm looking at, but it shows large differences on a Trash folder. I'm not sure if we also have to take syncroton_synckey.pendingdata into account (that's null in my case though), and maybe other things?
Fixup
This is just a refactoring and shouldn't change the behaviour.
I see that MoveItems has a global Status (that we do not use) and per-item Status. https://learn.microsoft.com/en-us/openspecs/exchange_server_protocols/ms-ascmd/acae4033-b4f9-4f2a-8d83-51e097eb3b90
Sep 19 2024
Can you add to the commit message/description *why* you're changing this?
FYI. Not necessarily better, but Roundcube already supports ENV by default. See https://github.com/roundcube/roundcubemail/blob/3e4894ee061e884099f1acc26f34697fbd8b5f8e/program/lib/Roundcube/rcube_config.php#L386
Sep 18 2024
Sep 17 2024
Its kolab 16 on almalinux 9
libkolab-3.2.0-1.35.el9.kolab_16.x86_64
php-kolabformat-1.3.1-1.23.el9.kolab_16.x86_64
roundcubemail-1.5.8.4-4.3.el9.kolab_16.noarch
iRony-0.4.8.5-1.16.el9.kolab_16.noarch
But of course there might be much older entries on the IMAP server since I have been using kolab for the last 13-15 years. Unfortunately the log does not mention the exact entry it is having problems with.
- Unify the way user impersonation is configured in data migrator URIs
The PHP code uses kolabformat class for v3 and kolabobject (from libkolab) for v2. What Kolab version and system do you use? What roundcubemail and iRony version?
Sep 13 2024
Sep 12 2024
- Fix so 2fa entries are cleaned up on delete
- Merge branch 'master' into dev/oauth-authorize-ui
Sep 11 2024
Sep 10 2024
Ok. I have increased the debug output to 9. Unfortunately nothing is logged. kolab-saslauthd failed at 08:03:39 and is automatically restarted.
Sep 9 2024
Included into the other patches