1. Web Components
1.1. How-To: Customize the Quarantine Report Template

Product: All

Version & Build: All


Note: The following instructions apply to both modusGate and modusMail programs. 
 

1.  Locate the appropriate root installation folder for your modus package: 

      

e.g. for modusGate - C:\Program Files\Vircom\modusGate

       e.g. for modusMail - C:\Program Files\Vircom\modusMail


2.  Go to modus [Gate or Mail]\Templates\Quarantine\Default\Theme


3.  Inside the Theme folder, make a copy of the Default subfolder and rename the copy with your custom theme name, e.g, “Company.” 
NOTE: If you plan to customize the report for multiple domains, make as many copies of the Theme folder as needed, and rename each one according to the respective company or domain name. The following steps will have to be repeated for each new Theme folder.


4.  Next, open the Company\Images folder: here you will find the images used for the Quarantine Report template


5.  To change the CompanyLogo.gif image, simply replace the .gif file with your own. Make sure this file is stored in the new Company\Images directory.
  
      NOTE: All images in this directory can be replaced, but the original file sizes must be respected.


6.  Next, locate the Theme.xml file within the Quarantine\Default\Theme\Company folder  


7.  Open the Theme.xml file and modify the following entries, where applicable:


<Category id="15">Forbidden.gif</Category>
<Category id="14">MimeParseError.gif</Category>
<Category id="13">Corrupted.gif</Category>
<Category id="32">Custom.gif</Category>
<Category id="33">Phishing.gif</Category>
<Category id="34">Adult.gif</Category>
<Category id="35">Patterns.gif</Category>
<Category id="36">Money.gif</Category>
<Category id="37">Goods.gif</Category>
<Category id="38">Health.gif</Category>
<Category id="40">Blacklist.gif</Category>
<Category id="41">Miscellaneous.gif</Category>
<Category id="42">SpamLink.gif</Category>
<Category id="44">Foreign.gif</Category>
</Categories>
<CompanyLogo>Image.gif</CompanyLogo>
<FooterLogo>LogoCompanyFooter.gif</FooterLogo>
<Border1>border1.gif</Border1>
<headergradient>header.gif</headergradient>
<lessattentiongradient>lessattention.gif</lessattentiongradient>
<attentiongradient>attention.gif</attentiongradient>


8.  Finally, go to the Quarantine folder, right-click and select Properties > Security tab, click Advanced, then click Edit, enable “Replace all existing inheritable permissions on all descendants with inheritable permissions from this object,” and click Apply.  (In other words, propagate all existing permissions on the Quarantine folder to all of its subfolders.)

1.2. Info: Modus v4.4.543 Message Audit Log

 

Product: All

Version & Build: 4.4.543 and up

 

In an effort to facilitate the use of the Message Audit Log in the WebMonitor application, Vircom has created a document that explains its functions and the steps required to configure the it.

The Message Audit Log can be used to: 

·         Provide Administrators with an overview of how messages are being processed

·         Provide a consolidated message history in one feature

·         Help Administrators easily track errant messages – Were they delivered?  Who were the recipients/senders?

·         Help Administrators enforce corporate email policies by monitoring mail

 

 

1.3. Info: Configuring Norton Internet Security for Webmail Access

 

Product: ModusMail

Version & Build: All

 

Please see the attached document for instructions for configuring Norton Internet Security to allow for Webmail access.


Thanks to Kim Atwater for providing this information!
 
1.4. How-To: Convert WebMail POP Servers to IMAP (v4.3+)
 
 

Product: ModusMail

Version & Build: 4.3 and above

 

Please read the attached User Guide for configuration information and detailed instructions for using the pop2imap.exe utility.  Note that this utility can only be used with ModusMail version 4.3 and above.  If you are running an earlier build, please upgrade first.

Should have any questions or problems with the instructions or the utility itself, please contact our Support Department by email at support@vircom.com or, by phone, at: (514) 845-8474.
 
1.5. How-To: Customize the Date Displayed in Webmail / WebQuarantine


 

Product: All

Version & Build: 4.3

 

There are three different date formats used in WebMail / WebQuarantine, depending on the age of the message:

1. Messages that arrive on the current day show only the time
2. Messages that arrived during the current year show the month and day
3. Older messages dating back to previous years show the month, day and year

To change the format:

  • Go to the ...\Vircom\Web\Web<Mail or Quarantine>\WebRoot\Locales folder and open the folder of the language you want to change (e.g. Locales\en)
  • With Notepad, open the strings.xml file and search for DateToday
  • You will see the following lines:

  <DateToday>t</DateToday>
  <DateThisYear>MMM dd</DateThisYear>
  <DatePastYear>d</DatePastYear>

  • Change the value between the > and < characters to what is to be displayed for each of the time stamps

The following tables provide examples of different date displays based on the English language.  ** The order of the date and the separator may change depending on the language.

 Character  Format  Example
 d  M/d/yyyy    1/1/2006
 g  M/d/yyyy h:mm  1/1/2006 12:00 AM
 t  h:mm  12:00 AM

You can also combine the following characters to represent certain parts of the date:

 Character  Format  Example

 d 

 day of the month  1
 dd      day of the month (2 digits)  01
 ddd    abbreviated day of the week    Sun
 dddd    full weekday  name     Sunday
 M       month of the year   1
 MM      month of the year (2 digits)  01
 MMM      abbreviated month of the year  Jan
 MMMM    the full month  name      January
 yy   year without century    06
 yyyy       year with century  2006
 h           the hour in 12-hour clock  2
 hh      the hour in 12-hour clock (2 digits)  02
 H    the hour in 24-hour clock    0 
 HH    the hour in 24-hour clock (2 digits)   00
 mm       the minutes (2 digits)  00
 ss       the seconds (2 digits)  00 
 tt       AM/PM designator  AM


Example of a character combination:

 Combined characters  Result
 dddd   Sunday
 dddd h:mm  Sunday 12:00 
 MMM dd  Jan 01

 

1.6. Info: Diagnostic Utility for WebMail / WebQuarantine


 

Product: All

Version & Build: 4.1.361 & up

 

 

Versions 4.1.361 and above of the WebMail / Web Quarantine User Interface provide a diagnostic tool to help troubleshoot configuration or connectivity errors.  Please note that this utility can only be used with the 4.x version of the UI

From the machine where the Modus Web Components are installed, you can access a diagnostic page that will provide the current state of your setup and give you information about any errors in your configuration.

  1. Logon to the machine where the Web components are installed
  2. InURL field, replace login.aspx with diagnostic.aspx, e.g. http://www.mydomain.com/webmail/diagnostic.aspx
  • If you are unable to login, type in your <webmail or webquarantine URL>/diagnostic.aspx
    • The system will display the diagnostic page but will not provide as much detail about your setup
 
The system displays the diagnostic page:

 

1.7. How-To: Configure the Web Components for ModusGate

 

Product: ModusGate

Version & Build: 4.1.361 & up

 

Background:

This how-to is designed to aid you with:

