Old forwarding rules are causing fatal error on roundcube #504
Labels
No Label
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
help wanted
Howto
In progress
🤔️ Investigate
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
question
Ready
refined
Roundcube
searX
spam-protection
Staging Server
Themes
TOR
Urgent!
Website
windows
wontfix
xmpp
Yearly Report
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#504
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Formatting used in Rainloop for sieve filters creates number of display issues. However for forwarding it causes a fatal error where users arent able to view their rules nor create new ones.
We have decided that rewriting all the current sieve rules will require too much labor and time, so we settled for the situation where although all the rules are still working, users should re-do them in roundcube once they see the need for it. Those rules are still visible in roundcube so the problem is rather minor annoyance when you try to edit them. Way forward is recreation.
However forwarding rules case fatal error on "Forwarding" option in the Settings menu. TO address the issue and prevent frustration and additional futurte support overhead, we should:
We should make sure that only people with rainloop rules are informed and not those who created rules using different client.
The howto page is done, so its link could be added in the email.
list of users is done, the text is more or less done, @muppeth will correct/improve it and send it tonight normally.
we decided that this is not done at the end of September, we just close this as not on complains so far anyway.
I actually got today the first ticket on zammad about that issue!