-
-
General
wodPop3Server component has two versions (both included in
the package):
wodPop3ServerCom is a COM object (wodPop3Srv.dll), designed
to be initialized dynamically from your code, and declared
from within your code. It does not have user interface, it
is windowless. Usually, you will initialize it with
- Dim WithEvents Pop3 as
wodPop3ServerCom
and wodPop3Server as ActiveX control (wodPop3Srv.ocx) -
designed to be put on application's form using
drag&drop from control toolbox. Once you put it on the
form, no special code is required to initialize it, since
your environment (usually VB) will handle it.
COM object licensing is not directly supported by any
container. Unlike ActiveX controls which are licensed the
moment you put them on the form (if you have licensed
version of wodPop3Server, of course), you need one more
line to put in your code to license wodPop3Server
correctly:
-
- Pop3.LicenseKey =
"put.your.key.here"
-
Filename |
wodPop3Srv.DLL
(wodPop3Srv64.DLL for x64) |
Class
name |
WeOnlyDo.wodPop3ServerCom.1 |
Class ID |
{0F48B57D-0BB7-422A-B99C-D8214A609279} |
Events class
ID |
{0x3ED48136,0x1B93,0x4AB4,{0xA0,0x71,0x0E,0x5E,0xD8,0x45,0xA1,0x0E}} |
Compatibility |
VB 5.0 and above, VFP
5.0 and above |
Built
with |
Microsoft Visual Studio 2008
C++, OpenSSL |
Required
DLLs |
None required. |
-
Filename |
wodPop3Srv.OCX
(wodPop3Srv64.OCX) |
Class
name |
WeOnlyDo.wodPop3Server.1 |
Class ID |
{3E7087CA-4626-44AB-8D76-6D06E3D6C83C} |
Events class
ID |
{0x845E43BE,0xD543,0x4501,{0xA4,0xC5,0x45,0x31,0x65,0xEB,0xDB,0xE1}} |
Compatibility |
VB 5.0 and above, VFP
5.0 and above |
Built
with |
Microsoft Visual Studio 2008
C++, OpenSSL |
Required
DLLs |
None required. |
-
IPop3Message |
{2ACFF928-8423-45AF-B3DB-3ABE02309A86} |
IPop3Messages |
{AF2286BE-E89E-486F-A4D7-6B92F08DF523} |
IPop3User |
{5F1D2792-8DB1-4B4F-809B-B58170EE2449} |
IPop3Users |
{5F1D2792-8DB1-4B4F-809B-B58170EE2449} |
IwodPop3Notify |
{63E4482A-1C36-4417-8D1C-F5B3D3344E76} |
-
Help
filename |
wodPop3Srv.CHM |
Distribution note
When you develop and distribute an application that uses
this component:
1. Choose between COM object (wodPop3Srv.DLL/wodPop3Srv64.DLL) and the
ActiveX control (wodPop3Srv.OCX/wodPop3Srv64.OCX) to include into the
installation package. Both versions are independent on each
other.
2. You should include wodCertificate.DLL/wodCertificate64.DLL for
Certificate management - if it is needed in your application.
wodSmtpServer does not depend on it - only uses it for client
authentication with the certificate or private key.
3. Above binaries can be included royalty-free in your
application.
4. Use RegSvr32.EXE (or any other installer package
creator) to register both the OCX and the DLL. Usually,
installer software will do this for you
5. Install the component file(s) into the user's
Windows SYSTEM32 folder. The component file(s) has/have
version information built into it. So, during installation,
you should ensure that you are not overwriting a newer
version.
Using licensed version
To use retail (licensed) version in your code, put your
license key into LicenseKey property, imediately after
initializing the component. For ActiveX control, you cannot
do this (there is no LicenseKey property) because your
license key will be read internaly by wodPop3Server.
|