a) Manual configuration of the web components

or

b) a two server configuration with ModusGate on one machine and the Web components on a separate machine

 
Installation Requirements:

Both IIS and .NET framework version 1.1 must be installed on the server hosting the Web components before the following configuration can be completed. 

NOTE: Version 1.0 of the .NET framework is no longer compatible with our code and should be uninstalled prior to installing the v1.1.

If using Windows Server 2003, please see How-To: Configure Windows 2003 for Web Components before continuing to ensure that the .NET framework has been properly configured on the server.


Manual Configuration of Web Sites:

The following folder structure will automatically be created upon installation of the Web components:

 

WebQuarantine Site Configuration in IIS: Windows 2000 & 2003

  • Open IIS
  • Expand the machine name
  • Right-click Default Web Site and select New > Virtual Directory
  • Alternatively, you could create a new real site
  • Use the wizard & enter the name to be used for the WebQuarantine directory and the directory path:
    • If using the 3.x user interface, the path must point to the location of the Quarantine folder, e.g. ...\Vircom\Web\Quarantine
    • If using the 4.x, the path must point to ...\Web\Quarantine\WebSite 
  • Keep the default settings for the remainder of the wizard panels
  • After the site name is created, right-click on it and select Properties > Configuration
  • Click on App Options (Windows 2000 Server) or Options (Windows Server 2003) and make sure that  Enable parent paths is checked. 
  • Click on Directory Security 
  • Click on Anonymous Access & Authentication Control > Edit and make sure that Integrated Windows Authentication is enabled

 

WebAdmin Site Configuration

Follow the same procedures as above but the directory path will point to the WebAdmin\Root folder, e.g. ...\Vircom\Web\WebAdmin\Root.  Verify that Enable parent paths is checked along with Integrated Windows Authentication.

 

WebMonitor Site Configuration

Follow the above procedure.  The Directory path will point to the WebMonitor folder, e.g. ...\Vircom\Web\Monitor.  Verify that Enable parent paths is checked along with Integrated Windows Authentication.

 

Verify the Configuration Files

Web Quarantine: Webmailsvr.ini configuration file

Locate the webmailsvr.ini file in the ...\Web\Quarantine directory and open it with a text editor.  All connection information is entered automatically during the installation phase>  However, you may need to change some of the entries:

  • The host address must be the first static IP address of the ModusGate server or the first static IP address of the Web server if the web components are installed on a separate machine from ModusGate  
  • The TypeMainInbox will always display MODUSGATE
  • The POP3Server, Imap4Server and SmtpServer addresses all default to the loopback: 127.0.0.1.  These settings do not need to be changed.  The actual IP address used will be that of the ModusGateServer address (below)
  • The DomainName defaults to the Gate server's FQDN name, e.g. machine1.mycompany.com.  It is recommended that you change it to display the actual domain name used in your email addresses, such as mycompany.com.
  • The ModusGateServer address should also display the first static IP address of the ModusGate server or the first static IP of the Web server if the web components are installed on a separate machine from ModusGate 
  • The WebAdminURL path will be "/WebAdmin/" if created as a virtual directory of the Default Web Site, otherwise enter its full URL path.

If any of the above settings must be changed, save the file and stop/restart the Webmail Server Service

  • if everything is installed on one server, you can stop/start the WEBMAILSVR service from the ModusGate administration console
  • if the web components are installed on a separate Web server, the services must be stopped/started using the Windows > Administration Tools > Services panel

NOTE: The connection information in this file is used by both the 3.x and 4.x WebQuarantine interfaces.  If you are using the 4.x UI, see the WebMonitor: WebSite\Custom.config section below for further config info.

 

WebAdmin: Web.config file

Locate the web.config file in the ...\WebAdmin\Root folder.  The site value ( in <add key="Site" value="" />) will be blank, by default, because it assumes that the localhost address will be used.  However, if there are multiple NICs on the ModusGate or Web server, enter the first static IP address to avoid communication problems. 

The Site Directory value of "/WebAdmin"/ (<add key="Site Directory" value="/WebAdmin"/>)applies if it had been created as a virtual directory under the Default Web Site.  If your IIS setup is different, enter the full URL path here.

If any changes are made to this file, stop and start both the WEBMAILSVR service (in the Console) and IISAdmin (run the iisreset command from a command prompt).

 

WebMonitor: WebSite\Custom.config file

The connection information required for the WebMonitor program is located in the Custom.config file, located in ...Web\Quarantine\WebSite. 

If you have multiple NICs on the ModusGate or Web server, replace "localhost" with the first static IP address for the following values: 

  • Site
  • WebMailServerAddress
  • MonitoringServerAddress

Make sure that the Temp and LogDir values point to the correct location of these files within the Web directory.

NOTES:

  1. The custom.config file is used by the 4.x Web Quarantine UI for the MonitoringServerAddress, Temp and LogDir values
  2. If the web components are installed on a separate Web server, the MonitoringServerAddress must point to the first static IP address of the ModusGate server
  3. If any changes are made to this file, stop and start the WEBMAILSVR service (in the Console) and IISAdmin (run the iisreset command from a command prompt)

 

File & Folder Permissions:

The machine's IUSR and ASP.NET accounts must be given Modify rights on the Web Components (replace the ASP.NET account with the Network Service account in Windows 2003), e.g. ...\Vircom\Web.

 

Authentication Request Settings in the ModusGate Console

In order for end users to log into the WebQuarantine program, they must be authenticated against the mail server or authentication server (such as LDAP or Active Directory) to ensure they have a valid email account on the system. 
 
To configure the Web authentication connection, in the ModusGate Console, go to Connections - Properties - General.  Highlight the route and verify or create the configuration for Authentication requests.  This setting is used for all Web component logins (WebQuarantine, WebAdmin and WebMonitor).  Select the authentication method supported by the mail/authentication server, e.g. SMTP_Auth, Exchange 2000+, etc.  The port number appears automatically but can be changed to comply with the network configuration.

The Web component logins require the full email address.  If your mail server/authentication server does not support this type of login, select Strip domain name for authentication requests.  Users will still be required to enter the full email address at the web login screens but only the username portion of the address will be passed to the mail server/authentication server.

 

Testing the WebQuarantine Site:

1. Try accessing the WebQuarantine login screen using either of the following methods:

  • Right-click the site name in IIS and select browse
  • Open a browser window and enter http://localhost/webquarantine or http:// [Gate server's IP]/webquarantine<enter the site name created in IIS>

2. Log in using your email address

Follow the same procedure above to access the WebAdmin and WebMonitor sites.

 

Troubleshooting

If using an SMTP_Auth authentication method in the ModusGate Console, it must be supported and enabled on both the mail server and the firewall (if there is a firewall between the ModusGate and mail servers).  On the firewall, the extended authentication requests (e.g. EHLO) must be allowed.

If SMTP_Auth does not work, try using a POP connection instead, if the mail server supports it.

