Bug 569824

Summary: (Alert Page )Email Configuration option does not reject Invalid email format
Product: [Other] RHQ Project Reporter: spandey
Component: AlertsAssignee: John Mazzitelli <mazz>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: low    
Version: 3.0.0CC: cwelton, kbanerje
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-02 07:21:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 585306    

Description spandey 2010-03-02 14:26:59 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Repro : 

1)Login to RHQ host with valid credentials
2)Create Alert for Added Resource
3)Add Email from Alert Notification Option 
4)At Receiver Email Address(es) field enter following Line and Press SAVE Button
*&*^*%()******

Expected Result : At step 4 Friendly Message should display Invalid email format 
			invalid format should not be saved.

Actual Result : At step 4 “*&*^*%()******”value has been saved no error message displays.
Comment 1 spandey 2010-03-02 14:43:19 UTC 
Revision: 6278e7056403b2dcd0ffde84a7109e60790022eb
Comment 3 John Mazzitelli 2011-02-17 17:26:45 UTC 
see if we can put in a regex to the config property within the server plugin's descriptor
Comment 4 John Mazzitelli 2011-02-18 19:32:02 UTC 
commit ba92016

to do "real" email address validation would require a huge regex (if its possible at all - see http://www.dominicsayers.com/isemail/ to see the complexities involved). Note this doesn't even take into account the differences between gwt/javascript regex and java regex that we are dealing with.

I added a simple regex validation to catch many invalid inputs. That is not to say it will capture all invalid email addresses, but it catches many now.
Comment 5 Mike Foley 2011-06-09 18:52:26 UTC 
verified
Comment 6 Heiko W. Rupp 2013-09-02 07:21:27 UTC 
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.