By default, newsletters sent via Jint come from the address newsletter@jint.io. This feature allows you to use an address from your own domain instead, for example newsletter@yourcompany.com. This improves deliverability, reduces the risk of being reported as a phishing attempt, and allows recipients to immediately recognize your organization.

Table of Contents

1. Why use a custom domain?
2. How does it work?
3. What your IT team needs to do
4. What your content creators need to do
5. Setup process
6. If you encounter sending issues
7. Frequently asked questions

1. Why use a custom domain?

• Your recipients immediately recognize your organization. An email from newsletter@yourcompany.com inspires more trust than an unfamiliar address, which encourages opens.
• Reduces phishing alerts and reports. Security filters and your recipients are less likely to report your emails as phishing attempts.
• Improves deliverability and reduces the risk of being marked as spam. Mailboxes and security tools trust known domains more.
• DMARC compliance. If your organization enforces a strict DMARC policy, emails sent from jint.io may be blocked. Sending from your own domain solves this issue.

2. How does it work?

When the feature is enabled for your account:

1. Jint creates a sending subdomain linked to your domain (for example newsletter.yourcompany.com).
2. Jint generates the DNS records to add to your domain configuration and provides them to your IT team.
3. Your IT team adds these records to your DNS provider.
4. Jint validates the configuration and activates it.
5. From that point on, each newsletter is cryptographically signed (DKIM) and routed from your domain — with no action required from you at send time.

Before each send, Jint performs a pre-send domain validity check. If this check fails, the send is blocked (see section If you encounter sending issues).

3. What your IT team needs to do

The technical setup is done in collaboration with the Jint operations team. Your IT team will need:

• Access to the DNS settings of your domain (via your registrar or DNS provider: OVH, Cloudflare, Azure DNS, Amazon Route 53, GoDaddy, etc.)
• The ability to add CNAME and TXT records
• Knowledge of your organization’s DMARC policy (strict or relaxed alignment)

Technical Glossary

4. What your content creators need to do

Nothing. Once the setup is active, all newsletters will automatically be sent from your custom domain. The way you create, schedule, and send a newsletter in Jint does not change.

The only visible difference: the sender address shown to your recipients will be yours, not newsletter@jint.io.

If there is a sending error, a message will appear on the dashboard — see the section If you encounter sending issues below.

5. Setup process

The setup is managed by the Jint operations team. Here are the steps:

1. Request the feature — Contact your Jint account manager or support team.
2. Define the configuration — The Jint team agrees with you on the subdomain and exact sender address (e.g., newsletter.yourcompany.com and newsletter@yourcompany.com).
3. Receive the DNS records — Jint provides you with the records to add.
4. Your IT team adds them to your DNS provider.
5. Confirm — Your IT team informs Jint once the records are in place.
6. Jint validates and activates — Validation can take up to 48 hours (DNS propagation).
7. It's active — Your next send automatically uses your custom domain.

Estimated timeline: 5 business days between request and activation, assuming your IT team acts promptly.

6. If you encounter sending issues

If your domain validation fails, the send is blocked and an error message appears on your dashboard. Here are the two possible errors and the actions to take:

7. Frequently Asked Questions

Can I use my primary domain (e.g., newsletter@yourcompany.com) instead of a subdomain?

It depends on your DMARC policy. With relaxed DMARC alignment, it is possible. With strict alignment, a subdomain address will be required (e.g., newsletter@newsletter.yourcompany.com). The Jint team will advise you during setup.
 

What if my organization has a strict DMARC policy?

With strict DMARC alignment, the sender address must exactly match the authenticated domain. In this case, Jint will configure a dedicated sending subdomain (e.g., newsletter@newsletter.yourcompany.com) to ensure compliance. The Jint team reviews your DMARC configuration during setup and recommends the best approach.
 

Can I have multiple different sender addresses?

Not in the current version. Only one sender address is configured per account. Support for multiple addresses may be available in a future release.

What happens if we stop using Jint Newsletter?

The Jint team will disable the dedicated subdomain configuration. This has no impact on your primary domain or other email services.

Is this setup self-service?

Not yet. The setup is currently performed by the Jint operations team. A self-service interface may be available in a future release.

Is our organization responsible for emails sent from our domain?

Yes. By sending from your own domain, your organization is the official sender. It is your responsibility to ensure your newsletters comply with applicable regulations (GDPR, CAN-SPAM Act, etc.). Jint acts as the sending infrastructure provider.

Have a question or want to enable this feature? Contact your Jint account manager or our support team.