If using Exchange 2000+ authentication, try using the Global Catalog Port 3268 instead of LDAP's Post 389.

 

1.8. How-To: Configure the Web Settings in the Modus Console


 

Product: All

Version & Build: All

 

Modus Console Configuration

A default install will automatically enter all of the necessary file path information for WebMail/WebQuarantine in the Console but, if you run a manual setup or change any configuration information in the Web configuration files, then you should verify that these changes are reflected in the Console.

Conversely, any file path info (such as the location of the WebMail or WebQuarantine Users directory) can be changed in the Console and these changes will be updated in the Web configuration files.

NOTE: any configuration changes will require a stop/start of the WEBMAILSVR service in the Console to take effect.

 

The following information outlines the various configuration settings for the Web components:

System - Properties - Services, WEBMAILSVR Service

This service can be stopped and started from this panel only when WebMail/WebQuarantine is installed and running on the same machine as ModusMail or ModusGate.  The Settings button will display the local machine name.

When WebMail/WebQuarantine is installed on a machine separate from that Modus, the service will appear to be stopped in the Console.  This is normal as the service is running on a different machine.  Also, the Settings button is not operational in this case.  You cannot enter the remote server name and be able to control the service remotely.

The service can be stopped and started on the Web server in Windows > Administrative Tools > Services: look for ModusMail WebMail Server.

The service can also be controlled in either situation using DOS commands from a command prompt: net stop webmailsvr and net start webmailsvr. 

 

Web - WebAdmin - Privileges

Options available under Allowed User types, Allowed List types (ModusMail only), Allowed operations (ModusMail only), Allowed Domain properties and Allowed User properties (Administrators drop-down list only) let you control what settings your system and/or domain administrators are able to change via the WebAdmin program.

The Normal Users list within Allowed User properties lets you control what settings end users are able to change via the WebMail/WebQuarantine Settings options.

Note that not all items listed in the Allowed User types and Allowed List types are functional in WebAdmin. You cannot remotely add an NT mailbox or NT mailing list to the system as this information must be pulled from the domain controller.  The user/group must be added to the DC first before the properties can be changed via WebAdmin.

Similarly, you may not be able to remotely add database mailboxes or lists unless you specifically create web access with "write" capabilities to your database.  Otherwise, new users/lists must be created directly in the database and then the properties can be changed via the WebAdmin.

To give an account administrative rights to WebAdmin, please see Creating Server and/or Domain Administrative Accounts for WebAdmin below.

 

Web - WebMail - Options

Verify that the correct full path to the Users directory is entered in the Web Users directory box, e.g. ...\Vircom\Web\WebMail\Users 

  • If this directory was not created automatically, create it manually and enter the full path in this window
  • NOTE: this Users directory is meant to be separate from the ModusMail\Mailbox directory and contents.  This setup allows users to see temporary copies of their messages through WebMail access yet still be able to see and download the same messages via a standard email client (such as Outlook or Netscape).
  • In ModusGate, the Users directory provides access to the WebQuarantine - users are able to see and control their quarantine contents and scan settings (if permitted).  It does not provide full email capabilities such as sending or receiving messages.

 

Verify the WebAdmin URL 

  • If you did not use a default setup, you must specify the full URL path here, e.g. http://<your website>/webadmin/ 
  • NOTE that the path must end with "/"

 

Protocol Settings: Select the type of mailbox access: POP3 or IMAP (ModusMail only)

  • Be sure to select the option that will be used by the majority of your users
  • Keep in mind that the POP3 option has the look and feel of IMAP (e.g., it allows folder creation; deleting messages involves delete & purge with a strikethrough appearance, etc.) but it only allows for a single connection to the server and cannot be synchronized with a standard email client, such as Outlook or Netscape.  If users want the ability to synchronize folders and their contents with another mail client, select IMAP.

WARNING:  Keep in mind that converting POP3 access to IMAP or vice versa is not an easy process and runs the risk of possibly lossing data.  Therefore, select one type and stick to it!  Also, it is not possible to select POP access for some and IMAP access for others - there can be only 1 access type for all users.

 

Settings: Strip domain from login

  • Select this option if you are using WebMail or WebQuarantine with a mail server that does not support the full email address as the login.  This option can also be configured on a per-domain basis in Domain - WebMail - General.
  • NOTE: When strip domain is enabled, users are still required to enter their full email address when logging in but the program will only forward the "username" portion of the address to the authentication server
  • In ModusMail: when users belong to the default or primary domain, they are not required to enter the full email address when logging into WebMail.  It is only required when they belong to the non-default domain.

 

Settings: Show Quarantine folder

To hide or disable access to the quarantine folder and contents, disable this function (it is enabled by default) and stop/start the WEBMAILSVR service.

This option is available on a per-domain basis in Domain - WebMail - General.

 

Web - WebMail - Advanced

Encoding:

This setting allows you to change the on-screen language of the WebMail program from English (the default) to the language of your choice.  Select the appropriate language code from the drop-down menu, click on Apply and stop/start the WEBMAILSVR service for the change to take effect. 

 

Quota Settings:

The settings listed here are applicable to WebMail/WebQuarantine only and do not affect the actual mailbox sizes or functions in ModusMail. 

The Visual Settings (Max. Contacts i.e. address book contact list and Max. Messages i.e.Inbox message list) are set to 99 by default in ModusMail v4.1+.  End users can set their own Inbox message limits in WebMail via Settings > Options, Number of messages displayed per page.

WARNING:  Any mailbox quota limits, auto-cleanup functions, etc. that you may set in ModusMail do not apply to the WebMail folders.  For example, if a mailbox expires in ModusMail (either because a mailbox lifetime was set under Quotas or you are using the Automatically delete not found mailboxes setting in Auth), the corresponding user's folder in the WebMail\Users directory will not be automatically removed - it must be deleted manually.

 

Creating Server and/or Domain Administrative Accounts for WebAdmin

You can configure an account to allow for administrative rights to all domains (the equivalent of a Server Administrator) or rights to a specific domain (Domain Administrator) by doing the following:

  • Go to Domain - WebAdmin - Administrators and select a domain
  • Click on Add and use the drop-down menu to select the user(s) for which to assign administrator rights
  • Click on Apply
  • Go to Users - WebAdmin - Administrators 
  • There are two options options to set the account(s): a member of All Domains (Server Admin) or These Domains only (Domain Admin)
  • If you want 1 account to have access to more than one domain but not all, click Add and select the domain names from the drop-down menu
    • Note: multiple selections are not permitted

 

1.9. How-To: Configure Webmail for Blockade

 

Product: All

Version & Build: 4.2 & up

 
 
Background:
 
If you attempt to use a conventional installation of WebMail in a cluster or blockade configuration (i.e.,stand-alone copies per machine but the WebMail Users folder is shared), there is a problem when users close their sessions improperly, such as not logging off and then trying to log in again using WebMail on another member of the blockade.
 
