This is a great step forward in the continued efforts to help protect all users. The technical specification seems to be fairly easy to implement and we are currently testing it with one of our customers already. As we continue through this test I will provide more information as well as any other additional industry news.

For more information please go to http://www.dmarc.org/

What does teamwork have to do with deliverability you might be asking yourself? Well, everything. No matter what your focus is within the digital marketing eco-system, you are on a team and must work with others to ensure that you are reaching your customers and sending them relevant campaigns.

More times than I would like to admit, I have worked with various companies that had no idea who, or what departments, were creating and sending email messages. The problem with this is that if there is not a single vision and global understanding of how your customers are being communicated to, there is a chance that you will lose them as a customer in the long run.

This could happen for a number of reasons; most commonly this is due to over-communication. Without a global view of the various campaigns that are getting sent to each and every customer, there is a good chance they might find the number to be too high for their liking. Because of this, I usually present a number of opportunities to clients in order to reduce the likelihood of this occurring.

1. Perform a messaging audit. For most larger companies, there are different departments that are sending campaigns promoting their particular piece of the business. Many times there are opportunities to work together and combine various programs that potentially can increase your ROI.

2. Control message frequency. Determine the maximum number of messages a customer should receive from your organization in a specified time period. When I first started in this industry many years ago, I would have never believed that there would be an entire business model based on sending daily emails to the company’s entire list. But organizations like Groupon, LivingSocial and others have made this acceptable. The key is to understand if this will work for your business model and if you are setting the proper expectations with your customers. If your company is sending out campaigns from so many different departments that even you aren't aware of them and are surprised to see them,  don’t you think it is likely that your customers will be too?

3. Create a preference center. Allowing your customers to determine the types of messages that they wish to receive as well as how often they want to receive them enables you to maintain that customer in your database with less of a chance of losing them to an unsubscribe or a spam complaint.

As we all work hard to get through this holiday season, remember that you must respect your customers and the valuable space that they are allowing you to take up in their inbox. In order to continue this relationship, it is important to understand how your entire company is communicating with them, and work together as a team to keep them as a customer.

Don’t think that these are things that you can do on your own—you need your entire team. Together, you can continue to be successful as a brand and as a digital marketing organization, because you will continue to reach your customers' inboxes.

1. Scrub Your Lists Regularly. Keep your email lists clean by regularly running them against a register of known bad domains and removing duplicate addresses and role accounts. You can automate the latter by adding “info@*,” “sales@*,” and other common addresses to your suppression list. Your email system may also enable you to automatically suppress bad domains and role-based distribution lists.

2. Remove Bad Domains. Bad domains should be removed immediately. Closely review your failure reports, identify bad addresses and evaluate whether they are the result of a data capture problem or a non-existent domain.

3. Review Data Capture Processes– List hygiene starts with collecting good data. Make sure your sign-up forms prompt users to fix incorrect email address or syntax errors before they are submitted.

4. Actively Manage Hard and Soft Bounces – In addition to having established policies for automatically removing hard-bounced addresses due to bad addresses and unknown users, you should have similar policies for removing soft bounces after a pre-determined number of consecutive failures.

5. Promptly Remove Unsubscribes – Don’t wait the 10 days allowed by CAN-SPAM to process unsubscribes. Remove unsubscribed addresses immediately to avoid users hitting the “this is spam” button and damaging your sender reputation.

6. Mark Inactive Addresses for Reengagement – Transfer inactive addresses to another list that is designed to reengage them.  A good rule of thumb for identifying inactives is no more than 12 months – but 6 months can be preferable depending on factors related to the seasonality of your business.

7. Sign Up for Feedback Loops and Whitelists – Sign up for available feedback loops at your top ISPs to monitor the number of spam complaints generated from your mailings. Similarly, maximize your inbox delivery by signing up for whitelists offered by ISPs and other providers.

