tracker issue : CF-4019511

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

cfmailparam file attachments and Amazon Web Services file name bug

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Neil Pugh / Neil Pugh (Neil Pugh)

Created: 07/10/2015

Components: Net Protocols, MAIL

Versions: 11.0

Failure Type:

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Normal / Most users will encounter

Locale/System: English / Windows 7

Vote Count: 1

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on September 01, 2019 using build 2016.0.01.298513
Problem Description: If you place a path to a file in cfmailparam that is to a file sitting within an AWS bucket then the attached filename is prepended with the path to the file within the bucket (minus any forward slashes).

Steps to Reproduce: Attach a file to an cfmail email using cfmailparam. Use the file attribute of cfmailparam to specify the full path to the file. Ensure the file is hosted on Amazon Web Services. Make sure the file is not in the bucket root but in one or more nested subfolders. 

Actual Result:The names of the subfolders will be prepended to the server filename when you receive the email in your inbox.

Expected Result: The file is named exactly as it is on the server.

Any Workarounds: Place all your files in the root bucket of Amazon Web Services or use a local file system.

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

Watson Bug ID:	4019511

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

Attachments:

Comments:

+1 ......................
Vote by External U.
6749 | September 23, 2015 01:04:16 AM GMT
Verified on build #295692.
Comment by Akhila K.
6748 | September 24, 2015 02:02:58 AM GMT
Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). Thanks!, -Aaron
Comment by Aaron N.
31256 | September 01, 2019 08:55:52 AM GMT