1. 2018 Official Holidays & Support Schedule
 
 

New Years Day

Monday January 1

Support will be closed. Emergency support calls only.
 
 
 
Good Friday
Friday
March 30
Reduced support staff.  Office is open from 8:00AM to 5:00PM EDT.
 
 
 
Easter Monday
Monday
April 2
Reduced support staff.  Office is open from 8:00AM to 5:00PM EDT.
 
 
 
Victoria Day
(Canada)
Monday
May 21
Reduced support staff.  Office is open from 8:00AM to 5:00PM EDT.
 
 
 
Memorial Day
(USA)
Monday
May 28
Support will be closed. Emergency support calls only
 
 
 
St. Jean Baptiste
(QC only)
Monday
June 25
Reduced support staff.  Office is open from 8:00AM to 5:00PM EDT.
 
 
 
Canada Day
Monday
July 1
Reduced support staff.  Office is open from 8:00AM to 5:00PM EDT.
 
 
 
Independence Day
(USA)
Wednesday
July 4
Support will be closed. Emergency support calls only.
 
 
 
Labor Day
(Canada & USA)
Monday
September 3
Support will be closed. Emergency support calls only
 
 
 
Thanksgiving
(Canada)
Columbus Day
(USA)
Monday
October 8
Support will be closed. Emergency support calls only.
 
 


Thanksgiving
(USA)
Thursday
November 22
Support will be closed. Emergency support calls only.
 
 
 
Black Friday

(USA) 

Friday November 23
Support will be closed. Emergency support calls only.





Christmas

Monday \ Tuesday
December 25 -26
Support will be closed. Emergency support calls only.
2. IMPORTANT: End of Life of SHA1 on Windows Server 2003

EOL of SHA1 Encryption and Windows 2003

NOTE: If you’re running modus on Windows 2008 or Windows 2012, this does not apply to you.              

 

         The SHA family of hashing algorithms was developed by the National Institute of Standards and Technology (NIST) and is used by the majority of SSL certificates. Presently, the most common of these hashing algorithms is SHA1 which was adopted by certificate authorities as the successor of MD5 algorithm because it signified a major advancement in cryptographic security. Over the years computing power has strengthened and SHA1 level of encryption has been considered as not being sufficiently secure. As a result there has been a major advancement to transition from SHA1 to the stronger SHA2 algorithm. The recent announcement from Microsoft and Google about deprecating support for SHA1 in browsers has accelerated this transition. There are, however, a few systems that continue to operate using SHA1. This includes most servers running Windows 2003 (not R2). Users who continue to operate using SHA1-based security certificates can expect to receive security warnings from web browsers by the end of this month (October). 

As of January 1st 2017, support for SHA1 will completely come to an end and it is highly likely that updates will be sent out to all major platforms to start erroring out on SHA1 requests.

“Microsoft’s SHA-1 deprecation plan differs in the activation time and browser behavior. Microsoft’s security advisory on “Deprecation of SHA-1 Hashing Algorithm for Microsoft Root Certificate Program” informed us that Windows will cease accepting SHA-1 SSL certificates on January 1, 2017. To continue to work with Microsoft platforms, all SHA-1 SSL certificates issued before or after this announcement must be replaced with a SHA-2 equivalent by January 1, 2017. The SHA-1 deprecation plans also impact SHA-1 intermediate certificates; SHA-2 end-entity certificates must be chained to SHA-2 intermediate certificates to avoid the adverse browser behaviors described above. SHA-1 root certificates are not impacted.” -- From Symantec’s website.

The problem with this is that an unpatched Vanilla Windows 2003 server does not support SHA2 natively. Even a patched Windows 2003 does not support SHA1. To be able to support SHA2 you need to be running Windows 2003 R2 SP2 fully patched.

“Windows users do not need to do anything in response to this new technical requirement – Windows XP Service Pack 3 supports SHA2 SSL certificates, and Windows Server 2003 Service Pack 2 or later add SHA2 functionality to SSL certificate by application of hotfixes (KB968730 and KB938397).”

In other words, if you’re running Windows 2003R2 SP2 or better with the related hotfixes, you should be fine. However you should verify your current certificates to confirm if they are encoded using SHA1 versus SHA2.

If you’re not patched, you really should start updating your Windows 2003R2 with the latest service packs & security fixes. According to GlobalSign, to support SHA2 (SHA 256) with Windows 2003, you need Windows 2003 R2 SP2 + MS13-095 (KB2868626).

https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility

KB2868626 should already be installed if your server is going through the normal windows updates process.

 


https://support.microsoft.com/en-us/kb/2868626

 

1 - What does all of this mean as a Vircom customer?  

For modus users running Windows 2003 "Vanilla":

Any version of modusGate/modusMail on Windows 2003 as of January 01, 2017 will no longer receive Anti-Virus and Anti-Apam definitions. Which means that your email servers and infrastructure will be exposed to malware threats.

It is strongly advised that you migrate off of Windows 2003 as soon as possible. The operating system itself is not supported by Microsoft at this point and Vircom has discontinued support for Windows 2003.

 

2 - Windows 2003 R2 SP2 (fully patched)

Clients using Windows 2003 R2 SP2 with all the updates will not be affected by these changes. Our testing indicates that modus has no issues in getting updates from SHA2-based update servers. However, upgrading to the latest version of modusGate/modusMail (6.2 and higher) will no longer be possible on a Windows 2003 Server

Windows 2003 is still EOL by Microsoft and we strongly recommned that you migrate to Windows server 2008 or 2012.

 

3 - Need help to migrate modusGate/modusMail?

Vircom can assist you with your migration. We have a vast amount of experience with this and if you do not wish to move to a new server, we can also move you to our cloud spam filtering service as an alternative (for those running modusGate).

 

Please contact our Professional Services team to schedule a time and cost for your migration. We've performed hundreds of migrations professionally so that the process is simple and painless for you.

Please do not hesitate to contact us if you have any questions at +1.888.484.7266.

 

 

 

3. IMPORTANT: Supported Operating Systems
Supported Operating Systems
 

Dear Clients,

As you might know, Microsoft announced an End of Life for Windows 2003 as of July 1, 2015.
 
This action impacts Vircom products too, forcing us to discontinue development and fixes for older modus versions that ran on Windows 2003. As a result, our development is now limited to both Windows Server 2008, and 2012 and our two most recent modus releases: versions 6.0 and 6.1.
 
Specifically, for modusMail and modusGate 6.1:
  • Windows® 2003 Server is no longer supported
  • The system requires .NET 3.5 SP1 prior to upgrading modus to 5.0
  • The Windows Server version must be 2008 or above to support .NET 3.5
 If you are currently using Windows 2003, we kindly ask that you update your Operating System to either 2008 or 2012. And, to ensure that your Vircom products continue to run optimally, we also ask that you update your modus version to either 6.0 or 6.1 (with a valid support plan).

Should you need help or advice regarding your modus upgrade, please do not hesitate to contact our Support Team at
support@vircom.com.
4. PLEASE READ: Our Update Server IPs Have Changed
Vircom has changed IP ranges for one of its collocations, and the old site will be shut down on Wednesday, October 28, 2009.
 
We can see that some modus servers are still trying to contact the old site even though the DNS entries have been updated to point to the new IPs. To ensure that your server is fetching updates from the new site, please do the following:

 
1. Manually stop and restart both the moduscan and modusadm services to force a connection to the new site.
2. Check your firewall and/or proxy server to ensure that you can connect to the new IP ranges:
  • Old: 64.18.73.0 /24
  • NEW: 207.115.110.0 /24
     
  • Old: 64.254.235.128 /28
  • NEW: 216.46.27.192/26
5. Support
5.1. Customer Support Hours and Statutory Holidays

Support Hours:

4h00AM to 6h00PM Eastern Time (north America) Monday through Friday


Phone Support: 514-845-8474

Begins at 4:00AM and ends at 6:00PM, Monday through Friday. If your call is directed to voice mail, please leave a detailed message, including your Customer ID, and we will answer your request according to the priority level of your service package.  If you have an emergency situation, we recommend that you contact us by phone.

If you call outside of our business hours, you will be able to leave a message and you will receive a call back within 30 minutes.

After-hour calls are reserved for High or Critical priority issues and Trial customers.


Email Support: support@vircom.com

Emails are answered within the business day and according to the severity of the issue. Please note that Vircom offices are closed during statutory holidays.

In case of emergency, it is preferable to call our support line. You can email emergency@vircom.com and it will trigger an alert for our 24/7 system.

If all else fails, you can email escalations@vircom.com and a manager will find the resources to assist you. 

 

Statutory Holidays:

During most holidays, Vircom maintains a skeleton crew and only processes critical system down issues on those days. The only exceptions are Christmas and New Year's day where Vircom offices are actually closed on those days. Vircom is located in Quebec, Canada so we observe local holidays. Since a large percentage of our clients are from the United States, we also observe the major American holidays ie. Independance Day.

Vircom Holiday Observances: http://kb.vircom.com/default.asp?SID=&Lang=1&id=1659



 



 



 

5.2. Customer Support: Our Values

Statement of Values – Vircom Customer Service

 

Respect

We firmly believe in mutual respect and in treating others with the same honesty, fairness and courtesy that we would like in return.   We will always speak and correspond with our customers in a respectful and courteous manner.

 

Trust

There is so much confidential information at risk that it is imperative you know who you are working with. We will always be honest with you and never knowingly misrepresent ourselves or any solution. Confidential records and proprietary information will always be kept in the strictest of confidence and, at no time, will any of your company's information, including contact names or e-mail addresses, be shared with any third-party vendors.

 

Professionalism

We pride ourselves on providing respectful, courteous and helpful responses to our customers.  We know that how we conduct ourselves also reflects on our customers' businesses, which we take seriously.   Furthermore, we work efficiently and skillfully, assuring that critical problems are always our top priority and resolved in a timely manner.

 

Effectiveness

We start our day prepared and on time, establishing priorities and goals for the day.  We value our Customers' business and take our job seriously and with care.

 

Focus

We stay focused on our responsibilities of serving Customers and limit external distractions to a minimum.  We use technology to increase collaboration between Vircom employees, not for distraction.

 

 

5.3. Required Information When Contacting Customer Support

 

When calling/emailing Vircom's customer support, please be prepared to provide our service technician with the following information:

 

  • Your Customer ID.  This number was given to you upon purchase of your products and confirmed with an activated code, sent to you by email. 
  • Your name, the company name, email address and telephone number
  • Product name, version and build number
  • Priority of your request (Critical, High, Normal or Low)
  • Detailed description of the problem including any test results
  • Information on how to reproduce the problem and the error logs

 

Why your Customer ID is important

 

Important:  The software version that you are currently running can be found by clicking on Help > About.  This information allows us to properly assess technical issues and recommend the most efficient solution to resolve them.  Providing this information decreases the time it takes to resolve problems because it allows the technician to research "known issues" that may be fixed with a patch or upgrade.


When a problem is reported to Vircom's support, the service technician enters the information into a tracking system and a Ticket Number and description of the request is immediately relayed to the Customer.

 

Clients should always refer to the ticket number for updates, follow-ups or escalations on the reported issue.  It is recommended that you reply to this email to update us on your situation.

 

 

5.3.1. Why Your Customer ID is Important

