Bug 38804 - ucs-test: check mail related modifications of user objects
ucs-test: check mail related modifications of user objects
Status: CLOSED FIXED
Product: UCS Test
Classification: Unclassified
Component: Mail
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Ammar Najjar
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-07-01 11:05 CEST by Sönke Schwardt-Krummrich
Modified: 2023-03-25 06:52 CET (History)
1 user (show)

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-07-01 11:05:29 CEST
Please implement several test scripts that check the behaviour of the mail stack (dovecot and cyrus) when modifying user objects later on.

All tests should be performed with 
mail/cyrus/mailbox/rename=yes and mail/cyrus/mailbox/delete=no resp.
mail/dovecot/mailbox/rename=yes and mail/dovecot/mailbox/delete=no

1) Create a user with mailHomeServer and mailPrimaryAddress
   → mailbox should have been created and is accessible
   Change mailPrimaryAddress
   → mailbox with NEW name should have been created and is accessible
   → mailbox with OLD name should NOT be accessible

2) Create a user with mailPrimaryAddress and without mailHomeServer
   → mailbox should NOT have been created
   Add local FQDN as mailHomeServer
   → mailbox should have been created and is accessible

3) Create a user with mailPrimaryAddress and without mailHomeServer
   → mailbox should NOT have been created
   Add "foreign" FQDN as mailHomeServer
   → mailbox should NOT have been created

4) Create a user without mailPrimaryAddress and mailHomeServer==$LOCALFQDN
   → mailbox should NOT have been created
   Add mailPrimaryAddress
   → mailbox should have been created and is accessible

5) Create a user with mailHomeServer and mailPrimaryAddress
   → mailbox should have been created and is accessible
   Change mailHomeServer
   → mailbox should NOT be accessible

6) Create a user with mailHomeServer and mailPrimaryAddress
   → mailbox should have been created and is accessible
   Remove mailHomeServer
   → mailbox should still be accessible

7) Create a user with mailHomeServer and mailPrimaryAddress
   → mailbox should have been created and is accessible
   Remove mailPrimaryAddress
   → mailbox should NOT be accessible
Comment 1 Ammar Najjar univentionstaff 2015-07-10 08:39:55 CEST
A new script with the name "29_mail_related_modifications_of_user_objects" is created to include the mentioned test cases.
Comment 2 Daniel Tröder univentionstaff 2015-09-08 11:49:41 CEST
Modified test script to treat "[UNAVAILABLE] Internal error occurred." as normal login error (see Bug #39317).
Comment 3 Stefan Gohmann univentionstaff 2016-10-12 07:48:20 CEST
For this bug is no separate QA needed.