Common Problems
Q. I'm getting an error: "File or assembly name SmtpDotNet, or one of its dependencies, was not found."
A. You may also get error detail that may include:
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileNotFoundException: File or assembly name SmtpDotNet, or one of its dependencies, was not found.
This is caused by a conflict in the version of Smtp.NET compiled and the version that is found at runtime. Check to ensure that the version of Smtp.NET you are referencing is the same version that is in either your application's bin folder or in the GAC (Global Assembly Cache)
General
Q. How do I know that a message was sent?
A. If emailQ.NET is configured to do so, all sent messages are moved to the "Sent" directory after being successfully sent. By default, emailQ.NET is configured to do this.
Licensing
Q. How does the licensing work?
A. Licensing is based on the number of CPUs on the server on which emailQ.NET is installed on.
For example:
- If you install emailQ.NET on one single processor machine, you will need one license.
- If you install emailQ.NET on one two processor machine, you will need two licenses.
- If you install emailQ.NET on two four processor machines, you will need a total of eight licenses.
If you need special pricing information, please contact us directly.
Performance
Q. What is the expected performance of emailQ.NET?
A. Performance tests were performed on a Dual Pentium III 500 Mhz with 384MB memory on Windows.NET Server RC1. emailQ.NET was running in Windows Service Mode with 20 concurrent threads. CPU utilization averaged less than 10% and averaged sending 125,000 emails per hour (2083/emails/minute, 34.7/emails/second)
Scalability
Q. How well can emailQ.NET scale for our needs?
A. emailQ.NET scales well in a multithreaded and multiprocessor environment. As the number of processors increase, so does the amount of email messages at which emailQ.NET can send.
Stability
Q. Is emailQ.NET stable? Does it require maintenance or checking up on?
A. emailQ.NET has been rigorously tested and has proven itself to be stable under heavy loads. It has also undergone two months of beta testing with current Smtp.NET customers; none of which reported any problems with stability.
