wodImapServer

Many large organizations maintain their own internal email servers which allow each and every user to have a mailbox with their unique ID and perform mail exchange with other servers. It is necessary that all the protocols must be activated on such a server to ensure seamless email exchange. One such protocol is IMAP which allows users to access messages on bulletin board and emails from a shared server. In other words, this protocol allows client program to access emails from a remote server as if they are stored locally. If you are the administrator of such a mail server which is in the process of setup or re-configuration, and need a quick solution for implementation of IMAP, then you can use wodImapServer v.2.3.2 which is a powerful component and is quite affordable if compared in the light of other similar developer components.

wodImapServer v.2.3.2 is an ActiveX control which can be directly put on a VB form for complete implementation of the IMAP4 rev1 protocol on a mail server. After you have put this component on a VB form, you just have to call the start method of this component and it will automatically start accepting incoming connections and sharing requests from the client systems. This is just a COM object and not a complete component so it is obvious that it would require some server administrator intervention in a few respects. You will have to ensure a mechanism for dealing with the preservation of information in-between the sessions and most importantly, keep the Unique Identification information of messages and their respective folders. Message flags are not supported as this is a COM object and thus, you need to deal with it on your own.

wodImapServer v.2.3.2 gets an average rating of three points on the scale of five as it requires some additional development to become a full application, but as such, it is perfect in the way it is meant for, being merely an optimally priced COM object.

WeOnlyDo! COM ImapServer ActiveX control is component that can be easily integrated into your applications to provide full IMAP4rev1 protocol server implementation. 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.