Skip to content

Set up incoming and outgoing email

Quick summary: For a typical setup with your own email provider, use one dedicated mailbox and several email aliases. Connect Odoo to that mailbox for incoming messages and configure SMTP for outgoing messages, so replies reach the correct document and delivery failures are tracked.


The main procedure below applies to Odoo hosted by Implex or on your own infrastructure, using an external email provider. A practical starting point is one real mailbox, such as odoo@company.example, with catchall, bounce, and your application aliases all delivered into it. The same account can authenticate SMTP if the provider allows it; a separate SMTP relay is also possible.

An email alias at the provider is an additional address delivered into a mailbox, usually without a separate login. An alias in Odoo tells Odoo where to route the received message. For an application address to work, configure both sides. Creating an alias in Odoo does not create an address at your provider.

One mailbox is sufficient when the provider supports these aliases and preserves the original recipients and message headers. Separate mailboxes are also possible, but each mailbox Odoo must read needs its own incoming server connection. Do not create multiple incoming connections to the same mailbox just because it has multiple aliases.

On Odoo Online and Odoo.sh, the default yourdatabase.odoo.com email domain already sends and receives mail without a separate mailbox. For a custom domain, redirection of each address to its matching Odoo address is a supported alternative to mailbox fetching. For example, redirect catchall@company.example to catchall@yourdatabase.odoo.com, and do the same for bounce and every application alias. Preserve the original sender and headers. Do not enable redirection and IMAP fetching for the same messages. On self-hosted Odoo, direct mail delivery requires a configured mail gateway; changing DNS alone does not deliver messages into the database.

  • Real mailbox: odoo@company.example is the dedicated account with IMAP access and the provider’s required authentication. It can also be the SMTP login if permitted.
  • Catchall: catchall@company.example receives replies to existing Odoo conversations when no application alias is available. Deliver this required alias to the mailbox. It is not an address for starting new requests.
  • Bounce: bounce@company.example receives delivery failures returned to Odoo. Deliver this required alias to the mailbox, and check how the SMTP provider handles the envelope sender and return path.
  • Default sender: notifications@company.example is the default outgoing sender. Authorize it at the SMTP provider if used. Add a provider alias if the provider requires one; it does not need its own inbox.
  • Application addresses: sales@company.example and support@company.example can receive new leads, opportunities, or support tickets, and their replies. These are optional provider aliases delivered to the mailbox, with corresponding aliases configured on the relevant Odoo teams.

The required roles are catchall and bounce. Their default names are catchall and bounce, but you may choose other names. Enter the same names in Odoo and at the provider. The Odoo catchall address does not require a domain-wide wildcard catch-all at the provider: explicitly delivering the addresses you use is sufficient.

  1. Create the dedicated mailbox and enable IMAP. Prefer IMAP with SSL/TLS, normally port 993. Odoo reads unread messages from the inbox; rules must not move them elsewhere or mark them as read before Odoo fetches them.
  2. Add the catchall and bounce addresses as aliases delivered to that mailbox. Add each application address you intend to use. Preserve the original recipients, sender, and threading headers when delivering messages.
  3. Enable SMTP submission or arrange an authenticated relay. Obtain the server, port, and encryption settings. Common combinations are port 587 with STARTTLS or 465 with SSL/TLS; use the provider’s documented combination and certificate validation. Port 25 is blocked on Odoo Online and Odoo.sh and is often restricted elsewhere.
  4. Authorize every address Odoo will send from. Receiving mail through an alias does not automatically grant permission to send from it. For the simplest setup, use one approved sender; to send as individual users or teams, configure the provider’s send-as permissions or domain authorization.
  5. Configure authentication supported by the provider. For Google Workspace/Gmail or Microsoft 365, follow the Odoo OAuth setup linked below, including the provider application and consent requirements. Use a password or app password only where the provider supports it. Keep credentials in Odoo’s protected configuration and your password manager.

If the SMTP service rewrites the return path or processes bounces itself, confirm how delivery failures will reach Odoo. Otherwise outgoing email may arrive successfully while Odoo never receives delivery-failure notifications. Also check any tagged addresses the provider or relay uses, such as bounce+tag@company.example.

Set the domain and default aliases in Odoo

Section titled “Set the domain and default aliases in Odoo”
Open alias domain settings in Odoo

Your Odoo address

Enter the base address of your Odoo instance. It will be stored only in this browser.

The documentation does not receive your address, username, or password.

  1. Open Settings > General Settings. Under Emails, set Alias Domain to your email domain, for example company.example. Use the domain that receives the aliases, without @ or a website prefix. Save the settings. In a multi-company database, select and check each company’s domain separately.
  2. With developer mode active, open Settings > Technical > Email > Alias Domains and open that domain. Check Domain, Catchall Alias, Bounce Alias, and Default From Alias. For the standard names, use catchall, bounce, and notifications respectively. Alias fields take the part before @.
  3. Decide how outgoing senders should appear. Default From Alias can contain a local part such as notifications, which provides the fallback sender, or a complete address such as odoo@company.example, which overrides outgoing sender addresses. Use the complete address for a simple single-sender setup, and ensure the SMTP provider authorizes it.

