Hey guys – My only concern is the short-sightedness of Email On Acid’s spam tester. EOA and Litmus both examine your email’s content to make sure there aren’t any pieces of code or words that will trigger a spam filter. They are essentially using a criteria to examine the code of the email and make suggestions to help you not get got.
ReturnPath’s inbox placement tests actually test the entire content of the email. They provide you with a seed list of about 100 emails, all from different domains (yahoo, Comcast, AOL, Hotmail, Verizon, etc.). You then send a live email to the seed list, and RP will tell you whether the email was placed in the inbox or not, and will generally tell you why. This is a more effective way of testing because it takes into account the entire email: IP address, authenticated domain of the sending address, info in the header of the email, subject line, and email content. This multidimensional approach will tell us not only if our content is bad, but if the system sending the email is bad, too. Let me know if you have any additional questions; happy to help! Brent Walter Marketing Automation Strategist, DEG 913.951.3112 (direct) | [email protected]<mailto:[email protected]> From: Benjamin Niolet [mailto:[email protected]] Sent: Thursday, July 9, 2015 2:47 PM To: Ryan Kelly Cc: John Gruen; dev-fxacct; Christopher Karlof; Brent Walter Subject: Re: Let's set up a proper spam testing system +Brent Walter from DEG Thanks for the question. For what it's worth, I use Email on Acid for inbox preview testing and like John, I'm paying out of pocket and getting reimbursed. Might be time for a better deal / license. Email on Acid offers seed testing, which is the same type of service I mentioned to Ryan in Whistler. The basic gist of how it works is you send an email to a bunch of inboxes controlled by the testing service. They are able to report on whether the message made it to the inbox (might have gone to spam or might have even just gotten lost in the mail. Strange but true). I have never used Email on Acid for seed testing, but I suspect it's a lot cheaper than ReturnPath, the service I'm most familiar with. Since we already have an Email on Acid account in use, and from what I can tell, seed testing is included, this seems like the right service to start with. Brent, any flags or blockers on using Email on Acid for seed testing the AWS confirm emails for accounts? Ben Niolet | Email Marketing Manager Mozilla | [email protected]<mailto:[email protected]> On Thu, Jul 9, 2015 at 1:38 AM, Ryan Kelly <[email protected]<mailto:[email protected]>> wrote: On 9/07/2015 03:13, John Gruen wrote: > We should really be doing a better job of automating and testing spam > scores for FxA emails. One of the major factors determining email > spammy-ness is the overall reputation score of the email service > provider. This means that running spam tests from localhost will not > produce consistent, representative data.* > > Thus far, we’ve been using Email on Acid to test our emails. In Email on > Acid world, a proper spam test would mean sending emails from our > production servers to a specific set of secret email addresses provided > through the EoA account. I’ve generally enjoyed using EoA, but maybe > there is better tooling out there. Either way, I think we should do a > better job establishing situational awareness about where our emails end > up. It’d be great if the whole thing were automated so that when we > deployed each new train, we automatically kicked off full email test. Sounds extremely worthwhile. I'm cc'ing Ben who may be able to comment on whether EoA is the best choice for automating this, or if we have existing agreements with a similar service. I recall him mentioning a similar-sounding service at Whistler. > Oh, also, it seems like we could buy a team license to EoA or Litmus and > I could stop paying for this stupid thing out of pocket. We are, after > all sending out a TON of emails. Thoughts? Yes, assuming with stay with EoA, we should definitely do this! LMK if you're paying out of pocket for any other services as well, and we'll make sure we get better arrangements in place. Cheers, Ryan
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
