MailBee IMAP4 Component

MailBee IMAP4 Component

Fast and flexible COM object that enables your application or ASP page to search, receive, parse and manage email over IMAP4 protocol
MailBee Objects bundle includes SMTP, POP3, IMAP, S/MIME components.
     
Current version: 8.2
Last update: 25 Nov 2013

Clients

Clients Say:

  • “Thanks, the product is really great ;)”

    Lennon Seno

Development Services

Engage our developers when you require services above and beyond product support, such as:

MailBee IMAP4 enables developers to easily add IMAP capabilities to their Windows or classic ASP applications. The component supports message search and checking new/read/unread status (all of the above - without downloading entire messages or even message headers). All the basic features are fully supported as well - preview messages, download, parse and manage messages and mailboxes (folders). The component can be used in any ActiveX-aware language such as classic ASP, VB, Delphi, C++, etc.

The component supports a number of IMAP extensions like IDLE (instant notifications about new events like arrival of a new e-mail) and XLIST (special folder flags like Drafts, Sent, Trash).

With SSL support available at no additional cost, you can download e-mail from S/IMAP servers, such as Gmail.

With the help of MailBee S/MIME Component, encrypted or signed e-mails can be decrypted and verified.

Supports all Windows versions from 2000 to 2012, 32/64 bit.

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


IMAP Object

  • Retrieves entire message, message header, message header and part of message body, message envelope and body structure
  • Searches messages that match specified criteria
  • Retrieves, selects and manages mailboxes
  • Copies and deletes messages on the IMAP4 server
  • Provides event notification mechanism and background processing
  • Supports logging IMAP4 session into the file
  • Executes user-supplied commands
  • Ping method for keeping connection alive
  • Automatically decodes received messages from MIME format
  • Automatically generates plain-text version for HTML-only messages
  • Supports secure authentication methods (NTLM, MSN, GSSAPI, including Integrated Windows Authentication)
  • Supports special folder flags (Drafts, Sent, etc) using XLIST extension developed by GMail and Apple
  • Supports UIDs
  • Supports IDLE and QUOTA extensions
  • Full support for Unicode, UTF8, and UTF-7M mailbox names. Supports international headers, attachment names, bodies, etc

IMAP4 Object reference...


What's new

Version 8.2
  • Windows 8/8.1 compatible installer.
  • Better handling of non-English characters in encoded headers.
  • Better handling of quoted strings in IMAP responses and MIME messages.
  • Misc. improvements in MIME parser.
  • Fixed disconnect-related issues.
  • When saving e-mail with embedded pictures, can now save them under original filenames plus suffixes to avoid overwriting when an e-mail has multiple images with the same filename.

Version 8.1
  • Support of Content-Location header when displaying e-mails with embedded images
  • Better MIME parsing

Version 8.0
  • Full Unicode support in all aspects
  • New charset-manipulation functions
  • Improved support of international filenames of attachments
  • Events and methods to track all the data traffic between the client and the server
  • Numerous S/MIME enhancements
  • New samples for Visual C++

MailMessage Object

  • 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...