For more information, please go to the Speaker Bureau and Deliverability pages. Make sure to check out any others you might be interested in as well.

Just recently Microsoft announced some major changes to what their webmail services such as Hotmail will look like and how users will interact with their email moving forward. One of the biggest reasons Microsoft made these changes was because they realized that getting rid of true spam was not enough. They understand that many people report legitimate emails, such as newsletters, offer campaigns and even notifications. Users might do this for a number of possible reasons

1. They no longer want to receive the email and do not trust the unsubscribe links
2. They feel it is easier to check a large number of emails at once and mark them as spam rather than going into each email and unsubscribing.

Microsoft calls this type of mail graymail, and they have created new ways to help users organize their inbox and remove the clutter. Previously Microsoft had implemented the “Sweep” feature which allowed customers to automatically move specific emails to different folders. They have now taken that technology a step further by creating a specific "Newsletter" folder where they will automatically put newsletters it delivered to users.

Another item that will potentially change the graymail issue is the implementation of the one-click unsubscribe. By utilizing this process, Microsoft will ask you if you want to unsubscribe from the mailing. Microsoft will then respond to the marketer notifying them to remove the user from future mailings. For any mailings received from the marketer after this process was put in place, the mailings will be automatically sent to the Junk folder.

Finally, another change that Microsoft has implemented is the ability to flag emails. Much like Gmail’s labels, or Outlook's flags, this functionality allows users to no longer have to mark messages at unread in order to go back and follow up on items but create flags in order to help them better organize their messages in their inbox.

As a marketer, these changes should not change your approach to your email marketing campaigns. As we have always said at StrongMail, it is all about relevancy. If your campaigns are not relevant to your users, you will not see the returns you are looking for. But if your customers find your campaigns relevant they will look for those emails no matter where they land within their mailboxes.

In addition to deliverability news found here, you can also stay connected to the Email Marketing Insights Blog for more of the latest news in email marketing.

You will see these rejected addresses classified as a 2000 series bounce, normally removed after one hard bounce.  Given this information, your best course of action is to reactivate these rejected addresses from late Thursday, July 14 through Friday, July 15.  You can resend to these addresses normally the next time that you send and the invalid users will be removed normally.

StrongMail customers should log into our Spark customer community for the latest information on addressing the situation.

http://www.linkedin.com/jobs?viewJob=&jobId=1463997&trk=jobs_biz_nprem

When going through the sales process with a new Email Service Provider (ESP) and the topic of email delivery comes up, I simply suggest all marketers verify that the proposed system is technically capable of sending out their campaigns in the required volume and timing requirements, as well as handle all bounce processing, complaints and other necessary functions from a deliverability standpoint. Once the message has gone through the large list of technical checks that the ISPs look for, delivery to the inbox comes down to the sender’s reputation.

If any ESP ever promises you a particular percentage of inbox delivery, make sure you ask them how they plan on backing that up, and if they make the same promise to all of their clients? If they are making this same promise to all of their clients, what will they do if one of them rents or buys a list? What magic tricks do they have to ensure the inbox delivery of those email addresses?

In summary, if you are promised something that sounds too good to be true, it probably is. Please share your experiences with these types of questions and answers here—I would love to hear them.

According to some sources they were trying to merge with Symantec but that fell through this week so they are shutting down.

From the StrongMail point of view we suggest that any customer that was using GoodMail closely monitor their mailings over the next couple of weeks. These customers need to ensure that their feedback loops are set up and working properly and they should utilized the StrongDelivery Tools Mailbox monitor to track any possible reduction in inbox placement.

We have reached out to GoodMail to see if there is any more information at this time and I will share anything additional that we find out.

