Skip to content

fix(compose): prioritize reply-to header over from address#529

Merged
andrinoff merged 2 commits intofloatpane:masterfrom
ronKzl:fix/reply-to-address
Apr 16, 2026
Merged

fix(compose): prioritize reply-to header over from address#529
andrinoff merged 2 commits intofloatpane:masterfrom
ronKzl:fix/reply-to-address

Conversation

@ronKzl
Copy link
Copy Markdown
Contributor

@ronKzl ronKzl commented Apr 16, 2026

What?

Added ReplyTo property tracking across the core data models and protocol parsers.

Added ReplyTo []string to backend.Email and fetcher.Email structs.

Updated imap, jmap, and pop3 backend parsers to extract the Reply-To header from incoming messages.

Updated tui.ReplyToEmailMsg handler in main.go to prioritize the Reply-To destination (if present) before falling back to the From address.

I believe the fix is straightforward but do let me know if there is anything that I missed.

Why?

Fixes #527

@ronKzl ronKzl requested a review from a team as a code owner April 16, 2026 00:25
@github-actions github-actions bot added the bug Something isn't working label Apr 16, 2026
Fixed inconsistent address format between backends and POP3 fragile raw string parsing

Signed-off-by: drew <me@andrinoff.com>
Copy link
Copy Markdown
Member

@andrinoff andrinoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@andrinoff andrinoff merged commit 2a7493a into floatpane:master Apr 16, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BUG: Mind the Reply-to

2 participants