Skip to main content

Cloudmail

Table of Contents:

Cloudmail

Overview​

360Works CloudMail is a plug-in for sending outbound e-mail messages and monitoring e-mail interactions using Amazon Web Services.

Sending: CloudMail offloads the actual e-mail sending to a virtual machine set up in your Amazon Web Services (AWS) account. It queues the e-mail contents and distribution list(s) almost instantly, leaving your computer free for other tasks. The virtual machine then starts processing all the actual e-mails. It removes duplicate addresses, removes anybody that has requested an unsubscribe, and then starts sending them via Amazon's Simple Email Services (SES) at whatever sending rate your AWS account is set up for (10 per second by default, but expandable to hundreds per second upon request).

Campaign Metrics: CloudMail automatically takes care of Unsubscribes. It also embeds tracking codes into the e-mail message that will allow your FileMaker database to see how many people viewed your message, and how many clicked a link in the message. Whenever you want, you can run a script to download activity related to your e-mail campaign. This will import Deliveries, Bounces, Complaints, Clicks, Views, and Unsubscribes

You can run this script as often as you like, and you can also schedule it to run at regular intervals using FileMaker Server. Every time the script runs, it will only download new activity since the last time it was run.

User Guide​

See the 360Works CloudMail User Guide for a comprehensive list of all functions, their parameters, and their usage.

Demo mode​

You can use CloudMail in demo mode, as much as you want, for up to 10 recipients. After 2 hours of use, you will need to quit FileMaker and restart to continue using the demo. A limited privilege 360Works Amazon Web Services (AWS) access key is already embedded into the demo, allowing you to start sending and monitoring emails instantly!

The 360Works access key is shared with other people using the demo. Therefore, it is possible that when you download the results of your test campaign, you will see the results of the last person to try the demo, if they did not download their test results. Also, keep in mind that if you do not download the results from your test, other people will see your results, including the e-mail addresses that you used for testing. This is normal behavior when using the 360Works shared access key. To prevent this from happening, be sure to download the results from your test campaign, or better yet, you can set up your own free AWS account and use that with CloudMail

These are the demonstration access keys, in case you type over or otherwise lose the ones that come with the demo file:

Access key: AKIAIMZPKY3OKOCVKJEQ
Secret key: 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

Pricing​

There are two components of pricing for CloudMail: The cost of the plug-in itself, and the cost for Amazon Web Services.

The plug-in cost is $395 US with optional yearly maintenance renewals (25% of the cost of the license per year).

Amazon's charges can vary over time (usually gradually decreasing). In addition, there is special introductory pricing for the first year after you open a new AWS account. Find the latest pricing for AWS Simple Email Service here.

Moving to production​

There are a some required steps and a few optional steps to complete before sending your e-mail campaign to thousands of recipients.

Required steps​

You must set up an AWS account.

When you set up a new AWS account, your e-mail sending is limited to 'sandbox' mode. In sandbox mode, your maximum sending rate is just 1 message per second, your maximum daily messages is limited to 200, and you can only send to verified recipients. Verifying a recipient is what you did when clicked the Amazon e-mail in your inbox to be able to send the quick start campaign. To send to additional recipients besides yourself, you can either 1) verify additional recipients using the Amazon Web Services SES console, or 2) request that your account be switched to production mode.

Important

Production mode is region specific. CloudMail currently only works in the US East (N.Virginia) us-east-1 region. Before going into production mode you must change your geographic location on the AWS console home page to this region. See AWS Production Mode for CloudMail.

Submitting a support request to AWS​

In order to put your account into production mode, you need to submit a support request to AWS:

  1. Log in to your AWS account and set the region to US-East-1 N.Virginia
  2. Do a search for the Amazon Simple Email Service (SES) and select it from the results
  3. Once in the SES module, select Get Set Up from the navbar on the left.
  4. Follow the wizard to submit your request to Amazon

AWS will email you if/when your request has been approved. If you are having issues getting your account approved, please contact us as we may be able to help!

Optional steps​

