MailBee POP3 Component

MailBee POP3 Component

Enables your application or ASP web page to reliably and securely receive Internet mails via POP3 protocol
MailBee Objects bundle includes SMTP, POP3, IMAP, S/MIME components.
     
ãƒãƒ¼ã‚¸ãƒ§ãƒ³: 7.0.1
最終更新日: 28 Dec 2011

Clients

Clients Say:

  • “Hey, I just wanted to let you know that the component is working great. Thanks much.”

    Michael C. Gates

Development Services

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

MailBee POP3 allows you to easily download and parse e-mail from POP3 servers in classic ASP, VB, Delphi or any other ActiveX-aware environment. The component supports secure authentication on a POP3 server (including NTLM and GSSAPI used by MS Exchange 2007/2010), full and partial download of messages (downloading headers), deleting messages, parsing and decoding messages into easy-to-use Message objects.

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

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

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

MailBee POP3 returns downloaded messages as Message objects. Nothing gets saved to disk unless the developer explicitly needs this.

Message class is a standard e-mail message container in MailBee. For instance, you can get a message from POP3 object and then re-send it with SMTP object.


POP3 Object

  • Supports secure authentication methods (APOP, NTLM, GSSAPI, including Integrated Windows Authentication)
  • Can retrieve all messages as a collection, retrieve only headers for each message, headers + part of message body
  • Can retrieve any single particular message or (its headers)
  • Can detect total message count in the mailbox, total size of all messages and sizes of every message. All of above does not require to retrieve messages or headers
  • Automatically parses retrieved messages and headers (decoding from base64/quoted-printable/uue, converting charset to windows code page, etc.)
  • Automatically creates plain-text version of HTML formatted message if plain version is not available in the message itself
  • Can determine whether a message contains attachments when downloading message headers only
  • Can delete messages from POP3 server
  • Supports logging POP3 session into the file
  • Can execute user-specified commands (SendCommand method)
  • Ping method allows to implement "keep connection alive" function in your applications
  • Supports event mechanism to track retrieval progress (and abort retrieval if needed)

POP3 Object reference...


最新

Version 7.0
  • IPv6 support
  • Support of multiple HTML bodies in the message (such as e-mails created by Apple Mail)
  • Load e-mail from memory

Version 6.0
  • GSSAPI/NTLM and GSSAPI/Kerberos authentication
  • plain NTLM authentication rewritten with SSPI, now works with MS Exchange 2007/2010
  • Integrated Windows Authentication (authenticate using the current Windows user credentials)
  • SSL support now built-in and easier to use, no separate license required

Version 5.8.5
  • SaveKey utility (saves MailBee license key in the registry) is now also available for Windows Vista/2008/Seven (32-bit and 64-bit).

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