Bot releases are hidden (Show)
.
and must be a minimum of 1 characterNote: This release adds ReplyTo
information in the messages summary & API, however any existing messages in your database will not return this as they need to be reindexed first. If you have existing messages and require this information (eg: API integration and/or want to search specifically for this), then please see mailpit reindex -h
.
-f 'Name <email[@example](https://github.com/example).com>'
formatnpm run build
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.
unexpected non-whitespace character
)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.
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.
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:
hr
element test/view/latest
endpoints (#206)/view/latest
) to view latest message in web UI (#166)