My customer receives a complete html file from his mrktg dept with links to graphics that are hosted. I'd like to build him an interface to use this html file as the body for an email blast.

I see that the EmailSetBodyFile function expects a url to the file (not a path or a container field name).

In keeping with the current design, we'll have a queued/approved blast record that will be processed by a server script. The server finds this record, goes to related member records, and loops, creating activity records that serve as the data source for the email that is sent. Another server script runs and finds all "unsent" activities and sends them.

This client uses SuperContainer. Currently, we attach PDFs to emails using EmailAttachFile ( ) and feed this function the SC Raw path for the file.

I was wondering, then, where I should store this html file and how should I specify the URL to the EmailSetBodyFile function? If the function accepted a container, I'd just put it in a container field in the blast record.

I experimented and set the url to that of the html file on my desktop and locally ran the "server script" (with me as the recipient) it all works. However, I do believe that the url must be resolved from the perspective of the FMS for the server script to work.

Any help appreciated.

Barbara

The EmailSetBodyFile function does require a URL as a parameter. Given that you are already using SuperContainer, the easiest way to handle this is to store the HTML files in SuperContainer since this will create a distinct URL for each file.

Thank you, yes. And...for others...that is the RawData url.