Your Customer ID is very important when calling or emailing Vircom's Technical Support.  Many of us here can recognize customers by their voice, name, and/or company name.  However, Vircom's requirement for all support personnel is that they must log the customer's ID for every call or email.  In fact, a ticket cannot be created without the customer's ID number.  Even if the technician knows you or your company, it is unlikely that he/she will have memorized your ID.  For this reason, you should not be surprised when the support person, who you might know very well, asks for your number.

Other than for ticket creation, having your ID ready or including it in your email to Support saves time.  When a customer does not have his/her ID ready, the technician must perform search(es) against our database to find a match with your name, company, etc.   Although this process may only add up two minutes to the support call or the email ticket generation, it can quickly add up.  For example, if, in the morning, we receive 10 emails and none provide the ID number, then the person creating the tickets must spend an additional 20 minutes (10x2min) searching for the ID.  On some days, especially when we are busy, those 20 minutes saved can make a big difference for all our customers (one more reply to an email, one more call back, one more KB article, less time waiting in the phone queue, etc.).

Thank you for your cooperation,

Vircom Customer Support 

 

5.4. Support Response Times & Coverage

 

Contacting Vircom

 

      Hours: 4h00 to 18h00 Eastern Time (North America). Emergency support available after hours.

      Phone: 514-854-8474 (direct) or 1-888-484-7266 and press "1" for support.

      Email: support@vircom.com

      Afterhours Emergencies: emergency@vircom.com or call our normal support line and leave a message, you will be called back within 30 minutes.

      Escalations: escalations@vircom.com.

 

Vircom will use best commercial efforts to provide remote and telephone software support within the time frames defined below.

P1 - Critical Issue:

A critical issue is defined as having a major functionality severely or critically impaired.

  • No mail flow.
  • No access to the user interface.
  • No spam getting caught at all.
  • Compromised accounts causing mail queuing.
Usually a critical issues affect every person in the organization.

Expected Response Times:

  • First reaction within 30 minutes.
  • Resolution expectation within 4 hours or until a suitable workaround is provided.

P2 - High Priority Issue:

A high issue is defined as having an important functionality impaired but not completely down.

  • Quarantine digests/reports not getting generated.
  • Unusually high number of false-positives or false-negatives.
  • Successful phishing attack.
Usually a high issue affects most of the organization but mail flow is preserved where spam and viruses are being quarantined.

Expected Response Times:

  • First reaction within 1 business hour (first call back or email).
  • Resolution expectation within 24 hours or until a suitable workaround is provided.
 

P3 - Normal Priority Issue:

A normal issue is defined as an issue that is not impacting any major or important functionality and not impacting a large number of users.

  • Single user not receiving certain emails.
  • A user not receiving a quarantine digest.
  • Single user is getting more spam than others.
  • Cosmetic issues with the software
  • A usage question.
Usually a normal issue tends to apply to a single user or a small subset of users within the organization.

Expected Response Times:

  • First reaction within 4 business hours.
  • Resolution expectation within 48 - 72 hours if it is an operational/usage question or will be fixed in next operational release. 

 

Please not that if a technician reaches back to you within the first reaction time expectation but you are not available to continue with the troubleshooting, these response times are null & void (in other words, if we get back to you and your are not there or available, obviously we will not be able to respect these response times.


Support Coverage:

Our technical support covers exclusively our products and it's direct dependencies.

 

  • modusGate
  • modusMail
  • modusCloud
  • modusHosted

 

 

Dependencies: modusGate and modusMail require SQL Express or the full MS-SQL, we will support these as well.

If you are having network issues, problems with DNS, firewalls, operating systems or other ancilliary systems, our support coverage does not cover those items. We will often provide some advice and assist with some diagnostic efforts on how to fix these issues - in fact, we often go beyond the purview of our support services and assist clients with third party systems, but please understand that this is not part of the normal support coverage and is often and the discretion and skill level of the technician serving you. If you want us to fix a problem with a subsystem that is not directly related to modus, this becomes a professional service and is billable as a consultant fee and is subject to technician availability.

Technical support is meant to cover operational problems or issues with modus only. If you require Vircom support to do any activity that is schedulable in time (perform an upgrade of a server, a server migration from an old physical or virtual server to a new server) these are considered professional services and are thus billable as consultant fees.

 


 

5.5. My Vircom Website

 

Accessing the secure Vircom website can be accomplished in two ways: 

1) By using your product license key

2) By using a log-in ID and password 

To access the MyVircom site, go to www.vircom.com and click on Services and then Customer Portal on the Vircom home page.  Enter your user name and password or  license key and click on the orange arrow:

 

 


 


 

Log-in IDs: 

You may have up to 4 log-in IDs (contacts) but you must use the log-in ID/Password combination (method # 2 above) in order to change or add the contacts.  For this function to work, you must: 

1) Be listed as the Primary Contact for your company

2) Connect using the log-in / Password boxes - NOT the license key box (see screen shot above)

If you do no't follow both of the methods listed above, an error will occur.  If you are not the Primary Contact, you must email us at support@vircom.com with your Client ID and/or VCI number (Vircom Customer ID) and we will update our information.  Once the update is complete, you may login to create any additional log-ins.

Follow the procedure outlined below to add new log-in IDs:

Select Get / Change Log-in from the tool bar:

 

 

 

 

You can add up to 4 additional users to your private MyVircom section.  To create a new log-in, click on Modify to display blank surname: 

 

 

Complete the missing information:

 

 

 

After completing the registration, you will be able to log into MyVircom using a personalized log-in and password. 

Each log-in ID will automatically be included in Vircom’s master mailing list.  This mailing list is used to communicate important information to all customers such as the release of new versions or patches and general information about the support desk.  Email notification will have the following tag in the subject line: [ModusNews] or [VircomRadiusNews].

 


 

 

5.6. Full Support for Trial Customers

INSTALLATION SUPPORT

Vircom will provide assistance with installation if you already have the software pre-requisites for modusGate or modusMail.

Virtual or Physical Appliance Requirements:

  • Windows Server 2003, 2003R2, 2008, 2008R2, 2012R2 (32-bit and 64-bit) or Windows Small Business Server (SBS) 2003 x86, 2008 x64 and 2011 x64 with the following packages installed: 
  • IIS & ASP.NET,  .NET framework 3.5 and .NET framework 4.0
  • All Windows patches must be done prior to our intervention.
  • For most installations under 1000 mailboxes, you will need a dual core system or VM, with at least 2 gigs of RAM and 60 gigs of hard drive space on the "c:\" drive. 


Vircom will help you setup one or two domains or domain routes as well. 

Free assistance will be provided within reason.  If your installation needs go beyond this, please contact our sales team and we will be happy to provide you with a professional services quote.


POST INSTALLATION SUPPORT:
 

Customer has the equivalent of Platinum support for the first 30 days of the trial, phone & Email.

 
CONTACTING SUPPORT:


Contact customer support, by phone, at 514-845-8474 or, by email, at support@vircom.com.

 

  

5.7. Mailing Lists and Client Community

Vircom Mailing Lists 

Your daily source of Vircom info! Vircom hosts several mailing lists that allow customers to help one another with Vircom's product line.  Vircom also uses these lists to announce new releases, patches and updates, including any important alerts that we may need to broadcast to our customer base.  Finally, we use these lists as a way to get feedback about our software.  This helps us when we need to set priorities in our development efforts.


Discussion / Self-Help Lists:
These are interactive lists used by our customers:

Modus@vircom.com
Discussion list for Vircom's Modus-powered solutions.  This is a high-traffic list with peaks of 50+ emails per day.  You can create a rule in your mail client to segregate these messages if you do not wish to be overwhelmed: they have the word [MODUS] in the subject line.  You can subscribe to this list by clicking on the following link:  mailto:modus-request@vircom.com?subject=subscribe.


Vircom's policy regarding the lists:

Common net-etiquette applies to our lists.  Vircom reserves the right to remove any person from the list who behaves in an abusive manner.  Vircom occassionally participates directly in the discussion groups.  However, if you have support issues that you can't resolve by talking to people on our lists, you should address your questions directly to support@vircom.com.
5.8. How-to: Submit Spam to Vircom
 

In our continuing effort to make Modus the most effective email security solution, we ask that you send spam samples to the Spam Team for analysis.

 

 

False-Negatives:

 

In the event that Modus is not blocking spam, please send your spam samples to spamtrap4@vircom.com:

 

  • Windows:  create a new email and drag the spam into it (the spam message will appear as an attachment)
  • GroupWise:  highlight the messages to be reported (multiple messages can be selected), right-click and select "Forward as Attachment", fill in the To: field and click on Send

 

 

 

False-Positives:


If you have reports of false-positives, please send copies of these messages to falsepositives@vircom.com or use the false-positive submittal system in the Quarantine of the Modus Console:

  • From the Console, click on Quarantine
  • Select the false-positive
  • Click on the false-positive button
  • Follow the instructions on screen

 

 

Please do not automatically forward spam to the spamtrap4@vircom.com address.  This includes creating a catchall for unknown recipient addresses.  The result of automatic forwarding is that our Spam Buster Team receives too many legitimate messages and false-positives.

 

We also ask that you do not use this address for support questions.  Support questions sent to the spam trap address will not be acknowledged.

 

5.9. Submitting Spam and False Positives

 

Spam and False-Positives Submitted by Clients


The SpamBuster team would like to thank all of you who send data to
falsepostives@vircom.com and spamtrap4@vircom.comYour contributions are appreciated and we would not be able to tweak the spam engine to keep its performance sharp and up-to-date without your constant feed of spam and false-positives.  We would also like to make some suggestions regarding the information sent to these mailboxes.

Automatic Feeds

Obsolete Mailboxes:

Many of you have started feeding the traffic from inactive or obsolete mailboxes to our spamtrap4 mailbox without pre-filtering for content.  Although this may seem like a good idea, we've found that many of these boxes still receive legitimate mail from contacts or "good" mailing lists.  In some cases, the lists the person used to belong to may look fairly spammish, so it is becoming difficult for us to be able to separate the spam from the non-spam coming from these mailboxes.  Furthermore, messages that are sent to spamtrap4 should only be spam.  Otherwise we have to spend valuble time sorting through the messages which slows down the update process on our end.  Unfortunately, these obsolete boxes do not help us that much.
 

Catchall mailboxes:

Some of you have redirected your catchall mailboxes for certain domains directly to our spamtrap4 address.  This shouldn't be done because we get a lot of legitimate mail in this mailbox which hinders our efforts.    We already have several "ancient" domains (12 years old or more in our case) set up as internal spamtraps for detecting spam attacks.  They no longer receive any legitimate mail so they have become very valuable.  Catchall redirections should not be used with spamtrap4@vircom.com.
 

 
Ideally you should send us messages that were submitted by your users in the proper way, according to the instructions in "
I have spam that I want to send you."  A
, a new message must be created with the original spam message included as an attachment. This has the benefit of conserving the original message without ruining the contents or the headers.  This works well with most mail clients except for Microsoft Outlook which tears apart messages as soon as they come in via POP or IMAP.  Outlook Express, however, works fine.
 
Confirmed spam messages should be sent to spamtrap4@vircom.com.
 
Please, do NOT submit legitimate messages, false-positives or Quarantine Reports to 
spamtrap4@vircom.com.

 

5.10. How-to: Report a Virus to Vircom
 

If you have the original MSG (message) file in the user's inbox (modusMail™), zip the MSG file and call it infected.zip with vircom as the password.

