MySQL Bugs: #50161: MEM email notification - can have 2 emails with no comma between

Bug #50161	MEM email notification - can have 2 emails with no comma between
Submitted:	7 Jan 2010 21:04	Modified:	18 Jan 2010 14:46
Reporter:	Lig Isler-Turmelle	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S3 (Non-critical)
Version:	2.1.0.1096	OS:	Any
Assigned to:	Darren Oldag	CPU Architecture:	Any

Description:
When updating a notification listing it is possible to create a listing where there are multiple email addresses on the same line without a comma between them.

How to repeat:
1) create a notification group with at least 2 email addresses in it and save.
2) update the notification group and delete the comma between the email addresses and save

Note the saved email addresses.  it is the same way in the mem database:

mysql> select * from target_email;   
+-----------+----------+-------+-----------------------------------+-----------+
| target_id | memAdmin | name  | recipients                        | smsFormat |
+-----------+----------+-------+-----------------------------------+-----------+
|        14 |          | test2 | test@example.com test@me.com      |           | 
+-----------+----------+-------+-----------------------------------+-----------+

Suggested fix:
verify email still is in valid format when updating

when an alert is triggered connected to the notification group with this problem get the following error:

javax.mail.internet.AddressException: Illegal whitespace in address in string ``test@example.com test@me.com''

also happens when you remove the comma and add a new line to separate the email address

Keith Russell writes: 
Patch available in builds => 2.1.1.1138.

Marcos Palacios writes: 
Verified fixed in Monitor build 2.1.1.1138.

A note has been added to the 2.1.1 changelog: 

It was possible to updated an existing email notification list with two email addresses in the destination without a required comma between the addresses. Addresses are now validated during the editing phase to ensure that this does not occur.