Take the community feedback survey now.

alga
Nov 24, 2009
  5170
(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

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP - Introducing the beta of Opti Graph Extensions add-on

Introducing Opti Graph Extensions: Enhanced Search Management for Optimizely CMS I am excited to announce the beta release of **Opti Graph...

Graham Carr | Sep 15, 2025

Content modeling for beginners

  Introduction Learning by Doing – Optimizely Build Series  is a YouTube series where I am building  a fictional  website called  TasteTrail , food...

Ratish | Sep 14, 2025 |

A day in the life of an Optimizely OMVP - Enhancing Search Relevance with Optimizely Graph: Synonyms and Pinned Results

When building search experiences for modern digital platforms, relevance is everything. Users expect search to understand their intent, even when...

Graham Carr | Sep 14, 2025

Optimizely CMS and HTML validation message: Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

When using the W3C Markup Validation Service, some annoying information messages pop up because Optimizely CMS adds the trailing slash to...

Tomas Hensrud Gulla | Sep 14, 2025 |