If you do not have the original MSG (message) file but the end-user has it in his/her mail client:

  • Save the infect message as a txt file (save in cleartext)
  • Note that you must save the entire email – only saving the attachment is not sufficient
  • Zip the txt file to a zip file called infected.zip with the password vircom
  • Send the infected.zip file to virustrap@vircom.com for analysis.

 

In the email message, include the product you are using and the build number (click on Help > About in the modus™ Console.

 

 

5.11. How to submit a feature request

How-to: Submit a Feature Request:

To submit an enhancement, feature or change request, send an email to support@vircom.com.  Please include the following information:

  • The product in question (e.g. ModusMail, Radius, etc.) 
  • Your VCI Number and Contact Information
  • Desired behavior
  • Technical justification
  • Business justification (if relevant)
  • Any additional comments

Please note that Vircom does not commit itself to implementing all requests.  The decision to implement (or not) a feature is based on a variety of factors, including the difficulty of implementing it, the value it adds to the product and how it fits in with our product strategy.   Keep in mind that Vircom’s decision to reject a feature request should not be taken as a rejection of the underlying idea.

5.12. What happens when my trial / temporary key expires?

Product: ModusMail & ModusGate


If the license key you are using is a trial key (i.e. temporary), the product will stop working -  all services will stop and email will be rejected. However, if you have a permanent key and the support plan expires, the auto-update feature for spam and virus definitions will no longer receive updates.  The services will continue to function but there will be no new updates.



 

 

5.13. Support for Microsoft Windows 2008/2003 Web Edition

Support for Microsoft Windows 2008/2003 Web Edition?


Product: modusMail & modusGate
Version & Build: all

Microsoft Windows Web Edition and Vircom Products

This document is important for customers considering using Microsoft Windows 2008/2003 Web Edition with Vircom products.


Question:  Does Vircom support its products on Windows Web Edition Server?

Answer:  Vircom only supports the installation of the modus web components on a Windows Web Edition server. All other products (modusMail Server, modusGate Server, VOP Radius, and VOPCOM) are not supported.

With respect to modusMail / Gate, the only supported implementation scenario is where the web components are installed on the Web Edition and the modus server is installed on another (supported) Windows server version.

Microsoft states: “
Licensing terms for Web Server also further clarifies that the server software may only be used for front-end Web serving Internet-accessible Web pages, Web sites, Web applications, Web services, and POP3 mail serving*" (* i.e., webmail).


Source:
http://www.microsoft.com/windowsserver2008/en/us/licensing-web-server.aspx 


NOTE: As long as Microsoft prohibits running non-webserving applications on its 2008/2003 Web Edition, Vircom, in turn, must insist that deploying modusMail or modusGate Server on the Web Edition is not supported.  Because of Microsoft license restrictions, Vircom cannot legally test modus server on the 2003/2008 Web Edition.


6. modusGate for Microsoft Azure
6.1. Deploying modusGate on Microsoft Azure MarketPlace

Deploying modusGate on Microsoft Azure MarketPlace

The following article describes how you can access modusGate on the Azure MarketPlace and deploy a VM in Azure with modusGate installed.

Note: In order to deploy modusGate on Microsoft Azure you must have an Azure Subscription account or you can sign up with your Microsoft Account here at sign-up for a free trial.

 

      1. Access your Azure portal and search for modusGate on the MarketPlace.

      2. Select modusGate email security from the list and click the "Create" button.

      3. Enter details of your VM in the "Create Virtual machine" panel.

                  a. Basics – Configure basic settings.

                  b.  Size - Choose the virtual machine size. Recommended VM for modusGate is A2 Standard, A3 Standard and A6 Standard. Visit this page for VM size details.

                  c.  Settings - These are optional feature settings. ie. Such as configuring a Static Public IP.

                  d. Summary details panel of the VM being deployed.

                  e. Buy - Purchase the VM offer. Vircom pricing is separate from MS Azure and is a BYOL (Bring Your Own License), please see Azure Pricing for all details.

                  f. Allow the VM approx. 5 minutes to be provisioned and once ready, log into the VM via the RDP client.

 

Start using modusGate on Azure with a free 30 day-trial license. See the following KB article on how to obtain your free 30 day-trial license.

 

Contact a Vircom representative for all modusGate pricing inquires. Contact us at 1-888-484-7266.

6.2. Get started with modusGate on Azure

Getting started with modusGate on Azure

This article describes how you can get access to your modusGate or sign up for your 30-day free trial license for Azure BYOL (Bring Your Own License) .

Note: If you’ve not deployed modusGate from the Azure MarketPlace go to this KB page: deploying modusGate on Azure.


      1.  Log into your MS Azure Portal.

      2.  Select the VM from the MS Azure Dashboard.

      3.  Simply select the “Connect” button from your Azure Portal.

 

      4.  Login to your VM via the RDP client.

       5.  Once logged into the VM you wil be prompted with a "modusGate for Azure" onboarding application.

 

      6.  There are two options that can be used to start using modusGate.

              1. Select “I want to start a free trial, please send me a key!”. Complete a simple sign-up form and we will email you a free 30-day trial license. 

                 2. If you already have a modusGate ASV-AB key, then you can simply copy and paste it in the text box.

      7.  Copy and paste a Key in the text filed and seledt the "GO" button and modusGate will be initialized and ready to be used.

 

If you have any issues, please contact a Customer Support representative at 1-888-484-7266.

Next Step: How to configure a Route in modusGate.

6.2.1. Setting up a Route with the Route Wizard

Setting up a Route with Route Wizard

 

This article describes how to configure modusGate with your mail server.

 

NOTE: You must create a route for each domain for which modusGate is to filter email.

 

 

      1.  Launch the modusGate console. The Console will be launched and you will be prompted with the Routing Wizard.

 

      2.  Select the "Next" button and enter your Mail Domain Name, e.g. xyz.com. Email sent to this address will be filtered by modusGate.

 

      3.  Select the appropriate Mail server type from the dropdown list. If your server type is not listed, select one of the following: SMTP, SMTP_VRFY.

 

Please note the following server Types:

  • The SMTP option cannot validate mail recipients, therefore invalid addresses will be created in the user list and count against your user license. In addition, if alias email addresses are used, they will be added to the user list and total user count. 
  • SMTP_VRFY is supported by most mail servers, but must only be used if the mail server is protected by a firewall with no direct public access. Without a firewall, the list of valid user accounts can be easily obtained over the Internet. Alias email addresses are supported by SMTP_VRFY; they will not be counted against the user license.

     4.  Enter the Mail server name or IP.

     5.  The SMTP Port number automatically displays 25; change this only if you use a different port number.

      6.  If you had selected Exchange as a mail server type, click "Next" and enter your Active Directory/LDAP server information.

Note: The Exchange option authenticates with your LDAP/AD server. In order for the VM on Azure to have access you must create an inbound firewall rule to allow the public IP address of your VM to access port 389/3268 (LDAP). How to setup a Static IP in Azure.

      7.  Enter the Server name or IP address for your Active Directory or LDAP servers.

      8.  Verify the Port Numbers:

  • If using Exchange 2007-2016, port 3268 is automatically configured for the Global Catalog: this provides access to the entire list of users’ mailboxes. Selecting Use TLS will auto-reset the port to 3269.
  • You may optionally enter a custom port. 

      9.  Enter the AD root domain name. This is the root or internal domain name configured on your Active Directory/LDAP server, e.g. domain.local.

    10.  User DN and Password: enter the email address and password of the Administrator.

Note: Optionally you can create a mgate user in AD that has only read access. The email address format is supported by both Active Directory and LDAP. 

    11.  Enter a valid email address in the Enter Email to Test field and click Test Route.

  • The system will attempt to connect to your mail server and send a message to your address.
  • You will receive feedback if there are any errors.
  • Check your Inbox to confirm the message was received.

    12.  Click Next to view the summary table.

  • Click Add to enter other domains or mail servers, if necessary.
  • To edit or change any information, use the Console's Connection settings.
  • Click Finish to close the wizard.

 

If you have any issues, please contact a Customer Support representative at 1-888-484-7266. 

Next Step: Test your mail flow.             

6.2.2. Test your mail flow

Test your mail flow

 

After creating a route, you can optionally run this automated mail flow test to ensure the system is working properly.

 

Note: You must have configured a Route before testing the mail flow.

 

      1.  Ensure the modusGate VM is running and you’ve logged in, open the modusGate Administration Console to System > Services to verify that all services are running.

  • The most important services required for basic functionality are: SMTPRS, SMTPDS, MODUSADM and MODUSCAN. 

      2.  Locate the Email Flow Diagnostic Tool on the desktop and click to open the program.

      3.  Verify that the SMTP server displays the modusGate server name, and enter your email address to perform the test.

      4.  Select to test a spam message, a legitimate message or both, and click Send.

  • Check your Inbox in Outlook to verify that you received the legitimate test email.
  • On the modusGate console, open the Quarantine tab and verify that the spam test message appears in the list (if the console Quarantine screen was already open, you might need to click the Refresh button to see the message). 

      5.  The mail flow test can be re-run at any time.

 
 
If you have any issues, please a Contact Support representative at 1-888-484-7266. 
 
 
6.2.3. Setting up a Static IP address

Setting up a Static IP address

 

Note: By default VM’s on Azure are configured with a dynamic IP. The IP of the VM will only change every time the VM is Stopped and then Started again. If you Restart the VM in Azure the IP will not change.

It’s important to note that it is highly recommended that the VM be configured with a Static IP when modusGate is deployed in a production environment.

 

      1.  Access the VM running modusGate from your Azure Portal Dashboard.

      2.  In the Settings panel select “Network interfaces” and then select the configured “Network Interface” that was created at deployment time.

      3.  Select the “IP Addresses” option from the Settings panel. 

 

      4.  From the IP Addresses panel select the option “IP Address” under the Public IP Address Settings section.

      5.  Select "Create New".

 

      6.  Give the new IP address a new Name and select the Assignment to "Static".

      7.  Select the OK button and your VM with modusGate on Azure will be assigned a Static IP.

Note: With every Azure Subscription you are entitled to 5 static IP’s. Please refer to the following link for prices of IP’s.

 

If you have any issues, please contact a Customer Support representative at 1-888-484-7266. 

Next Steps: Changing your MX Records.      

 

6.2.4. Changing your MX Records

Changing your MX records

 

Once your connection(s) are tested and working, the next step is to change your DNS records.

  • On the DNS Server, modify the MX (Mail Exchange) record so that your mail domain points to the modusGate server instead of the Exchange.
  • Create an A or Host record that maps the new modusGate MX to the Gater server's IP address.
  • Since the new MX records can take anywhere from 12 to 48 hours to propagate, only remove teh mail server's MX after modusGate's MX has been propagated. Do this to hide your mail server from public view: when spmmers see multipel MX's for the same domain, they often bypass the primary (modusGate's) and target the secondary (the mail server).

If you wish to check whether your MX record change has been propagated try using our Email Security Grader tool at www.emailsecuritygrader.com and enter your domain name.

 
7. modusCloud
7.1. Archive
7.1.1. How to Configure Archive with IMAP on O365

Product: ModusCloud

 

Situation:

With modusCloud the ability to enabled archive for inbound and outbound emails is now possible. The process requires the archive feature be enabled followed by creating a connector on modusCloud, and then finalizing the setup with O365 send connector.

