Setting up with Exchange/Outlook
If your organisation uses Microsoft 365 (formerly Office 365) or runs an on-premises Exchange server, this guide will walk you through connecting your email to Jelly.
This setup is more involved than Gmail because it typically requires an administrator and involves configuring DNS records. We'll explain each step and why it's necessary.
The process has two parts:
Set up forwarding at the server level so incoming emails arrive in Jelly
Verify your domain with DNS records so Jelly can send replies on your behalf
Before You Start: What You'll Need
For forwarding setup:
An Exchange administrator (someone with access to the Exchange Admin Center or Exchange Management Shell)
If you're not an admin yourself, you'll need to share these instructions with your IT team
For domain verification:
Access to your domain's DNS settings (usually at your domain registrar or a service like Cloudflare)
The ability to add TXT and CNAME records
If you're not sure about any of this, loop in your IT team from the start — they'll likely need to be involved for the forwarding piece.
Part 1: Setting Up Forwarding
Important: forwarding configured in Outlook or at the mailbox (user-level forwarding) won't work correctly with Jelly.
Why user-level forwarding doesn't work:
Outlook-level forwarding creates a new email that quotes the original message (a wrapped/forwarded message).
Jelly needs a server-level copy of the original email with intact headers so threading and replies work correctly.
Server-level forwarding requires Exchange administrator access. If you're not an admin, ask your IT team to perform the steps below.
The configuration can be done either through the Exchange Admin Center (web interface) or via PowerShell. Use the stepper for the overall process; within options, steps are listed as well.
Enable server-level forwarding (overview)
Choose one of the options below to configure server-level forwarding:
Option A: Exchange Admin Center (web interface)
Option B: Exchange Management Shell (PowerShell)
Forwarding should deliver an exact copy of incoming emails to Jelly:
Jelly forwarding address:
[email protected]
Recommended: keep a copy in the original mailbox (
DeliverToMailboxAndForward $true) as a backup.
Option A: Exchange Admin Center (Web Interface)
Follow these steps in the Exchange Admin Center:
Sign into the Exchange Admin Center
Microsoft 365: admin.microsoft.com → Admin centers → Exchange
On-premises: use your organisation's EAC URL
Navigate to Recipients → Mailboxes
Select the mailbox to forward (e.g., [email protected])
Click Edit (or double-click the mailbox)
Go to Mailbox features (name may vary by Exchange version)
Find Mail Flow and click View details
Check Enable forwarding
Enter the Jelly forwarding address:
[email protected]Check Deliver message to both forwarding address and mailbox (recommended)
Click OK and then Save
Note: Some EAC versions only allow forwarding to internal addresses. If you cannot enter an external address, use PowerShell (Option B).
If forwarding doesn't work
Exchange environments may block external forwarding for security. If forwarding fails, check:
Remote Domains settings (controls forwarding outside the organisation)
Mail flow rules (might block or redirect forwarding)
Outbound spam filter policies (Microsoft 365 may block automatic forwarding)
Ask your Exchange admin to review these settings or contact Microsoft support if needed.
Testing forwarding
Send a test email to your Exchange mailbox from an external account (Gmail, etc.)
Check Jelly — the email should appear within a few seconds
Open the email in Jelly and confirm it displays the original (not wrapped)
If the email arrives wrapped (shows "---------- Forwarded message ----------"), user-level forwarding is still active. Disable any Outlook rules or mailbox-level forwarding and ensure only server-level forwarding is used.
Part 2: Verifying Your Domain for Sending
Microsoft doesn't provide a way for third-party apps to send through Exchange in the same way Gmail allows. Jelly sends replies using Postmark, so you must verify your domain by adding DNS records authorising Postmark to send on your behalf.
Why DNS verification matters:
Recipient servers check whether the sending server is authorised for your domain to prevent spoofing and spam.
The DNS records tell the world that Postmark (Jelly's delivery service) is allowed to send from @yourcompany.com.
Step 1: Start Domain Verification in Jelly
In Jelly, go to Email Setup (click your profile photo → Email Setup)
Click Add Email Address
Enter the email address you want to send from (e.g., [email protected])
Choose Verify Domain
Jelly will display the DNS records you need to add. Keep this page open to copy values.
Step 2: Understanding the DNS Records
Jelly will ask you to add two DNS records:
DKIM Record (TXT)
Purpose: Cryptographically signs your emails to prove authenticity and integrity.
Example fields Jelly provides:
Type: TXT
Host/Name:
20250819154921pm._domainkey(copy exactly from Jelly)Value:
k=rsa; p=MIGfMA0GCS...(a long string Jelly provides)
Return Path Record (CNAME)
Purpose: Directs bounce notifications (delivery failures) to Postmark's servers.
Example fields Jelly provides:
Type: CNAME
Host/Name:
jelly-bounces(copy from Jelly)Value/Target:
via.letsjelly.com
Step 3: Add the DNS Records
Add the records at wherever your DNS is managed (domain registrar, hosting provider, or dedicated DNS service like Cloudflare or AWS Route 53).
Adding a TXT record:
Add new record → type TXT
Enter hostname (copy exactly from Jelly)
Enter the value (copy exactly from Jelly)
Save
Adding a CNAME record:
Add new record → type CNAME
Enter hostname (copy from Jelly)
Enter target/value:
via.letsjelly.comSave
Common gotcha: Some DNS providers require a trailing dot on hostnames/values (via.letsjelly.com.). If verification fails, try adding or removing the trailing dot.
Step 4: Complete Verification
After adding both DNS records, return to Email Setup in Jelly
Click Verify Domain
DNS changes usually propagate in minutes but can take longer (rarely a few hours). If verification fails:
Copy/paste values exactly from Jelly (do not retype)
Wait a few minutes and retry
Use a tool like https://dnschecker.org to check propagation
Once verified, you can send from any address on that domain without adding more DNS records.
Testing the Complete Setup
After forwarding and domain verification:
Test receiving: send an email to your Exchange mailbox from an external account
Verify it appears in Jelly and displays correctly
Test sending: reply from Jelly
Confirm the reply:
Arrived at your personal email
Shows the correct From address ([email protected])
Can be replied to normally
If both receiving and sending work, setup is complete.
Troubleshooting
Emails Not Arriving in Jelly
Check forwarding configuration:
```powershell Get-Mailbox -Identity "[email protected]" | Format-List Forward* ``` - Ensure it's server-level forwarding. If emails are wrapped with "---------- Forwarded message ----------", user-level forwarding is active—disable Outlook rules and mailbox-level forwarding. - Check for forwarding blocks in Remote Domains, mail flow rules, and outbound spam filter policies.
DNS Verification Failing
Copy/paste values directly from Jelly (don't retype).
Try adding or removing a trailing dot on hostnames/values.
Wait 10–15 minutes and retry—DNS propagation can take time.
Use an online DNS checker to verify records are visible.
Sent Emails Going to Spam
Ensure both DKIM (TXT) and return-path (CNAME) records are correctly added.
Check for conflicting DKIM or email authentication records on your domain.
New domains may need time to build sending reputation—give it some time.
Next Steps
Add more addresses: Set up additional email addresses at your domain → Adding More Addresses
Learn the inbox: See how Jelly organises conversations → How the Inbox Works
Set up rules: Automatically route and organise emails → Rules
If you need help at any point:
Last updated