Closed
Bug 166165
Opened 22 years ago
Closed 22 years ago
Message confirmation is too invasive
Categories
(SeaMonkey :: MailNews: Backend, enhancement)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 151244
People
(Reporter: timeless, Assigned: jt95070)
Details
I'm reading mail, I should be able to read a message and at the end decide
whether I want to confirm receipt of the message.
What actually happens: I get the message and have to decide to confirm before I
read the message.
It's true that in physical certified mail you have to sign on the dotted line
before you can read the message. However this is email, and it makes more sense
to allow the reader to decide to confirm receipt after reading instead of before.
I scan my mail quickly and then go back to things which are important (real
people do the same thing with real mail, although they tend to only look at the
envelope -- unfortunately the envelope for email isn't always helpful in
indicating importance).
My parents and relatives actually send me MDN'd messages, but while they do want
to know that I got the message, they're almost always more interested in knowing
that I actually *read* the message. Usually the message is an invitation or
indication about an event of some sort. If my computer has received the message
and i've marked it as read because i was skimming through my mail, but i didn't
actually read the message, then the notification is useless and misleading.
IMO a better UI would be chrome at the bottom of the message "The sender has
requested a receipt. <send receipt reply>" with a little receipt icon in the
envelop chrome which links to the bottom of the message.
I'm duping as dupe of bug 151244.
Timeless feel free to add your comments there.
*** This bug has been marked as a duplicate of 151244 ***
Severity: normal → enhancement
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
Component: MailNews: Return Receipts → MailNews: Backend
QA Contact: grylchan → offline
You need to log in
before you can comment on or make changes to this bug.
Description
•