The steps below allows one to follow step-by-step sequence. 

Note: It is recommended that the NDR undeliverable mailbox is not a shared mailbox.

Enable Archiving on modusCloud:

  • By default the feature is not enabled and must be activated for each client.

          1- Log into the modusCloud website US or EU

          2- Click the Features tab.

          3- Enable "Enable Email Archive" and click Save.

          4- This will activate a new tab in modusCloud ARCHIVE as shown below.


 

Create an IMAP Connector in modusCloud Archive:

  • A Connector is required so modusCloud is to associate to the tenant on O365 for each client.

          1- In the Archive tab hover over the GEAR icon and click Connections.

          2- Click the plus symbol + on the top right corner.

          3- Enter a Description for the connector.

           4- Select the connection type of IMAP.

           5- Enter the Server Name to which modusCloud should connect to.

           6- Enter the Username of the account that should be used to connect to the archive mailbox. 

           7- Enter the Password of the account that should be used to connect to the archive mailbox.  

          8- Enter the Port for the connection (Port 993 recommended) and click Save.

  

 

Create a Connector in O365 for modusCloud:

  • A dedicated outbound connector must be created so that all archive traffic is sent directly to the modusCloud Archive environment, instead of getting routed through the modusCloud gateway.

          1- Sign-in to the Office 365 Administration Portal.

          2- Click Admin (in the toolbar) and choose Exchange (in the left pane).

          3- Click Mail Flow.

           4- Click the Connectors tab.

           5- Add an outbound connector by clicking the plus sign "+".                   

           6- Select Office 365 from the From drop-down.

           7- Select Partner organization from the To drop-down and click Next.

           8- Enter a descriptive Name for the connector.

           9- Then enable the connector by checking Turn it on. and click Next.

         10- In the new screen that opens, select Only when email messages are sent to these domains.

         11- Then click "+" sign and enter "*.earchive.cloud".

         12- Click OK to return to the connectors screen and click Next.

         13- Select Use the MX record associated with the partner's domain and Click Next.

         14- Leave the default settings for TLS and click Next.

         15- A summary of the configuration is displayed if all look correct click Next.

         16- Enter an email address in order to validate the connector based on your region. 

               - US: verification@us.earchive.cloud 

               - EU: verification@eu.earchive.cloud

         17- When prompted to validate the connection, click Validate.

         18- Validation results are shown. To dismiss the results click Close.

 

Configure O365 to Remote-Archive Message Data to modusCloud:

          1- Sign-in to the Office 365 Administration Portal.

          2- Click Admin (in the toolbar) and choose Exchange (in the left pane).

          3- In the Exchange Admin Center, click Compliance Management.

           4- Click the Journal Rule tab.

           5- In the customer admin address area, click Select Address, click Browse, and select an admin email account.                   

               - This account will receive notification of non-deliverable archive reports. It is the same email address configured in modusCloud archive connection archive1@domain.com.

           6- Add a new journal rule by clicking the plus sign "+".

           7- Enter a descriptive Name for the rule.

           8- From the If the message is sent to or received from... list, choose Apply to all messages.

           9- From the Journal the following messages... list, choose All messages and click Save.

         10- When prompted to confirm that you want the rule to apply to all messages click Yes.

 


7.1.2. How to Configure Archive with O365

Product: ModusCloud

 

Situation:

With modusCloud the ability to enabled archive for inbound and outbound emails is now possible. The process requires the archive feature be enabled followed by creating a connector on modusCloud, and then finalizing the setup with O365 send connector.

The steps below allows one to follow step-by-step sequence. 

Note: It is recommended that the NDR undeliverable mailbox is not a shared mailbox.

Enable Archiving on modusCloud:

  • By default the feature is not enabled and must be activated for each client.

          1- Log into the modusCloud website US or EU

          2- Click the Features tab.

          3- Enable "Enable Email Archive" and click Save.

          4- This will activate a new tab in modusCloud ARCHIVE as shown below.


 

Create a Connector in modusCloud for O365 Archive:

  • A Connector is required so modusCloud is to associate to the tenant on O365 for each client.

          1- In the Archive tab hover over the GEAR icon and click Connections.

          2- Click the plus symbol + on the top right corner.

          3- Enter a Description for the connector.

           4- Select the connection type of SMTP (Office 365).

           5- Enter a mailbox for the Undeliverable Journal Address.

               - This mailbox will need to match the undeliverable archive address you define when you create the send connector on Office 365. It is recommended you use a dedicated mailbox for the Undeliverable Archive address.

           6- Click Next. A response is returned, providing you with a unique SMTP address. Copy  or make note of this address as you will need to specify it when you configure Archiving on Office 365. 

           7- Click Done. so the details will look similar to as below.

 

Create a Connector in O365 for modusCloud:

  • A dedicated outbound connector must be created so that all archive traffic is sent directly to the modusCloud Archive environment, instead of getting routed through the modusCloud gateway.

          1- Sign-in to the Office 365 Administration Portal.

          2- Click Admin (in the toolbar) and choose Exchange (in the left pane).

          3- Click Mail Flow.

           4- Click the Connectors tab.

           5- Add an outbound connector by clicking the plus sign "+".                   

           6- Select Office 365 from the From drop-down.

           7- Select Partner organization from the To drop-down and click Next.

           8- Enter a descriptive Name for the connector.

           9- Then enable the connector by checking Turn it on. and click Next.

         10- In the new screen that opens, select Only when email messages are sent to these domains.

         11- Then click "+" sign and enter "*.earchive.cloud".

         12- Click OK to return to the connectors screen and click Next.

         13- Select Use the MX record associated with the partner's domain and Click Next.

         14- Leave the default settings for TLS and click Next.

         15- A summary of the configuration is displayed if all look correct click Next.

         16- Enter an email address in order to validate the connector based on your region. 

               - US: verification@us.earchive.cloud 

               - EU: verification@eu.earchive.cloud

         17- When prompted to validate the connection, click Validate.

         18- Validation results are shown. To dismiss the results click Close.

 

Configure O365 to Remote-Archive Message Data to modusCloud:

          1- Sign-in to the Office 365 Administration Portal.

          2- Click Admin (in the toolbar) and choose Exchange (in the left pane).

          3- In the Exchange Admin Center, click Compliance Management.

           4- Click the Journal Rule tab.

           5- In the customer admin address area, click Select Address, click Browse, and select an admin email account.                   

               - This account will receive notification of non-deliverable archive reports. It is the same email address configured in modusCloud archive connection archive@domain.com.

           6- Add a new journal rule by clicking the plus sign "+".

           7- In the Send journal reports to field, enter the unique email address provided by modusCloud Archive as our example ie: 153bea1a-e7d8-xxxxxxxxxxxxxxxxxx@us.earchive.com.

           8- Enter a descriptive Name for the rule.

           9- From the If the message is sent to or received from... list, choose Apply to all messages.

         10- From the Journal the following messages... list, choose All messages and click Save.

         11- When prompted to confirm that you want the rule to apply to all messages click Yes.

 

Note: It is recommended that a backup archive connection be made via IMAP. Click to the link to create a Backup Archive.

7.1.3. How to Configure Archive with SMTP on Exchange 2013/2016

Product: ModusCloud

 

Situation:

With modusCloud the ability to enabled archive for inbound and outbound emails is now possible. The process requires the archive feature be enabled followed by creating a connector on modusCloud, and then finalizing the setup with O365 send connector.

The steps below allows one to follow step-by-step sequence. 

Note: It is recommended that the NDR undeliverable mailbox is not a shared mailbox.

Enable Archiving on modusCloud:

  • By default the feature is not enabled and must be activated for each client.

          1- Log into the modusCloud website US or EU

          2- Click the Features tab.

          3- Enable "Enable Email Archive" and click Save.

          4- This will activate a new tab in modusCloud ARCHIVE as shown below.


 

Create an SMTP Connector in modusCloud Archive:

  • A Connector is required so modusCloud is to associate to a local MS Exchange server for each client.

          1- In the Archive tab hover over the GEAR icon and click Connections.

          2- Click the plus symbol + on the top right corner.

          3- Enter a Description for the connector.

           4- Select the connection type of SMTP (Local Exchange 2013+).

           5- Enter the IP Addresses of the Senders Server public IP from which SMTP requests will be sent. 

           6- Click Next and a unique SMTP Address will be provided, Copy that address. 

           7- Click Save and Done.

 

Create an Archive Mailbox in Exchange 2013/2016 for modusCloud:

  • The archive account should not have any size restrictions applied to it. In addition, no Exchange Server rules should be applied to the account, especially rules that might move or delete messages from the account or move them to another folder such as Junk Mail.

          1- While logged into the ECP web portal, click recipients in the left panel.

          2- Click the mailboxes on the right panel.

          3- Click the plus sign "+" and select User Mailbox.

           4- In the popup window, click New User.

           5- Enter the Alias, First Name and Last Name of this account.                   

           6- Browse to select the Organization Unit in which you want to create the account.

           7- Enter the User Logon Name.

           8- Enter and verify a Password.

           9- Browse to the Mailbox database in which you want to create the account and click Save.

         10- Select the mailbox you just created and click the Edit icon.

         11- On the Mailbox Feature tab (left panel), in the Message Delivery Restrictions section, click View Details.

         12- For "Accept message from", select Only senders in the following list, click "+" and select the mailbox created earlier.

         13- For "Reject messages from", ensure No Sender is selected.

         14- Click OK, then Save.

         15- Log into the new account using OWA to have Exchange initialize the mailbox.

 

Configure Exchange Archive:

          1- While logged into the ECP Web Portal, click Compliance Management in the left panel.

          2- Click Journal Rules in the right panel.

          3- Click the plus sign "+" icon to create a new journal rule.

           4- In the Send journal report to field, enter the email address of the journal mailbox (created in the previous step).

           5- In the Name field, enter a descriptive name for the journaling rule.

           6- Choose the appropriate option from the If the message is sent to or received from list.

           7- Choose the appropriate option from the Journal the following messages list and click Save.

 

Create a Send Connector to modusCloud Archive:

          1- In the Exchange Admin Center, navigate to Mail Flow, and select Send Connector.

          2- Add a send connector by click the plus sign "+".

          3- Enter a descriptive Name for the connector.

           4- For type, select Custom, then click Next.

           5- Under Network Settings select MX record associated with recipient domain, then click Next.

           6- Click the plus sign "+" to edit Address Space.

           7- Set Type to SMTP.

           8- For Full Qualified Domain Name (FQDN): enter "*.earchive.cloud".

           9- Set Cost field to 1 and click Save, Then Next.

         10- Click the plus sign "+" to edit Source Server.

         11- Select the transport server(s) that will be associated with the connector.

         12- Click Add, then OK, then Finish.

 

7.2. 554 5.7.1: Relay Access Denied

Product: modusCloud

 

Why do I keep getting a 554 5.7.1: Relay access denied?

 

ModusCloud is a closed relay system. This means that all mail going through the platform must have a user associated with the platform, whether that be End-User, Alias, or Functional Account.

To resolve this issue you will want to check a few areas in modusCloud.

1-   Check to see if the Domain has relay access turned on.

  • Go to Company Settings > Domains, then make sure the switch is turned on to green.