On Odoo Online with its default outgoing service, the return path remains Odoo’s bounce@yourdatabase.odoo.com, regardless of a custom bounce alias. Check the actual headers when testing.

Open outgoing mail servers in Odoo

Your Odoo address

Enter the base address of your Odoo instance. It will be stored only in this browser.

The documentation does not receive your address, username, or password.

  1. In Settings > General Settings > Emails, enable Use Custom Email Servers and save. With developer mode active, open Settings > Technical > Email > Outgoing Mail Servers and click New.
  2. Enter a recognizable Name. In Connection, set SMTP Server, SMTP Port, Connection Encryption, and the required authentication details. Prefer an encryption option that validates the server certificate. For OAuth, complete the provider-specific connection procedure instead of assuming a mailbox password will work.
  3. Set FROM Filtering to the approved full sender address, such as odoo@company.example, or to company.example if the provider permits sending for that entire domain. This filter helps Odoo select the server; it does not grant send-as permission at the provider. Check the sender on user profiles and email templates as well.
  4. Set Priority if there are multiple servers; lower numbers take precedence among applicable servers. Save and click Test Connection.
  5. Send a real message from a test quotation or another document to an external test recipient. Confirm arrival and inspect its sender, reply address, return path, and authentication results. A successful connection test alone does not prove delivery or permission to use every sender address.

If you use Email Marketing, check its dedicated sending server and provider quotas separately. Successful transactional email setup does not establish the capacity or permission for bulk campaigns.

Open incoming mail servers in Odoo

Your Odoo address

Enter the base address of your Odoo instance. It will be stored only in this browser.

The documentation does not receive your address, username, or password.

  1. Open Settings > Technical > Email > Incoming Mail Servers and click New. Create one connection for the dedicated mailbox, rather than one per alias.
  2. Enter Name, choose IMAP Server as Server Type, and enter Server Name, Port, SSL/TLS, and Username using the provider’s settings. The username is the real mailbox login, not the catchall or bounce alias. Enter the supported authentication details or complete the OAuth connection.
  3. Decide how to handle messages without a matching conversation or application alias. To place them in a monitored queue, select Helpdesk Ticket in Create a New Record, as described below. Leave it empty only if you deliberately want no fallback record; unmatched messages then fail routing and need manual investigation.
  4. Save, then click Test & Confirm. Send a test message to a configured application alias, then click Fetch Now and check the resulting record. Test catchall by replying to a message sent from Odoo; a new, unrelated email addressed directly to catchall is normally rejected.
  5. In Settings > Technical > Automation > Scheduled Actions, check that Mail: Fetchmail Service is active and scheduled. Confirm that your Odoo host runs scheduled actions. Incoming mailbox fetching is periodic, so allow for its interval when testing.

Prefer IMAP over POP. POP retrieves the mailbox history and deletes fetched messages from the mailbox. IMAP keeps the messages but marks fetched messages as read, so another mail client must not read them first. Messages that fail routing can also be marked read: inspect the error and mailbox before assuming that the next fetch will retry them.

Use Create a New Record on the incoming mail server to create a record when a fetched message cannot be linked to an existing conversation or a configured application alias. This applies to messages fetched from that mailbox, not to every incoming email in the database. Recognized replies and application aliases keep their normal routing.

Helpdesk Ticket is a sensible default for a general business inbox when someone regularly checks Helpdesk. It gives unmatched mail a visible place for triage and reassignment. The Helpdesk application must be installed, and the receiving team needs a clear owner who also checks unassigned tickets.

  1. Open Settings > Technical > Email > Incoming Mail Servers and open the connection for the shared mailbox.
  2. On Server & Login, find Actions to Perform on Incoming Mails. In Create a New Record, select Helpdesk Ticket and save.
  3. Check where fallback tickets will be reviewed. This field selects the record type, not a specific helpdesk team. Without an application alias supplying the team, Odoo uses its default team selection. Verify the resulting team, company, visibility, and assignee rather than assuming they match your usual support address. If a fixed team is required, use that team’s email alias for explicitly routed messages or arrange the appropriate defaults with your administrator.
  4. Send a new external test email to the real mailbox address, such as odoo@company.example, with no matching application alias or reference to an earlier Odoo message. Click Fetch Now. Confirm that exactly one ticket appears where the responsible people will see it, with the correct sender, subject, message, and attachments. Check any outgoing acknowledgment as well.
  5. Reply to an existing Odoo email and send a new message to a configured application alias. Confirm that both still reach their usual destinations. Finally, test another unmatched message through the scheduled fetch.

