MailMessage ActiveX Control  
 

Compose and parse MIME-formatted email messages and newsgroup articles. The control supports plain text and HTML content, attachments, custom headers, and international character sets, along with local storage for collections of messages.

Reference

Control Information

Object Name MailMessageCtl.MailMessage
File Name CSMSGX12.OCX
Version 12.0.3041.1380
ProgID SocketTools.MailMessage.12
ClassID 65A25CF7-655D-4223-869A-3CDBBC4FE934
Threading Model Apartment
Help File CST12CTL.CHM
Dependencies None
Standards RFC 822, RFC 2045, RFC 2046, RFC 2047, RFC 2048

Overview

The MailMessage ActiveX control provides methods for composing, parsing, and modifying email messages and newsgroup articles structured according to the Multipurpose Internet Mail Extensions (MIME) standard. High-level methods simplify common message creation tasks, while the properties for individual headers and message parts give applications control over more complex content. Messages can be imported from or exported to files, strings, and the clipboard.

Applications can create multipart messages containing alternative plain text and HTML bodies, file attachments, and inline images. Attachments can be added from files or memory buffers, enumerated or located within an existing message, and extracted individually or together. Message part properties expose content types, lengths, text, and attachment names so applications can inspect and process each part as needed.

Header and address methods allow applications to enumerate, retrieve, create, update, or delete header fields and parse sender and recipient information. The control can process Base64 and quoted-printable text encoding, and character set conversion. This helps applications work with international message content without constructing or decoding the underlying MIME representation manually. Applications can also inspect the authentication results for a message, including the reported status of SPF, DKIM, and DMARC checks.

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 distributing an application which uses this control, you can either install the OCX file as a shared component in the appropriate system folder or in the same folder as your application executable. If the control is installed in a shared system location, the installer should manage it as a shared component to prevent other applications from being affected when it is updated or removed. 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.

This control has no external runtime dependencies beyond the standard Windows system libraries. It does not require the Microsoft Visual C++ Redistributable or any additional third-party libraries to be installed. All required components are either provided by Windows or statically linked into the ActiveX control, simplifying deployment and eliminating the need to distribute additional runtime files.