2-   Check the Users and Groups.

  • Make sure the user who is receives the relay access denied error messages is listed in this section of the platform.
  • If the account is a functional account, make sure the account is also listed under Functional Account tab.
 

NOTE: 

          If you just added a new user in the last hour or enabled a relay on the Domains tab, your changes might have not taken effect. Give any enabled domain or added users 30 to 60 minutes to properly propagate on the platform. If you continue to receive this error message after trying these steps please contact Vircom support.

7.3. Adding AD Functional Accounts manually

Product: ModusCloud

 

Description:

A functional account on modusCloud consist of mailboxes that are not tied to a single user mailbox.. etc. 

 

  • Distribution Groups
  • Shared mailboxes
  • Scanners\Printers
  • Virtual phones\Fax
  • Security Groups 

 

 

Registering Functional Accounts manually:

 

   1-  While logged into the user interface, navigate to Users & Groups, click on Functional Accounts tab. 

   2-  Click on Add a Functional Account button.

   3-  Enter the Name.

   4-  Enter the Email address.

   5-  Select the Account type (Security Group/Distribution Group).

   6-  Click Save.

 

Note:

Functional accounts can also be added automatically through our Active Directory syn option. 

 


7.4. Building & Sending Reports in modusCloud

Product: ModusCloud

 

Building and Sending Reports in modusCloud

 

   1-   To build a report select REPORTS tab. 

   2-   On the left report panel select the report you wish to view.

   3-   Then configure the report with the data pints you wish to view.

   4-   on the right hand side click the GRAY GEAR and select SAVE REPORT AS FAVORITE.

   5-   Give the report a name and click the green checkbox.

 

On the left report panel you will see a new category called FAVORITES. Here is where you will find all your saved reports.

   1-   To send reports to your email select the SCHEDULE LIST tab.

   2-   Click ADD A REPORT SCHEDULE.

   3-   Give a description for the report.

   4-   Select the sending frequency of the report.

   5-   Enter the email address you want receiving the report.

   6-   The choose the report from your favorites drop down menu.

   7-   Click SAVE.

 

You now will receive reports via email.

 

7.5. Bulk Email Limitations Explained

Product: ModusCloud

 

Bulk email limitations explained:

There are two limits:

Standard: 500 per day, 100 per 10 minutes

Bulk: 10,000 per day, 2000 per 10 minutes

Bulk is designed for users who need it for business critical purposes, e.g. Recruitment consultants emailing individuals applying for a specific job(s), support users needing to update their users and accounts departments sending invoices.

The danger of giving all users bulk permissions is that this massively increases the risk to the company, the company’s clients and modusCloud of a spambot (for example) causing serious IP reputation problems.

When a spambot is detected, modusCloud will shut down the infected address(es) to eliminate the risk of it causing any problems. Increasing the bulk limit for all users affectively removes this ability.

There are specific third-party programs that are free to use and are designed for bulk sending, these would be recommended for services such as sending marketing material like newsletters.


7.6. Difference between Azure and Active Directory Sync.

Product: modusCloud

 

modusCloud Sync Behavior:

 

The below table illustrates the sync behavior of different tools available in modusCloud.

The Azure Directory Sync and Active Directory Sync tools are used to allow customers to sync user accounts from their Active Directory or Azure Active Directory environments.

Due to some differences between these directories, there are differences in how modusCloud handles user account syncing.


7.7. Does modusCloud limit attachment sizes

Product: ModusCloud

 

Does modusCloud limit attachment sizes?

Standard Messaging:

ModusCloud supports email attachments up to 100MB in size by default - however, many organisations' mail servers enforce a lower size restriction on attachments than this (sometimes as low as 10MB). If you are having problems sending emails with large attachments, this is most likely due to a restriction on the recipient's mail server. If you are having problems receiving email with large attachments, please consult your organisation's Tech Contact.

It is also possible to create filters to impose size restrictions on inbound and outbound emails at both an Organisation and User level in modusCloud. 


Encryption Messaging

ModusCloud encryption service does not use the same messaging gateway. The maximum file size when using encryption services is 35mb.

 

7.8. Emergency Inbox

Product: ModusCloud

 

Emergency Inbox:

The Emergency Inbox service was created for mail continuity as indicated on the linked page. Users that can access this feature are able to use a web mail based mail feature while their mail server is down.

The modusCloud service will continue to try and check the customer's mail server, as per the standard set-up. As we are unable to relay the email from our system to the customer's server (as it is down), we are required by RFC to send a deferral notice back to the sending mail server that we have not been successful in delivering the email. As long as the customer's mail server is down, we will continue to send deferral messages for some time (we set 30 days) then bounce the message back to the sender. It is important that the customer mail server be brought back as soon as possible to not lose email.

Emergency Inbox is used to provide users access to email in the event that their mail environment is unavailable. Once this occurs modusCloud will automatically begin to spool mail for the affected domain and the Emergency inbox will immediately begin to show the spooled mail. Users are able to send new messages as well as reply to received messages. When an email is sent out from Emergency Inbox – new email, reply to email – it is treated like any outbound message. So the email will show up in another internal user’s Emergency Inbox. Users are unable to see messages that were successfully delivered prior to mail delivery being impacted. 

 

How to access the Emergency Inbox:

End-user Access:

   1- Log into the interface. By default, you are at the Account Setup page.

   2- From here, you can go directly to the Emergency Inbox from the sub-heading under Account Setup.

 

Admin Access:

   1- As an admin, once you are logged in, go to the Users & Groups tab.

   2- By default, you are in the Users sub-heading.

   3- Find the end-user you want to go to.

   4- Click the end-user's name/email address or the 'Edit" link on their line

   5- A new sub-heading bar will be available, and click on Emergency Inbox.

 

Testing Emergency Inbox: 

For testing the Emergency Inbox, you can deadhead the SMTP delivery address by changing the delivery server to 1.2.3.4 This should start spooling and deferring the messages putting them in the Emergency Inbox.

  • To accomplish this go to Company Settings -> Domains 
  • Click on the Pencil Icon to the domain your looking to change. 
  • In the SMTP Delivery destination put in 1.2.3.4 or any other bogus IP address 
  • When your done testing just reverse the changes made. 

Note that Strategic Partners and Channel Administrators cannot access other customer's Emergency inbox's but their own. When attempting to launch an Emergency inbox that you do not have permission to view - a blank window will be displayed. 

 

7.9. Getting Started with modusCloud

Product: modusCloud

 

Connnection Details:

 

Customers hosted on modusCloud North America or Europe should refer to the following table for details on configuring and accessing your account.


Information

modusCloud-US

modusCloud-EU

URL

https://moduscloud-cloud-protect.net

https://moduscloudeu-cloud-protect.net

MX Records

mx1-us1.ppe-hosted.com

mx2-us1.ppe-hosted.com

mx1-eu1.ppe-hosted.com

mx2-eu1.ppe-hosted.com

SPF

“v=spf1 a:dispatch-us.ppe-hosted.com ~all

“v=spf1 a:dispatch-eu.ppe-hosted.com ~all

Smarthost

outbound-us1.ppe-hosted.com

outbound-eu1.ppe-hosted.com

IP Addresses ports 25/389

         67.231.152.0/24           

                       67.231.153.0/24

         67.231.154.0/24           

                       67.231.155.0/24

         67.231.156.0/24           

                       67.231.144.0/24

         67.231.145.0/24           

                       67.231.146.0/24

         67.231.147.0/24           

                       67.231.148.0/24

     148.163.128.0/19       

                        207.115.110.3

        207.115.110.7           

                           192.69.1.3

               192.69.1.7                 

                         207.96.143.7

          91.209.104.0/24           

          91.207.212.0/24           

          91.207.213.0/24           

           62.209.50.0/24            

                        62.209.51.0/24

                      185.132.180.0/24

                               185.132.181.0/24

                               185.132.182.0/24

                               185.132.183.0/24

                               185.183.28.0/24 

                      185.183.29.0/24

                               185.183.30.0/24

                               185.183.31.0/24 

                         207.96.143.7

207.115.110.3

207.115.110.7

192.69.1.7

 192.69.1.3 

Email Archive port 143/993

34.192.199.2

52.55.243.18

52.54.85.198

35.158.81.74

18.195.34.45

35.158.59.63

7.10. How to access the Emergency Inbox

Product: ModusCloud

 

How to access the Emergency Inbox:

The Emergency Inbox feature is available by default to all registered accounts with at least end-user privileges to access the interface. There is a predetermined number of days that this Emergency Inbox is available. This is termed as Instant Replay in the features. 

End-users will need to know the specific URL and use their email credentials to log in:

   1- https://moduscloud.cloud-protect.net - North American Clients.

   2- https://moduscloudeu.cloud-protect.net - Euro\AsiaPac Clients.

Emergency Inbox feature is available for all registered end users across all three packages. However, the availability of this feature is available for maximum 30 days.

 

End-user Access: 

    1- Log into the interface. By default, you are at the Account Setup page.

    2- From here, you can go directly to the Emergency Inbox from the sub-heading under Account Setup. 


Admin Access: 

   1- As an admin, once you are logged in, go to the Users & Groups tab.

   2- By default, you are in the Users sub-heading.

   3- Find the end-user you want to go to.

   4- Click the end-user's name/email address or the Edit link on that line.

    5- A new sub-heading bar will be available, and you may now click on the Emergency Inbox. 

7.11. How to Configure Outbound relay on Office 365

Product: ModusCloud

 

Situation:

The following steps should be taken to route email outbound from Office 365 to modsuCloud. These steps will help you provision/setup outbound mail-flow.

 

Configure Outbound Relaying on modusCloud: 

 

  • Follow these steps to enable relaying on modusCloud.

          1- Log into the modusCloud website US or EU

          2- Click the Features tab.

          3- Enable Outbound Relaying and click Save.

          4- Click on the Domains tab.

          5- Click on the button Manage Hosted Services.

          6- Click on the slider of Office 365 and click Save.

NOTE: When this is enabled modusCloud will automatically manage the IP ranges for Office 365 published by Microsoft. Updates are performed daily.            


Configure Outbound Relaying on Office 365: 

 

  • Follow these steps to route outbound from Office 365 to modusCloud. 

          1- Log into the Office 365 Admin Center.

          2- Select the Admin Center > Exchange menu item. The Exchange Admin Center is displayed.

          3- Select the Mail Flow > Connectors menu item.

               - Create a new connector by clicking the + icon at the top and set a New Connector as follows.

                   From: Select Office 365 from the drop down list.

                   To: Select Partner Organization from the drop down list. 

           4- Click the Next button and complete the following below.

                   Name: Enter a name for your connector.

                   Description: Enter a description.

                   Turn On: Select this option to enable connector.

           5- Click the Next button. 

           6- Select the Only when email messages are sent to these domains option.

               - Click the plus icon + to add domains that should use this connector.

               - Enter a value of * (asterisk) and a second value of *.com, this will route all outbound emails through moduscloud. 

               - Click the OK button and click the Next button. 

           7- Select the Route email through these smart hosts option. 

               - Click the plus icon + to add your modusCloud smart host.  

               - Click the Next button.

           8- Select the following options.

               - Always use Transport Layer Security (TLS) to secure the connection (recommended) Issued by a trusted certificate authority. 

               - Click the Next button twice to verify settings and continue. 

            9- Add and email address of a recipient for a domain external to your organisation and click Validate button. 

