In het Nederlands
How it works · Domain, DNS and mail

Interactive presentation · click anything for an explanation

From domain to ticket

Where does your mail actually go?

The addressMail inMail out
Speaker notes

A customer sends an email and a moment later there is a ticket in Odoo. In between is a chain almost nobody oversees: the domain, the address book, the mailbox, Odoo. This presentation walks that chain.

We use one image: an address and a mailroom. Three parts to hold on to: the address, mail in and mail out.

The whole picture

One address, two streams of mail.

The top shows who knows where everything lives. The bottom is the mail itself, coming in and going out again.

your registrationRegistrar
the signpostName servers
the address bookDNS at Cloudflare
Website
Mailboxes
Odoo
senderCustomer
address book lineMX record
catch-all and aliasesOdoo's mailbox
the front officeOdoo
SMTPSending server
recipientCustomer

If something goes wrong at the top, the bottom stalls.

Speaker notes

This is the picture to remember. The top lane is the address: the registrar holds your domain, the name servers point to the address book, and the address book says where the website, the mailboxes and Odoo live.

The bottom lane is the mail. A customer sends an email, the MX record shows the way to the mailbox, Odoo turns it into a record and sends an answer back through the sending server. The two dotted lines show where the lanes touch: the address book decides where mail goes and who may send.

01 · The address

You rent your domain. Who holds the key?

Three things that often get mixed up. Together they decide whether your address is really yours.

Your address

The domain

example.com. You rent it by the year. If you don't renew, it's gone.

Renting, not owning
Your registration

The registrar

Holds the domain for you: contact details, renewal and the transfer code

Who logs in here?
The signpost

The name servers

One setting at the registrar. They say who answers the questions about your domain.

They point to the address book

Requesting through Newway

You can request a domain through us. The price differs per extension, and some countries set their own conditions. Different per country

.com.nl.be.de.eu.fr

Watch out

Is the domain registered to a former employee or the previous web agency? Then they decide about your address.

Speaker notes

A domain is your address. You rent it from a registrar, by the year. The registrar records in whose name it is, when it expires, and issues the transfer code when you want to leave.

The name servers are one setting at that registrar. They point to the party that keeps the address book. You can request a domain through Newway. What it costs differs per extension, and some countries ask for something extra, such as a local address or an agreement with the registry.

The question to take away: in whose name is your domain registered? Often it is a former employee or a previous supplier.

01 · The address

The address book: each line answers one question.

A · CNAME
Where does the website live?example.com → 203.0.113.10 · www → example.com
address
CNAME
Where does Odoo live?portal.example.com → example.odoo.com
address
MX
Where does the mail come in?example.com → the mail provider
mail in
TXT · SPF
Which servers may send on our behalf?v=spf1 include:mailprovider include:_spf.odoo.com ~all
mail out
DKIM
How do you recognise our signature?odoo._domainkey → the public key
mail out
TXT · DMARC
What do you do with mail that doesn't check out?v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com
mail out

Where does mail for example.com go?To the mail provider.

Why at Cloudflare

A change is live in seconds.

You can see who changed what.

It puts a shield in front of your website.

Speaker notes

DNS is the address book of your domain. Each line is the answer to one question. Where does the website live. Where does the mail come in. Which servers may send on our behalf.

The animation on the right shows what happens thousands of times a day: a server asks a question and gets the answer back. Click a line to see what it does and what goes wrong when it is missing.

We keep the address book at Cloudflare. A change is live in seconds, you can see what was changed, and it does more than the address book alone. That is the next slide.

01 · The address

Cloudflare is also the doorman at the door.

All traffic to your website and Odoo passes a filter first. That is where we set who passes, who is slowed down and who stays out.

Visitorscustomers and colleagues
passes
Good botssearch engines, integrations
passes
AI crawlersallow, limit or block, per bot
you choose
Attackers and scrapersguessing, copying, flooding
stays out
behind the shieldWebsite and Odoo

It stops a lot, not everything. Above all it shows what is coming, so you can choose.

Speaker notes

Cloudflare is more than the address book. Because traffic to your website passes through it, we can set rules there. Four kinds of traffic.

Visitors pass. Good bots, like a search engine's, do too. AI crawlers are a choice: you can allow, limit or block them, per bot. And attackers and scrapers we stop or slow down before they reach the server or Odoo.

To be honest about it: it stops a lot, not everything. The gain is that you see what comes in and that you can act.

02 · Mail in

The mailbox: where your mail really sits.

One person's

Personal mailbox

sanne@example.com. Own login, own inbox.

A team's

Shared mailbox

info@ or support@. Several colleagues look in.

An extra name

Alias

An extra address that lands in an existing mailbox.

Where is the mailbox hosted?

Microsoft 365Odoo connects with OAuth
Google WorkspaceOdoo connects with OAuth
Mailbox at the registrarwith username and password

