tracker issue : CF-3868520

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

Incorrect e-mail attachment names

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Maurice Griep / Maurice Griep (MauriceNL)

Created: 12/12/2014

Components: Net Protocols, MAIL

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final /

Priority/Frequency: Normal / All users will encounter

Locale/System: English / Win All

Vote Count: 2

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on September 02, 2019 using build 2016.0.01.298513 
Problem Description:Since the upgrade to CF Update 14 e-mail attachment names are incorrect. This only seems to occur when sending attachments with long file names.

Steps to Reproduce:

1) Create a file with the name: c:\TheQuickBrownFoxJumpedOverTheLazyFenceTheQuickBrownFoxJumpedOverTheLazyFence.txt

2) Run the following CFM script

<cfset strDestination = "C:\TheQuickBrownFoxJumpedOverTheLazyFenceTheQuickBrownFoxJumpedOverTheLazyFence.txt">
<cfmail to="john.doe@company.com" from="NoReply@company.com" subject="Test Mail">
<cfmailparam file="#strDestination#" disposition="attachment">
</cfmail>
<cfoutput>Mail sent</cfoutput>

3) In the resulting e-mail the name of the attachment is incorrect:

TheQuickBrownFoxJumpedOverTheLazyFenceTheQuickBrownFoxJumpedOverTheLazyFence.txteQuickBrownFoxJumpedOverTheLazyFence.txt


Actual Result:
TheQuickBrownFoxJumpedOverTheLazyFenceTheQuickBrownFoxJumpedOverTheLazyFence.txteQuickBrownFoxJumpedOverTheLazyFence.txt

Expected Result:
TheQuickBrownFoxJumpedOverTheLazyFenceTheQuickBrownFoxJumpedOverTheLazyFence.txt

Any Workarounds:

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

Watson Bug ID:	3868520

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

Coldfusion 10 update 14 on IIS Windows Server 2012 R2

Attachments:

Comments:

