Browse Prior Art Database

Dynamic Alteration of the "Reply All" Recipient List for an Email Thread

IP.com Disclosure Number: IPCOM000245622D
Publication Date: 2016-Mar-22
Document File: 6 page(s) / 426K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a function within an email client to allow the addition and removal of an email recipient at any time after an email or thread has been created. In the client, the function provides additional links to add/remove recipients to an email or thread.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 45% of the total text.

Page 01 of 6

Dynamic Alteration of the "Reply All" Recipient List for an Email Thread

If a person is mistakenly forgotten on an original email's recipient list, there is currently no way for the sender to go back and add that person as a recipient. The current solution is to send another Reply All to add that recipient to the next note in the thread. Even after sending the next reply, there is no guarantee that the next person that replies will do so to the latest note that includes the new recipient, which still does not

guarantee that the new recipient will be kept on this thread in the future. In addition, there are times when a thread branches into a different direction and it makes sense to add or remove others from this thread. In this instance, as for the removal of a recipient, the only way to have a user removed from this email thread is to ask everyone on the recipient list to not add that user on any replies going forward; again, there is no guarantee that everyone will do so.

The novel contribution is a function within an email client to allow the addition and removal of an email recipient at any time after an email or thread has been created. In the client, the function provides additional links to add/remove recipients to an email or thread. After that person is added, the system automatically pushes to that recipient the thread of notes that was previously sent. Once another recipient decides to perform a Reply All to ANY note in that thread, the recipient that was added/removed to/from the thread now receives/does not receive notes from this thread going forward.

To implement this invention, each email thread receives a unique thread ID to identify the recipients that are currently on each thread. A database on a centralized server

saves these thread IDs that contain the list of recipients associated with each thread. The mail client contains new links called Add Recipient and Remove Recipient . (At any

time, if the user wants to request the most recent list of recipients on the thread, the

user can click the Display Recipients button to do so.) At any point after a sender

creates a thread, any recipient on this thread can Add or Remove any other recipient. When user adds or removes a person from an email thread, the centralized database automatically updates. If a recipient is added, the email client automatically sends the latest note in the thread (with the previous notes in the thread appended to the bottom

of this note) to the new recipient(s), without sending a new email to every recipient on

the thread. After the system updates the thread in the database with the new recipient, any time a user decides to perform a Reply All on any note in the thread, the mail client performs a request for the most recent list of recipients on this thread, and then sends the reply to only these recipients.

This feature can be used across multiple email clients that support the new x_threadid message header field. Following are the proced...