ARTICLE HIGHLIGHTS:
Marketers must use correct and consistent terminology if they want to understand each other
For example, we need to define "delivery rate" before we analyze our email campaign data
Many people within the email marketing industry have varying perspectives on what granting permission really means
If you live in the South like I do, you probably felt the effects of the recent winter storm. Here in Atlanta, we received around 5 inches of snow within just a few hours, followed by sleet and freezing rain. If you're wondering what the difference is between sleet and freezing rain, you are not alone. It was only after watching endless hours of coverage on this storm that I can now say I know the difference. In the simplest of terms, sleet is precipitation that freezes on the way down -- you can actually see it bounce off of the ground when it hits. Freezing rain, on the other hand, freezes when it hits the ground, causing the ice to form around your rear-view mirrors as you drive down the street.

All this talk of sleet and freezing rain in an email column might lead you to believe that I am experiencing cabin fever from the weather-induced shutdown of Atlanta that has prevented me from getting out of my driveway for the last three days. While this might be the case, the point of explaining these differences is to highlight how often people use terminology without truly knowing what it means.

When discussing email marketing (or any marketing for that matter), if you don't know the true meaning of a term, there is a good chance for not only confusion within your team, but also incorrect interpretation of reports or ideas within the industry. I'm not the first person to present this concept. When it was founded a few years ago, the Email Experience Council began a project to remove the "-" (dash) from "e-mail." The idea was to allow everyone within the industry to consistently communicate in the same format.

Chasing delivery rates
Lately, I have seen some discussions around "delivery rates," a term that is very near and dear to my heart. While most marketers look at this number as the ratio between total number of emails they attempted to send minus those that were not accepted by ISPs, some folks think we should take it a bit further.

I have seen many companies use various mathematical equations to come up with delivery rates, including counting blocked emails as delivered because the emails were "accepted" by the ISP. Most marketers would not agree with this type of formula, but again, if we don't have consistent definitions, how can we accurately analyze our data?

Others have proposed that the industry do away with the term "delivery rate" and simply look at those emails that land in the inbox. The problem with this approach is that I don't know of one system that can track every email's journey into the inbox or bulk folder. While there are some systems out there that attempt to provide this information, the reality is that these programs are only able to determine whether the recipients open the message. Other systems can only give you results of a designated seed list that, to me, is just a statistically significant sample of what probably happened with your messages.

While this information is valuable, data from a small sample (10-20 addresses) should not be something that marketing professionals weigh heavily. Instead, marketers should think of this information as only a partial indication of their overall marketing campaign effectiveness and ROI calculations.

Defining permission
Another term that has been discussed a lot lately is "permission." According to Dictionary.com, permission is the "authorization granted to do something; formal consent." Many people within the email marketing industry have varying perspectives on what granting authorization really means. Some believe that unless the end user checks a box to opt in to site-specific mailings, companies do not have permission to email. Others interpret a user's failure to uncheck a box as permission. Some companies believe they have a right to send you mail because your sister's boyfriend's mother opted in at one time.

The last example is an exaggeration, of course. I do this to drive home the point is that even if the end user doesn't uncheck a box that states that he or she is willing to receive mail from your partners, you don't really have permission. Put yourself in the recipient's shoes: If you were the end user, would you expect to receive a message from your company, or would you wonder how the sender got your email address?

So, while the industry continues to try to agree on various terms, it is important to make sure that the terms you use with your fellow colleagues are understood and agreed upon. Whether you agree with my definitions or not, the industry needs to have consensus on key terms. Only then can we accurately measure and benchmark our programs.

Good luck and good sending.

This means that your info@company.com, deals@company.com and newsletter@company.com are all being assigned different reputations, instead of an aggregate reputation based on any message from your core "@company" domain. Whatever is left of the @ sign is key, as Yahoo doesn't appear to be looking at the "friendly" From name.

Making things even more complicated, Yahoo is assigning unique reputations to each combination of From Name + Domain Name + IP Address. So, if you use two different IP addresses to send messages from deals@company.com, then Yahoo is assigning a separate email sender reputation to each stream.

