Relay · anti-virus · spam filtering · delivery

We take the mail.
You keep your server.

The SMTP gateway puts our relay, anti-virus and spam filtering in front of a mail server you run yourself. Clean mail is handed to your server on port 25; if your server is unreachable, we hold everything and keep trying.

01 / How it works

What happens between them and you.

Every message addressed to your domain passes through the same chain before it reaches your server. Each stage can reject or quarantine, so most of what would have hit your server never arrives.

  1. Stage 01
    Our relay servers accept it
    Your domain's MX records point at us, so the sending server talks to our relays rather than to yours. Your server's address never appears in public DNS.
  2. Stage 02
    Anti-virus scanning
    The relay hands the message to our anti-virus servers before anything is queued for you.
  3. Stage 03
    Spam filtering
    From there it goes to the spam filtering servers, which score it and act according to the level set on your account.
  4. Stage 04
    Held at a storage point
    What survives is queued at a storage point ready for delivery. This is the buffer that means an outage at your end costs you nothing.
  5. Stage 05
    Delivered to your server on port 25
    We connect directly to port 25 of the IP address set in your control panel — which should be the address of your own SMTP server. If that address changes, change it there first.

Prefer it as a diagram? The platform schematic shows the same chain — MX, anti-virus and anti-spam clusters, the storage facility, and the delivery paths out to IMAP, POP3, SMTP and webmail. Platform schematic (PDF, 163 KB)

02 / When your server is unreachable

We hold it, and keep trying.

If we can't connect to your server — whatever the reason — nothing is bounced back to the sender and nothing is discarded. The queue simply builds on our side until you're back.

The retry schedule

Attempt 1ImmediatelyOn arrivalfirst try
Attempt 2After 1 minuteQuick re-try+1 min
Attempt 3After 1 more minuteSecond quick re-try+1 min
Then onEvery 5 minutesUntil it goes throughrepeating

While the queue is building

Read itIn webmailQueued mail stays visiblebrowser
SafeReading changes nothingRe-delivery still happensno effect
SendersSee nothing wrongNo bounces while queuedquiet

That webmail window is the part people forget. If your office connection is down for the afternoon, someone can still read the urgent messages from a phone — and when your server comes back, the same mail is delivered to it as normal. You don't have to choose between reading it now and having it properly delivered later.

03 / Firewall

Let us through.

If there's a firewall in front of your mail server, it has to accept connections on port 25 from our delivery ranges. Blocking these is the most common reason a gateway that worked yesterday stops working today — usually after someone tightens a rule.

195.78.94.0/23 85.119.248.0/24

The first is our own range. The second belongs to a partner network that also delivers on our behalf — allow both.

Allow both, for TCP port 25 inbound. If you're restricting by single address rather than by range, you'll need to revisit it whenever we add capacity — the ranges are the stable thing to allow, not individual servers.

04 / Test your server

Are you actually listening?

Enter the IP address we deliver to and we'll try to open a connection to port 25, the same way our delivery servers do. A failure here means the problem is between us and your server, not with your mail.

This is the address set in your control panel. If you're not sure what it is, that's where to look — and if it's wrong there, the test will pass against the wrong machine.

Queue building up? Ring us.

If mail is queuing and you can't see why, we can look at our side of the connection while you look at yours. That's usually a five-minute call rather than an afternoon.