NewThe agent now reads your files and links, and can search the web.Files, links and web search in the agent.See how

DownloadTry the demoRequest access

DocsEmail delivery

Why an email didn’t arrive

The common reasons a site’s email fails — a refused login, a blocked port, an unverified sender, a rejected address — and what to do about each.

Open Native AI → Email → Email log and click the email. The red row shows the error and, below it, what it usually means. The same explanations are here.

What you seeWhat it meansWhat to do
Could not authenticate, invalid login or keyThe provider refused the username, password or key.Check the username and key. Gmail, Yahoo and iCloud need an app password. For an API provider, create a new key with sending permission and enter it again.
Could not connect, timed outThe site can’t reach the mail server; many hosts block outgoing mail on ports 25, 465 or 587.Try port 587 with TLS, or 2525, or ask the host to open the port. The most reliable fix is an API provider, which uses ordinary HTTPS.
Certificate, SSL or TLS errorsThe secure connection failed.Switch the encryption: 587 with TLS, 465 with SSL.
Sender or domain not verifiedThe provider hasn’t verified the from address or its domain.Verify the sender or domain in the provider’s dashboard (add the SPF and DKIM records it shows), or use a verified address as the connection’s from address.
Recipient rejected, user unknown, inactiveThe address is wrong, or it bounced or was suppressed before.Check for typos. Remove it from the provider’s suppression list, or stop emailing it. A rejected address is not retried on a backup, because every provider would refuse it.
Rate limit, quota, too many requestsThe sending limit was reached.Wait, send more slowly (for CRM campaigns lower the emails per minute) or raise the limit with the provider. A backup takes over automatically.
The saved key can’t be readThe site’s security keys changed.Edit the connection and enter the key again.

Sent, but it isn’t in the inbox#

  • Check the spam folder, and that the from address is on your own domain with SPF and DKIM set up at your provider.
  • A green row means the provider accepted the email, not that the recipient’s server delivered it. Your provider’s own dashboard shows bounces.
  • If WordPress default shows as the connection, no connection was used: add one in Email → Connections.

Nothing is logged at all#

  • Make sure Email delivery is switched on in Native AI → Settings → Features.
  • Another plugin may be handling mail before Native AI sees it. The Email screen warns when it detects that; turn off email sending in that plugin.

You can also ask the AI: “Why did my last email fail?” It reads the log, explains the error and suggests the fix.

Related articles

On the features pages