Bug 49851 - mailfilter creation in OX fails if default UCS sieve script exists
mailfilter creation in OX fails if default UCS sieve script exists
Status: NEW
Product: Z_Internal OX development
Classification: Unclassified
Component: Mail
UCS 5.0 / 7.10.6
Other Linux
: P5 normal (vote)
: ---
Assigned To: Mail maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-07-16 08:27 CEST by Daniel Tröder
Modified: 2023-03-06 16:50 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 4: A User would return the product
User Pain: 0.229
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Tröder univentionstaff 2019-07-16 08:27:57 CEST
From https://help.univention.com/t/spam-wird-nicht-in-den-spam-ordner-verschoben/12530/3
------------
When activating the mail/dovecot/sieve/spam variable, every new user will have a “default.sieve” script in his mailbox configuration.
If this is the case, mailfilter creation in Open-Xchange will fail though:

Caused by: com.openexchange.jsieve.export.exceptions.OXSieveHandlerException: Currently active script "default" is not the expected one "Open-Xchange"
[..]
------------
Comment 2 Dirk Ahrnke univentionstaff 2023-03-06 16:50:30 CET
while writing down some notes for another customer I had a look into the mailfilter.properties

# If you want the script to be generated with another script name change it here.
# Note that the mail filter bundle will then leave the old script with the old
# script name behind, and doesn't delete it
com.openexchange.mail.filter.scriptName=Open-Xchange


The question is if there ever was a reason to use this name in OXSEFORUCS.
Otherwise it might be a lowhangig fruit be setting an UCRV.