Component is licensed on per-developer basis. You have to obtain a valid license for each human who writes the code which directly uses the component.

Back to the top...

# Do we have to pay for each copy of our software we ship that includes your component?

No. The component is licensed per-developer, not per user. Once you have purchased a license for each of your developers, you can redistribute the component DLLs with your application royalty free and to any number of end users and to any number of computers.

Back to the top...

# Is your product royalty free?

Yes.

Back to the top...

# Do I need to a special license for automated buildserver?

No. Only developers need a license.

Back to the top...

# What is support contract good for?

Support contract includes:

Every new version of the licensed component both major and minor.
Every new component released (if you have a Rebex Total Pack license).
Email questions answered within one business day.
Phone support upon request.

Support contract for the first year is included in every license of the Rebex component.

Back to the top...

# Can I use my component when the support contract expires?

Yes! (of course).

The license is perpetual. See page about Support Contracts for details.

Back to the top...

Purchase

# How can I order the product?

Different payment possibilities are described in How to order document.

If there is not suitable option for you, please contact us.

Back to the top...

Install And Setup

# How do I install and use component?

Install the package into a folder of your choice and inspect the contents.

The bin folder contains both debug and release builds of the assembly and can be either used as an application-private assembly and deployed within the directory structure of your application, or installed into GAC as a shared assembly, which can be used by multiple applications on the machine. To use the component from your project in Visual Studio, just add a reference to it!

The manual is in docs folder and code samples are in samples folder.

Back to the top...

# How do I upgrade to a new version without having to recompile all the code?

Check out this upgrading HOWTO for more information.

Back to the top...

# How do I install the component into Global Assembly Cache (GAC)?

There are two ways:

Start .NET Framework Configuration Management Console (Start -> Settings -> Control Panel -> Administrative Tools -> Microsoft .NET Framework Configuration).

Then select "Assembly Cache" and click "Add an Assembly to the Assembly Cache" to add Rebex.Net.*.dll into GAC.
Use the gacutil command line utility. It can be usually found in Microsoft.NET\Framework\v1.*.* subfolder of the Windows folder or inside the .NET Framework SDK tree.

See the .NET Framework SDK documentation for a full description of the options supported by gacutil.

Back to the top...

Trial Version

# How do I register the trial version?

When you buy Rebex Mail, you will receive an email with your login and password to a protected section of our website, where you can download the full version of the component.

Back to the top... | More info...

# How do I upgrade from trial version to full version when I already bought the component?

First of all, you need to download the full version of your component. You can download the latest releases from the protected section of our website.

Steps to upgrade your component in your project:

Remove the reference to the trial version dlls in your project.
Replace trial version dlls with the full version dlls.
Add reference to the new dll files to your project.
Recompile your project.

Back to the top...

# How do I determine whether my DLL is a trial or full version?

To check which version your are actually using try to locate Rebex.*.dll on your disk (typically somewhere under C:\Program Files\Rebex\ or in your project folder), lookup it’s properties and check the "Version" tab (or "Details" in Windows Vista).

If the DLL is a trial version, you'll find "Trial Version" at the end of the "Description:" (or "File description" in Windows Vista) string. If the "trial version" text is missing, it's a full version DLL.

Back to the top...

Support

# What do I need to do to get upgrades or bug fixes?

If you have bought component, you can download the latest releases from the protected section of our website. You will also receive an email when a new version is released.

When you report a bug, it gets fixed as soon as we are able to identify and correct it. After the new version is tested, it appears in the protected section and a new trial version gets released as well.

Back to the top...

# What kind of support do you offer?

Email (support@rebex.net) and online forum (forum.rebex.net support is available to everyone.

Registered users with active support contract can also use a phone support (contact).

Back to the top...

Platforms

# Does it work with the .NET Compact Framework?

Yes, the .NET Compact Framework version is available for .NET CF 2.0 and higher.

Back to the top...

Mail protocol questions

# Does it work with Microsoft Exchange?

Yes, it does. If the appropriate protocols are enabled, you can access Exchange mailboxes using IMAP or POP3 and send mail using SMTP. For more information about the known pitfalls of different Microsoft Exchange versions, check out the questions and ansers below.

Back to the top...

# How do I authenticate to Microsoft Exchange 2007?

By default, Microsoft Exchange does not support plain text authentication methods for security reasons. This leaves us with the following options:

A. Authenticate over a connection protected using TLS/SSL

You need Rebex Secure Mail to be able to use TLS/SSL.

B. Use NTLM authentication

To utilize NTLM authentication, call the Smtp, Imap or Pop3 object's Login method with an optional argument which specifies that NTLM is to be used. Unlike plaintext authentication, NTLM is allowed over an unencrypted channel by default.

C. Enable unencrypted plain text authentication

If none of the two options above is suitable for you, the only solution is to enable plain text authentication for non-TLS/SSL connections using Exchange Management Console.

Back to the top...

# How do I authenticate to Microsoft Exchange 2000 or 2003?

When connecting to Microsoft Exchange 2000 or 2003 server using IMAP or POP3 protocols, you should be aware of the issues caused by mismatched logon name and alias name. The logon name identifies the user, the alias name identifies the mailbox.

A. Authenticating using a method other than NTLM

When authenticating using a method other than NTLM to an account whose alias name does not match the logon name, the username of the following form must be used to log in:

domain/logon/alias

Example:

rebex/johns/john.smith

B. Authenticating using NTLM

To utilize NTLM authentication, call the Smtp, Imap or Pop3 object's Login method with an optional argument which specifies that NTLM is to be used. When authenticating to Microsoft Exchange 2000/2003 server using NTLM, it is not possible to specify an alias name, because NTLM does not support this. Therefore, it is not possible to authenticate to accounts whose alias name does not match the logon name. This is a limitation of Exchange 2000/2003, and even Microsoft Outlook Express cannot authenticated in this case. An alias name must be changed to match the logon name to make NTLM authentication possible.

To change the user's alias name:

1) Start 'Active Directory Users and Computers' management console.

2) Open the 'Properties' of the user whose mailbox you want to access using IMAP/POP3 with NTLM authentication.

3) Determine the user's logon name from the 'User logon name' field in the 'Account' tab.

4) Select the 'Exchange General' tab and make sure the 'Alias' field is set to the same value as the 'User logon name' from the previous step.

Please note that alias name has nothing to do with the user's e-mail addresses, so changing the alias is unlikely to break anything - unless some other applications depend on the former alias name.

Back to the top...

# Does TLS/SSL work with Microsoft Exchange?

You need Rebex Secure Mail to be able to use TLS/SSL. It works with Microsoft Exchange.

Back to the top...

Samples

# Do you have any examples on .......?

See the list of our free samples!

If what you need is missing, please let us know. We are constantly improving the existing samples and writing new ones.

Back to the top...