Skip to content

chore(deps): update mailflow to v4.1.1 - #590

Merged
anatolinicolae merged 1 commit into
mainfrom
renovate/mailflow
Oct 30, 2026
Merged

anatolinicolae merged 1 commit into
mainfrom
renovate/mailflow

Conversation

@renovate

@renovate renovate Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
ghcr.io/maathimself/mailflow-backend minor 4.0.5 → 4.1.1
ghcr.io/maathimself/mailflow-frontend minor 4.0.5 → 4.1.1

Release Notes

maathimself/mailflow (ghcr.io/maathimself/mailflow-backend)

v4.1.1: MailFlow v4.1.1

Compare 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
  • Reply with AI (#​577). Tell the AI in a few words what your reply should say ("approve the artwork and ask for the print date") and it writes the reply from the conversation so far. It's in the reading pane, on each message in a conversation, and in a reply's AI menu, where it takes the place of Write draft. The suggestion appears next to your draft, and you can apply it, dismiss it, or reword your instruction and ask again. It reads up to the latest 10 messages of the conversation and tells you when older ones were left out. Because it sends received mail to your AI provider, it's offered only when an admin has turned on both the writing assistant and summaries, and the server enforces that too.
Fixes
  • The unread badge stayed at 1 (#​701). After deleting, archiving or moving new messages one after another, or marking them read, the badge could stay at 1, or go back up, for up to a minute after the last one. Refreshing the page didn't help. The account count, All inboxes, the app icon, the tab and the desktop badge now show the right number. This was not new in 4.1.
  • Replying to your own sent mail (#​691, #​692). Reply and Reply All on a message in Sent went to yourself instead of to the people you wrote to. They now go to the original recipients, and Reply All includes the Cc. Mail sent from your own address with only a Reply-To for someone else, such as a contact form, still replies to that address.
  • The hidden folders toggle after a folder is deleted (#​694). If you deleted a hidden folder at your mail provider, the sidebar kept showing "1 hidden folder", and the toggle did nothing. It now counts only hidden folders that still exist. Renaming a hidden folder in MailFlow keeps it hidden, and deleting one in MailFlow clears it, so a new folder with the same name starts out visible.
Upgrading

ghcr.io/maathimself/mailflow-backend:latest points 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.0

Compare 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
  • Send later (#​543). Send in the composer now has a menu next to it with Tomorrow morning, Tomorrow afternoon, Monday morning, Later today (6 PM, offered until 4 PM), or any date and time up to a year ahead. Ctrl/Cmd+Shift+Enter opens it. On a phone, use the clock button next to Send. The message is stored encrypted on your MailFlow server and sent from there, so your browser doesn't need to be open. Attachments and forwarded messages are saved when you schedule, so archiving the original doesn't break the send.
  • The Scheduled view. Scheduled messages appear under Scheduled in the sidebar, next to Snoozed. From there you can edit, reschedule, send now or delete them, and restore a deleted one for a few minutes. Messages that need you are listed first, with the reason in words.
  • A scheduled message is sent at most once. If MailFlow can't tell whether the server took the message (for example, the connection dropped mid-send), it never retries on its own. The message shows as "Check delivery" and you decide: send anyway, or mark as sent. Temporary errors are retried for about four hours, a sign-in problem pauses the message until you sign in again, and you get a notification whenever a message needs you.
  • Offline at send time. If your server was down when a message was due, MailFlow sends it once it's back, if it's at most 6 hours late, and marks it "Sent late". Later than that, it pauses the message and asks you, so a "see you in an hour" note never goes out two days late.
  • Editing a scheduled message is safe. A message you have open can't be sent underneath you. If it's open in another window or device, MailFlow asks before moving it to the one you're using. If you close the tab after the send time has passed, the message is paused instead of sent.
  • Same action buttons in conversations (#​650). Each message in a conversation now has the same icon buttons, in the same order, as a single open message. That brings the read toggle (a message in a conversation could be marked unread but not read again), View full headers, Todoist, the remote images and unsubscribe notices, and attachments above the message. The menus work from the keyboard, and on a phone the extra tools sit in a More menu.
  • Faster first opens (#​677). Resting the mouse on a message loads its body ahead of the click, and bodies are fetched with fewer server round trips. Opening Gmail messages that weren't cached yet is noticeably quicker.
Fixes
  • A normal send could go out twice (#​685). When a send failed after the mail server had already accepted the message, MailFlow could retry on another server address and deliver it again. It now switches address only if the first attempt never got as far as starting the message.
  • Delete forever in Trash could remove a different message (#​666). MailFlow now checks the message is still the one you chose before removing it.
  • Moves on servers without UIDPLUS (#​665). After a move, MailFlow now finds the moved copy by its content instead of guessing, and drops a row it can't match rather than pointing it at another message. Applies to label removal and GTD too.
  • New mail right after adding an account (#​682). Mail that arrived during the first sync sometimes didn't all appear until a reload.
  • Mark as unread (#​683). After marking a message unread, the right-click menu, the GTD panel and the unread count now agree. A read still in progress can no longer undo a Mark as unread you just made, and opening a conversation no longer counts its first message as read twice.
  • OAuth settings in .env on Docker (#​676). GOOGLE_* and MS_* settings in .env were never passed to the backend container. They are now, once you update your compose file (see Upgrading).
  • Microsoft accounts with sending turned off. Microsoft turns off sending from mail apps (SMTP) for some Outlook.com mailboxes, often new ones, and work admins can turn it off too. MailFlow used to call this a sign-in problem, which signing in again can't fix. It now says what happened, and that you can still send from Outlook on the web.
  • Reconnecting after sleep. Returning to the tab no longer reloads the list twice, a connection that stopped answering is replaced, and a resync that fails is retried instead of leaving the list stale.
  • Clicks during background loading. Opening a message no longer waits behind prefetching and other background work on the same account.
  • Smaller fixes: the custom snooze picker used the UTC date, so it offered the wrong day in the evening west of UTC. Mark all read now refreshes the counts after the server has the change. A sent message and its Sent copy now have the same Date header. The close buttons of the headers and spam explanation windows now have labels for screen readers, and notifications are now read out by screen readers. A folder's favorite button showed a raw label instead of its name, and the Favorites labels were English in every language. Undoing a GTD classify after the message changed elsewhere now says so instead of showing a server error.
Security
  • Hardened access checks. Every route now looks up mail, accounts, rules and contacts through one shared ownership check, and a test fails the build if a route adds its own lookup.
  • Stored credentials: a damaged encrypted value is now rejected instead of being partly read.
Upgrading

ghcr.io/maathimself/mailflow-backend:latest points at 4.1.0, published for amd64 and arm64.

  • Download the new compose file (docker-compose.yml or docker-compose.ghcr.yml). It passes your .env OAuth 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.
  • One database migration (0071), applied automatically when the backend starts. It adds the tables for scheduled messages; existing data is unchanged.
  • Downgrading to 4.0.x: 4.0.x doesn't send scheduled messages, so send or delete any pending ones first. 4.0.x also refuses to make backups while the scheduled send tables exist. After switching back, remove them (this deletes every scheduled message):
    docker compose exec postgres psql -U mailflow -d mailflow -c "DROP TABLE scheduled_message_attachments, scheduled_messages; DELETE FROM schema_migrations WHERE version = '0071_scheduled_messages';"
    
    Use your DB_USER and DB_NAME if 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)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@coderabbitai

coderabbitai Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: af43ecf3-de47-4c95-a27d-1be9606679bc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

| 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
renovate Bot force-pushed the renovate/mailflow branch from 4b0a830 to a041f7e Compare October 29, 2026 17:39
@renovate renovate Bot changed the title chore(deps): update mailflow to v4.1.0 chore(deps): update mailflow to v4.1.1 Oct 29, 2026
@anatolinicolae
anatolinicolae merged commit e04692a into main Oct 30, 2026
6 checks passed
@anatolinicolae
anatolinicolae deleted the renovate/mailflow branch October 30, 2026 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant