What changed on 7–8 October
Buttondown’s 8 October changelog adds a Gmail clipping estimate to the email preview and fixes mobile navigation from a missing-alt-text warning to the relevant image. Its 7 October entry records fixes for unsubscribe links that could lead to sign-in screens or loops. These are reported fixes, not outcomes independently reproduced by Fewertools.
Preflight is a set of checks, not a delivery receipt
The official preflight documentation lists checks for email size, links, unresolved draft markers, image alt text and other issues. Most checks are advisory rather than a block on sending. It also notes that firewalls and other edge cases can limit link validation.
An estimate in the editor answers a narrower question than a message rendered in a subscriber’s mailbox. The update does not establish your inbox placement, the behavior of every email client or a successful unsubscribe in your particular configuration.
A draft that tests more than the happy path
Use one synthetic issue as a repeatable fixture. Include a short introduction, a long body section, an ordinary external link, an image with a useful text description and a deliberately unfinished draft marker. Save the exact starting draft so each later check refers to the same input.
- Capture the preview estimate. Record what the editor says before and after simplifying the long section. Keep the actual contents and output size if available; word count alone is not the rendered message.
- Exercise an editing warning. In a disposable copy, remove the image description and check whether the mobile preflight action reaches the right image. Restore a meaningful description before proceeding.
- Resolve the intentional draft defect. Check whether the unfinished marker is identified. Record the warning and the corrected content as separate states rather than describing the starting draft as ready.
- Reserve reader checks for an authorized send. Use only addresses you control. Compare the mailbox view with the saved preview, follow the relevant subscriber links and retain the observed final subscriber status.
For an unsubscribe check, a confirmation page and the resulting subscription state are separate evidence. Do not use a real subscriber as a test fixture. If no controlled send has happened, record the reader-side steps as pending instead of inferring success from the changelog.
Bring the result back to the buying decision
A newsletter trial becomes useful when it records the editor work, resulting message and exit behavior together. Our newsletter trial pack supplies a synthetic brief and export checklist; native provider steps remain unexecuted. The newsletter comparison covers feature gates and costs, and the Buttondown profile holds its product record.
No newsletter, subscriber import, unsubscribe or provider account change was executed for this report.
Sources and scope
Official sources read 10 October 2026. Facts above are attributed to the provider; the evaluation worksheets are proposed checks. This article does not report a native product test or assign a tool score.