Give Odoo one mailbox of its own. All Odoo addresses are aliases on it.

Speaker notes

The address book says where mail should go. The mailbox is where it really sits. There are three kinds: a personal mailbox, a shared mailbox and an alias, an extra address on an existing mailbox.

Mailboxes are hosted at a mail provider, usually Microsoft 365 or Google Workspace. Odoo connects to both with OAuth: you give permission once and no password is stored in Odoo.

The advice: give Odoo one mailbox of its own and put every address Odoo uses on it as an alias. Then there is one place Odoo reads, and no person works in it.

02 · Mail in

Mail in: from email to ticket.

1The customerMails helpdesk@

A customer sends an email to helpdesk@example.com.

2The address bookMX shows the way

The customer's mail server reads the MX record and delivers to your mail provider.

3The mailboxOdoo's mailbox

helpdesk@ is an alias. The mail lands in Odoo's one mailbox.

4The front officeOdoo fetches

Every few minutes Odoo empties the mailbox.
fetchor forward

5The recordAddress decides

Odoo reads which address the mail was sent to and creates the right record.

The address decides the record

helpdesk@→ticket
sales@→lead
invoices@→vendor bill
Speaker notes

Now the route itself, step by step. A customer mails helpdesk@example.com. The customer's mail server asks the address book where the mail should go and delivers to your mail provider.

There, helpdesk@ is an alias on Odoo's mailbox. Odoo empties that mailbox every few minutes, over a secure connection. The other route is that the provider forwards to Odoo.

Then the most important part: Odoo looks at which address the mail was sent to. helpdesk@ becomes a ticket, sales@ a lead, invoices@ a vendor bill. The address decides the record.

02 · Mail in

The mailroom: where replies and returns come in.

In Odoo this setup is called the alias domain. It has three settings: the catch-all, the bounce and the default sender.

Replies

The catch-all

Every email from Odoo gets a reply address and its own number. When the customer replies, the reply falls back into the same record.

Returns

The bounce

Every email also gets a return address (Return-Path). If it doesn't arrive, the return message lands at Odoo. Odoo marks the email as not delivered and counts it against the contact.

Watch out. Never make the catch-all the same as info@ or the helpdesk alias. Every reply to every Odoo email then becomes a new ticket. catch-all at your mail provider is something else

Speaker notes

Odoo has a mailroom with two counters. The first is the catch-all: the central reply address. Every email Odoo sends carries a reply address and its own number. When the customer replies, Odoo knows from that number which record it belongs to.

The second counter is the bounce: return to sender. If the address doesn't exist, the return message comes to Odoo, which marks the email as not delivered. In Odoo all of this is set up in the alias domain.

The pitfall we often see: the catch-all has been made the same as info@ or the helpdesk. Then every reply to a quotation or invoice becomes a new ticket. And at a mail provider the word catch-all means something else: all mail to unknown addresses in one mailbox.

02 · Mail in

A ticket in four steps. Follow the envelope.

The customer's reply arrives in Odoo. Not in your colleague's Outlook.

Customer
Colleague
Ticket 1042 · Late delivery
Peter: Where is my order?
Sanne: It shipped today.
Peter: Thanks, it's here.
notified

The customer's email

FromPeter Jansen
Tohelpdesk@example.com
Number

Odoo sees the address helpdesk@ and creates ticket 1042.

Two buttons in the ticket

Send messagegoes as an email to the customer and the followers
Log notestays internal, the customer sees nothing

Sanne chooses Send message. A note would never reach the customer.

The email from Odoo

FromSanne (Example Ltd)
Topeter@customer.example
Reply toHelpdesk Example Ltd
Number<1042.b7c2@example.com>

For a ticket, the reply address is the helpdesk team's address.

The customer's reply

FromPeter Jansen
Tohelpdesk@example.com
In reply to<1042.b7c2@example.com>
Resultsame ticket, followers get a notification

Odoo recognises the number and puts the reply in the same ticket.

Speaker notes

This slide is interactive. Click steps one to four, or simply click through.

One: the customer mails helpdesk@ and Odoo creates a ticket. Two: the colleague answers from the ticket with Send message. Not with Log note, because that stays internal. Three: the email goes out. The reply address is the helpdesk team's address and the email has its own number. Four: the customer replies. Odoo recognises the number, puts the reply in the same ticket and the followers get a notification.

The lesson: the reply arrives in Odoo and not in the colleague's personal Outlook. That is exactly the point. Someone being ill or away doesn't leave a customer waiting.

03 · Mail out

Mail out: three routes to the outside.

the mail is readyOdoo
the inbox ofThe customer
For everyday business mailThrough Odoo itself

Included, little to set up. But a daily cap.

If your mail is already thereThrough Google or Microsoft

Odoo connects with OAuth and sends through their server. Daily caps here too.

For volume: newsletters, mailingsThrough a sending service

