Browse Prior Art Database

To avoid receiving duplicate Emails Disclosure Number: IPCOM000210672D
Publication Date: 2011-Sep-08
Document File: 3 page(s) / 67K

Publishing Venue

The Prior Art Database


The idea described in this article is to avoid receiving duplicate emails. We will receive many mails everyday and usually these emails will be sent from the same source but forward more than once. As a result we will see many duplicate mails in our inbox. Actually we may want to see so many duplicate mails but want the server or client to filter these duplicate ones. Our idea provides a method to filter these duplicate mails automatically.It will associate a unique identifier to every mails. The email client will do some proper check using this unique identifier when an email reaches and will ignore it if it is duplicate to a original one.

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

Page 01 of 3

To avoid receiving duplicate Emails

We receive many Emails everyday, but actually theremay be some duplicate Emails which is sent by the same person but forwarded by others more than once.Each time we may not want to receive these emails twice or more. We just hope the Email server or our clients to filter these duplicate Emails. As a result we will save much time of reading duplicate Emails as well as much space of the Email server. But we also want to read the additional contents which are added by the person who forwards it. That means we only want to filter the original E-mail's content but keep the content newly added.

There are no solutions.

In our invention a unique identifier will be bound to every sent email. When our inbox check new Emails from server, it will filter all the Emails which have the same identifier and do proper actions. Using our invention will save your space for storing received email as well as your time of reading duplicate emails.

Our invention works like this:
(1) When we send an Email to a contact list which includes several persons, the Email client will generate a unique identifier, and then this identifier will be bound to this email and sent to the receiver together with the Email itself.
(2) When the recipient receives this Email, it will get this identifier and store it to its local repository. The local repository is a list which contains all the identifiers that this client received.
(3) If one of these recipients wants to forward this Email to others, generally he will click the forward button. After he clicks forward button, the Email client system will generate a unique identifier for this forwarded Email. Also together with the original E-mail's identifier this two identifiers are both sent to the recipient. But the content of this forwarded Email will be divided into two parts. Content which belongs to the original Email will be associated with the original E-mail's identifier, and the left content will be associated with the new identifier.
(4) The recipient check Email from the server, it will firstly get the identifier bound to every Email. These identifiers will be compared to its local identifier repository. If same identifier is found the client will filter the corresponding email and delete the conte...