NOTE: If you did not choose to turn the connector on Step 4, validation will fail. if your validation results show that the connection was successful, but the email filed to send because the domain of the recipient is not configured as part of connector - this may be due to connector being disable. Try enabling the connector and re-attempt the validation.

           10- Once Office 365 has been successfully validated click Save to complete the configuration. 

7.12. How to Manage User Accounts

Product: ModusCloud

 

Managing Users:

Users and groups are accessed under the Users & Groups tab. Users and groups can be added manually or through LDAP Discovery or CSV upload 

An administrator can add a user and group by providing basic details through the web form. Users can only be added if there SMTP address domain has already been registered. 

 

To Add a User:

 

   1-  Click on the Users & Groups tab.

   2-  Click on the Users tab.  

   3-  Click on Add a User button.

   4-  Fill in the required information (*Required Fields).

   5-  First Name: The first name of the user.

   6-  Surname: The last name (surname) of the user.

  • Email Address: The primary email address of the user. 
  • User Privileges: The role of the user.                             

   7-  Click Save. 

Note:

When you create an End-User, a welcome email is sent by default. Users will be directed to click on an encoded URL in order to set their own password.

 

To Reset a User Password: 


   1-  Click on the Users & Groups tab.

   2-  Click on the Users tab.  

   3-  Locate the user you wish to update.

   4-  Click the users name or the Edit button.

   5-  Click on Reset Password.

Note:

This will automatically send users an email with a link to create a new password.

 

To Update a User:  


   1-  Click on the Users & Groups tab.

   2-  Click on the Users tab.  

   3-  Locate the user you wish to update.

   4-  Click the users name or the Edit button.

   5-  Update information as needed.

   6-  Click Save. 

 

To Delete a User: 

 

   1-  Click on the Users & Groups tab.

   2-  Click on the Users tab.

   3-  Locate the user you wish to delete.

   4-  Check the checkbox next to the user.

   5-  Click the Select list and select Delete.

   6-  Click Apply.

 

To Add an Alias to a User: 

 

   1-  Click on the Users & Groups tab.

   2-  Click on the Users tab.

   3-  Click on the name of the user you wish to add the alias to.

   4-  Click on the Aliases tab.

   5-  Click Add Alias.

   6-  Type the alias into the text box.

   7-  Click Save.

 

 

 

7.13. How to Setup ModusCloud with Google APPS

Product: ModusCloud

 

Description:

This article explains how to configure G Suite to use ModusCloud as your mail gateway. 

 

What is G Suite:

G Suite (also known as Google Apps) is a cloud-based solution from Google which offers email, messaging, security, archiving and other capabilities delivered from Google’s worldwide network of cloud data centers. 


Before You Start:

Before continuing with the provisioning and configuration of the modusCloud service, it is recommended that you have the information listed below. 

 

  • MX record(s) for domain(s) you are configuring.
  • ModusCloud IPs, Smarthost and SPF (Getting Started Document at the end of the article).
  • Google Admin account.

 

 

Setup INBOUND Mail Flow:

ModusCloud is deployed between the customer’s G Suite environment and the Internet. Inbound mail is routed to ModusCloud by changing the customer’s MX records. After email is processed by ModusCloud it is routed to G Suite.

 

CONFIGURE MODUSCLOUD: 

Adding domain(s) to ModusCloud: 

   1-  Sign-in to the ModusCloud interface.

   2-  Click the Domains tab.

   3-  Click on New Domain.

   4-  Enter the domain name you wish to configure.

   5-  Ensure "Relay" is selected for domain purpose.

   6-  Enter the delivery and failover destinations value. 

   7-  Choose the method you wish to use for domain verification.

   8-  Click Save. 

   9-  Repeat if you are adding more than 1 domain.

 

CONFIGURE G SUITE:

Configure Inbound Mail Gateway:

   1-  Sign-in to the Google Admin console.

   2-  From the dashboard go to AppsG SuiteGmailAdvanced Settings. 

   3-  While on the General Settings tab, scroll down to the Spam> Inbound> Gateway.

   4-  Hover the cursor to the right of Inbound gateway. To create a new inbound gateway setting, click Configure. 

   5-  Under Gateway IPs, enter the IP addresses listed on our (Getting Started Document at the end of the article).

   6-  Check the option Automatically detect external IP. 

   7-  Check the option Reject all mail not coming from gateway IPs.

   8-  Check the option Require TLS for connection from the email gateways listed above. 

   9-  Click Add Settings. 

 

 

Setup OUTBOUND Mail Flow:

ModusCloud is deployed between the customer’s G Suite environment and the Internet. Outbound mail is routed to ModusCloud by configuring an outbound mail gateway. This will route all outbound mail to ModusCloud.

 

CONFIGURE MODUSCLOUD: 

Enable Outbound Relaying:

   1-  Sign-in to the ModusCloud interface.

   2-  Click the Features tab.

   3-  Check Enable Outbound Relaying.

   4-  Click Save. 


Add Service IP addresses to your Inbound Gateway:

   1-  While logged into ModusCloud interface, click the Domains tab.

   2-  Click Managed Hosted Services.

   3-  Choose Google APPS.

   4-  Click Save. 


CONFIGURE G SUITE:

Configure Outbound Mail Gateway: 

   1-  Sign-in to the Google Admin console.

   2-  From the dashboard go to Apps> G Suite> Gmail> Advanced Settings.

   3-  While on the General Settings tab, scroll down to the Routing> Outbound Gateway.

   4-  In the Outbound Gateway text field, enter the ModusCloud Smarthost value from the (Getting Started Document at the end of the article).

   5-  Click Save.


Update Sender Policy Framework (SPF):

When sending outbound email through the ModusCloud gateway, recipients receive mail sent from ModusCloud rather than G Suite mail servers. If the recipient's mail service attempts to verify that the message came from your domain, it must confirm that the gateway server is an authorized mail server for your domain.

To enable this, you need to add the ModusCloud SPF record to your domain. View this information in our (Getting Started Document at the end of the article).

 

CONFIGURE MX record change:

Locate your MX record for the domain in G Suite:

   1-  Sign-in to the Google Admin Console.

   2-  From the dashboard go to Apps> G Suite> Gmail> Advanced Settings. 

   3-  While on the General Settings tab, scroll down to Setup> MX Records and make note of all the "Points to" value. 

7.14. How to Whitelist and IP Address from Spam Scanning

Product: modusCloud

 

How to whitelist an IP address from spam scanning:

 

If an email has been blocked by modusCloud as a result of content we can ensure further delivery of these emails by whitelisting there IP address.

To whitelist and IP so that it is not blocked as a result of content:

1-   Click on Company Settings.

2-   Click on Filter tab.

3-   Click on New Filter button.

4-   Choose a name for the filter.

5-   Click on the Continue button.

6-   Choose a proper scope for the filter. 

  • If you want the filter to be applied to everyone, leave the scope = "Company".
  • If you want to target a specific individual or group of individuals, change the scope.

7-   Choose Email Header from the drop-down list or option message elements

8-   Choose Contain(s) Any Of from the drop-down list or operators.

9-   Type in the IP address what you wish to whitelist.

  • You can enter more than 1 IP address by separating values with a comma.
  • CIDRs (x.x.x.x/x) are not support.
  • IP ranges (x.x.x.x-y) are not support.

10-  Choose "Allow" from the drop-down list of actions. Click Save


NOTE: 

          If you wish to add additional IP addresses at a later date, you can either edit this filter or create a new filter. These IP addresses can also be added to a domain or users Safe Senders List as an alternative solution as well.

7.15. modusCloud Email Encryption Plug-in for Outlook

Product: ModusCloud

 

About:

The modusCloud Plug-in for Microsoft Outlook allows users to send secure messages from within the Outlook interface.

 

Step 1: Download the proper Outlook Plug-in

Refer to the compatibility matix below and the installation file at the bottom of the article

 

Step 2: Install the Outlook Plug-in

  1- Double-click the downloaded installation file to start the installation process

    2- Click Run on the security warning if it pops up

    3- Click Next on the modusCloud Encryption Plug-In for Microsoft Outlook Setup screen

    4- Check the box for the license agreement and click Next

    5- Click Next to install in the default folder or click Change to select another location 

    6- Click Next

    7- Click Install

    8- Click Finish when the installation has completed

 

Step 3: Verify Installation

    1- Launch Outlook

    2- Compose message

    3- Look for the Send Securely button in the message composition window  

   

Step 4: Create a Custom Filter

    1- Login to the interface

    2- On the Company Settings tab, click Filters

    3- Click the Outbound Tab

    4- Click New Filter

    5- Enter a name for the filter (e.g., Encryption Plug-In)

    6- Click Continue

   7- Select Email Header from the drop-down list

   8- Select Contain(s) Any Of from the drop-down list

   9- Type encryptdesktop into the text field

  10- Select Encrypt from the drop-down list to the right of "Do"

  11- Click Save  

 

modusCloud Encryption Plug-in Compatibility Matrix: 

Exchange Version

Windows Version

Outlook Version

Installer Version

Exchange 2007

Windows 7

Outlook 2007

MC_Plugin_Outlook_1.2.6.0.msi (32-bit)

Exchange 2010

Outlook 2010

MC_Plugin_Outlook_1.2.6.0_x64.msi (64 bit)

Exchange 2013

Outlook 2013

Exchange 2010

Windows 7

Outlook 2010

MC_Plugin_Outlook_1.3.5.msi (32-bit)

Exchange 2013

Outlook 2013

Windows 10

MC_Plugin_Outlook_1.3.5_x64.msi (64-bit)

Exchange 2016

Outlook 2016

 

7.16. modusCloud Error Codes

Product: ModusCloud

 

Common Error Codes:

Delivery summary: Any time you see, "This message was rejected by its destination for reasons outside the control of modusCloud, and got returned to the sender", this literally means that this is outside our control, and this issue must be with the Customer/Recipient server accepting the message. 

452 4.3.1 Insufficient system resources: This normally means that the recipient/customers server doesn’t have enough resources to accept messages. Customer/recipient needs to resolve this issue before we can deliver the message. (MS Exchange).

550 5.7.1 : Recipient address rejected: User email address is marked as invalid. This means normally you have SMTP Discovery enabled and the user is on the SMTP Discovery Invalid list. Remove this user from this list to resolve this issue. 

550 5.1.0 sender rejected: The senders IP address is rejected due to a Blacklist/ wrong SPF. This is outside the control of modusCloud. 

550 5.7.1 Relay Access Denied: We are a closed relay system. This means if a user is in the modusCloud system we will deny access to any e-mail that is not registered. 

 

For more information and understand on error codes please visit https://tools.ietf.org/html/rfc3463 

7.17. Not Receiving Inbound Email from a Sender or Domain

Product: ModusCloud

 

Situation:

If modusCloud users are unable to receive email from certain email addresses, it is most likely an issue with the sending mail server. However there are a few possible areas where this may be a configuration issue on the modusCloud platform: 

 

      1- There maybe a rule in the "Filters" section quarantining emails from that address or domain.

        To view Company filters:

  • Login to the modusCloud user interface.
  • Type the customer name into the search bar (Top Header)
  • Click on Company Settings.
  • Click on Filters tab.

 

      2- There is a 3rd party MX record pushing some emails towards another mail server.

      3- The sending server IPs may be blacklisted. We mainly utilize modusCloud RBL service for connection level validation, but also take in other feeds along with RBL. You can verify if an IP is                   being blocked by RBL here: www.emailsecuritygrader.com.

 

