{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 可以哭但决不认输i 的问题《What RFCs need to be considered in developing an S》','https://www.manongdao.com/q-577114.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
In theory, the set of Request For Comments (RFC) contain everything that a developer needs to know to build an SMTP client. However, it is not always easy to know which RFCs need to be considered and which ones can be ignored.
Does anyone have an RFC roadmap to steer developers through this? By RFC roadmap, I mean:
- A complete list of RFCs that need to be read and understood, in order to develop an SMTP client.
- An indication of which RFCs no longer need to be considered, because they have been superseded.
- A summary of the relevant RFCs.
- Detail on how the relevant RFCs interrelate to each other.
- An indication of the logical order to read and understand the relevant RFCs.
You should read RFC 5321 first, followed by RFC 5322... assuming you already know how to handle DNS queries.
The old answer used to be read 2821, then 2822... but it seems that it's been updated.
The Wikipedia article has a good list of related RFCs.