<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Inbucket News</title>
  <link href="http://www.inbucket.org/atom.xml" rel="self"/>
  <link href="http://www.inbucket.org"/>
  <updated>2025-08-03T18:53:22+00:00</updated>
  <id>http://www.inbucket.org/news</id>

  
  <entry>
    <title>Official release of Inbucket 3.1.0</title>
    <link href="http://www.inbucket.org/news/2025/08/threeonezero-final.html"/>
    <updated>2025-08-03T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2025/08/threeonezero-final</id>
    <content type="html">&lt;p&gt;Inbucket 3.1.0 is out, containing many improvements from the 3.0.x
series.  The most significant new features are:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Lua scripting to support more complex configurations and integrations&lt;/li&gt;
  &lt;li&gt;The ability to reject mail based on the origin domain&lt;/li&gt;
  &lt;li&gt;Expanded TLS support for SMTP and POP3 services&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;More details can be found in the
&lt;a href=&quot;https://github.com/inbucket/inbucket/blob/v3.1.0/CHANGELOG.md&quot;&gt;CHANGELOG&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Binaries and Linux packages available &lt;a href=&quot;https://github.com/inbucket/inbucket/releases/tag/v3.1.0&quot;&gt;on GitHub&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Inbucket is also getting a real manual.  It’s still a work in progress, but
you can find it at &lt;a href=&quot;https://book.inbucket.org/&quot;&gt;book.inbucket.org&lt;/a&gt;.&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Second beta release of Inbucket 3.1.0</title>
    <link href="http://www.inbucket.org/news/2024/02/threeonezero-beta2.html"/>
    <updated>2024-02-05T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2024/02/threeonezero-beta2</id>
    <content type="html">&lt;p&gt;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:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Lua scripting to support more complex configurations and integrations&lt;/li&gt;
  &lt;li&gt;The ability to reject mail based on the origin domain&lt;/li&gt;
  &lt;li&gt;Expanded TLS support for SMTP and POP3 services&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;More details can be found in the
&lt;a href=&quot;https://github.com/inbucket/inbucket/blob/v3.1.0-beta2/CHANGELOG.md&quot;&gt;CHANGELOG&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Binaries and Linux packages available &lt;a href=&quot;https://github.com/inbucket/inbucket/releases/tag/v3.1.0-beta2&quot;&gt;on GitHub&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Official release of Inbucket 3.0.2</title>
    <link href="http://www.inbucket.org/news/2022/07/threezerotwo.html"/>
    <updated>2022-07-04T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2022/07/threezerotwo</id>
    <content type="html">&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Changes from 3.0.1:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;arm Docker builds now rely on amd64 frontend build stage&lt;/li&gt;
  &lt;li&gt;Frontend build migrated from npm+webpack to yarn+parcel, node 16&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Binaries and Linux packages available &lt;a href=&quot;https://github.com/inbucket/inbucket/releases/tag/v3.0.2&quot;&gt;on GitHub&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>What happened to 3.0?</title>
    <link href="http://www.inbucket.org/news/2022/05/whathappenedtothree.html"/>
    <updated>2022-05-29T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2022/05/whathappenedtothree</id>
    <content type="html">&lt;p&gt;We released Inbucket 3.0.0 back in October 2021, but I forgot to write a post
about it.  Mea culpa.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What’s New:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Change highlights from 3.0.0-rc1 to 3.0.1-rc2:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Many bug fixes, build &amp;amp; test improvements&lt;/li&gt;
  &lt;li&gt;Support for SMTP AUTH LOGIN command&lt;/li&gt;
  &lt;li&gt;Dark mode support; follows OS setting&lt;/li&gt;
  &lt;li&gt;Reduced chance of click-jacking&lt;/li&gt;
  &lt;li&gt;Docker images also available on GitHub container registry&lt;/li&gt;
  &lt;li&gt;Docker image tags now use modern naming:
    &lt;ul&gt;
      &lt;li&gt;&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;stable&lt;/code&gt; has been renamed to &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;latest&lt;/code&gt;&lt;/li&gt;
      &lt;li&gt;&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;latest&lt;/code&gt; (unstable) has been renamed to &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;edge&lt;/code&gt;&lt;/li&gt;
      &lt;li&gt;Version number tags are now available, ie &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;3.0.1-rc1&lt;/code&gt;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Docker images for arm7, arm64 (for Raspberry Pi, etc)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I also updated the screenshots on this site to reflect the 3.0 user interface.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/inbucket/inbucket/blob/v3.0.1-rc2/CHANGELOG.md&quot;&gt;Full
