All articles

Getting Started

What is CICDoo Getting started: the onboarding wizard The Dashboard and Infrastructure Map

Concepts

Production, staging and development stages Domains, subdomains and SSL Odoo versions and editions (Community vs Enterprise) Workspaces and team collaboration

Servers

Adding a server Server domains and DNS Using a load balancer Connecting through a jump server Server actions: deploy, logs and charts Deleting a server

Projects & Git

Creating a project Connecting GitHub Project GitHub settings and webhook Connecting GitLab Branches and instances Tagging and filtering projects High availability with app nodes Project environments, extensions and deletion

Instances & Console

Creating an instance Restarting, stopping and removing an instance Merging branches between stages Web IDE and remote access SSH access to instances Instance settings explained Email from your instances (Mail tab and outgoing mail) Deployments and the job queue

Agent Tasks

What agent tasks are Setting up agent tasks Running a task and reviewing the result Agent time and top-ups Agent insights and task filters

Monitoring & Backups

Monitoring your instance Backups and restore S3 storage, uploads and bulk backup actions Alert notifications (email and SMS)

Workspaces & Permissions

Inviting workspace members Member permissions and resource access A member cannot see or use a resource Audit log and server activity

Account & Security

Two-factor authentication (2FA) Profile and integrations settings Passwords and account recovery Instance security score and checks The Security page: every instance and member at a glance

Billing & Plans

Plans and pricing Upgrading and managing your subscription If a project subscription goes unpaid The channel partner program Onboarding a client as a partner

Support & Tickets

Opening a support ticket Getting help from the CICDoo team

Troubleshooting

Troubleshooting: cannot connect a server Troubleshooting: a deployment failed Troubleshooting: git push fails with 403 after moving a repository Troubleshooting: my instance is down or slow Troubleshooting: domain or SSL problems

Instances & Console

Email from your instances (Mail tab and outgoing mail)

Why staging and development instances never send real email and how to read what they send in the Mail tab, and how to choose how a production instance sends email in Settings, Mail.

Staging and development: mail is captured, never delivered

A staging or development instance usually runs a copy of your production database, full of real customer, supplier and employee addresses. So that a test can never email those people, CICDoo captures every email these instances send. Nothing leaves the server: no invoice reminder, password reset, newsletter or follow-up reaches a real inbox.

This is always on for staging and development and cannot be switched off. It works whatever mail servers are configured inside Odoo, including ones copied over from production.

Reading captured mail

  1. Open the staging or development instance in the Console.
  2. Click the Mail tab. A note at the top says "Mail from this instance is captured, never delivered."
  3. Messages show up within about a minute of Odoo sending them, newest first. Type in the search box to filter by sender, recipient or subject, and click Refresh to check for new ones.
  4. Click a message to read it. Switch between the HTML, Text and Headers views, and download any Attachments from below the message.
  5. To clean up, click the trash button on a message, or Delete all to empty the list.

Captured mail is kept for 14 days, and each instance keeps its 1,000 most recent messages.

Note: In a workspace, the Mail tab is shown to members with the "Logs" instance permission, because captured mail carries the same kind of content as the logs. See Member permissions and resource access.

If the Mail tab stays empty although Odoo says it sent mail, run a Hard Restart once; instances created before mail capture existed pick it up on their next Hard Restart. See Restarting, stopping and removing an instance.

Production: choosing how mail is sent

Production instances send real email. You choose how in the instance's settings.

  1. Open the production instance in the Console and click the Settings tab.
  2. Click the Mail sub-tab. It is shown on production instances only.
  3. Under Outgoing mail, pick one of the options described below.
  4. Click Save Mail Settings. The change is "Applied on the next restart.", so run a Hard Restart afterwards.
  5. Open the Mail sub-tab again after the restart. If a note says outgoing mail servers were active inside Odoo, Odoo is still using those instead of your choice here: archive them in Odoo (in developer mode: Settings, Technical, Email, Outgoing Mail Servers) and run a Hard Restart again.

