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. The upcoming verification emails also contain an image served care of our outreach team’s Exact Target service. We should reach out to them to get metrics on HTTP requests for that asset. 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? JG * By way of example: on successive tests to Email on Acid’s spam testing suite from my local build I both passed and failed on AOL mail and Outlook.com <http://outlook.com/>.
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
