WO2002011025A2 - System and method for verifying delivery and integrity of electronic message - Google Patents
System and method for verifying delivery and integrity of electronic message Download PDFInfo
- Publication number
- WO2002011025A2 WO2002011025A2 PCT/US2001/023565 US0123565W WO0211025A2 WO 2002011025 A2 WO2002011025 A2 WO 2002011025A2 US 0123565 W US0123565 W US 0123565W WO 0211025 A2 WO0211025 A2 WO 0211025A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- message
- server
- sender
- agent
- identity
- Prior art date
Links
- 238000012384 transportation and delivery Methods 0.000 title claims abstract description 248
- 238000000034 method Methods 0.000 title claims description 224
- 238000012795 verification Methods 0.000 claims abstract description 21
- 230000004044 response Effects 0.000 claims abstract description 7
- 230000005540 biological transmission Effects 0.000 claims description 28
- 238000012790 confirmation Methods 0.000 claims description 19
- 230000032258 transport Effects 0.000 claims description 13
- 238000004891 communication Methods 0.000 claims description 9
- 238000010200 validation analysis Methods 0.000 claims description 8
- 238000004422 calculation algorithm Methods 0.000 claims description 7
- 238000012546 transfer Methods 0.000 claims description 5
- 230000000694 effects Effects 0.000 claims description 3
- 230000000737 periodic effect Effects 0.000 claims description 3
- 230000000717 retained effect Effects 0.000 claims description 2
- 241001108995 Messa Species 0.000 claims 1
- 230000006870 function Effects 0.000 description 25
- 238000010586 diagram Methods 0.000 description 20
- 238000012545 processing Methods 0.000 description 13
- 238000012012 milestone trend analyses Methods 0.000 description 12
- 230000008901 benefit Effects 0.000 description 8
- 230000008859 change Effects 0.000 description 8
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 5
- 229910052799 carbon Inorganic materials 0.000 description 5
- 101001094649 Homo sapiens Popeye domain-containing protein 3 Proteins 0.000 description 4
- 101000608234 Homo sapiens Pyrin domain-containing protein 5 Proteins 0.000 description 4
- 101000578693 Homo sapiens Target of rapamycin complex subunit LST8 Proteins 0.000 description 4
- 102100035477 Popeye domain-containing protein 3 Human genes 0.000 description 4
- 230000009471 action Effects 0.000 description 4
- 230000008520 organization Effects 0.000 description 4
- 238000007781 pre-processing Methods 0.000 description 4
- 102100024412 GTPase IMAP family member 4 Human genes 0.000 description 3
- 101000833375 Homo sapiens GTPase IMAP family member 4 Proteins 0.000 description 3
- 238000000151 deposition Methods 0.000 description 3
- 230000008021 deposition Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- GKSPIZSKQWTXQG-UHFFFAOYSA-N (2,5-dioxopyrrolidin-1-yl) 4-[1-(pyridin-2-yldisulfanyl)ethyl]benzoate Chemical compound C=1C=C(C(=O)ON2C(CCC2=O)=O)C=CC=1C(C)SSC1=CC=CC=N1 GKSPIZSKQWTXQG-UHFFFAOYSA-N 0.000 description 2
- 238000013478 data encryption standard Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000011156 evaluation Methods 0.000 description 2
- 230000010365 information processing Effects 0.000 description 2
- 238000007689 inspection Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000012805 post-processing Methods 0.000 description 2
- 241000237858 Gastropoda Species 0.000 description 1
- 101000942586 Homo sapiens CCR4-NOT transcription complex subunit 8 Proteins 0.000 description 1
- 101001094629 Homo sapiens Popeye domain-containing protein 2 Proteins 0.000 description 1
- 101000608230 Homo sapiens Pyrin domain-containing protein 2 Proteins 0.000 description 1
- 102100035482 Popeye domain-containing protein 2 Human genes 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
- 230000001131 transforming effect Effects 0.000 description 1
Classifications
-
- G06Q50/60—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/23—Reliability checks, e.g. acknowledgments or fault reporting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/234—Monitoring or handling of messages for tracking messages
Definitions
- This invention relates generally to a system and method for verifying delivery and content of an electronic message and, more particularly, to a system and method of later providing proof regarding the delivery and content of an e-mail message.
- E-mail has become an indispensable business tool.
- E-mail has replaced "snail mail" for many business practices because it is faster, cheaper and generally more reliable.
- hard copy is still dominant, such as registered and certified mail.
- a returned registered mail receipt adds the Postal Service's confirmation that the letter was successfully delivered to the addressee or the addressee's authorized agent.
- private couriers such as Federal Express® and United Parcel Service® (UPS) provide some type of delivery confirmation. Since every piece of courier mail is, in effect, registered it is natural for consumers to turn to these services when they want proof of delivery.
- e-mail systems and e-mail programs already provide for some form of proof of delivery. For instance., some e-mail systems today allow a sender to mark a message with "request for notifications" tags. Such tags allow a sender to request notification that the message was delivered and/or when the message was opened.
- the Internet e-mail system may provide the sender with an e-mail receipt that the message was delivered to the mail server or electronic inbox of the recipient.
- the receipt message may include the title of the message, the destination address, and the time of delivery.
- It may also include (depending on the types of "flags” that are provided and activated in the mailing software) a list of all the Internet "stations" that the message passed through en route to its destination. This form of reporting is built into some of the rules and protocols which implement e-mail. Furthermore, when a message is sent with a "read notification" request, the recipient's e- mail program may send to the sender an e-mail notification that the recipient opened that message for reading. Many electronic mail clients can and do support this kind of reporting; however, Internet protocols do not make this mandatory.
- a registration receipt from the United States Postal Service (USPS) constitutes proof of delivery because the USPS stands behind it.
- the receipt represents the Post Office's confirmation that the letter or package in question was actually delivered to the addressee or his authorized representative.
- various hurdles exist to an e-mail receipt being admitted and relied upon as persuasive evidence in a court of law as a proof that the message was delivered.
- the receipt may be just another e-mail message that could have been altered or created by anyone, at any time.
- senders may receive third party proof of delivery by enrolling in services whereby: a) The sender transmits an electronic message to a third party together with a list of the document's intended recipients. b) The third party sends a notification to each of the message's intended recipients inviting them to visit the third party's web site where the message can be viewed.
- some systems provide proprietary e-mail clients or web-browser plug-ins that will notify senders when a message has been received provided that a recipient uses the same.e-mail client.
- the obvious disadvantage of such systems is that they require both sender and recipient to use the same e-mail client. Therefore, there exists a need for an e-mail system/method that can provide reliable proof of the content and delivery of electronic messages which does not require the compliance or co-operation of the recipient, which requires no special e-mail software on the part of sender or recipient, which operates with the same or nearly the same convenience and speed of use as conventional e-mail, and which can be operated economically by a service provider.
- a general object of the present invention is to provide a system and method for reliably verifying via secure and tamper-proof documentation the content and delivery of an electronic message such as an e-mail.
- the invention will give e-mail and other electronic messages a legal status on a par with, if not superior to, that of registered United States mail.
- any particular legal status is accorded to messages sent according to the methods taught herein, as the invention provides useful information and verification regardless.
- the present invention includes an electronic message system that creates and records a digital signature of each electronic message sent through the system.
- An originator may send a copy of the electronic message to the system or generate the electronic message within the system itself.
- the system then forwards and delivers the electronic message to all recipients (or to the designated message handlers associated with the recipients), including "to" addressees and "cc" addressees. Thereafter, the system returns a receipt of delivery to the originator of the electronic message.
- the receipt includes, among other things: the original message, the digital signature of the message, and a handshaking and delivery history including times of delivery to the recipients.
- the originator or user sends a copy of the receipt to the system.
- the system then verifies that the digital signature matches the original message and the rest of the receipt. If the two match, then the system sends a letter or provides other confirmation of authenticity verifying that the electronic message has not been altered.
- the system may be a form of e-mail server connected to the Internet, which can be utilized in many ways. For instance, individual users can register their electronic messages, such as e-mails, by sending a "carbon copy" (cc:) to the system or composing the message within the system itself. For corporate or e-commerce users, these users can change their server to a server incorporating the present invention and have all of their external electronic messages registered, with the option of having the system retain and archive the receipts.
- the system can accept and verify encrypted electronic messages and manage the electronic messages within and/or outside a "fire wall.”
- web-based users i.e., individuals or corporations using web-based e-mails, such as MSN Hotmail® or Yahoo Mail®
- such users could check a box or otherwise set a flag within their e-mail programs to select on a case-by-case basis whether to register the e-mails and/ or to archive the messages using the present system.
- the digital signature can be created using known digital signature techniques, such as by performing a hash function on the message to produce a message digest and then encrypting the message digest. Separate digital signatures can be created for the body of the message, any attachments, and for the overall message including the body, the attachments, and the individual message digests.
- the encrypted message digest provides one type of message authentication or validation code, or secure documentation. Other message authentication and/or validation codes may also be generated and used.
- the invention is a method of providing proof regarding the delivery and content of an electronic message, comprising: receiving from a sender across a computer network an electronic message, the message having a delivery address associated therewith; computing a message digest according to the message; encrypting the message-digest; sending the message electronically to a destination corresponding to the delivery address; recording the Simple Mail Transport Protocol (SMTP) or Extended SMTP (ESMTP) dialog which effects the delivery of the message; receiving Delivery Status Notification information associated with the message and the delivery address; providing to the sender an electronic receipt, the receipt comprising: a copy of the message, the encrypted message digest, the (E)SMTP transcripts, and at least a subset of the Delivery Status notification information, and, at a future date, receiving electronically the electronic receipt from the sender, verifying that the encrypted message digest corresponds to the message, and verifying that the message was received by an electronic message handler associated with the delivery address.
- SMTP Simple Mail Transport Protocol
- ESMTP Extended SMTP
- the invention is a method of verifying delivery of an electronic message, comprising: in a wide area network computer system, receiving an electronic message from a message sender for routing to a destination address; establishing communication with an electronic message server associated with the destination address, the server defining a destination server; querying the destination server to determine whether the destination server supports Delivery Status Notification (DSN) functionality; receiving a response to the query, the query and response together defining an SMTP dialog; requesting Delivery Status notification information from the destination server according to results of the SMTP dialog; transmitting the electronic message to the destination address; receiving DSN information from the destination server with respect to delivery of the electronic message; and providing to the message sender at least a portion of the SMTP dialog, and at least a portion of the DSN information.
- DSN Delivery Status Notification
- the invention is a method of verifying content of a received electronic message, comprising: receiving the electronic message; generating a digital signature corresponding to content of the received message; providing the message and the digital signature to a designated addressee; and, at a later time, verifying that the digital signature corresponds to the message.
- the method includes establishing whether a message was electronically received by a recipient, comprising: providing a message to be dispatched electronically along with a recipient's address from a sender; creating a signature associating with the message; dispatching the message electronically to the recipient's address; tracking the message to determine a final Delivery Status of the message dispatched to the recipient's address; upon receiving final Delivery Status of the message, generating a receipt, the receipt including a copy of the message, the signature, and the final Delivery Status for the message; and providing the receipt to the sender for later establishing that the message was electronically received by the recipient.
- a method for proving that an electronic message sent to a recipient was read comprising: providing an electronic message along with a recipient's address; calculating a digital signature corresponding to the electronic message; dispatching the electronic message electronically to the recipient's address; requesting a Mail User Agent (email client "reading") notification from the recipient; upon receiving the reading notification, generating a reading receipt, the reading receipt including a copy of the message, the digital signature for the corresponding electronic message, and a second digital signature for the reading receipt from the recipient; and providing the reading receipt for later verification that said message was received by the recipient.
- a Mail User Agent email client "reading
- a method for validating the integrity of a purported copy of an electronic message comprising: receiving the purported electronic message copy, said purported copy including an encrypted message digest associated therewith; decrypting the message digest; generating a second message digest based on content of the purported copy; and validating the purported copy by comparing the decrypted message digest and the second message digest to determine whether the two message digests match.
- a method for validating a received registered e-mail comprising: receiving an electronic receipt, said receipt including a base message and an encrypted message digest; decrypting the encrypted message digest; generating a second message digest from the base message; and validating the e-mail if the decrypted message digest matches the second message digest.
- the invention is of a website at which users can go to send and receive secure messages, with the website host acting as an independent third party which will send and receive the messages and provide secure documentation regarding the content and delivery of the messages.
- FIG. 1 is a system diagram of a first embodiment of the present invention, in which outgoing messages are registered by being transmitted by a special Mail Transport Agent (MTA).
- MTA Mail Transport Agent
- FIGS. 2A-2F constitute a representative flow diagram for registering an outgoing e-mail according to the embodiment of FIG. 1.
- FIG.3 is a system diagram of a second embodiment of the present invention, in which senders may direct a Mail Transport Agent to transmit selected messages through a separate registering MTA.
- FIG. 4 is a system diagram of a third embodiment of the present invention, in which carbon copies (cc's) of outgoing messages are sent to a special server to be registered.
- FIG. 5 is a system diagram of a fourth embodiment of the present invention, in which users compose outgoing messages to be registered at a designated website.
- FIG. 6 is a system diagram of a fifth embodiment of the present invention in which users may send registered e-mails and store receipts from within a Web Based Mail User Agent (MUA).
- MUA Web Based Mail User Agent
- FIG. 7 is a flow diagram for validating a registered e-mail receipt.
- FIG. 8 is a system diagram of an embodiment of the present invention for registering incoming messages.
- FIG. 9 is a flow diagram for registering incoming messages.
- FIG. 10 is a flow diagram for validating received registered messages.
- FIG. 11 is a system diagram showing an exemplary use of the present invention by an e-business to register and acknowledge incoming and outgoing communications.
- RPost will refer in general terms to a third party entity which creates and/or operates software and/or hardware implementing the present invention, and or acts as a disinterested third party message verifier.
- the term is used for convenience of exemplary discussion only, and is not to be understood as limiting the invention.
- FIG. 1 is a system diagram of a first embodiment of the present invention, wherein outgoing e-mails are registered according to the present invention.
- the RPost registering server 14 serves as the primary outgoing Mail Transport Agent (MTA) for a message sender's Mail User Agent (MUA) 13.
- MTA Mail Transport Agent
- UUA Mail User Agent
- message recipient 18 is technically the addressee and is therefore merely the intended recipient or intended destination at this point in time, for simplicity of discussion this entity will be referred to herein as the recipient, addressee, or destination. Note that a single message may have many different destinations and that each of these may be reached through a different MTA.
- the method of sending registered messages may divided into three parts:
- Preprocessing Steps to be taken before a message is transmitted; 2 ) Transmission: The method of delivering messages to addressees; 3) Post Processing: Procedures for gathering information about messages after their delivery, the creation of receipts, and the validation of receipts.
- the RPost server On receiving a message for transmission, the RPost server will create records in a database for each message that will be used to store such information as: a) the time at which the message was received; b) the names of the attachments of the message; c) the number of addresses of the message; For each destination of the message the database will record: a) the name of the destination (if available); b) the internet address of the destination; c) the time at which the message was delivered to the destination's Mail Server; d) The Delivery Status of this destination Recipient Delivery Statuses used by the system will include:
- This status indicates that the message has been delivered to an ESMTP compliant MTA that supports Delivery Status
- DSN DELIVERED
- This status signifies that a DSN message has been received which indicates that the copy of the message sent to this recipient was delivered to the mailbox of the recipient RELAYED
- This status indicates that after repeated attempts RPost has been unable to connect to an MTA to deliver the messages to this recipient.
- FAILED This status signifies that an MTA DSN has been received that indicates a failure to deliver a copy of the message to this recipient.
- RPost server 14 employs a hash function and an encryption algorithm.
- the hash function may be one of any well-known hash functions, including MD2, MD5, the
- Hash algorithms and methods are-described in Brace- Schneider, Applied
- the hash function should be at least weakly collision-free, which means that, given a message x, it is computationally infeasible to find some input y such that H(x) - H(y). The consequence of this is that a would-be forger who knows the algorithm used and the resulting hash value or message digest will nevertheless not be able to create a counterfeit message that will hash to the same number.
- the hash value h returned by a hash function is generally referred to as a message digest.
- the message digest is sometimes referred to as a "digital fingerprint" of the message x.
- digital fingerprint the number of bits long in order to ensure that the results are secure and not forgeable.
- the recommended length for secure hash functions may increase.
- RPost server 14 computes a message digest for the message body, and a separate message digest for each of the attachments of the message and stores these in a manner in which they may be later included in a receipt for the message. Before the message is altered in the ways that registration will require, a copy of the original message and its attachments are stored in a manner in which they can be later retrieved by the system.
- the RPost server may alter a message in several ways before transmission to the recipient's MTA.
- the message may be tagged to denote the fact that the message has been registered, such as by inserting the word "Registered” or at the beginning of the "subject" line of the message, by appending a tag such as:
- the tag may contain instructions, World Wide Web addresses, or links that invite and allow the recipient to send a registered reply to the message by linking to a Web Page from which registered messages may be composed and sent.
- tagging is optional, the delivered message will generally be referred to herein as the tagged message.
- e-mails that are sent by a recipient's MTA notifying the nominal sender of the message that various events have occurred.
- MT As that conform to the SMTP protocol will typically only send a notification in the event that the mailer cannot deliver a message to the mailbox of the addressee (as might happen if the address is not valid or if the addressee's mailbox has exceeded its allotted storage quota).
- DSNs Delivery Status Notifications
- ESMTP Extended SMTP
- DSN is a term that only came into use with the advent of
- MUA NOTICES READING NOTIFICATIONS
- the RPost server 14 will configure and transmit messages in a way that attempts to elicit both MTA DSNs and MUA notices from compliant MTAs and' MUAs.
- certain headers must be included in the header section of an e-mail message. Different MUAs respond to different headers; hence Server 14 will add several different headers to each message requesting a read notification in a form recognized by various MUAs. These headers all take the form:
- Header label user name ⁇ user address> For example: Disposition-notification- to : John smith ⁇ jsmith@adomain . co ⁇ t ⁇ > read-notification- to : ohn smith ⁇ jsmith @ adomain . com> where 'john smith' is the name of the user to whom an MUA notification is to be sent and ! ⁇ jsmith@adomain.com>' is that user's Internet address. Normally such headers would refer to the author of the message but in the case of the present method it is required that the notification be returned to RPost so that the notification can be processed by RPost.
- Server 14 will insert headers that request that MUA receipts be sent to an address where they can be processed by the RPost server, for example: "readreceipt@RPost.com”. This will direct any compliant recipient MUAs to send their notifications to an RPost address for processing.
- MUA notifications raises another problem that must be dealt with at this stage.
- the system receives a MUA notification it must be able to identify the message that prompts it, so as to include the notification information in the receipt that RPost will generate.for.the sender.
- the system must at least be able to reliably identify the sender of the message to which the MUA notification refers so that the notification information can be passed on to the sender in the form of an RPost Reading receipt (see below).
- the system can take advantage of the fact that internet addresses have two components: a name field and an address field, where the address field is set off by corner quotes "o". Most MUAs will include both fields in the destination address of their MUA notifications.
- the RPost system will include the Server 14 read receipt-handling address as the address for the notification but will use the address of the original sender in the name field of the header. For example, where the original sender of the message is user John Smith with Internet address i smith@adomain.com, the RPost server will include headers of the form:
- Disposition-noti ication- o j smith@adomain . com ⁇ readreceipts @ EFos . co >
- the server can, by parsing the addressee's field, determine that the notification concerns a message originally sent by fsmith(a).adomain. com, even if this could not be determined by any examination of the contents of the notification. With this information in hand, the server can then package the contents of the notification in a digitally signed RPost Reading receipt and send the receipt to the address j smith@adom.ain. com
- the RPost system will also endeavor to elicit and collect MTA DSN notices generated by recipient MTAs. Since such notifications are always sent to the address listed in the "FROM:" field of the message header, server 14 must alter each message header so that the message is received as "FROM:” an RPost address at which DSNs may be processed.
- DSNs do not have any standard content ozibr at; often it is impossible to determine, merely by examining the contents of these e-mails, what message their, contents are giving notification of.
- This problem was supposed to have c been addressed for DSNs generated in compliance with the ESMTP protocol by the use of DSN envelope ID numbers (see RFC 1869).
- a transmitting MTA can include a reference number along with its request for a DSN. This number would be quoted in any returning DSN, allowing the sender to identify the subject message of the DSN.
- the MTA for the domain may report these events in a DSN in ways that provide no way for the recipient of the DSN to determine which addressee was successfully delivered and which was not (as, for example, may happen if the DSN reports the recipient's addresses as their local alias names rather than by the addresses contained in the original message).
- the present invention solves this problem in four steps: 1) A unique identification number is generated for each outgoing message (e.g. based upon a time stamp). This number is stored in a database.
- the upshot of this form of addressing is that when the recipient MTAs issue DSNs (whether ESMTP compliant or not) they will address those DSNs to different RPost addressees.
- Server 14 can identify them as DSN messages by their "RCPT" prefix and, by parsing the addressees, can determine which message and which recipient is the subject of the DSN.
- System 14 will alter the 'FROM' field of each message to refer to a recipient of the message each time it attempts to transmit the message to that recipient's MTA. To insure that recipient replies to transmitted messages are directed properly system 14 will add an explicit "reply -to:" message header into the message listing the original sender's name and Internet address. In the case of the present example this would be:
- the RPost server transmits a separate copy of an outgoing message to each addressee of that message. Moreover RPost will attempt to make each such delivery through a direct SMTP connection with a mail eXchanger (MX) of record for each destination.
- MX mail eXchanger
- Each valid Internet e-mail address includes an Internet domain name or IP address.
- Each domain name/ address has associated with it an e-mail server(s) authorized to receive mail for addresses in that domain. It will be noted that some, domains have more than one server.
- the Domain Name Server responsible for each domain broadcasts the identity of its mail servers across the Internet. This information is publicly available and is managed and transmitted in ways that conform to rules and conventions which- govemTnternet e-mail and Doma Name service.
- the RPost server Before transmitting a copy of a message to any destination the RPost server will perform an Internet Name Server Lookup to identify an MTA associated with the destination's domain. Having identified the MTA responsible for receiving mail on behalf of a destination address, the system will attempt to open a telnet connection with the destination's local MTA.
- RPost will have delivered the message to an agent the recipient has legally authorized to receive his mail.
- RPost can claim to have proof of delivery to the recipient's authorized agent.
- the RPost server will attempt to open an ESMTP connection with the destination MTA by issuing an "EHLO" handshake in compliance with RFC 1869. If SERVER 16 supports ESMTP, it will respond by listing which ESMTP services it supports.
- the RPost server will first determine if SERVER 16 supports the ESMTP Service "VERIFY".
- the Verify service allows a calling SMTP server to determine, among other things, if an address in an MTA's domain is genuine. If the RPost Server determines by these means that the address it is attempting to deliver its message to is not valid, it will terminate the connection, cease attempting to deliver a message to this addressee, and record, in its database, the status of this message destination as UNDELIVERABLE. Whatever its result, the RPost Server will record the ESMTP VERIFY dialogue in a file and store it so that it may be later attached to or included in the Delivery Receipt for this message.
- the RPost server will then attempt to determine if the destination server supports the ESMTP service DSN. If it does, RPost will transmit the message with a request that SERVER 16 notify the sender of the message ' wim an ESMTP DSN if the delivery to the addressee succeeds or fails. After the successful transmission of the message to this destination the system will record the Delivery Status of this destination as DELIVERED-WAITING-FOR-DSN. If Server 16 replies to the "EHLO" handshake in a way that indicates that it does not support ESMTP, the RPost server will issue a "HELO" message to initiate an SMTP connection.
- the RPost server will transmit the message in compliance with the- SMTP protocol and will -record the Delivery Status of the destination as DELIVERED. Whether the connection is SMTP or ESMTP, the RPost server will record the entire protocol dialogue between the two servers. Typically this dialogue will include protocol messages in which, among other things, the destination server identifies itself, grants permission to upload a message for a named recipient, and acknowledges that the message was received. RPost will save the record of this transaction in such way that it may be later retrieved and included in or attached to the RPost Delivery Receipt for this message.
- RPost may not be able to achieve an SMTP connection with an MTA of a recipient or it may achieve such a connection but be denied permission to transmit the message by the recipient.
- the RPost server will attempt to deliver its message to each of these in turn.
- RPost will continue to attempt to deliver to an appropriate MTA as often as system resources permit. If, after a length of time, RPost cannot deliver the message to an address, it will mark the status of this recipient of this message as "UNDELIVERABLE" and stop attempting to send this message to this destination address.
- RPost When the RPost server succeeds in transmitting a message to a destination Server that explicitly supports ESMTP DSN, RPost will record the status of this recipient for this message as "DELIVERED-AND-WAITING-FOR-DSN".
- RPost server When the RPost server succeeds in transmitting a message to the destination Server via a connection that does not explicitly support ESMTP DSN, RPost will record the status of this recipient for this message as "DELIVERED.”
- MTA DSNs will be returned to the RPost Server addressed to fictitious addresses in its proprietary domain (e.g. "RPost.com"), these addresses having been constructed as described above.
- the RPost server will scan all inbound mail addressed to the domain and detect DSN messages by their identifying substring (e.g. "rcpt"). By parsing these addresses in the manner described above, the system can identify the message and the recipient that has prompted the DSN notification.
- the system always delivers mail to a proprietary MTA for the destination's domain, these MTAs will sometimes relay the message to a different server (as may be the case, for example, if the receiving MTA sends mail behind a firewall).
- the DSN will contain such phrases as "relayed” or “relayed onward”. In such cases the system will change the recipient's Delivery Status to "RELAYED".
- the system Having evaluated the DSN and updated the recipient's Delivery Status accordingly, the system will save the DSN and any attachments it may contain in such a way that this message(s) may be included in and/or attached to an RPost Delivery Receipt.
- DELIVERED This status indicates " that a copy of the message for this recipient has been delivered to an MTA that does not support ESMTP DSN. Such an MTA may nevertheless send a form of Delivery Status Notification in the event that the message could not be delivered to the Mailbox of the addressee
- the system will not treat the delivery for such a recipient as completed until a period of time has elapsed since the delivery to the recipient MTA.
- This time period typically two to twenty- four hours— represents an estimate of the maximum time required for a majority of servers to return a notification of a failure to deliver and it may be adjusted if the specific destination domain is remote or known to be prompt or tardy in producing such notifications.
- DELIVERED-TO-MAILBOX This status indicates that a DSN indicating successful delivery has been received for this recipient and hence the delivery of the message to this destination is completed.
- FAILED, UNDELINERABLE Deliveries to recipients with this status are always treated as complete.
- Delivery receipts are e-mails sent to the original-sender of the Registered message.
- the receipt 20 may contain:
- This identifier may be or may include reference to the sender's ID and/or the value of the Internet Message- ID of the sender's message as received by the system; 2. the date and time at which the receipt was generated;
- Delivery Status quoted in a Delivery Receipt is based upon the system's internal record of the destination's Delivery Status. They may be transcribed as follows: • Deliveries to destinations whose status is FAILED or UNDELINERABLE will be recorded in the receipt as "failed”.
- any files that were returned to the system as attachments to DS ⁇ reports. All of these separate elements of the receipt may have their own message digests or digital signatures included within the receipt. Additionally, the receipt may include a single overall encrypted message digest or digital signature computed and appended as part of the receipt, thus providing a single message authentication code which could be used to authenticate all of the information contained within the receipt. Since the receipt itself and SMTP dialogs and DS ⁇ reports within the receipt contain timestamps, the receipt includes a non-forgeable record of the message recipient(s), the message content, and the time(s) and route(s) of delivery. MUA Notification Processing MUA Notifications could be collected and incorporated within RPost Delivery receipts in the same manner as MTA DSNs.
- MTA notifications are typically issued by receiving MTAs within a few hours of delivery whereas MUA Notifications will not be generated, if ever, until the recipient opens his MUA e-mail client and takes some action with respect to the received mail. For this reason, in this embodiment of the invention MUA notifications are collected separately from MTA notifications and reported in "RPost Reading Receipts" separate from RPost Delivery Receipts.
- MUA notifications elicited by message headers constructed in the manner described above will be returned to a common RPost address (e.g. "readreceipts@RPost.com") and each notification will contain- in the name field of its address- the address of the original sender of this message. Because this is the only information required to generate an RPost reading receipt in the manner described below, the system can deal with MUA notices whenever these notices may arrive and without any need to have stored any information about the original message in its databanks.
- MUA notices may report, among other things, that a message has been read by a recipient, that a message has been displayed on the recipient's terminal (whether or not read), that a message has been deleted without having been opened.
- MUAs are not evaluated or interpreted by the RPost server but are, instead, passed on to the sender for his own evaluation in a form that can be authenticated by RPost. To accomplish this the system will create an e-mail message styled as an "RPost Reading Notice" which may include, among other items: 1. subject line of the received MUA notice;
- both RPost delivery receipts and Reading Notices are sent to the original sender of the registered message. Since these receipts are digitally signed with an encrypted hash, RPost can authenticate the information contained in these messages any time they are presented to RPost for this purpose, in the manner described below. This means that once it has transmitted a copy of the receipt to its sender (with instructions to the sender to retain the receipt for his records), RPost has no furfherneed to retain, any data concerning the message or its delivery and may expunge all such records from its system. Thus, RPost need not keep any copy of the original message or the receipt.
- third party verifier RPost may, perhaps for an additional fee, store a permanent copy of the receipt or of some or all receipt data.
- the receipt orpart(s) thereof may be kept on any suitable archival storage devices including magnetic tape, CD ROM, or other storage device types.
- RPost may return receipts or parts thereof to a storage system devoted to this purpose within the control of the sender or the sender's organization.
- RPost receipt information includes all of the data from the original sender's message and its attachments.
- the originator of a message requires evidence at a later date that an e-mail was sent, delivered, and/or read, the originator presents the receipt(s) for the message to the operators of the system.
- sender 10 sends to RPost a copy of receipt 20 with a request to verify the information contained within the receipt. This could be done by sending the receipt to a predefined mailbox at RPost, e.g., verify@RPost.com.
- RPost determines whether or not the receipt is a valid receipt.
- a receipt is a valid receipt if the digital signature matches the remainder of the receipt, and the message digests match the corresponding respective portions of the original message.
- RPost performs the hash function on the various portions of the message including the message body, the attachments, and the overall message including the SMTP dialog and DSN reports, to produce one or more message digests corresponding to the purported message copy.
- RPost compares the message digests in the purported copy, including the overall message digest, with- the message digests which RPost has computed from the purported message copy.
- the overall message digest can be compared by either decrypting the overall message digest received as the digital signature in the purported receipt, or by encrypting the overall message digest which was calculated from the purported message copy. If the message digests including the digital signature match, then the receipt is an authentic RPost-generated receipt.
- the receipt must have been a receipt that was generated by RPost, and therefore the message contained in the receipt, the to/from information, the date and time of delivery, the fact of successful delivery, the route by which the message traveled, and any DSN information contained within the receipt, must be a true copy of that information and is accurate.
- RPost can then provide authentication, verification, and confirmation of the information contained within the receipt.
- This confirmation can take the form of an e-mail confirmation, affidavit testimony from RPost employees familiar with the methods used by RPost, live sworn testimony in depositions and in court, and other forms of testimony.
- RPost can charge sender 10, recipient 18, or any other entity, fees for the various respective confirmation services.
- RPost can also provide testimony or other confirmation with regard to the non- authenticity of a purported receipt.
- Testimony may be provided in accordance with Federal Rules of Evidence 901(9), 901(10), 803(6), 803(7), 1001-1004, 1006, 702-706, corresponding state rules of evidence, and other applicable rules.
- the system provides reliable evidence based on the testimony of a disinterested third party that a particular message having a particular content was sent, when it was sent, who sent it, who received it, when it was opened for reading, and when it was deleted.
- This evidence can be presented any time a dispute arises regarding the content and delivery of messages, as for example in contract formation, the timing of stock buy or sell orders, and many other applications.
- the operators of the system can attest to the accuracy of the information contained in the receipt itself without the need for the operators to preserve any record or copy of the information contained in the receipt.
- the RPost Sever registers the delivery of all messages passing through it.
- an RPost server might register only those messages having certain destinations (e.g. external to an organization) or from certain senders (e.g. a customer relations group).
- the RPost server might register only those messages that had distinguishing characters or strings in the subject or body of the message. For example, the server might register only messages that the sender had included "(R)" in the subject of the message. All other messages might be delivered by the RPost Server or some other server function as an ordinary Internet MTA.
- RPost can raise revenue in a variety of ways. For instance: RPost can charge message sender 10 or her organization a fee on a per-message basis, on a per-kilobyte basis, on a flat fee periodic basis such as monthly, or on a combination of the above. RPost can also charge fees for authenticating and verifying a receipt, with a schedule of charges depending on whether the verification sought is a simple return e- mail, a written affidavit or declaration, sworn fact testimony in deposition or in court, or sworn expert testimony in deposition or in court. If the users opt to have RPost retain copies of the receipts, RPost can charge per item and /or per-kilobyte per month storage fees.
- FIGS.2A-2G constitute a flow chart showing an exemplary operation of the first embodiment of the system. Modifying this flow chart to apply to other embodiments is within the skill of one familiar with software and e-mail protocols.
- FIG 3 A Pre-processing, illustrates the steps taken with a message before it will be transmitted by the Registering Server (the System).
- an originator/sender/user creates an e- mail message using any Internet Mail User Agent (MUA).
- MUAs include: (1) client side e-mail programs; (2) server based e-mail programs; (3) web based e-mail services; and (4) HTML forms submitted through web pages.
- the message may contain attached files as described in the Requests for Comments (RFCs) 822, 2046, and 2047, which are hereby incorporated by reference.
- RFCs are a series of notes regarding the Internet that discuss many aspects of computer communication, focusing on networking protocols, procedures, programs, and concepts.
- the system functions as the sender's outgoing mail server and hence the sender's message will be directly transferred to the RPost Server by the sender's MUA (step 202).
- step 203 the system creates a copy of the original message to be stored for ' later processing.
- the system creates a record in a database which may include such information as: the time at which the message was received by the server, the names and size(s) of the file attachment(s) of the message, the name (if known) of each destination of the message; the internet address of each destination; the time at which the message was delivered to the destination's MTA (initially this value is null) and a unit which records the Delivery Status of eachrdestination.
- step 205 the Delivery Status of each destination is set to "UNSENT".
- step 206 the system generates and stores a message digest or digital fingerprint generated from the message body.
- step 207 the system generates and stores a hash or message digest for each attachment included in the message.
- step 208 the system may create a modified copy of the original message. In this second copy (step 209), the original subject line of the message may be amended to indicate that this copy is registered (e.g. by pre-pending "Registered").
- step 210 a notice that the message is registered by the system together with links to the system's Word Wide Web site may be appended to the body of the message.
- the e-mail headers may be added requesting reading notification in a variety of header formats recognized by various MUAs.
- the requests for notification direct the return notification to an address associated with the system: for example, "read eceipt@,RPost . com" .
- These headers will also include the address of the original sender of the message in the name field of the address to which the MUA notification should be sent.
- the system will now transmit a copy of the message to each of its destinations as illustrated in FIG 2B.
- Fig 2B illustrates the steps required to transmit a registered message. As step 220 indicates, the process requires a separate transmission for each recipient of the message.
- step 221 the system changes the header field of its working copy of the message to show the message as being "FROM:" a sender whose name is the original sender of the message but whose address is an "RPost.com” address constructed from: a) a string used to identify returning MTA notifications (e.g. "RCPT"); b) a string which uniquely identifies the message being sent; c) a tag which uniquely identifies the destination this copy of the message is being sent to.
- a string used to identify returning MTA notifications e.g. "RCPT”
- a string which uniquely identifies the message being sent e.g. "RCPT”
- a tag which uniquely identifies the destination this copy of the message is being sent to.
- step 222 using the domain name of the destination currently being sent to, the system does a Domain Name Server Mail exchange lookup to find the address of the MTA(s) responsible for collecting mail for addresses in this domain.
- step 223 the system attempts to make a direct telnet connection to the MTA of the destination. If the connection fails, the system will try to make the connection again.
- the system will try to remake the connection perhaps using another MX sever for the destination's domain (228).
- step 226 If, after a maximum number of retries, the system cannot connect to an MTA for this destination, the system will, as in step 226, record this destination's Delivery Status as "UNDELINERABLE" and cease attempting to deliver this message to this destination.
- the system On connecting to the destination's MTA, the system will begin making a record of its (E)SMTP dialog with the MTA (225). In step 229, the system attempts to initiate an Extended SMTP (ESMTP) exchange with the destination MTA by issuing an "EHLO" greeting.
- ESMTP Extended SMTP
- the system will then (230) determine if the destination MTA supports the SMTP function VERIFY. If the MTA supports VERIFY, the system will attempt to determine if the destination address is a valid address within the domain (231).
- step 232 the system will record the Delivery Status of this destination as "FAILURE" and will cease attempting to deliver this message to this destination.
- the system will then (233) determine if the receiving MTA supports the ESMTP service DS ⁇ (Delivery Status Notification).
- the system will transmit the message with ESMTP requests to notify the nominal sender of the message of delivery success or failure (234). Having transmitted the message, the system will record the Delivery Status of this destination as "DELIVERED-AND-WAITING-FOR-DSN" (235).
- the system will transmit the message using SMTP (236) and record the destination's status as "DELIVERED” (237).
- the system will then store the (E)SMTP dialog, recording the delivery in a manner in which it can later be recovered (238) and attempt to send the message to another destination.
- Fig. 2C illustrates the process by which the system processes MTA Notifications returned by recipient MTAs.
- MTA message notifications will be delivered to a fictional local address at the server.
- the system will be able to detect these notifications by a string (e.g. "rcpt" embedded in their addresses (241). By parsing the address, as illustrated in 242, the system can determine which message to which destination prompted the received notification.
- step 243 the system scans the subject line and the body of received MTAs for phrases that indicate whether the MTA is reporting a successful delivery, a failed delivery, or that the message has been relayed to another server.
- step 245 change the Delivery Status of the relevant destination of the relevant message to "DELIVERED-TO-MAILBOX". If the system determines that the MTA notice is reporting a delivery failure, the system will (247) change the Delivery Status of the relevant destination of the relevant message to "FAILURE".
- step 249 change the Delivery Status of the relevant destination of the relevant message to "RELAYED".
- the system will save this message and all of its attachments in such manner that they may be later recalled and used in construction of a receipt for this destination (250). From time to time, as illustrated in Fig. 2D, the system will examine the status of each message to determine if the system has recovered all of the MTA notifications it is likely to receive for each destination of message and may hence proceed to construct a receipt for the message.
- the system will examine the Delivery Status of each destination of the message. If any destination has the Delivery Status "UNSENT", then the processing of the message is not complete. (252).
- the system will not regard the processing for this destination as complete unless, as is illustrated in step 254, the time since delivery of the message has exceeded the system's waiting period (e.g. 24 hrs.).
- the system will regard the processing of this destination as complete provided (258) that a period of time has elapsed which the operators of the system treat as sufficient to have received notice of delivery failure from the destination's MTA. (e.g. 2 hours).
- Any other destination Delivery Status (e.g. "FAILED”, “UNDELIVER-ABLE”, “DELIVERED TO MAILBOX”) is treated as having completed processing. If processing of any of a message's destinations is not complete the system takes no action but moves to consider other messages in the system (step 255).
- the system will generate a Delivery Receipt for the message.
- the receipt may include: An identifier for administrative purposes as in block 271. This identifier may be or may include reference to the sender's ID and/or the value of the Internet Message-ID of the sender's message as received by the system.
- the quoted body of the original message 12 together with the e-mail addresses of its intended recipients may also be included.
- a table for each recipient listing may include: • the time at which the recipient's MTA received the message and/or the time at which the system received DSN from the recipient's MTA; • the Delivery Status report of the message for that destination, i.e., "Delivered to Mail Server", “Delivered to Mail Box”, “Relayed”, “Delivery Failure”, “Undeliverable”; As in block 274, a list of the original attachments of the e-mail together with their separate hash values or message digests. As in block 275, transcripts or abstractions of the transcripts of all of the SMTP dialogs involved in the delivery of the message to each destination.
- the system may attach to the receipt copies of all of the attachments of the original message, and, as in block 278, the system may additionally attach files returned to the system as attachments to DSNs.
- step 279 having generated the text of the receipt so far, the system then generates a first hash for the e-mail message and a second hash(es) for any attachments to the body of the receipt and calculates a digital signature for each of the hash(es) using an encryption key known only to the operators of the system. Encryption can employ, for example, the Data Encryption Standard described in Federal Information Processing Standard Publication 4-2 (FIPS PUB 46-2), the Data Encryption Standard, National Institute of Standards and Technology, which is hereby incorporated by reference. Alternatively, other known or new methods of encrypting the hash value may be used.
- step 280 the encrypted hash is then appended to the end of the message as the "document digital signature".
- step 281 the receipt 20, now being complete, may be sent by e-mail to the sender with the advice that it be kept for the sender's records.
- step 282 the system may now delete all copies of the original message, attachments, and DSNs.
- the system may store the receipt, or both the sender and system can store the receipt.
- embodiments of the system may choose to treat these return messages differently than MTA notifications.
- FIG. 2F illustrates how these MUA notifications may be treated by the system.
- MUA notifications are solicited by- the system by including various headers in outgoing messages in the manner of Fig 2 A, step 211.
- These headers direct compliant MUAs to send notifications to a system address (eg. "readreciept@RPost.com") set aside for this purpose.
- the headers also use, in the "name" field of this return address, the e-mail address of the original sender of the message. Accordingly, in step 286, when MUA notifications are returned to readreceipt@RPost.com the system can, by examining the address of the notification, determine the address to which a reading notification should be sent.
- the system Upon the arrival of a read receipt from a destination's MUA, the system, in step 287, generates a reading receipt that contains the subject of the received MUA notification as its subject and incorporates, in its message body, the body of the received MUA Notification.
- step 288 the system attaches to the receipt any files that may accompany the MUA's receipt (typically these may include details of delivery or disposition and identifying references to the original e-mail.)
- step 289 the system generates a hash for any files attached to the receipt and records this hash in the body of the receipt.
- step 290 the system generates a hash for the body of the receipt and its attachments, encrypts this hash, and appends the result to the message as a "document digital signature".
- step 291 the system sends the resulting receipt to the sender of the message.
- step 292 having sent this receipt, the system may delete all internal records of the transaction.
- FIG 3. is a system diagram of a second embodiment of the present invention wherein the RPost server does not serve as the user's primary MTA but rather works in collaboration with another MTA.
- the sender may elect to register a particular outgoing message by including some form of flag in an outgoing message, message subject, or message addresses. For example, if and only if a sender includes the symbol "(R)" in the subject of the message the sender's MTA will direct the message to be transmitted through the RPost server to generate a receipt.
- the operators of RPost receive revenues from the operator of the sender's MTA per message and/or per kilobyte transmitted.
- FIG. 4 is a system diagram of a third embodiment in which a carbon copy (“cc") is sent to the RPost server.
- the user or message sender 10 can use a standard MUA and standard MTA without modification.
- Message sender 10 composes the e-mail having- a message body and any number of attachments, and addresses it to message recipient 18, along with any carbon copies (cc's) and blind carbon copies (bee's) as desired. Additionally, message sender 10 addresses a cc to RPost.
- RPost server 14 tags the message as before, and sends the tagged message including attachments to the recipient's MTA 16 and any designated cc's. On receipt of such a copy RPost Server 14 may send an e-mail acknowledging receipt of the copy.
- Recipient 18 and other destinations of the message will now receive two versions of the same message: a first version of the message received directly from sender 10, and a second and tagged version which was forwarded from RPost.
- RPost server 14 composes message receipt 20 as before and sends the receipt to sender 10 for his records.
- Revenue can be generated by establishing accounts for message originating domains or individual message senders, and charging the users' accounts per message, per kilobyte, per month, or a combination of these. Revenue can also be generated for the placement of advertisements on receipts and from authentication and verification services as previously described. V. WEBSITE EMBODIMENT
- FIG.5 is a system diagram of a fourth embodiment.
- RPost server 14 is associated with a website at which a user composes messages.
- Message sender 10 visits the RPost Website and composes his message at the website by entering the desired "to", “cc", “bcc", “Subject”, and message text information. Attachments can be added by using features available on standard browsers and web servers.
- the sender must additionally provide an address to which the registration receipt may be sent.
- RPost server 14 sends the receipt to sender 10 through sender's MTA. Revenue can be generated by establishing accounts for message originating domains or individual message senders, and charging the users' accounts per message, per kilobyte, per month, or a combination of these. Revenue can also be generated for the placement of advertisements on receipts- and from authentication and verification services as previously described.
- FIG. 6 is a system diagram of a fifth embodiment.
- the RPost server 14 is associated with a web based Mail User Agent.
- MUA provides subscribers with browser viewable mailboxes that display messages stored on the Web server site. Subscribers to such a service gain access to mail accounts with usernames and passwords.
- message sender 10 visits the RPost Website, accesses a Web Based e-mail account by entering a username and password, and composes his message which is transported for delivery to RPost Server 14. Receipts generated by the RPost server are returned to a web based mailbox associated with the subscriber's account.
- the operators can charge storage fees for receipts held in the web based mailbox.
- the receipt may serve as evidence that: (1) the originator sent an e-mail message;
- the recipient took certain actions in response to the message, e.g., read or deleted.the e-mail, at a particular time.
- this embodiment produces documented evidence which may be attested to and verified by the disinterested third party operators of the system of the delivery and integrity of an electronic message.
- the system can be thought of as transforming the e-mail to a registered e-mail that can later be used to prove that a particular e-mail message was sent, that it was successfully delivered, and whemancLhow.
- the dispute can be resolved through the receipt generated by the system because the receipt is so encoded that the operators of the system can determine the authenticity of the receipt as the product of the system. Thereafter, operators of the system can attest to the accuracy of the information contained in an authentic receipt, relying only on information contained in the receipt itself and without the need for the operators to preserve any record or copy of the information contained in the receipt.
- the receipts generated by the system may also be useful- as evidence of the existence and authorship of such materials as might be transmitted through the system.
- the system is easy to use, as the system can be used from any Internet e-mail client program MUA, so that there is no additional software required.
- FIG. 7 is a flow diagram illustrating an exemplary method for validating a receipt.
- the sender of a message should require evidence that an e-mail was sent and delivered (and/or read) the sender presents the receipt(s) corresponding to the message to the operators of the system in step 700.
- the operators of the system then, in step 702, detach and decrypt the document digital signature appended to the receipt.
- the operators generate a hash of the balance of the document, including attachments.
- step 704 if the current hash value does not match the decrypted hash value, then the system generates a report stating that RPost cannot authenticate the receipt as an accurate record of the delivery or the contents of the message described in the receipt.
- the system can, as in step 706, warrant that the information contained in the body of the message is unchanged since the receipt passed through the system. If the original message contained no attachments, the system may now generate a report that warrants that the receipt is an accurate record of the message's contents and its delivery by the RPost Server.
- the receipt will also record the name and hash value of each attachment. In generating the receipt all attachments of the original message are attached unchanged to the receipt.
- the system will, for each such attached file, generate a hash of the attached file (708) and compare it to the hash value recorded in the body of the receipt (709).
- the system can warrant that the file attached to the receipt is identical to that attached to the message as originally delivered. If the hashes do not match, then the system will report that it cannot warrant that the file attached to the receipt is identical to the file attached to the original message.
- the system Having performed this calculation for each file attached to the original message, the system prepares a report which reports on the authenticity of the receipt and each of its attached files (710) or which reports the failure of validation (712). Having completed its evaluation, the system will then append a copy of the receipt and all of its attachments to the report it has generated and send it via e-mail to the return address of the user who submitted the report for validation.
- FIG. 8 is a system diagram illustrating another embodiment of the invention in which incoming e-mails are registered.
- a message sender 60 sends an e-mail message 70.
- Sender's MTA 62 sends message 70 onto the Internet as usual.
- NSI Network Solutions, Inc.
- MX server mail recipient
- RPost server 64 acts as an SMTP, POP, POP3 or IMAP MTA (collectively, "POP mail server") for recipient 68.
- SMTP, POP and IMAP MTAs are governed by RFC 821, the SMTP protocol, RFC 1939 Post Office Protocol - Version 3 (which obsoleted RFC 1725), and RFC 2060 IMAP (Internet Message Access Protocol) Version 4 rev 1 (which obsoleted RFC1730), which are hereby incorporated by reference.
- RPost Server 64 prepares a registered version 74 of the original message 70, and places this registered version 74 into recipient 68 's in-box instead of, or in addition to, the original message 70.
- the registered version may have all of the verification and informational features and options discussed earlier in connection with e-mails receipts. This information can include, but is not limited to: individual message digests for each of the message body and text, the to/from information, other header information, each attachment, an overall message digest and digital signature and message routing information andiags.
- Registered version 74 of message 70 as shown in FIG. 6 includes the message body including the header information, an attachment, separate message digests for each, and a digital signature or encrypted message digest.
- the hash functions and encryption are performed using private phrases or private keys known only to the operators of the system.
- the registered version 74 is made available to recipient 68 for inspection or downloading through the recipient's MUA.
- RPost server can optionally send a confirming e-mail 72 to message sender 60.
- Confirmation message 72 can be a simple text message indicating that a message was received and registered.
- Confirmation message 72 could also include a message such as, "Your e-mail message was received on March 24, 2000 at 2:05 p.m.
- the digital signature of the message was [128-bit digital signature]. For more information, visit our website at www.RPost.com.”
- confirmation message 72 could include all of the information contained in the registered version 74.
- the system may provide to message recipient 68 a receipt 74 or other verifiable confirmation that: (1) the recipient received an e-mail message;
- the system provides evidence, which may be attested to by the operators of the system, that particular electronic messages and documents were delivered to recipients having certain content and representing themselves as having come from certain senders.
- FIG. 9 is a flow chart illustrating one example of registering in-bound mail.
- RPost server 64 receives a new e-mail message.
- the system generates a hash/digital signature of the message's contents including the message's headers and attachments. Additionally, the system may generate a separate hash for each message attachment.
- the system encrypts the hash(es) using an encryption key known only to the operators of the system.
- the resulting encrypted hash(es) is then appended to the body of the message. Then, in step 905, the modified message may be made available for inspection or download through the recipient's MUA.
- FIG. 10 is a flow chart of one example of validating a received registered e-mail message.
- step 1000 in the event that the recipient of a message should require evidence that an e-mail with a specific content was received at a particular time, the recipient can present a copy of the registered version 74 (FIG. 8) of e-mail message 70 to the operators of the system for verification.
- step 1001 the system detaches and decrypts the document digital signature appended to the message.
- the system generates a hash of the balance of the document, and one for each file attached to the message.
- steps 1003 and 1004 the hashes are compared. If the document hash(es) matches the decrypted hash(es), then the message and its attachments must have passed through the system and have not been altered since their delivery to the recipient.
- step 1006 if the hash values do not match, then the operator cannot warrant that the e-mail is authentic, i.e., that the e-mail is an accurate version of an e- mail that was received by the system.
- FIG. 11 illustrates how the invention may be used by a business which utilizes electronic tools (an "e-business").
- E-business 30 can utilize the system to register all incoming ancLoutgoing e-mail messages from its customers 34.
- the system includes Post Office Protocol (POP) server 36 and Simple Mail Transfer Protocol (SMTP) server 38.
- POP Post Office Protocol
- SMTP Simple Mail Transfer Protocol
- the e-business 30 can set up its website to e-mail forms to customers, and to forward queries and complaints 40 from customers 34.
- the registered queries, complaints, orders, offers to purchase, and other information 46 are sent to the e-business 30 by the system. Receipts are then provided to the customers 34 via SMPT server 38. This way there is no question regarding whether or not the customer sent the communication and what it contained.
- the e-business can set up a web site 32 through the RPost server so that every communication with the customers can be registered.
- data orders 42 and automated responses 44 can be registered through the system server; furthermore, any confirmation, collections notices, customer support, and special offers 48 sent by the e-business to customers 34 can be registered and the confirmation sent to the customer to eliminate arguments about what was ordered, when, or by whom.
- identical receipts can be provided to both the customers 34 and to e-business 30.
- the functions of POP server 36 and SMTP server 38 may be combined in a single system server.
- POP is a protocol used to retrieve e-mail from an e-mail server. Many e-mail applications (sometimes called e-mail clients) use the POP protocol, although some can use the newer Internet Message Access Protocol (IMAP).
- IMAP Internet Message Access Protocol
- POP2 One version of POP, called POP2, requires SMTP to send messages.
- POP3 can be used with or without SMTP.
- SMTP is a protocol for sending e-mail messages between servers. Many e-mail systems that send e-mail over the Internet use SMTP to send messages from one server to another; the messages can then be retrieved with an e-mail client using either POP or IMAP.
- SMTP is generally used to send messages from a mail client to a mail server.
- E-mail servers may use a variety of protocols to communicate with the Internet. Commonly used protocols include SMTP, POP3 and IMAP4. Mail readers are at the opposite end of the server. Since mail servers receive messages via SMTP, e-mail readers send e-mail to a mail server using SMPT. Likewise, since mail servers send messages using POP3 and optionally IMAP4, mail readers receive messages from mail servers by using the POP3or IMAP4 protocol.
- Electronic messages may include text, audio, video, graphics, data, and attachments of various file types.
- the methods and techniques taught herein can be programmed into servers and other computers, and computer programs implementing the invention can be written onto computer readable media including but not limited to CD ROMs, RAM, hard drives, and magnetic tape.
- E-mail registration services according to the present invention can be bundled with Internet service provider (ISP) services to provide a single provider ISP solution to corporate and other institutional clients. Implementing the above-described invention is within the skill of the ordinary practitioner of the software arts.
- ISP Internet service provider
Abstract
Description
Claims
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA2417531A CA2417531C (en) | 2000-07-27 | 2001-07-25 | System and method for verifying delivery and integrity of electronic messages |
AU2001278025A AU2001278025A1 (en) | 2000-07-27 | 2001-07-25 | System and method for verifying delivery and integrity of electronic message |
BRPI0112960A BRPI0112960B1 (en) | 2000-07-27 | 2001-07-25 | method for verification of sending and integrity of electronic messages |
MXPA03000807A MXPA03000807A (en) | 2000-07-27 | 2001-07-25 | System and method for verifying delivery and integrity of electronic message. |
KR1020037001224A KR100604630B1 (en) | 2000-07-27 | 2001-07-25 | System and method for verifying delivery and integrity of electronic message |
EP01955979A EP1410278A2 (en) | 2000-07-27 | 2001-07-25 | System and method for verifying delivery and integrity of electronic message |
JP2002515672A JP2004521404A (en) | 2000-07-27 | 2001-07-25 | System and method for verifying delivery and integrity of electronic messages |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/626,577 US7966372B1 (en) | 1999-07-28 | 2000-07-27 | System and method for verifying delivery and integrity of electronic messages |
US09/626,577 | 2000-07-27 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2002011025A2 true WO2002011025A2 (en) | 2002-02-07 |
WO2002011025A3 WO2002011025A3 (en) | 2003-08-14 |
Family
ID=24510978
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2001/023565 WO2002011025A2 (en) | 2000-07-27 | 2001-07-25 | System and method for verifying delivery and integrity of electronic message |
Country Status (10)
Country | Link |
---|---|
US (6) | US7966372B1 (en) |
EP (1) | EP1410278A2 (en) |
JP (3) | JP2004521404A (en) |
KR (1) | KR100604630B1 (en) |
CN (1) | CN100413292C (en) |
AU (1) | AU2001278025A1 (en) |
BR (1) | BRPI0112960B1 (en) |
CA (1) | CA2417531C (en) |
MX (1) | MXPA03000807A (en) |
WO (1) | WO2002011025A2 (en) |
Cited By (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003073711A2 (en) * | 2002-02-22 | 2003-09-04 | Rpost International Limited | System and method for verifying delivery and integrity of electronic messages |
WO2004049654A3 (en) * | 2002-11-26 | 2004-11-04 | Rpost Int Ltd | Method for verifing delivery and integrity of electronic messages |
JP2005101883A (en) * | 2003-09-25 | 2005-04-14 | Hitachi Ltd | Electronic mail document originality assuring device |
ES2253040A1 (en) * | 2003-10-06 | 2006-05-16 | Manuel Pipeline Software 2.000 S.L. | Security system for electronic mail based on digital signature, uses digitally signed certification for transmitting and receiving electronic mails, and limits total certification volume for electronic mails for each user |
CN1301478C (en) * | 2002-02-12 | 2007-02-21 | 佳能株式会社 | Electronic-mail processing system for making feedback mails method thereof |
GB2436184A (en) * | 2006-03-17 | 2007-09-19 | Empower Interactive Group Ltd | Monitoring the distribution of messages |
WO2009068697A1 (en) * | 2007-11-26 | 2009-06-04 | Scytl Secure Electronic Voting, Sa | Method and system for the secure and verifiable consolidation of the results of election processes |
US7660989B2 (en) | 2002-11-26 | 2010-02-09 | Rpost International Limited | System for, and method of, authenticating an electronic message to a recipient |
US7707624B2 (en) | 2002-11-26 | 2010-04-27 | Rpost International Limited | System for, and method of, proving the transmission, receipt and content of a reply to an electronic message |
US7865557B2 (en) | 1999-07-28 | 2011-01-04 | Rpost International Limited | System and method for verifying delivery and integrity of electronic messages |
GB2473477A (en) * | 2009-09-14 | 2011-03-16 | Read Sure Ltd | Providing acknowledgement receipts for emails, preferably with non-repudiation properties |
US7970834B2 (en) | 2005-11-03 | 2011-06-28 | International Business Machines Corporation | Method and program product for tracking a file attachment in an e-mail |
US8108476B2 (en) | 2003-07-07 | 2012-01-31 | Quest Software, Inc. | High performance electronic message delivery engine |
JP2012039610A (en) * | 2004-02-09 | 2012-02-23 | Nokia Corp | Method and system for transmitting multimedia message to multiple recipients |
US8161104B2 (en) | 1999-07-28 | 2012-04-17 | Rpost International Limited | System and method for verifying delivery and integrity of electronic messages |
EP2443608A2 (en) * | 2009-06-17 | 2012-04-25 | Trustifi Corporation | Certified email system and method |
US8782415B2 (en) | 2003-11-21 | 2014-07-15 | Rpost Communications Limited | System for, and method of, providing the transmission, receipt and content of an E-mail message to a recipient |
US10664936B2 (en) | 2013-03-15 | 2020-05-26 | Csidentity Corporation | Authentication systems and methods for on-demand products |
US10685336B1 (en) | 2011-06-16 | 2020-06-16 | Consumerinfo.Com, Inc. | Authentication alerts |
EP3716177A1 (en) * | 2019-03-25 | 2020-09-30 | IPCO 2012 Limited | A method, apparatus and computer program for verifying the integrity of electronic messages |
US10911234B2 (en) | 2018-06-22 | 2021-02-02 | Experian Information Solutions, Inc. | System and method for a token gateway environment |
US11074641B1 (en) | 2014-04-25 | 2021-07-27 | Csidentity Corporation | Systems, methods and computer-program products for eligibility verification |
US11120519B2 (en) | 2013-05-23 | 2021-09-14 | Consumerinfo.Com, Inc. | Digital identity |
US11157872B2 (en) | 2008-06-26 | 2021-10-26 | Experian Marketing Solutions, Llc | Systems and methods for providing an integrated identifier |
US11288677B1 (en) | 2013-03-15 | 2022-03-29 | Consumerlnfo.com, Inc. | Adjustment of knowledge-based authentication |
US11941065B1 (en) | 2019-09-13 | 2024-03-26 | Experian Information Solutions, Inc. | Single identifier platform for storing entity data |
Families Citing this family (73)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9106626B2 (en) * | 2000-03-30 | 2015-08-11 | Nokia Solutions And Networks Oy | Method, apparatus and computer program product for copying content between servers |
US7685239B2 (en) * | 2000-06-28 | 2010-03-23 | Canon Kabushiki Kaisha | Image communication apparatus, image communication method, and memory medium |
JP3730858B2 (en) * | 2000-12-01 | 2006-01-05 | 株式会社エヌ・ティ・ティ・ドコモ | Mail system, server, and mail transmission / reception device |
US20090144382A1 (en) * | 2001-01-09 | 2009-06-04 | Benninghoff Iii Charles F | Method for certifying and unifying delivery of electronic packages |
US6999989B2 (en) * | 2001-03-29 | 2006-02-14 | At&T Corp. | Methods for providing video enhanced electronic mail return receipts |
US7225230B1 (en) * | 2001-06-28 | 2007-05-29 | Bellsouth Intellectual Property Corporation | System and method for electronic message status notification |
US7676546B2 (en) | 2003-03-25 | 2010-03-09 | Verisign, Inc. | Control and management of electronic messaging |
US7949877B2 (en) * | 2003-06-30 | 2011-05-24 | Realnetworks, Inc. | Rights enforcement and usage reporting on a client device |
US8230019B2 (en) * | 2003-07-17 | 2012-07-24 | International Business Machines Corporation | Alerting electronic mail users of undeliverable recipients |
US7281274B2 (en) * | 2003-10-16 | 2007-10-09 | Lmp Media Llc | Electronic media distribution system |
US8266218B2 (en) | 2004-02-12 | 2012-09-11 | International Business Machines Corporation | Automated electronic message filing system |
US9626655B2 (en) * | 2004-02-19 | 2017-04-18 | Intellectual Ventures I Llc | Method, apparatus and system for regulating electronic mail |
US8244913B1 (en) * | 2004-10-13 | 2012-08-14 | Progress Software Corporation | Replication horizon determination with an independent distributed database system |
US8151112B2 (en) * | 2005-04-22 | 2012-04-03 | Gerard Lin | Deliver-upon-request secure electronic message system |
US7673055B2 (en) * | 2005-06-23 | 2010-03-02 | Research In Motion Limited | System and method for automatically responding to a received communication |
US20070106737A1 (en) * | 2005-11-10 | 2007-05-10 | Barnes Thomas H | System and process for delivery status notification |
CN1980131B (en) * | 2005-12-09 | 2011-05-25 | 北京瑞星信息技术有限公司 | Mail interception method and module for realizing said method |
EA012795B1 (en) * | 2005-12-29 | 2009-12-30 | Регифи Аг | A communication system for providing the delivery of e-mail message |
WO2008064153A2 (en) * | 2006-11-21 | 2008-05-29 | Lucent Technologies Inc. | Processing method for message integrity with tolerance for non-sequential arrival of message data |
DE602008000204D1 (en) * | 2007-04-13 | 2009-11-26 | Teamon Systems Inc | Direct access e-mail distribution and synchronization system with IMAP IDLE implementation |
US20090043855A1 (en) * | 2007-08-08 | 2009-02-12 | Blake Bookstaff | System for providing information to originator of misdirected email |
US20090063631A1 (en) * | 2007-08-31 | 2009-03-05 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Message-reply-dependent update decisions |
US20090083413A1 (en) * | 2007-09-24 | 2009-03-26 | Levow Zachary S | Distributed frequency data collection via DNS |
JP4444998B2 (en) * | 2007-10-12 | 2010-03-31 | 富士通株式会社 | E-mail information management program, e-mail information management apparatus, and e-mail information management method |
US9503354B2 (en) * | 2008-01-17 | 2016-11-22 | Aerohive Networks, Inc. | Virtualization of networking services |
US8347355B2 (en) * | 2008-01-17 | 2013-01-01 | Aerohive Networks, Inc. | Networking as a service: delivering network services using remote appliances controlled via a hosted, multi-tenant management system |
JP5045472B2 (en) * | 2008-02-07 | 2012-10-10 | 富士通株式会社 | Mail management apparatus, mail management method, and mail management program |
US8244814B1 (en) * | 2008-03-31 | 2012-08-14 | Symantec Corporation | Methods and systems for managing email configuration |
US20090292780A1 (en) * | 2008-05-22 | 2009-11-26 | Rajaram Ramesh | System and method for selective application of a feature to multiple recipients of an email message |
US8032611B2 (en) * | 2008-12-19 | 2011-10-04 | Research In Motion Limited | Method and communication device for processing data for transmission from the communication device to a second communication device |
US20100179821A1 (en) * | 2009-01-09 | 2010-07-15 | Cerner Innovation, Inc. | Tracking direct reported adverse events |
US8374930B2 (en) * | 2009-02-02 | 2013-02-12 | Trustifi Corporation | Certified email system and method |
JP5435989B2 (en) * | 2009-03-12 | 2014-03-05 | キヤノン株式会社 | Email reception error information notification system |
US9800415B2 (en) * | 2009-08-27 | 2017-10-24 | Robert H. Cohen | Electronic name registry type |
US20110060796A1 (en) * | 2009-09-04 | 2011-03-10 | International Business Machines Corporation | E-mail address verification system |
CN102656579A (en) | 2009-11-04 | 2012-09-05 | 塞德克西斯公司 | Internet infrastructure survey |
US8832853B2 (en) | 2009-12-07 | 2014-09-09 | Dst Technologies, Inc. | Managed virtual point to point communication service having verified directory, secure transmission and controlled delivery |
US8825759B1 (en) | 2010-02-08 | 2014-09-02 | Google Inc. | Recommending posts to non-subscribing users |
US8582801B2 (en) | 2010-02-08 | 2013-11-12 | Google Inc. | Assisting the authoring of posts to an asymmetric social network |
US9729352B1 (en) * | 2010-02-08 | 2017-08-08 | Google Inc. | Assisting participation in a social network |
CN102202006B (en) * | 2010-03-26 | 2014-04-09 | 中国科学院软件研究所 | Registered E-mail transmission method |
US8745143B2 (en) * | 2010-04-01 | 2014-06-03 | Microsoft Corporation | Delaying inbound and outbound email messages |
KR20120005363A (en) * | 2010-07-08 | 2012-01-16 | 정보통신산업진흥원 | Electronic document distribution system, and electronic document distribution method |
US8527597B2 (en) | 2010-12-07 | 2013-09-03 | Google Inc. | Determining message prominence |
DE202011002655U1 (en) | 2011-02-11 | 2011-04-14 | Francotyp-Postalia Gmbh | Input / output station and system for network-based printing |
US9251367B2 (en) * | 2011-03-25 | 2016-02-02 | Nec Corporation | Device, method and program for preventing information leakage |
US9160725B2 (en) | 2011-09-23 | 2015-10-13 | Rpost Communications Limited | Computer implemented system and method for authenticating a sender of electronic data to a recipient |
US20130085793A1 (en) * | 2011-10-04 | 2013-04-04 | Wayne Evan Cooper | Method of prosecuting acquisition of responses to a proposition, and system for doing the same |
PT2632096T (en) * | 2012-02-21 | 2017-06-07 | Lleidanetworks Serveis Telemàtics S A | Method for certifying delivery of electronic messages |
EP2632097A1 (en) * | 2012-02-21 | 2013-08-28 | Lleidanetworks Serveis Telemàtics S.A. | Method for certifying delivery of SMS/MMS data messages to mobile terminals |
US9560001B1 (en) * | 2012-04-02 | 2017-01-31 | Google Inc. | Managing notifications across services |
HUE050169T2 (en) * | 2012-10-19 | 2020-11-30 | Lleidanetworks Serveis Telematics Sa | Method for the registration and certification of receipt of electronic mail |
US9779378B1 (en) * | 2012-11-16 | 2017-10-03 | Isaac S. Daniel | Automatic transmission mobile post office system |
US9712515B2 (en) * | 2012-12-21 | 2017-07-18 | Cellco Partnership | Verifying an identity of a message sender |
US9191344B2 (en) | 2013-02-11 | 2015-11-17 | International Business Machines Corporation | Validating content from an original communication included in a new communication |
US10320628B2 (en) | 2013-06-19 | 2019-06-11 | Citrix Systems, Inc. | Confidence scoring of device reputation based on characteristic network behavior |
KR101332607B1 (en) | 2013-09-02 | 2013-11-25 | 서호진 | System and method of forwarding # mail and verifying the forwarded mail in official mailing system |
US9258258B2 (en) * | 2013-10-21 | 2016-02-09 | International Business Machines Corporation | Implementing injection of formal numerical message identifiers in cloud stacks |
US20150215291A1 (en) * | 2013-12-05 | 2015-07-30 | Tarek A.M. Abdunabi | Secure decentralized content management platform and transparent gateway |
CN106465075A (en) * | 2014-03-27 | 2017-02-22 | 宇龙计算机通信科技(深圳)有限公司 | Information transmitting method and device and information receiving method and device |
CN104052650B (en) * | 2014-05-29 | 2017-06-27 | 天津三星通信技术研究有限公司 | The method and apparatus for sending mail |
US10412040B2 (en) * | 2015-02-06 | 2019-09-10 | Google Llc | Systems and methods for direct dispatching of mobile messages |
JP6048565B1 (en) * | 2015-11-02 | 2016-12-21 | 富士ゼロックス株式会社 | Image processing apparatus, information processing system, and image processing program |
US20170134280A1 (en) * | 2015-11-11 | 2017-05-11 | Mastercard International Incorporated | Method and system for validation of hashed data via acceptance frames |
DK3188435T3 (en) * | 2015-12-28 | 2020-01-27 | Lleidanetworks Serveis Telematics Sa | METHOD OF CERTIFICATING ELECTRONIC MAIL INCLUDING A SECURE DIGITAL SIGNATURE FROM A TELECOMMUNICATION OPERATOR |
US9559997B1 (en) | 2016-01-11 | 2017-01-31 | Paul Everton | Client agnostic email processing |
US9674129B1 (en) | 2016-10-05 | 2017-06-06 | eTorch Inc. | Email privacy enforcement |
US9824332B1 (en) | 2017-04-12 | 2017-11-21 | eTorch Inc. | Email data collection compliance enforcement |
CN107196842B (en) * | 2016-03-14 | 2020-07-14 | 阿里巴巴集团控股有限公司 | Method and device for realizing message anti-counterfeiting |
US10511564B2 (en) * | 2017-01-20 | 2019-12-17 | Salesforce.Com, Inc. | User availability aware communication system |
US11176021B2 (en) * | 2018-06-03 | 2021-11-16 | Apple Inc. | Messaging systems with improved reliability |
CN108882239B (en) * | 2018-06-25 | 2021-07-13 | 联动优势科技有限公司 | Information sending method and device |
CN117294670B (en) * | 2023-11-17 | 2024-04-05 | 麒麟软件有限公司 | Mail tracing and withdrawing method |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5553145A (en) * | 1995-03-21 | 1996-09-03 | Micali; Silvia | Simultaneous electronic transactions with visible trusted parties |
WO1996038987A1 (en) * | 1995-05-31 | 1996-12-05 | Sloo Marshall A | Method and apparatus for handling communications |
WO1998017042A2 (en) * | 1996-10-15 | 1998-04-23 | Mordhai Barkan | Electronic mail method |
WO1999008424A1 (en) * | 1997-08-06 | 1999-02-18 | Siemens Aktiengesellschaft | Method and device for generating information on messages transmitted |
WO2001010090A1 (en) * | 1999-07-28 | 2001-02-08 | Tomkow Terrance A | System and method for verifying delivery and integrity of electronic messages |
Family Cites Families (48)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB8704883D0 (en) | 1987-03-03 | 1987-04-08 | Hewlett Packard Co | Secure information storage |
JPH06141041A (en) * | 1992-10-27 | 1994-05-20 | Matsushita Electric Ind Co Ltd | Electronic mailing system |
JPH07177142A (en) | 1993-10-27 | 1995-07-14 | Hitachi Ltd | Message guarantee system |
US5530757A (en) | 1994-06-28 | 1996-06-25 | International Business Machines Corporation | Distributed fingerprints for information integrity verification |
JP2638525B2 (en) | 1994-08-03 | 1997-08-06 | 日本電気株式会社 | Electronic signature verification device |
US5606609A (en) | 1994-09-19 | 1997-02-25 | Scientific-Atlanta | Electronic document verification system and method |
BR9509131A (en) | 1994-10-28 | 1997-09-02 | Surety Technologies Inc | Registration process of first digital document for authentication process for authentication of digital document process for naming of first digital document digital representation of document certificate authentication and clock-stamp process for first digital document for authentication |
US5748738A (en) | 1995-01-17 | 1998-05-05 | Document Authentication Systems, Inc. | System and method for electronic transmission, storage and retrieval of authenticated documents |
US5615268A (en) | 1995-01-17 | 1997-03-25 | Document Authentication Systems, Inc. | System and method for electronic transmission storage and retrieval of authenticated documents |
US6393566B1 (en) | 1995-07-28 | 2002-05-21 | National Institute Of Standards And Technology | Time-stamp service for the national information network |
DE69503374T2 (en) * | 1995-08-28 | 1999-04-15 | Ofra Feldbau | Setup and method for authenticating the sending and content of a document |
US6021433A (en) * | 1996-01-26 | 2000-02-01 | Wireless Internet, Inc. | System and method for transmission of data |
US5673316A (en) | 1996-03-29 | 1997-09-30 | International Business Machines Corporation | Creation and distribution of cryptographic envelope |
US6396513B1 (en) * | 1996-05-14 | 2002-05-28 | At&T Corp. | Electronic message sorting and notification system |
JP3540511B2 (en) | 1996-06-18 | 2004-07-07 | 株式会社東芝 | Electronic signature verification device |
US6327656B2 (en) * | 1996-07-03 | 2001-12-04 | Timestamp.Com, Inc. | Apparatus and method for electronic document certification and verification |
CA2261947C (en) * | 1996-08-07 | 2008-11-18 | Silvio Micali | Simultaneous electronic transactions with visible trusted parties |
JPH10105057A (en) * | 1996-09-25 | 1998-04-24 | Hitachi Software Eng Co Ltd | Time stamp server system |
US5892909A (en) | 1996-09-27 | 1999-04-06 | Diffusion, Inc. | Intranet-based system with methods for co-active delivery of information to multiple users |
US6285991B1 (en) * | 1996-12-13 | 2001-09-04 | Visa International Service Association | Secure interactive electronic account statement delivery system |
US6009173A (en) * | 1997-01-31 | 1999-12-28 | Motorola, Inc. | Encryption and decryption method and apparatus |
US5872848A (en) | 1997-02-18 | 1999-02-16 | Arcanvs | Method and apparatus for witnessed authentication of electronic documents |
US6189097B1 (en) * | 1997-03-24 | 2001-02-13 | Preview Systems, Inc. | Digital Certificate |
JPH10268765A (en) * | 1997-03-28 | 1998-10-09 | Hitachi Software Eng Co Ltd | Method for confirming data dispatching |
US5926550A (en) | 1997-03-31 | 1999-07-20 | Intel Corporation | Peripheral device preventing post-scan modification |
US6651166B1 (en) * | 1998-04-09 | 2003-11-18 | Tumbleweed Software Corp. | Sender driven certification enrollment system |
US6825955B1 (en) * | 1997-12-01 | 2004-11-30 | Ricoh Company, Ltd. | Method and apparatus for facsimile that notifies an e-mail transmission using facsimile protocol |
US6594693B1 (en) * | 1998-02-10 | 2003-07-15 | Nitin A. Borwankar | Method and apparatus for a structured, synchronized conversation using electronic messages over a computer network |
JP3527090B2 (en) * | 1998-02-24 | 2004-05-17 | 富士通エフ・アイ・ピー株式会社 | Distributed mail system, recording medium recording mail arrival confirmation program, and mail server device |
US6199052B1 (en) | 1998-03-06 | 2001-03-06 | Deloitte & Touche Usa Llp | Secure electronic transactions using a trusted intermediary with archive and verification request services |
JP2000196583A (en) * | 1998-12-28 | 2000-07-14 | Mitsubishi Materials Corp | Broadcast communication system |
US7039805B1 (en) * | 1998-05-20 | 2006-05-02 | Messing John H | Electronic signature method |
US6341164B1 (en) * | 1998-07-22 | 2002-01-22 | Entrust Technologies Limited | Method and apparatus for correcting improper encryption and/or for reducing memory storage |
JP2000099421A (en) * | 1998-09-22 | 2000-04-07 | Hitachi Ltd | Method for confirming reception of electronic information |
WO2000022551A1 (en) * | 1998-10-13 | 2000-04-20 | Chris Cheah | Method and system for controlled distribution of information over a network |
US6625642B1 (en) * | 1998-11-06 | 2003-09-23 | J2 Global Communications | System and process for transmitting electronic mail using a conventional facsimile device |
US6618747B1 (en) * | 1998-11-25 | 2003-09-09 | Francis H. Flynn | Electronic communication delivery confirmation and verification system |
JP2000181817A (en) * | 1998-12-16 | 2000-06-30 | Fujitsu Ltd | Electronic mail system, electronic mail server and recording medium |
US6510513B1 (en) * | 1999-01-13 | 2003-01-21 | Microsoft Corporation | Security services and policy enforcement for electronic data |
US6654779B1 (en) * | 1999-04-14 | 2003-11-25 | First Data Resources | System and method for electronic mail (e-mail) address management |
US6760760B1 (en) * | 1999-06-09 | 2004-07-06 | Amx Corporation | Control system communication server for transmitting files via multiple communication paths |
US6760752B1 (en) * | 1999-06-28 | 2004-07-06 | Zix Corporation | Secure transmission system |
US7966372B1 (en) | 1999-07-28 | 2011-06-21 | Rpost International Limited | System and method for verifying delivery and integrity of electronic messages |
CN1451213B (en) | 1999-09-30 | 2012-10-10 | 美国邮政服务 | Systems and methods for authenticating an electronic message |
US6611869B1 (en) * | 1999-10-28 | 2003-08-26 | Networks Associates, Inc. | System and method for providing trustworthy network security concern communication in an active security management environment |
US6760750B1 (en) * | 2000-03-01 | 2004-07-06 | Polycom Israel, Ltd. | System and method of monitoring video and/or audio conferencing through a rapid-update web site |
US6643687B1 (en) * | 2000-04-07 | 2003-11-04 | Avid Technology, Inc. | Email system delivers email message to a proxy email address that corresponds to a sender and recipient pairing |
US7707624B2 (en) * | 2002-11-26 | 2010-04-27 | Rpost International Limited | System for, and method of, proving the transmission, receipt and content of a reply to an electronic message |
-
2000
- 2000-07-27 US US09/626,577 patent/US7966372B1/en not_active Expired - Fee Related
-
2001
- 2001-07-25 CN CNB018147488A patent/CN100413292C/en not_active Expired - Fee Related
- 2001-07-25 AU AU2001278025A patent/AU2001278025A1/en not_active Abandoned
- 2001-07-25 KR KR1020037001224A patent/KR100604630B1/en active IP Right Grant
- 2001-07-25 CA CA2417531A patent/CA2417531C/en not_active Expired - Fee Related
- 2001-07-25 WO PCT/US2001/023565 patent/WO2002011025A2/en active IP Right Grant
- 2001-07-25 BR BRPI0112960A patent/BRPI0112960B1/en not_active IP Right Cessation
- 2001-07-25 MX MXPA03000807A patent/MXPA03000807A/en active IP Right Grant
- 2001-07-25 JP JP2002515672A patent/JP2004521404A/en active Pending
- 2001-07-25 EP EP01955979A patent/EP1410278A2/en not_active Withdrawn
-
2007
- 2007-03-16 US US11/725,210 patent/US7865557B2/en not_active Expired - Lifetime
-
2009
- 2009-02-25 JP JP2009042721A patent/JP5236527B2/en not_active Expired - Fee Related
-
2010
- 2010-11-22 US US12/952,076 patent/US8224913B2/en not_active Expired - Lifetime
-
2011
- 2011-05-13 US US13/107,819 patent/US8275845B2/en not_active Expired - Fee Related
-
2012
- 2012-02-06 JP JP2012023225A patent/JP5256358B2/en not_active Expired - Fee Related
- 2012-07-16 US US13/550,476 patent/US8782154B2/en not_active Expired - Lifetime
- 2012-09-24 US US13/625,806 patent/US20130117387A1/en not_active Abandoned
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5553145A (en) * | 1995-03-21 | 1996-09-03 | Micali; Silvia | Simultaneous electronic transactions with visible trusted parties |
WO1996038987A1 (en) * | 1995-05-31 | 1996-12-05 | Sloo Marshall A | Method and apparatus for handling communications |
WO1998017042A2 (en) * | 1996-10-15 | 1998-04-23 | Mordhai Barkan | Electronic mail method |
WO1999008424A1 (en) * | 1997-08-06 | 1999-02-18 | Siemens Aktiengesellschaft | Method and device for generating information on messages transmitted |
WO2001010090A1 (en) * | 1999-07-28 | 2001-02-08 | Tomkow Terrance A | System and method for verifying delivery and integrity of electronic messages |
Non-Patent Citations (3)
Title |
---|
"METHOD FOR AUTOMATED COMMUNICATION TO THIRD PARTIES UPON COMPOSITE ACKNOWLEDGEMENT" IBM TECHNICAL DISCLOSURE BULLETIN, IBM CORP. NEW YORK, US, vol. 37, no. 2B, 1 February 1994 (1994-02-01), pages 345-346, XP000433872 ISSN: 0018-8689 * |
CERVENINI G ET AL: "A multiprovider, universal, e-mail service for the secure exchange of legally-binding multimedia documents" EUROCOMM 2000. INFORMATION SYSTEMS FOR ENHANCED PUBLIC SAFETY AND SECURITY. IEEE/AFCEA, 17 May 2000 (2000-05-17), XP002178670 Retrieved from the Internet: <URL:http.//ieeexplore.ieee.org> [retrieved on 2001-09-27] * |
MOORE K ET AL: "An Extensible Message Format for Delivery Status Notifications" IETF REQUEST FOR COMMENTS, XX, XX, no. 1894, January 1996 (1996-01), pages 1-39, XP002154302 * |
Cited By (54)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8209389B2 (en) | 1999-07-28 | 2012-06-26 | Rpost Communications Limited | System and method for verifying delivery and integrity of electronic messages |
US7966372B1 (en) | 1999-07-28 | 2011-06-21 | Rpost International Limited | System and method for verifying delivery and integrity of electronic messages |
US9596194B2 (en) | 1999-07-28 | 2017-03-14 | Rpost Communications Limited | System and method for verifying delivery and integrity of electronic messages |
US9432313B2 (en) | 1999-07-28 | 2016-08-30 | Rpost Communications Limited | System and method for verifying delivery and integrity of electronic messages |
US8161104B2 (en) | 1999-07-28 | 2012-04-17 | Rpost International Limited | System and method for verifying delivery and integrity of electronic messages |
US8782154B2 (en) | 1999-07-28 | 2014-07-15 | Rpost Communications Limited | System and method for verifying delivery and integrity of electronic messages |
US8504628B2 (en) | 1999-07-28 | 2013-08-06 | Rpost Communications Limited | System and method for verifying delivery and integrity of electronic messages |
US7865557B2 (en) | 1999-07-28 | 2011-01-04 | Rpost International Limited | System and method for verifying delivery and integrity of electronic messages |
US8468199B2 (en) | 1999-07-28 | 2013-06-18 | Rpost International Limited | System and method for verifying delivery and integrity of electronic messages |
US8468198B2 (en) | 1999-07-28 | 2013-06-18 | Rpost International Limited | System and method for verifying delivery and integrity of electronic messages |
US8224913B2 (en) | 1999-07-28 | 2012-07-17 | Rpost Communications Limited | System and method for verifying delivery and integrity of electronic messages |
US7240199B2 (en) | 2000-12-06 | 2007-07-03 | Rpost International Limited | System and method for verifying delivery and integrity of electronic messages |
CN1301478C (en) * | 2002-02-12 | 2007-02-21 | 佳能株式会社 | Electronic-mail processing system for making feedback mails method thereof |
JP2005518763A (en) * | 2002-02-22 | 2005-06-23 | アールポスト インターナショナル リミテッド | System and method for verifying delivery and integrity of electronic messages |
WO2003073711A2 (en) * | 2002-02-22 | 2003-09-04 | Rpost International Limited | System and method for verifying delivery and integrity of electronic messages |
AU2003224616B2 (en) * | 2002-02-22 | 2008-12-11 | Rpost International Limited | System and method for verifying delivery and integrity of electronic messages |
KR101029030B1 (en) * | 2002-02-22 | 2011-04-15 | 알포스트 인터내셔널 리미티드 | System and method for verifying delivery and integrity of electronic messages |
WO2003073711A3 (en) * | 2002-02-22 | 2003-11-27 | Rpost Int Ltd | System and method for verifying delivery and integrity of electronic messages |
US7707624B2 (en) | 2002-11-26 | 2010-04-27 | Rpost International Limited | System for, and method of, proving the transmission, receipt and content of a reply to an electronic message |
WO2004049654A3 (en) * | 2002-11-26 | 2004-11-04 | Rpost Int Ltd | Method for verifing delivery and integrity of electronic messages |
US7660989B2 (en) | 2002-11-26 | 2010-02-09 | Rpost International Limited | System for, and method of, authenticating an electronic message to a recipient |
US8108476B2 (en) | 2003-07-07 | 2012-01-31 | Quest Software, Inc. | High performance electronic message delivery engine |
JP2005101883A (en) * | 2003-09-25 | 2005-04-14 | Hitachi Ltd | Electronic mail document originality assuring device |
ES2253040A1 (en) * | 2003-10-06 | 2006-05-16 | Manuel Pipeline Software 2.000 S.L. | Security system for electronic mail based on digital signature, uses digitally signed certification for transmitting and receiving electronic mails, and limits total certification volume for electronic mails for each user |
US8782415B2 (en) | 2003-11-21 | 2014-07-15 | Rpost Communications Limited | System for, and method of, providing the transmission, receipt and content of an E-mail message to a recipient |
JP2012039610A (en) * | 2004-02-09 | 2012-02-23 | Nokia Corp | Method and system for transmitting multimedia message to multiple recipients |
US7970834B2 (en) | 2005-11-03 | 2011-06-28 | International Business Machines Corporation | Method and program product for tracking a file attachment in an e-mail |
GB2436184A (en) * | 2006-03-17 | 2007-09-19 | Empower Interactive Group Ltd | Monitoring the distribution of messages |
GB2436184B (en) * | 2006-03-17 | 2011-01-26 | Empower Interactive Group Ltd | Message forwarding system and method |
WO2009068697A1 (en) * | 2007-11-26 | 2009-06-04 | Scytl Secure Electronic Voting, Sa | Method and system for the secure and verifiable consolidation of the results of election processes |
US10445964B2 (en) | 2007-11-26 | 2019-10-15 | Sctyl Secure Electronic Voting, SA | Method and system for the secure and verifiable consolidation of the results of election processes |
US11157872B2 (en) | 2008-06-26 | 2021-10-26 | Experian Marketing Solutions, Llc | Systems and methods for providing an integrated identifier |
US11769112B2 (en) | 2008-06-26 | 2023-09-26 | Experian Marketing Solutions, Llc | Systems and methods for providing an integrated identifier |
EP2443608A4 (en) * | 2009-06-17 | 2014-06-25 | Trustifi Corp | Certified email system and method |
EP2443608A2 (en) * | 2009-06-17 | 2012-04-25 | Trustifi Corporation | Certified email system and method |
GB2473477A (en) * | 2009-09-14 | 2011-03-16 | Read Sure Ltd | Providing acknowledgement receipts for emails, preferably with non-repudiation properties |
US10685336B1 (en) | 2011-06-16 | 2020-06-16 | Consumerinfo.Com, Inc. | Authentication alerts |
US10719873B1 (en) | 2011-06-16 | 2020-07-21 | Consumerinfo.Com, Inc. | Providing credit inquiry alerts |
US11232413B1 (en) | 2011-06-16 | 2022-01-25 | Consumerinfo.Com, Inc. | Authentication alerts |
US10664936B2 (en) | 2013-03-15 | 2020-05-26 | Csidentity Corporation | Authentication systems and methods for on-demand products |
US11775979B1 (en) | 2013-03-15 | 2023-10-03 | Consumerinfo.Com, Inc. | Adjustment of knowledge-based authentication |
US11164271B2 (en) | 2013-03-15 | 2021-11-02 | Csidentity Corporation | Systems and methods of delayed authentication and billing for on-demand products |
US11288677B1 (en) | 2013-03-15 | 2022-03-29 | Consumerlnfo.com, Inc. | Adjustment of knowledge-based authentication |
US11790473B2 (en) | 2013-03-15 | 2023-10-17 | Csidentity Corporation | Systems and methods of delayed authentication and billing for on-demand products |
US11120519B2 (en) | 2013-05-23 | 2021-09-14 | Consumerinfo.Com, Inc. | Digital identity |
US11803929B1 (en) | 2013-05-23 | 2023-10-31 | Consumerinfo.Com, Inc. | Digital identity |
US11074641B1 (en) | 2014-04-25 | 2021-07-27 | Csidentity Corporation | Systems, methods and computer-program products for eligibility verification |
US11587150B1 (en) | 2014-04-25 | 2023-02-21 | Csidentity Corporation | Systems and methods for eligibility verification |
US10911234B2 (en) | 2018-06-22 | 2021-02-02 | Experian Information Solutions, Inc. | System and method for a token gateway environment |
US11588639B2 (en) | 2018-06-22 | 2023-02-21 | Experian Information Solutions, Inc. | System and method for a token gateway environment |
US11405408B2 (en) | 2019-03-25 | 2022-08-02 | Ipco 2012 Limited | Method, apparatus and computer program for verifying the integrity of electronic messages |
EP3716177A1 (en) * | 2019-03-25 | 2020-09-30 | IPCO 2012 Limited | A method, apparatus and computer program for verifying the integrity of electronic messages |
WO2020193016A1 (en) * | 2019-03-25 | 2020-10-01 | Ipco 2012 Limited | A method, apparatus and computer program for verifying the integrity of electronic messages |
US11941065B1 (en) | 2019-09-13 | 2024-03-26 | Experian Information Solutions, Inc. | Single identifier platform for storing entity data |
Also Published As
Publication number | Publication date |
---|---|
US8782154B2 (en) | 2014-07-15 |
US7865557B2 (en) | 2011-01-04 |
CA2417531A1 (en) | 2002-02-07 |
US20110246588A1 (en) | 2011-10-06 |
US7966372B1 (en) | 2011-06-21 |
US20130117387A1 (en) | 2013-05-09 |
KR100604630B1 (en) | 2006-07-28 |
AU2001278025A1 (en) | 2002-02-13 |
WO2002011025A3 (en) | 2003-08-14 |
KR20030051605A (en) | 2003-06-25 |
US8224913B2 (en) | 2012-07-17 |
US20110106897A1 (en) | 2011-05-05 |
JP5236527B2 (en) | 2013-07-17 |
JP2012110032A (en) | 2012-06-07 |
JP2009135962A (en) | 2009-06-18 |
US20070174402A1 (en) | 2007-07-26 |
JP5256358B2 (en) | 2013-08-07 |
CA2417531C (en) | 2013-05-28 |
BRPI0112960B1 (en) | 2016-12-06 |
JP2004521404A (en) | 2004-07-15 |
CN1653458A (en) | 2005-08-10 |
MXPA03000807A (en) | 2005-08-16 |
US8275845B2 (en) | 2012-09-25 |
BRPI0112960A8 (en) | 2016-09-13 |
EP1410278A2 (en) | 2004-04-21 |
CN100413292C (en) | 2008-08-20 |
BR0112960A (en) | 2004-06-08 |
US20120303956A1 (en) | 2012-11-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10887271B2 (en) | System and method for verifying delivery and integrity of electronic messages | |
US8275845B2 (en) | System and method for verified contract acceptance | |
US7240199B2 (en) | System and method for verifying delivery and integrity of electronic messages | |
US7660989B2 (en) | System for, and method of, authenticating an electronic message to a recipient | |
US8484706B2 (en) | System for, and method of, providing the transmission, receipt and content of a reply to an electronic message | |
US20050021963A1 (en) | System for, and method of, proving the transmission, receipt and content of a reply to an electronic message |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 81/KOLNP/2003 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2417531 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020037001224 Country of ref document: KR Ref document number: PA/a/2003/000807 Country of ref document: MX |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2001955979 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 018147488 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 1020037001224 Country of ref document: KR |
|
WWP | Wipo information: published in national office |
Ref document number: 2001955979 Country of ref document: EP |
|
WWG | Wipo information: grant in national office |
Ref document number: 1020037001224 Country of ref document: KR |