P
US8762385B2ActiveUtilityPatentIndex 54

Methods and systems for implementing email recipient templates

Assignee: GILL BIKRAM SINGHPriority: Jan 28, 2011Filed: Jan 28, 2011Granted: Jun 24, 2014
Est. expiryJan 28, 2031(~4.6 yrs left)· nominal 20-yr term from priority
Inventors:GILL BIKRAM SINGHSINGH MAYANKKG AMAR
G06F 16/2291G06F 16/245G06F 40/186G06Q 10/107G06F 17/30424G06F 17/30342
54
PatentIndex Score
2
Cited by
18
References
18
Claims

Abstract

The present invention is directed to methods and systems for implementing email recipient templates. The method including extracting a first set of email addresses from a first email message and extracting a second set of email addresses from a second email message. The first and second set of email addresses are included in one or more of the to, cc, or bcc fields of the email messages. The method further including storing, in a storage database, the first set of email addresses in a first recipient template and storing the second set of email addresses in a second recipient template. The first recipient template and the second recipient template each have an associated unique identifier. Further, the method includes receiving a request for a new email message in an email editor user interface and querying the storage database for recipient templates. The query is filtered by the associated unique identifiers. Further, the method includes receiving the first recipient template and the second recipient template as a result of the query, and displaying, in the email editor user interface, the email addresses associated with the first recipient template and the second recipient template.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
       1. A method for implementing email recipient templates, the method comprising:
 extracting a set of email addresses from each outbound email message sent by a user, wherein the set of email addresses are included in one or more of the to, cc, or bcc fields of the email messages; 
 storing, in a storage database, a template for each extracted set of email addresses, the templates comprising a first set of email addresses in a first recipient template and a second set of email addresses in a second recipient template, wherein the first recipient template and the second recipient template each have an associated unique identifier; 
 storing, in a dictionary maintained in the storage database, a unique index for each of the templates, the dictionary comprising a set of three lists, the lists comprising one list for the to field of email messages, one list for the cc field of email addresses, and one list for the bcc field of email addresses, and wherein storing the unique index for each of the templates in the dictionary comprises storing the index for each template in one or more of the lists based on which field the email address is extracted from; 
 receiving a request for a new email message in an email editor user interface; 
 querying the storage database for recipient templates using the dictionary, wherein the query is filtered by the associated unique identifiers; 
 receiving the first recipient template and the second recipient template as a result of the query; and 
 displaying, in the email editor user interface, the email addresses associated with the first recipient template and the second recipient template. 
 
     
     
       2. The method for implementing email recipient templates as in  claim 1 , further comprising storing an outbound record for each to/cc/bcc combination used by each email user in outbound email messages. 
     
     
       3. The method for implementing email recipient templates as in  claim 2 , further comprising storing an inbound record for each to/cc/bcc combination used by each email user in incoming email messages. 
     
     
       4. The method for implementing email recipient templates as in  claim 3 , further comprising generating a unique template for each of the outbound and inbound records. 
     
     
       5. The method for implementing email recipient templates as in  claim 4 , associating a name field for each unique template. 
     
     
       6. The method for implementing email recipient templates as in  claim 5 , wherein the name field is either automatically generated based in part on the to/cc/bcc fields of the template or a custom generation from user or an administrator. 
     
     
       7. The method for implementing email recipient templates as in  claim 1 , further comprising receiving one or more email addresses in any one of the to, cc, or bcc fields. 
     
     
       8. The method for implementing email recipient templates as in  claim 7 , further comprising receiving input of a toggle button/key configured to retrieve associated email addresses. 
     
     
       9. The method for implementing email recipient templates as in  claim 8 , further comprising displaying each of the recipient template which include the one or more entered email addresses. 
     
     
       10. The method for implementing email recipient templates as in  claim 9 , further comprising receiving a selection of one of the displayed recipient templates. 
     
     
       11. The method for implementing email recipient templates as in  claim 10 , further comprising populating the to, cc, and/or bcc fields with email addresses from the selected recipient template. 
     
     
       12. A computer-readable memory having sets of instructions stored thereon which, when executed by a computer, cause the computer to:
 extract a set of email addresses from each outbound email message sent by a user, wherein the set of email addresses are included in one or more of the to, cc, or bcc fields of the email messages; 
 store, in a storage database, a template for each extracted set of email addresses, the templates comprising a first set of email addresses in a first recipient template and a second set of email addresses in a second recipient template, wherein the first recipient template and the second recipient template each have an associated unique identifier; 
 storing, in a dictionary maintained in the storage database, a unique index for each of the templates, the dictionary comprising a set of three lists, the lists comprising one list for the to field of email messages, one list for the cc field of email addresses, and one list for the bcc field of email addresses, and wherein storing the unique index for each of the templates in the dictionary comprises storing the index for each template in one or more of the lists based on which field the email address is extracted from; 
 receive a request for a new email message in an email editor user interface; 
 query the storage database for recipient templates using the dictionary, wherein the query is filtered by the associated unique identifiers; 
 receive the first recipient template and the second recipient template as a result of the query; and 
 display, in the email editor user interface, the email addresses associated with the first recipient template and the second recipient template. 
 
     
     
       13. The computer-readable memory as in  claim 12 , wherein the sets of instructions when further executed by the computer, cause the computer to receive one or more email addresses in any one of the to, cc, or bcc fields. 
     
     
       14. The computer-readable memory as in  claim 13 , wherein the sets of instructions when further executed by the computer, cause the computer to receive input of a toggle button/key configured to retrieve associated email addresses. 
     
     
       15. The computer-readable memory as in  claim 14 , wherein the sets of instructions when further executed by the computer, cause the computer to display each of the recipient template which include the one or more entered email addresses. 
     
     
       16. The computer-readable memory as in  claim 15 , wherein the sets of instructions when further executed by the computer, cause the computer to receive a selection of one of the displayed recipient templates. 
     
     
       17. The computer-readable memory as in  claim 16 , wherein the sets of instructions when further executed by the computer, cause the computer to populate the to, cc, and/or bcc fields with email addresses from the selected recipient template. 
     
     
       18. A system for implementing email recipient templates, the system comprising:
 a memory device; and 
 a processor coupled with the memory device, the memory device having sets of instructions stored thereon, which when executed by the processor, cause the processor to: 
 extract set of email addresses from each outbound email message sent by a user, wherein the set of email addresses are included in one or more of the to, cc, or bcc fields of the email messages; 
 store, in a storage database, a template for each extracted set of email addresses, the templates comprising first set of email addresses in a first recipient template and storing the second set of email addresses in a second recipient template, wherein the first recipient template and the second recipient template each have an associated unique identifier; 
 storing, in a dictionary maintained in the storage database, a unique index for each of the templates, the dictionary comprising a set of three lists, the lists comprising one list for the to field of email messages, one list for the cc field of email addresses, and one list for the bcc field of email addresses, and wherein storing the unique index for each of the templates in the dictionary comprises storing the index for each template in one or more of the lists based on which field the email address is extracted from; 
 receive a request for a new email message in an email editor user interface; 
 query the storage database for recipient templates using the dictionary, wherein the query is filtered by the associated unique identifiers; 
 receive the first recipient template and the second recipient template as a result of the query; and 
 display, in the email editor user interface, the email addresses associated with the first recipient template and the second recipient template.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.