Four Doors Off a List, and One That Opens
There are four recorded reasons an address can come off an automated email sequence: the person unsubscribed, an administrator removed them, the mail bounced, or somebody marked it as spam. Three of those four have never been written by anything.
Every system that sends automated email keeps a suppression list — the addresses it must not write to again. What varies, and what almost nobody checks, is how an address gets onto that list.
We looked at our own on 26 August 2026. The list is real, it is honoured, and the sequences check it before every send. It records why each address is on it, and it recognises four reasons. One of the four has ever happened.
The four doors
They are not interchangeable, which is the whole point of recording them separately. Each represents a different party deciding, for a different reason, and each usually arrives by a different route.
| The reason recorded | Who decides | How it normally arrives | Happens here |
|---|---|---|---|
| Unsubscribed | The recipient | They click the link in the footer | Yes |
| Removed by an administrator | Your team | Somebody asks by phone or reply and you action it | No |
| Bounced | The receiving mail server | A rejection comes back from the destination | No |
| Marked as spam | The recipient, silently | Their provider reports the complaint back | No |
The one that works, and it is the important one
The unsubscribe link is real. It is in the footer, it works without a login, it records the address and the reason, and every subsequent send checks the list and skips. That is the mechanism that matters most, it is the one people actually use, and it is not what this article is complaining about.
What is worth knowing is that it is currently the only way in.
The recipient can take themselves off. Nobody else can take them off, and nothing takes them off on their behalf.
Why the administrator door is the one that bites first
The bounce and complaint doors are machinery, and their absence is a slow, quiet cost. The administrator door is different, because it fails in front of a person who has just asked you for something.
The request comes by reply, or on a call: please stop emailing me. It is a completely ordinary request, it is usually made politely, and the person receiving it in your business will say yes. There is an administration screen that lists everybody who has opted out, so it looks like the place this is done. It shows the list. It cannot add to it.
So the honest answer today is to send the person the unsubscribe link and ask them to click it themselves — which works, and which is a slightly awkward thing to say to somebody who has just asked you to handle it.
The two silent ones
A bounce means the destination refused the message. Sometimes that is temporary — a full mailbox, a server having a bad morning. Sometimes it is permanent: the address does not exist, usually because the person it belonged to has left the company it belonged to.
A permanent bounce is the clearest possible signal that an address should stop being written to. Nothing here reads it. The sequence continues on its schedule, addressed to a mailbox that has already said, in the most explicit terms a mail system has, that it is not there.
A spam complaint is the stronger signal and the quieter one. The recipient did not reply and did not click unsubscribe; they pressed a button in their own mail client, and their provider passes that back to the sender. It means the same thing as an unsubscribe and it means it more emphatically. It also does not reach the list here.
What to do about it while it is true
Four habits, none of which needs software
- When somebody asks you to stop emailing them, send them the unsubscribe link in your reply rather than promising to handle it. It works, it is immediate, and it produces a record.
- Keep your own note of anybody who asked and did not click, so the request is not lost between the ask and the action.
- Watch the mailbox your automated email replies to. Permanent bounce notices arrive there and are the only place a dead address currently announces itself.
- Treat a person who has left their employer as a suppression, not a data-quality task. It is the single most common source of a permanently dead address on any list.
That third habit is the one that carries the most weight for the least effort. Every failed delivery is telling you something, and where nothing is reading them automatically, a person reading them once a week recovers most of the value.
Three questions for anybody who sends email on your behalf
How does an address get onto your suppression list?
What you will hear
A description of the unsubscribe link.
How to read it
The link is the answer everybody gives because it is the visible half. The useful follow-up is "and what else", because the other routes are the ones that operate without anybody noticing.
If a message bounces permanently, what happens on the next send?
What you will hear
Varies enormously.
How to read it
A specific answer — a count, a threshold, a suppression — means somebody built it. A general answer about deliverability means nobody did. Ours does nothing today and we say so below.
Can somebody on your team suppress an address on a customer's request?
What you will hear
Usually yes, and usually assumed.
How to read it
Ask them to show you the screen. A list of people who have opted out looks exactly like a screen where you could add one, and the difference only appears when somebody tries.
What AWRA OpsHub does today
- A working unsubscribe link in the footer of every automated sequence, usable without a login, recorded with the address and the reason.
- A suppression list checked before every send, so an address that has opted out is skipped by every subsequent step of every sequence.
- A record of why each address is suppressed, and of when, so the list can be reasoned about rather than only obeyed.
- An administration view of everybody who has opted out, with a count, so the list is visible to your team.
- A delivery log of what was sent to whom and when, and the ability to preview a sequence before it goes anywhere.
More we can add to your workspace
- Suppression by an administrator on a customer's request, from the screen that already lists the suppressed addresses.
- Automatic suppression after a permanent bounce, so an address that no longer exists stops being written to.
- Automatic suppression on a spam complaint reported back by the recipient's provider.
- A bounce and complaint dashboard, showing which addresses are failing and how often.
- A re-subscribe path, so somebody who opted out and changed their mind can be put back deliberately.
Where we point you to a specialist
- The unsubscribe link stays the primary route and we would keep it that way. A recipient acting for themselves is the strongest form of consent signal there is, and every other door should support it rather than replace it.
- Whether a given message to a given person is permitted where you operate is a question for your own adviser. We build the suppression machinery and honour what it records; the rules that govern who may be written to are yours.
- We would decline to build a route that silently puts a suppressed address back on a list. A re-subscribe belongs to the person, deliberately, and an administrator restoring somebody quietly is the one version of this we would argue against.
Administrator suppression, bounce and complaint handling, and a deliverability view are one piece of work we can scope and quote on.
Three, and the first is an afternoon
The list, the reasons and the enforcement all exist. What is missing is the routes in, which makes each of these an addition rather than a design.
Suppress from the admin screen
A field and a button on the page that already lists opt-outs, recording the administrator as the reason. This is the one your team asks for, because it is the one a customer asks them for.
Bounce and complaint handling
Listening for the rejections and complaints the mail provider already reports, and writing them to the list under their own reasons — which are already defined and waiting for a writer.
A deliverability view
Which addresses are failing, how often, and how many suppressions came from each of the four routes. This is what turns a list into something you can manage rather than only obey.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. If anybody on your team has ever been asked to stop emailing somebody, the first item is the one to raise.
Talk to us about automated emailThe short version
A suppression list is only as good as the number of doors leading into it. Ours is honoured perfectly and has one door, which the recipient has to walk through themselves. If you run automated email anywhere — in this product or another — go and find out how many doors yours has, because the answer is almost always fewer than the list of reasons it can record.
Count the doors on your own list
Ask whoever runs your email how an address gets suppressed, then ask what else besides the link. The gap between those two answers is where dead addresses and annoyed customers accumulate.
Talk to us about email operations