Old forwarding rules are causing fatal error on roundcube #504

Closed
opened 2023-05-01 17:26:39 +02:00 by muppeth · 4 comments
Owner

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:

  • Asses the number of users with forwarding rules setup with rainloop
  • Send email informing them on possible issue when using rainloop and point to the solution.

We should make sure that only people with rainloop rules are informed and not those who created rules using different client.

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: - Asses the number of users with forwarding rules setup with rainloop - Send email informing them on possible issue when using rainloop and point to the solution. We should make sure that only people with rainloop rules are informed and not those who created rules using different client.
muppeth added the
Mail
label 2023-05-01 17:26:39 +02:00
muppeth added this to the 06.22 - June milestone 2023-06-07 10:14:18 +02:00
muppeth modified the milestone from 06.22 - June to 23.06 - June 2023-06-07 10:14:23 +02:00
Owner

The howto page is done, so its link could be added in the email.

The howto page is done, so its link could be added in the email.
Owner

list of users is done, the text is more or less done, @muppeth will correct/improve it and send it tonight normally.

list of users is done, the text is more or less done, @muppeth will correct/improve it and send it tonight normally.
muppeth modified the milestone from 23.06 - June to 23.07 - July 2023-07-03 22:28:12 +02:00
muppeth removed this from the 23.07 - July milestone 2023-08-06 15:35:28 +02:00
muppeth added this to the 23.08 - August milestone 2023-08-06 16:09:23 +02:00
muppeth modified the milestone from 23.08 - August to 23.09 - September 2023-09-03 21:00:37 +02:00
muppeth self-assigned this 2023-09-03 21:00:57 +02:00
Owner

we decided that this is not done at the end of September, we just close this as not on complains so far anyway.

we decided that this is not done at the end of September, we just close this as not on complains so far anyway.
Owner

I actually got today the first ticket on zammad about that issue!

I actually got today the first ticket on zammad about that issue!
meaz closed this issue 2023-10-01 15:57:07 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Disroot/Disroot-Project#504
No description provided.