Avatar

Correct answer by
Employee

Hello Rajesh,

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 :

calculated attachment.png

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

Regards,

Adhiyan

View solution in original post