The WeOnlyDo! COM ImapServer ActiveX control allows for seamless integration of IMAP4rev1 protocol server implementation into applications.

Although the wodImapServer is a COM object and not the full application, developers should be aware of a few things. This is because COM objects cannot deal with information that should be preserved between sessions. The most important thing to look after is to keep the UID information (UNIQUE ID) for folders and messages. By doing so, wodImapServer will work flawlessly with any client that connects to it.
On each client action, the wodImapServer will fire an appropriate event where you can internally handle the action and return a positive or negative result. You should also deal with message flags, as wodImapServer does not deal with message storage. You should do this by yourself.
The wodImapServer will deal with structures and references to folders and messages, but the actual contents of messages cannot be handled by wodImapServer. Rather, it will depend on your code when messages are accessed - hoping that you provided properly formatted messages and proper flag information. If you don't, it will not complain, but IMAP clients may.
It's important to consider all wodImapServer folders as virtual folders - none of them necessarily exist on your system. Each time the wodImapServer requires a list of folders or messages, an event is fired to notify you to populate its collections with the appropriate information - that's all. You can keep messages in a database or on an external system, or wherever you need - as long as you can provide the necessary information on wodImapServer's request.
Version 2.4.6:
2.4.6 January 15, 2018
Updated OpenSSL to 1.0.2n
Version 2.4.5:
2.4.3 March 20, 2013
* Memory leak fix
Version 2.4.3:
2.4.3 March 20, 2013
* Memory leak fix
Version 2.4.1:
2.4.1 March 6, 2011
* Improved message handling
2.4.0 January 15, 2011
* IPv6 support
Version 2.3.2:
2.3.2 April 15, 2010
* Fix in BODYSTRUCTURE response that caused problem with IPhone devices
Version 2.3.1:
2.3.1 January 25, 2010
* Distribution now contains x86 and x64 binaries
Version 2.1.3:
2.1.3 February 3, 2009
* Fix in IDLE command being announced in CAPABILITY, even not used
* Updated OpenSSL to latest version
Version 2.1.0:
2.1.0 February 10, 2007
* Switched to OpenSSL 0.9.7 which is FIPS140-2 certificated. See certificate #733 at
http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401val2007.htm
Version 2.1.0.0:
2.0.3 June 12, 2006
* Fix in ENVELOPE command that didn't properly encode subject
Version 2.0.3.0: N/A