Filter Rules not working after Patch 32

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
k.shahovich
Posts: 3
Joined: Wed Aug 04, 2021 1:32 pm

Filter Rules not working after Patch 32

Post by k.shahovich »

After install P32 (now version zimbra 8.8.15_GA_4372_FOSS) doesn't apply filter.

URL request: https://domain.com/service/soap/ApplyFilterRulesRequest
Method: POST
Error code: 500 Server Error

method: [unknown]
msg: system failure: java.lang.NumberFormatException: For input string: "796f8cba-114c-4e28-a575-a3dab2613326:998959"
code: service.FAILURE
detail: soap:Receiver

Has anyone encountered a similar problem?
phoenix
Ambassador
Ambassador
Posts: 27272
Joined: Fri Sep 12, 2014 9:56 pm
Location: Liverpool, England

Re: Filter Rules not working after Patch 32

Post by phoenix »

You should not add your post(s) to an eight year old thread as it's likely to get ignored, your post is also not relevant to the topic in which you posted as it's about Patch 32 - I've moved this to it's own thread.

It might be useful if you gave some information about the exact problem, is this about a specific filter or is it a specific type of filter? How about some examples?
Regards

Bill

Rspamd: A high performance spamassassin replacement

Per ardua ad astra
k.shahovich
Posts: 3
Joined: Wed Aug 04, 2021 1:32 pm

Re: Filter Rules not working after Patch 32

Post by k.shahovich »

This problem occurs for all users, on any filter.
The filter works through the console:

Code: Select all

zmsoap  -z -m user@domain.com ApplyFilterRulesRequest/filterRules/filterRule @name="example" ../../query="in:/Inbox"
.
This filter:
From contains: ad
Move to folder: TASKY
Attachments
Screenshot_4.png
Screenshot_4.png (17.74 KiB) Viewed 1170 times
Screenshot_2.png
Screenshot_2.png (17.94 KiB) Viewed 1170 times
Screenshot_3.png
Screenshot_3.png (21.24 KiB) Viewed 1170 times
k.shahovich
Posts: 3
Joined: Wed Aug 04, 2021 1:32 pm

Re: Filter Rules not working after Patch 32

Post by k.shahovich »

Problem solved, thanks. The error occurred due to double-shared folders in boxes. But there was no error before the update.
Post Reply