Maybe everyone will be very disappointed, why do the .NET's SMTP does not support ESMTP (identity authentication), now which SMTP does not need to authenticate? Really depressed, Microsoft likes to do this kind of chicken rib. Just starting to use .NET's SMTP, it is already in 2002, it is found that it does not support ESMTP, simply switch to Jmail, which is to use Interop, this method is indeed, it is not pure .NET It is also the weight of the right. Later, because the receiving part used I participated in the development.
OpenPOP.NET
, Found that the effect is good, simply use pure .NET, send part
Opensmtp.net
. Recently found
REFLECTOR
This thing, its anti-compilation effect is good, it is only a letter of function, it is too uncomfortable, later
HBifts
Introduce one
Reflector.fileDisassembler
It is much more effect, but unfortunately, it can only solve it by Assembly, they are very extreme, a solution, a solution assembly, is not to solve class, it seems that I have to write a plugin. Back to the topic, since I have a tool, I will compile it. The whole system of the .NET is completed, where I am most concerned about the implementation of SMTP, I found it actually used the historical relics of CDONTS! ! ! Even TCPs are not used, as well as those chicken ribs, really disappoint! ! ! ! At the same time, I also found that MimeMapping classes are in me.
OpenPOP.NET
The method of realization is exactly the same, it seems that the developer is not awkward. And its mail encoding is only Base64 and uuencode, and there is no very common quoted-printable. I suggest you use
Opensmtp.net
, Open source, powerful, supporting most of the SMTP characteristics, in addition to standard normal transmission and any multi-accessories, also supports Equation, such as ESMTP (identity authentication), related types attachments, particularly good Chinese support, etc.