WebMail can work in a blockade but the WEBMAILSVR service does not work well in a cluster setup.  You must, therefore, configure one instance of the WebMail service to act as coordinator for your two nodes.  The trick is to get WebMail installed on NODE 2 to use the WEBMAILSVR service on NODE 1 for user validation and coordination.
 
 
Configuration on NODE 2:
 
a) Modify the webmailsvr.ini file on NODE 2 to point to the WEBMAILSVR Service on NODE 1:
  • Go to the root Modus folder \ Web subfolder
  • Copy webmailsvr.ini to webmailsvr.bkp (make a backup)
  • Edit webmailsvr.ini with Notepad and change the RPC Server configuration so that the host=x.x.x.x value points to the IP address on NODE 1
 
b) Modify the custom.config file on NODE 2 to point to NODE 1
  • Go the the root Modus folder \ Web subfolder
  • Go to the Webroot subfolder
  • Copy custom.config to custom.config.bkp
  • Edit the custom.config file with the following changes:
Change this line:
<add key="WebMailServerAddress" value="localhost"></add>

To this line:
<add key="WebMailServerAddress" value="x.x.x.x"></add>
 
Where x.x.x.x is the IP address of NODE 1
  • STOP and START WEBMAILSVR and do an IISRESET on NODE 1
  • STOP and START WEBMAILSVR and do an IISRESET on NODE 2
 
 This will eliminate conflicting sessions.
 
1.10. How-To: Configure WebMail for Multiple Mail Servers and/or Domains


  

Product: All

Version & Build: 4.0 & above

 

WebMail supports MISP or multiple mail server configurations and multiple domain configurations where the connections are different from the default domain.

Background Information:

The main connection information is located in the WebMailSvr.ini file. Depending on your directory structure, this file may be located in the root directory of: Web\Webmail or MWMServer or VMWServer.

 

Multiple mail server (MISP) or multiple domain configuration:

1. Locate the WebMailSvr.ini file and open it with a text editor

2. Scroll to the bottom of the file.  Underneath the [Conversion] section, create the following section name:

[DomainName:Settings]

3. Enter the required configuration using the following syntax, e.g.:

[DomainName:Settings]

ConvertState=0

[xyz.com:Settings]

DomainName=xyz.com

Pop3Server=10.10.10.10 *

Pop3Port=110 *

SmtpServer=10.10.10.10

SmtpPort=25

QuarantineEnabled=0

[klm.com:Settings]

DomainName=klm.com

Pop3Server=12.12.12.12 *

Pop3Port=110 *

SmtpServer=12.12.12.12

SmtpPort=25

QuarantineEnabled=0

* Substitute the IMAP server IP address and port number (143) if using an IMAP connection instead of POP3.

NOTE: When using a MISP or multiple server setup, the Quarantine is not accessible.  Therefore, you must enter QuarantineEnabled=0: the accounts must be local to the ModusMail server in order for these functions to work.  When using a multiple domain configuration, the Quarantine is functional since the accounts are local to ModusMail and this step is not required.

 

1.11. How-To: Configure Windows 2003 for Web Components

 

Product: All

Version & Build: All

 

To run the Modus Web components on a Windows Server 2003, you must have the following configuration:
 

1. Ensure that you have .NET framework version 1.1 installed on the server

NOTE: .NET version 1.0 is no longer compatible with our code.  If you have both versions 1.0 and 1.1 installed on the server and are getting ASP.NET errors with our web applications, see the Troubleshooting section below.

If you have version 1.0 installed, it is recommended to uninstall it prior to installing 1.1 in order to avoid problems.

 

2. Verify that the ASP.NET component is activated on the server

  • Go to Control Panel > Add/Remove Programs > Add/Remove Windows Components > Application Server
  • Click on Details and select ASP.NET (if not checked)
  • Click OK and Next to install the component

 

3. Verify that Active Server Pages and ASP.NET are "allowed" in IIS

  • Right-click MyComputer > Manage > Services and Applications > Internet Information Services
  • Expand the directory tree and select Web Service Extensions
  • Make sure that Active Server Pages and ASP.NET are set to Allowed

 

4. Verify the properties of WebMail/WebQuarantine, WebMonitor and WebAdmin directories in IIS

  • In IIS, open the properties of Virtual Directory or Home Directory > Configuration > Options
  • Make sure that Enable Parent Paths is checked
  • Go to the Directory Security > Anonymous Access & Authentication control > Edit and make sure that Integrated Windows Authentication is checked

 

5. Permissions

Modify permissions must be given to the local machine's IUSR and Network Service accounts on:

  • The root Web folder, e.g., C:\Program Files\Vircom\Web

or 

  • The individual WebMail / WebQuarantine and WebAdmin folders, e.g. ModusMail: C:\Program Files\Vircom\Web\Webmail and ...\Web\WebAdmin; ModusGate: C:\Program Files\Vircom\Web\Quarantine and ...\Web\WebAdmin.

Also add Read & Execute, List Folder Contents, and Read permissions to the root ModusMail or ModusGate directory for the IUSR and Network Service accounts, e.g. C:\Program Files\Vircom\ModusMail or ModusGate.

IMPORTANT: Be sure to propagate all above-listed changes to the child files & folders

NOTE: If using an Access database for mailbox authentication, give IUSR and Network Service accounts Modify permissions on the .mdb file

 

Troubleshooting:

If the web components had been installed prior to installing or upgrading to .NET framework 1.1, run the following command from a DOS prompt: aspnet_regiis -I.  This will try to bind all aspx code to the new .NET framework.

If this step does not work:

  • Uninstall both .NET framework versions (1.0 and 1.1)
  • Reinstall .NET 1.1 and reboot
  • Reinstall the Modus Web components (no need to install the mail portion)
If none of the above steps work, contact Support at support@vircom.com or 514-845-8474.
 
1.12. How-To: Display the Paper Clip Icon

 

Product: ModusMail

Version & Build: 4.1.361 and above


Webmail Attachments Icon Display

By default, the web interface is not set to display an attachment paperclip icon for messages that have attachments because there COULD be a performance issue.  To be able to perform the check for attachments in a message, the whole message has to be transferred between the Mail Server and the WebMail Server and then to the IIS server.  If they are on the same computer, this should be fast but  if they are not, there could be a slowdown when loading the message list in your Inbox. 

To enable display of the attachment paperclip, proceed with the following steps:

 

  1. Open the custom.xml file in the ...\Themes\Vircom directory
  2. Add the following line between the existing <Theme> and </Theme> tags:

    <vircommessagelist UseServerAttachment="False"></vircommessagelist>

 

  1. Perform an IISReset (from a Command Prompt) to enable this change

 

1.13. Problem: Invalid Class String Errors with WebAdmin or LiveMonitor

 

Product: All

Version & Build: All

 

Description of the Problem:

When attempting to log into WebAdmin and/or LiveMonitor or when trying to access the Settings options within WebMail or WebQuarantine, following error occurs:

Source : /WebAdmin/Login.aspx
Exeption Description Stack :
Invalid class string

