- Axigen Binary File
- Axigen Working Directory
- Axigen Configuration File (axigen.cfg)
- The mqview Tool
- Message Flow Policies (smtpFilters.script)
- Securing SMTP Services
- SPF, DKIM & DMARC
- A-grade SSL Listeners
- Configuring IPv6
- Configuring the WebMail & WebAdmin Discovery by Search Engines
- Configuring the WebAdmin Customer Reference as Read Only
- Axigen Indexes
- Sender Rewriting Scheme (SRS)
On the Axigen machine
Add an entry similar with:
In order to get <content_of_public_key_pem_file_on_1_line>, you could run the following command:
Replace the name of the .pem file with the one you actually used.For the more experience, the final
grep -v AAAAAAAAAA has the purpose of adding a new "
\n" to wrap the prompt on a new line. The string
AAAAAAAAAA is highly unlikely to be present in the public key.
If bind DNS server is used, you should split the 'p' value on multiple lines as bind accept only 256 characters per line
The "p" value need to be split to 256 characters per line.
Here's an example on how to generate this on Linux, using your existing public key:
Check if the DNS entry has been propagated with the following command:
dig +short txt 2015._domainkey.domain1.com @220.127.116.11
For incoming messages
Acceptance & Routing → Advanced Settings Rule name: "Check_DomainKeys_and_DKIM"
For signing outgoing messages
Acceptance & Routing → Advanced Settings Rule name: "DomainSign-domain1_com"