Pricing is based only on how much email you need to send each month.
Accounts are provisioned on dedicated servers: all customer data and email sending is isolated from all other customers for IP reputation, security, and performance reasons.
|All Plans Include|
HIPAA-compliant: Business Associate Agreement
HIPAA-compliant Email: Send ePHI in your messages
Dedicated IP Address
Email Sending via SMTP
Email Sending via API
Server-side Email Templates for SMTP and API
Open & Click Tracking
Feedback Loop Tracking
SPF, DKIM, DMARC Support
Maximum sending rate
Searchable Email Activity
*Longer time periods are available; however, if you are sending a lot of email, a longer retention period may require a server upgrade.
For those sending a lot of email (millions of messages each month), a shorter time period would be recommended to keep the database server requirements modest and the costs down.
Ticket, Chat, & Phone Support
The server included is a Business Class Server with enough horsepower to enable sending to the indicated volume of email recipients. If you are interested in faster sending, larger-scale sending, a multi-server solution, Enterprise Class servers, extensive API usage, or other custom configurations, Contact Sales.
High Volume messages are delivered to LuxSci via API or SMTP. They are then passed to the proprietary SecureLineTM encryption engine. SecureLine gathers information from numerous sources to dynamically determine the optimal email encryption method to use for each recipient. The messages are then encrypted and securely delivered.
Everything is automatic and dynamic. The sender does not have to do anything.
Unlike other SaaS solutions that place all client data in a shared cloud, LuxSci is unique in that it provides each client with their own dedicated server, cluster, or unique custom deployment. This can be compared to having one's property secured in a moated castle versus a communal camping site. The solution is more reliable, ensures consistency, and vastly improves the overall security of your data.
Custom solutions can be tailored for very high volumes of sending, very high throughput, very high security, and business continuity. They can include:
If a custom solution might be right for you, talk to a LuxSci Expert.
No. LuxSci provides High Volume Secure Sending only on dedicated servers for maximum security, performance, and sending reputation.
As many as you like! LuxSci does not limit the number of legitimate subscribers or how you segment your lists. We base our plans only on the number of recipients you send messages to each month.
A recipient is an email address a message is sent to. It's also the unit we use to measure your email sending. One message to one person is one recipient, two messages to the same 10 people comprise 20 recipients, 1000 messages to one person each equals 1000 recipients.
LuxSci does not limit the number of messages you can send at once. You can send a single message or email blasts that go to thousands or millions of recipients. Your plan determines the maximum number of recipients you can send to per month.
If you reach your email sending limit for the month, you will still be permitted to send email; however, you will be charged a fee for the excess sending at the beginning of the next month. If you are going to exceed your sending limits consistently and by a significant amount, it will be more cost effective to upgrade your plan to a higher monthly sending limit.
If you would prefer that your sending be suspended if you hit your sending limit, so that there is no possibility for excess use fees, please contact LuxSci support.
You can review your monthly sending limit, what happens if you hit your limit, and what the excess usage fee is in your account's High Volume Sending Overview Page.
Yes, LuxSci provides the option of purchasing LuxSci Mailer, a web-based HIPAA-compliant email marketing and campaign management solution. You also have the option of continuing to use your current email software.
Yes. LuxSci SecureLineTM has a special feature called TLS Exclusive. When you enable this, LuxSci will dynamically use Forced TLS to deliver your messages securely to everyone who can support TLS and will drop messages to those who don't (with appropriate notes in our delivery tracking system). If you have low priority messages (e.g., email marketing messages) which still need to be secure (e.g., in health care), "TLS Exclusive" high volume sending is a perfect fit.
The number of sustained concurrent SMTP connections you can make at once depends on the type of dedicated server that you have. For standard plans, sustained concurrent connections should be 1-4 and bursting should be 20 or less. See Sending Rates.
While any email provider can and does get blocked on occasion, LuxSci takes stringent measures to keep this from happening. LuxSci has very strict acceptable use policies and manually checks every new customer to keep spammers out. LuxSci's monitoring system works to detect any improper use before it becomes a problem. As a result, problems are rare. If a problem does occur, LuxSci's staff have the training to resolve the issue ASAP. Also, when you have a dedicated server (and thus a dedicated IP address), your IP address reputation reflects only your own sending history.
No, you do not need to change your email hosting service to LuxSci. You can easily configure your sending programs to send your emails through LuxSci's email sending service without affecting your existing email solution.
LuxSci will send your email through a dedicated server that has a dedicated IP address. Your dedicated server may or may not use IP addresses recently used by other customers. So, they may or may not be "pre-warmed." We recommend warming up your new server yourself for best delivery results. See also: Warm up your IP automatically.
While neither LuxSci nor anyone else can ensure that every message is delivered to every INBOX, our excellent reputation and stringent security measures maximize the chances that your email messages will go to the intended recipients. LuxSci will advise you on how to construct your messages and maintain your lists and campaigns for the best result. See Key Ingredients for Good Deliverability.
To maximize throughput, contact sales so that your account can be put on a powerful server or server cluster.
When delivery speed (i.e., messages/hour) is a factor, a more powerful server will receive, process, and deliver deliver your messages faster and will allow you to use more sustained concurrent connections.
The server size included with the places listed above is "1 CPU".
|Dedicated Server Size|
|1 CPU||2 CPU||4 CPU||8 CPU|
For increased capacity, high burst rates, or to account for other factors (see below) like large messages, lack of pipelining, etc., we recommend choosing a larger server or a load-balanced multi-server clusters.
The maximum sustained rate at which you can deliver email to the server, have it processed, and have it delivered to the recipient's mail servers depends on many factors. These include:
The speed by which you can deliver message to your server:
The speed by which the messages can be processed (i.e., encrypted, tracked, etc.):
The speed by which the messages can be delivered to recipients
These factors determine how fast you can have a quantity of messages delivered to their recipients. Some of these factors are under your control and some of them are not.
The "maximum sending rate" (msgs/hr) is the upper bound rate that you can achieve through the service. It assumes optimal sending conditions for high volume encrypted email: very small (5 KB) messages, all to the same domain, sent over a fast network using SMTP Pipelining, and encrypted using TLS. Under these conditions, there is no block listing, gray listing, or DNS slowness, there are no problems with some recipient email servers, and we choose an optimal sustained number of concurrent sending connections to the server.
Expected Rate: Under normal sending conditions, your delivery throughput may be below the maximum sending rate.
|Maximum msgs/day||This is an estimate of the maximum number of messages that your server could process and deliver over 24 hours of sustained sending at approximately the maximum hourly rate.|
For some customers, the speed of sending is very important. There are two significant modes of sending:
Making one or more connections to your server and then sending at a consistent rate for a long period of time. E.g. 20,000 messages/hour for minutes or hours. Sustained rates are relevant when sending an email marketing blast to a large subscriber list or when offloading a large number of messages from an external application through your sending server.
A "burst" refers to sending a bunch of messages in a very short time; e.g. 25 or 50 messages within a second or two. Burst differs from "sustained" in that "bursts" are short duration events and when you are not "bursting" you are sending relatively few messages here and there ... infrequent sending. Bursting is relevant for transactional email messages when you are sending them "as needed" but require the ability to send many at once should that need arise, as it will.
Sending speed is important for customers who need to send large mailings at a sustained rate. Understanding sending speed helps you determine how long it will take to send that blast to 100,000 or 1 million subscribers.
There is a theoretical maximum number of messages/hour that any server can manage. How fast you can actually send is affected by a number of factors.
|1. Server Power||
More powerful servers can handle more concurrent connections, process more messages at once, deliver more messages at once, and thus give you higher sending rates. The number of CPU cores is the primary factor governing performance; however, memory and disk speed are also important.
|2. Email Sending Program||
Different email marketing/sending programs have different capacities for how efficiently they can send high volumes of email. Simply switching from one program to another can increase your throughput significantly.
|3. SMTP Pipelining||
Use an email marketing program that supports SMTP Pipelining. With this feature, the program opens a single authenticated connection to the server and sends multiple messages in succession over that connection. This is significantly faster than opening a new connection and authenticating again for every single message to be sent.
|4. Concurrent Connections||
If your sending program can open multiple connections to our SMTP servers at the same time and send multiple messages at once, then you can delivery messages to our servers more quickly. Depending on how powerful your server is and how slow your network connections are, you can use more and more concurrent connections to achieve higher and higher sending rates. Combined with SMTP Pipelining, an appropriate number of concurrent connections goes a long way to maximizing your throughput potential.
Under most circumstances, sending programs can deliver messages to our servers much more quickly than the servers can process those messages (i.e., encrypt them, track them, log them, etc.) and then deliver them to the recipients' mail servers.
The recommended maximum number of concurrent connections to use for sustained email sending is given in the table, above. It is important to note that while exceeding that recommended value will get your email to your server faster, sustained sending at that rate will overtax the server and cause the overall rate of processing and delivery of your messages to your recipients to slow down. Stick to the recommended number of concurrent connections for sustained sending.
|5. Network Speed||
Your messages must be transmitted from your email sending program to our servers. The speed of your network, any packet loss, and the distance between your sending computer and our servers can significantly impact the maximum rate that you can send messages.
|6. Message Size||
Like network speed, the larger your messages are, the more time it will take to transmit them from your email sending program to our servers. For example, on a fast network, increasing message size from 5KB to 1MB decreased throughput by 50%. The actual impact of size will depend greatly on your network speed and other factors.
|7. Recipient Email Server and DNS Speed||
In order for our servers to deliver messages to your recipients, the servers have to (a) look up where to deliver the messages to (DNS), and (b) talk to those servers to deliver the messages to them. If the DNS lookup as slow or the recipients are in domains that do not exist, this step can take a while. If the recipient's email servers are overloaded, on a slow network, or are having other issues, then the delivery phase can be slow.
Delivering many messages to recipients with these issues can slow down your entire sending process... as other messages have to wait for the slower ones to be sent.
|8. Block listing and Greylisting||
If your email content or sending patterns have gotten your server block listed or greylisted, then delivering email messages to recipient servers that are now blocking you or deferring you can slow down your delivery rates.
This can also cause a backlog of messages that are waiting to be accepted by these recipient servers. The need to Retry the backlog slows the process of delivering all other messages (though it does not block their delivery).
|9. Recipients per message||
Most email marketing and transactional email messages are sent individually to each recipient. This allows easier tracking of opens, views, etc. However, if you send each message to many recipients (e.g., 100s of recipients), then your sending program has significantly fewer messages to deliver to our servers. The delivery of your messages to our servers can happen 10s or 100s of times faster than if you sent in the usual one recipient/message pattern.
Additionally, if each message contains only recipients in a specific domain, then actual delivery to these recipients can be expedited by this efficiency. E.g. If you are sending to 500 AOL users, instead of sending 500 individual messages, send one message with all 500 AOL users listed as "BCC" recipients. Delivery can be almost 500 times faster.
|10. SecureLine Email Encryption||
In the example sending rates, we assumed that all messages would be sent using SecureLine TLS. If PGP, S/MIME, or Escrow are used, that can also impact email processing speed.
|11. Outbound Email Processing||
If you are using other email processing features that come with High Volume Secure Sending (e.g. content scanning, recipient restrictions, size restrictions,etc.), this processing may affect your maximum sending rate.
LuxSci has features that can be used to rate limit the processing of outbound email. This is usually used when "warming up" IP addresses to assist senders in sending slowly and establishing their IP address reputation.
This rate limiting is on, your maximum sending rate will be capped by this process.
Zero tolerance policy for sending of spam and unsolicited commercial email
The Acceptable Use Policy is very explicit about what you can and cannot do with the High Volume Secure Sending service. Highlights include:
Headers are added to each message sent so that it can trace back to the sender should anyone report abuse complaints. Headers also include information to notify recipients to contact LuxSci to report abuse.
High Volume services may not be used for the sending of email:
Furthermore, High Volume services are not to be used for the sending of email for any of the following industries:
Customers wishing to send this type of content should consider setting up their own mail servers, as most legitimate email marketing companies will not be able to help you.