Filter Rules disappearing
-
dagent log is completely empty (created 3 months ago).
That’s the bad thing in kopano using the SQL db just as data heap: I can’t check if they are really there. I don’t think they will come back, but perhaps I get surprised.
The rule created with core-8.6.80.1018 didn’t get deleted after upgrading to core-8.6.80.1055, so it seams not to be a problem of the upgrade itself but more a problem of the format of the old rules. -
Same problem here, at least with one User. Another Users rules dont seem to be affected.
Problematical user recreated his rules, are visible with py-script but no more in webapp and dont get applyed :(
-
Up until this point we were sadly not able to reproduce this issue. If you have any more information about the rules of the user, or with which master version this appeared first we would be happy to hear about this.
-
I’ve upgraded from core-8.6.80.752_0+85-Debian_9.0-amd64 to core-8.6.80.1018_0+152-Debian_9.0-amd64, then the problem occured.
The User was greeted by the webapp configuration wizard, others not.
Afterwards, i upgraded to core-8.6.80.1055_0+156-Debian_9.0-amd64 with no change.Then i recreated the rules in webapp, after switching windows in webapp they disappeared there again.
Using rules based on “Includes these words in the sender’s address” are showing up correctly in py-script, those using full senders address are having an empty Condition-Table entry. Maybe there the Problem comes from?
After Upgrade working users rules only use the first, working, condition.
Another thing i notices:
The problematic user is also missing the mail signature, setup via webapp. -
@fbartels Can you provide a SQL Statement to list all rules from the database directly? So we could check if they are still there.
-
After deleting the Rules with missing conditions, the remaining rules reappeeared in the Webapp, test if they’re working is pending.
-
Update: Not working and rules disappeared again :(
-
If you have any more information
Better yet, if you have any disk images, shell prompts, etc., …
SQL Statement to list all [dagent] rules from the database directly?
SELECT h.owner, val_binary FROM properties AS p INNER JOIN hierarchy AS h ON p.hierarchyid=h.id WHERE tag=0x3FE1 -
@jengelh Ok, I have executed the statement on my updated system and imported a database-dump from some months ago into an other database and executed the statement. I don’t think that I changed the rules since then - just created one rule after the update when all rules got lost.
Both are returning exactly one record with a binary field. The size of the field is very different: about 58kb on the old and about 2kb on the new.I’m not really able to read the content of the binary, but I was able to find the sender addresses I use with the rules to sort the mail into different folders inside the binary blob.
In the old one there are many addresses (I expect all addresses of all rules) in the blob and in the new one only one for the one rule I created.So it seams to me all rules get lost also in the database and/or the whole blob was thrown away.
Could I help you in some way to find the problem? Perhaps exporting my old blob in some way and sending it to you?
-
Update: I just saw, that the blob is an XML dokument.
So i started to recreate my rules over the Webapp. I entered my 6 rules and clicked to save. Then I went to Mail view and back to settings / rules and my rules where gone (they are still in database now and kopano-rules lists them, but not shown in the webapp).
Perhaps the number of sendes in a rule is the problem…
-
Update: I tried to recreate the rules with Webapp several times in different orders. And lost the rules two times after saving them, going to Mail and returning to Rules.
So I think the problem is the size of the whole blob. I think the limit is somewhere between 50kB and 62kB. -
Update: I saved my rules an hour ago and they where there in the WebApp when I check the last time. I didn’t do anything since then, but now they are lost in tde WebApp. They are still displayed by kopano-rules.py, but they are not respected when processing mails.
-
@fbartels Is this issue fixed? As already said I"m able to reproduce it.
-
Hi @bmaehr ,
no no luck reproducing it on our side and therefore also no fix for this. We have added two changes though to get some additional logging:
https://stash.kopano.io/projects/KC/repos/kopanocore/commits/5f7b0f351f78266a773d323f657b89ce34f60a61
https://stash.kopano.io/projects/KC/repos/kopanocore/commits/614469db65191788ef15d6416e7a83192a4afbf0 -
@fbartels I just have to add enough rules on my running instance and the rules get lost without any upgrade. I can provide you the information to reproduce it.
-
I tried to reproduce this with 66 kB of rules, unfortunately I wasn’t able to reproduce. Could you perhaps send us your rules? If you don’t want to post it here on the forum, you could alternatively send it to: feedback@kopano.io
To backup your rules:
kopano-backup --only-meta -u <username> -f Inbox -
This post is deleted! -
This post is deleted! -
Hello,
I have the same issue with the filter rules.
I have created about 20 rules in the WebApp. And after the next mail ist processed by dagent the rules disappeared in the WebApp.
But they can be displayed via kopano-rules.py --list. So they are still available.
And after they disappeared in the WebApp they don’t show up in the dagent log, so they aren’t used any more.
After I delete the last rule they show up again in the WebApp and in the dagent log. But they aren’t used by dagent. Every log entry says: Rule “***” does not match: not found (8004010f)
And afterwards the rules tab is empty again in the WebApp. -
@freyuh to prevent spam bots (usually newly registered accounts) from posting messages there is a moderation queue for new users which you tripped into three times. I have approved all three of your posts, maybe you want to trim them down into a single post (the largely cover the same, but each one has different details).
also posting the exact version where you encounter an issue would be helpful as well.
