Create Notification UI does not accept email addresses ending with .corp

[jobrs]

We were not able to create a EMAIL notification to any address ending with '.corp'

The response is: Unable to edit the notification: Address <email address hidden> is not of correct format

[Allan G (greental)]

sounds like a horizon issue, may be limited to 3 char extension ? does this work from the CLI ?

[Daniel Haupt (danhaupt)]

same error with CLI from manasca client

[jobrs (joachim-barheine)]

I will check whether Apache Commont Validator 1.4.1 (instead of 1.4.0) improves the situation

[jobrs (joachim-barheine)]

fyi https://commons.apache.org/proper/commons-validator/changes-report.html#a1.4.1

[jobrs (joachim-barheine)]

Probably this is the reason why *.corp are not supported: It seems like they are not accepted by ICANN.

See: http://icannwiki.com/.corp, for the reasons see http://icannwiki.com/New_gTLD_Program#Technical_Concerns_Impede_Delegation

[jobrs (joachim-barheine)]

ACV 1.4.1 did not help. My conclusion: *.corp is not supported by Monasca because it is by intention not supported by Apache Commons Validator. They will not fix it I am sure.

However we might consider adding support for such top-level domains, e.g.
a) through a configuration entry with additional acceptable domains
b) by making the check optional and just issue a warning to the user

Allan, what do you think?

[jobrs (joachim-barheine)]

Please review fix https://review.openstack.org/#/c/254643/

[OpenStack Infra (hudson-openstack)]

Change abandoned by Joachim Barheine (<email address hidden>) on branch: master
Review: https://review.openstack.org/254643
Reason: will move to python api