Bug 38348 – Contact / NotificationEmail must not be an invalid email address

Bug 38348 - Contact / NotificationEmail must not be an invalid email address


Summary:	Contact / NotificationEmail must not be an invalid email address

Status:	NEW

Product:	UCS Test
Classification:	Unclassified
Component:	App Center
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	App Center maintainers
QA Contact:

URL:
Keywords:

Depends on:	33902
Blocks:
	Show dependency tree / graph

Reported:	2015-04-24 12:01 CEST by Dirk Wiesenthal
Modified:	2016-10-21 18:50 CEST (History)
CC List:	2 users (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
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dirk Wiesenthal

2015-04-24 12:01:28 CEST

We should not allow appcenter@software.com and sales@software.com. It has been documented with those addresses and they are just wrong - although valid and emails will actually be sent there if someone copies the file and forgets to change the value.

+++ This bug was initially created as a clone of Bug #33902 +++

NotificationEmail must not be an invalid email address.
Example:
NotificationEmail=
means notification_email = '' which is not a valid email address.
(To achieve the fallback to Contact the field must not be set at all which leads to notification_email = None)

Contact likewise has to contain a valid email address.

Comment 1 Janek Walkenhorst

2015-04-24 12:15:18 CEST

Please also make sure that the test checks for a valid MX-record for the domain part. (Won't help with software.com but will help with correct documentation addresses)