Changelog&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Release candidate for 3.0.0</title>
    <link href="http://www.inbucket.org/news/2020/09/threezerozero-rc1.html"/>
    <updated>2020-09-25T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2020/09/threezerozero-rc1</id>
    <content type="html">&lt;p&gt;The first release candidate for Inbucket 3.0.0 is out!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What’s New:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The biggest change from the 2.x series is a brand new user interface that makes
Inbucket feel much more like an application than a website.&lt;/p&gt;

&lt;p&gt;Other significant changes include the ability include the domain in a mailbox
name (see &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;INBUCKET_MAILBOXNAMING&lt;/code&gt;), and a configurable URL base path
(&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;INBUCKET_WEB_BASEPATH&lt;/code&gt;) to aid in placing Inbucket behind an application
proxy.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/inbucket/inbucket/blob/v3.0.0-rc1/CHANGELOG.md&quot;&gt;Full
Changelog&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Official release of Inbucket 2.1.0</title>
    <link href="http://www.inbucket.org/news/2018/12/twoonezero.html"/>
    <updated>2018-12-15T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2018/12/twoonezero</id>
    <content type="html">&lt;p&gt;Inbucket 2.1.0 is official.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Changes from 2.0.0:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Added SMTP TLS support.&lt;/li&gt;
  &lt;li&gt;Added &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;INBUCKET_WEB_PPROF&lt;/code&gt; configuration option for performance profiling.&lt;/li&gt;
  &lt;li&gt;Render UTF-8 addresses correctly in both REST API and Web UI.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Binaries and Linux packages available &lt;a href=&quot;https://github.com/inbucket/inbucket/releases/tag/v2.1.0&quot;&gt;on GitHub&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Official release of Inbucket 2.0.0</title>
    <link href="http://www.inbucket.org/news/2018/05/twozerozero-final.html"/>
    <updated>2018-05-05T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2018/05/twozerozero-final</id>
    <content type="html">&lt;p&gt;Inbucket 2.0.0 is official.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Changes from rc1:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Corrected docs for INBUCKET_STORAGE_PARAMS.&lt;/li&gt;
  &lt;li&gt;Disabled color log output on Windows, doesn’t work there.&lt;/li&gt;
  &lt;li&gt;Added an &lt;a href=&quot;/configurator&quot;&gt;online configurator&lt;/a&gt; to simplify creating
a configuration suited to your needs.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Binaries and Linux packages available &lt;a href=&quot;https://github.com/inbucket/inbucket/releases/tag/v2.0.0&quot;&gt;on GitHub&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Release candidate for 2.0.0</title>
    <link href="http://www.inbucket.org/news/2018/04/twozerozero-rc1.html"/>
    <updated>2018-04-07T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2018/04/twozerozero-rc1</id>
    <content type="html">&lt;p&gt;The first release candidate for Inbucket 2.0.0 is out!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What’s New:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A &lt;em&gt;lot&lt;/em&gt; has changed, but a few of the highlights:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;In-memory storage option, best for small installations and desktops.  Will be
used by default.&lt;/li&gt;
  &lt;li&gt;Message seen flag in REST and Web UI so you can see which messages have
already been read.&lt;/li&gt;
  &lt;li&gt;Configurable support for identifying a mailbox by full email address instead