No cap getting in the way. On a Newway account: Mailjet (now), Resend and others.

What a sending service adds

No cap of so many emails per hour or per dayStatistics: delivered, opened, clickedHandling of returns and spam complaintsGuarding your domain's reputation
Speaker notes

Now the other direction. Odoo doesn't deliver mail itself, it hands it to a sending server. There are three routes.

Through Odoo itself: included and fine for everyday business mail. Through Google or Microsoft: Odoo connects to your mail provider and sends through their server. And through a sending service, for volume. Newway has its own accounts for that, through which we can route a customer's mail. Right now that is Mailjet, also Resend, and there are other providers such as Amazon SES, Brevo and Postmark.

What gets in the way most in practice are the caps: so many emails per hour or per day through Odoo itself or through Google and Microsoft. A sending service does not have that brake. It also does more than send. You see what was delivered, opened and clicked, it handles returns and spam complaints and guards your domain's reputation. That is why you choose it for newsletters and large mailings.

03 · Mail out

Whichever route you choose: three ticks on the envelope.

SPFThe server is on the listThe address book names the server you send with.
DKIMThe signature is validEvery email is signed and unaltered on the way.
DMARCThe policy is onYou say what happens to mail that doesn't check out.

Without the three ticks: a real chance of the spam folder.

Three ticks: the mail is trusted and arrives.

Inbox
Spam
Speaker notes

Whichever route you choose, the recipient asks three questions. Is the sending server on this domain's list? That is SPF. Is the signature valid? That is DKIM. And what does the domain owner want me to do with mail that doesn't check out? That is DMARC.

Click through and watch the ticks turn green one by one. Without ticks the envelope drops into the spam folder, and nobody tells you. With three ticks your mail is trusted.

All three live in the address book. That is why DNS belongs in this story.

03 · Mail out

Whose name is on the envelope?

Who is sending
No person

An automatic reminder or confirmation

There is no logged-in colleague. Odoo uses the default sender of the alias domain.

What the recipient sees

Your company name with a fixed address. Recognisable: every automatic email comes from the same sender.

Who is sending
sanne@example.com

Sanne sends a quotation

Sanne's address falls under the sender filter. The sending server may mail on behalf of example.com.

What the recipient sees

Sanne herself, with her own address. Personal, and the address matches the domain the mail comes from.

Who is sending
sanne.devries@gmail.com

Sanne has an address on another domain

Your server may not use that address. The recipient sees it as spoofing. Odoo rewrites it.

What the recipient sees

Sanne's name, with the company's fixed address behind it. The mail stays personal and still arrives.

Example Ltd
catchall@example.com
No person, so the fixed address
Sanne
catchall@example.com
example.com falls under the filter
Sanne
Sanne
catchall@example.com
gmail.com doesn't fit: Odoo rewrites

In all three the reply address points to Odoo. The reply comes back into the record.

Speaker notes

Whose name is on the envelope as the sender? That depends on who is sending. Click the three situations.

Odoo itself, for example an automatic reminder: the sender is the company's fixed address. A colleague with an address on your own domain: the colleague is on it, because the sending server may mail on behalf of that domain. A colleague with an address on another domain, such as gmail: Odoo rewrites the sender to the fixed address and puts the colleague's name in front. Otherwise the recipient sees it as spoofing.

In all three cases the reply address points to Odoo. So the reply always comes back into the record.

Who manages what

Who manages what? That decides what you can promise.

In one hand

  • A change in seconds
  • One point of contact
  • Someone oversees the whole

Spread across parties

  • Every change is an appointment
  • Waiting for someone else
  • Nobody oversees the whole

Five questions you can ask yourself

In whose name is the domain?
Who manages the name servers?
Are SPF, DKIM and DMARC right?
Which mailbox does Odoo read?
Where do returns end up?
Speaker notes

Finally the question that decides everything: who manages what. If domain, address book and mailbox are in one hand, a change takes seconds and someone oversees the whole. If they are spread out, every change is an appointment with another party.

Spread out is not wrong. It only means nobody can guarantee the chain works. During an outage everyone looks at the other.

Five questions you can ask today. If you can answer all five, you are in control.

To conclude
What you don't manage,
you can't guarantee.
The addressMail inMail out

Bring domain, address book and mailbox into one hand. Give Odoo one mailbox of its own.

Ask the five questions today. If you don't know the answer, you know where to start.

Follow us for new knowledgeLinkedInInstagramFacebook
Speaker notes

The main line in one sentence: what you don't manage, you can't guarantee. From domain to ticket is one chain, and it is as strong as the link nobody oversees.

The advice: bring domain, address book and mailbox into one hand, and give Odoo one mailbox of its own. Ask the five questions from the previous slide today.

If you would like us to take a look with you, plan a conversation.

→ next · ← back · click a part for an explanation · I contents · N notes · F full screen
Contents