This change could have a positive or negative impact on your programs depending on your sending practices. If you've been playing it risky with one email stream because the other email messages you send balance out your email reputation, then it's likely that the one email stream will now go to the bulk folder, but you will continue to see good deliverability on the streams that more closely follow best practices. On the flip side, if one bad email slips out, it will only damage of the reputation for that From Name + Domain Name + IP Address combination.

The bottom line is that you should follow best practices across all of your mail streams and closely monitor deliverability for each From name that goes out from your domain.

http://spark.strongmail.com/community/support/blog/2011/01/24/announcement-live-update-44-is-now-available

http://www.returnpath.net/blog/received/2010/12/mx-record/

by J.D. Falk
Director, Internet Standards and Governance
Well, here’s an odd one for you.
Annalivia Ford reports on her blog that AOL’s MX record vanished for three hours this morning. (Anna used to work in AOL’s postmaster team, so she notices things like that. So do some of the denizens of the postfix-users mailing list.)
MX records are a surprisingly useful vestige of a simpler time. Until the mid-1980s, it could generally be assumed that if you wanted to deliver mail to foobar@kremvax.example.com, you’d open a connection directly to the server named kremvax.example.com and transfer the message. But this only scales so far: what happens if kremvax.example.com goes offline for a while? Or if example.com wants consistent usernames and mailboxes across all of their servers? Or if example.com wants someone else to host their mail?
Then MX records, which are a specific type of pointer in DNS, were introduced. These provided a lot of flexibility: a domain name could have different MX records with different priorities, so that mail servers would attempt to connect to the higher priority (lower number) server first, and lower priority (higher number) servers later as backup. Or, a large site like AOL could have a whole bunch of records at the same priority, permitting parallel load-balancing.
And that’s exactly what they did: mailin-01.mx.aol.com through mailin-04.mx.aol.com all have the same priority, and for further load balancing each of those four hostnames points to five geographically disparate IP addresses.
MX records could also point to servers in entirely different domains. We do this with senderscore.org, whose MX record points to mx.returnpath.net — meaning one server can handle mail routing for multiple domains. These days, this scenario is so common it’s difficult to imagine there was ever a time when things didn’t work that way.
So what happens when the MX record disappears?
Well, to deal with network hiccups and similar issues, any DNS server which had looked up aol.com previously would cache it for about twelve hours. (The cache refresh time is something AOL specified in their DNS record; the default is only one hour.)
If the MX record isn’t in the local cache, some (but not all) mail server software will fall back to the A record — behavior left over from the early days of the network. However, these days A records tend to point to web servers, not mail servers — and that’s certainly true in AOL’s case. None of the three IP addresses in their A record accept SMTP connections.
And if a site looked up aol.com’s MX record during the three hours or so where it didn’t exist, their nameserver will cache the lack of an MX record — for twelve hours! If that’s happened to you, the most effective way to fix it is probably to restart your local DNS servers. You may also have to flush other caches; if so, it may be easier to just reboot.
How do you know if this happened to you? Check your mail server logs. If the server couldn’t connect to aol.com, it might be because of this. But that’s not a particularly big deal, because most mail server software will queue the message until a connection can be made. Only thing to worry about is whether your software will do a new MX lookup before retrying (which is what it should do), or keep pounding away at the A record (bad idea.)
If the logs show that it did connect, and got a response — even if that response is a rejection (5xx) or a deferral (4xx) — then it’s not because of the MX record. The MX record must exist in order to connect to their SMTP server, and get a reply from it.
We haven’t heard, yet, what caused AOL’s MX record to disappear. Chances are, they’ll keep it kinda quiet. It was probably a simple typo — and while I’m sure they have end-to-end monitoring of their mail systems, it may not have been caught until the DNS cache expired.
Have you checked your MX record recently? Would your monitoring notice if it disappeared? Hmm!
You can learn much more about MX records from this wikipedia article, and in RFC 5321 section 5. Or, feel free to ask us any questions in the comments section below.