AJO email sender overrides and suppression list override explained

Adobe Journey Optimizer now lets you override email sender and delivery fields on the individual journey or campaign action, rather than building a separate channel configuration for each variation. That arrived on 28 October 2026, alongside a Limited Availability suppression list override and self-serve setup for high throughput email. For anyone who runs email across several brands, regions or teams, the first of these changes how you structure your configuration estate.

Key takeaways

• From name, From email prefix, Reply-To, recipient address and list-unsubscribe values can be set per action, using profile attributes or contextual data, from 28 October 2026.
• The suppression list override is Limited Availability. You request it through your Adobe representative, and you should write down who may use it before you do.
• Teams that have bought the High throughput transactional messaging add-on can create the IP pool and channel configuration themselves from 28 October 2026.
• Custom outbound channels reached General Availability on 2 October 2026 and gained Decisioning, business rules and API-triggered campaign support.
• Coworker picked up several new skills this month. The read-only analysis skills are the low-risk place to start.
• Audit what you have before you override anything. The point is fewer channel configurations, not more exceptions.

What the email override change actually does

Until now, a sender identity in Journey Optimizer lived in the channel configuration. If the same configuration served two programs and one needed a different Reply-To, you either cloned the configuration or lived with the compromise. The October release moves several of those fields down a level. On a journey or campaign email action, you can now override From name, From email prefix, Reply-To, the recipient address and the list-unsubscribe values.

The notes say each value can be driven by a profile attribute or by contextual data. That matters more than the per-action part. A static override just saves you a clone. A dynamic one means a single action can send as the account manager on the profile, or reply to a regional inbox chosen by data on the profile, without a branch per region.

Notice what is on the list and what isn't. The From email prefix is overridable, which suggests the domain half stays tied to the channel configuration. The release notes don't spell that out, so confirm it in Adobe's detailed documentation before you promise anyone a custom domain per brand. If a brand needs its own sending domain, it still needs its own configuration and the authentication work that comes with it.

The notes frame the use case as one configuration serving multiple programs, regions or teams that each need a distinct From address or reply routing. That is a fair description of a lot of enterprise setups, and it's where the gain is.

Who should act, and who can ignore it

Not every team needs to touch this. A single-brand company with one sender identity and one reply inbox has nothing to fix. Skip it and spend the time elsewhere.

Three groups should look closely.

• Multi-region marketing teams. If regional teams currently have their own channel configurations only because of the Reply-To address or sender name, those configurations are candidates for consolidation.
• Sales-led or service-led senders. If emails should come from a named person on the profile, such as an owner or advisor, the dynamic override is the first clean way to do it without a workaround.
• Governance and deliverability owners. You inherit the risk. A field that used to be locked in one admin-controlled place can now be set in any journey by anyone with edit rights.

That last point is the real change. Channel configurations were a control point. An override moves a slice of control from the administrator to the journey author. Whether that's good depends on who your authors are. In a central team of five, it's fine. In a federated model with forty people building journeys, you need a rule about what may be overridden and who reviews it.

How to audit your channel configurations before you override anything

The tempting move is to start overriding and tidy later. Resist it. Do the audit first, because the audit is where the value is.

1. Export or list every email channel configuration you have, with its sender name, prefix, Reply-To and unsubscribe settings.
2. Group them by what differs. Many will differ only in one of the fields that can now be overridden.
3. Mark each group as consolidate, keep or unclear. Keep any configuration that differs in ways the override can't touch, such as sending domain or IP pool.
4. For the consolidate group, list the journeys and campaigns that use each configuration. These are your migration set.
5. Decide the rule for each overridable field. For example: From name may be dynamic, Reply-To may be dynamic, list-unsubscribe stays at configuration level unless compliance signs off.

The fifth step is the one teams skip. List-unsubscribe values sit in the same group as the harmless cosmetic fields, but they aren't cosmetic. Anything that changes where an unsubscribe goes deserves a second pair of eyes, whatever your regional rules say. Check your own legal requirements, and the Adobe documentation for the exact behaviour.

The suppression list override, and why it needs a policy

The second Channels item is the one that will make some people nervous. Journey Optimizer now has a per-action toggle that allows delivery to locally-suppressed addresses for a specific email action in a journey or campaign. Adobe's stated purpose is compliance scenarios where a communication must be demonstrably attempted. Its example is a required notification to an address that has previously bounced.

This is Limited Availability, for a set of customers. You contact your Adobe representative to request access, and the notes list an availability date of 28 October 2026. Details can change before any wider release, so don't build a process around assumptions.

Be clear about what it's for. A regulated notice, such as a change to terms or a statutory notification, may need a documented attempt even when an address is on your local suppression list. That is a narrow set of messages. A promotional campaign to a lapsed segment is not on that list, and switching the toggle on to recover reach would be a mistake. Sending to addresses that bounced is exactly how sender reputation gets damaged.

If you request access, set these rules first:

