News Archive What's old and new with Inbucket
Inbucket 3.2.0 released
Inbucket 3.2.0 is out. The headline feature is automatic TLS certificate reloading: when your certificate or key files change on disk, Inbucket picks up the new ones without a restart. Other improvements:
- TLS+POP3 related bug fixes
- Header decoding failures are now logged, making misbehaving mail easier to diagnose
- Routine dependency and build updates
More details in the CHANGELOG
Binaries and Linux packages available on GitHub
Official release of Inbucket 3.1.0
Inbucket 3.1.0 is out, containing many improvements from the 3.0.x series. The most significant new features are:
- Lua scripting to support more complex configurations and integrations
- The ability to reject mail based on the origin domain
- Expanded TLS support for SMTP and POP3 services
More details can be found in the CHANGELOG
Binaries and Linux packages available on GitHub
Inbucket is also getting a real manual. It’s still a work in progress, but you can find it at book.inbucket.org.
Second beta release of Inbucket 3.1.0
We’ve published v3.1.0-beta2, containing many improvements from the 3.0.x series. The most significant features in 3.1.x thus far:
- Lua scripting to support more complex configurations and integrations
- The ability to reject mail based on the origin domain
- Expanded TLS support for SMTP and POP3 services
More details can be found in the CHANGELOG
Binaries and Linux packages available on GitHub
Official release of Inbucket 3.0.2
Release 3.0.2 resolves build and packaging issues we ran into with previous 3.0 releases. The user experience should be the same as 3.0.1-rc2.
Changes from 3.0.1:
- arm Docker builds now rely on amd64 frontend build stage
- Frontend build migrated from npm+webpack to yarn+parcel, node 16
Binaries and Linux packages available on GitHub
What happened to 3.0?
We released Inbucket 3.0.0 back in October 2021, but I forgot to write a post about it. Mea culpa.
There were some problems with the initial release, the RedHat and Debian packages were incomplete. I began work on a 3.0.1 release to resolve that and upgrade some of our dependencies, but some aspects of the front end build were not cooperating.
I’ve since migrated the front end to build with Yarn and Parcel, which simplifies things a great deal, and will hopefully reduce maintenance effort for myself. I feel this is too much of a change to keep the 3.0.1 label, so this will become 3.0.2. There will not be a final 3.0.1 release.
What does this mean for you? If you want a stable docker release, you should be OK to use 3.0.0. If you want a stable RedHat or Debian package, you should use 3.0.1-rc2.
What’s New:
Change highlights from 3.0.0-rc1 to 3.0.1-rc2:
- Many bug fixes, build & test improvements
- Support for SMTP AUTH LOGIN command
- Dark mode support; follows OS setting
- Reduced chance of click-jacking
- Docker images also available on GitHub container registry
- Docker image tags now use modern naming:
stablehas been renamed tolatestlatest(unstable) has been renamed toedge- Version number tags are now available, ie
3.0.1-rc1
- Docker images for arm7, arm64 (for Raspberry Pi, etc)
I also updated the screenshots on this site to reflect the 3.0 user interface.