SENDER AUTHENTICATION FOR DIFFICULT TO CLASSIFY EMAIL

• US 20110271349A1
• Filed: 07/13/2007
• Published: 11/03/2011
• Est. Priority Date: 07/13/2007
• Status: Active Grant

• Current Assignee: Michael Gregor Kaplan
• Original Assignee: Michael Gregor Kaplan
• Inventors: Kaplan, Michael Gregor
• Granted Patent: US 8,073,912 B2
• Time in Patent Office: Days
• US Class Current: 726/26
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 51/48 Message addressing, e.g. address format or anonymous messages, aliases
• CPC Class Codes: H04L 63/0236 Filtering by address, protocol, port number or service, e.g. IP-address or URL
• CPC Class Codes: H04L 63/0245 Filtering by information in the payload
• CPC Class Codes: H04L 63/126 the source of the received data

Abstract

The portion of email traffic that cannot be definitively determined to be spam or definitively determined to be ham (non-spam) is processed by sending a bounceback email to the sender, requiring the sender to reply using a sub-address created by the bounceback generator. The type of bounceback email depends on whether the domain of the received email indicates that the sender is or is not likely to be a spammer. When the sender is not likely to be a spammer, the bounceback email includes a sub-address in computer readable form. When the sender is likely to be a spammer, the bounceback email includes a test that must be solved to yield the sub-address; preferably, the test is very difficult for a computer to solve but reasonably easy for a human to solve. When a reply email to the bounceback email (“reply bounceback”) is received, the presence of the sub-address indicates that the sender is not a spammer, so the reply bounceback is determined to be ham and delivered to the destination mailbox. The bounceback can have the sub-address encoded in such a way that a human must be involved in decoding, which is appropriate for situations where the envelope sender domain of the original email is considered suspicious. The bounceback can have the sub-address presented in a computer readable format when the envelope sender domain of the original email is more trustworthy, if authenticated. Authentication information can be retained in a local private Sender Policy Framework (SPF) database, or shared in a centralized private SPF database.

Claims

1. A method for authenticating a received email used by an email system, comprising:

classifying the received email as either a first type or a second type based on whether the sender domain of the received email is associated with a spammer,

when the received email is classified as the first type, sending a first type of bounceback email with a new sub-address to a sender of the received email, the first type of bounceback email having the new sub-address in computer-readable form, the new sub-address being appended to the origination email address in the bounceback email, and

when the received email is classified as the second type, sending a second type of bounceback email to a sender of the received email, the second type of bounceback email having a test in a body of the second type of bounceback email, the test for differentiating a human from a machine and having a solution that is the new sub-address,

wherein a destination address of a reply-to-bounceback email includes the new sub-address.

2. The method of claim 1, further comprising delivering the received email to its destination inbox after the sender of the received email is authenticated.

3. The method of claim 1, wherein the test is a CAPTCHA.

4. The method of claim 3, wherein the CAPTCHA presents the new sub- address.

5. The method of claim 1, wherein the received email includes an original sub-address and further comprising deactivating the original sub-address.

6. The method of claim 5, wherein the deactivating is performed by an executing software program.

7. The method of claim 5, further comprising receiving a subsequent email with the original sub-address, and performing spam filtering on the email while ignoring the now deactivated original sub-address, thereby increasing the likelihood that the deactivated email is classified as spam.

8. The method of claim 5, further comprising reactivating the original sub- address after determining that the sender of the received email is authentic.

9. The method of claim 8, wherein the reactivating is performed by an executing software program.

10. The method of claim 1, further comprising receiving the reply-to-bounceback email in reply to the bounceback email, and determining that the sender of the received email is authentic upon receipt of the reply-to-bounceback email.

11. The method of claim 10, wherein the bounceback email includes the message content of the received email.

12. The method of claim 1, wherein the new sub-address is in the FROM field of the bounceback email.

13. The method of claim 1, further comprising updating a private database with the authenticated sender information.

14. The method of claim 13, wherein the private database is local to a computer performing the authentication.

15. The method of claim 14, wherein the private database is centralized at a computer other than a computer performing the authentication.

16. The method of claim 1, further comprising

receiving, at a computer associated with the sender of the received email, a bounceback email relating to an original email, the bounceback email having a new sub-address appended to the origination email address,

checking, at the computer associated with the sender of the received email, whether the original email originated from the receiver of the bounceback email, and

when the original email originated from the receiver of the bounceback email, replying, by the computer associated with the sender of the received email, to the bounceback email without human involvement.

17. The method of claim 16, further comprising determining whether the bounceback email includes a computer readable sub-address, and if so, then performing the checking

18. The method of claim 17, further comprising determining whether the computer readable sub-address exists in an electronic address book, and if not, then updating the electronic address book to include the computer readable sub-address.

19. The method of claim 1, further comprising

receiving, at a computer associated with the sender of the received email, a bounceback email relating to an original email, the bounceback email including a new sub-address generated by a sender of the bounceback email, the sub-address being in the body of the bounceback email encoded as a test requiring human participation,

determining, at the computer associated with the sender of the received email, that the bounceback email includes a test requiring human participation to solve, the test involving the new sub-address,

reformatting, at the computer associated with the sender of the received email, the bounceback email, and

delivering, at the computer associated with the sender of the received email, the reformatted bounceback email to an inbox.

20. The method of claim 19, wherein the test is a CAPTCHA.

21. The method of claim 19, wherein the CAPTCHA presents the new sub-address.

22. The method of claim 19, wherein the reformatting includes providing a text entry field for the solution of the test, and an actuation element that, when actuated, sends the solution to a source of the bounceback email.

23-33. -33. (canceled)