• Name the message types that qualify, in writing, and have compliance or legal sign off.
• Limit who can enable the toggle on an action, and require a review before publish.
• Keep the override away from any action that shares a channel configuration with high-volume marketing sends where you can. Check the documentation on how it interacts with suppression at other levels.
• Plan how you will report on these sends separately, so a spike in bounces from a compliance notice isn't read as a deliverability problem.

If you don't have a compliance scenario of this kind, don't ask for it. Having the toggle available and unused is a smaller risk than having it available and casually used.

Self-serve high throughput email

The third change is practical rather than strategic. If you've purchased the High throughput transactional messaging add-on, you can now set up high throughput for API-triggered email campaigns yourself in the product UI. You create a dedicated High throughput IP pool, then a High throughput email channel configuration that uses it. Previously, per the notes, this meant requesting a manual setup for each resource. It's also dated 28 October 2026.

Who benefits? Teams that send transactional email triggered by an API call, such as order confirmations, password resets or booking notices, and that have outgrown standard throughput. For them, waiting on a manual request for each pool and each configuration was a scheduling dependency. Removing it makes it easier to stand up a second brand or a staging path without a ticket.

Two cautions. First, this applies only if you've bought the add-on. The notes don't say it's included in other entitlements, so don't assume it is. Second, self-serve doesn't mean self-warming. A new IP pool still has a reputation to build, and the notes say nothing about how that's handled. Plan warm-up and volume ramps with your deliverability lead as you would for any new sending infrastructure, and read Adobe's documentation for what the UI does and doesn't set up.

This pairs naturally with the sender override. A transactional stream might use a dedicated high throughput configuration, with the From name and Reply-To adjusted per action for each brand that uses it.

Custom outbound channels and the Coworker skills

The release notes also cover custom outbound channels reaching General Availability on 2 October 2026, so briefly. Administrators can bring an outbound HTTP-based channel, such as WeChat, Kakao Talk, Messenger or a proprietary provider, into Journey Optimizer through a no-code Channel Builder. The GA release adds Journey Optimizer Decisioning in the custom channel payload through the Personalization Editor, business rules on custom channels, and the ability to pick custom channels for API-triggered campaigns. It was previously Limited Availability and is now open to all environments.

If you have a messaging provider that isn't native, the practical question is whether the integration is worth maintaining inside AJO or should stay outside it. The GA notes say custom channels carry personalization, experimentation, preview and proof, reporting, and consent and governance enforcement, which is the argument for bringing it inside.

Coworker is the other thread. The October notes list a Channel Builder skill for creating custom channels by chat, and a handful of analysis skills: Business Performance Analysis, Journey Hygiene Analysis, Trace Journey Profile, Journey Execution Timeline, and a Decisioning rule generation skill. The Trace Journey Profile skill is described as read-only and profile-level. The Journey Hygiene Analysis skill scans journeys for configuration issues and suggests fixes in chat.

A sensible order of use: start with hygiene analysis, because it pairs with the audit above. Use the trace skill when support asks why one person didn't get a message. Be more careful with the Channel Builder skill and the rule generation skill, since what they produce affects live behaviour. Review the output as you would a colleague's work.

Rolling it out and measuring it

A sensible sequence keeps the risky parts small. The table sets out one version of it.

For testing, use proof sends with test profiles that cover the awkward cases: a profile missing the attribute that drives the override, a profile with an unusually long name, a profile in each region. A dynamic field with no fallback is how a blank From name reaches a real inbox. Ask in the documentation what happens when the source value is empty, and design around the answer.

For measurement, watch the things the override might disturb: bounce and complaint rates by sender identity, reply handling, and unsubscribe volume. Compare a migrated journey with its previous behaviour over a comparable period. Direction is enough. You're looking for a clear change, not a small one.

What not to do, and where a partner helps

A few mistakes are easy to predict.

• Don't override everything because you can. Every override is an exception someone has to remember.
• Don't treat the suppression override as a reach tool.
• Don't delete old channel configurations before the journeys using them have moved and run cleanly.
• Don't assume Limited Availability features are stable. The notes warn that coming-soon information is subject to change.

Most of this a capable in-house team can do alone. The audit, the pilot and the Coworker trials need platform knowledge, not outside help. A partner earns their fee in the harder parts: consolidating a large, grown-over-years estate of configurations without breaking reporting, designing governance for a federated authoring model, building the compliance case and operating model for the suppression override, and planning high throughput infrastructure alongside a deliverability programme. If you're weighing that, the Adobe Journey Optimizer partners page is a reasonable place to see who works in this area, and the Journey Optimizer RFP template will help you write a brief that names the configuration audit and governance work explicitly rather than leaving them to be discovered mid-project. If you're still choosing, find partners lets you narrow by what you need.

One more point of timing. The notes show a Coming soon section that was cut short in the text available, and Adobe says items there are subject to change. Check the live release notes before you commit dates to anyone.

Sources

• Adobe Experience League: Journey Optimizer release notes — October 2026 release notes, last updated 3 November 2026: Channels section and Coworker summary