Hi Edward, There's no mailing-lists. Last time I created a mailing-list is was basically dead for a similar project, so I'm not in a rush to create them. Emailing me personally or filing issues on GitHub is fine, so... I guess it doesn't matter.
The main advantage of MailKit's SmtpClient is compliance with the specifications. S.N.M is pretty bad when it comes to encoding of filenames of attachments and encoding of headers in general. I *just* saw a website with a list of all the problems with S.N.M the other day and now I can't find it again. I should have bookmarked it. But anyway, yea, MimeKit supports constructing any type of MIME message structure you could dream of whereas S.N.M is limited to the ~3 or so common structures (which is usually fine, to be fair), but it also does not support S/MIME or PGP. Hope that answers your questions, Jeff On Fri, Oct 17, 2014 at 6:37 AM, Edward Ned Harvey (bouncycastle) < [email protected]> wrote: > > From: Jeff Stedfast [mailto:[email protected]] > > > > After about a year in the making for MimeKit[1] and nearly 8 months for > > MailKit[2], they've finally reached 1.0 status. > > Congratulations and thank you for that! I have a few questions - > > Do they have a mailing list or forum or anything? When I look (at least > at MailKit) I don't see anything... > > I see clearly that MailKit does all kinds of cool stuff, with > pop/imap/etc. But there's one question I have in particular. You said you > started out implementing SmtpClient with support for TLS etc. But I > recently used the .Net built-in SmtpClient for the first time, for sending > mail, and had no trouble - I am guessing MailKit's implementation of > SmtpClient is probably much more robust? With support for file attachments > and so on? Is that the main difference or advantage? > > Again, thanks. Cool projects. >
