1. modusMail & modusGate Technical Information
1.1. Documentation & Release Information
1.1.1. Version 6.5
Important information about upgrading to modus 6.5
 

System Requirements:
        

Operating System: Windows Server 2008 (32 and 64-bit), 2008R2, 2012, 2012R2, 2016 (Server with Desktop Experience) and Windows Small Business Server (SBS) 2008 x64 and 2011 x64. Windows Web Edition is not supported.

 Web Server: IIS version 7.0 or later.

Components: MDAC 2.8 SP1 or higher, .NET Framework 3.5 SP1 and 4.5 

Exchange Integration: Microsoft Exchange 2007/2010/2013/2016. 

SQL Server: 2008 x86/x64, 2008R2, 2008 Express Edition, SQL 2012 x86/x64, SQL 2014 x86/x64, SQL 2016, SQL 2017.

Microsoft Office: Microsoft Office 2007, 2010, 2013, 2016 (This only applies to directQuarantine.)

Web Browsers:

Desktop: Internet Explorer 9+, Chrome 30+, Safari 7+, or Firefox 25+

Mobile*: iOS Safari 4.0+ (4x, 5.x), Android Browser 4.0+ (4.x, 5.x), Chrome 30+

* Note that the mobile web browsers only apply to the Web Quarantine.


Change Logs
 
See the modusMail / modusGate pages below for their respective change logs and list of fixes. 

1.1.1.1. modusGate
New in modusGate 6.5


This latest release of modusGate is version 6.5 and it includes several improvements as well as the new Web Admin site.

 

Highlights: 

 

  • The Web Admin site incorporates the new UX and significant performance improvements. The old web admin site is still available in this release but will soon be phased out. The old web admin does not include new features from this release and is being deprecated.
  • modusGate filtering engines have improved protection against emails containing malicious URL's that could send end-users to malicious sites.
  • modusGate now supports sending aggregated DMARC reports.
  • modusGate now supports configuration of routes for Office 365 Active Directory including population and authentication support.
  • modusGate filtering engines now have additional protection against phishing messages with fraudulent display names to combat email fraud.
  • modusGate now supports deployment on Windows Server 2016 (Server with Desktop Experience).
  • modusGate now supports database configuration on SQL Server 2016 and SQL Server 2017.

 

                                                                                          IMPORTANT – PLEASE READ

 

modusGate can no longer be installed on sites where the Quarantine database is configured on servers earlier than SQL 2008. To ensure that mdosuGate utilizes the latest performance and security enhancements of MS SQL, we highly recommend you upgrade to MS SQL Server 2014. 

If you need help migrating your modusGate server or MS SQL database, please contact our Support Team to schedule a time and cost estimate for your migration.

It is highly recommended to access modus Web sites via https with a proper certificate installed and configured on your web server.

The latest version of the directQuarantine Outlook client (DQ) must be installed to see spoofing spam messages caught. This version of DQ is available with this release of modusGate. 

 

Change Logs: 

  • Opportunistic TLS is now enabled by default.
  • SPF Sender ID (SPF 2.0) is no longer supported by modusGate.
  • Upgraded to the latest Mailshell SDK version 8.0.9 which improves accuracy, ease of use, disk usage, latency, network and reliability.
  • SPF recursive limit is increased from RFC recommended 10 to 20.
  • Added performance counters to count SPF/DKIM/DMARC/Malicious URL.
  • Improvements on email address, display name extraction to address rare cases of Mailsploit exploit that could bypass DMARC and DisplayName filters.
  • Upgraded SSL library to OpenSSL version 1.1.
  • Updated Avira SDK to version 4.6.2.
  • Updated Bitdefender engine to version 3.0.0.159.
  • Updated Perl library to version 5.26.
  • Avira license key has been updated.
  • Addressed spam which by-passed Forbidden Attachment scans through UTF-8 encoding.
  • Fixed an issue in Web Quarantine where sender mailbox that contained invalid characters could not be removed from Trusted and Blocked lists.
  • Fixed an issue when customer with Modus Web Components installed on a separate server could not upgrade to the latest version.
  • Fixed an issue where modusGate attempted to deliver emails to addresses containing wildcard characters for Exchange routes.
  • Fixed an issue when modusGate with opportunistic TLS enabled was not populating MAIL FROM in certain cases.
  • Fixed an issue where an IP containing invalid character imported into Mail Relay list allowed relay of emails via modusGate.
  • Fixed an issue where SPF record  query results were not included in OPR logs.
  • Fixed an issue when items caught by anti-spoofing filters were present in Quarantine Reports configured to show only items with low spam probability level.
  • Fixed an issue where certain items were presented twice in Quarantine Report.
  • Fixed an issue when modusGate could not be installed with LocalDB configuration.
  • Fixed an issue when license count for distribution groups was incorrect in certain cases.
  • Fixed an issue where adding an IP to the SMTP Security Trusted does not bypass the HELO\EHLO identity.
  • Fixed an issue when admin user could not login into Wedadmin when "Force HELO\EHLO identity" was checked.
  • Fixed an issue where a server name beginning with underscore could not be added to the list of DNSBL Servers in Security - DNSBL - DNSBL Servers.
  • Fixed an issue where deleting a database user would not delete from the modus console.

 

Operational Considerations:

1. New Web Admin site is accessible via http(s)://<modusWebServerAddress>/admin (e.g. https://127.0.0.1/admin). 

