If you went looking for @forinda/kickjs-mailer on npm and found a deprecation banner instead of a v5 release, here's the punchline: the package isn't gone. It's just... yours. The framework still has everything you need to wire a mailer into the DI container — defineAdapter , createToken , lifecycle hooks — and the email surface turns out to be small enough that owning it in your own repo is the better trade. This post walks through what that pattern looks like, why it matters, and how to lay out the four pieces every BYO mailer collapses to. What got deprecated and why The README on the abandoned package is unusually direct. Quoting verbatim: Deprecated — going private in v4.1.2. Replaced by a BYO recipe using defineAdapter / definePlugin from @forinda/kickjs directly. That sentence captures a philosophical shift in how the framework treats peripheral concerns.…