Last Updated on
The Newsletter main configuration contains a number of parameters that must be set properly. Below you’ll find an explanation of each parameter and the pros and cons you can face while using it. Some parameters are required to get Newsletter work.
Please use the support forum to ask questions.
The Newsletter page
Newsletter needs a page to show service messages, like the activation, the welcome and goodbye messages (all those message are configurable from the admin panels).
That page should be a regular WordPress page that contains only the [newsletter] short-code, nothing else.
If you followed the welcome wizard, that page is created for you and pre-configured by Newsletter: you can find it under the name “Newsletter” in your blog page list.
The page should be selected in the “Newsletter page” option field, so Newsletter knows where to redirect the subscriber once an action is performed and a message needs to be shown. There is the option to not use a WordPress page, in that case Newsletter show messages in a flat, neutral page without any blog element.
If the selected page is later deleted or unpublished it may happens a 404 error page is shown instead: check the configuration. More, if the page is changed removing the [newsletter] shortcode it stops working.
Pay attention to not use any other Newsletter shortcodes, like the [newsletter_form] since they won’t show the service messages.
Do not add other text in said page or it will be shown everytime a message is displayed.
If you want customize the layout of the Newsletter page, for example without the regular sidebar or menu, we suggest to check if your theme has the option to change the layout at page level, most themes do. Or if you theme has a special page layout for landing pages, which usually are simpler and without all the regular stuff (menu, sidebars, footer and so on).
You can even create a custom template page in your theme (or better in a child theme): check the theme documentation or find out support form the theme author.
The sender (name and email address)
The sender is “who” is sending emails to your subscribers. With “who” we mean a name (for example your name if your’s is a personal blog or your brand name if it is a company blog) and an email address.
Most of the times the best choice is to use an email address from your domain and possibly with a real mailbox behind. Never use as email address an account from free services as gmail, yahoo, aol, outlook and so on. Your blog (server) is not allowed to send emails for those accounts.
Some providers do not allow you to send emails with a fake sender (like firstname.lastname@example.org) if that address is neither an alias nor a real email address.
Remember to always use the status panel to send test email to verify if those settings are affecting the delivery.
More tips on “how to choose the sender address” article.
The return path is an email address where undelivered messages are returned.
If it is a real mailbox you can check it to remove addresses from your list which are no longer reachable. The bounce extension can do it for you automatically.
Some provides do not allow to specify a return path address.
The reply to is an additional address used as destination by email clients when the receiver wants reply to a newsletter. As per the return path, sometime setting this field can lead to blocked email and you should set it to an address in your domain.
If you bought a license to activate the professional extension you should set it in this field to enable the direct installation from the Newsletter extension panel and their update (once installed) from your blog plugins panel.
Max emails per hour
Newsletter has a delivery engine which sends out emails as quickly as configured. This configuration is important since providers donot like blogs on shared web spaces that send out tons of emails in a limited time frame.
You should always ask your provider which is the limit they will tolerate.
Even on a private server, setting this limit to a reasonable value is a good idea to avoid saturating the server with queued email.
This limit is internally divided by 12 since Newsletter sends a batch of emails every five minutes.
If you experience a lower delivery speed than set, remember that Newsletter can internally lower that value if it detects a PHP max execution timeout that does not let you send all planned emails in a run.
Enabling the logger at info level and looking at the generated log file, you can see this situation clearly reported.
See the Delivery Engine page for more information about the delivering process.
Enabling access to the editors means blog users with editor role can use the Newsletter. Every part of the Newsletter plugin from the configuration panels to the newsletter composer panel.
Since version 5.5.0.
With this option you can select if the IP address of your subscribers should be stored, anonymized or not stored at all. IP address is collected at the subscription time and with statistics (read and click tracking). Anonymized ip address are changed removing the last number and replacing it with zero.
Note: flood control and geolocation are affected by this setting. If you decide to not store this information geolocation and flooding check will be disabled. If you keep the IP address anonymized, the geolocation usually will work, even if with less precision.
Every Newsletter component (and even the professional extension) can log internal state and errors. The log level defines how fine should be those logs.
Warning: debug level can create huge log files.
Log files are listed at the bottom of the status panel, and can be downloaded or deleted. Log files are rotated monthly.
The debug mode is only for support operations. It intercept even the PHP errors and logs them in a specific log file.
Direct email sending
This option enables Newsletter to send emails directly without using the WordPress internal api. You should enable this option if you want to send even the text part of your newsletter. You must keep it disabed if you’re using a plugin to send all blog emails via an external service like an SMTP server. Just to name few of those plugins: Postman, WP SMTP, SMTP bank, …
Email body encoding
Is the way an email message is internally encoded: usually the default should be good, but some providers have old mail servers with problems managing messages with long lines: try to set it to “base 64”, it’s the configuration I usually use.
Note: this option has no meaning when you use an integration extension to send emails with providers like Amazon SES, Mailjet, Sendgrid and so on.
In this panel you can configure few geneal parameters for your business, like the social pages, the logo, your business name and address, copyright notices. All those values could be used by Newsletter to pre-compose the content of your newsletters.
You logo should be a png image with transparency for the best rendering on different newsletter themes. Keep the file lightweight and ideally smaller than 500px in width and 200px in height.