tracker issue : CF-4187127

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

Whitespace being stripped out when using CFMAIL

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Erik Aulbach / Erik Aulbach (Erik Aulbach)

Created: 09/06/2016

Components: Net Protocols, MAIL

Versions: 2016

Failure Type: Incorrect w/Workaround

Found In Build/Fixed In Build: CF2016_Update1 / 2018.0.0.306721

Priority/Frequency: Normal / All users will encounter

Locale/System: English / Windows 10 64 bit

Vote Count: 9

Listed in the version 2016.0.06.308055 Issues Fixed doc
Problem Description: If there is only whitespace in between coldfusion variables used in the body of a CFMAIL msg, the whitespace is being removed in the email msg and the values are run together. This only happens in CF2016 (works fine in CF10) and while not a big issue it does cause some data corruption - like incorrect email links

Steps to Reproduce:
<cfset FN = "John">
<cfset LN = "Smith">
<cfset email= "">

<cfmail to="" from="" subject="whatever">
#FN# #LN# #email#

Actual Result:
The resulting email reads: which in turn causes incorrect email links in the msg.

Expected Result:
The email should read: John Smith

Any Workarounds: Use any workaround that puts some non-whitespace character in between the vars (like a hyphen) or forces a blankspace (like "nbsp" or #chr(160)#) or set the data into a single variable before using, etc. IMO - this is not something users should be expected to do

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

Watson Bug ID:	4187127

External Customer Info:
External Company:  
External Customer Name: Erik Aulbach
External Customer Email:  
External Test Config: My Hardware and Environment details:



This bug says it was fixed? In which version/update is the fix? Still seemed to be broken in update 3....
Comment by Dan C.
1870 | January 09, 2017 08:08:47 PM GMT
Affected as well. CF 2016 HF4 on Windows 2008R2.
Vote by Brian C.
1877 | May 01, 2017 05:46:49 PM GMT
This fix would be available as part of next update, i.e., update5, for which timeline is not decided yet.
Comment by HariKrishna K.
1871 | May 03, 2017 05:35:22 AM GMT
This is still not fixed in update 5 and is an important fix. Please fix this in the next update.
Comment by John S.
1872 | September 21, 2017 11:33:18 PM GMT
This needs to be fixed asap!
Vote by John S.
1878 | September 21, 2017 11:33:33 PM GMT
Its been over a year now since the original bug was opened and this still isn't fixed. Why is this so difficult??
Comment by Dan C.
1873 | September 21, 2017 11:49:21 PM GMT
This is probably impacting many customers that don't even realize it. I found it by accident myself. Please fix this.
Comment by Troy A.
1874 | September 22, 2017 12:02:19 PM GMT
This fix will be made available in the next bug-fix update release. Note that a security release is not counted as a bug-fix release and the recently released updates were security updates.
Comment by Vamseekrishna N.
1875 | September 25, 2017 04:08:10 AM GMT
Still an issue in CF 2016 HF5. What is the status on this? When will the next "bug-fix update release" be released? It has been almost a year and a half since it was reported.
Comment by Daniel S.
1876 | February 20, 2018 06:33:04 PM GMT
Good news on this: CF2016 update 6 came out today, and it specifically lists this bug as fixed, in its bugs fixed list, (While the "Fixed In Build" field above says this was fixed in "2018.0.0.306721", which could have seemed to some readers that this might not be fixed until CF2018, that's clearly not what it meant.) And FWIW, the "build" number for update 6 as released today is "308055", but at least that's above 306721. Adobe folks, it is pretty confusing to us when you use references for the "fixed in build" that don't tie to the things we know, like canonical update numbers. We have no insight into your internal build process and how those build numbers relate to CF update numbers.
Comment by Charlie A.
27570 | April 10, 2018 03:24:32 PM GMT
Not fixed! This just started for me with the last security patch on cf11!
Vote by Heather H.
27571 | April 19, 2018 07:05:00 AM GMT