Manage email messages and mailboxes on a mail server.
Reference
Control Information
| Object Name |
ImapClientCtl.ImapClient |
| File Name |
CSMAPX12.OCX |
| Version |
12.0.3024.1286 |
| ProgID |
SocketTools.ImapClient.12 |
| ClassID |
59BFA765-A116-40E8-9A27-BF1C9FB5DE3A |
| Threading Model |
Apartment |
| Help File |
CST12CTL.CHM |
| Dependencies |
None |
| Standards |
RFC 3501 |
Overview
The Internet Message Access Protocol (IMAP) is an application
protocol which is used to access a user's email messages which are
stored on a mail server. However, unlike the Post Office Protocol
(POP) where messages are downloaded and processed on the local
system, the messages on an IMAP server are retained on the server and
processed remotely. This is ideal for users who need access to a
centralized store of messages or have limited bandwidth. For example,
traveling salesmen who have notebook computers or mobile users on a
wireless network would be ideal candidates for using IMAP.
The SocketTools IMAP control implements the current standard for
this protocol, and provides functions to retrieve messages, or just
certain parts of a message, create and manage mailboxes, search for
specific messages based on certain criteria and so on. The interface
is designed as a superset of the Post Office Protocol interface, so
developers who are used to working with the POP3 control will find
the IMAP control very easy to integrate into an existing
application.
The control supports secure explicit and implicit connections using
TLS 1.2 or later with client certificates for authentication. By
simply setting a few properties, a secure connection using 256-bit AES
encryption can be established, providing your application with the
highest level of security available.
Authentication is supported using both standard passwords and
OAuth bearer tokens.
Requirements
The SocketTools ActiveX Edition components are self-registering
controls that are compatible with any programming language that
supports the Component Object Model (COM) and the ActiveX control
specification. If you are using Visual Basic 6.0, Service Pack 6 (SP6)
is required. We recommend installing all available updates for your
development tools. Although the Visual Basic 6.0 runtime is supported
on Windows 11, the IDE itself is no longer officially supported by
Microsoft. Legacy IDEs and compilers may also require elevated
(administrator) privileges to run properly.
The ActiveX controls are supported on Windows 7, Windows Server
2008 R2, and later versions of both desktop and server editions of
Windows. For Windows 7, Service Pack 1 (SP1) is the minimum
requirement. For Windows 8 systems, the 8.1 update must be installed.
On ARM-based platforms, the minimum supported version is Windows 10
build 1709.
SocketTools includes components for both 32-bit (x86) and 64-bit
(x64) Windows platforms. All modern versions of Windows are 64-bit,
but we continue to include 32-bit components for compatibility with
legacy development tools such as Visual Basic 6.0. We also provide
native ARM64 ActiveX controls for systems running Windows on ARM. Note
that 32-bit applications on ARM run using x86 emulation, and Microsoft
no longer supports native ARM32 applications.
If you are using VBScript, Visual Basic for Applications (VBA), or
another scripting environment on an ARM-based system, be aware that
64-bit hosts will require ARM64 components, while 32-bit hosts will
use x86 components under emulation. This includes applications created
with Visual Basic 6.0. To reduce deployment complexity and avoid
confusion, SocketTools does not include ARM32 ActiveX controls in its
standard redistribution packages but they are available on request for
legacy or specialized scenarios.
Distribution
When you distribute an application that uses this control, you can
either install the file in the same folder as your application
executable or as a shared component in the appropriate system folder.
If you install the control in the system folder, it is important that
you distribute the correct version for the target platform and it
must be registered. If you install the control in the same folder as
your executable, it is recommended that you use registration-free
activation or COM redirection to ensure that the correct version of
the control is loaded by the application.
|