OK, I have made the move to the .Net version from Pro. Everything basically runs, except there is no info on how to configure the web interface. I am already running IIS for my web sites.

In the pro version I had the port mapped to 2525, so users could go to thier own domain:2525 and get the login prompt. Now this no longer exists. I have the webmail interface set up on the Default web site, but this does not help if each web site can no longer access it directly without going to the "default web site". So as a work around until I can get some help on how to set this up, I had to create a "Virtual Directory" on each web site and point it to the default web site. I hope this is not the only option since I will have to do this every time I set up a new site.

Also, where (specifically) are the files for editing the webmail pages. I know some are in the \Auth directory, but I can not find all of them (especially the log in page). Is there a list of the files somewhere? I used to use the Outlook Clone that I download from this site. Is there anything like that for the .Net version?

Thanks.

The .NET web interface runs on port 80, or what ever port you have IIS listening to.  Here is what I did:

1. I created a new web site in IIS.  I set the Host Headers to the domains that I wanted to use webmail for.  By doing it this way, I have one install of the web interface that can service several domains.

2. I ran the install program for the web interface and instead of selecting the "Default Web Site" I selected the newly created site. (I named it ArGomail).

3. I placed a default.aspx file in the root of the web site.  The contents of this file will redirect the user to the \webmail folder where the web interface resides.  So if a user types webmail.mysite.com it will redirect them to webmail.mysite.com/webmail.   I will attach my default.aspx to this message. It is Zipped up so not to cause any issues with the web site.

Notes:  When creating the folder for the new site, make sure that IUser_[Computer Name] Account and Network Service account have "Read & Execute", "List Folder Contents" and "Read Permissions".  I throw the Administrator account with Full Control.  In IIS on the Home Directory Tab, click the "Create" Button to create a new application. In the Execute Permission drop down, set this to "Script Only".  For application pool, you can use the default, or create your own application pool.

For me, as a rule of thumb, I never use the default web site for anything, for security purposes. As a matter of fact that site is disabled on my server.

 Currently there are no theme packs like there were for the pro version.  The interface uses "Themes" so you can customize it.  Information on Themes can be found here at http://www.argosoft.com/rootpages/M...hemes.aspx

I have not yet had the time to play around with the themes yet, so I do not know how easy/hard it is to customize.