Repository navigation
chore(deps): update mailflow to v4.1.1 - #590
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
| datasource | package | from | to | | ---------- | ------------------------------------- | ----- | ----- | | docker | ghcr.io/maathimself/mailflow-backend | 4.0.5 | 4.1.1 | | docker | ghcr.io/maathimself/mailflow-frontend | 4.0.5 | 4.1.1 |
renovate
Bot
force-pushed
the
renovate/mailflow
branch
from
October 29, 2026 17:39
4b0a830 to
a041f7e
Compare
anatolinicolae
approved these changes
Oct 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.0.5→4.1.14.0.5→4.1.1Release Notes
maathimself/mailflow (ghcr.io/maathimself/mailflow-backend)
v4.1.1: MailFlow v4.1.1Compare Source
MailFlow v4.1.1
This update fixes the unread badge that could stay at 1 after you deleted your last new message, and replies to your own sent mail that went back to you. It also adds Reply with AI. Thanks to @prudenciooficial for Reply with AI, to @salmonumbrella for the sent-reply fix, and to @fabien4444 and @thecoffeebin for reporting the badge and sidebar bugs.
New
Fixes
Upgrading
ghcr.io/maathimself/mailflow-backend:latestpoints at 4.1.1, published for amd64 and arm64. No database changes and no compose file changes since 4.1.0. Coming from 4.0.x, follow the 4.1.0 upgrade notes first.MailFlow is built and maintained by one person. If it's useful to you, you can support it on GitHub Sponsors or Ko-fi. Using MailFlow in a business? A business license supports development too. Thank you to everyone who already does.
v4.1.0: MailFlow v4.1.0Compare Source
MailFlow v4.1.0
You can now schedule a message to send later, and this release fixes a long list of reliability problems: a send that could go out twice, a Delete forever that could remove the wrong message, slow first opens of Gmail mail, and new mail that didn't show until a reload. Thanks to @fahadalisarwar1 for requesting scheduled send, to @Monkey7539 for the Delete forever fix, to @salmonumbrella for working through the move handling with us, and to @eldridgea, @faldor20 and everyone else who reported these.
New
Fixes
.envon Docker (#676).GOOGLE_*andMS_*settings in.envwere never passed to the backend container. They are now, once you update your compose file (see Upgrading).Security
Upgrading
ghcr.io/maathimself/mailflow-backend:latestpoints at 4.1.0, published for amd64 and arm64.docker-compose.ymlordocker-compose.ghcr.yml). It passes your.envOAuth settings to the backend (#676), and it gives the backend 30 seconds to stop, so a send in progress can finish during an update. Settings saved under Settings > Email providers still take precedence over.env.DB_USERandDB_NAMEif you changed them. Upgrading to 4.1 again recreates the tables.MailFlow is built and maintained by one person. If it's useful to you, you can support it on GitHub Sponsors or Ko-fi. Using MailFlow in a business? A business license supports development too. Thank you to everyone who already does.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.