call Stack :
   at LicObjActivatorLib.ActivatorClass.CreateLicensedInstance(String strProgID, String strKey)
   at Vircom.modusWebAdmin.VMAHelper.Server.GetServer()
   at Vircom.modusWebAdmin.UserControls.Login.CustomValidatorLogin_ServerValidate(Object source, ServerValidateEventArgs args)
   at System.Web.UI.WebControls.CustomValidator.OnServerValidate(String value)
   at System.Web.UI.WebControls.CustomValidator.EvaluateIsValid()
   at System.Web.UI.WebControls.BaseValidator.Validate()
   at Vircom.modusWebAdmin.UserControls.Login.ButtonSubmit_Click(Object sender, EventArgs e)
   at Vircom.modusWebAdmin.UserControls.Login.Page_Load(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain()

 

Solutions:

Windows 2000 Server:

This type of error, if accompanied by the lines "Server object error xxx, Server.CreateObject Failed", can occur if one of the program's components was not properly registered during the installation. There are 2 ways to fix it:

a) Manually register the specified component's dll file:

    • Make sure the dll is present on the server
    • Register at a Command Prompt:  go to the directory of the dll and use the regsvr32 command followed by the name of the dll file
      • E.g. if the "Server object error" quotes the aspupload.dll file, go to the directory containing that dll and type: regsvr32 aspupload.dll

b) Reinstall the component

 

Windows Server 2003:

The class string errors can point to problems with permissions settings in the registry.  To correct it, please follow the instructions outlined in this Microsoft Knowledge Base article: http://support.microsoft.com/kb/313222/

 

1.14. How-To: Configure and Troubleshoot Modus Web 4.x Components


Product:
ModusMail & ModusGate
Version & Build: Version 4.2
 
 

Background information:

Over the course of Modus' development, we have provided 3 different user interfaces for the WebMail / WebQuarantine programs. This how-to describes the most recent, Version 4.2.

NOTE: A diagnostic utility is available to help determine any connectivity or configuration problems. Before reading further, please see the Diagnostic Utility for WebMail/WebQuarantine to help pinpoint any errors you may have, then refer to the appropriate section below for configuration details.

Folder Structure:

To access the configuration files described below, locate the directory entitled Webroot. In a default installation, it can be found in C:\Program Files\Vircom\Web\Webmail\Webroot (machines upgraded from older builds may find it in the VMWServer or MWMServer directory).

 

The main configuration information is contained in a file called webmailsvr.ini, located in Web\Webmail.  This file is used by both old and new UI versions.  This is where you specify the IPs used for the SMTP, POP and IMAP connections.  Below is a breakdown of the required configuration information.

 

Configuration 1: Modus and Web components installed on 1 server  

 

WebMail & Quarantine: Webmailsvr.ini configuration

[RPC:Settings]

The Host address must be the IP of the server where Webmail or Quarantine is installed and running.

 

[Default:Settings]

The POP3Server, IMAP4Server and SmtpServer fields must all display either the static IP of the mail server or the loopback address, 127.0.0.1 

1) The address entered in the SmtpServer field must be added to the security settings in the ModusMail admin console: Security / Mail Relay / Accept mail for relay from these hosts.

2) The loopback can only be used for the SMTP, POP & IMAP values if Webmail is installed on the same server as ModusMail.  If Webmail is on a separate server, you must enter the mail server's IP instead (either internal or public IPs can be used). 

In ModusGate: the IP for SmtpServer, POP3Server and IMAP4Server will always be the loopback address, 127.0.0.1.  The ModusGateServer value is used instead, and must display the actual IP of ModusGate.

 

DomainName: this must match the default domain name as displayed in the ModusMail configuration console, i.e. the first domain name in the list.  Example, if the primary domain is abc.com in Modus, enter that information here; if it is mail.abc.com (i.e. the machine name is included), then use that same format here.

In ModusGate: The default entry is in machine.domain.com name format.  Delete the machine name and ensure that the domain used in the actual email address is displayed, e.g. mycompany.com.

 

BasePath: this must contain the full path to the Users subfolder within WebMail or Web Quarantine, e.g. C:\Vircom\Web\WebMail\Users.

 

NumSpellChecker: The spellcheck function became unreliable in Modus 3.x because of changes made to Microsoft's Word.  It's recommended to change the value to 0 (off) to prevent a build-up of errors in the Windows Event Viewer.

The new Webmail UI in versions 4.0 and 4.1 has its own spell-check function built in and no longer relies on Microsoft; it also no longer requires the use of the NumSpellChecker line in this file.

 

WebAdminURL: A default install will auto-create a virtual directory called WebAdmin under the Default Web Site in IIS. Therefore the path here can be simply /webadmin/ - note that the path must end with a forward slash.

If WebAdmin was created under a different site, enter the full URL path here, e.g.:

http://www.mydomain.com/webadmin/

 

QuarantineEnabled: The value =1 to display the quarantine tab; value =0 to hide it.

 

NOTE: In brand new installs, this value does not appear as the quarantine is enabled for all users by default. If you wish to prevent users from seeing their quarantine contents, either create the entry manually with the desired value, or control it from the Modus admin console: Web > Webmail: disable "Show Quarantine Folder" > Apply. After making the change, stop/restart the Webmail Server Service.

It can also be configured on a per domain basis in the Modus admin console > domain properties > WebMail tab.

 

[DomainName:Settings]

This is where to configure the connections for other domains or mail servers, where the connection info is different from the default domain.  For example, if you have a single webmail website that all local users log into: all domains use the settings under the [Default:Settings] section, even if each domain has its own IP.

If you have domains that require different settings from the Defaults, or if you want to allow WebMail access to multiple mail servers, create a section called [DomainName:Settings] and enter the required configuration using the following syntax, e.g.:

[DomainName:Settings]

ConvertState=0

[xyz.com:Settings]

DomainName=xyz.com

Pop3Server=10.10.10.10

Pop3Port=110

SmtpServer=10.10.10.10

SmtpPort=25

QuarantineEnabled=0

 

WebAdmin Configuration

Go to the Web \ WebAdmin \ Root folder in Windows Explorer and open the file called Web.config: <appSettings> section:

 

Site value: the default value will be blank. If there are any problems accessing this program, enter either 127.0.0.1 or the Mail server's IP between quotes (either internal or public IP). If the machine has more than 1 NIC card, use the 1st static IP; don't use 127.0.0.1.

 

WebMonitor Configuration

Go to the Web \ WebMonitor > web.config file: the default value will be: <add key="ModusServerAddress" value="127.0.0.1"></add>

If there are any problems accessing this program or the IP must be changed (such as when there are multiple NIC cards on the machine), copy the following lines from the Web.config file and paste them to Custom.config file and enter the new IP:

<add key="DefaultLanguage" value="en-US"></add>
<add key="DefaultTheme" value="Vircom"></add>
<add key="ModusServerAddress" value="127.0.0.1"></add>

 

Folder Permissions

