You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason the list of scripts stored in the sqlite index got out-of-sync with the content of the #sieve folder. It might have been our fault when we did some data migration. Right now we can't say it got broken during normal operation.
To find out what's going on encountered some issues:
reconstructing the #sieve folder didn't fix the issue (it did not de-activate nor remove records from sieve_scripts table).
dav.db file is not mentioned at https://www.cyrusimap.org/3.8/imap/concepts/deployment/databases.html, sieve is mentioned in DAV Index (<userid>.dav) section, but the file is dav.db not <userid>.dav. If it was properly documented or the file was sieve.db we would find the issue faster.
maybe accessing a sieve script that exists in the sieve_scripts table, but not in the #sieve folder should trigger re-sync?
It would be much easier if 1. or 3. just worked for this case, but documentation could be clearer too.
The text was updated successfully, but these errors were encountered:
Cyrus 3.6.3 with Murder.
For some reason the list of scripts stored in the sqlite index got out-of-sync with the content of the #sieve folder. It might have been our fault when we did some data migration. Right now we can't say it got broken during normal operation.
To find out what's going on encountered some issues:
dav.db
file is not mentioned at https://www.cyrusimap.org/3.8/imap/concepts/deployment/databases.html, sieve is mentioned inDAV Index (<userid>.dav)
section, but the file isdav.db
not<userid>.dav
. If it was properly documented or the file wassieve.db
we would find the issue faster.It would be much easier if 1. or 3. just worked for this case, but documentation could be clearer too.
The text was updated successfully, but these errors were encountered: