Practical guide
Use a dedicated email address for newsletters
Use a separate, permanent newsletter address. Give each reader control of subscriptions, receive only mail sent to that address, preserve sender and issue URLs, and keep personal correspondence outside the system.[1][2]
Why this gets difficult
Connecting a personal inbox exposes far more than a newsletter workflow needs. Filters also remain dependent on the personal account and make migration difficult when subscriptions change.[1][2]
A practical way through
- Choose a stable address dedicated to newsletter subscriptions.[1][2]
- Move retained subscriptions one at a time and confirm delivery from each publisher.[1][2]
- Record publication, sender, official URL, and subscription state beside received issues.[1][2]
- Maintain an exportable source list so leaving the service does not strand subscriptions.[1][2]
An example
The situation: A reader wants twenty newsletters summarized but does not want a service reading receipts, personal messages, or work mail.[1][2]
What changes: The publications are subscribed through a separate address that receives only chosen newsletter issues.[1][2]
What you get: The briefing system gets the intended reading material without access to the personal inbox.[1][2]
What to watch for
Sources worth keeping
How Scottie helps
Scottie gives the reader a private @scottie.fyi address and reads only the newsletters sent there; the personal inbox remains outside the product boundary.[3]