VS.NET 2010 (and above) Users Click Here   

Licensing FAQ
Software Updates
Support Forums
Feature Requests
About Us
Contact Us
Hosting Companies
Privacy Policy
Shopping Cart


web site
What is aspNetEmail?
  aspNetEmail is a .NET email component, also known as an assembly. It is written in 100% C# for speed and efficiency. It does not have any dependencies on CDO or any unmanaged code. aspNetEmail only requires the .NET framework to be installed on the computer.
Can I use aspNetEmail in windows applications?
  Absolutely! The name aspNetEmail was chosen by the marketing division, but from a programmer’s perspective, you can use aspNetEmail from a Windows Form application, web services, ASP.NET web pages, and any other .NET supported application.
What can aspNetEmail do for me?
  aspNetEmail allows you to send email from any .NET application. aspNetEmail can be used from ASP.NET web pages, to windows forms, to web services. The only limitation to using aspNetEmail is your programming imagination.
What isn’t aspNetEmail?
  aspNetEmail is not a mail server or a mail reader. aspNetEmail cannot receive email nor can it read email messages. aspNetEmail is used to send email messages, programmatically, from any .NET application.
What’s the difference between aspNetEmail and System.Web.Mail?
  The advantages of aspNetEmail over System.Web.Mail are too numerous to list, but here are some of the major differences. System.Web.Mail is simply a wrapper around CDONTS. When you call System.Web.Mail you are actually making an unmanaged call to CDONTS. To verify this, take a look at these two ILDASM figures: Figure 1 and Figure2. Besides the inefficiency of CDONTS, aspNetEmail also provides advanced logging, mailmerge functionality, and advanced mail message manipulation.
System.Web.Mail works for me, why should I buy aspNetEmail?
  If System.Web.Mail works for you, then great! By all means use it. We want you to use the right tool for the job. The last thing we want is someone to purchase aspNetEmail and then be unhappy because they find System.Web.Mail can do what they need. But based upon our personal experiance, System.Web.Mail has been unstable, which lead us to write aspNetEmail. Just how unstable? Well, take a look at some of these problems over at Google Groups.

And if all else fails, here's a post from someone at Microsoft telling you to use RegMon or FileMon to trouble shoot the problem. View Post

And in case you think that post is unique, here is another, different one

Nothing like deploying a client app, then 1 month after they have been using it, it blows up, and you send him this lengthy explanation to go into the registry. :-) Want to see what people have been saying about aspNetEmail? Read some of these 3rd party testimonials.


What's New

Latest .NET Versions
aspNetEmail runs under all releases of .NET. From 1.0, to 1.1 to the current release.

iCalendar Serialization
Added Serialization and Derialization methods to the iCalendar class for developer flexibility.

Better Attachment Filename Control
Exposed the InvalidPathChars array for developers to control aspNetEmail's filename character filtering capability.

Sender Properties
Added the Sender property, to set the Sender header. Also added the config option to set the Sender from the .config file.

Added the CssOption to the MhtUtility class for better control over MHT sources.

MhtUtility Class
Created and added the MhtUtility class. This class is used for creating email based upon MHT (MHTML) sources.

HtmlUtility Class Expansion
Expanded the HtmlUtility class with many more features to allow better manipulation and control over different Html sources.

Queuing Classes
Added more support for filesystem queueing. This allows aspNetEmail to take advantage of 3rd part email systems, and submit files directly to their queues. Currently aspNetEmail natively supports the IIS SMTP Service, Mail Enable, IMail, SmarterMail and all RFC2822 formatted queues. Additional support for other mail systems is in development.

NTLM Authentication Support
aspNetEmail support native NTLM authentication support for authentication against Microsoft Exchange Servers

TimeZone Expansion
Expanded the internal TimeZones that can be used by aspNetEmail for creating iCalendars.

Large File Support
Added the capability for aspNetEmail to stream large files directly from the filesystem to the SMTP server, without loading the entire file in memory. This allows for very large files to be emailed with a minimum memory footprint.

Direct SMTP Data Support
aspNetEmail now supports directly emailing RFC2822 formatted files from the filesystem. This allows for very fast SMTP sends, without creating the email in memory.

CSV Data Support
aspNetEmail now supports using CSV files as data sources for mail merges.

iCalendar Improvements
We've worked hard to improve the iCalendaring classes in aspNetEmail. We now check for null Organizers and Attendees, and intelligently populate those classes if the information is available in the EmailMessage class.

  • Formatting classes have been exposed so you can more easily control how the iCalendar objects are formatted in emails.
  • A new option has been added for those Exchange-only users. If your recipients will be using MS Exchange, the iCalendar format can be optimized for those users.
  • We've also added the capability to easily cancel iCalendar events, along with better support for those TimeZones that recognize daylight savings time.
  • Got your own custom implementation? No problem. aspNetEmail's calendaring supports custom iCalendar properties.
  • Better support for automatically loading binary data.


