Notification system silently drops failures to unicode email addresses
|Reported by:||John Hampton||Owned by:|
|Severity:||major||Keywords:||unicode email addresses|
|Cc:||raphael.schmid@…, Thijs Triemstra||Branch:|
See #9082 for some background.
Currently, email addresses with unicode in them are silently discarded when sending ticket updates. While not trying to deliver the email is correct, it's a little misleading. If the user enters a unicode email address in the
CC list, then it appears to get added (indeed it does) but they will never receive any emails. Unfortunately, there is no indication as to why the email will never be delivered. An admin can look in the log and see the email addresses which have been discarded, but they first have to know what they are looking for. Additionally, the same thing occurs for addresses in the
We could show a warning indicating that the email wasn't delivered to the problem addresses. The problem with the
CC list, is that the invalid address is put on the
CC list, and so anytime an update occurred, the warning would be shown. An administrator would then need to clean out the
CClist. The problem is even more complicated if a user has the invalid email address in their preferences and simply puts their username on the
CC list (or as the owner/reporter/updater of a ticket). An admin would then need to clear out the email address in the user's session.
I think the solution is to warn when an email can't be delivered, as well as stricter input validation. Input validation would need to be in:
- when entering email address
would need to differentiate between entering an email address and a username. This might be really hard when taking into account
- Don't know how to properly validate these, or whether it's worth it. Populating these with invalid values should be readily apparent to the admin.