|
⚠️ Feature available upon request Sender domain customization is available for eligible customers. Contact your Jint account manager to get started. |
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
- Why use a custom domain?
- How does it work?
- What your IT team needs to do
- What your content creators need to do
- Setup process
- If you encounter sending issues
- Frequently asked questions
1. Why use a custom domain?
-
Your recipients immediately recognize your organization. An email from
newsletter@yourcompany.cominspires 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.iomay be blocked. Sending from your own domain solves this issue.
2. How does it work?
When the feature is enabled for your account:
- Jint creates a sending subdomain linked to your domain (for example
newsletter.yourcompany.com). - Jint generates the DNS records to add to your domain configuration and provides them to your IT team.
- Your IT team adds these records to your DNS provider.
- Jint validates the configuration and activates it.
- 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).
|
💡 Good to know If your domain validation fails at send time, the send is blocked and an error message appears on your dashboard. Jint never silently falls back to |
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)
|
⚠️ Note on strict DMARC alignment If your organization enforces strict DMARC alignment, the sender address must exactly match the sending subdomain — for example |
Technical Glossary
| Term | What it is |
|---|---|
| Sender domain | The part after the @ in your sending address. In newsletter@yourcompany.com, it is yourcompany.com. |
| Subdomain | A prefix attached to your main domain, reserved for a specific use. Jint usually configures a subdomain dedicated to sending newsletters, for example newsletter.yourcompany.com. |
| Subdomain for links | If your newsletters contain links, these can be routed through a dedicated subdomain (e.g., newsletterlinks.yourcompany.com). |
| DNS record | An entry in your domain’s configuration that tells mail servers how to handle your emails. |
| CNAME | A type of DNS record that redirects your subdomain to Jint’s sending infrastructure. |
| TXT | A type of DNS record that publishes your authentication policies (SPF, DMARC). |
| DKIM | A security mechanism that adds a digital signature to each email, proving it comes from an authorized source. |
| SPF | A policy listing the servers authorized to send emails on behalf of your domain. |
| DMARC | A policy that tells recipient servers what to do with an email that fails DKIM or SPF checks: ignore it, mark it as spam, or reject it. DMARC can use strict or relaxed alignment, which affects how sending via subdomains is evaluated. |
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:
- Request the feature — Contact your Jint account manager or support team.
-
Define the configuration — The Jint team agrees with you on the subdomain and exact sender address (e.g.,
newsletter.yourcompany.comandnewsletter@yourcompany.com). - Receive the DNS records — Jint provides you with the records to add.
- Your IT team adds them to your DNS provider.
- Confirm — Your IT team informs Jint once the records are in place.
- Jint validates and activates — Validation can take up to 48 hours (DNS propagation).
- 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:
| Error message | Likely cause | What to do |
|---|---|---|
| Send failed: your custom domain is not responding. Contact your Jint administrator to resolve this issue. | DNS records have been deleted, modified, or expired. | Ask your IT team to verify that the DNS records are still in place. DNS changes can take up to 48 hours to propagate. If everything looks correct, contact Jint support. |
| Send failed: no sender address is configured. Contact your Jint administrator to resolve this issue. | Configuration is incomplete on the Jint side. | Contact your Jint CSM or support team to finalize the setup. |
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.
Comments
0 comments
Please sign in to leave a comment.