Page 3 of 20
Knowledge Base Articles
When messages are DKIM signed using the "simple" Header Canonicalization Algorithm, the message headers must not be modified when the message transits intermediate mail servers in order for the DKIM verification to pass.
If the DKIM signed messages are relayed via a mail gateway it is preferable to use the "relaxed" Header Canonicalization Algorithm which is more tolerant to common in-transit modifications like white space replacement and line wrapping.
This article describes how to access Axigen's Domain Contacts using Mozilla Thunderbird and the Sync Kolab add-on.
Axigen versions starting with 9.0 address this issue by limiting the attachment types for which the in-browser preview is available.
For Axigen 8.x versions, we strongly recommend you to download & apply the patch below.
MIMEDefang includes in the default configuration a filter that rejects email attachments by file extension. This article describes how to integrate Axigen with MIMEDefang with the purpose to block such email attachments.
Email messages sent with Microsoft Outlook sometimes use the Rich Text format, or TNEF format. Such messages, when read using other email clients, contain a single attachment named winmail.dat, and any files that the sender may have attached to the message cannot be opened. This article describes how to integrate Axigen with MIMEDefang with the purpose to convert such attachments to a readable format.
This article describes the method to delete all messages from the Axigen queue matching a pattern.
This articles details on how to set specific banners for the SMTP/IMAP/POP3/IMAP Proxy/POP3 Proxy services.
This article describes two methods of migrating users from ATMail to Axigen: automatic and manual migration.
When purchasing a signed certificate from a CA a CSR file must be exported.
This article provides a brief description of the Spam Thresholds.
This article contains the procedure which explains how to configure an Axigen Mail Server as a log server. This procedure contains 2 parts, first one explaining the steps used to configure Axigen as a log server and the 2nd part explain how to configure a service for Axigen Mail Server to log on a remote host.
It is assumed that you have two Axigen services installed and running, one represents the actual mail server and the other one will be used as log server.
For debugging purposes it is necessary that you inform the support team of the exact Axigen version you have running.
Starting with Axigen 7.5 the DomainKeys services are incorporated in Axigen service itself. Support for the DomainKeys through the 'axigenfilters' service has been removed starting with Axigen 7.6.
Therefore, it isn't necessary to start the 'axigenfilters' service anymore for benefiting from DomainKeys services.
In order to use the internal DomainKeys services, SMTP filtering rules will need to be configured in your Axigen configuration for using DomainKeys signing and verifying.
This article describes how you can create a chart to display the configured parameters in a week-wide representation.