2. For access via the Web interface to the new configuration options (Scan for Malicious URL's, protection against Display Name phishing) the admin should use the new Web Admin application.

3. Monitoring DB may consume slightly more disk space in some cases.

4. Since modusGate relies on IP reputation data, it needs to see teh IP address of the originating server to be able to make a proper judgement on inbound spam of a message. If modusGate is not the first server to receive all email from the outside world, please contact our support team so that they can assist you in configuring your system. Step 6 below needs to be done for the first server.

5. As of modusGate 6.x our anti-spam engine SCAV2 requires that the UDP outbound port 53 and TCP port 80 to remain open to properly filter emails. If you require a list of IP's to our servers, you may contact our support team for the complete list.

6. If your modusGate is configured to perform outbound filtering the following steps are needed to:

  • Go the following folder …Vircom\modusGate\SCAV2
  • Open the file called "spamcatcher.conf"
  • Search for the parameter called "ignored_ip_list"
  • Remove the # character and enter the IP of the mail server the emails are being filtered from. 

             ie: ignored_ip_list=192.168.0.179

 

  • Save and RESTART moduscan service..

 

 


Known Issues:

Description

Workaround

If downgrading from 6.5 to 6.4 the installation won’t be completed

Before downgrading:

·         Stop the ModusSecurity service manually via Microsoft Component Services.

·         Stop ModusWeb service

·         Delete the “perl” folder from \\installationPath\Vircom\modusGate\

dQ Outlook clients are not able to connect to dQ server. Verify if the server’s localhost is mapped to an IPV6 address.

1.    Locate the directQuarantine Server.exe.config file

2.    Change all "localhost" addresses to "127.0.0.1" and save the file

3.    Restart the directQuarantine service.

The upgrade process may be interrupted with an error window, labelled “Update Error” followed by 4 similar errors. At this point the installer will terminate and the upgrade is incomplete.

 

This issue may only present itself when the server running modusGate is low on system resources. This in turn could impact SQL processes from running optimally during the upgrade.

 

1.    Select “OK” button on all installer error pop-ups.

2.    Kill all installer processes if still running.

3.    Stop processes that may be taking up a lot of the server’s resources.

4.    Stop “ModusScan” service from Windows Service manager.

5.    Restart the installer and complete the upgrade.

 

 

 

 

 

Support:

Web:            http://www.vircom.com/support  
Phone:         1-888-484-7266
Email:          
support@vircom.com


Trademarks:

Vircom, Email Security Grader, Email Security Matters, SysAdmin on the Line, NetAdmin on the Line, modus, modusMail, modusGate and modusCloud are trademarks of Vircom Inc. Windows and Exchange are registered trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners.


 

 

  
1.1.1.2. modusMail
New in modusMail 6.5

This latest release of modusMail 6.5 includes several security improvements and bug fixes.

For a more complete set of security features and improvements, Vircom recommends that you install modusGate 6.5 in front of your modusMail. Please contact the Vircom support team to help you set this up. Several of our modusMail customers have made this change already and are benefiting from the full set of email security features offered by modusGate.

 

                                                                                          IMPORTANT – PLEASE READ

 

It is highly recommended to access modus Web sites via https with a proper certificate installed and configured on your web server.

 

Change Logs:

  • Upgraded to the latest Mailshell SDK version 8.0.9 which improves accuracy, ease of use, disk usage, latency, network and reliability.
  • Updated Avira SDK to version 4.6.2.
  • Updated Bitdefender engine to version 3.0.0.159.
  • Addressed spam which by-passed Forbidden Attachment scans through UTF-8 encoding.
  • Fixed an issue where an IP containing invalid character imported into Mail Relay list allowed relay of emails via modusMail.
  • Fixed an issue when modusMail with opportunistic TLS enabled was not populating MAIL FROM in certain cases.
  • Opportunistic TLS is now enabled by default.
  • Avira license key has been updated.
  • Fixed an issue when Webmail service was consuming 50% of CPU.
  • Fixed an issue where deleting a database user would not delete from the modus console

 

Operational Considerations:

1. Since modusMail relies on IP reputation data, it needs to see the IP address of the originating server to be able to make a proper judgement on the spamminess of a message. If modusMail is not the first server to receive email from the outside world, please contact our support team so that they can assist you in configuring your system.

2. As of modusMail 6.x our anti-spam engine SCAV2 requires that the UDP port 53 and TCP port 80 to remain open to properly filter emails. These ports are needed for both outbound and inbound traffic. If you require a list of IP’s to our servers, you may contact our support team for the complete list.

3. If your modusMail is configured to perform outbound filtering the following step are required:

 

  • Go the following folder ...Vircom\modusMail\SCAV2
  • Open the file called "spamcatcher.conf"
  • Search for the parameter called "ignored_ip_list"
  • Remove the # character and enter the IP of the mail server the emails are being filtered from.
           ie: ignored_ip_list=192.168.0.179

 

  • Save and RESTART moduscan service.

 

  

 

Known Issues: 

 

The upgrade process maybe interrupted with an error window, labelled "Update Error" followed by 4 similar errors. At this point the installer will terminate and the upgrade is incomplete.

The issue may only present itself when the server running modusMail is low on system resources. Which may impact SQL processes to run optimally during the upgrade.

 


- Select "OK" button on all installer error pop-ups.

- Kill all installer processes if still running.

- Stop processes that maybe taking up a lot of the server's resources.

- Stop "ModusScan" service from Windows Service manager.

- Restart the installer and complete the upgrade.


 

Support:    

Web:               http://www.vircom.com/support
Phone:            1-888-484-7266
Email:            
support@vircom.com


Trademarks

Vircom, Email Security Grader, Email Security Matters, SysAdmin on the Line, NetAdmin on the Line, modus, modusMail, modusGate and modusCloud are trademarks of Vircom Inc. Windows and Exchange are registered trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners.


 
 


1.1.1.3. Customizing Webmail/WebQuarantine 5.13 (new installs)

Product: All

Version & Build: 5.13



Important: When upgrading to Modus 5.13 the default "Vircom" theme will be applied. Please follow steps below to make the appropriate changes to your custom pages.


The following customization information can be used with both ModusMail and ModusGate - where applicable.

There are many levels of customization that you can make for the web interface, depending on what you want to do:

  • you can substitute your company logo for the Vircom logos (which appear on the login and on each web page)
  • you can modify attributes of the Vircom theme such as the color or the size of the text
  • you can bypass Vircom's login page and have your users access their webmail through your own portal
  • you can create a completely different theme for the web interface that bears no resemblance to the Vircom theme - this theme will not be overwritten by future upgrades, BUT any interface enhancements made by Vircom will not be reflected in your custom-built interface. We provide only very basic customization information here: we provide enough information that if you know what you're doing, you'll know how to support your own customizations and you can go ahead and build your own interface.

Note: The web.config and style.css files contain the product default values. Never alter these files because any work you do will be lost upon upgrading the software. Change the custom.config and custom.css files instead. A Modus upgrade will not overwrite these files, except that it will set back the DefaultTheme to Vircom. This is needed because major changes have been done in the styles for this version.  Please note also that Vircom Technical support cannot debug any custom interfaces you build. We can support only basic style changes to the Vircom interface that include rebranding and recoloring (changing images and modifying CSS styles).

Custom.Config Basic Functionality Customization

NOTE: Any modifications you make in the custom.config file will require you to Stop/Start the IIS Admin service after you have finished.

1. The default language of the WebMail interface is defined in this key. The value must match an existing folder under Locales.

<add key="DefaultLanguage" value="en"></add>

2. The default theme of the WebMail interface is defined in this key. The value must match an existing theme folder under Themes.

<add key="DefaultTheme" value="vircom"></add>

3. This is the domain name or IP address of your WebMail Server service.

<add key="WebMailServerAddress" value="localhost"></add>

4. This is the port number of your WebMail Server service.

<add key="WebMailServerPort" value="31804"></add>

5. This is the character set in which the page will be displayed.

<add key="Charset" value="iso-8859-1"></add>

6. This is the path of the temporary folder that the installation program configures automatically.

<add key="Temp" value=""></add>

7. This is the path of the log folder that the installation program configures automatically.

<add key="LogDir" value=""></add>

8. This is the relative path and file name of the Login page. If you want to design your own login page or you want to integrate webmail with your portal, change this value to your to the relative path and file name of your custom-designed login page. When logging off, users will be redirected to this page instead of the main webmail login page.

<add key="LoginPage" value="Login.aspx"></add>

9. This is the name of the application that will be shown in the browser windows title bar.

<add key="Title" value="Webmail"></add>

10. This option determines whether WebMail should parse messages to find out if there is an attachment.

<add key="ShowPaperClip" value="false"></add>

NOTE: When this option is turned on, you might encounter performance drops for POP3 accounts since the message must be downloaded completely. This does not affect IMAP4 accounts. Set the value to "true" to enable or to "false" to disable it.

11. This option determines whether users can specify the email address that will be shown in the From field of outgoing emails.  Turn on this option with caution since it allows users to enter any email address.

<add key="AllowChangeFromAddress" value="false"></add>

Set the value to "true" to enable or to "false" to disable it.

Logos

In the custom.config file, you can set the image and hyperlink for the Login logo and the top menu logo.  These images must exist in your selected theme in order to work.

<add key="LoginLogoUrl" value="http://www.vircom.com"></add>
<add key="511LoginLogoImage" value="LogoLogin.gif"></add>
<add key="MenuLogoUrl" value="
http://www.vircom.com"></add>
<add key="511MenuLogoImage" value="LogoMenu.gif"></add>

Custom Login Page or Portal Integration

You can create your own login page or insert the login form in your portal.  Your login page should include a form with the two following form fields:

<input type="text" name="txtLogin"/>
<input type="password" name="txtPassword"/>

The page's form action should be set to "Login.aspx" and the method set to "POST".  Here's a simple Login page:

<html>
<body>
<form action="Login.aspx" method="POST">
<input type="text" name="txtLogin"/>
<input type="password" name="txtPassword"/>
<input type="submit" value="Login"/>
</form>
</body>
</html>

Theme Customization

The WebMail application theme is made through a main CSS file (and if you vary functionality between domains, you'll also need a customized .config file).  DO NOT alter the Style.css file or the Web.config file (or will you will lose all your work when you perform a Modus upgrade).  Instead, you must redefine colors, fonts, and other attributes in the Custom.css, and any functionality variations (see config file attributes above) in the custom.config files.

Any changes you make to the custom files will override the values in the style.css and web.config files.

For domain customization, create css and config files and name them according to the domain, for example:

  • domain.com.css (which should be saved in your custom theme directory)

  • domain.com.config (which should be saved in the webroot directory)

  • domain.net.css (which should be saved in your custom theme directory)

  • domain.net.config (which should be saved in the webroot directory)

These domain files will override the custom.css and custom.config files which override the main style.css and web.config files.

NOTE: you only have to create a domain customized config file if you want to vary functionality between domains as well as the look and feel of it. Otherwise only create a domain customized .css file for your theme.

Changing the Login page color

The login page orange color constitutes of an image (Login_RoundBorder.gif) and a table cell. For example, to change the color to lightgrey:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #tdLoginRight
    {
    background-color: lightgrey;
    }

4. Save and close the file

Note that unless you change the Login_RoundBorder.gif image to lightgrey, it will look odd, so you can edit that file in an image editor or you can hide it altogether. To do so, add the following lines in the custom.css right after the lines previously added: #tdLoginMiddle

    #tdLoginMiddle
    {
    display: none;
    }

Changing the Top Menu color:

The top menu constitutes of an image (LogoMenu.gif) which is configured in the custom.config file, and a gradient image of 1 pixel width. The gradient image adds a level of depth to the menu bar while preserving a very small file size. If you want to change the gradient coloring, open the GradientMenu.gif file in an image editor such as Gimp, PaintShopPro or Photoshop and change the color or gradient value of the image to your preference. You can also discard the gradient in the top menu and only use a solid color, such as lightgrey. To do this:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .Menu
    {
    background-color: lightgrey;
    background-image: none;
    }


4. Save the file

Changing the lists hover color:

Each message status has a separate class. This allows you to define different attributes for when an email is read, unread or deleted. In order to change the hover color, you will need to change each of these classes:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .dgListItemHover
    {
    background-color: lightgrey;
    }
    .dgListItemUnreadHover
    {
    background-color: lightgrey;
    }
    .dgListItemDeletedHover
    {
    background-color: lightgrey;
    }

4. Save the file

Changing the background color of all panels:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .MessageViewMsgHeader,
    .SettingsAccount,
    .SettingsOption,
    .SettingsOptionGeneral,
    .SettingsFolders,
    .SettingsOptionsAntiSpam,
    .SettingsOptionsAntiVirus,
    .SettingsOptionsRules,
    .SettingsOptionsAutoReply,
    .SettingsContacts,
    .SettingsOptionsHome,
    .SettingsOptionsBusiness,
    .SettingsTrusted,
    .SettingsBlocked,
    .SettingsOptionsBlocked,
    .SettingsOptionsTrusted,
    .SettingsAliases,
    .SettingsOptionsReporting,
    #divContactEditor_main,
    .DiagnosticContainer
    {
    background-color: lightgrey;
    }

4. Save the file


Hiding the Server Blocked/Trusted List from the Settings Page:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #Trustedlist_TableRowWhitelistServerTitle,
    #Trustedlist_TableRowWhitelistServerData,
    #Blockedlist_TableRowBlacklistServerTitle,
    #Blockedlist_TableRowBlacklistServerData
    {
    display:none;
    }

4. Save the file

 
 

modusMail only:


Removing Statistics (or other major menu items)

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 Statistics menu option from the web interface.

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #tdStatistics
    {
    display: none;
    }

4. Save the file

NOTE: these instructions apply to the other menu items: #tdAddressBook, #tdFolders, #tdSettings, #tdLogoff. Change the syntax for the line in step 3 from <#tdStatistics> to the menu item you want to hide.

Hiding Sections in Settings:

As with the login page, it is possible to hide certain parts of the page. This is especially useful if you don't want your users to access particular types of settings.

Hiding the options section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsOptions
    {
    display: none;
    }

4. Save the file

Hiding the email filtering section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsFiltering
    {
    display: none;
    }

4. Save the file

Hiding the user contact information section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsUserInfo
    {
    display: none;
    }

4. Save the file

Hiding the rules section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsRules
    {
    display: none;
    }

4. Save the file

Hiding the auto-reply section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAutoreply
    {
    display: none;
    }

4. Save the file

Hiding the external accounts section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAccounts
    {
    display: none;
    }

4. Save the file

Hiding the aliases section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAliases
    {
    display: none;
    }

4. Save the file

Webmail Message Customization

You can customize your own webmail messages (what we call "strings") - this could be especially useful for foreign language support if the translation provided does not adequately communicate an action or system response.

Each language has its own strings file stored in:

..."Vircom"Web"WebRoot"Locales

There is a strings.xml file - the default translations provided with Webmail - and a custom.xml file. Make your changes in the custom.xml file (as follows in the instructions below) and this file will override strings.xml.

Changing default strings

1. Go to the language folder whose messages you want to customize and open both the strings.xml and the custom.xml files

2. Copy and paste the strings to be customized from the strings.xml file into the custom.xml file

3. Modify the strings in the custom.xml file and save it.

4. You can also include HTML formatting instructions in the custom.xml file to specify how you want the customized strings to be displayed. This is useful, for instance, for the TEXT1000 & TEXT1001 tags which are shown at the top and bottom of the right-hand side of the login page respectively (where the beta version information and the upcoming features information was previously displayed).

5. Save the strings.xml file as well to change its timestamp so that the changes you have made can be viewed immediately (not changing the timestamp on the strings.xml file will mean that the customized strings are not shown until you restart IIS).

1.1.1.4. Customizing Webmail/WebQuarantine (Upgrades)

Product: All

Version & Build: 5.13



Important: Before the process of upgrading from 5.0, 5.1 to 5.13 some folder and file changes are required for the customization.  Please perform the following steps before the upgrade is done.


MODUSGATE INSTRUCTIONS:

1.  Locate the appropriate root installation folder for the Quarantine files, e.g. C:\Program Files\Vircom\Web\Quarantine

2. Open up the directory WebRoot\Themes

3. In this directory you will find three or more folders named Gray, Vircom, and your own Custom folder which contains your customization images and styles. Note that we will use the folder name Custom for the rest of this article while your custom folder could have a different name.

4. Rename the Vircom folder to Vircom1.

5. Next make a copy of your Custom folder (for backup purposes) and rename your original Custom folder to Vircom.  Your Themes folder should look like:

 

6. The reason for this is that Modus 5.12 only checks the default Vircom folder for all the style changes.

7. Open up your new custom folder named Vircom.

8. In this directory you will find the customization files named style.css and custom.css.

9. If your customized pages have some custom colors, there is a good chance that you had made these changes in the style.css file. If you know your customizations were made in the custom.css file then proceed to step 12.

10. If you made changes to the style.css file, open it and copy those changes onto the clipboard (CTRL-C).

11. Open the custom.css file in the same directory and paste the clipboard contents into it (CTRL-V).  Save your changes and close both files.  custom.css should now contain your customizations.


12. Once all this is has been done, you can now launch the upgrade for version 5.12.

13. Once the install is complete, open the custom.config file located in c:\Program Files\Vircom\Web\Quarantine\WebRoot folder.

14. There are 2 lines which need to be modified. Both lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

15. Restart Modus Webmail service and IIS. Your customizations should be visible.


MODUSMAIL INSTRUCTIONS:

1. Download and install Modus 5.12.

2. Once the install is complete, open the custom.config file located in C:\Program Files\Vircom\Web\WebMail\WebRoot (assumes a default install location).  

3. There are 3 lines of code which need to be modified. All 3 lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines -<add key="DefaultTheme" value="Vircom"/>.

TO

<add key="DefaultTheme" value="CUSTOM"/>

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

4. Restart Modus Webmail service and IIS. Your customizations should be visible.


1.1.1.5. Configuring Exchange on Windows Small Business Server to listen on an alternate port (25)
Product: modusGate
Version & Build: all

If you're interested in getting modusGate running on the same system as Microsoft Exchange (example, on a Windows Small Business server), with both of them co-existing on the same machine, you cannot have modusGate & Exchange both listening on the same SMTP port 25. 



What you want to do is have modusGate listen on port 25 and it would redirect the traffic to the local exchange server on an alternate port (usually 26).
 
This being said, how do you get Microsoft Exchange to listen on port 26?
 
 
On Exchange 2007 and 2010:
 
 
You can change the receive connector port thus:

1. Go to the Exchange Management Console under Hub Transport
2. Select thereceive connector name you want to change
3. Click on properties
4. Select “network”
5. Choose local IP address
6.  Edit the Receive Connector Bindings
7.  Change the port to the desired port to listen on for SMTP traffic (ex: 26)
 
 

Optional: You can restrict who can send to this SMTP server by editing the “receive mail from remote servers which have these IP addresses”. In this case, you could restrict it to 127.0.0.1 if you want to allow inbound port 26 traffic to only come from modusGate which is sitting on the same box.
 
 
On Exchange 2000 and 2003:
 
 
1. Start the Exchange System Manager.
2. Select the Servername you want to change.
3. Click on Protocols
4. Click  on SMTP
5. Right-click the Default SMTP Virtual Server object
6. Click Properties.



7. On the General tab click the Advanced button
8. Click the Edit button
9. Set the TCP port to desired port (ex: 26).
 
 
 
 
On Exchange 5.5:

 
To change the SMTP listening port on a server that is running Exchange 5.5 from port 25 to another port (for example: port 26) follow these steps:

1.  Open the Control Panel
2. Select Administrative Tools
3. Select Services
4. Stop the Exchange Server Internet Mail service.
5. Open the file c:\Winnt\System32\Drivers\Etc\Services using notepad
6. Locate the line containing: "smtp 25/tcp mail" and change the 25 to 26.
7. Save the Services file.
8. Start the Exchange Server Internet Mail service.


1.1.1.6. Customizing Webmail/WebQuarantine (Upgrades)

Product: All

Version & Build: 5.31 +


modusGate 5.42 includes a brand new quarantine interface.  Customizations of this new interface  is not compatible with prior versions.

You will find your previous WebQuarantine installation and any customization done is still available via the QuarantinePre5-30 virtual directory.

MODUSGATE INSTRUCTIONS:

1.  Locate the appropriate root installation folder for the Quarantine files, e.g. C:\Program Files\Vircom\Web\WebQuarantine

2. Open up the file custom.config

3. At the end of the file, you will find the following lines, each of them denote a configurable setting for WebQuarantine.

  <add key="LoginLogoUrl" value="http://www.vircom.com" />
  <add key="LoginLogoImage" value="logo-login.png" />
  <add key="FooterLoginLogoUrl" value="http://www.vircom.com" />
  <add key="FooterLoginLogoImage" value="footer-logo-login.png" />
  <add key="MobileLoginLogoUrl" value="http://www.vircom.com" />
  <add key="MobileLoginLogoImage" value="logo2.png" />
  <add key="MobileFooterLoginLogoUrl" value="http://www.vircom.com" />
  <add key="MobileFooterLoginLogoImage" value="logo-vircom.png" />
  <add key="MobileMenuLogoImage" value="logo.png" />
  <add key="MenuLogoUrl" value="http://www.vircom.com" />
  <add key="MenuLogoImage" value="logo.png" />
  <add key="FooterLogoUrl" value="http://www.vircom.com" />
  <add key="FooterLogoImage" value="logo-vircom.png" />

4. To use your own logo, change the Image values to your own logo filename, for example:

To change Login page logo, change


  <add key="LoginLogoImage" value="logo-login.png" />

To:

  <add key="LoginLogoImage" value="my-logo-login.png" />

And put your new logo file in the WebRoot\Wres\img folder.

Mobile logos needs to be put in WebRoot\Wres\mobile\images

5. Change the matching Url value to your desired URL.

6. To customize other attributes such as colors, font type, etc, you can overwrite any CSS rules in the file located at WebRoot\Wres\custom\custom.css

MODUSMAIL INSTRUCTIONS:

1. Download and install Modus 5.42.

2. Once the install is complete, open the custom.config file located in C:\Program Files\Vircom\Web\WebMail\WebRoot (assumes a default install location).  

3. There are 3 lines of code which need to be modified. All 3 lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines -<add key="DefaultTheme" value="Vircom"/>.

TO

<add key="DefaultTheme" value="CUSTOM"/>

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

4. Restart Modus Webmail service and IIS. Your customizations should be visible.


1.1.1.7. modus Upgrade Checklist

 modus Upgrade Checklist

Introduction

         This document is intended for existing Vircom customers who are currently running an older version of ModusGate. You should read this document thoroughly before upgrading. If you have any questions or feel something is missing from this document, feel free to contact us by e-mail at support@vircom.com.


Before upgrading, please ensure that you have met the following requirements:


  • Backup your databases (QT, Audit, Monitoring and Sieve) before launching the upgrade
  • Ideally, this should be a full backup
  • If you are using SQL Server Express, ensure that Full Text Indexing is installed
  • For instructions, please consult the following KB article:
  • http://kb.vircom.com/Kbase/default.asp?SID=&Lang=1&id=1621&Lang=1&SID=
  • Ensure that .Net 3.5 Framework is installed
  • For more information, consult the following Microsoft® websites:
  • Microsoft .NET Framework Version 3.5
  • Ensure that you have your current installation package
  • In the event that you must roll back after upgrading, keep a copy of the *.exe installation file
  • If you do not have a copy of the file, before upgrading, send an email to: support@vircom.com requesting it
  • Backup your Windows Registry
  • On the modus server, click on Start > Run
  • Type regedit to open the Registry Editor
  • In the Registry Editor, click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup any customized quarantine reports and/or web applications folders
  • Read the Release Notes for all new features and changes to modus, especially the section regarding encryption

If you opt to use encryption, there is a sieve script that must be added to prevent issues with foreign languages for outbound messages. This script is included in the Release Notes.


Upgrading modusMail/modusGate to v6.0 

         Due to a series of architectural changes in versions upgrading from version 4.7 must be done in two steps:

        1. upgrade from v4.7 to v 5.0 or v5.1

        2. upgrade directly to v6.0

If you are running any version higher the 5.1 you can directly upgrade to v6.0.


Changes to the installation process:

         Starting from v5.31 ModusGate comes with a new web interface. The new interface will not overwrite your existing WebQuarantine programs. This will allow you to continue using the 'old' site until you have had time to test and/or customize the new one.

ModusGate Web Quarantine information:

         There will be a new folder created called WebQuarantine locate under C:\Program Files(x86)\Vircom\Web. This folder will contain the new websites attributes for the new web quarantine pages. The virtual directory will still exist in IIS.


IMPORTANT:

          If you plan to use the monitoring feature, it is preferable to use a Microsoft SQL database instead of the native Access format. Whether to use Microsoft Access or Microsoft SQL depends on your volume of traffic. A good rule of thumb would be to use your quarantine database as your guide: if you use SQL for the quarantine, then you should use it for the monitoring stats as well.


Upgrading ModusGate

Upgrading requires a certain number of precautions. The most important is doing a backup before upgrading:

  • Make sure you have access to your old Modus installation package in case you need to rollback. If you do not have a copy, click on the help -> about button in your ModusGate console to find out what version you have and the build number; contact us by email, and we will be happy to provide you with the original install package.
  • Backup your configuration: - Open the ModusGate administration console and select File > Backup configuration - Select the path where the configuration file will be stored (*.reg file) - Keep this registry file (*.reg) in a safe location as a backup of your Modus configuration.
  • Backup the Registry: - Open the Registry Editor (regedit) - Click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup the Web directory: Located under...\Vircom\Web
  • Backup the databases: Normally located under the root installation of SQL \\Microsoft SQL Server\MSSQLXX.SQLEXPRESS\MSSQL\DATA
  • Proceed with the upgrade.


Upgrading ModusMail

Upgrading requires a certain number of precautions. The most important is doing a backup before upgrading:


Steps to take before upgrading:
  • If you have the hardware and software capability, it would be best to mirror your existing machine so you could hot-swap (switch the IP addresses over) should the upgrade fail. However, in the event that you cannot mirror your server, proceed with the following:
  • Make sure your datasource is up-to-date. If you are using an external datasource for authentication (such as a billing package), ensure that it is up-to-date.
  • Note: If you are using Platypus or RODOPI, check with Boardtown or RODOPI to find out if a new stored procedure is required. In any event, you should run the latest stored procedures for ModusMail.
  • Make sure you have access to your old Modus installation package in case you need to rollback. If you do not have a copy, click on the help -> about button in your ModusMail console to find out what version you have and the build number; contact us by email, and we will be happy to provide you with the original install package.
  • Backup your configuration:

         - Open the ModusMail administration console and select File -> Backup configuration

         - Select the path where the configuration file will be stored (it will be a .reg file)

         - Keep this registry file (*.reg) in a safe location as a backup of your Modus configuration

  • Backup your registry:

         - Open the Registry Editor (regedit)

         - Click on File > Export

         - Select the file location, enter a name for the backup file and click OK

  • Backup the Web directory: Located under...\Vircom\Web
  • Backup the databases: Normally located under the root installation of SQL \\Microsoft SQL Server\MSSQLXX.SQLEXPRESS\MSSQL\DATA
  • Proceed with the upgrade. 

After upgrade is done please ensure that Modus antivirus engines are up and running:

  • In Advanced console go to Virus Tab and see that both AV were successfully updated with the latest version.
  • Go to System Tab and see that all Modus services are up and running.
  • Note! It could take up to 5 minutes to modus to download and install latest versions of antivirus engine and definitions.
  • Customer may use Email flow diagnostic tool provided with modus installation to verify the legit and spam mail flow.







 


 

1.1.2. Version 6.4
Important information about upgrading to modus 6.4
 

System Requirements:
        

Operating System: Windows Server 2008 (32 and 64-bit), 2008R2, 2012, 2012R2 and Windows Small Business Server (SBS) 2008 x64 and 2011 x64. Windows Web Edition is not supported.

 Web Server: IIS version 7.0 or later.

Components: MDAC 2.8 SP1 or higher, .NET Framework 3.5 SP1 and 4.5 

Exchange Integration: Microsoft Exchange 2007/2010/2013/2016. 

SQL Server: 2008 x86/x64, 2008R2, 2008 Express Edition, SQL 2012 x86/x64, SQL 2014 x86/x64.

Microsoft Office: Microsoft Office 2007, 2010, 2013, 2016 (This only applies to directQuarantine client application.)

Web Browsers:

Desktop: Internet Explorer 9+, Chrome 30+, Safari 7+, or Firefox 25+

Mobile*: iOS Safari 4.0+ (4x, 5.x), Android Browser 4.0+ (4.x, 5.x), Chrome 30+

* Note that the mobile web browsers only apply to the Web Quarantine.


Change Logs
 
See the modusMail / modusGate pages below for their respective change logs and list of fixes. 

1.1.2.1. modusGate
New in modusGate 6.4


This latest release of modusGate 6.4 includes several security improvements that incorporate email authentication mechanisms to detect spoofed emails.

 

Highlights: 

 

  • modusGate now supports the latest email authentication protocol, DMARC (Domain-Based Message Authentication, Reporting & Conformance.” (without Reporting).
  • A new and improved RFC compliant SPF (Sender Policy Framework) mechanism that is now configurable at all levels (System, Domain or User).
  • A new DKIM (DomainKey Identified Mail) cryptographic authentication mechanism for all inbound email flow. That can be configurable at all levels (System, Domain or User).
  • For all dual AV modusGate, the Bitdefender AV engine now leverages Bitdefender’s Cloud to enhance anti-malware performance, detection rate, disinfection and reduce false positives.
  • New modusGate service called ModusSecurity which handles all anti-spoofing mechanisms (DMARC, SPF and DKIM).

 

                                                                                          IMPORTANT – PLEASE READ

 

All modusGate versions will no longer support MS SQL 2005 as of modusGate 6.4 and above. Microsoft has officially ended all support and security updates as of April 12, 2016. To ensure that modusGate utilizes the latest performance and security enhancements of MS SQL, we highly recommend you upgrade to MS SQL Server 2014. 

If you need help migrating your modusGate server or MS SQL database, please contact our Professional Services to schedule a time and cost estimate for your migration.

 

 

Change Logs: 

  • All SPF hard failures are now quarantined and releasable by the end-user via the QT Report or Web QT.
  • New setting to force HELO/EHLO identity upon an SPF verification.
  • Upgraded to the latest Mailshell SDK version 8.0.6 which improves detection of ideographic symbols in URLs and domains, including several bug fixes.
  • All RSS feeds, antivirus updates and license validation now will be performed over HTTPS by default.
  • Increased DKIM (outbound) signing length to 1024 (Key Size) by default.
  • Removed SHA1 (RFC4870 signs using rsa-sha1) from our DKIM (outbound).
  • modusGate now will reject messages with multiple From headers. This setting is on by default.
  • Issue fixed where Shared mailboxes on Exchange were set to disabled by default. They are now set to enabled.
  • directQuarantine loading issue fixed with Outlook 2016 updated with version 1702 Build 787020.
  • Issue fixed where the categories associated with After-Scanning where not displayed in the quarantine.
  • Issue fixed where Target Phishing emails are not displayed in quarantine reports.
  • Issue fixed where any user on the network would have access to WebMonitor.
  • modusGate does not support Port 465 to populate with SMTP.
  • Removed Real Time Whitelist verification servers from modusGate.
  • Bitdefender license key has been updated and also incorporates an updated mechanism.
  • Update Bitdefender SDK to version 3.0.0.144.

 

Operational Considerations:

1. The new ModusSecurity service will take 200 MB to 400 MB of additional RAM on the server. 

2. Since modusGate relies on IP reputation data, it needs to see the IP address of the originating server to be able to make a proper judgement on the spamminess of a message. If modusGate is not the first server to receive email from the outside world, please contact our support team so that they can assist you in configuring your system.

3. As of modusGate 6.x our anti-spam engine SCAV2 requires that the UDP port 53 and TCP port 80 to remain open to properly filter emails. These ports are needed for both outbound and inbound traffic from the modusGate. If you require a list of IP’s to our servers, you may contact our support team for the complete list.

4. If your modusGate is configured to perform outbound filtering the following steps are needed to:

  •   Go the following folder …Vircom\modusGate\SCAV2
  •   Open the file called "spamcatcher.conf"
  •   Search for the parameter called "ignored_ip_list"
  •   Remove the # character and enter the IP of the mail server the emails are being filtered from. 

                  ie: ignored_ip_list=192.168.0.179

5. Save and Restart moduscan service.

 


Known Issues:

Description

Workaround

If downgrading from 6.4 to 6.3 the 6.3 installer will not be able to stop modusSecurity service and the downgrade will not be performed.

      Before downgrading stop the ModusSecurity service manually via Microsofts Component Services.

dQ Outlook clients are not able to connect to dQ server. Verify if the server’s localhost if is mapped to an IPV6 address.

1.    Locate the directQuarantine Server.exe.config file

2.   Change all "localhost" addresses to "127.0.0.1" and save the file

3.  Restart the directQuarantine service.

The upgrade process may be interrupted with an error window, labelled “Update Error” followed by 4 similar errors. At this point the installer will terminate and the upgrade is incomplete.

This issue may only presents itself when the server running modusGate is low on system resources. Which may impact SQL processes to run optimally during the upgrade.

 

1.    Select “OK” button on all installer error pop-ups.

2. Kill all installer processes if still running.

     3. Stop processes that may be taking up a lot of the server’s resources.

     4. Stop “ModusScan” service from Windows Service manager.

     5. Restart the installer and complete the upgrade.

 

 



 

Support:

Web:            http://www.vircom.com/support  
Phone:         1-888-484-7266
Email:          
support@vircom.com


Trademarks

Vircom, Email Security Grader, Email Security Matters, SysAdmin on the Line, NetAdmin on the Line, modus, modusMail and modusGate are trademarks of Vircom Inc. Windows and Exchange are registered trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners.


 

 

  
1.1.2.2. modusMail
New in modusMail 6.4

This latest release of modusMail 6.4 includes the following:


Highlights:
  •        For all dual AV modusMail, the Bitdefender AV engine now leverages Bitdefender’s Cloud to enhance anti-malware performance, detection rate, disinfection and reduce false positives.

 

                                                                                         IMPORTANT – PLEASE READ

All modusMail versions will no longer support MS SQL 2005 as of modusMail 6.4 and above. Microsoft has officially ended all support and security updates as of April 12, 2016. To ensure that modusMail utilizes the latest performance and security enhancements of MS SQL, we highly recommend you upgrade to MS SQL Server 2014. 

If you need help migrating your modusMail server, please contact our Professional Services to schedule a time and cost estimate for your migration.

 

Change Logs:

  • All RSS feeds, antivirus updates and license validation now will be performed over HTTPS by default.
  • directQuarantine load issue fixed with Outlook 2016 updated with version 1702 Build 787020.
  • Issue fixed where the categories associated with After-Scanning where not displayed in the quarantine.
  • Issue fixed where Target Phishing emails are not displayed in quarantine reports.
  • Increased DKIM (outbound) signing length to 1024 (Key Size) by default.
  • Removed SHA1 (RFC4870 signs using rsa-sha1) from our DKIM (outbound).
  • Removed Real Time Whitelist verification serves from modusMail.
  • Bitdefender license key has been updated and also incorporates an updated mechanism.
  • Updated Mailshell SDK to version 8.0.5.
  • Updated Bitdefender SDK to version 8.0.6.

 

Operational Considerations:

1. Since modusMail relies on IP reputation data, it needs to see the IP address of the originating server to be able to make a proper judgement on the spamminess of a message. If modusMail is not the first server to receive email from the outside world, please contact our support team so that they can assist you in configuring your system.

2. As of modusMail 6.x our anti-spam engine SCAV2 requires that the UDP port 53 and TCP port 80 to remain open to properly filter emails. These ports are needed for both outbound and inbound traffic. If you require a list of IP’s to our servers, you may contact our support team for the complete list.

3. If your firewall is configured with specific inbound/outbound rules for our anti-spam and antivirus update servers, you will need to add some additional addresses for modusMail 6.2 and higher. Please contact our support team for the addresses.

 

Known Issues: 

 

The upgrade process maybe interrupted with an error window, labelled "Update Error" followed by 4 similar errors. At this point the installer will terminate and the upgrade is incomplete.

The issue may only presents itself when the server running modusMail is low on system resources. Which may impact SQL processes to run optimally during the upgrade.

 


- Select "OK" button on all installer error pop-ups.

- Kill all installer processes if still running.

- Stop processes that maybe taking up a lot of the server's resources.

- Stop "ModusScan" service from Windows Service manager.

- Restart the installer and complete the upgrade.


 

Support:    

Web:               http://www.vircom.com/support
Phone:            1-888-484-7266
Email:            
support@vircom.com


Trademarks

Vircom, Email Security Grader, Email Security Matters, SysAdmin on the Line, NetAdmin on the Line, modus, modusMail and modusGate are trademarks of Vircom Inc. Windows and Exchange are registered trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners.


 


1.1.2.3. Customizing Webmail/WebQuarantine 5.13 (new installs)

Product: All

Version & Build: 5.13



Important: When upgrading to Modus 5.13 the default "Vircom" theme will be applied. Please follow steps below to make the appropriate changes to your custom pages.


The following customization information can be used with both ModusMail and ModusGate - where applicable.

There are many levels of customization that you can make for the web interface, depending on what you want to do:

  • you can substitute your company logo for the Vircom logos (which appear on the login and on each web page)
  • you can modify attributes of the Vircom theme such as the color or the size of the text
  • you can bypass Vircom's login page and have your users access their webmail through your own portal
  • you can create a completely different theme for the web interface that bears no resemblance to the Vircom theme - this theme will not be overwritten by future upgrades, BUT any interface enhancements made by Vircom will not be reflected in your custom-built interface. We provide only very basic customization information here: we provide enough information that if you know what you're doing, you'll know how to support your own customizations and you can go ahead and build your own interface.

Note: The web.config and style.css files contain the product default values. Never alter these files because any work you do will be lost upon upgrading the software. Change the custom.config and custom.css files instead. A Modus upgrade will not overwrite these files, except that it will set back the DefaultTheme to Vircom. This is needed because major changes have been done in the styles for this version.  Please note also that Vircom Technical support cannot debug any custom interfaces you build. We can support only basic style changes to the Vircom interface that include rebranding and recoloring (changing images and modifying CSS styles).

Custom.Config Basic Functionality Customization

NOTE: Any modifications you make in the custom.config file will require you to Stop/Start the IIS Admin service after you have finished.

1. The default language of the WebMail interface is defined in this key. The value must match an existing folder under Locales.

<add key="DefaultLanguage" value="en"></add>

2. The default theme of the WebMail interface is defined in this key. The value must match an existing theme folder under Themes.

<add key="DefaultTheme" value="vircom"></add>

3. This is the domain name or IP address of your WebMail Server service.

<add key="WebMailServerAddress" value="localhost"></add>

4. This is the port number of your WebMail Server service.

<add key="WebMailServerPort" value="31804"></add>

5. This is the character set in which the page will be displayed.

<add key="Charset" value="iso-8859-1"></add>

6. This is the path of the temporary folder that the installation program configures automatically.

<add key="Temp" value=""></add>

7. This is the path of the log folder that the installation program configures automatically.

<add key="LogDir" value=""></add>

8. This is the relative path and file name of the Login page. If you want to design your own login page or you want to integrate webmail with your portal, change this value to your to the relative path and file name of your custom-designed login page. When logging off, users will be redirected to this page instead of the main webmail login page.

<add key="LoginPage" value="Login.aspx"></add>

9. This is the name of the application that will be shown in the browser windows title bar.

<add key="Title" value="Webmail"></add>

10. This option determines whether WebMail should parse messages to find out if there is an attachment.

<add key="ShowPaperClip" value="false"></add>

NOTE: When this option is turned on, you might encounter performance drops for POP3 accounts since the message must be downloaded completely. This does not affect IMAP4 accounts. Set the value to "true" to enable or to "false" to disable it.

11. This option determines whether users can specify the email address that will be shown in the From field of outgoing emails.  Turn on this option with caution since it allows users to enter any email address.

<add key="AllowChangeFromAddress" value="false"></add>

Set the value to "true" to enable or to "false" to disable it.

Logos

In the custom.config file, you can set the image and hyperlink for the Login logo and the top menu logo.  These images must exist in your selected theme in order to work.

<add key="LoginLogoUrl" value="http://www.vircom.com"></add>
<add key="511LoginLogoImage" value="LogoLogin.gif"></add>
<add key="MenuLogoUrl" value="
http://www.vircom.com"></add>
<add key="511MenuLogoImage" value="LogoMenu.gif"></add>

Custom Login Page or Portal Integration

You can create your own login page or insert the login form in your portal.  Your login page should include a form with the two following form fields:

<input type="text" name="txtLogin"/>
<input type="password" name="txtPassword"/>

The page's form action should be set to "Login.aspx" and the method set to "POST".  Here's a simple Login page:

<html>
<body>
<form action="Login.aspx" method="POST">
<input type="text" name="txtLogin"/>
<input type="password" name="txtPassword"/>
<input type="submit" value="Login"/>
</form>
</body>
</html>

Theme Customization

The WebMail application theme is made through a main CSS file (and if you vary functionality between domains, you'll also need a customized .config file).  DO NOT alter the Style.css file or the Web.config file (or will you will lose all your work when you perform a Modus upgrade).  Instead, you must redefine colors, fonts, and other attributes in the Custom.css, and any functionality variations (see config file attributes above) in the custom.config files.

Any changes you make to the custom files will override the values in the style.css and web.config files.

For domain customization, create css and config files and name them according to the domain, for example:

  • domain.com.css (which should be saved in your custom theme directory)

  • domain.com.config (which should be saved in the webroot directory)

  • domain.net.css (which should be saved in your custom theme directory)

  • domain.net.config (which should be saved in the webroot directory)

These domain files will override the custom.css and custom.config files which override the main style.css and web.config files.

NOTE: you only have to create a domain customized config file if you want to vary functionality between domains as well as the look and feel of it. Otherwise only create a domain customized .css file for your theme.

Changing the Login page color

The login page orange color constitutes of an image (Login_RoundBorder.gif) and a table cell. For example, to change the color to lightgrey:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #tdLoginRight
    {
    background-color: lightgrey;
    }

4. Save and close the file

Note that unless you change the Login_RoundBorder.gif image to lightgrey, it will look odd, so you can edit that file in an image editor or you can hide it altogether. To do so, add the following lines in the custom.css right after the lines previously added: #tdLoginMiddle

    #tdLoginMiddle
    {
    display: none;
    }

Changing the Top Menu color:

The top menu constitutes of an image (LogoMenu.gif) which is configured in the custom.config file, and a gradient image of 1 pixel width. The gradient image adds a level of depth to the menu bar while preserving a very small file size. If you want to change the gradient coloring, open the GradientMenu.gif file in an image editor such as Gimp, PaintShopPro or Photoshop and change the color or gradient value of the image to your preference. You can also discard the gradient in the top menu and only use a solid color, such as lightgrey. To do this:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .Menu
    {
    background-color: lightgrey;
    background-image: none;
    }


4. Save the file

Changing the lists hover color:

Each message status has a separate class. This allows you to define different attributes for when an email is read, unread or deleted. In order to change the hover color, you will need to change each of these classes:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .dgListItemHover
    {
    background-color: lightgrey;
    }
    .dgListItemUnreadHover
    {
    background-color: lightgrey;
    }
    .dgListItemDeletedHover
    {
    background-color: lightgrey;
    }

4. Save the file

Changing the background color of all panels:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .MessageViewMsgHeader,
    .SettingsAccount,
    .SettingsOption,
    .SettingsOptionGeneral,
    .SettingsFolders,
    .SettingsOptionsAntiSpam,
    .SettingsOptionsAntiVirus,
    .SettingsOptionsRules,
    .SettingsOptionsAutoReply,
    .SettingsContacts,
    .SettingsOptionsHome,
    .SettingsOptionsBusiness,
    .SettingsTrusted,
    .SettingsBlocked,
    .SettingsOptionsBlocked,
    .SettingsOptionsTrusted,
    .SettingsAliases,
    .SettingsOptionsReporting,
    #divContactEditor_main,
    .DiagnosticContainer
    {
    background-color: lightgrey;
    }

4. Save the file


Hiding the Server Blocked/Trusted List from the Settings Page:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #Trustedlist_TableRowWhitelistServerTitle,
    #Trustedlist_TableRowWhitelistServerData,
    #Blockedlist_TableRowBlacklistServerTitle,
    #Blockedlist_TableRowBlacklistServerData
    {
    display:none;
    }

4. Save the file

 
 

modusMail only:


Removing Statistics (or other major menu items)

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 Statistics menu option from the web interface.

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #tdStatistics
    {
    display: none;
    }

4. Save the file

NOTE: these instructions apply to the other menu items: #tdAddressBook, #tdFolders, #tdSettings, #tdLogoff. Change the syntax for the line in step 3 from <#tdStatistics> to the menu item you want to hide.

Hiding Sections in Settings:

As with the login page, it is possible to hide certain parts of the page. This is especially useful if you don't want your users to access particular types of settings.

Hiding the options section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsOptions
    {
    display: none;
    }

4. Save the file

Hiding the email filtering section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsFiltering
    {
    display: none;
    }

4. Save the file

Hiding the user contact information section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsUserInfo
    {
    display: none;
    }

4. Save the file

Hiding the rules section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsRules
    {
    display: none;
    }

4. Save the file

Hiding the auto-reply section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAutoreply
    {
    display: none;
    }

4. Save the file

Hiding the external accounts section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAccounts
    {
    display: none;
    }

4. Save the file

Hiding the aliases section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAliases
    {
    display: none;
    }

4. Save the file

Webmail Message Customization

You can customize your own webmail messages (what we call "strings") - this could be especially useful for foreign language support if the translation provided does not adequately communicate an action or system response.

Each language has its own strings file stored in:

..."Vircom"Web"WebRoot"Locales

There is a strings.xml file - the default translations provided with Webmail - and a custom.xml file. Make your changes in the custom.xml file (as follows in the instructions below) and this file will override strings.xml.

Changing default strings

1. Go to the language folder whose messages you want to customize and open both the strings.xml and the custom.xml files

2. Copy and paste the strings to be customized from the strings.xml file into the custom.xml file

3. Modify the strings in the custom.xml file and save it.

4. You can also include HTML formatting instructions in the custom.xml file to specify how you want the customized strings to be displayed. This is useful, for instance, for the TEXT1000 & TEXT1001 tags which are shown at the top and bottom of the right-hand side of the login page respectively (where the beta version information and the upcoming features information was previously displayed).

5. Save the strings.xml file as well to change its timestamp so that the changes you have made can be viewed immediately (not changing the timestamp on the strings.xml file will mean that the customized strings are not shown until you restart IIS).

1.1.2.4. Customizing Webmail/WebQuarantine (Upgrades)

Product: All

Version & Build: 5.13



Important: Before the process of upgrading from 5.0, 5.1 to 5.13 some folder and file changes are required for the customization.  Please perform the following steps before the upgrade is done.


MODUSGATE INSTRUCTIONS:

1.  Locate the appropriate root installation folder for the Quarantine files, e.g. C:\Program Files\Vircom\Web\Quarantine

2. Open up the directory WebRoot\Themes

3. In this directory you will find three or more folders named Gray, Vircom, and your own Custom folder which contains your customization images and styles. Note that we will use the folder name Custom for the rest of this article while your custom folder could have a different name.

4. Rename the Vircom folder to Vircom1.

5. Next make a copy of your Custom folder (for backup purposes) and rename your original Custom folder to Vircom.  Your Themes folder should look like:

 

6. The reason for this is that Modus 5.12 only checks the default Vircom folder for all the style changes.

7. Open up your new custom folder named Vircom.

8. In this directory you will find the customization files named style.css and custom.css.

9. If your customized pages have some custom colors, there is a good chance that you had made these changes in the style.css file. If you know your customizations were made in the custom.css file then proceed to step 12.

10. If you made changes to the style.css file, open it and copy those changes onto the clipboard (CTRL-C).

11. Open the custom.css file in the same directory and paste the clipboard contents into it (CTRL-V).  Save your changes and close both files.  custom.css should now contain your customizations.


12. Once all this is has been done, you can now launch the upgrade for version 5.12.

13. Once the install is complete, open the custom.config file located in c:\Program Files\Vircom\Web\Quarantine\WebRoot folder.

14. There are 2 lines which need to be modified. Both lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

15. Restart Modus Webmail service and IIS. Your customizations should be visible.


MODUSMAIL INSTRUCTIONS:

1. Download and install Modus 5.12.

2. Once the install is complete, open the custom.config file located in C:\Program Files\Vircom\Web\WebMail\WebRoot (assumes a default install location).  

3. There are 3 lines of code which need to be modified. All 3 lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines -<add key="DefaultTheme" value="Vircom"/>.

TO

<add key="DefaultTheme" value="CUSTOM"/>

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

4. Restart Modus Webmail service and IIS. Your customizations should be visible.


1.1.2.5. Configuring Exchange on Windows Small Business Server to listen on an alternate port (25)
Product: modusGate
Version & Build: all

If you're interested in getting modusGate running on the same system as Microsoft Exchange (example, on a Windows Small Business server), with both of them co-existing on the same machine, you cannot have modusGate & Exchange both listening on the same SMTP port 25. 



What you want to do is have modusGate listen on port 25 and it would redirect the traffic to the local exchange server on an alternate port (usually 26).
 
This being said, how do you get Microsoft Exchange to listen on port 26?
 
 
On Exchange 2007 and 2010:
 
 
You can change the receive connector port thus:

1. Go to the Exchange Management Console under Hub Transport
2. Select thereceive connector name you want to change
3. Click on properties
4. Select “network”
5. Choose local IP address
6.  Edit the Receive Connector Bindings
7.  Change the port to the desired port to listen on for SMTP traffic (ex: 26)
 
 

Optional: You can restrict who can send to this SMTP server by editing the “receive mail from remote servers which have these IP addresses”. In this case, you could restrict it to 127.0.0.1 if you want to allow inbound port 26 traffic to only come from modusGate which is sitting on the same box.
 
 
On Exchange 2000 and 2003:
 
 
1. Start the Exchange System Manager.
2. Select the Servername you want to change.
3. Click on Protocols
4. Click  on SMTP
5. Right-click the Default SMTP Virtual Server object
6. Click Properties.



7. On the General tab click the Advanced button
8. Click the Edit button
9. Set the TCP port to desired port (ex: 26).
 
 
 
 
On Exchange 5.5:

 
To change the SMTP listening port on a server that is running Exchange 5.5 from port 25 to another port (for example: port 26) follow these steps:

1.  Open the Control Panel
2. Select Administrative Tools
3. Select Services
4. Stop the Exchange Server Internet Mail service.
5. Open the file c:\Winnt\System32\Drivers\Etc\Services using notepad
6. Locate the line containing: "smtp 25/tcp mail" and change the 25 to 26.
7. Save the Services file.
8. Start the Exchange Server Internet Mail service.


1.1.2.6. Customizing Webmail/WebQuarantine (Upgrades)

Product: All

Version & Build: 5.31 +


modusGate 5.42 includes a brand new quarantine interface.  Customizations of this new interface  is not compatible with prior versions.

You will find your previous WebQuarantine installation and any customization done is still available via the QuarantinePre5-30 virtual directory.

MODUSGATE INSTRUCTIONS:

1.  Locate the appropriate root installation folder for the Quarantine files, e.g. C:\Program Files\Vircom\Web\WebQuarantine

2. Open up the file custom.config

3. At the end of the file, you will find the following lines, each of them denote a configurable setting for WebQuarantine.

  <add key="LoginLogoUrl" value="http://www.vircom.com" />
  <add key="LoginLogoImage" value="logo-login.png" />
  <add key="FooterLoginLogoUrl" value="http://www.vircom.com" />
  <add key="FooterLoginLogoImage" value="footer-logo-login.png" />
  <add key="MobileLoginLogoUrl" value="http://www.vircom.com" />
  <add key="MobileLoginLogoImage" value="logo2.png" />
  <add key="MobileFooterLoginLogoUrl" value="http://www.vircom.com" />
  <add key="MobileFooterLoginLogoImage" value="logo-vircom.png" />
  <add key="MobileMenuLogoImage" value="logo.png" />
  <add key="MenuLogoUrl" value="http://www.vircom.com" />
  <add key="MenuLogoImage" value="logo.png" />
  <add key="FooterLogoUrl" value="http://www.vircom.com" />
  <add key="FooterLogoImage" value="logo-vircom.png" />

4. To use your own logo, change the Image values to your own logo filename, for example:

To change Login page logo, change


  <add key="LoginLogoImage" value="logo-login.png" />

To:

  <add key="LoginLogoImage" value="my-logo-login.png" />

And put your new logo file in the WebRoot\Wres\img folder.

Mobile logos needs to be put in WebRoot\Wres\mobile\images

5. Change the matching Url value to your desired URL.

6. To customize other attributes such as colors, font type, etc, you can overwrite any CSS rules in the file located at WebRoot\Wres\custom\custom.css

MODUSMAIL INSTRUCTIONS:

1. Download and install Modus 5.42.

2. Once the install is complete, open the custom.config file located in C:\Program Files\Vircom\Web\WebMail\WebRoot (assumes a default install location).  

3. There are 3 lines of code which need to be modified. All 3 lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines -<add key="DefaultTheme" value="Vircom"/>.

TO

<add key="DefaultTheme" value="CUSTOM"/>

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

4. Restart Modus Webmail service and IIS. Your customizations should be visible.


1.1.2.7. modus Upgrade Checklist

 modus Upgrade Checklist

Introduction

         This document is intended for existing Vircom customers who are currently running an older version of ModusGate. You should read this document thoroughly before upgrading. If you have any questions or feel something is missing from this document, feel free to contact us by e-mail at support@vircom.com.


Before upgrading, please ensure that you have met the following requirements:


  • Backup your databases (QT, Audit, Monitoring and Sieve) before launching the upgrade
  • Ideally, this should be a full backup
  • If you are using SQL Server Express, ensure that Full Text Indexing is installed
  • For instructions, please consult the following KB article:
  • http://kb.vircom.com/Kbase/default.asp?SID=&Lang=1&id=1621&Lang=1&SID=
  • Ensure that .Net 3.5 Framework is installed
  • For more information, consult the following Microsoft® websites:
  • Microsoft .NET Framework Version 3.5
  • Ensure that you have your current installation package
  • In the event that you must roll back after upgrading, keep a copy of the *.exe installation file
  • If you do not have a copy of the file, before upgrading, send an email to: support@vircom.com requesting it
  • Backup your Windows Registry
  • On the modus server, click on Start > Run
  • Type regedit to open the Registry Editor
  • In the Registry Editor, click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup any customized quarantine reports and/or web applications folders
  • Read the Release Notes for all new features and changes to modus, especially the section regarding encryption

If you opt to use encryption, there is a sieve script that must be added to prevent issues with foreign languages for outbound messages. This script is included in the Release Notes.


Upgrading modusMail/modusGate to v6.0 

         Due to a series of architectural changes in versions upgrading from version 4.7 must be done in two steps:

        1. upgrade from v4.7 to v 5.0 or v5.1

        2. upgrade directly to v6.0

If you are running any version higher the 5.1 you can directly upgrade to v6.0.


Changes to the installation process:

         Starting from v5.31 ModusGate comes with a new web interface. The new interface will not overwrite your existing WebQuarantine programs. This will allow you to continue using the 'old' site until you have had time to test and/or customize the new one.

ModusGate Web Quarantine information:

         There will be a new folder created called WebQuarantine locate under C:\Program Files(x86)\Vircom\Web. This folder will contain the new websites attributes for the new web quarantine pages. The virtual directory will still exist in IIS.


IMPORTANT:

          If you plan to use the monitoring feature, it is preferable to use a Microsoft SQL database instead of the native Access format. Whether to use Microsoft Access or Microsoft SQL depends on your volume of traffic. A good rule of thumb would be to use your quarantine database as your guide: if you use SQL for the quarantine, then you should use it for the monitoring stats as well.


Upgrading ModusGate

Upgrading requires a certain number of precautions. The most important is doing a backup before upgrading:

  • Make sure you have access to your old Modus installation package in case you need to rollback. If you do not have a copy, click on the help -> about button in your ModusGate console to find out what version you have and the build number; contact us by email, and we will be happy to provide you with the original install package.
  • Backup your configuration: - Open the ModusGate administration console and select File > Backup configuration - Select the path where the configuration file will be stored (*.reg file) - Keep this registry file (*.reg) in a safe location as a backup of your Modus configuration.
  • Backup the Registry: - Open the Registry Editor (regedit) - Click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup the Web directory: Located under...\Vircom\Web
  • Backup the databases: Normally located under the root installation of SQL \\Microsoft SQL Server\MSSQLXX.SQLEXPRESS\MSSQL\DATA
  • Proceed with the upgrade.


Upgrading ModusMail

Upgrading requires a certain number of precautions. The most important is doing a backup before upgrading:


Steps to take before upgrading:
  • If you have the hardware and software capability, it would be best to mirror your existing machine so you could hot-swap (switch the IP addresses over) should the upgrade fail. However, in the event that you cannot mirror your server, proceed with the following:
  • Make sure your datasource is up-to-date. If you are using an external datasource for authentication (such as a billing package), ensure that it is up-to-date.
  • Note: If you are using Platypus or RODOPI, check with Boardtown or RODOPI to find out if a new stored procedure is required. In any event, you should run the latest stored procedures for ModusMail.
  • Make sure you have access to your old Modus installation package in case you need to rollback. If you do not have a copy, click on the help -> about button in your ModusMail console to find out what version you have and the build number; contact us by email, and we will be happy to provide you with the original install package.
  • Backup your configuration:

         - Open the ModusMail administration console and select File -> Backup configuration

         - Select the path where the configuration file will be stored (it will be a .reg file)

         - Keep this registry file (*.reg) in a safe location as a backup of your Modus configuration

  • Backup your registry:

         - Open the Registry Editor (regedit)

         - Click on File > Export

         - Select the file location, enter a name for the backup file and click OK

  • Backup the Web directory: Located under...\Vircom\Web
  • Backup the databases: Normally located under the root installation of SQL \\Microsoft SQL Server\MSSQLXX.SQLEXPRESS\MSSQL\DATA
  • Proceed with the upgrade. 

After upgrade is done please ensure that Modus antivirus engines are up and running:

  • In Advanced console go to Virus Tab and see that both AV were successfully updated with the latest version.
  • Go to System Tab and see that all Modus services are up and running.
  • Note! It could take up to 5 minutes to modus to download and install latest versions of antivirus engine and definitions.
  • Customer may use Email flow diagnostic tool provided with modus installation to verify the legit and spam mail flow.







 


 

1.1.3. Version 6.3
Important information about upgrading to modus 6.3
 

System Requirements:
        

Operating System: Windows Server 2008 (32 and 64-bit), 2008R2, 2012, 2012R2 and Windows Small Business Server (SBS) 2008 x64 and 2011 x64. Windows Web Edition is not supported.

 Web Server: IIS version 7.0 or later.

Components: MDAC 2.8 SP1 or higher, .NET Framework 3.5 SP1 and 4.5 

Exchange Integration: Microsoft Exchange 2007/2010/2013/2016. 

SQL Server: 2008 x86/x64, 2008R2, 2008 Express Edition, SQL 2012 x86/x64, SQL 2014 x86/x64.

Microsoft Office: Microsoft Office 2007, 2010, 2013, 2016 (This only applies to directQuarantine client application.)

Web Browsers:

Desktop: Internet Explorer 9+, Chrome 30+, Safari 7+, or Firefox 25+

Mobile*: iOS Safari 4.0+ (4x, 5.x), Android Browser 4.0+ (4.x, 5.x), Chrome 30+

* Note that the mobile web browsers only apply to the Web Quarantine.


Change Logs
 
See the modusMail / modusGate pages below for their respective change logs and list of fixes. 

1.1.3.1. modusGate
New in modusGate 6.3


This latest release of modusGate 6.3 includes several security improvements and overall maintenance fixes.

 

Highlights: 

 

  • modusGate antispam engines have been improved and modusGate now supports protection against Targeted Phishing (Enabled by default).
  • modusGate Audit functionality has been replaced by a new Message Log functionality that allows to quickly identify what happened to a specific email (Delivered, Rejected, Quarantined, etc…).
  • Installation process is now validating that modusGate is able to reach all of the required virus and spam update servers and will warn the user if there is an issue.
  • When using modusGate with Exchange, Group managers and co-managers of an email distribution list have now have access to the quarantine via WebQuarantine.
  • In the Web/WebAdmin-Privileges, there is a new option to allow Administrators to release viruses from quarantine using the WebAdmin interface.
  • In order to continue to improve modusGate user interfaces, web components will now send analytics to Vircom.
  • modusGate now allows to force server authentication for outgoing emails. 
  • Extended the support of Archives to support other archive formats then .zip such as .rar, 7zip, etc…
  • Made the location where modusGate Anti-Viruses decompress files configurable.
  • modusGate now supports domain names for RBL exclusion list.
  • In the Security/DNSBL panel, added an option (Enabled by default) to reject email only after the recipient information is obtained. This provide the ability to log who the intended recipients were in the new Message Log functionality.
  • Many SPF improvements (support of truncated record. 

 

                                                                                          IMPORTANT – PLEASE READ

 

To ensure your email servers remain fully protected as of January 01, 2017, all modusGate versions running on Microsoft Windows 2003 server must be migrated to Windows 2008 server or higher. This is due to SHA1 certificates being deprecated across the Internet. Starting January 01, 2017 all modusGate servers will no longer receive any antivirus or antispam definitions. Please see this KB article for further details.

If you need help migrating your modusGate server, please contact our Professional Services to schedule a time and cost estimate for your migration.

 

 

Change Logs: 

  • Updated with new Bitdefender license key. (Applies only to Dual AV packages 6.x.xxx-ASAB.exe). 
  • Fixed a bug with dQ Client not working with Outlook 2016 running version 1702 (Build 7870.2020)
  • Option to "Generate Now" from Web Quarantine has been re-added.
  • Detection of OLE2 objects within Office Documents has been removed as it was creating too many False Positives.
  • Validate Sender Addresses functionality in Security/SMTP Security tab has been removed as it has been superseded by SCAv2 functionality.
  • Fixed a ModusScan crash upon processing multiple emails embedded.
  • Improved support of apostrophe character for Trusted and Blocked Senders.
  • Improved display support of Arabic characters in Quarantine (Advance Console and WebAdmin).
  • Fixed test route button when User Domain name is not an email address.
  • Fixed a problem when adding email address to "Reject all incoming mail from these addresses".
  • Fixed a problem when Web components were not running on the same server as modusGate. Op

 

Operational Considerations:

1. While modusGate 6.3 is backward compatible with previous versions of directQuarantine Outlook plug-in, it is strongly recommended to update to the latest version to benefit of the new functionality and fixes.

2. Since modusGate relies on IP reputation data, it needs to see the IP address of the originating server to be able to make a proper judgement on the spamminess of a message. If modusGate is not the first server to receive email from the outside world, please contact our support team so that they can assist you in configuring your system.

3. As of modusGate 6.x our anti-spam engine SCAV2 requires that the UDP port 53 and TCP port 80 to remain open to properly filter emails. These ports are needed for both outbound and inbound traffic from the modusGate. If you require a list of IP’s to our servers, you may contact our support team for the complete list.

4. If your modusGate is configured to perform outbound filtering the following steps are needed to:

  •   Go the following folder …Vircom\modusGate\SCAV2
  •   Open the file called "spamcatcher.conf"
  •   Search for the parameter called "ignored_ip_list"
  •   Remove the # character and enter the IP of the mail server the emails are being filtered from. 

                  ie: ignored_ip_list=192.168.0.179

 

  •   Save and Restart moduscan service.

 

5. If your firewall is configured with specific inbound/outbound rules for our anti-spam and antivirus update servers, you will need to add some additional addresses for modusGate 6.2 and higher. Please contact our support team for the addresses. 

 

Known Issues:

 

The upgrade process maybe interrupted with an error window, labelled "Update Error" followed by 4 similar errors. At this point the installer will terminate and the upgrade is incomplete.

The issue may only presents itself when the server running modusGate is low on system resources. Which may impact SQL processes to run optimally during the upgrade.

 


- Select "OK" button on all installer error pop-ups.

- Kill all installer processes if still running.

- Stop processes that maybe taking up a lot of the server's resources.

- Stop "ModusScan" service from Windows Service manager.

- Restart the installer and complete the upgrade.

 

Support:

Web:            http://www.vircom.com/en/support/customer-service/  
Phone:         1-888-484-7266
Email:          
support@vircom.com


Trademarks

Vircom, Email Security Grader, Email Security Matters, SysAdmin on the Line, NetAdmin on the Line, modus, modusMail and modusGate are trademarks of Vircom Inc. Windows and Exchange are registered trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners.


 

 

  
1.1.3.2. modusMail
New in modusMail 6.3

This latest release of modusMail 6.3 includes several security improvements and overall maintenance fixes.


Highlights:
  • modusMail antispam engines have been improved and modusMail now supports protection against Targeted Phishing (Enabled by default).
  • Extended the support of Archives to support other archive formats then .zip such as .rar, 7zip, etc… 
  • Made the location where modusMail Anti-Viruses decompress files configurable.
  • modusMail now support domain name for RBL exclusion list. 
  • Many SPF improvements (support of truncated record). 

 

                                                                                         IMPORTANT – PLEASE READ

To ensure your email servers remain fully protected as of January 01, 2017, all modusMail versions running on Microsoft Windows 2003 server must be migrated to Windows 2008 server or higher. This is due to SHA1 certificates being deprecated across the Internet. Starting January 01, 2017 all modusMail servers will no longer receive any antivirus or antispam definitions. Please see this KB article for further details. 

If you need help migrating your modusMail server, please contact our Professional Services to schedule a time and cost estimate for your migration.

 

Change Logs:

  • Updated with new Bitdefender license key. (Applies only to Dual AV packages 6.x.xxx-ASAB.exe). 
  • Fixed a bug with dQ Client not working with Outlook 2016 running version 1702 (Build 7870.2020) 
  • Detection of OLE2 objects within Office Documents has been removed as it was creating too many False Positives. 
  • Validate Sender Addresses functionality in Security/SMTP Security tab has been removed as it has been superseded by SCAv2 functionality.
  • Fixed a ModusScan crash upon processing multiple emails embedded.
  • Improved support of apostrophe character for Trusted and Blocked Senders.
  • modusMail Admin guide updates. 

 

Operational Considerations:

1. Since modusMail relies on IP reputation data, it needs to see the IP address of the originating server to be able to make a proper judgement on the spamminess of a message. If modusMail is not the first server to receive email from the outside world, please contact our support team so that they can assist you in configuring your system.

2. As of modusMail 6.x our anti-spam engine SCAV2 requires that the UDP port 53 and TCP port 80 to remain open to properly filter emails. These ports are needed for both outbound and inbound traffic. If you require a list of IP’s to our servers, you may contact our support team for the complete list.

3. If your firewall is configured with specific inbound/outbound rules for our anti-spam and antivirus update servers, you will need to add some additional addresses for modusMail 6.2 and higher. Please contact our support team for the addresses.

 

Known Issues: 

 

The upgrade process maybe interrupted with an error window, labelled "Update Error" followed by 4 similar errors. At this point the installer will terminate and the upgrade is incomplete.

The issue may only presents itself when the server running modusMail is low on system resources. Which may impact SQL processes to run optimally during the upgrade.

 


- Select "OK" button on all installer error pop-ups.

- Kill all installer processes if still running.

- Stop processes that maybe taking up a lot of the server's resources.

- Stop "ModusScan" service from Windows Service manager.

- Restart the installer and complete the upgrade.


 

Support:    

Web:               http://www.vircom.com/en/support/customer-service/
Phone:            1-888-484-7266
Email:            
support@vircom.com


Trademarks

Vircom, Email Security Grader, Email Security Matters, SysAdmin on the Line, NetAdmin on the Line, modus, modusMail and modusGate are trademarks of Vircom Inc. Windows and Exchange are registered trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners.


 


1.1.3.3. Customizing Webmail/WebQuarantine 5.13 (new installs)

Product: All

Version & Build: 5.13



Important: When upgrading to Modus 5.13 the default "Vircom" theme will be applied. Please follow steps below to make the appropriate changes to your custom pages.


The following customization information can be used with both ModusMail and ModusGate - where applicable.

There are many levels of customization that you can make for the web interface, depending on what you want to do:

  • you can substitute your company logo for the Vircom logos (which appear on the login and on each web page)
  • you can modify attributes of the Vircom theme such as the color or the size of the text
  • you can bypass Vircom's login page and have your users access their webmail through your own portal
  • you can create a completely different theme for the web interface that bears no resemblance to the Vircom theme - this theme will not be overwritten by future upgrades, BUT any interface enhancements made by Vircom will not be reflected in your custom-built interface. We provide only very basic customization information here: we provide enough information that if you know what you're doing, you'll know how to support your own customizations and you can go ahead and build your own interface.

Note: The web.config and style.css files contain the product default values. Never alter these files because any work you do will be lost upon upgrading the software. Change the custom.config and custom.css files instead. A Modus upgrade will not overwrite these files, except that it will set back the DefaultTheme to Vircom. This is needed because major changes have been done in the styles for this version.  Please note also that Vircom Technical support cannot debug any custom interfaces you build. We can support only basic style changes to the Vircom interface that include rebranding and recoloring (changing images and modifying CSS styles).

Custom.Config Basic Functionality Customization

NOTE: Any modifications you make in the custom.config file will require you to Stop/Start the IIS Admin service after you have finished.

1. The default language of the WebMail interface is defined in this key. The value must match an existing folder under Locales.

<add key="DefaultLanguage" value="en"></add>

2. The default theme of the WebMail interface is defined in this key. The value must match an existing theme folder under Themes.

<add key="DefaultTheme" value="vircom"></add>

3. This is the domain name or IP address of your WebMail Server service.

<add key="WebMailServerAddress" value="localhost"></add>

4. This is the port number of your WebMail Server service.

<add key="WebMailServerPort" value="31804"></add>

5. This is the character set in which the page will be displayed.

<add key="Charset" value="iso-8859-1"></add>

6. This is the path of the temporary folder that the installation program configures automatically.

<add key="Temp" value=""></add>

7. This is the path of the log folder that the installation program configures automatically.

<add key="LogDir" value=""></add>

8. This is the relative path and file name of the Login page. If you want to design your own login page or you want to integrate webmail with your portal, change this value to your to the relative path and file name of your custom-designed login page. When logging off, users will be redirected to this page instead of the main webmail login page.

<add key="LoginPage" value="Login.aspx"></add>

9. This is the name of the application that will be shown in the browser windows title bar.

<add key="Title" value="Webmail"></add>

10. This option determines whether WebMail should parse messages to find out if there is an attachment.

<add key="ShowPaperClip" value="false"></add>

NOTE: When this option is turned on, you might encounter performance drops for POP3 accounts since the message must be downloaded completely. This does not affect IMAP4 accounts. Set the value to "true" to enable or to "false" to disable it.

11. This option determines whether users can specify the email address that will be shown in the From field of outgoing emails.  Turn on this option with caution since it allows users to enter any email address.

<add key="AllowChangeFromAddress" value="false"></add>

Set the value to "true" to enable or to "false" to disable it.

Logos

In the custom.config file, you can set the image and hyperlink for the Login logo and the top menu logo.  These images must exist in your selected theme in order to work.

<add key="LoginLogoUrl" value="http://www.vircom.com"></add>
<add key="511LoginLogoImage" value="LogoLogin.gif"></add>
<add key="MenuLogoUrl" value="
http://www.vircom.com"></add>
<add key="511MenuLogoImage" value="LogoMenu.gif"></add>

Custom Login Page or Portal Integration

You can create your own login page or insert the login form in your portal.  Your login page should include a form with the two following form fields:

<input type="text" name="txtLogin"/>
<input type="password" name="txtPassword"/>

The page's form action should be set to "Login.aspx" and the method set to "POST".  Here's a simple Login page:

<html>
<body>
<form action="Login.aspx" method="POST">
<input type="text" name="txtLogin"/>
<input type="password" name="txtPassword"/>
<input type="submit" value="Login"/>
</form>
</body>
</html>

Theme Customization

The WebMail application theme is made through a main CSS file (and if you vary functionality between domains, you'll also need a customized .config file).  DO NOT alter the Style.css file or the Web.config file (or will you will lose all your work when you perform a Modus upgrade).  Instead, you must redefine colors, fonts, and other attributes in the Custom.css, and any functionality variations (see config file attributes above) in the custom.config files.

Any changes you make to the custom files will override the values in the style.css and web.config files.

For domain customization, create css and config files and name them according to the domain, for example:

  • domain.com.css (which should be saved in your custom theme directory)

  • domain.com.config (which should be saved in the webroot directory)

  • domain.net.css (which should be saved in your custom theme directory)

  • domain.net.config (which should be saved in the webroot directory)

These domain files will override the custom.css and custom.config files which override the main style.css and web.config files.

NOTE: you only have to create a domain customized config file if you want to vary functionality between domains as well as the look and feel of it. Otherwise only create a domain customized .css file for your theme.

Changing the Login page color

The login page orange color constitutes of an image (Login_RoundBorder.gif) and a table cell. For example, to change the color to lightgrey:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #tdLoginRight
    {
    background-color: lightgrey;
    }

4. Save and close the file

Note that unless you change the Login_RoundBorder.gif image to lightgrey, it will look odd, so you can edit that file in an image editor or you can hide it altogether. To do so, add the following lines in the custom.css right after the lines previously added: #tdLoginMiddle

    #tdLoginMiddle
    {
    display: none;
    }

Changing the Top Menu color:

The top menu constitutes of an image (LogoMenu.gif) which is configured in the custom.config file, and a gradient image of 1 pixel width. The gradient image adds a level of depth to the menu bar while preserving a very small file size. If you want to change the gradient coloring, open the GradientMenu.gif file in an image editor such as Gimp, PaintShopPro or Photoshop and change the color or gradient value of the image to your preference. You can also discard the gradient in the top menu and only use a solid color, such as lightgrey. To do this:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .Menu
    {
    background-color: lightgrey;
    background-image: none;
    }


4. Save the file

Changing the lists hover color:

Each message status has a separate class. This allows you to define different attributes for when an email is read, unread or deleted. In order to change the hover color, you will need to change each of these classes:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .dgListItemHover
    {
    background-color: lightgrey;
    }
    .dgListItemUnreadHover
    {
    background-color: lightgrey;
    }
    .dgListItemDeletedHover
    {
    background-color: lightgrey;
    }

4. Save the file

Changing the background color of all panels:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .MessageViewMsgHeader,
    .SettingsAccount,
    .SettingsOption,
    .SettingsOptionGeneral,
    .SettingsFolders,
    .SettingsOptionsAntiSpam,
    .SettingsOptionsAntiVirus,
    .SettingsOptionsRules,
    .SettingsOptionsAutoReply,
    .SettingsContacts,
    .SettingsOptionsHome,
    .SettingsOptionsBusiness,
    .SettingsTrusted,
    .SettingsBlocked,
    .SettingsOptionsBlocked,
    .SettingsOptionsTrusted,
    .SettingsAliases,
    .SettingsOptionsReporting,
    #divContactEditor_main,
    .DiagnosticContainer
    {
    background-color: lightgrey;
    }

4. Save the file


Hiding the Server Blocked/Trusted List from the Settings Page:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #Trustedlist_TableRowWhitelistServerTitle,
    #Trustedlist_TableRowWhitelistServerData,
    #Blockedlist_TableRowBlacklistServerTitle,
    #Blockedlist_TableRowBlacklistServerData
    {
    display:none;
    }

4. Save the file

 
 

modusMail only:


Removing Statistics (or other major menu items)

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 Statistics menu option from the web interface.

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #tdStatistics
    {
    display: none;
    }

4. Save the file

NOTE: these instructions apply to the other menu items: #tdAddressBook, #tdFolders, #tdSettings, #tdLogoff. Change the syntax for the line in step 3 from <#tdStatistics> to the menu item you want to hide.

Hiding Sections in Settings:

As with the login page, it is possible to hide certain parts of the page. This is especially useful if you don't want your users to access particular types of settings.

Hiding the options section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsOptions
    {
    display: none;
    }

4. Save the file

Hiding the email filtering section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsFiltering
    {
    display: none;
    }

4. Save the file

Hiding the user contact information section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsUserInfo
    {
    display: none;
    }

4. Save the file

Hiding the rules section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsRules
    {
    display: none;
    }

4. Save the file

Hiding the auto-reply section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAutoreply
    {
    display: none;
    }

4. Save the file

Hiding the external accounts section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAccounts
    {
    display: none;
    }

4. Save the file

Hiding the aliases section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAliases
    {
    display: none;
    }

4. Save the file

Webmail Message Customization

You can customize your own webmail messages (what we call "strings") - this could be especially useful for foreign language support if the translation provided does not adequately communicate an action or system response.

Each language has its own strings file stored in:

..."Vircom"Web"WebRoot"Locales

There is a strings.xml file - the default translations provided with Webmail - and a custom.xml file. Make your changes in the custom.xml file (as follows in the instructions below) and this file will override strings.xml.

Changing default strings

1. Go to the language folder whose messages you want to customize and open both the strings.xml and the custom.xml files

2. Copy and paste the strings to be customized from the strings.xml file into the custom.xml file

3. Modify the strings in the custom.xml file and save it.

4. You can also include HTML formatting instructions in the custom.xml file to specify how you want the customized strings to be displayed. This is useful, for instance, for the TEXT1000 & TEXT1001 tags which are shown at the top and bottom of the right-hand side of the login page respectively (where the beta version information and the upcoming features information was previously displayed).

5. Save the strings.xml file as well to change its timestamp so that the changes you have made can be viewed immediately (not changing the timestamp on the strings.xml file will mean that the customized strings are not shown until you restart IIS).

1.1.3.4. Customizing Webmail/WebQuarantine (Upgrades)

Product: All

Version & Build: 5.13



Important: Before the process of upgrading from 5.0, 5.1 to 5.13 some folder and file changes are required for the customization.  Please perform the following steps before the upgrade is done.


MODUSGATE INSTRUCTIONS:

1.  Locate the appropriate root installation folder for the Quarantine files, e.g. C:\Program Files\Vircom\Web\Quarantine

2. Open up the directory WebRoot\Themes

3. In this directory you will find three or more folders named Gray, Vircom, and your own Custom folder which contains your customization images and styles. Note that we will use the folder name Custom for the rest of this article while your custom folder could have a different name.

4. Rename the Vircom folder to Vircom1.

5. Next make a copy of your Custom folder (for backup purposes) and rename your original Custom folder to Vircom.  Your Themes folder should look like:

 

6. The reason for this is that Modus 5.12 only checks the default Vircom folder for all the style changes.

7. Open up your new custom folder named Vircom.

8. In this directory you will find the customization files named style.css and custom.css.

9. If your customized pages have some custom colors, there is a good chance that you had made these changes in the style.css file. If you know your customizations were made in the custom.css file then proceed to step 12.

10. If you made changes to the style.css file, open it and copy those changes onto the clipboard (CTRL-C).

11. Open the custom.css file in the same directory and paste the clipboard contents into it (CTRL-V).  Save your changes and close both files.  custom.css should now contain your customizations.


12. Once all this is has been done, you can now launch the upgrade for version 5.12.

13. Once the install is complete, open the custom.config file located in c:\Program Files\Vircom\Web\Quarantine\WebRoot folder.

14. There are 2 lines which need to be modified. Both lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

15. Restart Modus Webmail service and IIS. Your customizations should be visible.


MODUSMAIL INSTRUCTIONS:

1. Download and install Modus 5.12.

2. Once the install is complete, open the custom.config file located in C:\Program Files\Vircom\Web\WebMail\WebRoot (assumes a default install location).  

3. There are 3 lines of code which need to be modified. All 3 lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines -<add key="DefaultTheme" value="Vircom"/>.

TO

<add key="DefaultTheme" value="CUSTOM"/>

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

4. Restart Modus Webmail service and IIS. Your customizations should be visible.


1.1.3.5. Configuring Exchange on Windows Small Business Server to listen on an alternate port (25)
Product: modusGate
Version & Build: all

If you're interested in getting modusGate running on the same system as Microsoft Exchange (example, on a Windows Small Business server), with both of them co-existing on the same machine, you cannot have modusGate & Exchange both listening on the same SMTP port 25. 



What you want to do is have modusGate listen on port 25 and it would redirect the traffic to the local exchange server on an alternate port (usually 26).
 
This being said, how do you get Microsoft Exchange to listen on port 26?
 
 
On Exchange 2007 and 2010:
 
 
You can change the receive connector port thus:

1. Go to the Exchange Management Console under Hub Transport
2. Select thereceive connector name you want to change
3. Click on properties
4. Select “network”
5. Choose local IP address
6.  Edit the Receive Connector Bindings
7.  Change the port to the desired port to listen on for SMTP traffic (ex: 26)
 
 

Optional: You can restrict who can send to this SMTP server by editing the “receive mail from remote servers which have these IP addresses”. In this case, you could restrict it to 127.0.0.1 if you want to allow inbound port 26 traffic to only come from modusGate which is sitting on the same box.
 
 
On Exchange 2000 and 2003:
 
 
1. Start the Exchange System Manager.
2. Select the Servername you want to change.
3. Click on Protocols
4. Click  on SMTP
5. Right-click the Default SMTP Virtual Server object
6. Click Properties.



7. On the General tab click the Advanced button
8. Click the Edit button
9. Set the TCP port to desired port (ex: 26).
 
 
 
 
On Exchange 5.5:

 
To change the SMTP listening port on a server that is running Exchange 5.5 from port 25 to another port (for example: port 26) follow these steps:

1.  Open the Control Panel
2. Select Administrative Tools
3. Select Services
4. Stop the Exchange Server Internet Mail service.
5. Open the file c:\Winnt\System32\Drivers\Etc\Services using notepad
6. Locate the line containing: "smtp 25/tcp mail" and change the 25 to 26.
7. Save the Services file.
8. Start the Exchange Server Internet Mail service.


1.1.3.6. Customizing Webmail/WebQuarantine (Upgrades)

Product: All

Version & Build: 5.31 +


modusGate 5.42 includes a brand new quarantine interface.  Customizations of this new interface  is not compatible with prior versions.

You will find your previous WebQuarantine installation and any customization done is still available via the QuarantinePre5-30 virtual directory.

MODUSGATE INSTRUCTIONS:

1.  Locate the appropriate root installation folder for the Quarantine files, e.g. C:\Program Files\Vircom\Web\WebQuarantine

2. Open up the file custom.config

3. At the end of the file, you will find the following lines, each of them denote a configurable setting for WebQuarantine.

  <add key="LoginLogoUrl" value="http://www.vircom.com" />
  <add key="LoginLogoImage" value="logo-login.png" />
  <add key="FooterLoginLogoUrl" value="http://www.vircom.com" />
  <add key="FooterLoginLogoImage" value="footer-logo-login.png" />
  <add key="MobileLoginLogoUrl" value="http://www.vircom.com" />
  <add key="MobileLoginLogoImage" value="logo2.png" />
  <add key="MobileFooterLoginLogoUrl" value="http://www.vircom.com" />
  <add key="MobileFooterLoginLogoImage" value="logo-vircom.png" />
  <add key="MobileMenuLogoImage" value="logo.png" />
  <add key="MenuLogoUrl" value="http://www.vircom.com" />
  <add key="MenuLogoImage" value="logo.png" />
  <add key="FooterLogoUrl" value="http://www.vircom.com" />
  <add key="FooterLogoImage" value="logo-vircom.png" />

4. To use your own logo, change the Image values to your own logo filename, for example:

To change Login page logo, change


  <add key="LoginLogoImage" value="logo-login.png" />

To:

  <add key="LoginLogoImage" value="my-logo-login.png" />

And put your new logo file in the WebRoot\Wres\img folder.

Mobile logos needs to be put in WebRoot\Wres\mobile\images

5. Change the matching Url value to your desired URL.

6. To customize other attributes such as colors, font type, etc, you can overwrite any CSS rules in the file located at WebRoot\Wres\custom\custom.css

MODUSMAIL INSTRUCTIONS:

1. Download and install Modus 5.42.

2. Once the install is complete, open the custom.config file located in C:\Program Files\Vircom\Web\WebMail\WebRoot (assumes a default install location).  

3. There are 3 lines of code which need to be modified. All 3 lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines -<add key="DefaultTheme" value="Vircom"/>.

TO

<add key="DefaultTheme" value="CUSTOM"/>

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

4. Restart Modus Webmail service and IIS. Your customizations should be visible.


1.1.3.7. modus Upgrade Checklist

 modus Upgrade Checklist

Introduction

         This document is intended for existing Vircom customers who are currently running an older version of ModusGate. You should read this document thoroughly before upgrading. If you have any questions or feel something is missing from this document, feel free to contact us by e-mail at support@vircom.com.


Before upgrading, please ensure that you have met the following requirements:


  • Backup your databases (QT, Audit, Monitoring and Sieve) before launching the upgrade
  • Ideally, this should be a full backup
  • If you are using SQL Server Express, ensure that Full Text Indexing is installed
  • For instructions, please consult the following KB article:
  • http://kb.vircom.com/Kbase/default.asp?SID=&Lang=1&id=1621&Lang=1&SID=
  • Ensure that .Net 3.5 Framework is installed
  • For more information, consult the following Microsoft® websites:
  • Microsoft .NET Framework Version 3.5
  • Ensure that you have your current installation package
  • In the event that you must roll back after upgrading, keep a copy of the *.exe installation file
  • If you do not have a copy of the file, before upgrading, send an email to: support@vircom.com requesting it
  • Backup your Windows Registry
  • On the modus server, click on Start > Run
  • Type regedit to open the Registry Editor
  • In the Registry Editor, click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup any customized quarantine reports and/or web applications folders
  • Read the Release Notes for all new features and changes to modus, especially the section regarding encryption

If you opt to use encryption, there is a sieve script that must be added to prevent issues with foreign languages for outbound messages. This script is included in the Release Notes.


Upgrading modusMail/modusGate to v6.0 

         Due to a series of architectural changes in versions upgrading from version 4.7 must be done in two steps:

        1. upgrade from v4.7 to v 5.0 or v5.1

        2. upgrade directly to v6.0

If you are running any version higher the 5.1 you can directly upgrade to v6.0.


Changes to the installation process:

         Starting from v5.31 ModusGate comes with a new web interface. The new interface will not overwrite your existing WebQuarantine programs. This will allow you to continue using the 'old' site until you have had time to test and/or customize the new one.

ModusGate Web Quarantine information:

         There will be a new folder created called WebQuarantine locate under C:\Program Files(x86)\Vircom\Web. This folder will contain the new websites attributes for the new web quarantine pages. The virtual directory will still exist in IIS.


IMPORTANT:

          If you plan to use the monitoring feature, it is preferable to use a Microsoft SQL database instead of the native Access format. Whether to use Microsoft Access or Microsoft SQL depends on your volume of traffic. A good rule of thumb would be to use your quarantine database as your guide: if you use SQL for the quarantine, then you should use it for the monitoring stats as well.


Upgrading ModusGate

Upgrading requires a certain number of precautions. The most important is doing a backup before upgrading:

  • Make sure you have access to your old Modus installation package in case you need to rollback. If you do not have a copy, click on the help -> about button in your ModusGate console to find out what version you have and the build number; contact us by email, and we will be happy to provide you with the original install package.
  • Backup your configuration: - Open the ModusGate administration console and select File > Backup configuration - Select the path where the configuration file will be stored (*.reg file) - Keep this registry file (*.reg) in a safe location as a backup of your Modus configuration.
  • Backup the Registry: - Open the Registry Editor (regedit) - Click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup the Web directory: Located under...\Vircom\Web
  • Backup the databases: Normally located under the root installation of SQL \\Microsoft SQL Server\MSSQLXX.SQLEXPRESS\MSSQL\DATA
  • Proceed with the upgrade.


Upgrading ModusMail

Upgrading requires a certain number of precautions. The most important is doing a backup before upgrading:


Steps to take before upgrading:
  • If you have the hardware and software capability, it would be best to mirror your existing machine so you could hot-swap (switch the IP addresses over) should the upgrade fail. However, in the event that you cannot mirror your server, proceed with the following:
  • Make sure your datasource is up-to-date. If you are using an external datasource for authentication (such as a billing package), ensure that it is up-to-date.
  • Note: If you are using Platypus or RODOPI, check with Boardtown or RODOPI to find out if a new stored procedure is required. In any event, you should run the latest stored procedures for ModusMail.
  • Make sure you have access to your old Modus installation package in case you need to rollback. If you do not have a copy, click on the help -> about button in your ModusMail console to find out what version you have and the build number; contact us by email, and we will be happy to provide you with the original install package.
  • Backup your configuration:

         - Open the ModusMail administration console and select File -> Backup configuration

         - Select the path where the configuration file will be stored (it will be a .reg file)

         - Keep this registry file (*.reg) in a safe location as a backup of your Modus configuration

  • Backup your registry:

         - Open the Registry Editor (regedit)

         - Click on File > Export

         - Select the file location, enter a name for the backup file and click OK

  • Backup the Web directory: Located under...\Vircom\Web
  • Backup the databases: Normally located under the root installation of SQL \\Microsoft SQL Server\MSSQLXX.SQLEXPRESS\MSSQL\DATA
  • Proceed with the upgrade. 

After upgrade is done please ensure that Modus antivirus engines are up and running:

  • In Advanced console go to Virus Tab and see that both AV were successfully updated with the latest version.
  • Go to System Tab and see that all Modus services are up and running.
  • Note! It could take up to 5 minutes to modus to download and install latest versions of antivirus engine and definitions.
  • Customer may use Email flow diagnostic tool provided with modus installation to verify the legit and spam mail flow.







 


 

1.1.4. Version 6.2
Important information about upgrading to modus 6.2
 

System Requirements:
        

Operating System: Windows Server 2008 (32 and 64-bit), 2008R2, 2012, 2012R2 and Windows Small Business Server (SBS) 2008 x64 and 2011 x64. Windows Web Edition is not supported.

 Web Server: IIS version 7.0 or later.

Components: MDAC 2.8 SP1 or higher, .NET Framework 3.5 SP1 and 4.5 

Exchange Integration: Microsoft Exchange 2007/2010/2013/2016. 

SQL Server: 2005 x86/x64, 2008 x86/x64, 2008R2 ,2005 Express Edition, 2008 Express Edition, SQL 2012 x86/x64, SQL 2014 x86/x64.

Microsoft Office: Microsoft Office 2007, 2010, 2013, 2016 (This only applies to directQuarantine client application.)

 

Web Browsers:

Desktop: Internet Explorer 9+, Chrome 30+, Safari 7+, or Firefox 25+

Mobile*: iOS Safari 4.0+ (4x, 5.x), Android Browser 4.0+ (4.x, 5.x), Chrome 30+

* Note that the mobile web browsers only apply to the Web Quarantine.


Change Logs
 
See the modusMail / modusGate pages below for their respective change logs and list of fixes. 

1.1.4.1. modusGate
New in modusGate 6.2


This latest release of modusGate 6.2 includes several security improvements and overall maintenance fixes. Also in this release, the latest Microsoft platforms are supported.


Highlights:

  • modusGate now supports Exchange 2016.
  • modusGate includes the latest AV engines for Avira and Bitdefender.
  • Scanning content engine (SCAV2) updated.
  • modusGate now detects Macros and OLE (Object Linking Embedding) objects in MS Office attachments. The option is disabled by default.
  • directQuarantine now supports Outlook 2016 and Windows 10.
  • modusGate installer will now check for RBL availability through DNS.

 

IMPORTANT – PLEASE READ

 

 

To ensure your email servers remain fully protected as of January 1, 2017, all modusGate versions running on Microsoft Windows 2003 server must be migrated to Windows 2008 server or higher. This is due to SHA1 certificates being deprecated across the internet. Starting January 1, 2017 all modusGate servers will no longer recieve any antivirus or antispam definitions. Pease see this

KB article for further details.

 

If you need help migrating your modusGate server, please contact our Professional Services to schedule a time and cost estimate for your migration.

 

 

 

Change Logs:

  • Updated expired Avira license key
  • modusGate 6.2 and future releases will no longer install on Windows 2003 servers.
  • Fixed an issue with SPF where a record that contains a redirect inside an “include” will take precedence over the root.
  • Fixed an issue with Opportunistic TLS where if a secure hand shake was unsuccessful the email would not be delivered in clear text.
  • Fixed an issue where the Sieve AV engine was not executed when an email contains a forbidden file within an archive. 
  • Fixed an issue with the Avira Plug-in where it would generate slowness errors in the Windows Event Log.
  • Fixed an issue where some emails would not display properly in WebAdmin-> Quarantine.
  • Fixed an issue with the search feature in WebAdmin. In some cases, the server would return “500 Internal Error” when asearch was performed.
  • Fixed an issue where certain registry parameters when restored from a modus Backup Configuration file would corrupt moduscan.
  • Fixed an issue with the search feature in WebAdmin, where users mailbox would not be displayed for specific search criteria’s.
  • Removed the option to “Generate Now” from the WebQuarantine “Reports” menu.
  • Fixed an issue where Bitdefender AV engine was not loading the latest definition files until moduscan was restarted.
  • The total license count in the Advanced Console will now include both mailboxes and distribution lists.
  • Fixed a text field label in the Reporting screen located in WebAdmin.
  • Fixed an issue in WebAdmin where adding a user of type “database” was not possible.
  • Fixed the “Contact Support” and “Contact Sales” links in the Simplified Console.
  • modusGate Admin guide updates.

 

Operational Considerations:

As of modusGate 6.x our anti-spam engine SCAV2 requires that the UDP port 53 and TCP port 80 to remain open to properly filter emails. These ports are needed for both outbound and inbound traffic from the modusGate. If you require a list of IP’s to our servers you may contact our support team for the complete list. 

When modusGate is configured to perform outbound filtering the following steps are needed to:

      1.    Go to the following folder …Vircom\modusGate\SCAV2

      2.    Open the file called “spamcatcher.conf”

      3.    Search for the parameter called “ignored_ip_list”

      4.   Remove the # character and enter theIP of the mailserver the emails are being filtered from.

           ie: ignored_ip_list=192.168.0.179

      5. Save and RESTART moduscan service.

 

Known Issues:

 

The upgrade process may be interrupted with an error window, labeled “Update Error " followed by 4 similar errors. At this point the installer will terminate andthe upgrade is incomplete.

 

This issue may only presents itself when the server running modusGate is low onsystem resources. Which may impact SQL processes to run optimally during theupgrade.

 

 

-       Select“OK” button on all installer error pop-ups.

-       Kill all installer processes if still running.

-       Stopprocesses that may be taking up a lot of the server’s resources.

-       Stop “ModusScan” service from Windows Service manager.

-       Restart the installer and complete the upgrade.

 




Support:

Web:            http://www.vircom.com/en/support/customer-service/  
Phone:         1-888-484-7266
Email:          
support@vircom.com


Trademarks

Vircom, Email Security Grader, Email Security Matters, SysAdmin on the Line, NetAdmin on the Line, modus, modusMail and modusGate are trademarks of Vircom Inc. Windows and Exchange are registered trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners.


 

 

  
1.1.4.2. modusMail
New in modusMail 6.2

The latest release of modusMail 6.2 includes several security improvements and overall maintence fixes.


Highlights:
 
         ·    modusMail includes the latest AV engines for Avira and Bitdefender.
         ·    Scanning content engine (SCAV2) updated.
         ·    modusMail now detects Macros and OLE(Object Linking Embedding) objects in MS Office attachments. The option isdisabled by default.
         ·    directQuarantine now supports Outlook 2016 and Windows 10.
         ·    modusMail installer will now check for RBL availability through DNS.

          

IMPORTANT – PLEASE READ

           To ensuer your email servers remain fully protected as of January 1, 2017, all modusMail verson running Microsoft Windows 2003 server must be migrated to Windoes 2008 server or higher. This is due to SHA1 certificates being deprecated across the internet. Starting January 1, 2017 all modusMail servers will no longer receive any antivirus or anitspam definitions. Please see this KBarticle for further details. 

If you need help migrating your modusMail server, Please contact our Professional Services to schedule a time and cost estimate for your migration.

 
Change Logs:
  • Updated expired Avira license key
  • modusMail 6.2 and future releases will no longer install on Windows 2003 servers.
  • Fixed an issue with SPF where a record that contains a redirect inside an “include” will take precedence over the root.
  • Fixed an issue with Opportunistic TLS where if asecure hand shake was unsuccessful the email would not be delivered in clear text.
  • Fixed an issue with the Avira Plug-in where it would generate slowness errors in the Windows Event Log.
  • Fixed an issue where certain registry parameters when restored from a modus Backup Configuration file would corrupt moduscan.
  • Fixed an issue where Bitdefender AV engine was not loading the latest definition files until moduscan was restarted.
  • The modusMail installer will now check for RBL availability through DNS.
  • Fixed the “Contact Support” and “Contact Sales” links in the Simplified Console.
  • modusMail Admin guide updates.

 

Operational Considerations:

As of modusMail 6.x our anti-spam engine SCAV2 requires that the UDP port 53 and TCP port 80 to remain open to properly filteremails. These ports are needed for both outbound and inbound traffic. If yourequire a list of IP’s to our servers, you may contact our support team for the complete list. 

 

Known Issues: 

   

The upgrade process may be interrupted with an error window, labeled “Update Error " followed by 4 similar errors. At this point the installer will terminate andthe upgrade is incomplete.

This issue may only presents itself when the server running modusGate is low onsystem resources. Which may impact SQL processes to run optimally during theupgrade.

- Select“OK” button on all installer error pop-ups.

- Kill all installer processes if still running.

- Stopprocesses that may be taking up a lot of the server’s resources.

- Stop “ModusScan” service from Windows Service manager.

- Restart the installer and complete the upgrade.




 

Support:    

Web:               http://www.vircom.com/en/support/customer-service/
Phone:            1-888-484-7266
Email:            
support@vircom.com


Trademarks

Vircom, Email Security Grader, Email Security Matters, SysAdmin on the Line, NetAdmin on the Line, modus, modusMail and modusGate are trademarks of Vircom Inc. Windows and Exchange are registered trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners.


 


1.1.4.3. Customizing Webmail/WebQuarantine 5.13 (new installs)

Product: All

Version & Build: 5.13



Important: When upgrading to Modus 5.13 the default "Vircom" theme will be applied. Please follow steps below to make the appropriate changes to your custom pages.


The following customization information can be used with both ModusMail and ModusGate - where applicable.

There are many levels of customization that you can make for the web interface, depending on what you want to do:

  • you can substitute your company logo for the Vircom logos (which appear on the login and on each web page)
  • you can modify attributes of the Vircom theme such as the color or the size of the text
  • you can bypass Vircom's login page and have your users access their webmail through your own portal
  • you can create a completely different theme for the web interface that bears no resemblance to the Vircom theme - this theme will not be overwritten by future upgrades, BUT any interface enhancements made by Vircom will not be reflected in your custom-built interface. We provide only very basic customization information here: we provide enough information that if you know what you're doing, you'll know how to support your own customizations and you can go ahead and build your own interface.

Note: The web.config and style.css files contain the product default values. Never alter these files because any work you do will be lost upon upgrading the software. Change the custom.config and custom.css files instead. A Modus upgrade will not overwrite these files, except that it will set back the DefaultTheme to Vircom. This is needed because major changes have been done in the styles for this version.  Please note also that Vircom Technical support cannot debug any custom interfaces you build. We can support only basic style changes to the Vircom interface that include rebranding and recoloring (changing images and modifying CSS styles).

Custom.Config Basic Functionality Customization

NOTE: Any modifications you make in the custom.config file will require you to Stop/Start the IIS Admin service after you have finished.

1. The default language of the WebMail interface is defined in this key. The value must match an existing folder under Locales.

<add key="DefaultLanguage" value="en"></add>

2. The default theme of the WebMail interface is defined in this key. The value must match an existing theme folder under Themes.

<add key="DefaultTheme" value="vircom"></add>

3. This is the domain name or IP address of your WebMail Server service.

<add key="WebMailServerAddress" value="localhost"></add>

4. This is the port number of your WebMail Server service.

<add key="WebMailServerPort" value="31804"></add>

5. This is the character set in which the page will be displayed.

<add key="Charset" value="iso-8859-1"></add>

6. This is the path of the temporary folder that the installation program configures automatically.

<add key="Temp" value=""></add>

7. This is the path of the log folder that the installation program configures automatically.

<add key="LogDir" value=""></add>

8. This is the relative path and file name of the Login page. If you want to design your own login page or you want to integrate webmail with your portal, change this value to your to the relative path and file name of your custom-designed login page. When logging off, users will be redirected to this page instead of the main webmail login page.

<add key="LoginPage" value="Login.aspx"></add>

9. This is the name of the application that will be shown in the browser windows title bar.

<add key="Title" value="Webmail"></add>

10. This option determines whether WebMail should parse messages to find out if there is an attachment.

<add key="ShowPaperClip" value="false"></add>

NOTE: When this option is turned on, you might encounter performance drops for POP3 accounts since the message must be downloaded completely. This does not affect IMAP4 accounts. Set the value to "true" to enable or to "false" to disable it.

11. This option determines whether users can specify the email address that will be shown in the From field of outgoing emails.  Turn on this option with caution since it allows users to enter any email address.

<add key="AllowChangeFromAddress" value="false"></add>

Set the value to "true" to enable or to "false" to disable it.

Logos

In the custom.config file, you can set the image and hyperlink for the Login logo and the top menu logo.  These images must exist in your selected theme in order to work.

<add key="LoginLogoUrl" value="http://www.vircom.com"></add>
<add key="511LoginLogoImage" value="LogoLogin.gif"></add>
<add key="MenuLogoUrl" value="
http://www.vircom.com"></add>
<add key="511MenuLogoImage" value="LogoMenu.gif"></add>

Custom Login Page or Portal Integration

You can create your own login page or insert the login form in your portal.  Your login page should include a form with the two following form fields:

<input type="text" name="txtLogin"/>
<input type="password" name="txtPassword"/>

The page's form action should be set to "Login.aspx" and the method set to "POST".  Here's a simple Login page:

<html>
<body>
<form action="Login.aspx" method="POST">
<input type="text" name="txtLogin"/>
<input type="password" name="txtPassword"/>
<input type="submit" value="Login"/>
</form>
</body>
</html>

Theme Customization

The WebMail application theme is made through a main CSS file (and if you vary functionality between domains, you'll also need a customized .config file).  DO NOT alter the Style.css file or the Web.config file (or will you will lose all your work when you perform a Modus upgrade).  Instead, you must redefine colors, fonts, and other attributes in the Custom.css, and any functionality variations (see config file attributes above) in the custom.config files.

Any changes you make to the custom files will override the values in the style.css and web.config files.

For domain customization, create css and config files and name them according to the domain, for example:

  • domain.com.css (which should be saved in your custom theme directory)

  • domain.com.config (which should be saved in the webroot directory)

  • domain.net.css (which should be saved in your custom theme directory)

  • domain.net.config (which should be saved in the webroot directory)

These domain files will override the custom.css and custom.config files which override the main style.css and web.config files.

NOTE: you only have to create a domain customized config file if you want to vary functionality between domains as well as the look and feel of it. Otherwise only create a domain customized .css file for your theme.

Changing the Login page color

The login page orange color constitutes of an image (Login_RoundBorder.gif) and a table cell. For example, to change the color to lightgrey:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #tdLoginRight
    {
    background-color: lightgrey;
    }

4. Save and close the file

Note that unless you change the Login_RoundBorder.gif image to lightgrey, it will look odd, so you can edit that file in an image editor or you can hide it altogether. To do so, add the following lines in the custom.css right after the lines previously added: #tdLoginMiddle

    #tdLoginMiddle
    {
    display: none;
    }

Changing the Top Menu color:

The top menu constitutes of an image (LogoMenu.gif) which is configured in the custom.config file, and a gradient image of 1 pixel width. The gradient image adds a level of depth to the menu bar while preserving a very small file size. If you want to change the gradient coloring, open the GradientMenu.gif file in an image editor such as Gimp, PaintShopPro or Photoshop and change the color or gradient value of the image to your preference. You can also discard the gradient in the top menu and only use a solid color, such as lightgrey. To do this:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .Menu
    {
    background-color: lightgrey;
    background-image: none;
    }


4. Save the file

Changing the lists hover color:

Each message status has a separate class. This allows you to define different attributes for when an email is read, unread or deleted. In order to change the hover color, you will need to change each of these classes:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .dgListItemHover
    {
    background-color: lightgrey;
    }
    .dgListItemUnreadHover
    {
    background-color: lightgrey;
    }
    .dgListItemDeletedHover
    {
    background-color: lightgrey;
    }

4. Save the file

Changing the background color of all panels:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .MessageViewMsgHeader,
    .SettingsAccount,
    .SettingsOption,
    .SettingsOptionGeneral,
    .SettingsFolders,
    .SettingsOptionsAntiSpam,
    .SettingsOptionsAntiVirus,
    .SettingsOptionsRules,
    .SettingsOptionsAutoReply,
    .SettingsContacts,
    .SettingsOptionsHome,
    .SettingsOptionsBusiness,
    .SettingsTrusted,
    .SettingsBlocked,
    .SettingsOptionsBlocked,
    .SettingsOptionsTrusted,
    .SettingsAliases,
    .SettingsOptionsReporting,
    #divContactEditor_main,
    .DiagnosticContainer
    {
    background-color: lightgrey;
    }

4. Save the file


Hiding the Server Blocked/Trusted List from the Settings Page:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #Trustedlist_TableRowWhitelistServerTitle,
    #Trustedlist_TableRowWhitelistServerData,
    #Blockedlist_TableRowBlacklistServerTitle,
    #Blockedlist_TableRowBlacklistServerData
    {
    display:none;
    }

4. Save the file

 
 

modusMail only:


Removing Statistics (or other major menu items)

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 Statistics menu option from the web interface.

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #tdStatistics
    {
    display: none;
    }

4. Save the file

NOTE: these instructions apply to the other menu items: #tdAddressBook, #tdFolders, #tdSettings, #tdLogoff. Change the syntax for the line in step 3 from <#tdStatistics> to the menu item you want to hide.

Hiding Sections in Settings:

As with the login page, it is possible to hide certain parts of the page. This is especially useful if you don't want your users to access particular types of settings.

Hiding the options section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsOptions
    {
    display: none;
    }

4. Save the file

Hiding the email filtering section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsFiltering
    {
    display: none;
    }

4. Save the file

Hiding the user contact information section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsUserInfo
    {
    display: none;
    }

4. Save the file

Hiding the rules section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsRules
    {
    display: none;
    }

4. Save the file

Hiding the auto-reply section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAutoreply
    {
    display: none;
    }

4. Save the file

Hiding the external accounts section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAccounts
    {
    display: none;
    }

4. Save the file

Hiding the aliases section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAliases
    {
    display: none;
    }

4. Save the file

Webmail Message Customization

You can customize your own webmail messages (what we call "strings") - this could be especially useful for foreign language support if the translation provided does not adequately communicate an action or system response.

Each language has its own strings file stored in:

..."Vircom"Web"WebRoot"Locales

There is a strings.xml file - the default translations provided with Webmail - and a custom.xml file. Make your changes in the custom.xml file (as follows in the instructions below) and this file will override strings.xml.

Changing default strings

1. Go to the language folder whose messages you want to customize and open both the strings.xml and the custom.xml files

2. Copy and paste the strings to be customized from the strings.xml file into the custom.xml file

3. Modify the strings in the custom.xml file and save it.

4. You can also include HTML formatting instructions in the custom.xml file to specify how you want the customized strings to be displayed. This is useful, for instance, for the TEXT1000 & TEXT1001 tags which are shown at the top and bottom of the right-hand side of the login page respectively (where the beta version information and the upcoming features information was previously displayed).

5. Save the strings.xml file as well to change its timestamp so that the changes you have made can be viewed immediately (not changing the timestamp on the strings.xml file will mean that the customized strings are not shown until you restart IIS).

1.1.4.4. Customizing Webmail/WebQuarantine (Upgrades)

Product: All

Version & Build: 5.13



Important: Before the process of upgrading from 5.0, 5.1 to 5.13 some folder and file changes are required for the customization.  Please perform the following steps before the upgrade is done.


MODUSGATE INSTRUCTIONS:

1.  Locate the appropriate root installation folder for the Quarantine files, e.g. C:\Program Files\Vircom\Web\Quarantine

2. Open up the directory WebRoot\Themes

3. In this directory you will find three or more folders named Gray, Vircom, and your own Custom folder which contains your customization images and styles. Note that we will use the folder name Custom for the rest of this article while your custom folder could have a different name.

4. Rename the Vircom folder to Vircom1.

5. Next make a copy of your Custom folder (for backup purposes) and rename your original Custom folder to Vircom.  Your Themes folder should look like:

 

6. The reason for this is that Modus 5.12 only checks the default Vircom folder for all the style changes.

7. Open up your new custom folder named Vircom.

8. In this directory you will find the customization files named style.css and custom.css.

9. If your customized pages have some custom colors, there is a good chance that you had made these changes in the style.css file. If you know your customizations were made in the custom.css file then proceed to step 12.

10. If you made changes to the style.css file, open it and copy those changes onto the clipboard (CTRL-C).

11. Open the custom.css file in the same directory and paste the clipboard contents into it (CTRL-V).  Save your changes and close both files.  custom.css should now contain your customizations.


12. Once all this is has been done, you can now launch the upgrade for version 5.12.

13. Once the install is complete, open the custom.config file located in c:\Program Files\Vircom\Web\Quarantine\WebRoot folder.

14. There are 2 lines which need to be modified. Both lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

15. Restart Modus Webmail service and IIS. Your customizations should be visible.


MODUSMAIL INSTRUCTIONS:

1. Download and install Modus 5.12.

2. Once the install is complete, open the custom.config file located in C:\Program Files\Vircom\Web\WebMail\WebRoot (assumes a default install location).  

3. There are 3 lines of code which need to be modified. All 3 lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines -<add key="DefaultTheme" value="Vircom"/>.

TO

<add key="DefaultTheme" value="CUSTOM"/>

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

4. Restart Modus Webmail service and IIS. Your customizations should be visible.


1.1.4.5. Configuring Exchange on Windows Small Business Server to listen on an alternate port (25)
Product: modusGate
Version & Build: all

If you're interested in getting modusGate running on the same system as Microsoft Exchange (example, on a Windows Small Business server), with both of them co-existing on the same machine, you cannot have modusGate & Exchange both listening on the same SMTP port 25. 



What you want to do is have modusGate listen on port 25 and it would redirect the traffic to the local exchange server on an alternate port (usually 26).
 
This being said, how do you get Microsoft Exchange to listen on port 26?
 
 
On Exchange 2007 and 2010:
 
 
You can change the receive connector port thus:

1. Go to the Exchange Management Console under Hub Transport
2. Select thereceive connector name you want to change
3. Click on properties
4. Select “network”
5. Choose local IP address
6.  Edit the Receive Connector Bindings
7.  Change the port to the desired port to listen on for SMTP traffic (ex: 26)
 
 

Optional: You can restrict who can send to this SMTP server by editing the “receive mail from remote servers which have these IP addresses”. In this case, you could restrict it to 127.0.0.1 if you want to allow inbound port 26 traffic to only come from modusGate which is sitting on the same box.
 
 
On Exchange 2000 and 2003:
 
 
1. Start the Exchange System Manager.
2. Select the Servername you want to change.
3. Click on Protocols
4. Click  on SMTP
5. Right-click the Default SMTP Virtual Server object
6. Click Properties.



7. On the General tab click the Advanced button
8. Click the Edit button
9. Set the TCP port to desired port (ex: 26).
 
 
 
 
On Exchange 5.5:

 
To change the SMTP listening port on a server that is running Exchange 5.5 from port 25 to another port (for example: port 26) follow these steps:

1.  Open the Control Panel
2. Select Administrative Tools
3. Select Services
4. Stop the Exchange Server Internet Mail service.
5. Open the file c:\Winnt\System32\Drivers\Etc\Services using notepad
6. Locate the line containing: "smtp 25/tcp mail" and change the 25 to 26.
7. Save the Services file.
8. Start the Exchange Server Internet Mail service.


1.1.4.6. Customizing Webmail/WebQuarantine (Upgrades)

Product: All

Version & Build: 5.31 +


modusGate 5.42 includes a brand new quarantine interface.  Customizations of this new interface  is not compatible with prior versions.

You will find your previous WebQuarantine installation and any customization done is still available via the QuarantinePre5-30 virtual directory.

MODUSGATE INSTRUCTIONS:

1.  Locate the appropriate root installation folder for the Quarantine files, e.g. C:\Program Files\Vircom\Web\WebQuarantine

2. Open up the file custom.config

3. At the end of the file, you will find the following lines, each of them denote a configurable setting for WebQuarantine.

  <add key="LoginLogoUrl" value="http://www.vircom.com" />
  <add key="LoginLogoImage" value="logo-login.png" />
  <add key="FooterLoginLogoUrl" value="http://www.vircom.com" />
  <add key="FooterLoginLogoImage" value="footer-logo-login.png" />
  <add key="MobileLoginLogoUrl" value="http://www.vircom.com" />
  <add key="MobileLoginLogoImage" value="logo2.png" />
  <add key="MobileFooterLoginLogoUrl" value="http://www.vircom.com" />
  <add key="MobileFooterLoginLogoImage" value="logo-vircom.png" />
  <add key="MobileMenuLogoImage" value="logo.png" />
  <add key="MenuLogoUrl" value="http://www.vircom.com" />
  <add key="MenuLogoImage" value="logo.png" />
  <add key="FooterLogoUrl" value="http://www.vircom.com" />
  <add key="FooterLogoImage" value="logo-vircom.png" />

4. To use your own logo, change the Image values to your own logo filename, for example:

To change Login page logo, change


  <add key="LoginLogoImage" value="logo-login.png" />

To:

  <add key="LoginLogoImage" value="my-logo-login.png" />

And put your new logo file in the WebRoot\Wres\img folder.

Mobile logos needs to be put in WebRoot\Wres\mobile\images

5. Change the matching Url value to your desired URL.

6. To customize other attributes such as colors, font type, etc, you can overwrite any CSS rules in the file located at WebRoot\Wres\custom\custom.css

MODUSMAIL INSTRUCTIONS:

1. Download and install Modus 5.42.

2. Once the install is complete, open the custom.config file located in C:\Program Files\Vircom\Web\WebMail\WebRoot (assumes a default install location).  

3. There are 3 lines of code which need to be modified. All 3 lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines -<add key="DefaultTheme" value="Vircom"/>.

TO

<add key="DefaultTheme" value="CUSTOM"/>

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

4. Restart Modus Webmail service and IIS. Your customizations should be visible.


1.1.4.7. modus Upgrade Checklist

 modus Upgrade Checklist

Introduction

         This document is intended for existing Vircom customers who are currently running an older version of ModusGate. You should read this document thoroughly before upgrading. If you have any questions or feel something is missing from this document, feel free to contact us by e-mail at support@vircom.com.


Before upgrading, please ensure that you have met the following requirements:


  • Backup your databases (QT, Audit, Monitoring and Sieve) before launching the upgrade
  • Ideally, this should be a full backup
  • If you are using SQL Server Express, ensure that Full Text Indexing is installed
  • For instructions, please consult the following KB article:
  • http://kb.vircom.com/Kbase/default.asp?SID=&Lang=1&id=1621&Lang=1&SID=
  • Ensure that .Net 3.5 Framework is installed
  • For more information, consult the following Microsoft® websites:
  • Microsoft .NET Framework Version 3.5
  • Ensure that you have your current installation package
  • In the event that you must roll back after upgrading, keep a copy of the *.exe installation file
  • If you do not have a copy of the file, before upgrading, send an email to: support@vircom.com requesting it
  • Backup your Windows Registry
  • On the modus server, click on Start > Run
  • Type regedit to open the Registry Editor
  • In the Registry Editor, click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup any customized quarantine reports and/or web applications folders
  • Read the Release Notes for all new features and changes to modus, especially the section regarding encryption

If you opt to use encryption, there is a sieve script that must be added to prevent issues with foreign languages for outbound messages. This script is included in the Release Notes.


Upgrading modusMail/modusGate to v6.0 

         Due to a series of architectural changes in versions upgrading from version 4.7 must be done in two steps:

        1. upgrade from v4.7 to v 5.0 or v5.1

        2. upgrade directly to v6.0

If you are running any version higher the 5.1 you can directly upgrade to v6.0.


Changes to the installation process:

         Starting from v5.31 ModusGate comes with a new web interface. The new interface will not overwrite your existing WebQuarantine programs. This will allow you to continue using the 'old' site until you have had time to test and/or customize the new one.

ModusGate Web Quarantine information:

         There will be a new folder created called WebQuarantine locate under C:\Program Files(x86)\Vircom\Web. This folder will contain the new websites attributes for the new web quarantine pages. The virtual directory will still exist in IIS.


IMPORTANT:

          If you plan to use the monitoring feature, it is preferable to use a Microsoft SQL database instead of the native Access format. Whether to use Microsoft Access or Microsoft SQL depends on your volume of traffic. A good rule of thumb would be to use your quarantine database as your guide: if you use SQL for the quarantine, then you should use it for the monitoring stats as well.


Upgrading ModusGate

Upgrading requires a certain number of precautions. The most important is doing a backup before upgrading:

  • Make sure you have access to your old Modus installation package in case you need to rollback. If you do not have a copy, click on the help -> about button in your ModusGate console to find out what version you have and the build number; contact us by email, and we will be happy to provide you with the original install package.
  • Backup your configuration: - Open the ModusGate administration console and select File > Backup configuration - Select the path where the configuration file will be stored (*.reg file) - Keep this registry file (*.reg) in a safe location as a backup of your Modus configuration.
  • Backup the Registry: - Open the Registry Editor (regedit) - Click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup the Web directory: Located under...\Vircom\Web
  • Backup the databases: Normally located under the root installation of SQL \\Microsoft SQL Server\MSSQLXX.SQLEXPRESS\MSSQL\DATA
  • Proceed with the upgrade.


Upgrading ModusMail

Upgrading requires a certain number of precautions. The most important is doing a backup before upgrading:


Steps to take before upgrading:
  • If you have the hardware and software capability, it would be best to mirror your existing machine so you could hot-swap (switch the IP addresses over) should the upgrade fail. However, in the event that you cannot mirror your server, proceed with the following:
  • Make sure your datasource is up-to-date. If you are using an external datasource for authentication (such as a billing package), ensure that it is up-to-date.
  • Note: If you are using Platypus or RODOPI, check with Boardtown or RODOPI to find out if a new stored procedure is required. In any event, you should run the latest stored procedures for ModusMail.
  • Make sure you have access to your old Modus installation package in case you need to rollback. If you do not have a copy, click on the help -> about button in your ModusMail console to find out what version you have and the build number; contact us by email, and we will be happy to provide you with the original install package.
  • Backup your configuration:

         - Open the ModusMail administration console and select File -> Backup configuration

         - Select the path where the configuration file will be stored (it will be a .reg file)

         - Keep this registry file (*.reg) in a safe location as a backup of your Modus configuration

  • Backup your registry:

         - Open the Registry Editor (regedit)

         - Click on File > Export

         - Select the file location, enter a name for the backup file and click OK

  • Backup the Web directory: Located under...\Vircom\Web
  • Backup the databases: Normally located under the root installation of SQL \\Microsoft SQL Server\MSSQLXX.SQLEXPRESS\MSSQL\DATA
  • Proceed with the upgrade. 

After upgrade is done please ensure that Modus antivirus engines are up and running:

  • In Advanced console go to Virus Tab and see that both AV were successfully updated with the latest version.
  • Go to System Tab and see that all Modus services are up and running.
  • Note! It could take up to 5 minutes to modus to download and install latest versions of antivirus engine and definitions.
  • Customer may use Email flow diagnostic tool provided with modus installation to verify the legit and spam mail flow.







 


 

1.1.5. Version 6.1
Important information about upgrading to modus 6.1
 

System Requirements:
        

Operating System: Windows Server 2008 (32 and 64-bit), 2008R2, 2012, 2012R2 and Windows Small Business Server (SBS) 2008 x64 and 2011 x64. Windows Web Edition is not supported.

 Web Server: IIS version 7.0 or later.

Components: MDAC 2.8 SP1 or higher, .NET Framework 3.5 SP1 and 4.5 

Exchange Integration: Microsoft Exchange 2007/2010/2013. 

SQL Server: 2005 x86/x64, 2008 x86/x64, 2008R2 ,2005 Express Edition, 2008 Express Edition, SQL 2012 x86/x64, SQL 2014 x86/x64. 

Web Browsers:

Desktop: Internet Explorer 8+, Chrome 20+, Safari 4+, or Firefox 12+

Mobile*: iOS Safari 4.0+ (4x, 5.x), Android Browser 4.0+ (4.x, 5.x), Chrome 18+

* Note that the mobile web browsers only apply to the Web Quarantine.


Change Logs
 
See the modusMail / modusGate pages below for their respective change logs and list of fixes. 

1.1.5.1. modusGate
New in modusGate 6.1


This latest release of modusGate 6.1 is comprised of new features that improve the overall security of the system. Also in this release we've taken steps to increase the performance and effectiveness of the SCA engine. 


Highlights:

  • Improved the overall performance of the SCA engine.
  • Fine-tuned the SCA engine to increase the spam catch rate and eliminate false-positives.
  • Additional performance counters to allow customers to generate more granular reports on modusGate spam statistics.
  • Overall security improvements for components such as SMTP AUTH, Web components logins and mail relay throttling.

*Please note our supported system requirements have changed. See the change log for all details in this release.


Change Logs:

  • modusGate 6.1 allows for mail relay throttling to prevent the server from being black listed or going down due to a comprised user account.
  • The WebQuarantine login security has improved and now incorporates a “Locked” account mechanism. Configurable via the Advanced Console.
  • AUTH Login security has improved and incorporates a similar “Locked” account mechanism as with WebQuarantine. Configurable via the Advanced Console.
  • SMTP Authentication can be configured to be advertised or not for specific IP’s.
  • TLS encryption can be forced with IP’s and now in 6.1 you can also use domain names.
  • Trusted and blocked senders are now searchable in WebQuarantine.
  • The auto-trust feature will not trust email addresses from automated emails sent from Outlook's "Out of Office" feature.
  • directQuarantine now respects the same release permissions as WebQuarantine. (Specifically for corrupted and forbidden attachments.)
  • Additional performance counters were added for more granular spam statistics.
  • The Advanced Console incorporates a search feature for all routes created.
  • Improved authentications mechanism for directQuarantine users using modusCloud.
  • The "User" and "Domain" search options in Web Admin are now toggle buttons. "User" toggle button is the default.
  • Improved the search feature for users in WebAdmin. Any part of the email address can be searched.
  • Loading icon appears when scrolling through a large quarantine in WebAdmin.
  • Loading icon appears when scrolling and loading the message audit in WebMonitor.
  • The Modus license mechanism is able to distinguish the differences between Exchange distribution lists and regular mailboxes.
  • Improved license error message for when an installation package does not match the license type.
  • All Manuals have been updated 

 

Operational Considerations:

As of modusGate 6.x our anti-spam engine SCAV2 requires that the UDP port 53 and TCP port 80 to remain open to properly filter emails. These ports are needed for both outbound and inbound traffic from the modusGate. If you require a list of IP’s to our servers you may contact our support team for the complete list. 

 

Known Issues:

The upgrade process may be interrupted with an error window, labelled “Update Error” followed by 4 similar errors. At this point the installer will terminate and the upgrade is incomplete.

This issue may only presents itself when the server running modusGate is low on system resources. Which may impact SQL processes to run optimally during the upgrade.


- Select "OK" button on all installer error pop-ups.

- Kill all installer process if still running.

- Stop processes that maybe taking up a lot of the server's resources.

- Stop "Moduscan" service from windows service manager.

- Restart installer to complete the upgrade.



Support:

Web:            http://www.vircom.com/en/support/customer-service/  
Phone:         1-888-484-7266
Email:          
support@vircom.com


Trademarks

Vircom, Email Security Grader, Email Security Matters, SysAdmin on the Line, NetAdmin on the Line, modus, modusMail and modusGate are trademarks of Vircom Inc. Windows and Exchange are registered trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners.


 

 

  
1.1.5.2. modusMail
New in modusMail 6.1

This latest release of modusMail 6.1 is comprised of new features that improve the overall security of the system. Also in this release we’ve taken steps to increase the performance and effectiveness of the SCA engine.


Highlights:
  • Improved the overall performance of the SCA engine.
  • Fine-tuned the SCA engine to increase the spam catch rate and eliminate false-positives.
  • Additional performance counters to allow customers to generate more granular reports on modusGate spam statistics.
  • Security improvements for SMTP AUTH.

* Please note our supported system requirements have changed. See the change log for all details in this release. 

             

Change Logs:  
  • Auth Login security has improved and incorporates a similar "Locked" account mechanism. Configurable via the Advanced Console.
  • SMTP Authentication can be configured to be advertised or not for specific IP's.
  • TLS encryption can be forced with IP's and now in 6.1 you can also use domain names.
  • The Auto-trust feature will not trust email addressees from automated emails sent from Outlooks "Out Of Office" feature.
  • directQuarantine now respects the same release permissions as WebQuarantine (Specifically for corrupted and forbidden attachments.)
  • Additional performance counters were added for more granular spam statistics.
  • Improved license error messages for when an installation package does not match the license type.
  • All manuals have been updated.


Operational Considerations:

As of modusMail 6.x our anti-spam engine SCAV2 requires that the UDP port 53 and TCP port 80 to remain open to properly filter emails. These ports are needed for both outbound and inbound traffic. If you require a list of IP’s to our servers you may contact our support team.

 

Known Issues: 

 

Support:    

Web:               http://www.vircom.com/en/support/customer-service/
Phone:            1-888-484-7266
Email:            
support@vircom.com


Trademarks

Vircom, Email Security Grader, Email Security Matters, SysAdmin on the Line, NetAdmin on the Line, modus, modusMail and modusGate are trademarks of Vircom Inc. Windows and Exchange are registered trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners.


 


1.1.5.3. Customizing Webmail/WebQuarantine 5.13 (new installs)

Product: All

Version & Build: 5.13



Important: When upgrading to Modus 5.13 the default "Vircom" theme will be applied. Please follow steps below to make the appropriate changes to your custom pages.


The following customization information can be used with both ModusMail and ModusGate - where applicable.

There are many levels of customization that you can make for the web interface, depending on what you want to do:

  • you can substitute your company logo for the Vircom logos (which appear on the login and on each web page)
  • you can modify attributes of the Vircom theme such as the color or the size of the text
  • you can bypass Vircom's login page and have your users access their webmail through your own portal
  • you can create a completely different theme for the web interface that bears no resemblance to the Vircom theme - this theme will not be overwritten by future upgrades, BUT any interface enhancements made by Vircom will not be reflected in your custom-built interface. We provide only very basic customization information here: we provide enough information that if you know what you're doing, you'll know how to support your own customizations and you can go ahead and build your own interface.

Note: The web.config and style.css files contain the product default values. Never alter these files because any work you do will be lost upon upgrading the software. Change the custom.config and custom.css files instead. A Modus upgrade will not overwrite these files, except that it will set back the DefaultTheme to Vircom. This is needed because major changes have been done in the styles for this version.  Please note also that Vircom Technical support cannot debug any custom interfaces you build. We can support only basic style changes to the Vircom interface that include rebranding and recoloring (changing images and modifying CSS styles).

Custom.Config Basic Functionality Customization

NOTE: Any modifications you make in the custom.config file will require you to Stop/Start the IIS Admin service after you have finished.

1. The default language of the WebMail interface is defined in this key. The value must match an existing folder under Locales.

<add key="DefaultLanguage" value="en"></add>

2. The default theme of the WebMail interface is defined in this key. The value must match an existing theme folder under Themes.

<add key="DefaultTheme" value="vircom"></add>

3. This is the domain name or IP address of your WebMail Server service.

<add key="WebMailServerAddress" value="localhost"></add>

4. This is the port number of your WebMail Server service.

<add key="WebMailServerPort" value="31804"></add>

5. This is the character set in which the page will be displayed.

<add key="Charset" value="iso-8859-1"></add>

6. This is the path of the temporary folder that the installation program configures automatically.

<add key="Temp" value=""></add>

7. This is the path of the log folder that the installation program configures automatically.

<add key="LogDir" value=""></add>

8. This is the relative path and file name of the Login page. If you want to design your own login page or you want to integrate webmail with your portal, change this value to your to the relative path and file name of your custom-designed login page. When logging off, users will be redirected to this page instead of the main webmail login page.

<add key="LoginPage" value="Login.aspx"></add>

9. This is the name of the application that will be shown in the browser windows title bar.

<add key="Title" value="Webmail"></add>

10. This option determines whether WebMail should parse messages to find out if there is an attachment.

<add key="ShowPaperClip" value="false"></add>

NOTE: When this option is turned on, you might encounter performance drops for POP3 accounts since the message must be downloaded completely. This does not affect IMAP4 accounts. Set the value to "true" to enable or to "false" to disable it.

11. This option determines whether users can specify the email address that will be shown in the From field of outgoing emails.  Turn on this option with caution since it allows users to enter any email address.

<add key="AllowChangeFromAddress" value="false"></add>

Set the value to "true" to enable or to "false" to disable it.

Logos

In the custom.config file, you can set the image and hyperlink for the Login logo and the top menu logo.  These images must exist in your selected theme in order to work.

<add key="LoginLogoUrl" value="http://www.vircom.com"></add>
<add key="511LoginLogoImage" value="LogoLogin.gif"></add>
<add key="MenuLogoUrl" value="
http://www.vircom.com"></add>
<add key="511MenuLogoImage" value="LogoMenu.gif"></add>

Custom Login Page or Portal Integration

You can create your own login page or insert the login form in your portal.  Your login page should include a form with the two following form fields:

<input type="text" name="txtLogin"/>
<input type="password" name="txtPassword"/>

The page's form action should be set to "Login.aspx" and the method set to "POST".  Here's a simple Login page:

<html>
<body>
<form action="Login.aspx" method="POST">
<input type="text" name="txtLogin"/>
<input type="password" name="txtPassword"/>
<input type="submit" value="Login"/>
</form>
</body>
</html>

Theme Customization

The WebMail application theme is made through a main CSS file (and if you vary functionality between domains, you'll also need a customized .config file).  DO NOT alter the Style.css file or the Web.config file (or will you will lose all your work when you perform a Modus upgrade).  Instead, you must redefine colors, fonts, and other attributes in the Custom.css, and any functionality variations (see config file attributes above) in the custom.config files.

Any changes you make to the custom files will override the values in the style.css and web.config files.

For domain customization, create css and config files and name them according to the domain, for example:

  • domain.com.css (which should be saved in your custom theme directory)

  • domain.com.config (which should be saved in the webroot directory)

  • domain.net.css (which should be saved in your custom theme directory)

  • domain.net.config (which should be saved in the webroot directory)

These domain files will override the custom.css and custom.config files which override the main style.css and web.config files.

NOTE: you only have to create a domain customized config file if you want to vary functionality between domains as well as the look and feel of it. Otherwise only create a domain customized .css file for your theme.

Changing the Login page color

The login page orange color constitutes of an image (Login_RoundBorder.gif) and a table cell. For example, to change the color to lightgrey:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #tdLoginRight
    {
    background-color: lightgrey;
    }

4. Save and close the file

Note that unless you change the Login_RoundBorder.gif image to lightgrey, it will look odd, so you can edit that file in an image editor or you can hide it altogether. To do so, add the following lines in the custom.css right after the lines previously added: #tdLoginMiddle

    #tdLoginMiddle
    {
    display: none;
    }

Changing the Top Menu color:

The top menu constitutes of an image (LogoMenu.gif) which is configured in the custom.config file, and a gradient image of 1 pixel width. The gradient image adds a level of depth to the menu bar while preserving a very small file size. If you want to change the gradient coloring, open the GradientMenu.gif file in an image editor such as Gimp, PaintShopPro or Photoshop and change the color or gradient value of the image to your preference. You can also discard the gradient in the top menu and only use a solid color, such as lightgrey. To do this:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .Menu
    {
    background-color: lightgrey;
    background-image: none;
    }


4. Save the file

Changing the lists hover color:

Each message status has a separate class. This allows you to define different attributes for when an email is read, unread or deleted. In order to change the hover color, you will need to change each of these classes:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .dgListItemHover
    {
    background-color: lightgrey;
    }
    .dgListItemUnreadHover
    {
    background-color: lightgrey;
    }
    .dgListItemDeletedHover
    {
    background-color: lightgrey;
    }

4. Save the file

Changing the background color of all panels:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .MessageViewMsgHeader,
    .SettingsAccount,
    .SettingsOption,
    .SettingsOptionGeneral,
    .SettingsFolders,
    .SettingsOptionsAntiSpam,
    .SettingsOptionsAntiVirus,
    .SettingsOptionsRules,
    .SettingsOptionsAutoReply,
    .SettingsContacts,
    .SettingsOptionsHome,
    .SettingsOptionsBusiness,
    .SettingsTrusted,
    .SettingsBlocked,
    .SettingsOptionsBlocked,
    .SettingsOptionsTrusted,
    .SettingsAliases,
    .SettingsOptionsReporting,
    #divContactEditor_main,
    .DiagnosticContainer
    {
    background-color: lightgrey;
    }

4. Save the file


Hiding the Server Blocked/Trusted List from the Settings Page:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #Trustedlist_TableRowWhitelistServerTitle,
    #Trustedlist_TableRowWhitelistServerData,
    #Blockedlist_TableRowBlacklistServerTitle,
    #Blockedlist_TableRowBlacklistServerData
    {
    display:none;
    }

4. Save the file

 
 

modusMail only:


Removing Statistics (or other major menu items)

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 Statistics menu option from the web interface.

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #tdStatistics
    {
    display: none;
    }

4. Save the file

NOTE: these instructions apply to the other menu items: #tdAddressBook, #tdFolders, #tdSettings, #tdLogoff. Change the syntax for the line in step 3 from <#tdStatistics> to the menu item you want to hide.

Hiding Sections in Settings:

As with the login page, it is possible to hide certain parts of the page. This is especially useful if you don't want your users to access particular types of settings.

Hiding the options section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsOptions
    {
    display: none;
    }

4. Save the file

Hiding the email filtering section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsFiltering
    {
    display: none;
    }

4. Save the file

Hiding the user contact information section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsUserInfo
    {
    display: none;
    }

4. Save the file

Hiding the rules section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsRules
    {
    display: none;
    }

4. Save the file

Hiding the auto-reply section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAutoreply
    {
    display: none;
    }

4. Save the file

Hiding the external accounts section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAccounts
    {
    display: none;
    }

4. Save the file

Hiding the aliases section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAliases
    {
    display: none;
    }

4. Save the file

Webmail Message Customization

You can customize your own webmail messages (what we call "strings") - this could be especially useful for foreign language support if the translation provided does not adequately communicate an action or system response.

Each language has its own strings file stored in:

..."Vircom"Web"WebRoot"Locales

There is a strings.xml file - the default translations provided with Webmail - and a custom.xml file. Make your changes in the custom.xml file (as follows in the instructions below) and this file will override strings.xml.

Changing default strings

1. Go to the language folder whose messages you want to customize and open both the strings.xml and the custom.xml files

2. Copy and paste the strings to be customized from the strings.xml file into the custom.xml file

3. Modify the strings in the custom.xml file and save it.

4. You can also include HTML formatting instructions in the custom.xml file to specify how you want the customized strings to be displayed. This is useful, for instance, for the TEXT1000 & TEXT1001 tags which are shown at the top and bottom of the right-hand side of the login page respectively (where the beta version information and the upcoming features information was previously displayed).

5. Save the strings.xml file as well to change its timestamp so that the changes you have made can be viewed immediately (not changing the timestamp on the strings.xml file will mean that the customized strings are not shown until you restart IIS).

1.1.5.4. Customizing Webmail/WebQuarantine (Upgrades)

Product: All

Version & Build: 5.13



Important: Before the process of upgrading from 5.0, 5.1 to 5.13 some folder and file changes are required for the customization.  Please perform the following steps before the upgrade is done.


MODUSGATE INSTRUCTIONS:

1.  Locate the appropriate root installation folder for the Quarantine files, e.g. C:\Program Files\Vircom\Web\Quarantine

2. Open up the directory WebRoot\Themes

3. In this directory you will find three or more folders named Gray, Vircom, and your own Custom folder which contains your customization images and styles. Note that we will use the folder name Custom for the rest of this article while your custom folder could have a different name.

4. Rename the Vircom folder to Vircom1.

5. Next make a copy of your Custom folder (for backup purposes) and rename your original Custom folder to Vircom.  Your Themes folder should look like:

 

6. The reason for this is that Modus 5.12 only checks the default Vircom folder for all the style changes.

7. Open up your new custom folder named Vircom.

8. In this directory you will find the customization files named style.css and custom.css.

9. If your customized pages have some custom colors, there is a good chance that you had made these changes in the style.css file. If you know your customizations were made in the custom.css file then proceed to step 12.

10. If you made changes to the style.css file, open it and copy those changes onto the clipboard (CTRL-C).

11. Open the custom.css file in the same directory and paste the clipboard contents into it (CTRL-V).  Save your changes and close both files.  custom.css should now contain your customizations.


12. Once all this is has been done, you can now launch the upgrade for version 5.12.

13. Once the install is complete, open the custom.config file located in c:\Program Files\Vircom\Web\Quarantine\WebRoot folder.

14. There are 2 lines which need to be modified. Both lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

15. Restart Modus Webmail service and IIS. Your customizations should be visible.


MODUSMAIL INSTRUCTIONS:

1. Download and install Modus 5.12.

2. Once the install is complete, open the custom.config file located in C:\Program Files\Vircom\Web\WebMail\WebRoot (assumes a default install location).  

3. There are 3 lines of code which need to be modified. All 3 lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines -<add key="DefaultTheme" value="Vircom"/>.

TO

<add key="DefaultTheme" value="CUSTOM"/>

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

4. Restart Modus Webmail service and IIS. Your customizations should be visible.


1.1.5.5. Configuring Exchange on Windows Small Business Server to listen on an alternate port (25)
Product: modusGate
Version & Build: all

If you're interested in getting modusGate running on the same system as Microsoft Exchange (example, on a Windows Small Business server), with both of them co-existing on the same machine, you cannot have modusGate & Exchange both listening on the same SMTP port 25. 



What you want to do is have modusGate listen on port 25 and it would redirect the traffic to the local exchange server on an alternate port (usually 26).
 
This being said, how do you get Microsoft Exchange to listen on port 26?
 
 
On Exchange 2007 and 2010:
 
 
You can change the receive connector port thus:

1. Go to the Exchange Management Console under Hub Transport
2. Select thereceive connector name you want to change
3. Click on properties
4. Select “network”
5. Choose local IP address
6.  Edit the Receive Connector Bindings
7.  Change the port to the desired port to listen on for SMTP traffic (ex: 26)
 
 

Optional: You can restrict who can send to this SMTP server by editing the “receive mail from remote servers which have these IP addresses”. In this case, you could restrict it to 127.0.0.1 if you want to allow inbound port 26 traffic to only come from modusGate which is sitting on the same box.
 
 
On Exchange 2000 and 2003:
 
 
1. Start the Exchange System Manager.
2. Select the Servername you want to change.
3. Click on Protocols
4. Click  on SMTP
5. Right-click the Default SMTP Virtual Server object
6. Click Properties.



7. On the General tab click the Advanced button
8. Click the Edit button
9. Set the TCP port to desired port (ex: 26).
 
 
 
 
On Exchange 5.5:

 
To change the SMTP listening port on a server that is running Exchange 5.5 from port 25 to another port (for example: port 26) follow these steps:

1.  Open the Control Panel
2. Select Administrative Tools
3. Select Services
4. Stop the Exchange Server Internet Mail service.
5. Open the file c:\Winnt\System32\Drivers\Etc\Services using notepad
6. Locate the line containing: "smtp 25/tcp mail" and change the 25 to 26.
7. Save the Services file.
8. Start the Exchange Server Internet Mail service.


1.1.5.6. Customizing Webmail/WebQuarantine (Upgrades)

Product: All

Version & Build: 5.31 +


modusGate 5.42 includes a brand new quarantine interface.  Customizations of this new interface  is not compatible with prior versions.

You will find your previous WebQuarantine installation and any customization done is still available via the QuarantinePre5-30 virtual directory.

MODUSGATE INSTRUCTIONS:

1.  Locate the appropriate root installation folder for the Quarantine files, e.g. C:\Program Files\Vircom\Web\WebQuarantine

2. Open up the file custom.config

3. At the end of the file, you will find the following lines, each of them denote a configurable setting for WebQuarantine.

  <add key="LoginLogoUrl" value="http://www.vircom.com" />
  <add key="LoginLogoImage" value="logo-login.png" />
  <add key="FooterLoginLogoUrl" value="http://www.vircom.com" />
  <add key="FooterLoginLogoImage" value="footer-logo-login.png" />
  <add key="MobileLoginLogoUrl" value="http://www.vircom.com" />
  <add key="MobileLoginLogoImage" value="logo2.png" />
  <add key="MobileFooterLoginLogoUrl" value="http://www.vircom.com" />
  <add key="MobileFooterLoginLogoImage" value="logo-vircom.png" />
  <add key="MobileMenuLogoImage" value="logo.png" />
  <add key="MenuLogoUrl" value="http://www.vircom.com" />
  <add key="MenuLogoImage" value="logo.png" />
  <add key="FooterLogoUrl" value="http://www.vircom.com" />
  <add key="FooterLogoImage" value="logo-vircom.png" />

4. To use your own logo, change the Image values to your own logo filename, for example:

To change Login page logo, change


  <add key="LoginLogoImage" value="logo-login.png" />

To:

  <add key="LoginLogoImage" value="my-logo-login.png" />

And put your new logo file in the WebRoot\Wres\img folder.

Mobile logos needs to be put in WebRoot\Wres\mobile\images

5. Change the matching Url value to your desired URL.

6. To customize other attributes such as colors, font type, etc, you can overwrite any CSS rules in the file located at WebRoot\Wres\custom\custom.css

MODUSMAIL INSTRUCTIONS:

1. Download and install Modus 5.42.

2. Once the install is complete, open the custom.config file located in C:\Program Files\Vircom\Web\WebMail\WebRoot (assumes a default install location).  

3. There are 3 lines of code which need to be modified. All 3 lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines -<add key="DefaultTheme" value="Vircom"/>.

TO

<add key="DefaultTheme" value="CUSTOM"/>

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

4. Restart Modus Webmail service and IIS. Your customizations should be visible.


1.1.5.7. modus Upgrade Checklist

 modus Upgrade Checklist

Introduction

         This document is intended for existing Vircom customers who are currently running an older version of ModusGate. You should read this document thoroughly before upgrading. If you have any questions or feel something is missing from this document, feel free to contact us by e-mail at support@vircom.com.


Before upgrading, please ensure that you have met the following requirements:


  • Backup your databases (QT, Audit, Monitoring and Sieve) before launching the upgrade
  • Ideally, this should be a full backup
  • If you are using SQL Server Express, ensure that Full Text Indexing is installed
  • For instructions, please consult the following KB article:
  • http://kb.vircom.com/Kbase/default.asp?SID=&Lang=1&id=1621&Lang=1&SID=
  • Ensure that .Net 3.5 Framework is installed
  • For more information, consult the following Microsoft® websites:
  • Microsoft .NET Framework Version 3.5
  • Ensure that you have your current installation package
  • In the event that you must roll back after upgrading, keep a copy of the *.exe installation file
  • If you do not have a copy of the file, before upgrading, send an email to: support@vircom.com requesting it
  • Backup your Windows Registry
  • On the modus server, click on Start > Run
  • Type regedit to open the Registry Editor
  • In the Registry Editor, click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup any customized quarantine reports and/or web applications folders
  • Read the Release Notes for all new features and changes to modus, especially the section regarding encryption

If you opt to use encryption, there is a sieve script that must be added to prevent issues with foreign languages for outbound messages. This script is included in the Release Notes.


Upgrading modusMail/modusGate to v6.0 

         Due to a series of architectural changes in versions upgrading from version 4.7 must be done in two steps:

        1. upgrade from v4.7 to v 5.0 or v5.1

        2. upgrade directly to v6.0

If you are running any version higher the 5.1 you can directly upgrade to v6.0.


Changes to the installation process:

         Starting from v5.31 ModusGate comes with a new web interface. The new interface will not overwrite your existing WebQuarantine programs. This will allow you to continue using the 'old' site until you have had time to test and/or customize the new one.

ModusGate Web Quarantine information:

         There will be a new folder created called WebQuarantine locate under C:\Program Files(x86)\Vircom\Web. This folder will contain the new websites attributes for the new web quarantine pages. The virtual directory will still exist in IIS.


IMPORTANT:

          If you plan to use the monitoring feature, it is preferable to use a Microsoft SQL database instead of the native Access format. Whether to use Microsoft Access or Microsoft SQL depends on your volume of traffic. A good rule of thumb would be to use your quarantine database as your guide: if you use SQL for the quarantine, then you should use it for the monitoring stats as well.


Upgrading ModusGate

Upgrading requires a certain number of precautions. The most important is doing a backup before upgrading:

  • Make sure you have access to your old Modus installation package in case you need to rollback. If you do not have a copy, click on the help -> about button in your ModusGate console to find out what version you have and the build number; contact us by email, and we will be happy to provide you with the original install package.
  • Backup your configuration: - Open the ModusGate administration console and select File > Backup configuration - Select the path where the configuration file will be stored (*.reg file) - Keep this registry file (*.reg) in a safe location as a backup of your Modus configuration.
  • Backup the Registry: - Open the Registry Editor (regedit) - Click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup the Web directory: Located under...\Vircom\Web
  • Backup the databases: Normally located under the root installation of SQL \\Microsoft SQL Server\MSSQLXX.SQLEXPRESS\MSSQL\DATA
  • Proceed with the upgrade.


Upgrading ModusMail

Upgrading requires a certain number of precautions. The most important is doing a backup before upgrading:


Steps to take before upgrading:
  • If you have the hardware and software capability, it would be best to mirror your existing machine so you could hot-swap (switch the IP addresses over) should the upgrade fail. However, in the event that you cannot mirror your server, proceed with the following:
  • Make sure your datasource is up-to-date. If you are using an external datasource for authentication (such as a billing package), ensure that it is up-to-date.
  • Note: If you are using Platypus or RODOPI, check with Boardtown or RODOPI to find out if a new stored procedure is required. In any event, you should run the latest stored procedures for ModusMail.
  • Make sure you have access to your old Modus installation package in case you need to rollback. If you do not have a copy, click on the help -> about button in your ModusMail console to find out what version you have and the build number; contact us by email, and we will be happy to provide you with the original install package.
  • Backup your configuration:

         - Open the ModusMail administration console and select File -> Backup configuration

         - Select the path where the configuration file will be stored (it will be a .reg file)

         - Keep this registry file (*.reg) in a safe location as a backup of your Modus configuration

  • Backup your registry:

         - Open the Registry Editor (regedit)

         - Click on File > Export

         - Select the file location, enter a name for the backup file and click OK

  • Backup the Web directory: Located under...\Vircom\Web
  • Backup the databases: Normally located under the root installation of SQL \\Microsoft SQL Server\MSSQLXX.SQLEXPRESS\MSSQL\DATA
  • Proceed with the upgrade. 

After upgrade is done please ensure that Modus antivirus engines are up and running:

  • In Advanced console go to Virus Tab and see that both AV were successfully updated with the latest version.
  • Go to System Tab and see that all Modus services are up and running.
  • Note! It could take up to 5 minutes to modus to download and install latest versions of antivirus engine and definitions.
  • Customer may use Email flow diagnostic tool provided with modus installation to verify the legit and spam mail flow.







 


 

1.1.6. Version 6.0
Important information about upgrading to modus 6.0
 

System Requirements:
        

Operating System: Windows Server 2003, 2003R2, 2008 (32 and 64-bit), 2008R2, 2012, 2012R2 and Windows Small Business Server (SBS) 2008 x64 and 2011 x64. Windows Web Edition is not supported.

 Web Server: IIS version 6.0 or later.

Components: MDAC 2.8 SP1 or higher, .NET Framework 3.5 SP1 and 4.5 

Exchange Integration: Microsoft Exchange 2003/2007/2010/2013.

SQL Server: 2005 x86/x64, 2008 x86/x64, 2008R2 ,2005 Express Edition, 2008 Express Edition, SQL 2012 x86/x64, SQL 2014 x86/x64. 

Web Browsers:

Desktop: Internet Explorer 8+, Chrome 20+, Safari 4+, or Firefox 12+

Mobile*: iOS Safari 4.0+ (4x, 5.x), Android Browser 4.0+ (4.x, 5.x), Chrome 18+

* Note that the mobile web browsers only apply to the Web Quarantine.


Change Logs
 
See the modusMail / modusGate pages below for their respective change logs and list of fixes. 

1.1.6.1. modusGate
What's New in modusGate 6.0


This latest release of modusGate 6.0 dramatically improves the overall spam catch rate and reduces false positives to 0.00%. Another area that is greatly enhanced is the filtering and the detection of foreign spam emails. Modus 6.0 incorporates a state of the art artificial intelligence (AI) engine that uses a number of real-time cloud-based data services to validate reputation, content and a series of other elements to address zero-day threats. This newest version leverages a live global grid of all electronically transmitted mail to optimally protect businesses and eliminate problems from inbound and outbound emails.


Bug Fixes:


  • Significantly improved spam catch rate for foreign languages.
  • Vircom’s Sender Reputation Service (SRS) is no longer available in ModusGate and has been removed from the application and interfaces. It has been replaced by a superior engine with its own reputation system to push pure performance to maximum degrees (99.9% catch rates and almost no false-positives).
  • Fixed a bug where the advanced console would crash when a user’s "block/trusted" list had a large amount of entries.
  • In Webmonitor, fixed a bug where it was impossible to download the Adobe SVG plug-in from the Vircom site.
  • Improved the directQuarantine authentication mechanism.
  • Fixed a problem where the ModusGate Web Components (WebAdmin, WebMonitor, WebQuarantine) browser cache would not update. 


Operational Considerations:

Although the trade off will benefit the vast majority of customers, the "moduscan" service in ModusGate uses 38% more CPU than the previous versions of the scanning engine with no significant increase in disk I/O. This should only affect customers whose servers are already near maximum capacity and Vircom is committed to optimize this for the next release.


Known Issues:


Support:

Web:           http://www.vircom.com/en/support/customer-service/  
Phone:         1-888-484-7266
Email:          
support@vircom.com 

 

strong style=
1.1.6.2. modusMail
What's New in modusMail 6.0


This latest release of modusMail 6.0 dramatically improves the overall spam catch rate and reduces false positives to 0.00%. Another area that is greatly enhanced is the filtering and the detection of foreign spam emails. Modus 6.0 incorporates a state of the art artificial intelligence (AI) engine that uses a number of real-time cloud-based data services to validate reputation, content and a series of other elements to address zero-day threats. This newest version leverages a live global grid of all electronically transmitted mail to optimally protect businesses and eliminate problems from inbound and outbound emails.

             

Bug Fixes:  
  • Significantly improved spam catch rate for foreign languages.
  • Vircom’s Sender Reputation Service (SRS) is no longer available in modusMail and has been removed from the application and interfaces. It has been replaced by a superior engine with its own reputation system to push pure performance to maximum degrees (99.9% catch rates and almost no false positives).
  • Fixed a problem where installing modusMail was adding an unnecessary webquarantine folder.
  • Fixed a problem when customer could not login to WebMail as they were getting an “unhandled error”.
  • Fixed a problem where Outlook was showing an invalid date for email that had long received headers
  • Fixed a problem where a ZIP file was wrongly identified as a mpg/mp3 file.
  • In WebMonitor, fixed a bug where it was impossible to download the Adobe SVG plug-in from the Vircom site
  • Fixed a problem where modusMail AS was wrongly displaying the Virus tab in WebAdmin
  • Improved directQuarantine authentication mechanism

Operational Considerations:

Although the trade off will benefit the vast majority of customers, the "moduscan" service in ModusGate uses 38% more CPU than the previous versions of the scanning engine with no significant increase in disk I/O. This should only affect customers whose servers are already near maximum capacity and Vircom is committed to optimize this for the next release.

 Known Issues: 

  • When downgrading from 6.0 the "Find" function in Adv.Console does not resolve SCAv2 messages

 

 

Support:    

Web:               http://www.vircom.com/en/support/customer-service/
Phone:            1-888-484-7266
Email:            
support@vircom.com

 


1.1.6.3. Customizing Webmail/WebQuarantine 5.13 (new installs)

Product: All

Version & Build: 5.13



Important: When upgrading to Modus 5.13 the default "Vircom" theme will be applied. Please follow steps below to make the appropriate changes to your custom pages.


The following customization information can be used with both ModusMail and ModusGate - where applicable.

There are many levels of customization that you can make for the web interface, depending on what you want to do:

  • you can substitute your company logo for the Vircom logos (which appear on the login and on each web page)
  • you can modify attributes of the Vircom theme such as the color or the size of the text
  • you can bypass Vircom's login page and have your users access their webmail through your own portal
  • you can create a completely different theme for the web interface that bears no resemblance to the Vircom theme - this theme will not be overwritten by future upgrades, BUT any interface enhancements made by Vircom will not be reflected in your custom-built interface. We provide only very basic customization information here: we provide enough information that if you know what you're doing, you'll know how to support your own customizations and you can go ahead and build your own interface.

Note: The web.config and style.css files contain the product default values. Never alter these files because any work you do will be lost upon upgrading the software. Change the custom.config and custom.css files instead. A Modus upgrade will not overwrite these files, except that it will set back the DefaultTheme to Vircom. This is needed because major changes have been done in the styles for this version.  Please note also that Vircom Technical support cannot debug any custom interfaces you build. We can support only basic style changes to the Vircom interface that include rebranding and recoloring (changing images and modifying CSS styles).

Custom.Config Basic Functionality Customization

NOTE: Any modifications you make in the custom.config file will require you to Stop/Start the IIS Admin service after you have finished.

1. The default language of the WebMail interface is defined in this key. The value must match an existing folder under Locales.

<add key="DefaultLanguage" value="en"></add>

2. The default theme of the WebMail interface is defined in this key. The value must match an existing theme folder under Themes.

<add key="DefaultTheme" value="vircom"></add>

3. This is the domain name or IP address of your WebMail Server service.

<add key="WebMailServerAddress" value="localhost"></add>

4. This is the port number of your WebMail Server service.

<add key="WebMailServerPort" value="31804"></add>

5. This is the character set in which the page will be displayed.

<add key="Charset" value="iso-8859-1"></add>

6. This is the path of the temporary folder that the installation program configures automatically.

<add key="Temp" value=""></add>

7. This is the path of the log folder that the installation program configures automatically.

<add key="LogDir" value=""></add>

8. This is the relative path and file name of the Login page. If you want to design your own login page or you want to integrate webmail with your portal, change this value to your to the relative path and file name of your custom-designed login page. When logging off, users will be redirected to this page instead of the main webmail login page.

<add key="LoginPage" value="Login.aspx"></add>

9. This is the name of the application that will be shown in the browser windows title bar.

<add key="Title" value="Webmail"></add>

10. This option determines whether WebMail should parse messages to find out if there is an attachment.

<add key="ShowPaperClip" value="false"></add>

NOTE: When this option is turned on, you might encounter performance drops for POP3 accounts since the message must be downloaded completely. This does not affect IMAP4 accounts. Set the value to "true" to enable or to "false" to disable it.

11. This option determines whether users can specify the email address that will be shown in the From field of outgoing emails.  Turn on this option with caution since it allows users to enter any email address.

<add key="AllowChangeFromAddress" value="false"></add>

Set the value to "true" to enable or to "false" to disable it.

Logos

In the custom.config file, you can set the image and hyperlink for the Login logo and the top menu logo.  These images must exist in your selected theme in order to work.

<add key="LoginLogoUrl" value="http://www.vircom.com"></add>
<add key="511LoginLogoImage" value="LogoLogin.gif"></add>
<add key="MenuLogoUrl" value="
http://www.vircom.com"></add>
<add key="511MenuLogoImage" value="LogoMenu.gif"></add>

Custom Login Page or Portal Integration

You can create your own login page or insert the login form in your portal.  Your login page should include a form with the two following form fields:

<input type="text" name="txtLogin"/>
<input type="password" name="txtPassword"/>

The page's form action should be set to "Login.aspx" and the method set to "POST".  Here's a simple Login page:

<html>
<body>
<form action="Login.aspx" method="POST">
<input type="text" name="txtLogin"/>
<input type="password" name="txtPassword"/>
<input type="submit" value="Login"/>
</form>
</body>
</html>

Theme Customization

The WebMail application theme is made through a main CSS file (and if you vary functionality between domains, you'll also need a customized .config file).  DO NOT alter the Style.css file or the Web.config file (or will you will lose all your work when you perform a Modus upgrade).  Instead, you must redefine colors, fonts, and other attributes in the Custom.css, and any functionality variations (see config file attributes above) in the custom.config files.

Any changes you make to the custom files will override the values in the style.css and web.config files.

For domain customization, create css and config files and name them according to the domain, for example:

  • domain.com.css (which should be saved in your custom theme directory)

  • domain.com.config (which should be saved in the webroot directory)

  • domain.net.css (which should be saved in your custom theme directory)

  • domain.net.config (which should be saved in the webroot directory)

These domain files will override the custom.css and custom.config files which override the main style.css and web.config files.

NOTE: you only have to create a domain customized config file if you want to vary functionality between domains as well as the look and feel of it. Otherwise only create a domain customized .css file for your theme.

Changing the Login page color

The login page orange color constitutes of an image (Login_RoundBorder.gif) and a table cell. For example, to change the color to lightgrey:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #tdLoginRight
    {
    background-color: lightgrey;
    }

4. Save and close the file

Note that unless you change the Login_RoundBorder.gif image to lightgrey, it will look odd, so you can edit that file in an image editor or you can hide it altogether. To do so, add the following lines in the custom.css right after the lines previously added: #tdLoginMiddle

    #tdLoginMiddle
    {
    display: none;
    }

Changing the Top Menu color:

The top menu constitutes of an image (LogoMenu.gif) which is configured in the custom.config file, and a gradient image of 1 pixel width. The gradient image adds a level of depth to the menu bar while preserving a very small file size. If you want to change the gradient coloring, open the GradientMenu.gif file in an image editor such as Gimp, PaintShopPro or Photoshop and change the color or gradient value of the image to your preference. You can also discard the gradient in the top menu and only use a solid color, such as lightgrey. To do this:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .Menu
    {
    background-color: lightgrey;
    background-image: none;
    }


4. Save the file

Changing the lists hover color:

Each message status has a separate class. This allows you to define different attributes for when an email is read, unread or deleted. In order to change the hover color, you will need to change each of these classes:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .dgListItemHover
    {
    background-color: lightgrey;
    }
    .dgListItemUnreadHover
    {
    background-color: lightgrey;
    }
    .dgListItemDeletedHover
    {
    background-color: lightgrey;
    }

4. Save the file

Changing the background color of all panels:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    .MessageViewMsgHeader,
    .SettingsAccount,
    .SettingsOption,
    .SettingsOptionGeneral,
    .SettingsFolders,
    .SettingsOptionsAntiSpam,
    .SettingsOptionsAntiVirus,
    .SettingsOptionsRules,
    .SettingsOptionsAutoReply,
    .SettingsContacts,
    .SettingsOptionsHome,
    .SettingsOptionsBusiness,
    .SettingsTrusted,
    .SettingsBlocked,
    .SettingsOptionsBlocked,
    .SettingsOptionsTrusted,
    .SettingsAliases,
    .SettingsOptionsReporting,
    #divContactEditor_main,
    .DiagnosticContainer
    {
    background-color: lightgrey;
    }

4. Save the file


Hiding the Server Blocked/Trusted List from the Settings Page:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #Trustedlist_TableRowWhitelistServerTitle,
    #Trustedlist_TableRowWhitelistServerData,
    #Blockedlist_TableRowBlacklistServerTitle,
    #Blockedlist_TableRowBlacklistServerData
    {
    display:none;
    }

4. Save the file

 
 

modusMail only:


Removing Statistics (or other major menu items)

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 Statistics menu option from the web interface.

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #tdStatistics
    {
    display: none;
    }

4. Save the file

NOTE: these instructions apply to the other menu items: #tdAddressBook, #tdFolders, #tdSettings, #tdLogoff. Change the syntax for the line in step 3 from <#tdStatistics> to the menu item you want to hide.

Hiding Sections in Settings:

As with the login page, it is possible to hide certain parts of the page. This is especially useful if you don't want your users to access particular types of settings.

Hiding the options section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsOptions
    {
    display: none;
    }

4. Save the file

Hiding the email filtering section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsFiltering
    {
    display: none;
    }

4. Save the file

Hiding the user contact information section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsUserInfo
    {
    display: none;
    }

4. Save the file

Hiding the rules section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsRules
    {
    display: none;
    }

4. Save the file

Hiding the auto-reply section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAutoreply
    {
    display: none;
    }

4. Save the file

Hiding the external accounts section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAccounts
    {
    display: none;
    }

4. Save the file

Hiding the aliases section:

1. Go to the Themes"Vircom folder
2. Open the custom.css file
3. Add the following lines:

    #SettingsAliases
    {
    display: none;
    }

4. Save the file

Webmail Message Customization

You can customize your own webmail messages (what we call "strings") - this could be especially useful for foreign language support if the translation provided does not adequately communicate an action or system response.

Each language has its own strings file stored in:

..."Vircom"Web"WebRoot"Locales

There is a strings.xml file - the default translations provided with Webmail - and a custom.xml file. Make your changes in the custom.xml file (as follows in the instructions below) and this file will override strings.xml.

Changing default strings

1. Go to the language folder whose messages you want to customize and open both the strings.xml and the custom.xml files

2. Copy and paste the strings to be customized from the strings.xml file into the custom.xml file

3. Modify the strings in the custom.xml file and save it.

4. You can also include HTML formatting instructions in the custom.xml file to specify how you want the customized strings to be displayed. This is useful, for instance, for the TEXT1000 & TEXT1001 tags which are shown at the top and bottom of the right-hand side of the login page respectively (where the beta version information and the upcoming features information was previously displayed).

5. Save the strings.xml file as well to change its timestamp so that the changes you have made can be viewed immediately (not changing the timestamp on the strings.xml file will mean that the customized strings are not shown until you restart IIS).

1.1.6.4. Customizing Webmail/WebQuarantine (Upgrades)

Product: All

Version & Build: 5.13



Important: Before the process of upgrading from 5.0, 5.1 to 5.13 some folder and file changes are required for the customization.  Please perform the following steps before the upgrade is done.


MODUSGATE INSTRUCTIONS:

1.  Locate the appropriate root installation folder for the Quarantine files, e.g. C:\Program Files\Vircom\Web\Quarantine

2. Open up the directory WebRoot\Themes

3. In this directory you will find three or more folders named Gray, Vircom, and your own Custom folder which contains your customization images and styles. Note that we will use the folder name Custom for the rest of this article while your custom folder could have a different name.

4. Rename the Vircom folder to Vircom1.

5. Next make a copy of your Custom folder (for backup purposes) and rename your original Custom folder to Vircom.  Your Themes folder should look like:

 

6. The reason for this is that Modus 5.12 only checks the default Vircom folder for all the style changes.

7. Open up your new custom folder named Vircom.

8. In this directory you will find the customization files named style.css and custom.css.

9. If your customized pages have some custom colors, there is a good chance that you had made these changes in the style.css file. If you know your customizations were made in the custom.css file then proceed to step 12.

10. If you made changes to the style.css file, open it and copy those changes onto the clipboard (CTRL-C).

11. Open the custom.css file in the same directory and paste the clipboard contents into it (CTRL-V).  Save your changes and close both files.  custom.css should now contain your customizations.


12. Once all this is has been done, you can now launch the upgrade for version 5.12.

13. Once the install is complete, open the custom.config file located in c:\Program Files\Vircom\Web\Quarantine\WebRoot folder.

14. There are 2 lines which need to be modified. Both lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

15. Restart Modus Webmail service and IIS. Your customizations should be visible.


MODUSMAIL INSTRUCTIONS:

1. Download and install Modus 5.12.

2. Once the install is complete, open the custom.config file located in C:\Program Files\Vircom\Web\WebMail\WebRoot (assumes a default install location).  

3. There are 3 lines of code which need to be modified. All 3 lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines -<add key="DefaultTheme" value="Vircom"/>.

TO

<add key="DefaultTheme" value="CUSTOM"/>

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

4. Restart Modus Webmail service and IIS. Your customizations should be visible.


1.1.6.5. Configuring Exchange on Windows Small Business Server to listen on an alternate port (25)
Product: modusGate
Version & Build: all

If you're interested in getting modusGate running on the same system as Microsoft Exchange (example, on a Windows Small Business server), with both of them co-existing on the same machine, you cannot have modusGate & Exchange both listening on the same SMTP port 25. 



What you want to do is have modusGate listen on port 25 and it would redirect the traffic to the local exchange server on an alternate port (usually 26).
 
This being said, how do you get Microsoft Exchange to listen on port 26?
 
 
On Exchange 2007 and 2010:
 
 
You can change the receive connector port thus:

1. Go to the Exchange Management Console under Hub Transport
2. Select thereceive connector name you want to change
3. Click on properties
4. Select “network”
5. Choose local IP address
6.  Edit the Receive Connector Bindings
7.  Change the port to the desired port to listen on for SMTP traffic (ex: 26)
 
 

Optional: You can restrict who can send to this SMTP server by editing the “receive mail from remote servers which have these IP addresses”. In this case, you could restrict it to 127.0.0.1 if you want to allow inbound port 26 traffic to only come from modusGate which is sitting on the same box.
 
 
On Exchange 2000 and 2003:
 
 
1. Start the Exchange System Manager.
2. Select the Servername you want to change.
3. Click on Protocols
4. Click  on SMTP
5. Right-click the Default SMTP Virtual Server object
6. Click Properties.



7. On the General tab click the Advanced button
8. Click the Edit button
9. Set the TCP port to desired port (ex: 26).
 
 
 
 
On Exchange 5.5:

 
To change the SMTP listening port on a server that is running Exchange 5.5 from port 25 to another port (for example: port 26) follow these steps:

1.  Open the Control Panel
2. Select Administrative Tools
3. Select Services
4. Stop the Exchange Server Internet Mail service.
5. Open the file c:\Winnt\System32\Drivers\Etc\Services using notepad
6. Locate the line containing: "smtp 25/tcp mail" and change the 25 to 26.
7. Save the Services file.
8. Start the Exchange Server Internet Mail service.


1.1.6.6. Customizing Webmail/WebQuarantine (Upgrades)

Product: All

Version & Build: 5.31 +


modusGate 5.42 includes a brand new quarantine interface.  Customizations of this new interface  is not compatible with prior versions.

You will find your previous WebQuarantine installation and any customization done is still available via the QuarantinePre5-30 virtual directory.

MODUSGATE INSTRUCTIONS:

1.  Locate the appropriate root installation folder for the Quarantine files, e.g. C:\Program Files\Vircom\Web\WebQuarantine

2. Open up the file custom.config

3. At the end of the file, you will find the following lines, each of them denote a configurable setting for WebQuarantine.

  <add key="LoginLogoUrl" value="http://www.vircom.com" />
  <add key="LoginLogoImage" value="logo-login.png" />
  <add key="FooterLoginLogoUrl" value="http://www.vircom.com" />
  <add key="FooterLoginLogoImage" value="footer-logo-login.png" />
  <add key="MobileLoginLogoUrl" value="http://www.vircom.com" />
  <add key="MobileLoginLogoImage" value="logo2.png" />
  <add key="MobileFooterLoginLogoUrl" value="http://www.vircom.com" />
  <add key="MobileFooterLoginLogoImage" value="logo-vircom.png" />
  <add key="MobileMenuLogoImage" value="logo.png" />
  <add key="MenuLogoUrl" value="http://www.vircom.com" />
  <add key="MenuLogoImage" value="logo.png" />
  <add key="FooterLogoUrl" value="http://www.vircom.com" />
  <add key="FooterLogoImage" value="logo-vircom.png" />

4. To use your own logo, change the Image values to your own logo filename, for example:

To change Login page logo, change


  <add key="LoginLogoImage" value="logo-login.png" />

To:

  <add key="LoginLogoImage" value="my-logo-login.png" />

And put your new logo file in the WebRoot\Wres\img folder.

Mobile logos needs to be put in WebRoot\Wres\mobile\images

5. Change the matching Url value to your desired URL.

6. To customize other attributes such as colors, font type, etc, you can overwrite any CSS rules in the file located at WebRoot\Wres\custom\custom.css

MODUSMAIL INSTRUCTIONS:

1. Download and install Modus 5.42.

2. Once the install is complete, open the custom.config file located in C:\Program Files\Vircom\Web\WebMail\WebRoot (assumes a default install location).  

3. There are 3 lines of code which need to be modified. All 3 lines are listed below.  Note that we are using cow.gif and eyes.gif as examples of customized gifs you would have for the Login logo and the Menu Logo respectively.

Change lines -<add key="DefaultTheme" value="Vircom"/>.

TO

<add key="DefaultTheme" value="CUSTOM"/>

Change lines - <add key="LoginLogoImage" value="custom.gif"></add>

TO

<add key="511LoginLogoImage" value="cow.gif"></add>

And change lines - <add key="MenuLogoImage" value="custom.gif"></add>

TO

<add key="511MenuLogoImage" value="eyes.gif"></add>

4. Restart Modus Webmail service and IIS. Your customizations should be visible.


1.1.6.7. modus Upgrade Checklist

 modus Upgrade Checklist

Introduction

         This document is intended for existing Vircom customers who are currently running an older version of ModusGate. You should read this document thoroughly before upgrading. If you have any questions or feel something is missing from this document, feel free to contact us by e-mail at support@vircom.com.


Before upgrading, please ensure that you have met the following requirements:


  • Backup your databases (QT, Audit, Monitoring and Sieve) before launching the upgrade
  • Ideally, this should be a full backup
  • If you are using SQL Server Express, ensure that Full Text Indexing is installed
  • For instructions, please consult the following KB article:
  • http://kb.vircom.com/Kbase/default.asp?SID=&Lang=1&id=1621&Lang=1&SID=
  • Ensure that .Net 3.5 Framework is installed
  • For more information, consult the following Microsoft® websites:
  • Microsoft .NET Framework Version 3.5
  • Ensure that you have your current installation package
  • In the event that you must roll back after upgrading, keep a copy of the *.exe installation file
  • If you do not have a copy of the file, before upgrading, send an email to: support@vircom.com requesting it
  • Backup your Windows Registry
  • On the modus server, click on Start > Run
  • Type regedit to open the Registry Editor
  • In the Registry Editor, click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup any customized quarantine reports and/or web applications folders
  • Read the Release Notes for all new features and changes to modus, especially the section regarding encryption

If you opt to use encryption, there is a sieve script that must be added to prevent issues with foreign languages for outbound messages. This script is included in the Release Notes.


Upgrading modusMail/modusGate to v6.0 

         Due to a series of architectural changes in versions upgrading from version 4.7 must be done in two steps:

        1. upgrade from v4.7 to v 5.0 or v5.1

        2. upgrade directly to v6.0

If you are running any version higher the 5.1 you can directly upgrade to v6.0.


Changes to the installation process:

         Starting from v5.31 ModusGate comes with a new web interface. The new interface will not overwrite your existing WebQuarantine programs. This will allow you to continue using the 'old' site until you have had time to test and/or customize the new one.

ModusGate Web Quarantine information:

         There will be a new folder created called WebQuarantine locate under C:\Program Files(x86)\Vircom\Web. This folder will contain the new websites attributes for the new web quarantine pages. The virtual directory will still exist in IIS.


IMPORTANT:

          If you plan to use the monitoring feature, it is preferable to use a Microsoft SQL database instead of the native Access format. Whether to use Microsoft Access or Microsoft SQL depends on your volume of traffic. A good rule of thumb would be to use your quarantine database as your guide: if you use SQL for the quarantine, then you should use it for the monitoring stats as well.


Upgrading ModusGate

Upgrading requires a certain number of precautions. The most important is doing a backup before upgrading:

  • Make sure you have access to your old Modus installation package in case you need to rollback. If you do not have a copy, click on the help -> about button in your ModusGate console to find out what version you have and the build number; contact us by email, and we will be happy to provide you with the original install package.
  • Backup your configuration: - Open the ModusGate administration console and select File > Backup configuration - Select the path where the configuration file will be stored (*.reg file) - Keep this registry file (*.reg) in a safe location as a backup of your Modus configuration.
  • Backup the Registry: - Open the Registry Editor (regedit) - Click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup the Web directory: Located under...\Vircom\Web
  • Backup the databases: Normally located under the root installation of SQL \\Microsoft SQL Server\MSSQLXX.SQLEXPRESS\MSSQL\DATA
  • Proceed with the upgrade.


Upgrading ModusMail

Upgrading requires a certain number of precautions. The most important is doing a backup before upgrading:


Steps to take before upgrading:
  • If you have the hardware and software capability, it would be best to mirror your existing machine so you could hot-swap (switch the IP addresses over) should the upgrade fail. However, in the event that you cannot mirror your server, proceed with the following:
  • Make sure your datasource is up-to-date. If you are using an external datasource for authentication (such as a billing package), ensure that it is up-to-date.
  • Note: If you are using Platypus or RODOPI, check with Boardtown or RODOPI to find out if a new stored procedure is required. In any event, you should run the latest stored procedures for ModusMail.
  • Make sure you have access to your old Modus installation package in case you need to rollback. If you do not have a copy, click on the help -> about button in your ModusMail console to find out what version you have and the build number; contact us by email, and we will be happy to provide you with the original install package.
  • Backup your configuration:

         - Open the ModusMail administration console and select File -> Backup configuration

         - Select the path where the configuration file will be stored (it will be a .reg file)

         - Keep this registry file (*.reg) in a safe location as a backup of your Modus configuration

  • Backup your registry:

         - Open the Registry Editor (regedit)

         - Click on File > Export

         - Select the file location, enter a name for the backup file and click OK

  • Backup the Web directory: Located under...\Vircom\Web
  • Backup the databases: Normally located under the root installation of SQL \\Microsoft SQL Server\MSSQLXX.SQLEXPRESS\MSSQL\DATA
  • Proceed with the upgrade. 

After upgrade is done please ensure that Modus antivirus engines are up and running:

  • In Advanced console go to Virus Tab and see that both AV were successfully updated with the latest version.
  • Go to System Tab and see that all Modus services are up and running.
  • Note! It could take up to 5 minutes to modus to download and install latest versions of antivirus engine and definitions.
  • Customer may use Email flow diagnostic tool provided with modus installation to verify the legit and spam mail flow.







 


 

1.2. Known Issues (non-release related)
1.2.1. Known Issue: Mailing list subscriptions by HTML email fails for some addresses

Product: modusMail

Version & Build:  All 

 
Issue:
 
Using an HTML email message to subscribe multiple email addresses to a mailing list will work for some addresses but not all.
 
Cause:
 
This problem can occur in the following circumstances:
 
1. You enter a series of addresses in the body and hit Enter at the end of each line except the last one, so that the hyperlink is not added to the last address (see list below). The hyperlinked addresses will be subscribed to the list, but the non-linked address will not be added.
 
SUBSCRIBE list1 user@gmail.com <Enter>
SUBSCRIBE list1 username@yahoo.com <Enter>
SUBSCRIBE list1 user@yahoo.com
 
2. You enter a series of addresses in the body, and the hyperlinks are formed for each address, but you then edit or alter one of the addresses. Example, after creating the above list, you return to the first line and change the address to user.Name@gmail.com. The resulting subscriptions will work for all but the first or modified address.
 
 
Resolution:
 
Once the subscription list is complete, and before clicking Send, you must hit Enter at the end of the final address on the list to properly set all the hyperlinks. This is also true if/when changes are made to any of the addresses: you must return to the last line of the list and hit Enter.
 
This will ensure that all addresses are added to the mailing list.
 
 
1.2.2. Known Issue: VsScanOrder Registry key must be removed.

 

Product: All

Version & Build: All


 

Description of Problem:

There has been increase of spam that has been bypassing our Modus scanning engines. there is currently a registry key that must be deleted to have this issue corrected.

 

Solution:

 

  • Log into the modus server.
  • open up the registry by typing regedit in the run command from the start menu.
  • locate the VsScanOrder registry key under HKLM\Software\Wow6432Node\Vircom\Vopmail
  • Once you have located it please DELETE it.
  • Do not delete the key VsScanningOrder.
  • then close the registry and restart the modusscan services so the setting may take effect.

 

1.3. Configuration Information
1.3.1. modusGate & modusMail
1.3.1.1. How-To: Configure TLS for POP, IMAP, SMTP
 

Product: All

Version & Build: All

 
The purpose of this document is to describe all steps needed to set up TLS encryption certificates on modus to secure email communications via POP/IMAP/SMTP. Note that only SMTP connections are applicable on modusGate.

Preconditions: 

You must have a certificate generated for the computer name or IP where it will be deployed, and it must be 'readable' by that computer.

Server Installation:

  • Launch the MMC console by clicking Start > Run, and entering mmc.exe
  • On the File menu, select Add/Remove Snap-in
  • Click on Add in the Standalone tab
  • Select  Certificates and click on Add
  • Select  Computer account in the Certificates Snap-in window
  • Click on Finish and Close to exit the screens
  • Close the Add/Remove Snap-in window
  • Click on OK on the Add/Remove Snap-in to validate the operation
  • Expand the certificate tree and right-click on Personal
  • Select All tasks > Import
  • Browse to select your certificate and validate the operation
  • Close the MMC console

 

Single Certificate Installation:

  • Launch the modus Administration Console
  • Select the Security tab
  • Select the Encryption & Certificates tab
  • Select your new certificate name from the Use certificate dropdown menu
  • Select which services will use this certificate (POP/IMAP/SMTP)
  • If necessary, change the corresponding port number(s)
  • Click on IP Addresses to enter all IPs for which the certificate must be used/forced
  • Click on Apply to save the changes
  • Go to System and stop/restart all services


Multiple Certificate Installation:

  • Launch the modus Administration Console
  • Select the Security tab
  • Select the Encryption & Certificates tab
  • Click on Advanced Certificate Setup
  • Link each certificate to a specific IP address (virtual IPs are valid)
  • On the Use certificate dropdown list, select the certificate you want to configure
  • Select which services will use this certificate (POP/IMAP/SMTP)
  • If necessary, change the corresponding port number(s)
  • Click on IP Addresses and enter all IPs for which the certificate must be used/forced
  • Click on Apply to save the changes
  • Go to System and stop/restart all services

 

1.3.1.2. How-To: Install modus Web Components on a Separate Server
 

Product: All

Version & Build: All

 
Please see the attached document for step-by-step configuration information.
1.3.1.3. Info: Configuring modus with a Proxy Server
Product: All
Version & Build: All
 

If you use the proxy settings in modusGate or modusMail and are experiencing issues with anti-spam / anti-virus updates or V6 license key validation (format = xxxx.xxxx.xxxx.xxxx.xxxx.xxxx), please verify the following configuration requirements:

1. Allow all traffic IN and OUT from *.vircom.com

2. Follow the instructions outlined in this Microsoft document:
      http://support.microsoft.com/default.aspx?scid=kb;en-us;317541
 
3. From the command prompt, run the following:
    C:\>proxycfg -u


Note:

Failing to follow steps 2 and 3 will result in a failure to update your spam and virus filters. All updates are done through HTTPS, therefore your modus server must be able to update its root certificate to confirm the validity of Vircom's wildcard certificate (*.vircom.com).

If you have any questions or difficulties, please contact support@vircom.com or call 514-845-8474.

 
1.3.1.4. Info: BATV Default Subject Tags
Product: All
Version & Build: 4.7 and above
 

Background:
 
The BATV feature allows you to specify a list of subject tags that will trigger the scan engine to verify whether a bounce message is legitimate or not. A list of default subject tags is provided when the feature is enabled.
 
Issue:
 
The default Subject Tags settings are set to Specify the list with the following tags listed onscreen:
  • failure
  • returned
  • returning
  • undelivered
  • undeliverable
If you select Use the list from this file then switch back to Specify the list, the default tag list does not get restored.
 
Before making any changes to the settings, it is recommended to back up the current list by exporting it to a text file and saving it. If the original set of tags is lost, the list can be imported and restored at any time.
 
 
1.3.1.5. How-To: Force Spam Updates
 

Product:  All

Version & Build:  All

 

 

If automatic spam updates are not being performed, you can force an update:

 

  • On the modus server, open the Registry Editor
  • Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ModusAdm\Parameters
  • Delete the following 2 keys
    • SieveUpdateLUD
    • SieveUpdateLUSN
  • Exit the Registry Editor
  • From the modus Console, go to Spam – Properties – Auto-Updates
  • Click on Update Now
  • Wait approximately 10-15 minutes
  • Go to Spam – Properties – General and ensure that the date and time of the last update is current

 

 

1.3.1.6. How-to: Repair databases that are missing objects such as indexes or constraints

 

Product: All

Version & Build: 4.5.654 and above

 

 

Installed with modus is a tool called DbTool.exe that can be used to create a new database or upgrade an existing one.

 

Options on the command line are:

 

  • -get dbschema [-Mailserver mserver]
    • Displays the database configuration for the specified schema
    • Could be the default, qt, sieve, monitoring, audit or shared
    • The mailserver, if specified, is the machine running modus
      • The default is the local machine

 

  • -set dbschema -override yes/no [-Server server -Driver driver -DbName db

      -UserName user -UserPwd pwd -AdminName admin –AdminPwd adminpwd]

      [-Mailserver mserver]

o    If override is no, the database parameters should not be given

o    If override is yes, the database parameters should be given

o    The mailserver, if specified, is the machine running modus

      •  The default is the local machine

 

  • -validate dbschema [-Server server -Driver driver -DbName db -UserName user -UserPwd pwd]
    • If the configuration parameters are not given, the validation will be made on the current database configuration

 

  • -update dbschema [-Server server -Driver driver -DbName db -UserName user -UserPwd pwd -AdminName admin -AdminPwd adminpwd] -xml xmlfile

 

  • -help
    • Displays this help screen.

 

·         -version

o    Displays the product version

 

 
 

 

To resolve a missing index problem:

 

·         Create a new database

·         Import the data from the old database to the new database

·         Change to settings so that modus uses the new database

 

 

  

 

Example: missing indexes for the quarantine database

 

There are two options to resolve this problem:

 

Ø  Option 1: create a new database via the modus Console (recommended)

 

§  Stop the modus services

 

§  From the Console, go to System – Properties – System Databases

o    For the Quarantine Database, click on Edit

o    At Database Name, enter the name for the new database and click on OK

o    Confirm that you want to create a new database

·         modus will create the database automatically

 

§  Use your favorite tool to import the data from the old database to the new one

 

§  Start the modus services

 

 

Ø  Option 2: Create a new database via the database program

 

§  Create a new database

o    Go to Enterprise Manager or Management Studio

o    Create a new empty database

 

§  From a Command Prompt, run the DbTool to create the database schema

o    The following is an example (using the abovementioned command line options):

·         DbTool.exe –update qt –Server localhost –Driver SQLServer –DbName newdb –UserName sa –UserPwd as  –xml DbUpdates.xml

 

§  Stop the modus services

 

§  Use your favorite tool to import the data from the old database to the new one

 

§  Change the settings in the Console to point to the new database

o    Go to System – Properties – System Databases

o    Edit the Quarantine Database to point to the newly created database

o    Click on Test Connection to test the connection

 

§  Start the modus services

 

 

 

1.3.1.7. How-to: Log Modus Logs to a *nix Host
 

Product: All

Version & Build: All

 

 

 

Programs used:

 

 

Tested with:

 

  • Gentoo Linux
  • Windows 2003 Server
  • ModusMail

 

 

 

Procedures:

 

  • Configure syslog-ng on the *nix machine (loghost) to accept incoming syslog connections on UDP port 514:
    • /etc/syslog-ng/syslog-ng.conf: udp(port(514))

 

  • Restart syslog-ng on the *nix server

 

 

  • Once installed create a file named syslog.host and place it in
    C:\Program Files\syslog\etc\syslog.host

 

  • Contents of syslog.host is the name or the ip of the *nix syslog host running syslog-ng followed by the port (default 514):
    • loghost:514

 

 

  • Run the logger/tail command:
    • C:\SFU\commontail -f C:\path\to\modus\logs\OPR20070208.LOG  | logger -t MODUS

 

  • Logger command line options:
     -f = File to feed/tail to the syslog daemon
     -t = Tag to prepend to the messages
     -l = Hostname to log to (loghost)
     -a = port to use (514 is the udp port for syslog)
     -m = protocol to use (udp)
     -p = priority to log to (user.notice is the default)

 

 

 

Example output on the loghost:

 #tail -f /var/log/messages
 Feb  8 15:51:42 SST-NG modus: <<< 550 <foo@foo.com is not a valid mailbox
 Feb  8 15:51:42 SST-NG modus: ---- SMTPDS log entry made at 02/01/2007 23:59:43
 Feb  8 15:51:42 SST-NG modus: This is session 048EB510
 Feb  8 15:51:42 SST-NG modus: Protocol error: 451 VS14-PR Mailbox bounce
 arrival rate exceeds system limit (#4.2.2) mailinglist@ncix.net\r\n
 Feb  8 15:51:42 SST-NG modus: ---- SMTPRS log entry made at 02/01/2007 23:59:55
 Feb  8 15:51:42 SST-NG modus: SMTP command failed when talking to 1.2.3.4:
 Feb  8 15:51:42 SST-NG modus:  RCPT TO: <foo@foo.com
 Feb  8 15:51:42 SST-NG modus: <<< 550 5.1.1 <foo@foo.com is not a valid mailbox


 

Notes:

  • Ideally you can create a batch file to pickup new log files from modus
     when they change
  •  Another tail program you can use is multitail which comes with the cygwin
     tools (
    http://www.cygwin.com)  this allows you to tail multiple files and merge the output into logger
  • Vircom does not know how much of a performance hit this can put on the box but you can force the logs (OPR*.LOG) to a syslog interface

1.3.1.8. How-To: Bypass Attachment Filtering TO: Certain Users or FROM: Certain Users

 

Product: All

Version & Build: 4.3 and above

 

 

 

Issue:  There is no way to whitelist a user or source for attachment filtering.  If you want to allow certain individuals to send and/or receive mail containing a particular type of attachment, you can use Sieve.

 

 

Using Sieve

 

If a certain type of attachment is received, fileinto (put the physical file) into the …Vircom\Modus<Gate or Mail>\spool\incoming folder which effectively bypasses all filtering mechanisms.

 

 

The following examples use a standard ModusGate installation. 

 

Example:  Allowing PDF and ZIP Files TO: Certain Users on a Local Domain

if attachment :matches ["*.pdf*","*.zip*"] {

   if envelope :contains "to" ["bob@yourdomain.com", "john@yourdomain.com"] {

      fileinto "c:\\program files\\vircom\\modusgate\\spool\\incoming";

      stop;

      }

}

 

 

Example2:  Allowing PDF and ZIP files FROM: a Certain User or Domain

 if attachment :matches ["*.pdf*","*.zip*"] {

   if envelope :contains "from" ["@xyz.com", "timmy@hotmail.com"] {

      fileinto "c:\\program files\\vircom\\modusgate\\spool\\incoming";

      stop;

      }

}

 

 

This information can be found in the following KB: How-To: Write simple sieve scripts

 

 

1.3.1.9. Info: What is an .ASY File Extension

Product: All

Version & Build: All


In an effort to effectively catch spam entering your mail system, Vircom has enabled a “delay” function for certain types of spam.  When a message is not identified as spam, but is suspicious, it is renamed as an .ASY file and stored in the …\Spool\Invirus directory for 30 minutes.  During this 30 minute delay, Modus receives the latest spam definition files.  After the update process, if the suspicious spam is correctly identified (as spam or not), Modus releases it from the Invirus directory and processes it accordingly.

Only incoming mail from outside of your environment is affected (not local or trusted).  This “delay” only affects a small percentage of incoming mail.

 

1.3.1.10. How-To: Reduce Image Spam by Using Dynamic IP Blocklists

Product: All

Version & Build: 5.20+


Problem:  Image-Spam is getting through the scanning engine

Explanation: New techniques are being used by spammers camouflage the messages.  We are responding to these problems as quickly as possible.  However, the cat-and-mouse game continues and whenever we issue a countermeasure, spammers come out with something to counter this.


Workaround: Use Dynamic IP Blocklists

Most spam originates from compromised home computers (Bots) which are controlled by a single controlling entity (Botnet).  These machines become compromised through vulnerabilities in Windows that virus writers exploit and act as open proxies on unusual ports that are not usually blocked by ISPs.  Normally, no mail should originate from home computers other than mail sent directly by the end-users.

There are blacklists that list the IP ranges used by various ISPs to provide dynamic IP addresses to end-users.  A notable Dynamic IP range list is operated by sorbs.net.  

In the past, customers have been reticent to use these blacklists for two reasons:

a) Their own IP blocks may be listed

b) Their connectivity providers (virtual ISPs) may have their IP ranges listed

However, in Modus 4.35.480, we implemented a new feature where we can wait until the AUTH LOGIN has occurred (SMTP Authentication) before the RBL check kicks in.  Therefore, if your users already use SMTP Authentication to relay through you, they will not be blocked if they come from a blacklisted (or listed) IP.

It has become much safer to use the Dynamic IP-based blacklists:

  • Open the Modus Console
  • Go to Security – Real-time Blacklists
    • Enable Perform a lookup for the SMTP host in the Real-Time Blacklist
  • Click on IP Exclusion
    • Enter your IP ranges
  • Do not check Reject connection immediately if the host is blacklisted
  • Enable the Perform RBL check after mailbox authentication
  • Click on RBL Servers
    • Add dul.dnsbl.sorbs.net
      • If you're feeling adventurous, you could use dnsbl.sorbs.net
  • Click Apply
Stop and Start the SMTPRS service under System - Services

 

 

 

With these changes, more spam should be blocked, including image-based spam.  If you have any problems where an end-user cannot send mail through your server as a relay, add their IP address or IP range (class C) to the IP exclusions list.


Caveats:

With this configuration, the connection stays open longer for each IP that hits the machine on Port 25.  It's important, then, to monitor things carefully after enabling this feature to see if users experience problems sending mail through your server (as a relay).  

This configuration requires that people who send mail through your server do so through SMTP Authentication.  If this is not the case for your particular user-base, you should not implement this how-to unless you are sure that the majority of your users are using SMTP Authentication.

 

 

 

 

 

1.3.1.11. How-To: Enable Persist Sorting Order

 

Product: All

Version & Build: All

 

 

 

Overview

It is now possible for users to have their preferred list sorting order persisted between web sessions.  If this feature is enabled, when the user makes a change to the list sorting order, WebMail will remember the change and persist it for future web sessions.

NOTE:  this feature affects the performance speed of WebMail.  It is disabled, by default, because when users log in, their inbox takes longer to load as the server must re-orders their messages according to any sorting preferences they made during their last web session.

 

  • Go to …\Program Files\Vircom\web\webquarantine
  • Open the WebMailSvr.ini file
  • Add the following line under [Default:Settings]:
    • PersistSort=1
  • Save the file  

* You can turn off this feature by setting the line to equal ‘0

 

1.3.1.12. Info: Fingerprinting Explained

Version & Build: All

When Modus receives an attachment, it first looks at the file extension and, if it is forbidden, the file is quarantined.  If fingerprinting is enabled and the extension is not forbidden, Modus then determines if the file is of a known type.


Example:

  • Modus receives an attachment that has been renamed tryme.txt from tryme.exe
  • Fingerprinting is enabled (as it is by default)
  • Even though .txt files are not forbidden, Modus recognizes that the file has been renamed from .exe to .txt and quarantines it because .exe is in the fingerprinting dictionary
  • However, if the file has no signature, if the signature is corrupt or if Modus cannot determine the file type, the attachment will go undetected

Fingerprinting checks for the following file types (not extensions):

  • .exe, .dll, .mdb, .gif, .jpg, .bmp, .mpg, .mp3 and .wmv and OLE components such as .doc, .vsd, .xls and .ppt
  • The accuracy rate for fingerprinting is not 100%
  • .mp3, .wmv and audio .mpg files have a better accuracy rate (v4.35+ only)
  • video .mpg files have a low accuracy rate

Fingerprinting is linked to the attachment scanning level (Normal, Strong, Extreme or Disabled):

  • If an administrator has set the scanning level to Normal and an attachment, file.wmv (scanned for only under the Extreme category), is received, fingerprinting will not  occur
  • If an extension is added to the list of forbidden attachments, Modus will check the extension only
  • Fingerprinting will not detect the file type, it will only detect the file signatur
1.3.1.13. Info: RBL Check After AUTH LOGIN

 

 

Product: All

Version & Build: 4.35.480+

 

 

With the release of Build 480, the Real-Time Blacklist (RLB) check can be performed after mailbox authentication.  With this feature, a successful AUTH LOGIN will bypass the RBL check, allowing access to the server even if the IP address has been blocked.

 

  • To enable this feature, from the Console, go to:  Security - Properties - Real-Time Blacklist

o        Check the option Perform RBL check after mailbox authentication

 

  • Do not check the Reject connection immediately if the host is blacklisted option

 

 

Overview:

 

In the past, RBL checking occurred after mailbox authentication.  Therefore, if users, (even legitimate users) coming from blacklisted IP addresses would be blocked if you used RBLs.

 

By enabling this feature, Modus waits until the user is authenticated (SMTP Auth or POP/IMAP before SMTP) before closing the connection if the IP address is blacklisted.  Therefore, if a user comes from a blacklisted IP address but is able to authenticate, Modus allows the user to connect to the SMTP port.  If the user is unable to authenticate, the connection is closed.

 

 

Drawback:

 

This maintains an open session until after the Mail From /Auth Login and reduces the effectiveness of RBLs as a load control mechanism.

 

 

Advantage:

 

SMTP AUTH overrides RBL check which is good for ISP an vISP clients.

 

 

Note:  In an upcoming service pack, we will be changing this feature so that if one option is enabled, the other will be disabled.  For the time being, however, follow these instructions to the letter.

 

 

 

 

1.3.1.14. How-To: Configure ODBC for a 64-bit environment

 

Product: All

Version & Build: All

 

 

Configuring ODBC for Small Business Server 2003 R2 x64

 

There are 2 ODBC control applets – one for a 32-bit operating environment and one for a 64-bit operating environment.  If you are moving Modus to 64-bit environment, follow these instructions to get the ODBC DSNs recognized:

 

  • Open Windows Explorers, go to C:\WINDOWS\SysWOW64\ and run odbcad32.exe
    • This will setup the DSNs using the 32-bit drivers instead of the native 64-bit drivers found in Administrative Tools -> Data Sources (ODBC) (c:\windows\system32\odbcad32.exe)

 

For more information about ODBC in a 64-bit operating environment, go to:

http://www.64advantage.com/blog/index.asp?ci=1&s=category

 

 

 

 

 

1.3.1.15. Info: Quarantine Clean-up Process in Modus

Product: All

Version & Build: 4.1.361 & up

The cleanup process in Modus helps with maintain the integrity of the quarantine.  This process runs once daily and deletes any file in the MAILBOX\@Quarantine\INBOX folder that does not have a corresponding row in the quarantine database.  Conversely, it will deletes any row in the quarantine database that does not have a corresponding .MSG file in the MAILBOX\@Quarantine\INBOX folder.

Never run the MODUSADM service when the contents of the database and the contents on the disk do not match.

 


 
 
 
1.3.1.16. How-To: Completely Uninstall Your Modus Product

 

Product: All

Version & Build: All

 

This article will explain how to uninstall your Modus product.

1) Stop ALL services:

  • MONITOR
  • SMTPRS
  • SMTPDS
  • POP3
  • IMAP4
  • MAILMS
  • LDAPS
  • MODUSCAN
  • MODUSADM
  • WEBMAILSVR
  • IISADMIN

Note:  Some of the services and/or keys may not exist, depending on your version of Modus.

2) Close the Modus Console

3) Run the uninstallers for:

  • modusMail
  • modusWebMail
  • modusWebAdmin
  • modusStats

4) In the Services manager, ensure that all services are no longer available:

  • modus ...
  • GWGuardian ...
  • VIRCOM WebMailSvr

   If any service still shows up in Service, delete the registry key in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

5) In the Registry, delete the following keys:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Vircom
  • HKEY_CURRENT_USER\Software\Vircom
  • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\modusMail
  • HKEY_LOCAL_MACHINE\Software\Norman Data Defense Systems
  • HKEY_LOCAL_MACHINE\Software\McAfee\Virus

6) In Internet Information Services (IIS) Manager, delete the virtual folders:

  • WebMail
  • modusWebMail
  • WebAdmin
  • modusWebAdmin
  • Delegation
  • Quarantine
  • QuarantineMgr

7) On the hard drive, delete the following folders:

  • C:\Program Files\Vircom\modusMail
  • C:\Program Files\Vircom\webmailclient
  • C:\Program Files\Vircom\webmailsvr
  • C:\Program Files\TMA\...
  • Shortcuts on the desktop

8) Go to the System properties (right-click My Computer) and click on Advanced - Environment Variables:

  • Remove the modusMail path from the PATH variable under System Variables

9) Reboot the computer

 

 

 

