Docs · Email

Send mail from your servers.

Port 25 is closed on every server. Sending through the ComputeForge relay (sign in on port 587, or let a server's port 25 go to the relay by itself) is in limited testing and not open to every account yet.

Coming soon Sending mail from servers is in limited testing, open only to a small number of test accounts. Until it opens for your account, the panel says “not available yet” and port 25 stays closed.

Why port 25 is closed

A server that can open port 25 to the internet can send spam from our addresses, and one spammer gets a whole address range blocked for everybody. So port 25 is closed twice: by the server’s firewall and at our network edge. Mail to your own mail server still arrives: only connections your servers open to port 25 elsewhere are blocked. Nothing else is affected.

Sign in on port 587 (recommended)

In the panel, open Email, then Sending from your servers, and create a credential. The password is shown once. A credential can count as the whole account or as one server (then that server’s limit applies, and the credential stops when that server’s mail is stopped). Then point your mail software at:

  • Server: cf.mtacf.com
  • Port: 587 with STARTTLS, or 465 with TLS
  • Sign-in: PLAIN or LOGIN, offered only after TLS; the user name looks like cfsmtp-0123456789ab

This works from any server, at ComputeForge or elsewhere. Postfix, sending everything through the relay:

# /etc/postfix/main.cf
relayhost = [cf.mtacf.com]:587
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options = noanonymous
smtp_tls_security_level = encrypt

# /etc/postfix/sasl_passwd (then: postmap /etc/postfix/sasl_passwd; chmod 600 /etc/postfix/sasl_passwd*)
[cf.mtacf.com]:587 cfsmtp-0123456789ab:PASSWORD

An app with its own SMTP settings (a WordPress SMTP plugin, a framework’s mailer) takes the same four values: host cf.mtacf.com, port 587, encryption TLS / STARTTLS, and the credential.

Relay mode: port 25 goes to the relay by itself

For software you cannot reconfigure (cron mail, a local MTA that delivers straight to the recipient), open the server’s Firewall tab and choose Send through the ComputeForge relay. From then on, a connection the server opens to any mail server on port 25 reaches the relay instead, which delivers the message to the recipient domain’s mail server. Nothing changes on the server.

  • IPv4 only for now: the server’s IPv6 port 25 stays closed, and mail software falls back to IPv4.
  • The relay’s certificate names cf.mtacf.com, not the recipient’s server. Mail software that insists on the recipient’s own certificate (DANE, MTA-STS in enforce mode, a “verify” TLS policy) will not deliver this way: use port 587.
  • A connection to a particular host on port 25 (a partner’s smart host) is delivered by the recipient domain’s MX instead.

What happens to every message

  • It is scanned before it goes out (spam, phishing and malware checks; an automated review may read it), and a copy is kept.
  • It is signed with DKIM: with your own key for a domain you added and verified under Email, Domains, and always for our bounce domain. The envelope sender is rewritten so bounces come back to us.
  • Your account’s sending limit applies. A new account starts at 1 message a minute and 10 an hour; the limit rises as the account builds a clean history and drops on spam. The panel shows your current limit. Mail over the limit waits and is sent later.
  • Mail the filter holds is not delivered; the sender gets a notice. Mail the portal refuses comes back as a bounce that says why.
  • Repeated spam, or one phishing or malware message, stops the server’s outbound mail. You get an e-mail, and support turns it back on after you have checked the server.

Direct port 25

A server that must deliver on its own (a real mail server with its own reputation) needs an exception from ComputeForge support, granted after a review. There is no panel button for it.