While using "Box" file sharing service to receive emails with attachments, sent through Spotfire Automation services, the attachments might be missing. This is due to the fact that "Box" looks for certain parameters in the back-end to detect email attachments. Spotfire has its own parameters that it uses to attach a file to an email. If the parameters that "Box" looks for are not used by Spotfire, the attachments will be missing in the email received by "Box".

Also, an automated email from "Box" will be sent to the email receiver account, notifying that a file failed to be attached in the email. The automated email will be as below.

All supported environments

"Box" looks for the following HTTP header parameters to detect an attached file in the email.
=====
Content-Type
Content-Disposition
Content-Transfer-Encoding
Content-ID
X-Attachment-Id
=====

Spotfire only uses the following HTTP header parameters .
=====
Content-Type
Content-Transfer-Encoding
=====

Since Spotfire doesn't use the three parameters (Content-Disposition, Content-ID, X-Attachment-Id), "Box" will not be able to detect an attached file in the email. This isn't an issue with Spotfire as it is working as designed. There are no configuration changes that can be done from Spotfire side to resolve this. Users are encouraged to log an enhancement request in the TIBCO ideas portal. 

When using third party content management tools like "Box", users may not receive email attachments sent through Spotfire Automation Services

External: BOX API Reference
https://developer.box.com/reference