...
FTPZIP is a MailUp application that allows to send an email message to a defined list of recipients by simply uploading a ZIP archive to an FTP location.
This features is typically used by advanced users that have a need for configuring and sending a campaign without accessing the MailUp admin console, and without using the MailUp APIs.
FTPZIP presents different operations mode. Depending on what you are trying to accomplish, you can enclose in the ZIP archive different kinds of files such as:
- An xml file, called settings.xml (it will be used to described desired behavior of FTPZIP).
- A CSV file containing recipients for the campaign.
- An email message in HTML format.
- Images that the HTML refers to.
- Attachments to be sent with the campaign, if any.
Based on the information enclosed in settings.xml, it is possible to drive the behavior of FTPZIP application and manage the following use cases:
- Send an already defined email message to a list of recipients.
- Send a copy of an already defined email message to a list of recipients.
- Create and send an email message to a list of recipients.
- Create an email message.
Send of email message to a list of recipients. can be executed in two different ways:
- Using MailUp Massive
...
Table of contents | |
---|---|
|
...
It is the only mandatory content of the ZIP Archive.
Settings.xml will contain in XML format:
...
XML structure is divided in three main nodes:
- Header: General data regarding FTPZIP operations
- Content: Data about the Mailing that will be executed
- AdvancedSettings: Data about message creation, Kind of Mailing, CSV File features.
Below a working example. In most cases you can copy this xml content and use it for your own purposes, of course changing the variables that need to be changed to match you MailUp account and campaign needs.
Note |
---|
All xml keys are required even though some values can be omitted. ( such as SenderName or ScheduleDateTime ). |
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<?xml version="1.0" encoding="UTF-8"?>
<FtpZip>
<Header>
<ActionType>full</ActionType>
<CampaignCode>Campaign0009</CampaignCode>
<FormatVersion>0.1</FormatVersion>
<NotifyEmail>peter@example.com</NotifyEmail>
</Header>
<Content>
<ListId>1</ListId>
<ListGUID>08c6348c-1e6b-4ae7-b44c-156fc4a7f012</ListGUID>
<SenderName>John Doe</SenderName>
<SenderEmail>john@doe.com</SenderEmail>
<ReplyToEmail>jane@doe.com</ReplyToEmail>
<EmailSubject>Campaign0009</EmailSubject>
<ScheduleDateTime>2014-11-04T11:20:00.000</ScheduleDateTime>
<ScheduleTimeZone>6</ScheduleTimeZone>
<Notes>Notes for campaign 00009</Notes>
</Content>
<AdvancedSettings>
<Separator>;</Separator>
<Attachments>false</Attachments>
<DynamicFields>true</DynamicFields>
<EmbeddedImages>false</EmbeddedImages>
<LinkTracking>true</LinkTracking>
<HttpLinkTracking>true</HttpLinkTracking>
<HttpsLinkTracking>true</HttpsLinkTracking>
<MailToTracking>false</MailToTracking>
<FtpTracking>true</FtpTracking>
<NewsTracking>true</NewsTracking>
<QueryStringAdditionalParams></QueryStringAdditionalParams>
<ContentOverride>
<MessageId>1136</MessageId>
<CloneMessage>true</CloneMessage>
</ContentOverride>
<SendType>transactional</SendType>
<Transactional>
<Username>sxxxxxxx</Username>
<Password>xxxxxxxx</Password>
<AggregationCode>xxxxxxx</AggregationCode>
<KeepDuplicates>false</KeepDuplicates>
</Transactional>
</AdvancedSettings>
</FtpZip> |
Input fields detail
...
title | Click here to see settings details |
---|
Node <Header>
Name | Type | Requires value? | Sample values | Meaning | Notes |
---|---|---|---|---|---|
ActionType | string | Y | One between "save", "full" or "send" | The kind of action FTPZIP will take with regard to the submitted ZIP archive. When set to save, FTPZIP will only create an email message without importing any recipient or scheduling any mailings. | ActionType is a very important field as its value drives a big shift in the executed tasks. |
CampaignCode | string | Y | Any | This is a unique identifier for the campaign. FTPZIP will read this value at each session to prevent users from uploading the same campaign twice by mistake. |
|
FormatVersion | string | Y | < 0.1 | 0.2 > | This value indicates the kind of xml validation FTPZIP wil run. Current implemented format is 0.1, and it will run xml validation againts its xsd schema definition file. |
|
NotifyEmail | String | N | peter@example.com | An email report containing the process result (success/failure) is sent to the specified address. | Recommended, it is the only way to receive an automated notification in case of errors |
Node <Content>
Name | Type | Requires value? | Sample values | Meaning | Notes |
---|---|---|---|---|---|
ListId | int | Y | < 1 | 2 | 3 > | The numeric identifier for the List in the MailUp account in which the various tasks will be executed (creation of the message, import of recipients, etc.). This is unique within a MailUp account, but not across MailUp accounts. | To locate your lists id’s please see: http://help.mailup.com/display/mailupapi/Codes+Table+and+List+GUID |
ListGUID | String | Y | b947d468-2751-40a7-83bf-1ecca0bbd6a1 | The unique identifier for each List across all MailUp accounts. ListID and ListGUID must refer to the same List. | To locate your lists Guid’s, please see: http://help.mailup.com/display/mailupapi/Codes+Table+and+List+GUID |
SenderName | String | N |
| The display name for the sender in the campaign being created/sent | If empty, the default value for the List will be used. |
SenderEmail | String | N |
| The email address that the campaign will be sent from | If empty, the default value for the List will be used. Mind that this is not an arbitrary field, the sender Email has to be approved withing your admin account to prevent any kind spam like activities. |
ReplyToEmail | String | N | example@email.com | The email address used when the subscriber reply to the received campaign. | If empty, the default value for the List will be used. |
EmailSubject | String | N |
| The email message subject |
|
Notes | String | N | This is a note | The email message note |
|
ScheduleDateTime | String | N |
| The date/time at which the campaign will be sent. If time is too close to current time, or already in past, or left empty, campaign will be sent out immediately. | If you upload many ZIP files with the same scheduled date and time, mailing will run in parallel. If you upload many ZIP files without a scheduled date, mailing will run sequentially, according to the file detection order. If the scheduled date and time is earlier than the actual processing time, the scheduled date&time will be ignored and mailing will be sequential
Transactional Mailing can't be scheduled, so this configuration will be ignored if SendType is transactional. |
ScheduleTimeZone | String | N | 6 | The time zone schedulation will occur for.Please see the time zone reference at the bottom of this section. | if unspecified it will be used western european standard time zone as default. ( GMT+ 1 ). 38 will be used as default when this values has not been specified. It also takes into consideration Daylight saving time for each area.
Transactional Mailing can't be scheduled, so this configuration will be ignored if SendType is transactional. |
Node AdvancedSettings
...
Name
...
Type
...
Requires value?
...
Sample values
...
Meaning
...
Notes
...
Separator
...
String
...
Y if ActionType set to Full, N if set to Newslettter
...
;
...
The column delimiter used in the Recipients.csv file.
...
...
Attachments
...
Bool (string)
...
Y
...
< true | false >
...
Attach files to current mailer campaign
...
If set to true FTPZIP will expect the folder attachments to be included in the submitted ZIP archive
...
DynamicFields
...
Bool (string)
...
Y
...
< true | false >
...
Toggles dynamic fields
...
...
EmbeddedImages
...
Bool (string)
...
Y
...
< true | false >
...
Toggles use of embedded images
...
...
LinkTracking
...
Bool (string)
...
Y
...
< true | false >
...
Toggles link tracking
...
...
HttpLinkTracking
...
Bool (string)
...
Y
...
< true | false >
...
Toggles plain http link tracking
...
...
HttpsLinkTracking
...
Bool (string)
...
Y
...
< true | false >
...
Toggles https link tracking
...
...
MailToTracking
...
Bool (string)
...
Y
...
< true | false >
...
Toggles Mailto tracking
...
...
FtpTracking
...
Bool (string)
...
Y
...
< true | false >
...
Toggles FTP tracking
...
...
NewsTracking
...
Bool (string)
...
Y
...
< true | false >
...
Toggles News Tracking
...
...
QueryStringAdditionalParams
...
String
...
N
...
utm_medium=email&utm_campaign=Nov14+offers
...
Appends a querystring to all included links
...
Suitable for third party campaign tracking systems such as Google Analytics
...
Create a copy of the newsletter described in MessageID Fields.
The copy will be sent.
...
This node will be used only if SendType is transactional, otherwise will be ignored.
...
If false, if recipients.csv contains the same email address more time, only the first will be use. So the email message will be sent only once to an email address.
If true, if recipients.csv contains the same email address more time, every entries will be used. So the email message could be sent more time to an email address.
...
This node will be used only if SendType is transactional, otherwise will be ignored.
Default false.
Time Zones
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Use Cases
Working example of settings.xml for the most common use cases.
Send an already defined email message (massive)
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<?xml version="1.0" encoding="UTF-8"?>
<FtpZip>
<Header>
<ActionType>send</ActionType>
<CampaignCode>Campaign0009</CampaignCode>
<FormatVersion>0.1</FormatVersion>
<NotifyEmail>peter@example.com</NotifyEmail>
</Header>
<Content>
<ListId>1</ListId>
<ListGUID>08c6348c-1e6b-4ae7-b44c-156fc4a7f012</ListGUID>
<SenderName>John Doe</SenderName>
<SenderEmail>john@doe.com</SenderEmail>
<EmailSubject>Campaign0009</EmailSubject>
</Content>
<AdvancedSettings>
<Separator>;</Separator>
<ContentOverride>
<MessageId>1136</MessageId>
</ContentOverride>
</AdvancedSettings>
</FtpZip> |
Send an already defined email message (transactional)
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<?xml version="1.0" encoding="UTF-8"?>
<FtpZip>
<Header>
<ActionType>send</ActionType>
<CampaignCode>Campaign0009</CampaignCode>
<FormatVersion>0.1</FormatVersion>
<NotifyEmail>peter@example.com</NotifyEmail>
</Header>
<Content>
<ListId>1</ListId>
<ListGUID>08c6348c-1e6b-4ae7-b44c-156fc4a7f012</ListGUID>
<SenderName>John Doe</SenderName>
<SenderEmail>john@doe.com</SenderEmail>
<EmailSubject>Campaign0009</EmailSubject>
</Content>
<AdvancedSettings>
<Separator>;</Separator>
<ContentOverride>
<MessageId>1136</MessageId>
</ContentOverride>
<SendType>transactional</SendType>
<Transactional>
<Username>sxxxxxxx</Username>
<Password>xxxxxxxx</Password>
</Transactional>
</AdvancedSettings>
</FtpZip> |
Send a copy of an already defined email message (massive)
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<?xml version="1.0" encoding="UTF-8"?>
<FtpZip>
<Header>
<ActionType>send</ActionType>
<CampaignCode>Campaign0009</CampaignCode>
<FormatVersion>0.1</FormatVersion>
<NotifyEmail>peter@example.com</NotifyEmail>
</Header>
<Content>
<ListId>1</ListId>
<ListGUID>08c6348c-1e6b-4ae7-b44c-156fc4a7f012</ListGUID>
<SenderName>John Doe</SenderName>
<SenderEmail>john@doe.com</SenderEmail>
<EmailSubject>Campaign0009</EmailSubject>
</Content>
<AdvancedSettings>
<Separator>;</Separator>
<ContentOverride>
<MessageId>1136</MessageId>
<CloneMessage>true</CloneMessage>
</ContentOverride>
</AdvancedSettings>
</FtpZip> |
Send a copy of an already defined email message (transactional)
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<?xml version="1.0" encoding="UTF-8"?>
<FtpZip>
<Header>
<ActionType>send</ActionType>
<CampaignCode>Campaign0009</CampaignCode>
<FormatVersion>0.1</FormatVersion>
<NotifyEmail>peter@example.com</NotifyEmail>
</Header>
<Content>
<ListId>1</ListId>
<ListGUID>08c6348c-1e6b-4ae7-b44c-156fc4a7f012</ListGUID>
<SenderName>John Doe</SenderName>
<SenderEmail>john@doe.com</SenderEmail>
</Content>
<AdvancedSettings>
<Separator>;</Separator>
<ContentOverride>
<MessageId>1136</MessageId>
<CloneMessage>true</CloneMessage>
</ContentOverride>
<Transactional>
<Username>sxxxxxxx</Username>
<Password>xxxxxxxx</Password>
<AggregationCode>Campaign John Doe</AggregationCode>
</Transactional>
</AdvancedSettings>
</FtpZip> |
Create and send an email message (massive)
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<?xml version="1.0" encoding="UTF-8"?>
<FtpZip>
<Header>
<ActionType>full</ActionType>
<CampaignCode>Campaign0009</CampaignCode>
<FormatVersion>0.1</FormatVersion>
<NotifyEmail>peter@example.com</NotifyEmail>
</Header>
<Content>
<ListId>1</ListId>
<ListGUID>08c6348c-1e6b-4ae7-b44c-156fc4a7f012</ListGUID>
<SenderName>John Doe</SenderName>
<SenderEmail>john@doe.com</SenderEmail>
<EmailSubject>Campaign0009</EmailSubject>
<ScheduleDateTime>2014-11-04T11:20:00.000</ScheduleDateTime>
<ScheduleTimeZone>6</ScheduleTimeZone>
<Notes>Notes for campaign 00009</Notes>
</Content>
<AdvancedSettings>
<Separator>;</Separator>
<Attachments>false</Attachments>
<DynamicFields>true</DynamicFields>
<EmbeddedImages>false</EmbeddedImages>
<LinkTracking>true</LinkTracking>
<HttpLinkTracking>true</HttpLinkTracking>
<HttpsLinkTracking>true</HttpsLinkTracking>
<MailToTracking>false</MailToTracking>
<FtpTracking>true</FtpTracking>
<NewsTracking>true</NewsTracking>
<QueryStringAdditionalParams></QueryStringAdditionalParams>
</AdvancedSettings>
</FtpZip> |
Create and send an email message (transactional)
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<?xml version="1.0" encoding="UTF-8"?>
<FtpZip>
<Header>
<ActionType>full</ActionType>
<CampaignCode>Campaign0009</CampaignCode>
<FormatVersion>0.1</FormatVersion>
<NotifyEmail>peter@example.com</NotifyEmail>
</Header>
<Content>
<ListId>1</ListId>
<ListGUID>08c6348c-1e6b-4ae7-b44c-156fc4a7f012</ListGUID>
<SenderName>John Doe</SenderName>
<SenderEmail>john@doe.com</SenderEmail>
<EmailSubject>Campaign0009</EmailSubject>
<Notes>Notes for campaign 00009</Notes>
</Content>
<AdvancedSettings>
<Separator>;</Separator>
<Attachments>false</Attachments>
<DynamicFields>true</DynamicFields>
<EmbeddedImages>false</EmbeddedImages>
<LinkTracking>true</LinkTracking>
<HttpLinkTracking>true</HttpLinkTracking>
<HttpsLinkTracking>true</HttpsLinkTracking>
<MailToTracking>false</MailToTracking>
<FtpTracking>true</FtpTracking>
<NewsTracking>true</NewsTracking>
<QueryStringAdditionalParams></QueryStringAdditionalParams>
<SendType>transactional</SendType>
<Transactional>
<Username>sxxxxxxx</Username>
<Password>xxxxxxxx</Password>
<KeepDuplicates>false</KeepDuplicates>
</Transactional>
</AdvancedSettings>
</FtpZip> |
Create an email message
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<?xml version="1.0" encoding="UTF-8"?>
<FtpZip>
<Header>
<ActionType>save</ActionType>
<CampaignCode>Campaign0009</CampaignCode>
<FormatVersion>0.1</FormatVersion>
<NotifyEmail>peter@example.com</NotifyEmail>
</Header>
<Content>
<ListId>1</ListId>
<ListGUID>08c6348c-1e6b-4ae7-b44c-156fc4a7f012</ListGUID>
<EmailSubject>Campaign0009</EmailSubject>
<Notes>Notes for campaign 00009</Notes>
</Content>
<AdvancedSettings>
<Separator>;</Separator>
<Attachments>false</Attachments>
<DynamicFields>true</DynamicFields>
<EmbeddedImages>false</EmbeddedImages>
<LinkTracking>true</LinkTracking>
<HttpLinkTracking>true</HttpLinkTracking>
<HttpsLinkTracking>true</HttpsLinkTracking>
<MailToTracking>false</MailToTracking>
<FtpTracking>true</FtpTracking>
<NewsTracking>true</NewsTracking>
<QueryStringAdditionalParams></QueryStringAdditionalParams>
</AdvancedSettings>
</FtpZip> |
Markup.htm
Markup.xml is the file that FTPZIP will use to generate the email message that will be sent. Note that FTPZIP will run no validation on the actual HTML markup. Making sure that the message was correctly coded and will render as expected in different email clients is up to the author.
The following is a working example of a Markup.htm file content, with HTML code that uses two dynamic fields to include the recipient's name and last name (dynamic fields are replaced with the corresponding values at the time the message is sent by MailUp).
Note that in this example the code contains a remotely hosted image, so no image would be included in the ZIP file.
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<html>
<body>
<br />
<img src="https://upload.wikimedia.org/wikipedia/it/b/bc/Wiki.png" /><br /><br />
<p style="font-family:arial;">Hello, I'm [firstname] [lastname]</p>
</body>
</html> |
Although this sample message only contains a remotely hosted image, FTPZIP supports "locally defined" images. To take advantage of this feature, include the images inside the zip and let FTPZIP to replace the image path accordingly. In this case markup would look like the following:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<html>
<body>
<br />
<img src="Wiki.png" /><br /><br />
<p style="font-family:arial;">Hello, I'm [firstname] [lastname]</p>
</body>
</html> |
Using images in the ZIP file does not require any property or settings enabled. Whatever image you enclose into the zip, FTPZIP will copy it and will attempt to reference it in the HTML markup.
- Path replacement is based on file name. So if you enclose Wiki.png, markup MUST display <img src="Wiki.png" />
- The allowed image formats are : JPG, GIF, PNG.
CORRECT
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<img src="Wiki.png" /> |
INCORRECT
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<img src="http://myurl.com/Wiki.png" /> |
Note |
---|
If you're enclosing an image named the same as one previously uploaded to your Mailup Admin Account, it will be overwritten. |
Recipients.csv
Recipients.csv is the file that will contain the recipients for the campaign when ActionType == full or send
- This file must comply with the formatting policies mentioned at the page http://help.mailup.com/display/mailupapi/CSV+File+Format
- You can add up as many dynamic fields as your account allows.
- You can use any kind of separator, but you must define it in the proper Settings.xml property (“Separator”).
- Make sure Recipients.csv was saved with UTF-8 encoding to avoid loss of special characters in some recipient names or content
Path FTPZIP listens to
Upload the ZIP file in the FTP subfolder “/import_zip” that can be accessed from your FTP root path :
Zip Samples
Note |
---|
When setting up your ZIP archive, please make always sure your archive is not password protected or FTPZIP won't be able to process it and will certainly throw an error. |
Use Cases
Create an email message
As it can be seen, this ZIP archive contains the mandatory files Settings.xml and Markup.htm, one image and the attachment folder. Recipients.csv is not necessary under this scenario as no recipients’ import job will actually take place.
Complete sample Archive for this case can be downloaded HERE
Create and send an email message
ZIP file this time contains Recipients.csv as well, as the full process will require a recipients’ list to import and to eventually send the newsletter to.
Complete sample Archive for this case can be downloaded HERE
Send an already defined email message
...
This case covers the scenario where there's no need to create new message and it will be used th value set in <MessageId> within Setting.xml
Notification alert messages
FTPZIP may run several minutes after the time the ZIP file was uploaded. The system will provide updates on the status of the various processes. Each process will throw at least one notification alert message, normally sent to the admin account at the very end of the process either if it completes successfully or not.
Error Messages
Expand | |||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||
|
Success Messages
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
|
Others
FTP ZIP throws and handles several offline processes.
It means it can’t be waiting for all of them to complete and even if it all seemed to run fine, some error may occur in further steps of the process FTP has no visibility on.
Therefore, it may happen that you are given the success message “CONTENT SUCCESSFULLY DELIVERED TO SERVER”, because FTP actually did its job correctly, and at a later stage receiving a secondary notification such as :
Alert code: Warn001 |
Usually, this kind of error is thrown for formatting problem in the Recipients csv file. Else, wrong field mapping or naming, or when it is attempted to schedule two campaigns at the same time (or nearly the same).
Please take a minute to read more at the URL : http://help.mailup.com/display/mailupapi/SendMessageNL+alerts
Multiple campaigns at once
FtpZip will look for any ZIP archive file in the defined FTP folder.
This means you can upload two or more campaigns at once.
If the first campaign processed should fail, FTPZIP will exit with errors and will step back into the process one hour later to complete the unprocessed sessions.
Execution of campaign that require Massive Mailing can fail do to work process limit of MailUp Import and Massive Mailing management.
We recommend for these reasons to upload multiple campaigns only once you are familiar with this tool and its settings and, in case there is the necessity to send more ZIP archive at the same time, evaluate to use the transactional Mailing.
We recomend to use Massive mailing when it is necessary to send one email message at a time to a big amount of subscribers.
Also, better not to play with multiple campaigns when you’re too close to deadlines or when they have to start too close each other in time.
Faqs
...
title | Click here to read FAQS |
---|
How do I know if a message was successfully created?
Every process, regardless of the result, will trigger an alert notification message to the admin account.
This message, beside describing the actual result, usually returns the Message Id (for both ActionTypes==”full” or ActionType==”newsletter”) and the Send Id only for ActionType == “full”). No Message or Send Id is returned in case of errors.
How do I know if my Settings.xml is properly formatted?
There’s plenty of online xml validators over the web: please try to validate your Settings.xml against one of the following :
- BASIC XML FORMAT VALIDATION - http://www.w3schools.com/xml/xml_validator.asp
- ADVANCED XSD ( Xml Schema Definition ) VALIDATION - http://www.utilities-online.info/xsdvalidation/#.VFisXfmG9LA
For the advanced XSD validation you’ll need the XML schema definition linked below :
What is the attachment size limit?
Although there’s no limitation with regard to the amount of files you can attach to a certain campaign, you must ensure that the aggregate size is below 3MB. Otherwise the file won’t be processed and you’ll be returned an Invalid Attachment Notification message.
How many images can I include in the ZIP file?
There is no limitation.
I submitted my campaign but I'm receiving no result or notification, why?
Please make sure the email address you are monitoring is registered as your MailUp admin account.
How do I know if my file was already processed?
FTPZIP engine usually runs in less then a minute and unless it stumbles into an internal system exception, it will move your ZIP to an internal location for later processing. One suggestion would be to connect to your MailUp FTP host and check if the submitted ZIP file is still on the FTP folder where you left it last time. If it’s there, it means FTP did not yet process it. Eventually, you will receive a notification message after a ZIP file has been processed (NotifyEmail tag has to be specified in Settings.xml).
Can I upload multiple ZIP files to my FTP location?
...
- Send (details here)
- Using MailUp Transactional Send (details here)