Once your AWS account is put into production mode, your daily limits will be substantially increased. You can see these limits in the SES dashboard in the AWS Web Console. However, if you send large email campaigns, it may still not be enough. You can submit additional requests via the AWS web console to request higher limits, both in terms of maximum messages per second and maximum messages per day.

It is highly recommended that you follow the process for domain verification in the AWS web console. This involves setting up DKIM records, which make it much less likely for your outgoing messages to be marked as spam by the recipients. DKIM allows Amazon to send e-mail through its own servers while having the receiving e-mail servers treat the message as if it arrived from your own company's email server. See the AWS documentation here for setting up DKIM records

You can get the public IP address of your virtual machine by going to the Elastic Cloud Computing (EC2) section of the AWS Web Console. If you like, you can then create a record in your DNS server, such as cloudmail.mydomain.com pointing to that IP address. You can then configure this DNS name in the CloudMail.fmp12 file, and that will cause all links in your outbound e-mails to point to this name instead of a default Amazon DNS name.

Unsubscribe​

In order to add an unsubscribe link to your emails, add [UNSUBSCRIBE] to the body of your email. When you send it, CloudMail will replace the [UNSUBSCRIBE] with a link to an unsubscribe page. Please note that this is just a find and replace operation so if you just have [UNSUBSCRIBE] in the HTML then this will show the entire link in the body of your email. If you want the word Unsubscribe as a hyperlink in the body of the email, make sure to put [UNSUBSCRIBE] in a tag like so:

<a href="[UNSUBSCRIBE]">Unsubscribe</a>

Once this form has been filled out, the email address will be added to your CloudMail blacklist. This means that even if you have not removed the email from your campaign recipients, emails will not be sent to them. This will work with both html and plaintext emails. To remove an email from the CloudMail blacklist use CMRemoveFromBlacklist

note

The CloudMail Blacklist is not the same as the AWS Suppression List. Amazon automatically adds email addresses to the AWS Suppression list when it has recently caused a hard bounce. You can remove addresses from the AWS Suppression list through the AWS console.

Personalized Messages​

It is possible to send personalized messages with CloudMail. However, the CloudMail.fmp12 file is not currently set up to do this, so you will either need to have CloudMail integrated into your own solution or modify the .fmp12 file.

To accomplish this you will need do a few things:

  1. Store your message template with placeholders for the information that you want to personalize such as the recipient names, address, etc. in a field.
  2. Create a loop that loops through your found set of intended recipients. The loop will need to call the Substitute script step for each placeholder, substituting in the personalized text and then storing the modified template in a variable. It will then need to call CMAddRecipient to add the current intended recipient to the recipient list.
  3. Call CMQueueMessage passing in the variable holding the personalized message text as the htmlMessage and/or plainTextMessage parameter, the subject, the fromAddress, and the campaign name. Be sure to use the same campaign for every iteration of the loop so that the results of the campaign are accurate.

Policies on Sending Bulk Emails to Gmail and Yahoo accounts​

In the first quarter of 2024, Gmail and Yahoo will be changing the requirements for email senders who send more than 5000 messages to their services in a single day. Any sender that doesn't meet the new requirements, may have their emails silently filtered by either Gmail or Yahoo. Requirements are as follows:

  1. Authenticate their email: Gmail and Yahoo will expect you to set up a DKIM for your sending email address. This means that the sending email address will have to come from a domain that you own. For instance, we own www.samplewebsite.com, you can verify ownership of that domain to send from sampleuser@samplewebsite.com. For instruction on setting up a DKIM for your sending email, see the optional steps.
  2. Enable easy unsubscription: see the unsubscribe documentation.
  3. Ensure they’re sending wanted email: Google is going to start blocking email senders who exceed a certain spam rate. Google didn't give a specific rate, but an AWS email indicated that any sending email address that gets reported as spam by over .3% of recipients will start getting blocked. Make sure those unsubscribe links are easy to find at the bottom of your email.

You can review the documentation of Gmail's new policy here and Yahoo's new policy here.

If you need help authenticating your email sending address against a domain, please contact us at support@360works.com.