• Alomas

    Dyn Inc has a full deliverability team to also help understand why your emails are not reaching certain ISP’s. We also have email seeding that gives you a realistic look at your sending from the inbox perspective. If you want to learn more shoot me an email alomas at dyn dot com

  • Anonymous

    Some good points Mia. When it comes to complex data rules, Our software (Goolara Symphonie) does this better than most with complete dynamic content capabilities available in transactional emails. But I’m not sure what you mean about phishing. Surely this is more of a problem for the email client. A phisher doesn’t have to have any access to your system to spoof your mailings. I get one of these every week from “Amazon,” “LinkedIn,” etc.

    • http://twitter.com/MiaPapanicolaou Mia Papanicolaou

      Hi Jim,

      Thanks for your response.

      To answer your question on phishing: As ESPs, we need to help ensure that emails we send aren’t confused with a phishing email. We should advise clients against sending emails that direct their customers back to an online portal where they need to log in – classic phishing tactics. Furthermore, ESPs should advise clients to include authentication information within the email itself as a way for customers to identify the email as one that comes from the company. This information is partial data that wouldn’t be available in a phishing email such as last 4 digits on the customer’s account and the start of the street address. Employing these methods are a way to start educating customers to tell the difference between a phishing email and one that is sent from the company. This is especially important when it comes to financial services.

      Let me know if you’d like to chat further on the subject!