Nov 24, 2009
(4 votes)

EPiServerMail should be reactivated if the project is moved / copied

The following information should be considered when opting to move / copy a project with an EPiServer Mail installation from a test server to a production server, rather than creating a fresh installation on the production server.

The EPiServerMail.config file is a file containing unique data relating to the server the project, and EPiServerMail installation, is hosted on.  This means that a project cannot simply be moved / copied from a test server to a production server without issue. Note: Trying to reinstall EPiServerMail on any projects which already have EPiServerMail installed can also cause issues.

Happily, however, when copying a project it is only certain values within the EPiServerMail.config file which will need to be updated. It will be necessary to:

  1. Empty the brokerName attribute in the broker element.
  2. Remove the rsaKeyValue element under broker.
  3. Update the attributes in the editor and smtpServer elements as necessary.

Another option, of course, would be to create a temporary project and install a new copy of EpiServerMail - putting in the details to match the production server as necessary.  This would create a new EPiServerMail.config file which could be used to replace the  file on the production server.

In both cases, it should be noted that certain corresponding values will also have to be deleted from the tblEPiServerCommonSetting table, in the database.  For example, the EPiServermail_Default_activationStatus row would need to be deleted, however, rows which contain EPiServerCommon_version or EPiServerMail_version should be left.

Once the changes have been made you will need to activate EPiServerMail again - using the 'create an account' option which should have become available again due to the above steps.

Disclaimer: Reasonable effort has been made by the author to ensure that the information provided here is accurate, however, no guarantees for the accuracy of information are made. You hold full responsibility for your actions - please remember to make a backup before making any changes.

Nov 24, 2009


Please login to comment.
Latest blogs
Preview multiple Visitor Groups directly while browsing your Optimizely site

Visitor groups are great - it's an easy way to add personalization towards market segments to your site. But it does come with it's own set of...

Allan Thraen | Sep 26, 2022 | Syndicated blog

The Report Center is finally back in Optimizely CMS 12

With Episerver.CMS.UI 12.12.0 the Report Center is finally re-introduced in the core product.

Tomas Hensrud Gulla | Sep 26, 2022 | Syndicated blog

Dynamic Route in ASP.NET Core When MapDynamicControllerRoute Does Not Work

Background Creating one of the add-on for Optimizely I had to deal with challenge to register dynamically route for the API controller. Dynamic rou...

valdis | Sep 25, 2022 | Syndicated blog

404 Error on Static Assets Within an Optimizely plugin

Background With the move to CMS 12 and .NET 5/6, developers are now able to build Plugins and Extensions using Razor Class Libraries (RCL).  These...

Mark Stott | Sep 23, 2022