Kentico CMS 7.0 Developer's Guide



Previous topic Next topic Mail us feedback on this topic!  


Previous topic Next topic JavaScript is required for the print function Mail us feedback on this topic!  

Problems with sending e-mails


If you are not correctly receiving newsletter e-mails, please check the following:


1. The newsletter issues are sent out using a scheduled task that is executed every 1 minute by default. You may need to wait for up to 2 minutes before you receive newsletter issue e-mail. The scheduled task status can be checked at CMS Desk -> Administration -> Scheduled tasks.


2. Go to CMS Desk -> Tools -> Newsletter -> Newsletter queue. If some e-mail failed, you will find the error message here. After you resolve the technical issue, you can resend all failed e-mails by clicking ResendAllFailed Resend all failed.


3. If your newsletters are configured to use the e-mail queue, go to CMS Site Manager -> Administration -> E-mail queue. Any e-mails lost due to errors can be monitored and re-sent here.


4. Make sure you are using the correct e-mail addresses.


5. Make sure the newsletter issues aren't being blocked by some anti-spam software.


6. Go to Site Manager -> Settings -> System -> E-mails or Administration -> SMTP servers and make sure your SMTP servers are configured correctly. You can find additional details on SMTP server configuration in the SMTP server configuration topic. You can try sending a test e-mail in Site Manager -> Administration -> System -> E-mail.


7. Newsletter e-mail debugging might be helpful when solving problems with newsletter e-mails. To enable newsletter debugging, add the following keys to the /configuration/appSettings section of your project's web.config file:


<add key="CMSLogEmails" value="true"/>

<add key="CMSDebugEmails" value="true"/>


The first key enables you to log all the sent e-mails. You can find the logged e-mails in <web root>/AppData/logemails.log. The log contains each e-mail's recipient and subject.


The second key enables you to log all the sent e-mails into event log without actually sending them to the recipients. This is helpful when you need to test the functionality but do not want the testing e-mails to actually reach the recipient. You can view the event log in Administration -> Event log section of both CMS Desk and Site Manager. The e-mails are logged as an Information type of event.


Additionally, with the second key enabled, a Sending failed for <recipient's e-mail address> error is generated at random to simulate an error when sending an e-mail.


Problems with unsubscription links


If your unsubscription links are not resolving correctly, check that the Base URL property of the given newsletter is set correctly according to the domain name of your website. To configure this property:


1.Go to CMS Desk -> Tools -> Newsletters.

2.Edit (Edit) the newsletter and switch to its Configuration tab.


Note: Newsletters only generate valid unsubscription links when sending issues to actual subscribers. Unsubscription links do not work in draft e-mails, since the recipients are not linked to subscribers in the system.


Problems with role or contact group subscribers


If you have a user role set as a subscriber for your newsletter, it is highly recommended to send the newsletter issues via the e-mail queue in order for the issues to be successfully sent to all members of the role. To set the newsletter to use the newsletter queue:


1.Go to CMS Desk -> Tools -> Newsletter.

2.Edit (Edit) your newsletter and switch to the Configuration tab.

3.Enable the Send issues via e-mail queue property.

4.Click Save Save.


Problems with event log spam [This option is only available after applying hotfix 7.0.18 or newer]


By default, the system logs an event log entry for every sent newsletter issue. When mailing out issues to a very large number of subscribers, this may lead to a cluttered event log or even website performance problems.


You can disable logging of newsletter issue changes (including send events) by adding the following key to the /configuration/appSettings section of your project's web.config file:


<add key="CMSLogNewsletterIssueEvents" value="false" />