of just the local part (username).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This release also includes changes to how Inbucket is configured, default ports
in Docker, and the format of log output.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/inbucket/inbucket/blob/v2.0.0-rc1/CHANGELOG.md&quot;&gt;Full
Changelog&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Official release of Inbucket 1.3.1</title>
    <link href="http://www.inbucket.org/news/2018/03/onethreeone-release.html"/>
    <updated>2018-03-10T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2018/03/onethreeone-release</id>
    <content type="html">&lt;p&gt;Inbucket 1.3.1 is available; changes since 1.2.0 include:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;Added Button to purge mailbox contents from the UI.&lt;/li&gt;
  &lt;li&gt;Simple HTML/CSS sanitization; Safe HTML and Plain Text UI tabs.&lt;/li&gt;
  &lt;li&gt;Reverse message display sort order in the UI; now newest first.&lt;/li&gt;
  &lt;li&gt;Fixed a race condition during message receive.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/jhillyerd/inbucket/blob/v1.3.1/CHANGELOG.md&quot;&gt;Full
Changelog&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Official release of Inbucket 1.2.0</title>
    <link href="http://www.inbucket.org/news/2017/12/onetwozero-release.html"/>
    <updated>2017-12-27T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2017/12/onetwozero-release</id>
    <content type="html">&lt;p&gt;Inbucket 1.2.0 is out.  There are no significant changes from rc2,
but I did setup a &lt;a href=&quot;http://demo.inbucket.org/&quot;&gt;demo instance&lt;/a&gt; you can
play with.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/jhillyerd/inbucket/blob/1.2.0/CHANGELOG.md&quot;&gt;Full
Changelog&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Second release candidate for 1.2.0</title>
    <link href="http://www.inbucket.org/news/2017/12/onetwozero-rc2.html"/>
    <updated>2017-12-15T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2017/12/onetwozero-rc2</id>
    <content type="html">&lt;p&gt;The second release candidate for Inbucket 1.2.0 is available!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What’s New:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;rest/client types MessageHeader and Message with convenience methods;
provides a more natural API&lt;/li&gt;
  &lt;li&gt;Powerful &lt;a href=&quot;https://github.com/jhillyerd/inbucket/wiki/cmd-client&quot;&gt;command line REST client&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;Allow use of &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;latest&lt;/code&gt; as a message ID in REST calls&lt;/li&gt;
  &lt;li&gt;Fixed a crash bug in new monitor code&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/jhillyerd/inbucket/blob/1.2.0-rc2/CHANGELOG.md&quot;&gt;Full
Changelog&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Release candidate for 1.2.0</title>
    <link href="http://www.inbucket.org/news/2017/01/onetwpzero-rc1.html"/>
    <updated>2017-01-29T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2017/01/onetwpzero-rc1</id>
    <content type="html">&lt;p&gt;The first release candidate for Inbucket 1.2.0 is out!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What’s New:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;New &lt;em&gt;Monitor&lt;/em&gt; tab lists incoming messages as they arrive&lt;/li&gt;
  &lt;li&gt;Increased local-part max-length for better Mailgun compatability&lt;/li&gt;
  &lt;li&gt;Use less file handles with large distribution lists&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/jhillyerd/inbucket/blob/1.2.0-rc1/CHANGELOG.md&quot;&gt;Full
Changelog&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Official release of Inbucket 1.1.0</title>
    <link href="http://www.inbucket.org/news/2016/09/oneonezero-final.html"/>
    <updated>2016-09-03T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2016/09/oneonezero-final</id>
    <content type="html">&lt;p&gt;Inbucket 1.1.0 is official.  Check out the
