Setting up sending address

Now that emails are arriving in Jelly, you need to be able to reply.

If you’re not using Gmail to send messages, this requires some configuration so that Jelly can prove to the internet that it is authorized to send from your address.

There are two options:

  • Domain verification (strongly recommended) — verify your entire domain via DNS
  • Single-email verification (fallback) — verify just one address via email confirmation

Domain verification is the best choice if you have access to your domain’s DNS settings. It provides:

  • Better deliverability — emails are properly authenticated and less likely to land in spam
  • Cleaner appearance — no “sent via” notices in recipients’ email clients
  • Multiple addresses — once your domain is verified, you can send from any address at that domain

What you’ll need:

  • Access to wherever your domain’s DNS is managed (your domain registrar, hosting provider, or a service like Cloudflare)
  • The ability to add TXT and CNAME records

Start Domain Verification

  • In Jelly, go to Email Setup
  • Click Connect a team address
  • Enter the email address you want to send from (e.g., support@yourcompany.com)
  • Choose Domain verification

Jelly will show you the DNS records you need to add. Keep this page open — you’ll need to copy these values.

Understand What You’re Adding

You’ll add two DNS records:

DKIM Record (TXT type)

DKIM (DomainKeys Identified Mail) cryptographically signs your outgoing emails.

Record example:

Type: TXT Name/Host: something like 20250819154921pm._domainkey (Jelly provides this) Value: a long string starting with k=rsa; p=… (Jelly provides this)

Return Path Record (CNAME type)

Tells receiving servers where to send bounce notifications.

Record example:

Type: CNAME Name/Host: something like jelly-bounces (Jelly provides this) Value: via.letsjelly.com

Add the DNS Records

Log into wherever your domain’s DNS is managed. Common places:

Domain registrars: GoDaddy, Namecheap, Google Domains, Hover, Porkbun

DNS services: Cloudflare, AWS Route 53, DNSimple, DigitalOcean

Hosting providers: If you have web hosting, DNS might be there

To add the TXT record:

Add a new record of type TXT

For the name/host field, enter the value from Jelly (just the part before your domain)

For the value/content field, paste the long string from Jelly

Save

To add the CNAME record:

Add a new record of type CNAME

For the name/host field, enter the value from Jelly

For the target/value field, enter via.letsjelly.com

Save

A common issue: Some DNS providers require a trailing dot after values (via.letsjelly.com.) and some don’t accept it. If verification fails, try adding or removing the dot.

Verify in Jelly

After adding both records, return to Jelly’s Email Setup.

  • Click Check verification…
  • DNS changes usually propagate quickly — often within seconds or minutes. If verification fails:
    • Wait a few minutes and try again
    • Double-check that you copied the values exactly
    • Use a tool like DNS Checker to see if your records are visible globally

Option B: Single-Email Verification (Fallback)

If you can’t access your domain’s DNS settings (maybe someone else manages your domain, or you’re using a service that doesn’t give you DNS access), you can verify a single email address instead.

The tradeoff: Emails sent this way will show a “sent via” notice to some recipients. In Gmail, for example, the recipient might see:

From: support@yourcompany.com via letsjelly.com

This works perfectly fine — your emails will be delivered, and recipients can reply normally. But domain verification provides a cleaner experience.

Start Single-Email Verification

  1. In Jelly, go to Email Setup
  2. Click Connect a team address
  3. Enter the email address you want to verify
  4. Choose Single email verification

Confirm Verification Email

  • Jelly will send a verification email to that address
  • Since you’ve already set up forwarding, the verification email will arrive in Jelly
  • Open the email and click the confirmation link

After Verification

  • Once confirmed, you can send from that address
  • To send from another address on the same domain, you must verify each address separately unless the domain is verified

Testing the Complete Setup

With forwarding and verification both complete, let’s make sure everything works:

  1. Test receiving — From a personal email account, send a message to your team address. It should appear in Jelly within seconds.
  2. Test sending — In Jelly, reply to that test message and send it.
  3. Check the result — In your personal email, verify that:
    • The reply arrived
    • The “From” address shows your team address (not a Jelly address)
    • If you used domain verification, there’s no “sent via” notice
    • You can reply to it normally

If all of that works, you’re all set.

Adding More Addresses

Once your domain is verified, adding more addresses at that domain is easy — no additional DNS setup required. Just go to Email Setup, add the new address, and Jelly recognizes that the domain is already verified.

For addresses on a different domain, you’d need to verify that domain separately.

For more details, see Adding More Addresses.

Troubleshooting

Forwarding Issues

Emails not arriving in Jelly:

  • Verify forwarding is enabled and saved in your email provider
  • Check you’re using the correct Jelly forwarding address
  • Look in Jelly’s spam folder
  • Some providers require a confirmation step — check if you missed it
  • Try sending a simple plain-text test email

Provider requires confirmation but email isn’t arriving:

If your email provider sends a confirmation email and it’s not appearing in Jelly, the forwarding might not be active yet. Check if there’s a confirmation link you need to click in your original inbox first.

DNS Verification Issues

Verification keeps failing:

  • Copy the values directly from Jelly — don’t retype manually
  • Check for trailing dots (try with and without)
  • Make sure you’re adding records to the correct domain
  • Wait 10–15 minutes for DNS propagation
  • Use an online DNS checker to verify your records are visible

Don’t know where DNS is managed:

Try logging into your domain registrar first. If DNS isn’t there, check your hosting provider. If you use Cloudflare or a similar service, DNS is managed there.

Sending Issues

Emails going to spam:

  • If using single-email verification, consider switching to domain verification
  • Make sure both DNS records are correct
  • Check your domain doesn’t have conflicting email authentication records
  • Give it some time — new senders sometimes need to build reputation

“Sent via” notice showing:

This is expected if you used single-email verification. To remove it, switch to domain verification (requires DNS access).