<p>I am considering converting a project that I've inherited from .net 1.1 to .net 2.0.  The main warning I'm concerned about is that it wants me to switch from <code>System.Web.Mail</code> to using <code>System.Net.Mail</code>.</p>

<p>I'm not ready to re-write all the components using the obsolete <code>System.Web.Mail</code>, so I'm curious to hear if any community members have had problems using it under .net 2.0?</p>

[{'answer_id': 64620, 'author': 'Esteban Araya', 'author_id': 781, 'author_profile': 'https://Stackoverflow.com/users/781', 'pm_score': 0, 'selected': False, 'text': "<p>Yes, we had the same issue, and we decided not to upgrade either. We haven't seen any problems, so you're OK ignoring the warnings.</p>\n"}, {'answer_id': 64628, 'author': 'Curt Hagenlocher', 'author_id': 533, 'author_profile': 'https://Stackoverflow.com/users/533', 'pm_score': 8, 'selected': True, 'text': "<p>System.Web.Mail is not a full .NET native implementation of the SMTP protocol. Instead, it uses the pre-existing COM functionality in CDONTS.  System.Net.Mail, in contrast, is a fully managed implementation of an SMTP client.</p>\n\n<p>I've had far fewer problems with System.Net.Mail as it avoids COM hell.</p>\n"}, {'answer_id': 64960, 'author': 'Jeremy', 'author_id': 8557, 'author_profile': 'https://Stackoverflow.com/users/8557', 'pm_score': 3, 'selected': False, 'text': "<p>The few times I ran into this, I found that that the methods and properties were all almost identical- changing the object type was just about all I had to do. There were one or two other little things, but they showed up with the lines and it was obvious what to do with Intellisense. I'd vote for going with the fully managed solution, get away from cdonts as soon as possible. It's not even installed on 03 server and newer.</p>\n"}, {'answer_id': 72533, 'author': 'Mike L', 'author_id': 12085, 'author_profile': 'https://Stackoverflow.com/users/12085', 'pm_score': 3, 'selected': False, 'text': "<p>System.Web.Mail is deprecated, but should still work.  You'll be annoyed with warnings about it being obsolete, but the functionality still carries on... for the time being.</p>\n\n<p>I would agree with others that the conversion to System.Net.Mail was very trivial.  I doubt you'd have to re-write more than a line or two.</p>\n"}, {'answer_id': 74634, 'author': 'quimbo', 'author_id': 12250, 'author_profile': 'https://Stackoverflow.com/users/12250', 'pm_score': 3, 'selected': False, 'text': '<p>here are 2 sites that provide documentation and samples for both</p>\n\n<p><a href="http://www.systemwebmail.com/" rel="noreferrer">http://www.systemwebmail.com/</a></p>\n\n<p><a href="http://www.systemnetmail.com/" rel="noreferrer">http://www.systemnetmail.com/</a></p>\n'}, {'answer_id': 1597131, 'author': 'Grace', 'author_id': 193381, 'author_profile': 'https://Stackoverflow.com/users/193381', 'pm_score': 0, 'selected': False, 'text': '<p>We had implemented .netmail it was working at the beginning now is requiring username and password. So we went back to webmail as is working OK.</p>\n'}, {'answer_id': 3654224, 'author': 'Travis Heseman', 'author_id': 175094, 'author_profile': 'https://Stackoverflow.com/users/175094', 'pm_score': 3, 'selected': False, 'text': "<p>Biggest issue with System.Net.Mail is that it has no support for Implicit SSL.  Use System.Web.Mail until you don't have a need for Implicit SSL support.</p>\n"}]
['https://Stackoverflow.com/questions/64599', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/7856/']