WeOnlyDo! Imap Server Component

張貼者:2010年8月10日 上午1:38未知的使用者   [ eddie liu 已於 2012年8月9日 上午2:00 更新 ]
WeOnlyDo! Imap Server Component 是一個ActiveX控件,能容易將他集成到你的程序中,並提供充分的IMAP4rev1 協議服務器支持。所有您需要做的,只是通過VB程序調用它的方法並使它立刻接受您要連接的客戶! 







--------------------------------------------
開發商:WeOnlyDo! Software Inc
原廠網址:http://www.weonlydo.com/ImapServer/imap-server-component.asp
更新日期:2011/05/18
採購正式版、大量授權報價、技術支援、軟體諮詢、委託採購、詢問報價請來電 02-29299388 分機16 , 
來信service@orderble.com,或點我
------------------------------------------------------------------------------


一般資料

WeOnlyDo! ActiveX控件的COM ImapServer是組件,可以很容易地集成到應用程序中提供充分的IMAP4rev1協議的服務器實現。 所有您需要做的是把它放在VB的形式,調用它的 啟動 方法和它的立即接受連接你的客戶! 它完全支持命令定義在 RFC2060

關於 IMAP協議

IMAP代表 Internet郵件訪問協議。 它是一種方法的訪問電子郵件或電子公告板郵件存放在一個(可能共享)的郵件服務器。 換句話說,它允許一個“客戶”的電子郵件程序來訪問遠程郵件存儲好像他們是本地的。

IMAP的能力,獲取信息(包括新的和保存)由多台計算機已經變得非常重要,因為依賴於電子信息和使用多台計算機的增加,但此功能不能被視為理所當然:廣泛使用郵局協議(POP)當一個最好的作品只有一台計算機,因為它被設計為支持“離線”郵件訪問,其中的郵件下載下來,然後刪除了郵件服務器。 這種模式不兼容的訪問是由多台計算機的訪問,因為它往往灑在所有郵件的計算機所使用的郵件訪問。 因此,除非所有的這些機器都有一個共同的文件系統,脫機模式設計了POP訪問,以支持有效的聯繫用戶一台計算機的信息存儲和操作。 (摘自 http://www.imap.org/)。

POP3和IMAP4的區別

差異眾所周知的POP3和IMAP4協議是支持的IMAP訪問多個文件夾 - 而只知道的POP3收件箱(一個文件夾的郵件)。 而不是使用您的本地系統創建的文件夾和移動接收的消息對他們為地方檔案,IMAP4允許你這樣做 - 但仍保持在遠程信息系統。 這樣你可以從任何地方訪問你的郵件,使用任何客戶端,支持IMAP4(甚至基於 Web的電子郵件),仍然有機會獲得 *所有*電子郵件。
向後兼容的POP3仍然存在 - 幾乎每一個 IMAP4服務器有一個文件夾,名為'收件箱',這是相同的文件夾(僅文件夾!),您訪問當您使用POP3協議。 請記住,'文件夾'是一樣的郵箱',因為所有的UNIX保持在一個文件中的電子郵件,而我們計劃繼續在我們的樣本郵件作為單獨的文件,但想法是相同的。
收件箱文件夾是在這個過程中非常重要的。 正因為如此,收件箱對象應始終存在在你的代碼,因為大部分客戶都會先訪問它! 你甚至可以添加此文件夾時自動用戶登錄,只是為了確保客戶端沒有收到一個錯誤。

WeOnlyDo! IMAP服務器的執行情況

wodImapServer是IMAP4rev1執行所定義的 RFC2060

由於 wodImapServer是COM對象,而不是完整的應用程序,還有一些事情要照顧開發商 - 簡單,因為 COM對象不能處理的信息應予以保留之間的會議。 最重要的是要保持信息的UID(唯一ID)的文件夾和郵件。 如果你這樣做 - wodImapServer將完美與任何客戶端連接到它。 在每個客戶的行動將觸發相應的事件wodImapServer在那裡你可以在內部處理的行動,並歸還積極或消極的結果。 你也應該處理的信息標誌。

wodImapServer並不處理消息存儲 - 你應該這樣做的自己。 它將處理結構和參考文件夾和郵件 - 但實際內容的郵件不能被處理 wodImapServer。 相反,它取決於你的代碼時,郵件訪問,希望你提供格式正確的信息,並適當標誌信息。 如果你沒有 - 也不會抱怨,但IMAP客戶端可能會 ...

你應該考慮所有wodImapServer文件夾作為虛擬文件夾 - 沒有他們並不一定存在於您的系統。 每次wodImapServer需要列表的文件夾,或列表的郵件 - 事件觸發通知你來填充他的收藏品適當的信息 - 這一切。 你可以在數據庫中保存的信息,對外部系統,或者你需要的地方 - 只要你能提供必要的資料,wodImapServer的要求。






General information

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.

About IMAP protocol

IMAP stands for Internet Message Access Protocol. It is a method of accessing electronic mail or bulletin board messages that are kept on a (possibly shared) mail server. In other words, it permits a "client" email program to access remote message stores as if they were local.

IMAP's ability to access messages (both new and saved) from more than one computer has become extremely important as reliance on electronic messaging and use of multiple computers increase, but this functionality cannot be taken for granted: the widely used Post Office Protocol (POP) works best when one has only a single computer, since it was designed to support "offline" message access, wherein messages are downloaded and then deleted from the mail server. This mode of access is not compatible with access from multiple computers since it tends to sprinkle messages across all of the computers used for mail access. Thus, unless all of those machines share a common file system, the offline mode of access that POP was designed to support effectively ties the user to one computer for message storage and manipulation. (taken from http://www.imap.org/).

Difference between POP3 and IMAP4

Difference between well known POP3 protocol and IMAP4 is that IMAP supports access to multiple folders - while POP3 knew only INBOX (one folder with messages). Instead of using your local system to create folders and move received messages to them for local archival, IMAP4 allows you to do the same - but still for messages to remain on remote system. This way you can access your messages from anywhere, using any client that supports IMAP4 (even web based emails) and still have access to *ALL* emails.
Backward compatibility to POP3 still exists - almost every IMAP4 server have one folder called 'INBOX', and this is the same folder (and only folder!) that you access when you use POP3 protocol. Keep in mind that 'folder' is same as 'mailbox' since UNIX keeps all emails in one file, while we plan to keep emails in our samples as separate files, but idea is the same.
INBOX folder is very important in this process. Because of this, INBOX object should always exist in your code because most clients will first try to access it! You might even add this folder automatically when user logs in, just to make sure client doesn't receive an error.


WeOnlyDo! Implementation of IMAP server

wodImapServer is IMAP4rev1 implementation as defined by 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.