---
title: "How email works – a message&#x27;s path from sender to mailbox | Hosteam"
description: "What happens to an email between clicking &quot;Send&quot; and the recipient's inbox: the submission server, the queue, encryption, SPF, DKIM and DMARC, retries and bounces."
canonical_url: "https://hosteam.pl/en/blog/jak-dziala-poczta-droga-wiadomosci"
---

> Index of every page on this site: [llms.txt](https://hosteam.pl/llms.txt)

# **How email works – a message's path from sender to mailbox**

What happens to an email between clicking "Send" and the recipient's inbox: the submission server, the queue, encryption, SPF, DKIM and DMARC, retries and bounces.

20 November 2026 [ #hosting](https://hosteam.pl/en/blog?tag=hosting) [ #poczta](https://hosteam.pl/en/blog?tag=poczta)

Sending an email looks like a single action, but the message actually passes through several servers, each with its own job. When mail does not arrive, lands in spam or comes back as a bounce, the cause almost always sits at one of these stages. Here is the whole path, step by step.

## Step 1. Submission – the server that accepts your message

Your mail client (Outlook, Thunderbird, your phone) does not deliver mail to the recipient directly. It hands it to your provider’s submission server (SMTP submission) – on port 587 or 465, after you log in with your address and password.

The submission server checks that you are who you say you are, enforces sending limits (they stop a hijacked account from sending thousands of spam messages) and **signs the message with your domain’s DKIM key**. From then on any server along the way can verify that the content was not altered and that it really came from your domain.

## Step 2. The queue – the message waits its turn

The accepted message goes into a queue kept on disk, not only in memory. A restart or a server failure therefore does not lose mail: once back up, the queue resumes delivery where it left off.

The queue decides when and where to send the message. If the recipient’s server is temporarily unreachable or answers “try again later”, the message is not lost – the queue retries at growing intervals. Only when the retries run out, or the recipient’s server answers with a permanent error (e.g. “no such mailbox”), does the sender get a **bounce** – a message explaining why the mail did not arrive.

## Step 3. Delivery – talking to the recipient’s server

To find the recipient’s server, our server asks DNS for the **MX** records of the recipient’s domain. It then connects and – if the recipient’s server supports it – encrypts the connection with **TLS**.

That “if it supports it” is the weak point: someone in between could pretend encryption is not available. So domains can publish rules that tell senders how to connect:

- **DANE** – the mail server’s certificate fingerprint stored in DNS and signed with DNSSEC,
- **MTA-STS** – a policy published over HTTPS that requires an encrypted connection to specific servers.

A good mail server checks both and follows what the recipient’s domain has published.

## Step 4. Receiving – the recipient’s server checks the message

Before letting the email into the mailbox, the recipient’s server checks:

1. **SPF** – whether the server connecting to it may send mail for the sender’s domain,
2. **DKIM** – whether the signature from step 1 is valid,
3. **DMARC** – what the owner of the sender’s domain wants done when SPF and DKIM fail: let it through, move it to spam or reject it.

On top of that a spam filter scores the content and the sender’s reputation. Only then does the message reach the mailbox, from which you fetch it over IMAP, POP3 or in the browser. How to set up SPF, DKIM and DMARC for your own domain is covered in [SPF, DKIM and DMARC step by step](https://hosteam.pl/en/blog/spf-dkim-dmarc-krok-po-kroku).

## What to check with any email provider

- Whether sending requires a login and works on port 587 or 465 with encryption.
- Whether the provider signs mail with your domain’s DKIM and gives you the SPF and DMARC records to add.
- The hourly and daily sending limits – they decide whether you can send a newsletter to your customers.
- How long mail logs are kept – without them it is hard to find out what happened to a particular message.

## How it works at Hosteam

Mail runs on our own mail server – software we wrote and develop ourselves. Since October 2026 every incoming and outgoing message of our customers passes through it.

- **Sending** – login on ports 587 and 465, your domain’s DKIM signature on every message, sending limits by plan: 500 messages per hour and 10,000 per day on the Eco plans, 2,000 per hour and 15,000 per day on the Business plans.
- **The queue** – kept on disk, with retries and a bounce explaining what went wrong when delivery fails. One sender with a large mailing does not block the queue for others – every customer gets their own share of the throughput.
- **Encryption** – we connect to recipients’ servers over TLS and check whether their domain publishes DANE or MTA-STS.
- **Receiving** – several MX servers, SPF, DKIM and DMARC checks and a spam filter.
- **No dropped connections** – updating the mail server does not disconnect your mail client or phone.
- **Mail logs** – from 1 to 30 days, depending on the plan.

Mail is part of every [hosting](https://hosteam.pl/en/hosting) plan, together with space for your website.

## **Looking for fast hosting?**

NVMe servers in a data centre in Poland, free migration from another provider and our own panel.

[**See hosting plans**](https://hosteam.pl/en/hosting)
