One Click unsubscription

Hi ​@at7140  you will have to test it on the Production env and your sender should have a good reputation for it to work

Hi ​@at7140 ,

Thanks for the detail on your setup — this is a good question, and I've dug into it.

Is it possible to centralize the code in a Personalization Block?

Yes. Moving the One-Click Unsubscribe header code into a shared Personalization Block and referencing it from the SMTP tab, while keeping the Web App and Typology logic unchanged, is a valid approach. You confirmed the raw email source shows both List-Unsubscribe and List-Unsubscribe-Post headers present and correctly formatted, which tells us your setup is generating the headers exactly as it should. So the Personalization Block reuse is not the issue here.

Why the Unsubscribe option still isn't showing next to the sender

Once the headers are present and correctly formatted, whether the "Unsubscribe" button actually appears next to the sender's name is a decision made entirely by the receiving mail provider (Gmail, Outlook, Yahoo, etc.) — not by Adobe Campaign. Each provider applies its own eligibility checks on top of header presence, mainly:

1. Sender authentication alignment — SPF, DKIM, and DMARC must all pass and be aligned with the visible "From" domain.
2. Sender reputation — spam complaint rate under the provider's threshold, and a consistent sending history from that domain/IP.
3. Sending pattern — a one-off test send from a domain with limited sending history is less likely to trigger the button reliably, even with fully correct headers. Providers are more consistent about rendering it for recognized, regular bulk senders.

We've seen this exact pattern before: headers technically perfect in the raw message, but the button still didn't render, purely due to the receiving provider's own criteria — not a defect in the platform.

Important: this is outside of Adobe Campaign Classic's scope. Campaign's job is to generate and send the correct headers — which it is doing correctly in your case. Whether the button renders is governed entirely by your sending domain's authentication/reputation setup and the receiving provider's policies, both of which sit with your organization's email/DNS/deliverability team, not with the Campaign configuration.

Next steps (owned by your email/DNS/deliverability team)

1. Send a small batch (not a single test) through your normal production sending domain/IP and check a few real recipient inboxes, rather than relying on one test send.
2. Confirm SPF, DKIM, and DMARC are all passing and aligned for your sending domain — verify this from the Authentication-Results line in the raw source you already pulled.
3. Check your sending domain's reputation/spam-complaint rate (e.g. via Google Postmaster Tools, if applicable).
4. If authentication and reputation are healthy and the button still doesn't appear consistently, this is expected provider-side behavior, not a Campaign configuration issue.

Status: Investigating — Campaign Classic is confirmed sending the correct headers; remaining checks are on your domain authentication/reputation, outside of Campaign's configuration.

Best regards,

Nolan

Hi ​@Nolan_Chabert 

Thanks for sharing your in-depth analysis. I was able to acheive desired result .Thanks