WeOnlyDo! COM ImapServer ActiveX control is component that can be easily integrated into your applications to provide full IMAP4rev1 protocol server implementation.
Version: 2.4.6WeOnlyDo! COM ImapServer ActiveX control is component that can be easily integrated into your applications to provide full IMAP4rev1 protocol server implementation.
License: Free To Try $169.00
Operating System: Windows
All you need to do is to put it on VB form, call it's Start method and it's immediately accepting connections by your clients! It fully supports commands defined in RFC2060.
Since wodImapServer is COM object and not the full application, there's few things developer should look after - simply because COM objects cannot deal with information that should be preserved between the sessions. Most important is to keep UID information (UNIQUE ID) for folders and messages. If you do so - wodImapServer will work flawlessly with any client that connects to it.
On each client action wodImapServer will fire appropriate event where you can internally handle the action and return positive or negative result. You should also deal with message flags.wodImapServer does not deal with message storage - you should do it by yourself.
It will deal with structures and references to folders and messages - but 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...
You should consider all wodImapServer folder as virtual folders - none of them doesn't necessarily exist on your system.
Each time wodImapServer requires list of folders, or list of messages - event is fired to notify you to populate his collections with appropriate information - and that's all. You can keep messages in database, on external system, or wherever you need - as long as you can provide 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.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 220.127.116.11: 2.0.3 June 12, 2006 * Fix in ENVELOPE command that didn't properly encode subject