SSL Support
With the release of the AdvancedIntellect.Ssl.dll, aspNetEmail now support secure SSL connections. With as little as 2 additional lines of code you can enable your application to securely communicate with your mail server. The AdvancedIntellect.Ssl.dll can be downloaded from http://www.advancedintellect.com/download.aspx at no charge

aspNetEmail now allows partially trusted callers to make requests into the aspNetEmail.dll. This option allows it to be hosted under the ASP.NET 2.0 and greater runtime.

HTML Manipulating Improvements
We've worked hard at making it even easier to manipulate HTML for your email messages.

  • The HtmlUtility class now supports cookies and sessions so you can download data that needs to maintain cookie state across WebRequests.
  • >
  • Automatically remove all Anchor tags from your HTML to control how the documents maintains it’s links.
  • Automatically embed images from templates created in ASP.NET forms.
  • Now you can replace all unwanted HTML tags and elements with an empty string, simply by setting an option.
  • Remove those unwanted HTML Form INPUT controls with a single option.
  • Convert all relative Anchor tags to absolute Anchor tags so they are resolved correctly.
  • Automatically embed images found in CSS files.
  • Control the TimeOut value now used to download content from remote HTTP locations.
  • New HTTP Proxy support to retrieve HTTP content from behind proxy servers.


More Events
We've added more events for the advanced developer to work without products.

  • Now you tie into the EmailMessage it is sent to the server for last millisecond manipulation.
  • Tie into the WebRequest object so you can finely control how content is downloaded over HTTP.
  • Wire up the OnError event to maintain and log each error generated by aspNetEmail in your application.


Advanced Email Address Parsing
Now you can set your email addresses using complex aliases and names, and aspNetEmail will automatically set the appropriate To, Cc, Bcc and From properties.

Direct Sending
Now you can better control how email messages are sent directly without a relay server. The internal MX resolution engine has been optimized along with offering you more options for controlling the DNS servers used for queries.

Better Support for IIS SMTP Service
Some IIS SMTP service implantations have a known 'DotStuffing' bug. We've built the solution in, so you don't have to apply the Microsoft patch found at http://support.microsoft.com/?id=286358.

Better Support for Multihomed machines
Does your server have multiple IP addresses? Now you can selectively control which IP address is used for sending all email.

Better Application Exception Emailing
Do you use aspNetEmail to email exceptions generated by your application? Now aspNetEmail can automatically serialize them to an attachment, so you can recreate them on your development machine, and determine why an application is throwing an exception.

Better Support for EmailTemplating
Due to great customer feedback, we've improved automatic email templating

  • Automatically encode ASP.NET form submitted data to programmatically format how it is viewed in the email client.
  • Better support for SELECT controls where you can control the selected label and the selected value.


Better Support for Mail Merges
Now you can perform a mail merge on your own custom objects/classes. Perform a mail merge against both properties and fields.

Better Attachment Handling
We've improved our attachment handling capabilities to support even the most discriminating developer.

  • Need advanced control of an attachment's headers? Now you can add custom headers along with controlling the specific characterset used to render the attachment on the end users email client.
  • Easily convert EmailMessages to attachments with one method call.
  • Better support for non US-ASCII filenames in zipped attachments.
  • Irregardless of your data source, now you can control the binary data of the attachment.


Better Debugging and Troubleshooting
We've added even more logging statements to be written to the debug log for easier troubleshooting. If you run into a problem using aspNetEmail, simply enable logging, and read the log in any text reader (ie Notepad). You may not even need to contact Advanced Intellect for support. Suggestions may be found right in the log file.

Programmatically Forward and Reply to an Email
aspNetEmail makes it even easier to Reply or Forward an email. No longer do you have to worry about complex formatting. aspNetEmail can handle all of the hard work for you.

Better Serialization
Now you can serialize aspNetEmail to your own data store using your own serializers.

Stronger RFC2822/822 Parsing Routines
With aspNetEmail, you can populate an EmailMessage with any RFC2922 data source. aspNetEmail has been improved, and become more accurate at parsing RFC2822 formatted messages. Whether a string, byte array, or file, aspNetEmail can convert a RFC2822 message into a completely accessible EmailMessage object. aspNetEmail now provides:

  • Optional control if you want exceptions thrown on broken messages.
  • Better optimizations for HTML formatted messages
  • Better support for attachments that also double as embedded images.
  • Better support for non US-ASCII header support.
  • Better support for broken Quoted-Printable and Base64 encoding routines.
  • Better support for uncommon RFC 2822 headers.


Want more? Be sure to check out our complete feature list here.




I'm very impressed with the component! "

Jay | iconologic.com

Read more testimonials
ListNanny aspNetDNS aspNetEmail aspNetPOP3 aspNetMX IPMuncher aspNetMIME aspNetPING aspNetTraceRoute aspNetIMAP aspNetMHT