Developer-roadmap: Add to DevOps: Email
E-Mail has been a core pillar of the web. You should at least know about ESPs, about SPF, DKIM and how to design HTML mails for the most important clients.
minthemiddle
All 3 comments
I brought this up in #101 too.
I feel like email layout is more of a Front-End thing... but sending is more DevOps. I wouldn't ever ask someone in DevOps to do design... best case that's going to get me something as ugly as Craigslist.
Integration with MailChip, Campaign Monitor, etc... good question as to who that falls on. Setting up your own little email service, that's going to be a DevOps task -- but I'm almost to the point where I don't any emails should be sent outside of the CRM any more. Getting email servers whitelisted and all that other crap you have to do to get emails so they end up in an inbox instead of a spam folder... it's just better to offload that to a CRM. ROI-wise, I can't make the case for setting up your own email service.
damengilland
on 22 Apr 2017
Whether you're sending your own email, of you're using something like Mailgun, or relying on an Exchange admin, or something in between, email is still a critical component of development and infrastructure. You need to know when to email, and how to do it. You need to understand that SMTP is not a real time protocol. You need to understand how to secure the transmissions (SSL/TLS SMTP on port 25 or 465 or 587, and which is which; as well as IMAPS POP3S).
Understanding whitelisting and greylisting, DomainKeys, SPF, DMARC, and more are all things that come into play. You don't necessarily need to be a master of any of these, but you need to know about them and how to learn more quickly in order to respond to problems.
skpy
on 21 May 2017
This has been fixed and will be published in the coming release. Thank you 馃檹
kamranahmedse
on 18 Jan 2020
Related issues
TheJaredWilcurt
路
4Comments
azzamsa
路
3Comments
GTHell
路
5Comments
lucaschain
路
4Comments
IuryAlves
路
3Comments
Most helpful comment
Whether you're sending your own email, of you're using something like Mailgun, or relying on an Exchange admin, or something in between, email is still a critical component of development and infrastructure. You need to know when to email, and how to do it. You need to understand that SMTP is not a real time protocol. You need to understand how to secure the transmissions (SSL/TLS SMTP on port 25 or 465 or 587, and which is which; as well as IMAPS POP3S).
Understanding whitelisting and greylisting, DomainKeys, SPF, DMARC, and more are all things that come into play. You don't necessarily need to be a master of any of these, but you need to know about them and how to learn more quickly in order to respond to problems.