The fallback does not override an alias’s sender restrictions or recover every processing error. Delivery failures follow the bounce handling, and a new, unrelated message sent directly to catchall is still normally rejected. Inspect the mailbox and logs when a message is missing; this setting is not an error queue.

Other destinations can make sense when they match an established workflow:

  • Lead/Opportunity in CRM suits a dedicated sales inbox whose owner reviews incoming inquiries. Avoid using it for general unmatched mail that would clutter the sales pipeline.
  • Task in Project suits an operations inbox with a clear task owner. Verify that fallback tasks have the intended project and assignee; selecting the record type alone does not select a project. Use a project email alias when the destination project must be explicit.
  • No fallback suits a mailbox intentionally restricted to known aliases and replies, provided someone monitors routing failures and unread or failed messages. It does not create an Odoo record for unmatched mail.

Choose the destination people will actually review. For a mixed business mailbox, a monitored Helpdesk queue is usually the clearest starting point.

Configure the address on its owning sales team, helpdesk team, project, or other feature that supports email aliases. Use the same local part and domain that you created at the provider, and check who is allowed to send to it. The relevant application must be installed and configured to create the intended records.

For example, deliver support@company.example into the shared mailbox and configure that address on the intended helpdesk team. A new email should create a ticket for that team; a reply to a ticket email should join the existing ticket conversation. Do not create ordinary application aliases named catchall or bounce, as those names are reserved for their special roles.

For an overview, use Settings > Technical > Email > Aliases. If messages reach the mailbox but the wrong alias is matched, inspect the original recipient headers and alias domain. Local-part based incoming detection deliberately matches only the part before @; enable it only when that broader matching is intended.

Have the domain administrator publish the DNS records for the service that actually sends your email:

  • MX determines where incoming mail is delivered. For the mailbox setup, it should point to your email provider. Do not replace the company’s existing MX records just to connect Odoo through IMAP.
  • SPF authorizes sending services for the envelope-sender domain. Keep a single SPF record for each domain and include all legitimate services in it, using the provider’s exact values.
  • DKIM signs outgoing messages. Publish the provider’s required selector and TXT or CNAME record, then enable signing at the sending service if required.
  • DMARC checks that the visible sender domain aligns with a domain authenticated by SPF or DKIM. Review the existing policy and reports before tightening it so legitimate company mail keeps working.

When sending through an external SMTP provider, use that provider’s DNS instructions. Odoo’s SPF include and DKIM records apply when using Odoo’s own sending infrastructure; they do not authorize a different SMTP provider. Configure every domain or subdomain you actually use for sending, and allow for DNS propagation before testing.

Use controlled external test accounts and non-confidential documents. Sending from a document can notify its followers, so choose the document and recipients accordingly.

Test Expected result
Send from Odoo to an external address Message arrives with the intended sender, permitted reply address, and passing authentication, without an unexpected spam classification.
Reply to that message Reply appears on the original document’s conversation after delivery or fetching. Test the catchall route and an application-alias route.
Start a new email to an application alias Exactly one record is created in the intended team or application, with the correct sender and attachments.
Send a new unmatched message to the real mailbox, with fallback enabled Exactly one fallback record is created in the monitored destination; check its team or project, company, visibility, and assignment.
Cause a controlled delivery failure using your provider’s test facility or an address you control Odoo receives a correlatable failure and displays the delivery error on the original message. A plain email to bounce does not test this.
Leave another test email unread and wait for the scheduled fetch Message is processed without Fetch Now, proving that periodic retrieval works.

The setup is ready when outbound delivery, replies, new-record creation, delivery failures, and scheduled retrieval all work with the intended access and sender identities. For multi-company or multiple-domain setups, repeat these checks for each route.

  • Connection or login fails: check hostname, port, encryption, certificate validity, firewall access, enabled IMAP/SMTP access, OAuth consent, and expired credentials. Some providers disable password-based authentication even when the password is correct.
  • SMTP test succeeds but mail does not arrive: check the actual message in Settings > Technical > Email > Emails, the provider’s delivery logs, send-as permissions, quota, attachment size, and the recipient’s spam folder. If mail stays queued, check the outgoing email queue scheduled action as well.
  • Mail reaches the mailbox but not Odoo: check that it is unread in the inbox, the incoming server is confirmed, scheduled actions run, and the original recipient matches an Odoo alias. Inspect server errors and logs for failed routing.
  • Replies create new records or land on the wrong record: preserve the original message and reply headers; avoid forwarding as a new message. Check the recipient domain, alias configuration, and any mailbox-level fallback record type.
  • Delivery errors do not appear: inspect the actual return path, the provider’s bounce handling, delivery to the bounce alias, and scheduled retrieval. Not every remote rejection produces an immediate or usable bounce.
  • Duplicate records or loops appear: check for duplicate forwarding rules, simultaneous forwarding and fetching, or automatic replies that feed back into an Odoo alias.