Hunny Mail.Net Features

Hunny Mail.Net is a .NET class library for sending and receiving Internet mail via SMTP, POP3, and IMAP4.

For even greater functionality, Hunny Mail.Net may be used together with Hunny MIME.Net, a .NET class library for parsing, creating, and modifying messages in MIME format.

Features Summary

  • Standards Compliant - Conforms to RFCs. Tested for interoperability.

  • CLS Compliant - Use from C#, Visual Basic.NET, Managed C++, JScript.NET, J#, and more.

  • Portable - CLS-compliant. May be used with any programming language that supports the .NET framework, including C#, Visual Basic.NET, J#, and more

  • Reliable - Thoroughly tested by our engineers.

  • Thoroughly Documented - Complete reference manual.

  • Includes Helpful Examples - Sending mail. Receiving POP3 mail. Accessing IMAP4 mailboxes.

  • Source Code Available - Well-documented and readable source code available.

  • Support Contracts Available - Reasonable rates by email experts.

Standards Compliant

Our developers follow Internet standards closely, and we make standards compliance a top priority. Hunny Mail.Net offers 100% compliance with the following standards:

SMTP

  • RFC 1893 Enhanced Mail System Status Codes
  • RFC 2034 SMTP Service Extension for Returning Enhanced Error Codes
  • RFC 1652 SMTP Service Extension for 8bit-MIMEtransport
  • RFC 1869 SMTP Service Extensions
  • RFC 1870 SMTP Service Extension for Message Size Declaration
  • RFC 1891 SMTP Service Extension for Delivery Status Notifications
  • RFC 2554 SMTP Service Extension for Authentication
  • RFC 2821 Simple Mail Transfer Protocol
  • RFC 3030 SMTP Service Extensions for Transmission of Large and Binary MIME Messages

POP3

  • RFC 1939 Post Office Protocol - Version 3
  • RFC 1734 POP3 AUTHentication command
  • RFC 2449 POP3 Extension Mechanism
  • RFC 2195 IMAP/POP AUTHorize Extension for Simple Challenge/Response

IMAP4

  • RFC 2060 Internet Message Access Protocol - Version 4rev1
  • RFC 1731 IMAP4 Authentication Mechanisms
  • RFC 2195 IMAP/POP AUTHorize Extension for Simple Challenge/Response

CLS Compliant

Hunny Mail.Net follows Microsoft's guidelines for creating reusable components for the .NET framework. All types in Mail.Net are compliant with the Common Language Specification (as well as the Common Type System). Therefore, you may use this class library from any CLS-compliant language, including C#, Visual Basic.NET, Managed C++, JScript.NET, J#, and more.

Reliable

Some of our customers run mission-critical messaging servers 24 hours per day, 7 days per week. Therefore, we take reliability very seriously. We follow established software development practices for bug-free software development: from version control to software testing to good coding practices. We respond to bug reports within 24 hours.

Thoroughly Documented

Good documentation is an important requirement for software re-use. The Hunny Mail.Net library includes an excellent reference manual, plus well-commented examples. The documentation is available in various formats, suitable for both printing and viewing in a browser. The reference manual is even available online at our web site.

Includes Helpful Examples

Most developers prefer to look at example code to get started quickly. Experienced developers can often achieve their programming goal in one or two days by starting with a relevant code example. Recognizing the importance of good code examples, we include numerous, helpful code examples in Hunny Mail.Net.

Some of the included examples show how to:

  • SMTP

    • Send a message to one or more recipients
  • POP3

    • Authenticate with the server using USER/PASS
    • Authenticate with the server using APOP
    • Download messages from a POP3 server
  • IMAP4

    • Get summaries of all the messages in a folder
    • Retrieve a complete message
    • Retrieve the text of a message, leaving the attachments on the server
    • Retrieve an attachment from a message
    • Get a list of all the available folders
    • Add messages to a folder
    • Move old messages to an archive folder

Source Code Available

Good documentation is important, but readable source code can provide a far more detailed understanding of a software product. With source code available, developers can truly understand how the library works, and thereby make better design decisions. For example, there may be more than one way to accomplish a certain program requirement. When the source code is available, developers can choose the alternative that provides the most efficient operation.

With source code, developers may also customize or adapt the library in ways that are not otherwise possible.

Support Contracts Available

We stand behind our products, offering to customers options for support contracts. Contact our sales team for more information.