Batch FTPZIP - Transactional

Overview

In case FTPZIP executes a Transactional Send, the personal data of subscribers listed in the Recipients.csv file (details here)  aren't imported in MailUp Account Database.  
Email message are sent using MailUp Transactional API. Details about how to enable and configure Transactional Mailing on a MailUp Account are here.  

When FTPZIP works in this way:

• Subscribers listed in Recipients.csv are subscribed to MailUp Account Database, but personal data aren't imported. It isn't a real Data Sync.
  For this reason  in Recipients.csv you can add up more dynamic fields as your account allows (see CSV File Format).
• Personal data of the subscribers listed in Recipients.csv file can be used as Dynamic Fields in the newsletter, if the use of Dynamic Fields is enabled for the account and the Newsletter (see Settings.xml and )
• To work is necessary that the SMTP+ functionality is enabled for the MailUp Account.
• To work is necessary that SMTP+ users are defined for the MailUp Lists.
• FTPZIP manages only immediate Transactional Mailing. Schedulation of Transactional Mailing isn't foreseen at the moment.
• Transactional mailing doesn't allow sending attachments.

SMTP+ user configuration

An FTPZIP transactional  can be configured in two way:

• SMTP+ user used to send message, have to be provided in the Settings.xml. 
  In this case the FTPZIP can send messages from each List of the MailUp account, if the list has an SMTP+ user enabled.
•  SMTP+ user is set in the configuration of the FTPZIP. In this case SMTP+ data must not be provided in the Settings.xml.
  In this case the FTPZIP send messages only from a List of the MailUp account, the list associated at the configured user.

ZIP Archive Structure

Description

Depending on which Operations Mode is indicate in the Settings.xml file, you can enclose in the ZIP archive different kinds of files such as:

• An xml file, named Settings.xml. It is the only file that must be present in the ZIP archive because it will be used to determine the behavior of FTPZIP. 
  For a general view of the XML structure see here). 
• A CSV file, named Recipients.csv. It contains the list of recipients that will receive the newsletter (for a general description see here).
• A HTM file, named Markup.htm. It contains an email message in HTML format (for a general description see here).
• Images that the HTML refers to. They are the list of all file images described in Markup.htm.
• Attachments to be sent with the campaign, if any. Ti is a folder that contains the files that will be attached to the newsletters.

File enclosed in the ZIP archive change based on the kind of operations (full, send, save) described in the Settings.xml file.

Use Cases

In case of the ZIP archive contains some files not necessary for the operation mode described (i.e. operation mode is send but ZIP archive contains same data of a full request), they will be ignored and the operation will be completed.

In case of the ZIP archive doesn't contains all files necessary for the operation mode described (i.e. operation mode is full but ZIP archive doesn't contains the files to create the newsletter), the operation won't be completed.

Following a list of examples of ZIP archive for each operation mode. 

Full 

Create a message without images and attachments 

Create a message with images 

Create a message with attachments  

Create a message with images and attachments 

Send

Save 

Create a message without images and attachments 

Create a message with images 

Create a message with attachments  

Create a message with images and attachments