-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change action name/icon when "replying" to a message sent by yourself #5731
Comments
Works for me with the latest stable version (5.806) and the latest beta version (5.904). Please provide the information asked for in the issue template and include (redacted) headers of the message you're replying to. |
Thanks @cketti for your test and feedback. I tested again and again, now found out which exact situation triggers the behavior. I can confirm that K-9 Mail 5.904 usually respects the "Reply-To:" header and works as expected. But there is a special situation where it does not: My configured Mail-Address is gunnar@demo-domain.demo and I hit the "Reply-to" button (or the "Reply-to-all" button) then the "Reply-To:" Address is not respected. So if the "Reply-To" address matches my own configured email-address which would practically lead to sending a Mail from me to myself, the "Reply-To:" is not respected and the mail is addressed to the "FROM:" address instead of using the "Reply-To" address. So - this is not a typical situation, it was just my test-case of testing a form-mailer which led to this "special scenario". No idea why there is an other behavior in this situation and if this is a bug or if it is intentional. K-9 Mail version: 5.904 |
Thanks 👍 It's not the According to the commit message that introduced the behavior, the idea is that the user most likely wants to send a message to the other party when replying to a message they sent themselves. |
When answering emails which was sent with an "Reply-To:" header the composed answer is addressed to the From: and not the Reply-To Address.
The text was updated successfully, but these errors were encountered: