> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.laposta.org/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.laposta.org/_mcp/server.

# What do you do if your newsletter does not arrive for a subscriber?

> Check whether your newsletter was actually sent and view the possible causes if a subscriber has not received your email.

Has a subscriber reported that your newsletter has not arrived? This happens very occasionally. Often, the email has indeed been sent, and something went wrong during delivery. First check whether the email really did not arrive, and then find out where things might have gone wrong.

## Check whether the email was sent and opened

In your list, click on the email address to open the subscriber's details and history. Check the following points:

* Is the address in one of your lists?
* Was that list ticked in the campaign in question?
* Do you see in the history that the newsletter was sent to this subscriber? If not, the subscriber may have been added after it was sent.
* Do you see that the newsletter was opened? Then this subscriber definitely received it.

> **Note**
>
> Recipients sometimes mistakenly claim that they have not received a newsletter, for instance because they have forgotten about it or overlooked it. It also happens that they do not want to admit to having received the email, for example because they were supposed to reply or because it concerns something less pleasant, such as an invoice.

## Possible causes after sending

If the history shows that the newsletter was sent, things may still have gone wrong at various points:

| What might be going on                                                                                | Where to read more                                                                                                                                    |
| ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| A bounce occurred for this address                                                                    | [Active, unsubscribed and cleaned subscribers](/waar-vind-ik-een-overzicht-van-actieve-uitgeschreven-en-opgeschoonde-relaties)                        |
| The address previously resulted in a hard bounce and is therefore no longer emailed                   | [Global block list](/globale-blokkadelijst)                                                                                                           |
| The newsletter ended up in the spam folder                                                            | [Why your newsletter ends up in the spam folder](/waarom-komt-mijn-nieuwsbrief-in-de-spammap-terecht)                                                 |
| It is a Gmail address: the email then often lands in the Promotions tab, which is not the spam folder | [Newsletters under the Promotions tab](/waarom-komen-nieuwsbrieven-bij-gmail-binnen-onder-de-tab-reclame)                                             |
| You want to know whether emails end up in a spam folder more often                                    | [Finding out whether newsletters have ended up in a spam folder](/hoe-weet-ik-of-er-geen-nieuwsbrieven-in-een-spambak-terecht-zijn-gekomen)           |
| It is a KPN address, such as `@planet.nl`, `@hetnet.nl` or `@xs4all.nl`                               | [Emails to KPN addresses that do not arrive](/e-mails-naar-kpn-adressen-die-niet-aankomen)                                                            |
| The sending and receiving domains are the same                                                        | [Potential issues when the sending and receiving domains are the same](/het-ontvangende-en-verzendende-domein-zijn-hetzelfde-kan-dit-problemen-geven) |

If this does not solve the issue, please let the helpdesk know which addresses are affected. If possible, the helpdesk will check the mail server log files. Sometimes this makes it possible to find out what the problem is.

## Improving delivery

If you want to make sure that all your newsletters are delivered as reliably as possible, authenticating your domain(s) will help the most. If you have not done so yet, start there.

#### [Configuring domain authentication step by step](/stap-voor-stap-je-domein-authenticeren)

Which records you need to add with your domain provider and how to activate authentication.

## Related articles

#### [Why does your newsletter end up in the spam folder?](/waarom-komt-mijn-nieuwsbrief-in-de-spammap-terecht)

Read how spam filters work and what you can do yourself to get your newsletter into the…

#### [Why is your newsletter not arriving for recipients on the same domain?](/het-ontvangende-en-verzendende-domein-zijn-hetzelfde-kan-dit-problemen-geven)

What you can do if your newsletter is rejected on your own domain or ends up in the…

#### [How does newsletter delivery work at Laposta?](/hoe-verzorgt-laposta-de-verzending-van-mijn-nieuwsbrieven)

What Laposta does to deliver your newsletter reliably and how fast it goes.

#### [Laposta glossary](/begrippenlijst)

Explanation of all terms from email marketing and Laposta from A to Z.