1. modusCloud
1.1. Archive
1.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.

 


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

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

 

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

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

 


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

 

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


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


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

 

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

 

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

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

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

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

 

 

 

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

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

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

 

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

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

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

 

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

 


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

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

 

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


 

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

 

  

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