Each license includes one year of free updates, and unlimited lifetime
technical support. Remember that each developer must have his own
design-time license.
General information
WeOnlyDo! COM Pop3Server ActiveX control
is a component that can be easily integrated into your applications to
provide full Pop3 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 RFC1939.
Usage model
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.
You should take care of messages - wodPop3Server does the rest
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!
Pop3Server 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.
Additional notes
NOTE: In DEMO version you cannot change
GreetingMessage property, and cannot Deny user in Connected event.