The latest production version of MailBee Objects is available at:
http://www.afterlogic.com/download/MailBee.exe
The latest beta version of 32-bit MailBee.dll is available at:
http://www.afterlogic.com/updates/mailbee.zip
The latest beta version of 64-bit MailBee64.dll is available at:
http://www.afterlogic.com/updates/mailbee64.zip
To reinstall MailBee Objects or install a new version, it's required to uninstall the existing version first.
Prior to uninstalling make sure no applications use MailBee Objects. For example, Internet Information Server (IIS) caches recently used components, so you need to stop or restart the server BEFORE uninstalling MailBee Objects (execute
"iisreset" command in
Start/Run menu).
Also, ActiveX-aware development environments (such as Developer Studio) might lock MailBee Objects if you develop an application or ASP page which uses MailBee Objects. You need to close your development environment before uninstalling.
The easiest way to make sure MailBee Objects DLL is not locked by some other application is to reboot the machine where MailBee Objects is installed. Of course, after rebooting you must launch MailBee uninstaller before using IIS or Developer Studio (otherwise, MailBee Objects might be locked again).
As soon as MailBee Objects is not locked anymore, you can uninstall it and install the new version.
Most likely, your application powered by MailBee Objects doesn't have sufficient permissions to
MailBee.dll or MailBee Objects installation was damaged for some reason. If your application is an ASP application, please refer to the following topics to learn how to resolve this problem:
For ASP.NET application powered by MailBee Objects:
If you're sure all permissions set correctly, MailBee Objects installation was damaged for some reason. Stop or exit all applications which can potentially use MailBee Objects (such as IIS or Developer Studio), uninstall MailBee Objects and install it again.
Yes, but you should ask your hosting provider to register it on the server. Similarly to any other ActiveX, it can be registered via standard system
regsvr32 utility. Example:
regsvr32 "C:\Program Files\MailBee\MailBee.dll"
For .NET environment, we recommend to use
MailBee.NET Objects instead of MailBee Objects. To learn how to add MailBee.NET Objects into your VB.NET project, please refer to
"How to add MailBee.NET Objects in my .NET-based project?" topic.
However, if you need to add MailBee Objects into your VB.NET project for some reason, you should go to
"Project" menu, then
"Add reference", select
"COM" tab and then search for
"MailBee Objects type library" in the list.
Note that MailBee is not a visual control, you cannot place it on the form; instead, you should create instances of MailBee classes programmatically in the code.
You should set
POP3.CodepageMode=1 prior to retrieving messages. This will activate an alternate method of charset conversions.
Dim Mailer, Msg
'Using visual basic to create object
Set Mailer = CreateObject("MailBee.POP3")
'Using ASP to create object
'Set Mailer = Server.CreateObject("MailBee.POP3")
'In ASP use Response.Write instead of MsgBox
Mailer.LicenseKey = "put your license key here"
Mailer.Connect "mailserver.com", 110, "MyName", "MyPassword"
If Mailer.Connected Then
If Mailer.MessageCount > 0 Then
' Now MailBee will convert the body
' into Windows version of the message's codepage
' instead of converting into current system's Windows codepage.
Mailer.CodepageMode = 1
Set Msg = Mailer.RetrieveSingleMessage(1)
If Not Msg Is Nothing Then
MsgBox Msg.BodyText
End If
End If
Mailer.Disconnect
End If
When
POP3.CodepageMode=0, MailBee Objects converts messages from their original codepages to default server codepage and this may cause non-latin characters loss.
POP3.CodepageMode=1 forces MailBee Objects to convert messages from their original codepages to their Windows counterparts.