On a Windows 2000 server, give Modify* permissions to the IUSR_machine and ASPNET accounts (often called aspnet_wp) on the folders listed below.  On a Windows 2003 machine, the permissions must instead be given to the IUSR_machine and Network Service accounts. Make sure the permissions are propagated to the child files and folders.

  • WebAdmin
  • WebMail (including server and client folders in older setups)
  • ModusMail
  • WebMonitor

* At a minimum, the above-named accounts must have Read & Execute, List and Read permissions on the above folders & contents, and Modify permissions on the Temp and Users directories within Web\Webmail or Web\Quarantine. 

 

IIS Site Configuration:

If you if you had an existing WebMail or Quarantine virtual directory, new sites are created under the names NewWebMail or NewQuarantine. You should therefore have the following sites:

  • WebMail (Mail): Local Path points to ...Web\Webmail\AspRoot
  • Quarantine (Gate): Local Path points to ...Web\Quarantine\AspRoot
  • NewWebMail (Mail): Local Path points to ...Web\Webmail\WebSite
  • NewQuarantine (Gate): Local Path points to ...Web\Quarantine\WebSite
  • WebAdmin (Mail & Gate): Local Path points to ...Web\WebAdmin\Root
  • WebMonitor (Mail & Gate): Local Path points to ...Web\WebMonitor

 

Custom settings

If you wish to change or customize any of the default settings for any of the web components, use the Custom.config files NOT the Web.config files.  Changes made to Custom.config will not be overwritten by subsequent upgrades, whereas any changes made to Web.config will be lost during an upgrade. 

For details about customization, see WebMail and WebQuarantine Interface Customization

 

Configuration 2:  WebMail and ModusMail installed on separate servers

To allow all components to talk to each other, you'll need to create pointers to the mail server after the install is complete:

 

WebAdmin:

Go to the Web \ WebAdmin \ Root folder in Windows Explorer and open the file called Web.config: <appSettings> section:

 

Site value: enter the Mail server's IP between quotes (either internal or public IP)

 

WebMail or Quarantine - webmailsvr.ini file:

Go to the Web\Webmail folder and open the webmailsvr.ini file: 

 

Host address: The Host address must be the IP of the machine where webmail is installed and running. 

 

POP3, IMAP4 and SMTPServer settings: enter the IP of the mail server

In ModusGate: the IP for SmtpServer, POP3Server and IMAP4Server will always be the loopback address, 127.0.0.1.  The ModusGateServer value is used instead, and must display the actual IP of ModusGate.

 

DomainName: this must match the default domain name as displayed in the ModusMail configuration console, i.e. the first domain name in the list.  Example, if the primary domain is abc.com in Modus, then enter that information here; if it's mail.abc.com (i.e. the machine name is included), then use that same format here.

For details about folder permissions, different domain settings, etc., see the information in Configuration 1.

 

Important Notes when WebMail / Quarantine is installed on a separate machine:

  • In the Modus Admin console > Services tab, the WebMail Server Service will appear to be disabled and the Settings button will not display a hostname or IP.  This is normal: the service is controlled on the other server where it's installed and running.
  • To stop and restart the WebMail Server Service, use the Windows > Admin Tools > Services panel.
  • The configuration options under Web / WebMail tab are not available in the console: these settings must be configured manually in the webmailsvr.ini file.

 

WebMonitor:

See the information in Configuration 1 above, but enter the ModusMail or ModusGate server's IP in the line: <add key="ModusServerAddress" value="127.0.0.1"></add>

 

Additional Configuration Information when using Database mailboxes:

Do you use database mailbox authentication?  If yes, create an ODBC connection between the web server and the database server, using a mirror of the ODBC configuration on the Modus server: same System DSN name, login and password.

 

Additional Configuration Information when using SQL quarantine:

Do you use SQL for the quarantine database?  If yes, create an ODBC connection to the database server, again mirroring the connection info on Modus: same System DSN name, login and password.

 

Configuration for Windows 2003

For more details about configuring a Windows 2003 server, see How-To: Configure Windows 2003 for web components

 

Installing the "old" UI

If you have a first-time installation of ModusMail or Gate, you will only have the new user interface that comes with 4.x.  If you wish to provide both the old and new UIs for browser compatibility or other reasons, see How-To: Install the "old" WebMail or WebQuarantine Interface

 

1.15. Archive: Web Info - Versions 4.0 & 4.1
1.15.1. Info: Web Configuration when upgrading to 4.x: ModusMail & ModusGate

 

Product: All

Version & Build: 4.0 & up

ModusMail:

If you're upgrading to Modus 4.x from a prior version**, there are some key changes in the webmail setup.  The "new" webmail contains a new user interface, but the core engine (e.g., the webmail server service, *.ini and other program files) still use the same architecture as the 3.x version of webmail. Thus, when you upgrade, the original web files are left intact, and any customizations you might have done to the AspRoot files are also left intact. You therefore have the option of using the old or new interface, or both: both versions can run concurrently! 

The new webmail interface is stored in a directory called "website".  Where the "website" directory is added depends on what version of the program was originally installed on the server:

If you originally had VOPMail: your folder structure will be VMWServer and VMWClient. The new Website directory is added to the VMWClient folder.

If you originally had pre-3.x Modus: your folder structure will be MWMServer and MWMClient. The new Website directory is added to the MWMClient directory.

If you originally had Modus 3.x: the folder structure is Web\Webmail.  The new Website directory is under Web \ Webmail \ Website. 

Note: If you're using modusGate, the above information still applies, but the 'old' directory is Quarantine. Therefore the Website directory is added to Quarantine.

Mail Server Connections:

Both the old and new webmail interfaces continue to use the mail server connection information stored in the webmailsvr.ini file (located in VMWServer, MWMServer or Web\Webmail directory, depending on your config). The settings should not have been changed during the upgrade, but verify them to ensure that the information is correct:

  • Host address = IP of server where webmail is installed and running
  • POP, IMAP and SMTP server = IP of mail server
  • DomainName = the primary or default domain as it appears in the Modus console, e.g. machine.domain.com, or just domain.com: the information here MUST be in the same format.

Also, verify the information contained in the vopmailweb.ini (located VMWClient, MWMClient or Web\Webmail):

  • Host address = IP of server where webmail is installed and running
  • TempDir = the full path to the Temp folder within the WebMail directory, e.g., C:\Vircom\Web\WebMail\Temp

IIS Configuration:

