Most outbound email problems get blamed on infrastructure. The domain is new, the inboxes are warming, the copy is too salesy. Sometimes the real problem is simpler and harder to fix: the person on the list never agreed to receive this particular message.

A recent post from Nithyanandan Ramakrishna makes the point with a short parable about a monkey holding a handful of peas. One pea slips and falls, the monkey opens his hand to catch it, and the rest scatter into the dust. Trying to recover one, he loses what he still had. The full post is worth reading: the original LinkedIn post.

The business version of that story is common in agencies. Someone signs up for your event and agrees to receive updates about it. Months later you want to restart the conversation, so their address goes into a campaign for a different service. The address still works. The validation result says "valid." But does their permission cover this message?

Validation checks the address. Consent concerns the person.

This is the line from the post that agencies should pin above their desks. Email validation tools answer one question: will this address accept mail without bouncing? They do not answer whether the recipient wants to hear from you, or whether they agreed to hear about this topic, from this sender, at this time.

That gap matters because the two failures look different. A bad address produces a bounce, and bounces are visible, measurable and fixable. A consent problem produces complaints, spam trap hits and a slow decline in sender reputation that is much harder to trace back to its cause. By the time deliverability suffers, the campaign that caused it is long finished.

So treat validation and consent as two separate checks that both have to pass before a contact enters a sequence.

The permission drift problem

Permission is not a permanent property of an email address. It is tied to a specific context: who collected it, what the person was told, and what they agreed to receive. That context erodes quietly.

A few ways it happens in agency work:

  • Topic drift. A contact opted in for event updates and later receives a pitch for an unrelated service.
  • Sender drift. A contact opted in to hear from one brand, and the address is reused across a different client account.
  • Time drift. The original signup was years ago and the relationship has gone quiet, so the next message lands with no context.
  • List drift. Contacts get merged from several sources into one master list, and the original opt in details are lost in the process.

None of these involve a fake or invalid address. All of them involve sending to someone whose agreement does not cover the message you are about to send.

What a genuine choice looks like

If you collect permission as part of a form, landing page or event signup, the choice has to be real. A few practical markers:

  • Say who will be in touch. Name the company or brand that will send future marketing, not just the event or the campaign.
  • Say what they are agreeing to. Future marketing emails, product updates, or a specific newsletter. Vague language like "partner communications" does not help the recipient understand what they signed up for.
  • Make withdrawal easy. The person should be able to decline future marketing and still continue to the intended landing page or complete the action they came for. Consent that is bundled with access to the thing they wanted is not really a choice.
  • Keep a record. Store what was agreed, when, and through which form. You will need it later when someone asks why they are on your list.

MailHeight provides a dedicated step where recipients can choose whether to receive future marketing, which is the kind of explicit checkpoint this approach needs. The point is not the specific tool. The point is that the choice is separated from the main action and clearly explained.

Opens and clicks are not consent

The post is direct on this: an email open is not consent, and neither is an ordinary link click. A confirmation step does not make consent valid on its own either. The choice has to be genuine, and the request itself has to be appropriate.

This matters because agencies often treat engagement as retroactive permission. Someone opened three of five emails, so they must be interested, so it is fine to add them to a new campaign. That reasoning is tempting and it is not the same as agreement. Engagement tells you the address is live and the subject line worked. It does not tell you the person agreed to a different kind of message.

If you want to expand what you send to an engaged contact, ask them. A short, honest email explaining what you would like to send and offering a clear way to say no is cheaper than repairing a reputation problem later.

A pre campaign consent check

Before your next outbound send, run through these questions for each list segment:

  1. What did this person originally agree to? Pull the source form or signup record. If you cannot find it, treat the permission as unclear.
  2. Does that agreement cover this message? Check the topic, the sender and the brand. If any of those changed, the permission may not travel with the address.
  3. Has anyone withdrawn it? Check unsubscribes, complaints and any do not contact notes. A withdrawal applies to the person, not just the address, so it should survive list merges and re imports.
  4. Is the sender identity consistent? The domain and brand in the From line should match what the recipient agreed to hear from.
  5. Is there a clear way out? Every message should make it obvious how to stop receiving future marketing.

If a segment fails any of these, the fix is not better copy or a warmer domain. The fix is to leave those contacts out, or to re establish permission with a message that is honest about why you are getting in touch.

Why this protects deliverability, not just compliance

The deliverability case for consent is straightforward. Recipients who did not agree to a message are far more likely to mark it as spam than to unsubscribe. Complaint rates weigh heavily on sender reputation, and reputation follows the domain and the sending IP across every campaign you run from it. One poorly sourced segment can affect every client you send for.

Consent also improves the metrics you actually care about. A list built on clear, specific agreements replies more, complains less and stays useful for longer. You spend less time cleaning up bounces and more time on campaigns that work.

The monkey in the story lost the rest of the peas trying to save one. Agencies do the same thing when they push an unclear permission into one more campaign to squeeze out a few extra leads. The address was valid. The permission was not. Before your next campaign, check what your contacts actually agreed to, what that agreement covers, and whether they have withdrawn it.