Open
Bug 608513
Opened 14 years ago
Updated 2 years ago
Replying to myself should be avoided
Categories
(Thunderbird :: Mail Window Front End, enhancement)
Thunderbird
Mail Window Front End
Tracking
(Not tracked)
NEW
People
(Reporter: martin, Unassigned)
Details
(Whiteboard: dupme?)
I often go to the "sent" folder and do a "answer all" there, to send another followup to a thread. Many mail clients offer a configuration setting to strip my own address (if identical to the from address in the mail I'm replying to) from the new generated recipients list automatically. If I accidently use "reply" instead of "reply all" this is even more annyoing (i.e. I'll reply to myself only, where I wanted off course to reply to original recipient again). Please consider a preference setting to allow auto-stripping my own address from replies and use the original recipient(s) address instead of "from" in this case.
Updated•14 years ago
|
Whiteboard: dupme?
Comment 1•13 years ago
|
||
Why a preference? Why not hard-code the sane behaviour?
OS: Windows XP → All
Hardware: x86 → All
Comment 2•12 years ago
|
||
Yeah. There's currently no proper option for replying on a conversation where the last message was mine. The bug I noticed is similar to Martin's, but IMO the bug is on the interface, not on the user. Among {"reply", "reply all", "forward", "reply mailing list"} there isn't a proper one to follow a conversation where the last message was from you. Actually, in my experience, the best is hit "reply all" and remove me from To:; but that's very annoying. Two way I see for this bug 1. "reply mailing list" could include this case, though it's not a proper mailing list 2. As Martin suggest - a filter (maybe optional, but by default) on "reply all" that'd remove me from To:
Reporter | ||
Comment 3•12 years ago
|
||
After noticing it works in current versions for a few co-workers, I looked at extended configuration and found that setting mailnews.reply_to_self_check_all_ident to true fixes it for my setup as well.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•