Bug 44725 - mailadress validity not checked when creating user via template
mailadress validity not checked when creating user via template
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Mail
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-01 14:46 CEST by Jens Thorp-Hansen
Modified: 2020-07-03 20:51 CEST (History)
2 users (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?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.171
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017060121000471
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 Jens Thorp-Hansen univentionstaff 2017-06-01 14:46:40 CEST
testvm: 10.200.6.100

steps to reproduce:

- change template "kopano account" to create mailadress as <lastname>@domain.stuff
- create a new user with the "kopano account" template
- lastname = "mueller schulz"

the resulting mailadress is displayed as: "mueller schulz@domain.stuff" and the user can be saved without an error. Either the blanks " " need to be replaced with "_" or an error should appear and the user should not be saved.
Comment 1 Thomas Stather 2017-06-02 13:27:59 CEST
I think an error message makes sense in any case since then the admin can decide how to replace the whitespaces.

The best way in addition would be to define a character that should be used as a substition ("-" in our case).

Best,
Thomas
Comment 2 Ingo Steuwer univentionstaff 2020-07-03 20:51:02 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.