Email Delivery

Publish a post, and it goes out by email to every subscriber - automatically, through Peakub's own sending infrastructure. No third-party email tool to connect, no separate "send as newsletter" step.

Sending it again after a change

Publishing changes to an article that is already out doesn't send another email. If you want your subscribers to get it again with the changes, open the publish window of the published article: Resend to all is in the Newsletter block, and shows only once the article is published and while the Newsletter switch is on. Turn it on, then publish the changes: every subscriber gets the email again.

Where your newsletter comes from

Newsletters are sent from an address on news.peakub.com, with your publication's address name in front, for example yourpublication@news.peakub.com. A publication that has no address name of its own sends with its author's. The name readers see next to it is your publication's name.

Peakub's own messages, such as sign-in links and receipts, keep coming from peakub.com. Newsletters and those messages no longer share a domain, so a problem with one doesn't touch the other. Every newsletter is signed and authenticated for news.peakub.com, which is what mail providers check before they trust a message.

Keeping your sender reputation someone else's problem

Deliverability - the infrastructure and reputation that decide whether an email lands in an inbox or a spam folder - is managed by Peakub, not you. If a subscriber says they're not getting your posts, it's almost always spam filtering or an outdated address on their end, the same as it would be on any email platform.

Each publication sends under its own record. Its bounces, its spam complaints and its unsubscribes are counted for that publication alone, so another publication's bad day is not held against yours, and yours is not held against theirs.

Unsubscribes stay scoped to one publication

Every email has an unsubscribe link. A reader using it only turns off that publication's emails - their account, and everything else they're subscribed to, is untouched. Mail apps that offer an "Unsubscribe" button of their own (Gmail, for one) use the same setting, with no extra step for the reader.

Some mail providers tell Peakub when a reader marks a message as spam. When one does, that reader is no longer emailed by that publication, and it counts against that publication only.

Replies come to you

When a reader replies to a newsletter, the reply is passed on to the email address of your Peakub account. Readers never see that address. It reaches you as a normal email, from a Peakub address, and answering it writes to the reader.

Before it reaches you, the reply is cleaned up:

• The newsletter the reader was answering, and their signature, are left out, so you read what they wrote.
• Automatic replies, such as "I'm out of office", are not passed on.
• A reply that looks like spam is not passed on.

Replies are not shown inside Peakub yet: they arrive in your mailbox, and that is also where you answer.

Each subscriber gets what their level reads

When some blocks of an article ask for a level, the email is made for each subscriber: the blocks their level reads, and a line ("For Paid members") in place of the others. A zine's email holds the issue itself, with the same rule. See Access and paywalls.