Bug 46753 - Can't use Umlaut-Maildomains
Can't use Umlaut-Maildomains
Status: NEW
Product: UCS
Classification: Unclassified
Component: UMC - Mail
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-03-28 14:27 CEST by Nico Stöckigt
Modified: 2021-05-03 21:38 CEST (History)
6 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?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.171
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
Ulaut Maildomain is rejected (56.20 KB, image/png)
2018-03-28 14:27 CEST, Nico Stöckigt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Stöckigt univentionstaff 2018-03-28 14:27:13 CEST
Created attachment 9488 [details]
Ulaut Maildomain is rejected

Since Umlaut maildomains exists [https://tools.ietf.org/html/rfc5894] it's possible to create them in the Mail module of UMC. The problem is you can't use them. When you try to assign an e-mail address with a Umlaut domain to a user you get the following error - see attach screenshot.

If you try this via console:
# udm users/user modify --dn "uid=socu,cn=users,dc=univention,dc=test" --set "mailPrimaryAddress=socu@rößlein.de"
LDAP Error: Invalid syntax: mailPrimaryAddress: value #0 invalid per syntax
Comment 1 Dirk Dörflinger 2018-05-30 15:19:57 CEST
Workaround:

Add the Umlaut domain to the mail domain: domäne.com

Add the Mailadress in puny code style (user@xn--domne-ira.com) to the user (I tested with mailAlternativeAddress) to the user. 

Send mail to user@domäne.com. 

Works. 

A real fix would be nice though.
Comment 2 Florian Best univentionstaff 2019-03-01 21:16:56 CET
Should be relatively easy to fix, just .encode('idna').
A patch for computers is at Bug #34948.
Comment 3 Sönke Schwardt-Krummrich univentionstaff 2019-03-04 12:09:37 CET
(In reply to Florian Best from comment #2)
> Should be relatively easy to fix, just .encode('idna').
> A patch for computers is at Bug #34948.

IIRC this will not fix following postfix configuration problems.
Comment 4 Florian Best univentionstaff 2019-03-04 13:01:19 CET
(In reply to Sönke Schwardt-Krummrich from comment #3)
> (In reply to Florian Best from comment #2)
> > Should be relatively easy to fix, just .encode('idna').
> > A patch for computers is at Bug #34948.
> 
> IIRC this will not fix following postfix configuration problems.

Okay, I thought it works, as described in comment #1.
Comment 5 Daniel Tröder univentionstaff 2019-03-25 07:46:38 CET
Requested again: https://help.univention.com/t/idn-domain-not-possible/11587/1