You do not have permission to access this area.


Add Feedback
Great step by step. Two things I would suggest you add.

1 - How to know which version of IIs you are running - simple i know but for some they wont know.

2 - By default the ASP wasn't available under ISAPI and CGI Restrictions area and has to be added as an option.

Lastly - Server 2012 has slightly different format for getting to things so number 14 - server 2012 has no start menu by default. Am installing classicshell to give me back my startmenu.

Shane Hollis (September 26, 2014 at 5:02 PM)
I followed these steps and get a configuration error with I try to access the site.

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive.

Version Information: Microsoft .NET Framework Version:2.0.50727.5485; ASP.NET Version:2.0.50727.5483

Andrew Bartle (February 23, 2015 at 7:15 PM)
Any guidance on how not to use the "NetworkService" account for the app pool? I'd prefer to follow a least privileges approach and create an account that only has the minimum rights on the box to enable the IIS webmail site.
Douglas White (March 12, 2015 at 8:29 AM)
Hi Dough,

You can create a new account of SmarterMail and make sure that account has full control over the MRS, Service folder under default path of c:\Program files (x86)\SmarterTools\SmarterMail and full control over the SmarterMail folder under the default path of C:\SmarterMail. Then after you apply the permissions run the self diagnostic to make sure all permission pass.

Brian Ward (March 12, 2015 at 8:41 AM)
Hoping for a quick fix; I purchased and setup SmarterMail on Server 2008. Working fine with built in web server. When I followed these instructions and moved it to IIS 7.5, I get an error message when trying to browse the site. It tells me "Server Error in '/' Application
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.

Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".

<!-- Web.Config Configuration File -->

<customErrors mode="RemoteOnly"/>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<customErrors mode="On" defaultRedirect="mycustompage.htm"/>

Any help would be greatly appreciated!

David Short (April 1, 2015 at 10:45 AM)
Hi David! Comments on a KB article are generally used to report additional steps that could be included, typos/misspellings or helpfulness of the article. For troubleshooting technical issues, I'd recommend posting in the SmarterTools Community by using the Community tab above or submitting a ticket to our technical support team. Please keep in mind when submitting a support ticket, if the issue is caused by a bug in the system, your ticket will be refunded.
Andrea Rogers (April 2, 2015 at 9:31 AM)
If you require someone to install it on IIS for you please contact we will install it for free.
dextor stone (June 19, 2015 at 7:23 PM)