Packtl

From here we can also create new Newsletters should we wish so. The Subscriptions tab allows us to see and manage the subscriptions to our various newsletters, the Sent issues tab lists issues sent out to the newsletter lists, and the Drafts tab lists issues which are still being written. From within the Settings tab, we can set how new issues for newsletters are created, as well as the email address shown as the sender of issues.

Don't forget to set the permissions; you want your users to be able to I

subscribe to newsletters. I

Users can subscribe to newsletters from within their account, or we can enable blocks for the relevant newsletters we have on our site.

Account

My newsletters

current newsietxer suDscnpEions

Select the newsletter(s) to which you want to subscribe or unsubscribe. □ Dino Space! newsletter

1 1

To send an "issue" to our newsletter list, we need to create the issue as a new content element via Create content | Newsletter issue.

We enter the subject of our email as the Title, select the newsletter to send the message to from the Newsletter drop-down list, and the message is entered into the Body box.

Our first newsletter!

Newsletter:

|Dino Space! newsletterM D Menu settings

I Split summary at cursor )

Body:

Our newsletterl

This will be the body of your newsletter. Available variables ere: isite (the name oF your website), iuri [a link to your homepage), iuri„brieF (homepage link without the httpi//), 'date (today's date), Mogin_uii (link to login page).

rpACKTl

L PUBLISHING J

Beneath these options, we have some newsletter specific-options within the Newsletter sending options box. These options allow us to set the priority of the email message (this is often ignored by email clients), if we wish to request a receipt to see if a user has read the message (this is also often ignored by email clients) and finally, we can select a sending method.

There are three sending methods, which are:

• Don't send now—this won't send the message, and will save it as a draft.

• Send one test newsletter to the test address—this will send the email message to the test email addresses, which we can set in the administration area. This allows us to review the newsletter, as if we were a subscriber, make any final alterations and then send it to our list.

• Send newsletter—this sends the email to our newsletter list.

How to send an email to all our users?

We can use the module to send an email to all of our users, by taking advantage of the subscriber import feature. Within Administer | Content management | Newsletters | Subscriptions, we have the ability to Import subscriptions, as shown in the following screenshot:

Importing subscribers consists of entering the E-mail addresses (separated by a comma) and selecting the newsletter which we wish the user to subscribe to. To get all of our current members to subscribe to the mailing list, we could export all of our users' email addresses directly from the Drupal database, using a tool such as phpMyAdmin. If we use the tool correctly, we can even get the data in a comma-separated list ready to be pasted into the form.

There are legalities involved with sending bulk emails, and mailing lists, especially with regards to SPAM. Most countries have their own laws relating to this. More information on the legalities of sending bulk mailings is available in Chapter 10,

Promoting your Site.

When web sites send out bulk email campaigns, it is important to be careful about their frequency of emails. If all emails in the campaign are sent at once, this could be seen as a sign of SPAM, leading to blacklisting on mail servers, and also penalties from many shared hosts. If emails are sent out slowly, it may take a long time for a campaign to be sent out to all recipients.

The Simplenews module allows us to configure the frequency of the emails sent. These settings can be accessed from Administer | Site configuration | Simplenews | Send mail. Here the cron box is checked, indicating that emails are sent each time the Drupal cron script is called. The Cron throttle defines how many newsletters are sent each time the Drupal cron script is called. By default, it is set to 20, which is very low. So this should be changed perhaps to 100 or 500. You may wish to contact your hosting company for advice on email limits imposed by them.

Give it a try

We have covered module installation and configuration extensively; so why not try and install the module yourself and experiment with HTML newsletters.

Give it a try

We have covered module installation and configuration extensively; so why not try and install the module yourself and experiment with HTML newsletters.

Legalities

Throttling

0 0

Post a comment