If further assistance is required, please contact support with as much details as possible:

  • Non Delivery Report (NDR).
  • Sending Server IP address.
  • Senders's email address.
  • Time and date the email was sent.
  • Also note that if an email is bounced the bounce error will also provide details as to why it was bounced which may help identify the cause.

7.18. Office 365 Account Login

Product: ModusCloud

 

Office 365 Account Login:

With our latest modusCloud release (5.60) users are able to login to their account via Office 365 integration. To login with your Office 365 account you must have already imported users into modusCloud via Azure Active Directory..

If this has not been done, you will have to perform the AZURE ACTIVE DIRECTORY SYNC. please contact Vircom support so that our support team may assist you.

   1-   Go to your modusCloud account login page.

   2-   Click on Office 365 Account button.

   3-   The option will redirect you to Microsofts account login.

   4-   Enter your credentials.

   5-   If successful the login will redirect back to modusCloud and you will be automatically signed into your account.

  •    If unsuccessful an error will be generated, error: Azure authentication failed. Please try again. 

 

NOTE:

Aside from importing user accounts, no further configuration changes are required.

 

7.19. Reporting False-Positives and False-Negative

Product: ModusCloud

 

Ticket Creation:

For these processes, we highly recommend providing the details directly in our ticketing system by attachments. Please make sure when submitting, follow these ticketing processes:

Creating a ticket:

Updating a ticket:

 

False Positive (FP): message that is not spam, but incorrectly being blocked as spam. 

The false positive sender of messages will have the message quarantined. (Depending on set-up, the user and/or admin will get a notification of this.) The Support Team will need a copy of the original message being sent. Without this original message, we cannot assist you in sending or receiving this message we will be unable to adjust our anti-spam service for this FP message issue. 

 

False Negative (FN): message that is spam, but is incorrectly seen as a regular email.

Incoming False negatives are messages that come through our system that passed our anti-spam filtering. This is an annoyance to end-users and should be reported to ensure that the message(s) are not seen again. 

 

Reporting FP/FN as an admin:

    1- Go to the Logs

    2- Search for this message (again)

    3- Click the detail/view button

    4- Press the "Report as ..." (False Negative - spam/False Positive - not spam)

    5- Fill out the information on the next page

    6- Submit

    7- If you would like to check the status of the reported message(s) please open a ticket with the permalink(s)

 


7.20. Sending Welcome Email to Multiple Users

Product: ModusCloud

 

Description:

Administrators at times would like to alert there users of a new account or having to setup the modusCloud password by sending a welcome email. This will allow the user to confirm his identity and specify a password login for his\her account.

 

Please follow the below steps to allow users to receive a welcome email:

 

   1- Select Users & Group.

   2- Check the checkbox beside the user(s) you wish to send the Welcome email to.

   3- Select Mass Update from the drop down list.

          

     4- Check the Send Welcome Email checkbox.

          

     5- Select Update Users.


All your checked end users will receive a welcome email. 

7.21. SMTP Discovery

Product: ModusCloud

 

SMTP Discovery

Description:

Another way to provision users to the modusCloud service is with SMTP Discovery. When enabled, SMTP Discovery allows email to be relayed to non-licensed users. Users become licensed-users when manually added within the span of 30 days, a specified number of valid messages are received for that unique address or one valid message has been send outbound from your local mail server via the modusCloud platform. An administrator can change the SMTP Discovery settings.

 

Please Note: 

Users will only be automatically added for received messages if "EXPIRED ADDRESSES DEFAULT TO NEW USERS" is enabled, and only added automatically for outbound if "AUTO-ADD NEW USERS DETECTED VIA OUTBOUND" is enabled (both options listed under the SMTP Discovery setting). If these options are not used, they will need to be added via the "DISCOVERED LIST" within the NEW USER report, or via the SMTP Discovery report under USERS & GROUPS - SMTP DISCOVERY.


Enable or Disable SMTP Discovery:

   1-   Click on the tabs COMPANY SETTINGS - FEATURES.

   2-   Disable (uncheck) or Enable (check) the SMTP Discovery checkbox and click SAVE.

 

Update SMTP Discovery Settings:

   1-   Click on the tabs COMPANY SETTINGS - SMTP DISCOVERY

   2-   Choose the default privileges type for new users.

  •  End User: This user privilege type will receive a quarantine report and can login to the modusCloud user interface.
  •  Silent User: This user privilege type will receive a quarantine report and cannot login to the modusCloud user interface.
   3-   Select Inbound Detection Threshold.

  •  The number of clean emails in a 1 month period before the address appears in the SMTP Discovery list.
   4-   Choose how many times you would like to be notified about an address before it expires. 
  •  The named technical contact will receive a weekly notification of discovered addresses. This selection determines the number of notifications, which will be delivered before an address expires. ModusCloud will not deliver email to an expired address. 
   5-   Disable (uncheck) or enable (check) if expired addresses default to new users. 
  •  This setting may create new users. As a result this option can only be controlled by the Organization Administrator.
   6-   Disable (uncheck) or enable (check) if aliases should be automatically associated with accounts.

   7-   Disable (uncheck) or enable (check) if users detected via outbound should become licensed. 

  •  This setting may create new users. As a result this option can only be controlled by the Organization Administrator.  

   8-   Disable (uncheck) or enable (check) to send out a report on new users.

   9-   Disable (uncheck) or enable (check) to send out a report on new aliases.

 10-   Disable (uncheck) or enable (check) to include the administrator contact in the report.

 11-   Click Save

 

Adding Discovered users via the Web Interface:

   1-   Click on the USERS & GROUPS tab.

   2-   Click on the SMTP DISCOVERY tab.

   3-   Use the pull down to select "DISCOVERED LIST" for discovered accounts, or "MARKED INVALID" for accounts that have been marked invalid (and can no longer receive emails).

   4-   Click the checkbox next to any accounts you would like to have added as users.

   5-   Change the pull down next to the APPLY button to "CREATE USER ACCOUNT" (to add as a normal user), "CREATE FUNCTION ACCOUNT" (to add as a functional account), or "MARK AS INVALID" (to move them to the Marked Invalid List. This will prevent them from receiving any emails).

   6-   Click the APPLY button.

 

Please view the article SMTP DISCOVERY MANAGEMENT for more information on managing SMTP Discovery users.

 

Please Note:    

SMTP Discovery will be disabled if LDAP 24 HOUR SYNC is enabled.

 

7.22. SMTP Discovery Management

Product: ModusCloud

 

SMTP Discovery Management

Description:

Chossing the SMTP Discovery method to add customer accounts will require a certain amount of on-going management attention and administration to ensure accounts are up to date and license balances are accurate.

To make this process more manageable for you, we have added the ability for partners to set the following specifications:

 

  • Choose what modusCloud should do with newly discovered addresses.
  • Decide how we should manage these new addresses for you.
  • Stipulate what notifications we should send

 

PLEASE CONFIGURE THESE NEW OPTIONS  for your entire user-base or on a per-customer basis and make the changes as soon as possible. The new settings will not take effect until the options are fully configured, otherwise the current SMTP settings will remain active or the defaults will become activated.

At modusCloud we continue to recommend LDAP (Active Directory) or Azure Sync as the preferred option for adding new customer accounts as it's the most accurate and requires minimal on-going management as it updates automatically itself periodically.

Where LDAP is not possible however please configure the following options for SMTP DISCOVERY.  Please note, the SMTP DISCOVERY process executes 4 times a day, so you may see some delay in discovered addresses appearing in the interface.

 

SMTP Discovery Settings

These settings will allow you to specify that modusCloud should do with newly discovered addresses, choose how we manage these and stipulate what notifications we should send.

   1-   DEFAULT NEW USER PRIVILEGES: Select the default user type, Silent Users will not receive welcome emails or be able to login to the interface, End Users will have both.

   2-   INBOUND DETECTION THRESHOLD: Select how many clean emails modusCloud must detect before the email address appears on the SMTP Discovery list.

   3-   NUMBER OF TIMES TO BE NOTIFIED: Choose the number of weekly SMTP Discovery Report notifications you would like to receive before the email address expires from the SMTP Discovery list.

   4-   EXPIRED ADDRESSES DEFAULT TO NEW USER: Selecting this option enables you to specify that any email address which has expired from the SMTP Discovery list is added as a new user rather than being marked as invalid. An invalid address will no longer receive emails

   5-   AUTO-ADD DETECTED ALIAS ADDRESSES: Select this option to allow SMTP Discovery to add detected alias addresses automatically. ModusCloud has logic in place to help us deduce as far as possible an alias address for a user e.g. blogs@company.com could be an alias of blogger@company.com. However a less obvious alias should be added manually to avoid being misconstrued as a user and the associated licensing implicaitons.

   6-   AUTO-ADD NEW USERS DETECTED VIA OUTBOUND: You can select this option if you wish SMTP Discovery to automatically add to the system any new address which is detected as sending outbound email.

   7-   REPORT ON NEW USERS: Select this option if you wish for modusCloud to send a confirmation to the technical and\or administrator contact, notifying them that a new user has been added by SMTP Discovery.

   8-   REPORT ON NEW ALIASES: Selecting this option will prompt modusCloud to send out a confirmation to the technical and\or administrator contact associated with the account, notifying them that an alias address has been added by SMTP Discovery.

   9-   INCLUDE ADMIN CONTACT IN REPORT: Select this option if you require the Administrator Contact to be send a report as well as the Tech Contact.

REMEMBER TO HIT SAVE AT THE BOTTOM. The changes will take effect immediately.

 

NOTES: 

  • Expired addresses default to New Users requires that a company's organizations admin agree to this by a pop-up statement. This agreement may have billing implications.
  • SMTP Discovery will be disabled if LDAP 24 hour sync is enabled. 


 

7.23. Spam Settings

Product: ModusCloud

 

Spam Settings:

Spam settings can be adjusted from the Spam option tab when logged into your interface. 

 

Customise Spam Filtering:

Some users might need different spam filter levels, filtering turned forward only, or to manage their own filter settings.

 

Spam filter levels:

Most users probably want all categories of spam filtered aggressively. Your Sales team, however, might want lenient filtering of Commercial Offers, so potential leads aren’t wrongly identified as spam. You might place sales@mycompany.com in an account where the spam slider is adjusted to a less aggressive trigger point.

 

Spam Slider:

This feature has a wide range of setting (2 - 22) which endeavour to meet the needs of all users. It is possible manage your users Spam trigger threshold by adjusting this slider to a trigger level more closely to their needs. The range includes:

  • Very Strict: 2 - 3
  • Strict: 4 - 5
  • Standard: 6 - 8
  • Loose: 9 - 14
  • Very Loose: 15 -22

Within each of these ranges is a fine tuning range to keep detection in as small steps of increment that is required to detect and manage modern sophisticated botnets. Spam sliders and adjustments of trigger levels are available per user and Per organisation. (The lower the trigger level, the more spam is stopped. The higher the trigger level, the less we stop spam.) 

 

Spam filtering on/Stamp & Forward:

Most users want their spam filters on. But they might want to forward spam that through to Customer Support for further analysis. So that potential spam can get through, you can choose
Stamp & Forward for the email addresses used by Customer Support.

 

Update spam detection settings above for all existing user accounts:

