If a new version of JungleMail is released and you have an active subscription, you can easily upgrade. We will notify you about the latest versions via email, but you can also check JungleMail Releases page.

The installation account must have at least the following permissions:

  • Member of the local server Administrators group (to install application files)
  • Member of the SharePoint Farm Administrators group (to deploy solutions to the farm)
  • SharePoint site collection administrator (to activate the features after installation)

How to upgrade JungleMail

  1. Download the latest JungleMail installer here.
  2. Copy the installer on the SharePoint server running the Central Administration service.
  3. Restart the World Wide Web Publishing Service (W3SVC) before installation on every server running it in your SharePoint farm. You can use the  iisreset  /stop / noforce  and  iisreset  /start command line commands. This will ensure that no system files that need to be updated are locked, which could cause the installation to fail.
  4. Launch JungleMail Installer from SharePoint Server running Central Administration Service. The product will be automatically deployed to all other SharePoint Farm servers by the SharePoint Timer service.
    Note: installation may cause 2-5 minutes of downtime.
  5. Follow the installation wizard instructions and choose the Upgrade option.

  6. When the installation is complete, review the summary screen to confirm that the product installed successfully, then click Close.
  7. Restart SharePoint Timer Service on all servers.

9. Run the setup program again. Follow the installation wizard instructions and choose a  Repair option.

10. When the installation is complete, review the summary screen to confirm that the product installed successfully, and then click  Close. Now your JungleMail successfully upgraded to the latest version.

Please note if you are upgrading from version 5.0 to 5.2 or later:

In order to fully utilize the new icon sets available in version 5.2 or later, please delete the old icons.

1. Navigate to site collection root, open Site Contents, then locate and open the  JungleMail Assets library. In the library, open the Built-in Email Builder Blocks Images folder and delete the Social folder.

2. Open your site collection settings, click  Site Collection Features, deactivate the JungleMail Core feature, then activate it again.

Upgrade to JungleMail 7

JungleMail is a farm solution, therefore it should either be installed on a SharePoint On-Premises server or on a fully controllable SharePoint server in the cloud.   

System requirements

  • SharePoint Server 2013, SharePoint Foundation 2013, SharePoint Server 2016


  • The installation and upgrading steps are described  at the beginning of the article. Read more about JungleMail installation guidelines.
  • Upgrading process can take longer due to analytical data processing.
  • Clear browser temporary files and run the JungleMail UI to check installation.
  • After upgrading to JungleMail 7, go to JungleMail License management in Central Administration. The product code is changed to JNML-1607 and JungleMail status is converted to Trial, as it requires license update. If you have an active Premium Support subscription, please contact us and we will send you the new license key.

Additional steps for JungleMail Enterprise

1. Enable SQL Mode for performance and extensive analytics.

2. Configure Cumulative Reports.

Changes to Subscription Web Part configuration

To make the subscription web part safer and to make sure workflows can be used without problems, we have changed the way it works when used on  Other Site Collections. For the new web part configuration to work on your environment, you will have to make some changes.

1. Create a separate user in Active Directory to access your main SharePoint Collection on which the JungleMail Core feature is activated. For example, your username could   be  Domain\jmUser. Note that the user should be a member of the Domain Users group. For security purposes, we recommend you to ensure that your domain service accounts are denied the log on locally user rights at the very least. This action will prevent a malicious user from logging in using a breached service account.

2. Create a new Permission level on root site level for the newly created account. This will ensure the account will only have access to the JungleMail Service and not to the parent lists or libraries of that site collection. 

  • Open root site’s Site Permissions and click Permission Levels

  • Click Add a Permission Level

  • Check the Use Remote Interfaces and Open boxes and save this custom permission level, and give it a custom name,  for  example  JungleMailWebPartsPrivileges

3. On the root site, go to site settings, click Site Permissions, then click Grant Permissions and assign the newly created permission level to the user created in Step 1.

4. Now you need to assign the required permissions for the user in JungleMail built-in lists. All lists are located on the root site collection. Assign the following permissions to the user on a list level in the following lists: 

  • JungleMail Subscribers  - View, Add and Edit items permissions
  • JungleMail Topics - Read permission level
  • JungleMail Tracker Links - Read permission level
  • JungleMail Tracker Actions - View, Add permissions

Note: you should disable permission inheritance or Set Unique permissions for the above lists.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us