Difference between revisions of "Email Marketing"

From Freephile Wiki
Jump to navigation Jump to search
(some notes)
Line 1: Line 1:
 +
There are two related parts to email marketing: making sure that your content is in good form; and making sure that it is actually delivered which is purely technical in nature.
 +
 +
They are related in that all major email service providers (GMail, HotMail, Yahoo!, Comcast, Verizon, etc) scan email '''content''' on the receiving side with some heuristics to determine a 'spam' score in addition to other more 'technical' measures.
 +
 +
== Content ==
 +
 
You want to do an email campaign.  You need to know what works and what doesn't in email these days.  Email is not the web.  It's worse.
 
You want to do an email campaign.  You need to know what works and what doesn't in email these days.  Email is not the web.  It's worse.
  
Line 8: Line 14:
 
# Campaign Monitor offers a number of [https://www.campaignmonitor.com/guides/ guides], including [https://www.campaignmonitor.com/css/  a complete breakdown of the CSS support for every popular mobile, web and desktop email client on the planet].  They also offer hundreds of free to use templates and design examples.
 
# Campaign Monitor offers a number of [https://www.campaignmonitor.com/guides/ guides], including [https://www.campaignmonitor.com/css/  a complete breakdown of the CSS support for every popular mobile, web and desktop email client on the planet].  They also offer hundreds of free to use templates and design examples.
 
# Premailer (http://premailer.dialect.ca/) is a cool service that will allow you to test your email content before you send it.  It will convert CSS styles to inline style attribues.  It gives you HTML and CSS warnings (including those from the Email Standards project).  It will also generate the text-only version for you. Premailer is written in Ruby, with a lot of help from Nokogiri, Hpricot and the Sinatra framework (goodbye eruby). The [https://github.com/premailer/premailer source is available] on GitHub.  As of 2014, there was discussion of making a 2.0 version, but it's 2015 now and there isn't a separate branch, so maybe the "new version" is just being incrementally built into the current.
 
# Premailer (http://premailer.dialect.ca/) is a cool service that will allow you to test your email content before you send it.  It will convert CSS styles to inline style attribues.  It gives you HTML and CSS warnings (including those from the Email Standards project).  It will also generate the text-only version for you. Premailer is written in Ruby, with a lot of help from Nokogiri, Hpricot and the Sinatra framework (goodbye eruby). The [https://github.com/premailer/premailer source is available] on GitHub.  As of 2014, there was discussion of making a 2.0 version, but it's 2015 now and there isn't a separate branch, so maybe the "new version" is just being incrementally built into the current.
 +
 +
== Technical ==
 +
 +
This Rackspace article covers the 3 types of DNS records you need to know about for Email delivery: http://www.rackaid.com/blog/email-dns-records/
 +
 +
 +
Aside from domain SPF records, one option you have for sending is 'smart hosting' which is to say SMTP relaying your mail off to your service provider such as Google Apps.  See [https://support.google.com/a/answer/2956491?hl=en here] for how to configure your Google Apps domain for SMTP relaying.  If you are going to send larger volumes of email than surpass the limits of your Google Apps account, you will want to use the services of SendGrid or Dyn etc.  SendGrid actually has a free service tier for < 17,000 messages per month.
 +
 +
The documentation for CiviCRM has a fairly comprehensive guide to setting up your email. http://book.civicrm.org/user/current/advanced-configuration/email-system-configuration/
 +
 +
Comcast has their 'Postmaster' website for help http://postmaster.comcast.net/index.html
 +
 +
Unfortunately, your hosting provider may be crippling your email service without even advertising the fact. https://warrenguy.me/blog/ipv6-digital-ocean-crippled
  
 
[[Category:Email]]
 
[[Category:Email]]
 
[[Category:Marketing]]
 
[[Category:Marketing]]
 
[[Category:Standards]]
 
[[Category:Standards]]

Revision as of 18:52, 11 August 2015