1.3.1.17. Info: SNMP OIDs Used by Modus

 

Product: All

Version & Build: 5.1 and up

 

ModusMail and ModusGate supported OIDs 

OID | Counter Name

.1.3.6.1.4.1.22491.1.1.1.1.1.1 = cpuProcessorTime
.1.3.6.1.4.1.22491.1.1.1.1.1.2 = memoryCommitted 
.1.3.6.1.4.1.22491.1.1.1.1.1.3 = memoryCommitLimit 
.1.3.6.1.4.1.22491.1.1.1.2.1.1 = pop3ActiveConnections 
.1.3.6.1.4.1.22491.1.1.1.3.1.1 = imap4ActiveConnections 
.1.3.6.1.4.1.22491.1.1.1.4.1.1 = smtprsActiveConnectionsIn 
.1.3.6.1.4.1.22491.1.1.1.4.1.2 = smtprsClearActiveConnectionsIn
.1.3.6.1.4.1.22491.1.1.1.4.1.3 = smtprsEncryptedActiveConnectionsIn 
.1.3.6.1.4.1.22491.1.1.1.4.1.4 = smtprsInvirusMessagesIn
.1.3.6.1.4.1.22491.1.1.1.4.1.5 = smtprsAverageReceiveTime
.1.3.6.1.4.1.22491.1.1.1.4.1.6 = smtprsRblResponse
.1.3.6.1.4.1.22491.1.1.1.4.1.7 = smtprsRelayAuthTime
.1.3.6.1.4.1.22491.1.1.1.5.1.1 = modusScanInvirusMessagesOut
.1.3.6.1.4.1.22491.1.1.1.5.1.2 = modusScanIncomingMessagesIn
.1.3.6.1.4.1.22491.1.1.1.5.1.3 = modusScanSpamMessagesIn
.1.3.6.1.4.1.22491.1.1.1.5.1.4 = modusScanSpamScanTime
.1.3.6.1.4.1.22491.1.1.1.5.1.5 = modusScanVirusScanTime
.1.3.6.1.4.1.22491.1.1.1.5.1.6 = modusScanSieveDbTime
.1.3.6.1.4.1.22491.1.1.1.6.1.1 = smtpdsActiveConnectionsOut
.1.3.6.1.4.1.22491.1.1.1.6.1.2 = smtpdsClearActiveConnectionsOut
.1.3.6.1.4.1.22491.1.1.1.6.1.3 = smtpdsEncryptedActiveConnectionsOut
.1.3.6.1.4.1.22491.1.1.1.6.1.4 = smtpdsAverageSendTime
.1.3.6.1.4.1.22491.1.1.1.6.1.5 = smtpdsIncomingMessagesOut
.1.3.6.1.4.1.22491.1.1.1.6.1.6 = smtpdsHoldingMessagesIn
.1.3.6.1.4.1.22491.1.1.1.6.1.7 = smtpdsHoldingMessagesOut
.1.3.6.1.4.1.22491.1.1.1.7.1.1 = modusAdmSpamMessagesOut
.1.3.6.1.4.1.22491.1.1.1.7.1.2 = modusAdmProcessingQueue
.1.3.6.1.4.1.22491.1.1.1.7.1.3 = modusAdmMessageDeliveryQueue
.1.3.6.1.4.1.22491.1.1.1.7.1.4 = modusAdmSystemDiskFree
.1.3.6.1.4.1.22491.1.1.1.7.1.5 = modusAdmMailboxDiskFree
.1.3.6.1.4.1.22491.1.1.1.7.1.6 = modusAdmSpoolDiskFree
.1.3.6.1.4.1.22491.1.1.1.7.1.7 = modusAdmQuarantineDiskFree
.1.3.6.1.4.1.22491.1.1.1.7.1.8 = modusAdmNetworkUsage
.1.3.6.1.4.1.22491.1.1.1.7.1.9 = modusAdmDnsResponse
.1.3.6.1.4.1.22491.1.1.1.7.1.10 = modusAdmMailboxAccess
.1.3.6.1.4.1.22491.1.1.1.7.1.11 = modusAdmQuarantineDbTime
.1.3.6.1.4.1.22491.1.1.1.8.1.1 = modusWebMailSvrCurrentSessions
.1.3.6.1.4.1.22491.1.1.1.9.1.1 = modusMonitorDbTime

