Bug 38660 - Check sieve script
Check sieve script
Status: CLOSED FIXED
Product: UCS Test
Classification: Unclassified
Component: Mail
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Ammar Najjar
:
Depends on: 38469
Blocks:
  Show dependency treegraph
 
Reported: 2015-06-08 14:12 CEST by Sönke Schwardt-Krummrich
Modified: 2023-03-25 06:49 CET (History)
0 users

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
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 Sönke Schwardt-Krummrich univentionstaff 2015-06-08 14:12:36 CEST
By default, a sieve script is created for new mail users. The script checks the spamassassin score and moved the mail to the user specific spam folder if the threshold has been reached.

Please create a script that
1) creates a new user mit mail account (mailPrimaryAddress and mailHomeServer are set)
2) checks if a default sieve script is created (use e.g. sieve-connect or sieveshell)
3) checks if a spam mail is delivered to the spam folder
4) deactivates the default sieve script via UCR and retries the steps 1-3 again
Comment 1 Ammar Najjar univentionstaff 2015-06-18 10:41:44 CEST
A new script with the name "31_sieve_script" is created to include the mentioned cases, tested on cyrus and dovecot.
Comment 2 Stefan Gohmann univentionstaff 2016-10-12 07:48:46 CEST
For this bug is no separate QA needed.