Your original webmail site in IIS is left intact and continues to point to the AspRoot directory in the Local Path.  If you had made any customizations to the AspRoot files, those are also kept intact (they're not replaced by the upgrade). Thus, the 'old' directory is left untouched and will continue to work.

A new virtual directory called 'newwebmail' is added under the Default Web Site when you select the "automatic" setup method.  If you had opted to set it up manually, then do the following:

  • Create a newwebmail virtual directory in IIS using the wizard, keep the default settings
  • Open the Properties, go to the Local Path box and browse to the location of the Website root directory.
  • Click the Configuration button > App Options or Options tab: make sure "Enable Parent Paths" is checked

Because of this dual structure, both the old and new webmail interfaces can be used at the same time.

ModusGate:

The 4.0 version of modusGate also includes the new user interface.  Similar to webmail, the original Quarantine interface is left intact, as are any customizations you may have done.  A new Website directory is added to your existing Web\Quarantine folder structure, and you have the choice of using the old interface, the new one, or both.

The 'old' folder structure is Web\Quarantine. The new structure becomes: Web\Quarantine\Website.

The connection information in the webmailsvr.ini and vopmailweb.ini files (located in Web\Quarantine) continue to be used by both the old and the new web interfaces, and any information in these files will be left intact by the upgrade.

IIS Configuration:

The 'old' directory in IIS is called Quarantine, and again that is left intact.  A new directory is added to the Default Web Site called newQuarantine.  Its Local Path directory will point to the Web\Quarantine\Website root directory.

Because of this dual structure, both the old and new webmail interfaces can be used at the same time.

**NOTE: If you're doing a "from scratch" install of 4.x, you will not have access to the "old" 3.x web interface because the code is not included. If you wish to install this version instead, please see How to install the old interface 

1.15.2. How-To: Change the default WebMail / WebQuarantine language in 4.0 & 4.1

Product: All

Version & Build: 4.0 & 4.1

By default, the WebQuarantine (ModusGate) and WebMail (ModusMail) interfaces are displayed in the English language. Once a user has selected a language and logged in, this set-up is saved locally in an Internet Explorer / Navigator 'cookie.' The next time the login page is called, the language and email address automatically show up thanks to the local cookie.

When you change the language setting, this new option will be recorded in the cookie. This active cookie automatically overwrites any default language setting at server level.

To change the default language:
 
The ModusGate / ModusMail administrator can change this server default language when no local Vircom cookies are present: this is done by modifying a setting in the 'Custom.config' file using a text editor, like Notepad.
 
The ModusGate default path is c:\Program Files\Vircom\Web\Quarantine\WebSite\Custom.config.
The ModusMail default path is c:\Program Files\Vircom\Web\WebMail\WebSite\Custom.config.
 
The start of a Custom.config file looks like this:

 <appSettings>
 <!--
 Define the default language to use if none is selected by the user.
 -->  
 <add key="DefaultLanguage" value="en"></add>
 <add key="DefaultTheme" value="Vircom"></add>
    <add key="Site" value="localhost"></add>
    <add key="WebMailServerAddress" value="localhost"></add>
    <add key="WebMailServerPort" value="31804"></add>
...
  </appSettings>


The line  <add key="DefaultLanguage" value="en"></add> can show up as <add key="DefaultLanguage" value="en-US"></add>
 
To switch the default language to French, for example, change the "en" to "fr".  If your value is "en-US", change it to "fr-CA". Save your modfied Custom.config file.
 
To activate the changes immediately, run IISRESET (Start > Run > enter iisreset, click OK), then stop and restart the Webmail Server service.

Other language values available in this version are:

English    en-US
French     fr-CA
German     de-DE
Danish     da-DK
Spanish    es-MX
Dutch      nl-NL
Norwegian  nn-NO
Portuguese pt-BR
Russian    ru-RU
Swedish    sv-SE
Turkish    tr-TR

This parameter will be retained after upgrades of ModusGate and ModusMail. A local cookie always overrides this parameter.

1.15.3. How-To: Configure ModusMail 4.0 & 4.1 Web Components

Product: ModusMail

Version & Build: Versions 4.0 & 4.1

Background information:

If you upgraded from the ModusMail 3.x build, both the 3.x and 4.0/4.1 versions of the Webmail user interface can be used at the same time.  This is important for end users who have Safari or Opera browsers: they are not compatible with the 4.0/4.1 user interface (UI).

Safari, Opera, and older versions of Netscape and IE are still supported in the 3.x version of WebMail.

NOTE: A new diagnostic utility was built into version 4.1 that can be used to help determine any connectivity or configuration problems. Before reading further, please see the Diagnostic Utility for WebMail/WebQuarantine to help pinpoint any errors you may have, then refer to the appropriate section below for configuration details.

Folder Structure:

The "old" Webmail configuration files are located in the Web\WebMail directory (Mail).  When you upgrade to Modus 4.0/4.1, a new directory called WebSite is added to the existing folder structure.

The main configuration information is contained in a file called webmailsvr.ini, located in Web\Webmail.  This file is used by both 3.x and new UI versions.  This is where you specify the IPs used for the SMTP, POP and IMAP connections.  Below is a breakdown of the required configuration information.

Configuration 1: Modus and Web components installed on 1 server  

WebMail: Webmailsvr.ini configuration

[RPC:Settings]

The Host address must be the IP of the server where Webmail is installed and running.

[Default:Settings]

The POP3Server, IMAP4Server and SmtpServer fields must all display either the static IP of the mail server or the loopback address, 127.0.0.1 

1) The address entered in the SmtpServer field must be added to the security settings in the ModusMail admin console: Security > Mail Relay > Accept mail for relay from these hosts.

2) The loopback can only be used for the SMTP, POP & IMAP values if Webmail is installed on the same server as ModusMail.  If Webmail is on a separate server, you must specify the mail server's IP (either internal or public IPs can be used - see Configuration 2, below). 

DomainName: this must match the default domain name as displayed in the ModusMail configuration console, i.e. the first domain name in the list.  Example, if the primary domain is abc.com in Modus, then enter that information here; if it's mail.abc.com (i.e. the machine name is included), then use that same format here.

BasePath: this must contain the full path to the Users subfolder within WebMail or Web Quarantine, e.g. C:\Vircom\Web\WebMail\Users.

WebAdminURL: A default install will auto-create a virtual directory called WebAdmin under the Default Web Site in IIS. Therefore the path here can be simply: /webadmin/ - note that the path must end with a forward slash.

If WebAdmin was created under a different site, enter the full URL path here, e.g.:

http://www.mydomain.com/webadmin/

QuarantineEnabled: Enter a value of 1 to display the quarantine tab; a value of 0 hides it.

NOTE: In brand new installs, this value does not appear as the quarantine is enabled for all users by default. If you wish to prevent users from seeing their quarantine contents, either create the above entry manually with the desired value, or control it from the Modus admin console: Web > Webmail: disable "Show Quarantine Folder" > Apply. After making the change, stop/restart the Webmail Server Service.

It can also be configured on a per domain basis in the Modus admin console > domain properties > WebMail tab.

[DomainName:Settings]

This is where to configure the connections for other domains or mail servers, where the connection info is different from the default domain.  For example, if you have a single webmail website that all local users log into: all domains use the settings under the [Default:Settings] section, even if each domain has its own IP.

If you have domains that require different settings from the defaults, or if you want to allow WebMail access to multiple mail servers, create a section called [DomainName:Settings] and enter the required configuration using the following syntax, e.g.:

[DomainName:Settings]
ConvertState=0