The options are:

  • Managed in Odoo: the default. Use the outgoing mail servers set up inside Odoo (in developer mode: Settings, Technical, Email, Outgoing Mail Servers). CICDoo changes nothing.
  • Your own SMTP server: Gmail, Microsoft 365, Mailgun, Amazon SES or any other provider. CICDoo writes the server into the instance's Odoo configuration.
  • CICDoo mail relay: send through CICDoo with your own domain. Available when it is enabled for your project.

Using your own SMTP server

  1. Choose Your own SMTP server.
  2. Fill in SMTP server, Port, Encryption, User name and Password. The password is never shown again after saving; leave it empty to keep the saved one.
  3. Optionally fill in Send as (optional): the domain or address this server may send as. On Odoo 15 and later, mail from any other address is sent from a matching address instead.
  4. Under Send a test email, enter a sender address such as [email protected] and click Send test. The test uses the settings in the form without saving them, and goes to your own email address.
  5. When the test arrives, click Save Mail Settings and run a Hard Restart.

Port 465 (SSL) cannot be set through odoo.conf. Most providers also accept port 587 with STARTTLS, so use 587. Gmail and Microsoft 365 usually need an app password rather than your normal password.

Using the CICDoo mail relay

The relay sends your instance's mail through CICDoo from your own domain, with DKIM signing and bounce handling set up for you. You only add a few DNS records. It is enabled per project: if the option shows "Not enabled for this project. Contact us to add it.", open a support ticket to ask for it.

  1. Choose CICDoo mail relay.
  2. Under Add a domain, type the domain you send from, for example mail.example.com or example.com, and click Set up domain.
  3. A table of DNS records appears (Type, Name, Value). Add each one at your DNS provider exactly as shown. If your DNS is on Cloudflare, set these records to DNS only, not proxied.
  4. The domain shows "Waiting for DNS" until the records are found. Verification usually takes a few minutes after they are published and is checked every 15 minutes; click Check DNS now to check straight away. Once found, it shows "Verified".
  5. In Odoo, set the catchall and default sender addresses to this domain too, so every message can be sent. On Odoo 14 and earlier, every address Odoo sends from must be on this domain; Odoo 15 and later sends mail from other addresses from a matching address on the domain instead.
  6. Once the domain shows "Verified", select it as the Sending domain. Saving and test emails are refused until then.
  7. Under Send a test email, enter an address on the domain, such as [email protected], and click Send test.
  8. When the test arrives, click Save Mail Settings and run a Hard Restart.

Each domain has a monthly sending allowance, shown as "Sent this month". To protect deliverability for everyone, a domain is paused ("Suspended") when it reaches its allowance or when too many of its messages bounce or are marked as spam. While a domain is paused, Odoo keeps its outgoing mail queued and sends it once the domain is active again, with no restart needed. An allowance pause lifts at the start of the next month. A pause for bounces or spam complaints is lifted by our team after looking at the cause, so open a support ticket if your domain shows "Suspended".

A sending domain belongs to your workspace, so several production instances can share it. A domain whose DNS records are not found within 7 days is removed, so add the records soon after setting it up. To stop using a domain, click Remove domain; this is refused while a production instance still sends through it, so switch that instance to another option first.

Troubleshooting

  • Test email fails: check the server name, port and encryption first, then the user name and password. Most providers refuse the sender address unless it belongs to the account you log in with.
  • Settings saved but Odoo still sends the old way (production): Odoo's own outgoing mail servers take precedence over these settings. Archive them in Odoo (in developer mode: Settings, Technical, Email, Outgoing Mail Servers) and run a Hard Restart.
  • Odoo shows mail as sent but nothing arrives (production): check that the sender address belongs to the domain or account your SMTP server or relay allows, and look in the recipient's spam folder.
  • A relay domain stays "Waiting for DNS": compare each record with the table character by character, make sure it was added under the right domain, and turn off any proxying.
  • Customers received emails from a test copy before: once the instance has had a Hard Restart since mail capture was added, staging and development mail stays in the Mail tab. Run one on any older staging or development instance.

Related: Instance settings explained, Production, staging and development stages, Restarting, stopping and removing an instance.

If you get stuck, open a support ticket from the Tickets page or the chat widget.

Run this on your own servers with CICDoo

Connect a server and link your repository. Deployments, backups and monitoring come set up, and Odoo engineers are a message away.

Still stuck? Open a ticket from the app or talk to an engineer.