- About the Kaspersky Secure Mail Gateway
- Application licensing
- About the End User License Agreement
- About the license
- About the license certificate
- About the key
- About the key file
- About the activation code
- About the subscription
- About data provision
- KSMG modes based on the license
- Adding an activation code
- Adding a key file
- Removing a key
- Monitoring license key status
- Configuring warnings about upcoming license key expiration
- Purchasing a license
- Renewing a license
- Scaling KSMG
- Application installation and setup
- Creating a virtual machine
- Starting the Setup Wizard
- Step 1. Selecting the language to display the End User License Agreement and the Privacy Policy in
- Step 2. Reviewing the License Agreement
- Step 3. Viewing the Privacy Policy
- Step 4. Transferring data to the hard drive
- Step 5. Configuring the domain name of the virtual machine
- Step 6. Beginning the configuration of network adapters
- Step 7. Configuring the receipt of network settings via DHCP
- Step 8. Configuring static network settings
- Step 9. Completing the configuration of network adapters
- Step 10. Editing the network settings of a cluster node
- Step 11. Setting the administrator password
- Step 12. Finishing the Setup Wizard
- Removing the application
- KSMG interface
- Getting started with the application
- Integration of KSMG into the corporate mail infrastructure
- Monitoring of application operation
- General protection settings
- About computer protection against certain legitimate applications
- Configuring the Anti-Virus module
- Configuring link scanning
- Configuring the Anti-Spam module
- Configuring the Anti-Phishing module
- Configuring Content Filtering
- Configuring external services
- Preparing to configure SPF and DMARC Mail Sender Authentication for outgoing messages
- Configuring the addition of X-headers to messages
- Using message processing rules
- Viewing the rule table
- Configuring rule table display
- Message processing rule configuration scenario
- Creating message processing rules
- Configuring Anti-Virus protection
- Configuring link scanning
- Configuring Anti-Spam protection
- Configuring Anti-Phishing protection
- Configuring Content Filtering
- Enabling or disabling Content Filtering in rule settings
- Configuring Content Filtering
- Creating a Content Filtering expression
- Creating a Content Filtering condition
- Enabling, disabling, or deleting expressions
- Enabling, disabling, or deleting conditions
- Configuring the final action to take on a message
- Mail Sender Authentication
- Notification settings for message scan events
- Adding a Warning about insecure message
- Adding email disclaimers
- Configuring KATA protection
- Examples of message processing rule configuration
- Dictionaries
- Viewing rule information
- Enabling and disabling a message processing rule
- Changing rule settings
- Deleting message processing rules
- Allowlists and denylists
- Managing the cluster
- Creating a new cluster
- Viewing the cluster node table
- Configuring the display of the cluster node table
- Viewing information about a cluster node
- Adding a node to the cluster
- Modifying node settings
- Removing a node from a cluster
- Changing the role of a node in a cluster
- Deleting the cluster
- Restarting a cluster node
- Managing the SSL certificate of the cluster node
- Checking data integrity
- Modifying the network settings of a cluster node
- Managing user accounts and roles
- Backup
- Configuring Backup settings
- Configuring personal Backup
- Viewing the table of objects in Backup
- Configuring the display of the table of objects in Backup
- Filtering and finding messages in Backup
- Viewing information about a message in Backup
- Viewing a message in Backup
- Viewing a message in personal Backup
- Viewing the sending history of a message in Backup
- Sending messages from Backup
- Sending messages from personal Backup
- Deleting a message from Backup
- Sending or deleting a group of messages in Backup
- Downloading a message from Backup
- Backup digest
- Event log
- Viewing the event log
- Configuring event table display
- Filtering email traffic processing events
- Filtering application events
- Viewing information about email traffic processing events
- Viewing information about an application event
- Application event types
- Exporting the event log
- Configuring the event log
- Message queue
- Reports
- Configuring date and time
- Configuring the proxy server connection settings
- Updating KSMG
- Upgrading KSMG to version 2.1
- Installing the ksmg_upgrade_2.1.0.7854_openssh_cve_2024_6387
- Updating KSMG databases
- Exporting and importing settings
- Participating in Kaspersky Security Network and using Kaspersky Private Security Network
- Integration with an external directory service
- Creating a keytab file
- Adding a LDAP server connection
- Deleting a LDAP server connection
- Modifying LDAP server connection settings
- Configuring the schedule of synchronization with the Active Directory domain controller
- Manually starting synchronization with the Active Directory domain controller
- Enhancing the security of a LDAP server connection
- KATA protection
- Integration with a single KATA server
- Integration with multiple KATA servers
- Creating a configuration file for the local balancer
- Configuring and running the local balancer on a cluster node
- Adding a KATA server
- Configuring KATA protection settings
- KATA integration dashboard
- Adding, modifying, and deleting IP addresses of KATA servers
- Disabling KATA integration
- Managing the application over SNMP
- Email notifications of the application
- Configuring notifications about application events
- Configuring notifications about bounce messages
- Configuring notifications about message processing rules triggering
- Configuring notification templates
- Using macros in notification templates
- Adding a unique message ID to the notification
- Configuring the address for messages sent by the application
- Authentication using the single sign-on technology
- Connecting to cluster nodes over the SSH protocol
- Configuring MTA settings
- DKIM signature for outgoing messages
- Configuring TLS for KSMG
- Domains and configuration of email routing
- Publishing application events to a SIEM system
- Contacting Technical Support
- Glossary
- Advanced persistent threat (APT)
- Anti-Phishing
- Anti-Spam
- Anti-Spam Quarantine
- Anti-Virus
- Backup
- Backup digest
- BEC attack
- Certificate fingerprint
- Cluster
- Content Filtering
- Content Filtering condition
- Content Filtering dictionary
- Content Filtering expression
- Control node
- Directory service
- DKIM Mail Sender Authentication
- DMARC Mail Sender Authentication
- Email notification
- Heuristic analysis
- Kaspersky Anti Targeted Attack Platform
- Kaspersky Private Security Network
- Kaspersky Security Network (KSN)
- Kerberos authentication
- Key file
- Keytab file
- LDAP
- Malicious links
- Moebius service
- MTA
- NTLM authentication
- Personal user
- Phishing
- Privileged user
- PTR record
- Reputation filtering
- SCL rating
- Secondary node
- Service Principal Name (SPN)
- SIEM system
- SMTP verification
- SNMP agent
- SNMP trap
- Spam
- SPF Mail Sender Authentication
- Spoofing
- TLS encryption
- Update source
- Virtual machine
- Information about third-party code
- Trademark notices
Monitoring application database status
To track down application database update problems, you can view summary information about the database status on all cluster nodes in the Databases update dashboard in the Nodes section.
The following statuses are available:
- No errors means all application databases are up to date, and the update process was completed without errors.
- Databases are out of date means that traffic processing was not stopped, and at least one of the following events occurred:
- Anti-Virus databases have not been updated for a period of 24 hours to 7 days
- Anti-Spam databases have not been updated for a period of 5 to 24 hours
- Anti-Phishing databases have not been updated for a period of 48 to 72 hours
- Databases are obsolete means that traffic processing was not stopped, and at least one of the following events occurred:
- Anti-Virus databases have not been updated for over 7 days
- Anti-Spam databases have not been updated for over 24 hours
- Anti-Phishing databases have not been updated for over 72 hours
- Errors means one of the following events occurred:
- Databases for one or more scanning modules are missing
- Traffic processing is stopped on one or more cluster nodes
- One or more cluster nodes are unavailable, application database status information cannot be obtained.
The number of cluster nodes on which the last update task returned an error is displayed under the horizontal line in the Last update errors field.
To view detailed information about the status of application databases on each cluster node:
click View details in the Databases update pane to go to the Settings → External services → Database update → Update status section.
The workspace displays the table of cluster nodes containing information about application databases for every scanning module:
- IP address:port is the IP address and port of the cluster node.
- Anti-Virus is the current status of the Anti-Virus databases.
- Anti-Phishing is the status of the Anti-Phishing module databases.
- Anti-Spam is the status of the Anti-Spam module databases.
- Update status is the status of the last update task:
- If the task was completed successfully, the completion time of the task is displayed.
- If the task returned an error, the launch time of the current task is displayed as well as the time of the last successful database update (if any).
- If the task has never been launched after the application was installed or if the cluster node is unavailable, a dash is displayed.
- If the task is in progress, its completion percentage is displayed.
This table is displayed if the user has View nodes information and/or Create/edit/delete nodes permissions, and View settings and/or Edit settings permissions.
You can also view information about the status of application databases in the information window of each cluster node.