[xyz.com:Settings]
DomainName=xyz.com
Pop3Server=10.10.10.10
Pop3Port=110
SmtpServer=10.10.10.10
SmtpPort=25
QuarantineEnabled=0

WebAdmin Configuration

Go to the Web \ WebAdmin \ Root folder in Windows Explorer and open the file called Custom.config: <appSettings> section:

Site value: the default value will be blank. If there are any problems accessing this program, enter either 127.0.0.1 or the mail server's IP between quotes (either internal or public IP). If the machine has more than 1 NIC card, use the 1st static IP; don't use 127.0.0.1.

WebMonitor Configuration

Go to the Web \ WebMonitor > web.config file: the default value will be: <add key="ModusServerAddress" value="127.0.0.1"></add>. 

If there are any problems accessing this program or the IP must be changed (such as when there are multiple NIC cards on the machine), copy the following lines from the Web.config file and paste them to Custom.config file and enter the new IP:

<add key="DefaultLanguage" value="en-US"></add>
  <add key="DefaultTheme" value="Vircom"></add>
        <add key="ModusServerAddress" value="127.0.0.1"></add>

Folder Permissions

On a Windows 2000 server, give Modify* permissions to the IUSR_machine and ASPNET accounts (often called aspnet_wp) on the folders listed below. On a Windows 2003 server, the permissions must instead be given to the IUSR_machine and Network Services accounts. Make sure the permissions are propagated to the child files and folders.

  • WebAdmin
  • WebMail (including server and client folders from older setups)
  • ModusMail
  • WebMonitor

* At a minimum, the above-named accounts must have Read & Execute, List and Read permissions on the listed folders & contents, and Modify permissions on the Temp and Users directories within Web\Webmail. 

IIS Site Configuration:

If you if you had an existing WebMail virtual directory, a new site is created under the name NewWebMail. You should therefore have the following sites:

  • WebMail: Local Path points to ...Web\Webmail\AspRoot
  • NewWebMail: Local Path points to ...Web\Webmail\WebSite
  • WebAdmin: Local Path points to ...Web\WebAdmin\Root
  • WebMonitor: Local Path points to ...Web\WebMonitor

Custom settings

If you wish to change or customize any of the default settings for any of the web components, use the Custom.config files NOT the Web.config files.  Changes made to Custom.config will not be overwritten by subsequent upgrades, whereas any changes made to Web.config will be lost during an upgrade. 

For details about customization, see WebMail and WebQuarantine Interface Customization

Configuration 2:  WebMail and ModusMail installed on separate servers

To allow all components to talk to each other, you'll need to create pointers to the mail server after the install is complete:

WebAdmin:

Go to the Web \ WebAdmin \ Root folder in Windows Explorer and open the file called Web.config: <appSettings> section:

Site value: enter the Mail server's IP between quotes (either internal or public IP)

WebMail - webmailsvr.ini file:

Go to the Web\Webmail folder and open the webmailsvr.ini file: 

Host address: The Host address must be the IP of the machine where webmail is installed and running. 

POP3, IMAP4 and SMTPServer settings: enter the IP of the mail server

DomainName: this must match the default domain name as displayed in the ModusMail configuration console, i.e. the first domain name in the list.  Example, if the primary domain is abc.com in Modus, then enter that information here; if it's mail.abc.com (i.e. the machine name is included), then use that same format here.

For details about folder permissions, different domain settings, etc., see the information in the Folder Permissions section (above).

Important Notes when WebMail is installed on a separate machine:

  • In the Modus Admin console > Services tab, the WebMail Server Service will appear to be disabled and the Settings button will not display a hostname or IP. This is normal: the service is controlled on the server where it's installed and running.
  • To stop and restart the WebMail Server Service, use the Windows > Admin Tools > Services panel.
  • The configuration options under Web / WebMail tab are not available in the console: these settings must be configured manually in the webmailsvr.ini file.

WebMonitor:

See the information in Configuration 1 above, but enter the ModusMail server's IP in the line: <add key="ModusServerAddress" value="127.0.0.1"></add>

Additional Configuration Information when using Database mailboxes:

If you're using database mailbox authentication, create an ODBC connection between the web server and the database server, using a mirror of the ODBC configuration on the Modus server: same System DSN name, login and password.

Additional Configuration Information when using SQL quarantine:

If using SQL for the quarantine database, create an ODBC connection to the database server, again mirroring the connection info on Modus: same System DSN name, login and password.

Configuration for Windows 2003

For more details about configuring a Windows 2003 server, see How-To: Configure Windows 2003 for web components.

1.15.4. How-To: Remove Access to Homepage Statistics

 

Product: All

Version & Build: 4.1.361

If you are not using the monitoring service, or if you prefer users not to have access to their mail statistics, you can remove the Homepage and its icon from the web interface.

To remove the homepage from the web interface:

  1. Open the Custom.css file in the ...\WebSite \ Themes \ Vircom directory
  2. Add these lines:

#Navigation1_WMNDashboard

{

    display:none;

}

 

Example: The file should look like this:

body
{
}
#Navigation1_WMNDashboard

{
    display:none;
}

  1. Save the file.
  2. Go to Start / Run and enter the command IISReset.
1.15.5. Problem: WebAdmin Settings Tab generates "Page cannot be displayed" until IIS reset

 Product: All

 Version & Build: 4.0 & 4.1

Problem Summary:
"Page cannot be displayed" when accessing the Webadmin URL or the Webmail Settings Tab. Performing an IIS reset fixes the issue until it happens again after X days. The Event viewer may show : Application popup: aspnet_wp.exe - Application Error : The instruction at "0x16dbad5f" referenced memory at "0x174eeba8"

 

Cause:

The exact cause is not known but seems to be related to IIS or the .NET framework. The administrator will likely see that multiple instances of the process "aspnet_wp.exe" running in Task Manager.
 

Resolution:

1) Stop the IIS Admin Service ; 2) Open Task Manager and stop all instances of the "aspnet_wp.exe" process. If necessary kill these processes using kill.exe ; 3) Restart the IIS Admin Service and the WWW Service.

 

1.16. Safari not supported by Webmonitor

Product:
modusGate
Version & Build: 5.51
 

Known Issue:

Safari Web browser on Windows OS does not support Microsoft NTLM authentication . You can use any other supported browser to access Web Monitor. If you prefer to use Safari, please follow the steps in this KB article on how to change your authentication settings in IIS.


Workaround:

For a list of other supported browsers view the following knowledge base article
OR

You can run a command-line string that will support Web Monitor browsing with Safari on Windows OS:
 
 
IMPORTANT:

Run this command where the Web Monitor site is hosted, running this command-line will disable IIS Negotiation on the server. This will create a large security hole not only for Web Monitor but any website being hosted in IIS. Apply this command at your own risk.

1-Open a command prompt

2-Run the following command-line string

 
     C:\appcmd.exe set config "Default Web Site" -section:system.webServer/security/authentication/windowsAuthentication /-"providers.[value="Negotiate" /commit:apphost
 
3-Restart IIS service.