--- title: Fix common issues with Transactional Email description: This page helps you fix common issues you may experience when using Scaleway Transactional Email tags: transactional email troubleshooting common issues errors dates: validation: 2026-05-20 posted: 2026-04-20 --- This page lists the most common issues you may encounter with your Scaleway Transactional Email and provides useful tips for troubleshooting them. | Problem | Cause | Solution | | ---------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | My emails are rejected with a "DMARC policy failure" error | The domain of the sending email address used in `From:` does not **exactly** match the domain in use. | Make sure the sending email address used in `From:` has **exactly** the same domain as the one in use. If you need multiple sending domains, each domain must be added.
For example, add the first domain `mysite.com` for emails sent from `noreply@mysite.com`. Then add the second domain `newsletter.mysite.com` for emails sent from `noreply@newsletter.mysite.com`. | | Multiple SPF records found | Two or more TXT strings start with `v=spf1` on the same domain. Only one SPF record is allowed according to [RFC 7208 standard](https://datatracker.ietf.org/doc/html/rfc7208). | Use only one SPF record.
- Incorrect example: `v=spf1 include:_spf.google.com ~all` and `v=spf1 include:_spf.tem.scaleway.com ~all`.
- Correct example: `v=spf1 include:_spf.google.com include:_spf.tem.scaleway.com ~all` | | SPF lookup limit exceeded | An SPF record is limited to up to 10 DNS lookups. | Use a tool like [SPF Record Check](https://mxtoolbox.com/spf.aspx) to count your current lookups. If you exceed 10, remove unnecessary `include:` entries or replace them with IPs directly. | | Invalid DKIM | The DKIM record does not start with `v=DKIM1;` or is truncated. | Make sure the DKIM record starts with `v=DKIM1;` and is complete. | | The DKIM record is too long for my registrar | Some registrars force a character limit for TXT records. | Use double quotes `"` to divide the DKIM key (e.g., `"v=DKIM1; k=rsa; p=MIIBIjAN..." "BgEFAAOCAQ8AMIIBCg..."`). | | The console displays my DNS records as invalid but they are correct when I check with external tools | DNS propagation is ongoing and can take up to 48 hours.
- You use a nested SPF record with an `include:` inside another `include:`. This is not supported by Transactional Email.
- A TXT record has an unsupported prefix. | Check the DNS server status using a tool like [MX Toolbox](https://mxtoolbox.com/SuperTool.aspx).
- Replace an embedded `include:` with its IP directly.
- Remove unsupported prefixes from your TXT records. |