wodPop3Server will deal with clients and connections – you must deal with messages. Once new user logs on to your POP3 server, you need to provide any kind of information about his mail. This is really easy task. If you keep all the emails in separate files, that’s just great for usage with wodPop3Server. If you prefer to keep it in one large file – we will not argue about it. You can specify filename, starting and ending position for each email in mailbox, and WeOnlyDo! wodPop3Server will pass it to remote client with ease. However, you might have some small problems maintaining such mailbox since sometimes it needs to delete messages, change status, etc.. But don’t worry – it all can be done after user logs off.
Use your favorite mail client (such as Outlook Express or Eudora) to read mail provided by your own application. How? That’s easy part: just put wodPop3Server control on your form, add some code around and it’s all setup to be used.
If you dislike adding additional code – it’s fine by wodPop3Server. It will still work, and reject all the clients (with bad username/password error). But, if you add login capabilities using ‘Connected’ event (that’s easy part – set Action = Allow for specific username/password combination). Still, if you want to make real POP3 server application, look no more for native support for socket related material – you just found it.
- Server side ActiveX for POP3 protocol
- No need for you to know POP3 specifications
- Set of events for all major client operations
- Easy to use and fast
- You take care of message storage, wodPop3Server takes care of hard work
- Installation contains x86 and x64 binaries
- Samples in VB, VC, Delphi
New in this version:
- Distribution now contains x86 and x64 binaries
- Binaries are from now on recompiled in VS 2008