Email Components, WebMail, Smtp, Pop3, Imap, SSL, SMIME for .Net, ASP, VB.NET, C#, VB

MailBee SMTP Component
Try It!
Download Free Trial

MailBee SMTP Component

Allows your applications or ASP web pages to create and send email messages over SMTP protocol just in a few lines of code

What's new in 5.5

  • Can queue e-mails to IIS SMTP service
  • DNX MX lookup improvements (SMTP.GetRelayServerFromEmailAddress)
  • Ability to create non-standard text body parts (such as calendar items)

Overview

MailBee SMTP is an easy to use component for creating and sending email messages over SMTP protocol. It supports creating both plain-text and HTML-formatted messages with attachments and inline objects (including automatic alternative body creation, automatic scanning and adding attachments for specified HTML source and more). SMTP authentication (both plain and secure) is also supported.

Like all other MailBee components, MailBee SMTP can be extended with MailBee SSL/SMIME plugin. This will enable full support of SSL/TLS connections (for instance, you can send to GMail) and S/MIME.

MailBee SMTP object can be extended with external MailBee Message Queue system to enable message queuing which can noticeably improve performance of email sending applications or web pages. If your mail server is IIS SMTP, you can submit messages directly into its queue for even better performance.

No knowledge of SMTP, SSL, MIME and S/MIME is required.

MailBee SMTP can send messages previously downloaded using POP3 or IMAP4 components or any other MIME-compliant messages. Nothing gets saved to disk until the developer explicitly requests it.
 

SMTP Object Features

  • Can send any Message object to SMTP server
  • Can send messages to IIS SMTP queue or MailBee Message Queue (MMQ) system instead of direct sending to SMTP server. Queuing allows SMTP component to operate very quickly because messages are actually delivered in a background ("fire and forget" delivery)
  • Supports ESMTP authentication, including secure authentication methods (CRAM-MD5, NTLM, MSN) during connection to SMTP server
  • Can relay (blind-forward) messages stored in disk files (RelayMessage method)
  • Supports creating plain-text and HTML messages. For HTML messages, HTML Import option is available (it allows you to export HTML files with embedded graphics, style-sheets, etc with a single line of code)
  • Supports non-standard text body parts such as calendar items
  • Provides method to add custom MIME-headers (AddHeader method)
  • Supports unlimited number of attachments
  • Supports international headers, attachment names, bodies, etc.
  • Can preserve original formatting of plain-text keeping long lines unwrapped but still providing compatibility with MIME rules (BodyEncoding property)
  • Includes method MakeAltBody to create plain-text version of HTML body if plain-text version is not available
  • Supports logging SMTP session into a file
  • Supports event mechanism to track send progress (and abort sending if needed)
Smtp Object reference...

Message Object Features

  • Available in all MailBee Objects packages (POP3, SMTP, Objects). Used as a main unit POP3 retrieval and SMTP sending methods operate with
  • Because SMTP object composes messages using Message object, all composing functionality of SMTP object also applies to Message object
  • Includes collection of a message's attachments
  • Provides access to custom message headers through GetHeader method
  • Can be created explicitly through CreateObject and then saved to disk or sent by SMTP object
  • Any content can be loaded to RawBody property (such as content of message file or attachment with message inside)
  • RawBody operates symmetrically: when you set Message properties or call Message-affecting methods (such as AddAttachment), RawBody will reflect this changes next time you read it; when you load RawBody with new value, other Message properties such as BodyText are refreshed
  • No redundant refreshes on RawBody. If you sequentially change some Message properties, RawBody will be updated only when you read it, not after every changing Message properties
Message Object reference...