This feature will retroactively activate the above features across all users (regardless of their personal settings currently set).

 

Inbound Sender DNS sanity checks (disable at own risk):

Please review this article for a more detailed explanation. When enabled, the “Inbound sender DNS sanity checks” provides an additional validation on the sender domain DNS on Inbound Email. The validation includes:

   1- Sender Domain MX Records.

 

  •  A message will be rejected if the MAIL FROM domain has:
         - No DNS, A record, or MX record.

               - A malformed MX record such as a record with a zero-length MX hostname. 

    2- Sender Domain MX records that point to private / reserved IP ranges.

 

  • This signals a severe DNS misconfiguration and as a result we would reject the message.

 

  

7.24. Understanding Bounces and Deferral of Emails

Product: modusCloud


The following information provides details of email behavior in the LOGS:

Bounce and Deferrals Troubleshooting:

 

Delivered: Messages that are sent through modusCloud platform and are delivered.

Quarantined: Message that are quarantined by one of the filters on the platform.

  • These messages can be released from quarantine.

Blocked: Messages that are blocked because of a virus or executable file.

  • Messages that are blocked are not allowed to be released.

Deferred: Message could not be delivered to client's/recipients server.

  • Messages will be retried up to 30 days. These emails will be automatically retried once every 5min, 15min, 30min and 1 hour after that for the next 30 days.
  • These error are temporary and normally result in 400 error codes.
Bounced: Messages did not get delivered to the recipient/customers server.

  • Messages get sent a non-delivery report (NDR).
  • These are what we call a Hard Bounce normally 500 error codes
  • These messages will need to be resent.
Queued: This is a placeholder for our back-end logs to update the Front-end UI logs. This normally does not indicate whether the message was delivered or not. 

 

8. Alleviating Spam – Best Practices

 

Product: All

Version & Build: All

 

 

This article describes how to optimize your modus server configuration to prevent as much spam as possible from entering your system.  This article assumes that modus is the mail entry point so that it sees the IP addresses of the external sending mail servers.  It also assumes you do not have a gateway in front of the modus server, pre-filtering mail, as it would show mail as coming from the gateway IP address.

 

 

Open the modus Administration Console to configure the following:
 
Security – Properties – DNS Blacklists (DNSBL)

 

  • Enable Perform a lookup for the SMTP host in the Real-Time Blacklist
  • Click on RBL Servers and enter the following:
    • Sbl-xbl.spamhaus.org
    • bl.spamcop.net
    • See below for additional RBLs 
  • Ensure that Reject connection immediately if the host is blacklisted is not enabled
  • Enable Perform RBL check after mailbox authentication
  • Set the Cache values to 9000 (lookup results) and 240 (minutes)
  • Click on IP Exclusion and enter the IP addresses for all of your IP blocks
    • E.g. 10.10.10.0/24, 10.10.20.0/20, 10.10.30.25, etc.
  • Click on Apply

 

Least Aggressive RBL Combination

 

sbl.spamhaus.org        known spam sources only
cbl.abuseat.org composite block list

           

  

Moderately Aggressive RBL Combination


sbl-xbl.spamhaus.org combination of sbl & xbl
cbl.abuseat.org composite block list
dul.dnsbl.sorbs.net dynamic ranges
bl.spamcop.net spamcop block list

 

Very Aggressive RBLs 


zen.spamhaus.org  includes sbl, xbl + pbl
cbl.abuseat.org composite block list
dnsbl.sorbs.net full sorbs zone
bl.spamcop.net spamcop block list

  • Warning: using the Perform RBL Check after mailbox authentication function keeps the connection open longer
  • If you are not an ISP/xSP or you do not have dynamic IP range provisioning for your users, it may be better to reject the connection immediately

For a good list of comparative RBLs, use this link:
http://www.sdsc.edu/~jeff/spam/cbc.html
If you want to completely block specific countries from sending you mail, information can be found here:
 

http://www.emailsecuritymatters.com/site/blog/best-practices/country-based-blocking/

 

Security – Properties – Connection Limits

 

  • Maximum simultaneous connection rate allowed for the same IP: enter 5
  • Total number of simultaneous connections allowed from the same IP: enter 5
  • Click on Apply

 

 

Security – Properties – Trusted Address List

 

  • Under SMTP Security Trusted Address, click on IP Address
  • Enter the enter the IP addresses for all of your IP blocks
    • E.g. 10.10.10.0/24, 10.10.20.0/20, 10.10.30.25, etc.
  • Click on Apply
NOTE: These options tell modus to do connection-level verification for messages originating from the specified IPs or IP blocks. It does not prevent content filtering. It only prevents RBL checking or throttling by "Block Scan Attack" or "Connection Limits," etc., from being applied to the specified addresses.
 
 

Security – Properties – SMTP Security

 

  • Check Enable SMTP Authentication
  • Enable the following:
    • Do not advertise SMTP AUTH for these  

        § In the IP Address list, enter the following 2 items:

        § !127.0.0.1 (the ! denotes not), and *.*.*.*

    • Force usage of fully qualified addresses in SMTP commands
    • Reject malformed addresses
    • Validate sender addresses
      • Set the Cache Size to 9000 entries
      • Set Keep in cache for 240 minutes
  • Click on Apply

 

 

Security – Properties – Block Scan Attack

 

  • Ensure that Enable Scan Attack Blocking is checked
  • Click on Slowdown the IP Connections
  • Disable Force a slowdown on IP connections and Close
  • Click on Block IP Addresses
  • Block IP for 240 minutes
  • Check After the number of invalid recipients reach and set the value to 3
  • Click on Close
  • Set the Cache values to 9000 (lookup results) and 240 (minutes)
  • Click on Apply

 

 

Security – Properties – Sender Reputation (or Sender Validation & Accreditation in earlier versions)

 

  • Enable Sender Reputation System
  • The recommendation is to quarantine messages with a 'bad' SRS reputation
    • Results are updated every 5 minutes
    • This option protects you from newly detected spam waves, and quickly delists IPs that have been removed from botnets
  • Enable SPF Support
  • Click on Apply
  • An SPF record is not required for this feature
  • Optionally, you could enable Perform a look up for the SMTP host in DNS
    • This is a reverse DNS lookup on the IP address of the sending server to check if it has a reverse PTR record
    • Historically, enabling this option caused more false-positives because many legitimate mail servers did not have reverse zones
    • However, as spam increases, more companies are turning this feature on, despite the risk
    • Most spam originates from IP addresses that are used for dynamic IP allocation which do not have a reverse PTR record (i.e. DSL or cable modem users with infected zombie machines)
    • Enabling this can be risky but will alleviate spam problems considerably – use with caution

Other articles of interest concerning reverse DNS
 
 


Spam – Preferences – Options


  • Set the Spam Scanning Level to Extreme
  • Click on Apply

 

 

Rules – Performance – Enable Attachment Size Verification
 
  • Do not scan messages with attachments greater than X kilobytes
    • This is a misnomer: it’s actually the message size that counts
    • The default size in recent modus versions is 950 kilobytes, but we recommend using a smaller size: 350 kilobytes
 
 

System – Properties – Services

 

  • Stop and restart:
    • SMTPRS
    • MODUSCAN


IMPORTANT SAFETY TIP

It is important that you never whitelist your own domain at the global or user level. It is also important that end-users never whitelist their own email addresses.

This is because spammers are in the habit of forging your domain in the “from” field. Whitelisting yourself means any email From yourself TO yourself will be whitelisted if the spammer is smart enough to forge your domain in the header “from” field.

Note that version 5.0 will automatically check for and ignore self-whitelisted addresses to ensure that the content undergoes spam scanning, to prevent potential abuse of your system. 

 

 

 

 

9. directQuarantine Technical Information
9.1. Direct Quarantine toolbar is greyed out.
Product: Direct Quarantine

Version & Build: All

 

 

Problem Summary:

 

Direct Quarantine toolbar is grayed out and right clicking on spam shows the spam option as grayed out (or going to quarantine shows zero messages).  

 

 

Cause:

  •             No communication between the workstation and modusGate.  You can test by using telnet on the workstation to the port 9000 of modusGate (ie:  telnet gate.yourdomain.com 9000) will usually tell you right away if the connection is happening or not.  If the connection is failing, make sure you open up port 9000 on your firewall between that workstation and your modusGate server.

  • License problem – your key doesn’t have dQ cleared or it’s expired.  Check in the modusGate advanced console -> SYSTEM -> License key and where it shows directQuarantine, make sure it says “directQuarantine licenses”.  If not contact your sales rep.

  • Failure to handshake:  On first statup, modusGate will send a handshake email to the user’s mailbox that _should_ be picked up by directQuarantine.  Sometimes that handshake email doesn’t make it to their inbox (it’s deemed as junk so sent to Junk Mail folder for instance, or some other third-party tool intercepted the message).  You can workaround that by forcing an authentication (see below).
  • A bug – in those cases, if points 1, 2 and 3 fail – you should escalate to our support team with the log files (see below). 

 

 

Resolution:     


1)   Get the logs:

  • First, before calling the support team or emailing support, try getting the direct Quarantine log file.
  • Usually you will find the log file under C:\users\<username>\appdata\local\vircom\directQuarantine (folder).
  • Locate the files called vircom.dQ.Client.Log and vircom.dQ.Client.config.
  • Zip them up and keep them handy when you open the ticket with support, email it to them as soon as you have a ticket with the support team.


2)   Force Authentication:

  • Get on the affected desktop and force an authentication.
  • Press down on the Left-CTRL and Left-SHIFT buttons on the keyboard while you click on the little blue envelope icon in the direct quarantine toolbar.

  • A pop-up should appear:



  • Put in the users email address and windows password.
  • The toolbar will be enabled.
9.2. How-To: Enable additional logging for Direct Quarantine
Product: Direct Quarantine

Version & Build: All

 

 

It is required at times that Admins need go login to the modusGate server to verify Direct Quarantine logging information. However by default the logging information is very little or insufficient. The steps below will show how an administrator can enable intensive logging for Direct Quarantine.

 

 

Solution:

   1- Ensure that you are able to login to the modusGate server with Administrative privileges.

   2- Locate the Direct Quarantine root installation folder usually located under "\Vircom\modusGate\directQuarantine Server"

   3- Locate a file named log4net.config and open it notepad.

    4- On line 31 of the file the following string is stated "<level value="ERROR" />

    5- This means that the logs will only display error only if reported thus leaving out any other options such as INFO, WARNINGS, FATAL...etc.

    6- Simply change the value from ERROR to ALL in capital letters. this is show all logging in the log files.

    7- Save the file and restart the modus Direct Quarantine service so that it will take effect.

    8- Once done the logs can be view under  \Vircom\modusGate\directQuarantine Server\Log" folder in extensive details from who logged in to app crashes... etc.

 

 

 

10. modusMail & modusGate Technical Information
10.1. Documentation & Release Information
10.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. 

10.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.


 

 

  
10.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.


 
 


10.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).

10.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.


10.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.


10.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.


10.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.







 


 

10.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. 

10.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.


 

 

  
10.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.


 


10.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).

10.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.


10.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.


10.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.


10.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.







 


 

10.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. 

10.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.


 

 

  
10.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.


 


10.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).

10.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.


10.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.


10.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.


10.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.







 


 

10.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. 

10.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.


 

 

  
10.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.


 


10.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