Just noting I was unable to repro this on CF10u14 or CF11u3 on Windows 8 Pro using IIS. For me, the expected result was the actual result. The resulting e-mail attachment's name was TheQuickBrownFoxJumpedOverTheLazyFenceTheQuickBrownFoxJumpedOverTheLazyFence.txt. Thanks!, -Aaron
Comment by External U.
9466 | January 06, 2015 04:43:45 AM GMT
Hi Aaron, I installed a Windows 8 Pro machine and also was not able to reproduce the issue. However on our two Windows Server 2012 R2 servers the issue remains. I'm now going to setup a new 2012 server with CF10 from scratch and see if I can reproduce the issue. If so, it may be the issue is limited to 2012 R2. Thanks for your help so far and I will let you know the outcome. Regards, Maurice
Comment by External U.
9467 | January 06, 2015 07:10:37 AM GMT
Hi Aron, **Update: the same issue occurs on a new/clean Windows 2012 R2 server** We installed a brand new Windows 2012 R2 server, configured IIS and installed CF 10. Before updating to CF10u14 the result was OK. After updating to CF10u15 we got the same result as on our production servers, the attachment name was incorrect, i.e.: TheQuickBrownFoxJumpedOverTheLazyFenceTheQuickBrownFoxJumpedOverTheLazyFence.txteQuickBrownFoxJumpedOverTheLazyFence.txt Hopefully this helps you tracking down the issue. Regards, Maurice
Comment by External U.
9468 | January 06, 2015 05:09:39 PM GMT
Hi Maurice, You're very welcome. I just tried w/ the following config and wasn't able to repro this. x64 Windows Server 2012 R2 Datacenter CF10u15 (10,0,15,292620) w/ isapi_redirect.dll v1.2.40.0 and JVM v1.7.0_15 No idea what would be causing the issue. The sent and received file name has always matched for me (thus far I've tried Standalone Enterprise CF10u14, CF10u15 and CF11u3 on both x64 Win8.1 Pro and x64 Win2012R2 Datacenter). Thanks!, -Aaron
Comment by External U.
9469 | January 07, 2015 12:10:20 AM GMT
Hi Aaron, There seems to be a dependency on the mail system you use. I tried sending the e-mail to my private ISP and the attachment name was correct. Our corporate mail system (we use Exchange Online) does show the incorrect attachment name. I took a look at the message header and the mail sent after upgrading to CF10u14 shows a different header: BEFORE Upgrade to CF10u14: ------=_Part_0_1141271736.1420656164465 Content-Type: application/octet-stream; name=TheQuickBrownFoxJumpedOverTheLazyFenceTheQuickBrownFoxJumpedOverTheLazyFence.txt Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*0*=TheQuickBrownFoxJumpedOverTheLa%7ayFenceTh; filename*1*=eQuickBrownFoxJumpedOverTheLa%7ayFence.txt ------=_Part_0_1141271736.1420656164465-- AFTER upgrade to CF10u14 ------=_Part_34_1069752039.1420655903642 Content-Type: application/octet-stream; name=TheQuickBrownFoxJumpedOverTheLazyFenceTheQuickBrownFoxJumpedOverTheLazyFence.txt Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*0*=TheQuickBrownFoxJumpedOverTheLa%7ayFenceTh; filename*1*=eQuickBrownFoxJumpedOverTheLa%7ayFence.txt; filename*1*=eQuickBrownFoxJumpedOverTheLa%7ayFence.txt ------=_Part_34_1069752039.1420655903642-- As you see the header after upgrading to CF10u14 shows a duplicate/redundant line, starting with (filename*1*=....). I guess this causing some mail agents to incorrectly format the attachment name. Although it's a very specific problem (Windows 2012 R2, MTA dependency) it's causing a lot of issues for us, so hopefully you can address this issue. Thanks a lot for the time and effort you've put in this issue so far! Regards, Maurice
Comment by External U.
9470 | January 07, 2015 02:07:20 PM GMT
Hi Maurice, You're very welcome. I've confirmed the corrupted file name when sending to Outlook 2010. Regarding the headers: My Outlook Web App doesn't allow me to view headers. My Outlook program allows me to view headers, but doesn't display any of the headers you listed, except Content-Type. The <cfexchangeemail action="get" getheaders="true"> (the getheaders attribute is new BTW) also doesn't list any of those headers, except Content-Type. Interestingly, my Outlook program displays 3 Received headers but <cfexchangeemail action="get" getheaders="true"> only lists 2 of those Received headers (possible bug Adobe?). Adobe, this filename corruption issue also exists when sending email from CF11 Update 3 to an Exchange 2010 mailbox. The code in the description suffices as the repro for that too. Thanks!, -Aaron
Comment by External U.
9471 | January 08, 2015 04:40:47 AM GMT
+1 - this filename corruption issue also exists when sending email from CF11 Update 3 to an Exchange 2010 mailbox
Vote by External U.
9475 | January 08, 2015 04:41:22 AM GMT
Hi Aaron, Out mail system allows me to view the complete "raw" message text in the form of an EML file. This is how I compared the pre/post update e-mail messages. Regards, Maurice
Comment by External U.
9472 | January 08, 2015 08:55:14 AM GMT
Hi Maurice, I could reproduce this behavior with CF 10 HF14, this has happened because of mail.jar upgrade to 1.5.0. We have upgraded to 1.5.0 mail.jar because, we were seeing few intermittent "unable to load body structure " errors. We have also tried with latest mail jar 1.5.2, and hit the same issue. Logged a bug with oracle https://kenai.com/bugzilla/show_bug.cgi?id=6662
Comment by HariKrishna K.
9473 | January 12, 2015 06:08:45 AM GMT
Hi Maurice, Ah! Okay, that makes sense. Thank you for that. Hi Hari, When I said I confirmed on Outlook 2010, I meant "Exchange 2010". I'm sorry, my fault there. Could "Outlook 2010" please be changed to "Exchange 2010" in that Oracle ticket? B/c the issue is when sending email w/ long attachment names to _Exchange_. Again, sorry about that! Thanks!, -Aaron
Comment by External U.
9474 | January 12, 2015 08:52:42 AM GMT
This bug is still present with CF11 U5 on a windows 2012 R2 Server. I'd appreciate if adobe would have a look at this as it impacts productive systems for a long time now.
Vote by External U.
9476 | July 13, 2015 08:34:25 AM GMT
Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513), as long file names no longer get mangled when sent to Exchange 2010. Didn't test later Exchange versions, as that's hopefully unnecessary. :) Thanks!, -Aaron
Comment by Aaron N.
31266 | September 02, 2019 11:17:18 AM GMT