Skip to content

Email sending

Applications send email such as password resets and order confirmations. Netkeel servers don’t run a mail server and block outgoing port 25, so an application without an email connection sends no email at all. Attach a connection to an email provider you trust, and the mail goes out through it and reaches the inbox.

Integrations › Email sending saves your provider’s SMTP login or API key once for the whole account. You then attach it to as many applications as you like, instead of typing the login into each one.

Netkeel does not run a mail relay. Mail goes from your application straight to your own provider, with the login you saved. Netkeel does not send it for you, does not host mailboxes and does not manage the DNS records of your sending domain.

Only the account owner and super admins can use this tab.

  1. In the sidebar, open Integrations, then Email sending.
  2. Click Add connection.
  3. Under Mail provider, choose how your provider connects:
    • SendGrid, Mailgun or MailerSend use the provider’s own API. The form asks for the API key (MailerSend calls it an API token), and for Mailgun your sending domain and its region (US or EU). A line under the list says where to find the key.
    • Other (SMTP settings) is for any other provider: enter the SMTP host, Port (587 is filled in) and Security yourself.
  4. Enter a Name (up to 60 characters; each name is used once).
  5. For an SMTP connection, enter the User name and the Password. For a provider’s API, enter the API key instead.
  6. Enter the Sender email address, an address your provider has verified. Sender name and Reply-to (optional) are optional.
  7. Click Test connection, then Save.
Security Port Notes
STARTTLS 587 (also 2525) The usual choice.
TLS 465 Encrypted from the first byte.
No encryption 2525 only The password and the mail cross the internet in the clear. Use it only if your provider offers nothing else.

Netkeel servers refuse outgoing connections on port 25, because that is how spam is sent straight from a server. Use 587 or 465, or 2525 where your provider offers it. A saved connection that still uses 25 shows a warning and cannot send.

An account can hold up to 10 connections.

With SendGrid, Mailgun or MailerSend, Netkeel keeps your API key encrypted and never shows it again. Test connection sends one message through the provider’s API to your own address. What your applications do with the connection depends on their type:

  • WordPress sends every message through the provider’s API instead of SMTP, which also works on servers whose cloud provider blocks SMTP ports. If the server needs an update for this first, Netkeel says so and the server updates by itself.
  • Laravel, Node.js and AI agents get the provider’s own environment variables: SENDGRID_API_KEY, MAILGUN_API_KEY, MAILGUN_DOMAIN and MAILGUN_ENDPOINT, or MAILERSEND_API_KEY, plus MAIL_FROM_ADDRESS and MAIL_FROM_NAME. Your application’s code has to call the provider, usually with the provider’s library; Netkeel only sets the variables.
  • Other application types show you the settings to copy. The key itself is never shown, so copy it from your provider.

You can’t change a connection’s provider after saving it. To switch, add a new connection and attach it; Netkeel removes the old connection’s variables from the application first.

The password is stored encrypted and never shown again. When you edit a connection, leave Password empty to keep it, as long as the host and user name stay the same. If you change either, enter the password again. If you lose it, edit the connection and enter it again.

Netkeel only connects to mail servers with a public name. IP addresses and names for private networks, such as localhost or names ending in .local or .internal, are refused. The ports allowed are 465, 587 and 2525, and the server’s certificate is always checked. Port 25 is refused because Netkeel servers block it.

There are two tests:

  • Test connection, in the form, signs in to the provider with what you typed and sends one message. Nothing is saved by testing.
  • Send test email, on a saved connection, does the same and updates the connection’s status.

The test message goes to your own address, the one you sign in to Netkeel with, and to no other. You need to have verified your email address first. If a test fails, Netkeel explains why in plain words, for example that the provider refused the login or does not accept the sender address.

A connection shows Not tested, Working or Failing. You can run up to 10 tests an hour.

Click Applications on the connection’s card, choose an application under Attach to an application and click Attach. How the settings reach the application depends on its type:

Application What happens
WordPress Set up for you. Netkeel writes the settings to the site’s own email settings. It needs an encrypted connection (STARTTLS or TLS).
Laravel Set up for you once a Git repository is connected under Deployments. Netkeel adds the MAIL_* environment variables and the application restarts. Before that, copy the settings.
Node.js Set up for you. Netkeel adds the SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, SMTP_SECURE and SMTP_FROM environment variables and the application restarts.
OpenClaw, Hermes Agent Set up for you with the same SMTP_* variables.
PHP, Static, Drupal, Joomla Copy the settings. Netkeel remembers which applications use the connection and shows the Host, Port, Security, User name and From address with a Copy button each. It never shows the password: copy that from your provider.

Your other environment variables are kept as they are. In your own code you can read the variables under different names if you prefer.

An application uses one connection at a time.

A staging copy is listed under Attach to an application as an application of its own, marked staging, once the copy has finished. A WordPress staging copy sends no email until you attach a connection to the staging copy itself. Attaching one to live doesn’t reach staging, and putting staging live never carries staging’s mail settings over to live. See Email from a staging copy.

When you restore a WordPress application from one of its own backups, it keeps the email settings it has now, those of the connection attached today. The backup’s older mail settings aren’t brought back, so a login you have since changed, detached or removed doesn’t return.

Editing a connection never changes a running application. After you save, its attached applications show Older settings. Click Apply to followed by the number of applications to write the new settings. Netkeel lists the applications first and warns that those using environment variables restart. If one application fails, the others still get the new settings.

Click Detach next to an application to stop using the connection. For WordPress the site’s email settings are cleared, and it sends no email until you attach a connection again. For environment variables, the ones Netkeel added are removed and the application restarts. Other variables stay. For applications where you copied the settings, Netkeel forgets the link, and the settings you copied stay where you put them.

Click Remove on the card. If applications use the connection, Netkeel tells you which and offers Detach and remove, which detaches it everywhere first. If that fails for some application, the connection is kept so you can try again.