Skip to content
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

"Send and archive" when replying to sent email #273

Open
mattfbacon opened this issue Jan 23, 2025 · 1 comment
Open

"Send and archive" when replying to sent email #273

mattfbacon opened this issue Jan 23, 2025 · 1 comment

Comments

@mattfbacon
Copy link
Contributor

Is it intentional that the sent email is moved to the Archive, or that this button is displayed at all? I find the behaviour a bit strange, that this is not special-cased, because replying to an own email is special-cased to swap the sender and receiver.

@mjl-
Copy link
Owner

mjl- commented Jan 23, 2025

The behaviour is intentional, but perhaps the action shouldn't be possible when the Sent mailbox is open. I think I've thought so far that the functionality is harmless because you can just choose not to use it when forwarding/replying to a message in the Sent mailbox.

So the way the "archiving" works: Only the messages in the thread (that is being archived after sending) that are in the same mailbox as is currently open (from where you're replying) will be moved to the archive mailbox. If you're replying to a message that is stored in the Sent mailbox, it matters where you're viewing it. If you're viewing it the inbox (or trash, or any other place), it isn't being moved (because it's not in the same mailbox as currently open). If you're viewing it in the Sent mailbox, it will be moved (since it's stored in Sent and you're viewing it in Sent).

Having the "send & archive" available in the Sent folder isn't very useful. At least I don't see why someone would want to use it. So I'm fine with not having it there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants