Loading...

All project content is available for reading, but you need to be a member of the project for Subversion checkout of source code, or to create/modify any information.
Login if you are a member. Apply here to request membership (open to all).

Frequently Asked Questions

FAQ Content

  1. Sales and Licensing
    1. How do I order the module?
    2. Can I use the module on an enterprise site?
    3. Can I change the source code?
    4. I get a license error for aspnetEmail
  2. General
    1. How many emails can the module handle?
    2. How are emails sent
    3. Why do you use the aspnetEmail component?
  3. Other Questions from Ticket System
  4. New Question?

Sales and Licensing

How do I order the module?

See the pricing section.

Can I use the module on an enterprise site?

Yes.

Can I change the source code?

Yes you can, for your own use (or for a given customer). You have full access to the source code, but make sure you read the license terms first. If you change the source we encourage you to contribute it back to us, as a patch or in a branch in the repository (or send us the code by email.) When you contribute, everyone benefits.

I get a license error for aspnetEmail

See the installation page. You need to purchase or download an evaluation license for aspNetEmail from Advanced Intellect

General

How many emails can the module handle?

The number of recipients the newsletter can send is theoretically limitless, as the sending process is handled by an EPiServer scheduled task. Practically, the number of recipients is limited by the time you feel is appropriate for a given newsletter to be sent.

The sending process is done in batches, which means that each time the task runs, it will grab a batch of recipients, and send emails. You can configure the number of emails in a batch, and how often the task runs. It is important that you tune the numbers to avoid idle time if you have lots of recipients. Use small batches and run task often if you have large amounts of emails to send.

If one email takes one second to send (depends on the size of the email, number of attachments etc.) it will send 86400 emails in 24 hours, given an optimal batch size and task schedule interval.

How are emails sent

The module sends emails one by one, and needs to connect to a SMTP server. It means that each email is sent separately with a unique to-address. If you have 1000 recipients, your SMTP server will receive 1000 emails to process. No BCC is used to send the same email to many recpients. This is to support personalized emails.

Why do you use the aspnetEmail component?

When we initially created the Newsletter module, the mail features in the .NET Framework (1.1) had no support for inline attachments, and separating the text and html part of the email was hard. We choose to buy a 3rd party component to handle this. At some time, we might move over to built-in .NET Framework email components, if they support all the requirements we have.

Other Questions from Ticket System

#342
Change the admin interface to use jquery for more dynamic look and feel
#341
Store Newsletter data in DDS
#268
Mass Testing

New Question?

Ask any Newsletter question by starting a new question thread.