DKIM adds a cryptographic signature to outgoing messages and publishes a public verification key in DNS. SiteWorx can manage signing for its hosted mail service, while external mail providers use their own selectors and keys.
IN THIS ARTICLE
Check access and requirements
Identify the service that actually sends your mail and the authoritative DNS provider. Preserve existing selectors used by other legitimate sending platforms. A DKIM public key may be published; the private signing key must remain protected.
01 Enable and publish SiteWorx domain signing records
- Open Administration > Mail Options > DKIM and locate the intended domain.
- Use the add action to enable signing through the available form. Review its testing-mode choice and save the intended setting.
- Inspect the resulting selector and public DNS record. If DNS is hosted elsewhere, publish the exact public record at that provider rather than assuming a local zone change is visible.
- Send a message through the actual SiteWorx mail submission path to an external mailbox. Inspect Authentication-Results for the DKIM result and signing domain.
- Repeat the test for website-generated mail if it follows another route, and keep separate external-provider selectors where required.
Confirm the expected result
The receiving service should verify the signature against the published public key. Check that the signing domain is appropriate for your DMARC policy and visible From address.
Resolve setup problems
A missing selector, truncated TXT value, stale DNS or a message modified after signing can cause failure. Do not repeatedly delete and regenerate keys while troubleshooting; that can invalidate messages still in transit and complicate diagnosis.
Does DKIM encrypt the message?
No. It signs selected headers and the message body for verification. Transport encryption and end-to-end message encryption are separate protections.