FAQ
0. Purchase And Licenses
1. Install And Setup
2. Trial Version
3. Support
5. Platforms
6. Samples
7. Exceptions
0. Purchase And Licenses
# 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 who directly
works with the component, you can redistribute the component DLLs
with your application royalty free and to any number of end users.
Back to the top...
# Is your product royalty free?
Yes. You can ship the component DLLs with your product
to any number of end users with no additional costs and
with no need of additional licenses.
Back to the top...
# Do I need to contact you to get a license key for each developer or end user?
No, you don't need to contact us.
The component you receive does not contain any limitations
and can be used by a developer and an end user without the need of any keys.
This also makes the so-called "xcopy deploy" possible.
Back to the top...
# How much does it cost in Euro?
We don't sell our components in Euro and the price in Euro depends on the current exchange rate.
Today, the rate is something like this.
Back to the top...
# What options do I have if my company has a policy of not buying over the internet?
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...
1. Install And Setup
# How do I install and use Rebex Mail for .NET?
Unzip the archive into a folder of your choice and inspect the contents.
No installation is necessary.
The bin folder contains both debug and release versions 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 .NET, just add a reference to it!
The manual is in documentation folder and the code samples are in examples.
Back to the top...
# How do I install Mail for .NET 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 all DLLs 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...
# Do I have to install Mail for .NET into Global Assembly Cache to get it working?
No, you don't have to.
Mail for .NET can be used either as application-private assembly and deployed within
the directory structure of your application,
or installed into GAC as shared assembly, which can be used by multiple
applications on the machine.
Both approaches have their pros and cons. Application-private assemblies allow
simple xcopy deployment and provide complete control over assemblies that
are isolated to the application. Shared assemblies load a bit faster, especially
if several applications are using the same assembly simultaneously, because the
code from the same location on disk can be loaded only once and shared. Installing
into GAC also simplifies deploying bug fixes or security patches
.
This decision is up to you.
Back to the top...
2. Trial Version
# How do I register the trial version?
When you buy Rebex Mail for .NET, 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 and the "Comments" property.
If the dll is a trial version then you'll find "trial version" at the end of the string
in the "Value:" box. If the "trial version" text is missing then it's a full version dll.
Back to the top...
3. Support
# What do I need to do to get upgrades or bug fixes?
If you have bought Mail for .NET, 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?
Our preferred form of support is by email (support@rebex.net) and is free.
Phone support is also possible on demand.
Back to the top...
5. Platforms
# Can I use the Mail for .NET component in ASP.NET?
Yes, you can. ASP.NET is still just .NET code.
However, it is not as easy as in ordinary applications.
There are several things to keep in mind:
- ASP.NET environment is multithreaded - several instances of the same page can be processed at the same time.
- Lot of operations might take a long time to complete, especially file transfers.
- Even Connect and Login methods may take a long time to complete, so you probably wouldn't want
to call this again and again - instances of the Smtp/Pop3/Imap classes can be made persistent by being stored in a Session
or Application objects, for example...
Back to the top...
# Does it work with Windows Server 2003 (or .NET Framework 1.1)?
Yes, it does. We provide native build for .NET 1.0, 1.1 and 2.0.
Back to the top...
# Does it work with .NET Framework 2.0?
Yes, it does. We provide native build for .NET 1.0, 1.1 and 2.0.
Back to the top...
# Does it work with the .NET Compact Framework?
Rebex Mail for .NET Compact Framework is not available yet.
We are working on it.
Back to the top...
# 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.
However, when connecting to Microsoft Exchange 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
When authenticating to Microsoft Exchange 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, 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 SSL work with Microsoft Exchange?
Yes, it does, if SSL is configured for appropriate protocols.
Also, be aware that Exchange supports explicit SMTP, implicit POP3 and implicit IMAP.
It does not support implicit SMTP, explicit POP3 or explicit IMAP.
Back to the top...
6. Samples
# Do you have any examples on .......?
See the list of our free samples and tutorials!
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...
7. Exceptions
# When I try to ......., an exception is thrown! Can you help me?
We need a bit more detailed description of what happened to be able to help you!
- What version of Mail for .NET are you using?
- What was the content of the stack trace of the exception?
- Are you connecting through a proxy? If so, what type of proxy is it and what software does it use?
- Are you behind a firewall?
- ...
Back to the top...