Interactive presentation · click anything for an explanation
Where does your mail actually go?
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 top shows who knows where everything lives. The bottom is the mail itself, coming in and going out again.
If something goes wrong at the top, the bottom stalls.
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.
Three things that often get mixed up. Together they decide whether your address is really yours.
example.com. You rent it by the year. If you don't renew, it's gone.
Holds the domain for you: contact details, renewal and the transfer code
One setting at the registrar. They say who answers the questions about your domain.
You can request a domain through us. The price differs per extension, and some countries set their own conditions. Different per country
Is the domain registered to a former employee or the previous web agency? Then they decide about your address.
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.
example.com → 203.0.113.10 · www → example.comportal.example.com → example.odoo.comexample.com → the mail providerv=spf1 include:mailprovider include:_spf.odoo.com ~allodoo._domainkey → the public keyv=DMARC1; p=quarantine; rua=mailto:dmarc@example.comWhere does mail for example.com go?To the mail provider.
A change is live in seconds.
You can see who changed what.
It puts a shield in front of your website.
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.
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.
It stops a lot, not everything. Above all it shows what is coming, so you can choose.
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.
sanne@example.com. Own login, own inbox.
info@ or support@. Several colleagues look in.
An extra address that lands in an existing mailbox.
Give Odoo one mailbox of its own. All Odoo addresses are aliases on it.
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.
A customer sends an email to helpdesk@example.com.
The customer's mail server reads the MX record and delivers to your mail provider.
helpdesk@ is an alias. The mail lands in Odoo's one mailbox.
Every few minutes Odoo empties the mailbox.
fetchor forward
Odoo reads which address the mail was sent to and creates the right record.
helpdesk@→ticketsales@→leadinvoices@→vendor billNow 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.
In Odoo this setup is called the alias domain. It has three settings: the catch-all, the bounce and the default sender.
Every email from Odoo gets a reply address and its own number. When the customer replies, the reply falls back into the same record.
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
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.
The customer's reply arrives in Odoo. Not in your colleague's Outlook.
Peter Jansen helpdesk@example.comOdoo sees the address helpdesk@ and creates ticket 1042.
goes as an email to the customer and the followersstays internal, the customer sees nothingSanne chooses Send message. A note would never reach the customer.
Sanne (Example Ltd) peter@customer.exampleHelpdesk Example Ltd <1042.b7c2@example.com>For a ticket, the reply address is the helpdesk team's address.
Peter Jansen helpdesk@example.com<1042.b7c2@example.com>same ticket, followers get a notificationOdoo recognises the number and puts the reply in the same ticket.
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.
Included, little to set up. But a daily cap.
Odoo connects with OAuth and sends through their server. Daily caps here too.
No cap getting in the way. On a Newway account: Mailjet (now), Resend and others.
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.
Without the three ticks: a real chance of the spam folder.
Three ticks: the mail is trusted and arrives.
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.
There is no logged-in colleague. Odoo uses the default sender of the alias domain.
Your company name with a fixed address. Recognisable: every automatic email comes from the same sender.
Sanne's address falls under the sender filter. The sending server may mail on behalf of example.com.
Sanne herself, with her own address. Personal, and the address matches the domain the mail comes from.
Your server may not use that address. The recipient sees it as spoofing. Odoo rewrites it.
Sanne's name, with the company's fixed address behind it. The mail stays personal and still arrives.
catchall@example.comcatchall@example.comcatchall@example.comIn all three the reply address points to Odoo. The reply comes back into the record.
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.
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.
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.
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.