SNMP counters use the Performance Monitor counters to get the values.

 

1.3.1.18. Info: Testing SMTP Connections

 

Product: All

Version & Build: All

 

We have a console utility (attached) that can be used for testing SMTPRS connections and SMTP authentication.

The utility sends a test message to the localhost server and the results are displayed in a DOS-like screen.  Basically, the utility performs a telnet test but saves you from having to enter the commands manually.  While it is not designed for in-depth troubleshooting, it may help to pinpoint certain connectivity problems. 

To run the program:

Download and extract the attached zip file to your ModusMail or ModusGate server (e.g. the desktop).  Double-click the smail.exe file to display the following window:

 

Test the SMTPRS connection:

Enter a valid email address in the To: box and click OK to send a preset test message to the local Modus server. Only 1 address can be entered here.

You will see the results of the connection attempt in the following screen:

If there are any problems sending the message (e.g. because of security restrictions), an error message, along with the source of the error, will appear onscreen.  There are limitations as to what the program can test and what it will display.

 

Test SMTP Authentication:

Select "Try SMTP AUTH" and enter a valid email address and password in plain text in the boxes provided on the main console screen.  Click OK.  The program will automatically encrypt the username and password in base64 format and you will see the results on the next screen.

For more information about testing and troubleshooting connection problems, please see the following articles:

 

 

