Save the newsletters worth keeping to Obsidian

The short answer

Treat your vault as the place for the issues that earned a second read, not as another inbox. When an issue is worth keeping, forward it. The next time the plugin fetches, it's a note you can link, tag and search alongside everything else you know.

That's the whole workflow. The rest of this page covers the details: the subject line to use, what the note looks like, and the one thing that doesn't work (subscribing your address directly).

Why newsletters get lost

You subscribe because the writing is good. Then the issues stack up between receipts and calendar invites, and the one with the framework you wanted to try is somewhere under 400 unread messages.

Copying an issue into Obsidian by hand sounds easy until you do it. Headings flatten, links break, and you spend five minutes cleaning up a note you meant to spend five minutes reading. Most people try it twice and stop.

Read-later apps help, but your archive then lives in someone else's product. If that product changes its pricing or closes, your highlights and saved issues go with it. A Markdown file in your own vault doesn't have that problem.

How to save an issue in three steps

1. 1

   Step 1: Forward the issue to your ingest address

   Open the issue in your mail app, tap Forward, and send it to your private Email2Obsidian address. Save the address as a contact so it autocompletes.
2. 2

   Step 2: Add tags to the end of the subject

   Type your tags after the subject, like "The Weekly Byte, issue 142 #newsletter #ai". The tags are removed from the title and added to the note. Delete the "Fwd:" prefix too if you want a clean title, because it isn't removed for you.
3. 3

   Step 3: Let the plugin fetch it

   The next time the plugin fetches (manually, on a schedule, or when your vault opens), the issue appears as a note in the folder you chose in the plugin settings.

One subject-line tip: never put a # inside the title text itself. Write "issue 142," not "#142," because everything after a # is read as a tag. A tag runs until the next #, so keep each tag to one word. You'll find the full rules in tag notes from the subject line.

What the note looks like

Here's an example of a forwarded issue with two tags. The subject was tidied before sending, so the title is clean.

The note is a plain Markdown file. You can link to it from a project note, quote it in your own writing, or find it later with Obsidian's search, the same as any note you wrote yourself.

Why you can't subscribe your address directly

This is the part that surprises people, so here it is plainly. Email2Obsidian accepts an email only when it comes from one of your authorized sender addresses. That's what stops strangers from filling your vault with spam if your address ever leaks.

A newsletter's sender is the publisher, not you. If you subscribe your ingest address, every issue is silently dropped. The same goes for Gmail filters and Gmail's automatic forwarding: Gmail keeps the original sender on the message, so it doesn't pass the check.

Here's what does work:

• Pressing Forward in any mail app, on desktop or phone. The forward comes from you.
• On iPhone, the share sheet to Mail, sent from your own account.
• In Outlook, a rule that uses "Forward to" sends the message as you, so it can work where your organization allows external auto-forwarding. "Redirect to" keeps the original sender and won't work. See Outlook rules (where your organization allows).
• In Apple Mail on a Mac, a "Forward Message" rule works, but only while Mail is open on that Mac.

If you want every issue of every newsletter captured with no effort at all, a forwarding address isn't the right tool. If you want the good ones, a manual forward is about as quick as it gets. Step-by-step instructions for each client are in how to forward from Gmail, Outlook and Apple Mail.

Build a reading list in your vault

Once issues are arriving, a little setup on the Obsidian side turns them into a proper reading list. These are your own choices in Obsidian, not something we add for you:

• A dedicated folder. Set "Newsletters" as the destination folder in the plugin settings so issues never mix with your other notes.
• A template with a status. If your note template includes a property like "status: to-read," every new issue starts out on your list.
• A view of everything tagged. If you use Bases or Dataview, a table of notes tagged #newsletter gives you one page with every saved issue.

Tag by topic rather than by publication if you read across many sources. #ai or #design stays useful longer than the newsletter's name.

Email2Obsidian or a read-later app?

They're different tools. At the time of writing (November 2026), Readwise Reader gives you a separate feed address you can subscribe newsletters to directly, plus highlighting built for heavy reading. If you read dozens of newsletters and want everything captured, that's a real advantage.

Email2Obsidian is narrower and cheaper. It saves the whole issue you picked as a file in your vault, and that's it. For the full comparison, see Email2Obsidian vs Readwise Reader.

How many emails will you use?

Fewer than you'd think. If you keep three issues a week, that's about 13 a month. The Free plan covers your first 10 emails (lifetime, they don't reset), which is enough to see if the habit sticks. After that, Starter gives you 300 emails a month for $2.49, which leaves plenty of room for receipts, tasks and anything else you forward. Pro adds 1,000 a month and multiple vaults if you need them.