tracker issue : CF-4198082

select a category, or use search below
(searches all categories and all time range)

CFMAIL fails with IDN domains and German Umlauts and maybe other special chars

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): e-domizil License Team / e-domizil License Team (Alexander Hass)

Created: 11/25/2016

Components: Language

Versions: 2016

Failure Type:

Found In Build/Fixed In Build: CF2016_Update3 / CF2016U11

Priority/Frequency: Major / All users will encounter

Locale/System: ALL / Win 2012 Server x64

Vote Count: 1

Problem Description: If we use IsValid() to validate email addresses it returns YES for email addresses with German Umlauts. This are valid, so IsValid is working properly here, but CFMAIL cannot handle these email addresses and causes an exception.

Steps to Reproduce: Run the attached example and see the output and dumps. Example email addresses are,foo@bäüöß.com,fäüö

Actual Result: Both foo@bäüöß.com and fäüö cannot send via CFMAIL, but isValid validates them properly as valid.

Expected Result: We expect that CFMAIL works properly with all chars that are supported in email addresses per RFC. It should never error like it does today. More and more of our customers have such email addresses and use them. We cannot tell customers to have a different email address just because CF 2016 is not able to handle it.

Any Workarounds: None.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4198082

External Customer Info:
External Company:  
External Customer Name: Alexander Hass
External Customer Email:  
External Test Config: My Hardware and Environment details:


  1. November 25, 2016 00:00:00: 1_index.cfm


We expect that CFMAIL automatically does the IDN conversion.
Comment by External U.
1445 | November 25, 2016 06:27:28 AM GMT
Developer comments .. h3. tested with the snapshot version of java mail 1.6 and i can see email getting sent to those email addresses. We need to upgrade to java mail 1.6 *once it is released publicly.*
Comment by Suresh J.
1446 | March 07, 2017 12:08:47 PM GMT
Will consider this bug, once the 1.6 mail jar, is released publicly.
Comment by HariKrishna K.
1447 | March 27, 2017 04:50:50 AM GMT
July 17, 2017 - JavaMail 1.6.0 Final Release Can you provide the requested hotfix to us now, please? 8 month wait time are really too many month for such critical isdues.
Comment by Alexander H.
1448 | July 19, 2017 06:33:08 AM GMT
We will evaluate the same and share an update.
Comment by Vamseekrishna N.
1449 | July 19, 2017 07:19:00 AM GMT
Did this fix make it into Update 7? I didn't see it in the list of fixed bugs for Update 7 and there were only 3 in the list.
Comment by Dan C.
29734 | September 24, 2018 01:44:29 PM GMT
No. Last two updaters (CF2016 Updater 6 and 7) seems to be security updates only.
Comment by ALEXANDER H.
29735 | September 24, 2018 01:47:16 PM GMT
Not fixed as of today. CF2016 update 8, 9 & 10 have been released, but there are more bugs related to this now. CF-4204050 does something weird with accents in the user name. Any "from" address over 73 characters throws a "The label in the input is too long" error. CF-4204100 is regarding isValid("email"); strings with "display names" are now considered part of a valid email address contrary to other isEmail() functions on other platforms. We recently upgraded from CF10 to CF2016 and these bugs have really negatively impacted us.
Comment by James M.
30555 | March 21, 2019 03:20:51 PM GMT
Correct. The fix has not released with an official updater. I asked several times why it is not included, but received no answer in last ~6 weeks.
Comment by e
30556 | March 21, 2019 03:28:20 PM GMT