Releases: axllent/mailpit
v1.12.1
This release brings significant database performance improvements by using SQLite's WAL (Write-Ahead-Log) feature, resulting in far less disk I/O while writing to & deleting from the database. Previously, any changes made to the database were immediately written back to the database file (eg: mailpit.db), however now an temporary mailpit.db-wal & mailpit.db-shm file will exist alongside while Mailpit is running, which are then merged into the original mailpit.db when the program exists or during automatic pruning.
There is also a new feature (--smtp-allowed-recipients) which allows you to define (using regex) allowed recipients. All other SMTP connections will receive a 550 5.1.0 Requested action not taken: mailbox unavailable error response. This means you can run Mailpit as an open SMTP server allowing only recipients you have defined (ie: like a regular mail server). Please refer to #219 for more information.
Lastly there are a few minor big fixes to the runtime statistics visible when clicking on the "About" in the web UI.
Chore
- Significantly increase database performance using WAL (Write-Ahead-Log)
- Standardize error logging & formatting
Feature
- Add option to only allow SMTP recipients matching a regular expression (disable open-relay behaviour #219)
UI
- Automatically refresh connected browsers if Mailpit is upgraded (version change)
Fix
- Log total deleted messages when auto-pruning messages (--max)
- Prevent rare error from websocket connection (
unexpected non-whitespace character) - Log total deleted messages when deleting all messages from search
Libs
- Update node modules
Tests
- Run tests on Linux, Windows & Mac
v1.12.0
This release includes a notable change to the underlying message tagging database structure which should both drastically increase performance and reduce memory usage with large mailboxes. After upgrading, your existing message tags will be automatically migrated to the new structure.
Chore
- Include runtime statistics in API (info) & UI (About)
- Use memory pointer for internal message parsing & storage
- Update caniemail test data
- Convert to many-to-many message tag relationships
- Standardize error logging & formatting
Libs
- Update node modules
- Update Go modules
UI
- Refresh search results when search resubmitted or active tag filter clicked
v1.11.1
v1.11.0
In order to allow easier testing in some environments, this release adds the option of requesting the latest message from some API calls (eg: /api/v1/message/latest) to return the latest message summary without knowing the database ID first. This "latest" is also available for headers, raw message and HTML & link check API calls. More information can be found in the API documentation.
It also adds an option to change/set the default 100-recipient limit for incoming messages.
API
- Allow ID "latest" for message summary, headers, raw version & HTML/link checks
Feature
- Add configuration option to set maximum SMTP recipients (#205)
Libs
- Update node modules
- Update Go modules
v1.10.4
This is a very minor update to remove some JavaScript debug information for the favicon functionality, and replaces v1.10.3. The original changelog is as follows:
[v1.10.3]
Chore
- Update caniemail library & add
hrelement test
Feature
- Add @ as valid character for webroot (#215)
Fix
- New favicon notification badge to fix rendering issues (#210)
Libs
- Update node modules
- Update Go modules
v1.10.3
v1.10.2
v1.10.1
v1.10.0
Feature
- Support search query params to
/view/latestendpoints (#206) - Option to allow untrusted HTTPS certificates for screenshots & link checking (#204)
- Add URL redirect (
/view/latest) to view latest message in web UI (#166)
Fix
- Correctly close websockets on client disconnect (#207)
Libs
- Update node modules
- Update Go modules