1.3.1.19. Info: Upgrading From a Previous Version to Modus 5.x

 

Product: ModusGate & ModusMail

Version & Build: 5.22 to 5.31+

 

This document is not targeted to new customers.

 

 

Introduction

This document is intended for existing Vircom customers who are currently running an older version of  ModusGate. You should read this document thoroughly before upgrading.  If you have any questions or feel something is missing from this document, feel free to contact us by e-mail at support@vircom.com.

 

Changes to the installation process:

ModusGate 5.31 come with a new web interface.  The new interface will not overwrite your existing WebQuarantine programs. This will allow you to continue using the 'old' site until you have had time to test and/or customize the new one.

 

ModusGate Web Quarantine information:

There will be a new folder created called WebQuarantine locate under C:\Program Files(x86)\Vircom\Web. This  folder will contain the new websites attributes for the new web quarantine pages. The virtual directory will still exist in IIS.

 

IMPORTANT:

If you plan to use the monitoring feature, it is preferable to use a Microsoft SQL database instead of the native Access format. 

 

Whether to use Microsoft Access or Microsoft SQL depends on your volume of traffic.  A good rule of thumb would be to use your quarantine database as your guide: if you use SQL for the quarantine, then you should use it for the monitoring stats as well.

 


 

Upgrading ModusGate

 

Upgrading requires a certain number of precautions.  The most important is doing a backup before upgrading:

 

a) Make sure you have access to your old Modus installation package in case you need to rollback.  If you do not h