&lt;a href=&quot;/screenshots/&quot;&gt;screenshots&lt;/a&gt; or get your own copy via the &lt;em&gt;Get It&lt;/em&gt;
menu above.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Changes from rc2:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;OS X Homebrew inbucket.conf and formula (see &lt;a href=&quot;https://github.com/jhillyerd/homebrew-inbucket&quot;&gt;Homebrew Tap&lt;/a&gt; repository)&lt;/li&gt;
  &lt;li&gt;Log and continue when unable to delete oldest message during cap enforcement&lt;/li&gt;
&lt;/ul&gt;

</content>
  </entry>
  
  <entry>
    <title>Second release candidate for 1.1.0</title>
    <link href="http://www.inbucket.org/news/2016/03/oneonezero-rc2.html"/>
    <updated>2016-03-06T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2016/03/oneonezero-rc2</id>
    <content type="html">&lt;p&gt;The second release candidate for Inbucket 1.1.0 is now available!  Check out the
&lt;a href=&quot;/screenshots/&quot;&gt;screenshots&lt;/a&gt; or get your own copy via the &lt;em&gt;Get It&lt;/em&gt;
menu above.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Changes from rc1:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Added &lt;em&gt;Message Cap&lt;/em&gt; to status page&lt;/li&gt;
  &lt;li&gt;Added search-while-you-type message list filter&lt;/li&gt;
  &lt;li&gt;Fixed shutdown hang in retention scanner&lt;/li&gt;
  &lt;li&gt;Inbucket now displays empty subjects as &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;(No Subject)&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  
  <entry>
    <title>Release candidate for 1.1.0</title>
    <link href="http://www.inbucket.org/news/2016/03/oneonezero-rc1.html"/>
    <updated>2016-03-04T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2016/03/oneonezero-rc1</id>
    <content type="html">&lt;p&gt;The first release candidate for Inbucket 1.1.0 is out!  Check out the
&lt;a href=&quot;/screenshots/&quot;&gt;screenshots&lt;/a&gt; or get your own copy via the &lt;em&gt;Get It&lt;/em&gt;
menu above.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What’s New:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Inbucket now builds with Go 1.5 or 1.6&lt;/li&gt;
  &lt;li&gt;Add new default theme based on Bootstrap (responsive!)&lt;/li&gt;
  &lt;li&gt;Your recently accessed mailboxes are listed in the GUI&lt;/li&gt;
  &lt;li&gt;HTML-only messages now get down-converted to plain text automatically&lt;/li&gt;
  &lt;li&gt;RESTful API moved to &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;/api/v1&lt;/code&gt; base URI&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  
  <entry>
    <title>Over 1 million served</title>
    <link href="http://www.inbucket.org/news/2014/06/1million-served.html"/>
    <updated>2014-06-06T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2014/06/1million-served</id>
    <content type="html">&lt;p&gt;I won’t claim it’s bullet-proof… But my production instance of Inbucket
recently passed 1 million emails received.  This particular install is running
Inbucket 1.0rc4 and has been up for nearly 3 months:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/1million.png&quot; alt=&quot;1 million screenshot&quot; /&gt;&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>New Website</title>
    <link href="http://www.inbucket.org/news/2014/06/new-site.html"/>
    <updated>2014-06-04T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2014/06/new-site</id>
    <content type="html">&lt;p&gt;The new website for Inbucket is up!  I’ve based it on Twitter Bootstrap 3.1,
and have tried to take advantage of Bootstrap’s responsive features.&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Run Inbucket with Docker</title>
    <link href="http://www.inbucket.org/news/2014/05/docker-image.html"/>
    <updated>2014-05-26T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2014/05/docker-image</id>
    <content type="html">&lt;p&gt;Inbucket now includes a Dockerfile, which allows you to build a 
&lt;a href=&quot;https://www.docker.io/&quot;&gt;Docker&lt;/a&gt; image.  I’ve setup a
&lt;a href=&quot;https://index.docker.io/u/jhillyerd/inbucket/&quot;&gt;trusted build&lt;/a&gt; for Inbucket,
so you don’t even have to build your own image.  Try it out:&lt;/p&gt;

&lt;div class=&quot;language-plaintext highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;docker run -p 9000:10080 -p 2500:10025 jhillyerd/inbucket
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Then point your browser at &lt;a href=&quot;http://localhost:9000/&quot;&gt;localhost:9000&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Version 1.0 Released</title>
    <link href="http://www.inbucket.org/news/2014/04/one-point-oh.html"/>
    <updated>2014-04-14T00:00:00+00:00</updated>
    <id>http://www.inbucket.org/news/2014/04/one-point-oh</id>
    <content type="html">&lt;p&gt;After four release candidates, it’s time to call Inbucket 1.0 ready!  I’m not
aware of any crash bugs and my production instance of rc4 has been running for
over a month without any noticeable memory leaks.&lt;/p&gt;
</content>
  </entry>
  
</feed>
