mantoshkumar1 / mantoshkumar1/mantoshkumar1.github.io

Verify newsletter unsubscribe lifecycle in Gmail and Outlook

Open
#38 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1
Forks
0
Avg merge
13m
Merged PRs (30d)
2

Description

Priority: High

Problem

The newsletter unsubscribe experience has not been verified end to end. It must be easy to unsubscribe, actually stop future sends, and behave correctly across Gmail and Outlook. Newsletter emails should also have no known preventable configuration that causes them to land in Junk.

Goal

Test the complete subscribe → receive → unsubscribe → post-unsubscribe lifecycle using both Gmail and Outlook accounts.

Scope

  • Subscribe fresh Gmail and Outlook test addresses.
  • Verify confirmation and newsletter delivery behavior in each provider.
  • Locate and exercise the unsubscribe link from an actual email.
  • Confirm the subscriber state changes correctly in Buttondown.
  • Verify an unsubscribed address is not sent later newsletter mail.
  • Verify any resubscribe behavior is understandable and consent-safe.
  • Record inbox/Junk placement during the lifecycle and cross-reference any deliverability defect with the dedicated Outlook Junk investigation.

Acceptance criteria

  • Gmail subscribe/unsubscribe lifecycle passes end to end.
  • Outlook subscribe/unsubscribe lifecycle passes end to end.
  • Unsubscribe requires no account login or unnecessary friction.
  • Buttondown reflects the correct subscriber state after unsubscribe.
  • Unsubscribed addresses do not receive subsequent newsletter sends.
  • Inbox/Junk results are recorded and there is no known preventable deliverability misconfiguration.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with fresh Gmail and Outlook test addresses, then exercise the complete subscribe, delivery, unsubscribe, and resubscribe lifecycle using the actual newsletter. Record inbox/Junk placement and confirm each subscriber state in Buttondown; done means both provider checklists pass and unsubscribed addresses receive no later sends.

Written by the indexing model from the issue text.

Assessment

Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.