We are trying to attach a pdf file (from the folder placed on C:// drive for testing because, FTP is not supported) during the email delivery in the template.
I got an error below.
1. How to resolve this issue?
2. Post the testing of attaching the files from desktop, i would like to do the same from an FTP location. How can i do this (any SFTP/other server location Adobe provides from where i can attach the files)?
PS: We have a hosted version of Adobe Campaign v6.1
This is a known limitation when using calculated attachments uploaded from the local system . The reason is that when the attachment is prepared during delivery analysis , the MTA is responsible for preparing the attachment. The MTA for a hosted environment runs on a debian(linux) server and the local file being on a Windows OS causes a compatibility issue and creates the wrong path for the file by appending usr/local/neolane/ (default location of a campaign instance) ahead of the file name.
To overcome this you can :
1>. Use a file from a public location like this :
2>. Else , like you have mentioned , you can have the file on a SFTP server and mention the path of the server here like :
/sftp/<user>/incoming/<file_name> in place of the public url
3>. Create a workflow to generate the file on the workflow execution and then export the file to the var/<instance_name>/export folder using the data extraction activity and then use the delivery ,attachment name should be : export/<file_name>
Hope this helps
I saw that once the calculated attachment is configured in message center template and for any reason MTA is not able to locate the file; emails are not getting delivered. Is it a expected behavior Or we can do something in configuration so that emails can be delivered even if the file to be attached is not found ?
Kindly let me know.
No , unfortunately not . This is a limitation . The personalization of the calculated attachment is done by the Mid MTA and hence the path will be appended when using mid-sourcing.
You can see the solution described at the beginning of the topic and see if it works for you.
1>. Use a SFTP location to pull the files.
2>. Use the URL of a public location (like google drive) to fetch the files.
The SFTP path appears to be correct and if the same location syntax works for file collector it should work in delivery attachment as well.
It does look like though a Linux server is involved . May I know which mode you send the delivery from, are you using a mid-sourced server by any chance ?
Yes the file name is being passed in the target data. The data in flat file is reconciled to the recipient in nms:recipient and then the target data from the file is still passed for dynamic use. This setup works fine when there is no attachment involved. If I do a standard delivery (no attachment) the file attachment data is populated successfully in the content of the delivery within the <%= targetData.cAttachment %> block, so there is no issue of the file name being directly passed correctly.
Here is a screenshot of the logs -- it failed and went into retry pending. It looks like it was due to adobe appending the location with the standard linux sftp location. How do i prevent this since we are not adobe hosted and I do not want the path to be appended, and still remain dynamic
General question. Is it possible to do a dynamic pull of a file from an on prem sftp with this delivery setup? Am I setting up the delivery correctly? The file path works fine when using a file collector/export.... which is why I find this strange.
When you are using targetData.cAttachment , is the value for cAttachment being passed via a workflow ?
Can you share the logs of the delivery which is failing , it can provide some idea about the failure .
I have a similar issue; however, in my situation we are using an on prem hosted solution on windows server. I am trying to pull a file, dynamically, based off data that is passed in the targeting. The path to the SFTP which has been successfully tested via a file collector is as follows: E:\SFTP_ROOT\sftpuser01\AdobeCampaign\Inbound\AbuseCampaign\
Here is what does work:
1. File collector referencing the above path is able to pull the file, so there is no access issues.
2. Hardcoded File Path attachement --- A delivery is successfully able to attach the file if the attachment setting is set to "File name is specified when creating the delivery template." This works if I put the above sftp location and hardcode the file name. A personalization block does not work here, so dynamic pull of the file does not work here.
Here is what does NOT work:
3. Dynamic file pull test based on target data --- If I select "File name is computed during delivery for each message" and include the file path as either the hardcoded path or one that includes a personalization block, the delivery fails and goes into pending . There is no information in the log about the file. Am I incorrectly referencing this path? Is this feature not able to pull a file based off the SFTP using a file path that has a dynamic variable produced in the targeting?
Any advice is greatly appreciated.
Adobe Hosted environment SFTP is on the Adobe Serve itself and to access it you just need to give folder path without using SFTP call.
please try below path as is
<Client Name>- > replace it with client name.
For me above path works.
If, it doesn't work, I suggest you contact Adobe Support they will be able to provide you correct path.
It is a hosted environment (v6.1). Please find the details below and help me in constructing the path. We do not have any password.
I tried...various combinations with the info below and nothing worked.
Access right, i will check and get back. I now have only read access as per the log.
Is it Adobe Hosted environment or on- premise ?
If, It is Adobe Hosted then as per my experience you need to give SFTP path as /home/customer/<Client Name>/incoming/ ..... to access SFTP in Adobe Campaign application.
Otherwise, can you also make sure the SFTP path is proper and access on folder is define properly.
We have got the SFTP configured on Adobe server and i used the same for reading the calculated attachment from the sftp server. It is giving me the same error. error screen below.
Http not working for me and SFTP is in the process of configuration and yet to be tested, i am trying to test the 3rd approach of creating the file in the workflow.
This works fine if we are extracting the data and then the csv file (which will be attached as a file in the attachment) of that data, as shown below.
How can i do this to attach pdf file from the local machine or an ftp account (Campaign FTP Test), in a work flow? Something like below.
I was trying to test by using a file from a public location (yet to test the SFTP method, though). Placed the files on my google drive and extracted a shareable link to view the files and pasted the link as shown in the screenshot.
Got the below error. Not sure, if it accepts, https link from google drive instead of http. Any help?