Email processing system

• US 20050044153A1
• Filed: 06/14/2004
• Published: 02/24/2005
• Est. Priority Date: 06/12/2003
• Status: Abandoned Application

• Current Assignee: Idealab IdeaLab
• Original Assignee: Idealab IdeaLab
• Inventors: Gross, William
• Application Number:
  US10/867,276
• Publication Number:
  US 20050044153A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/212 using filtering or selective blocking

Abstract

In accordance with the foregoing, in one embodiment of the present invention, an email processing system comprises a first database configured to store a user'"'"'s email routing preferences. The system further comprises a second database configured to store registration information on paying email senders. The system further comprises email identification analysis code configured to determine whether an incoming email is commercial bulk email. The system further comprises email routing code configured to selectively deliver the incoming email to a folder or to delete the incoming email. The email routing code routes email based at least partially on the user'"'"'s email routing preferences, the determination of the email identification analysis code, and the email sender registration information.

Claims

1. An email processing system comprising:

a first database configured to store a user'"'"'s email routing preferences;

a second database configured to store registration information on paying email senders,

email identification analysis code configured to determine whether an incoming email is commercial bulk email; and

email routing code configured to selectively deliver the incoming email to a folder, wherein the folder is an inbox folder or a junk mail folder, or to prevent the incoming email from reaching the user, based at least partially on

the user'"'"'s email routing preferences,

the determination of the email identification analysis code, and

the email sender registration information,

wherein the email routing code is configured to deliver the incoming email to the junk folder if the email identification analysis code determines that the incoming email is commercial bulk email, the email sender is a paying sender, and the user'"'"'s email routing preferences indicate that commercial bulk email from a paying sender is to be delivered to the junk mail folder.

2. The email processing system of claim 1, further comprising a digital signature processor configured to authenticate the email sender.

3. The email processing system of claim 1, wherein the email routing code is configured to deliver the incoming email to the inbox folder if the email identification analysis code determines that the incoming email is not commercial bulk email.

4. The email processing system of claim 1, wherein the email routing code is configured to deliver the incoming email to the junk mail folder if

the email identification analysis code determines that the incoming email is commercial bulk email,

the email sender is a nonpaying sender, and

the user'"'"'s email routing preferences indicate that commercial bulk email from a nonpaying sender is to be delivered to the junk mail folder.

5. The email processing system of claim 1, wherein the email routing code is configured to prevent the incoming email from reaching the user if

the email identification analysis code determines that the incoming email is commercial bulk email,

the email sender is a nonpaying sender, and

the user'"'"'s email routing preferences indicate that commercial bulk email from a nonpaying sender is not to be delivered to the user.

6. The email processing system of claim 1, wherein the email routing code is configured to deliver the incoming email to the inbox folder if

the email identification analysis code determines that the incoming email is commercial bulk email,

the email sender is a nonpaying sender, and

the user'"'"'s email routing preferences indicate that commercial bulk email from a nonpaying sender is to be delivered to the inbox folder.

7. The email processing system of claim 1, wherein the email routing code is configured to deliver the incoming email to the inbox folder if

the email identification analysis code determines that the incoming email is commercial bulk email,

the email sender is a paying sender, and

the user'"'"'s email routing preferences indicate that commercial bulk email from a paying sender is to be delivered to the inbox folder.

8. A method for processing email comprising:

receiving an incoming email addressed to a recipient;

identifying a sender of the incoming email and determining if the sender is a paying sender;

determining if the recipient has elected to receive nonpaying email from the sender;

determining if the recipient has elected to receive commercial bulk email from paying senders;

determining if the incoming email is commercial bulk email;

if the incoming email is not determined to be commercial bulk email, delivering the incoming email to an inbox folder; and

if the incoming email is determined to be commercial bulk email

(a) delivering the incoming email to a junk mail folder if the sender is not a paying sender and if the recipient has not elected to receive nonpaying email from the sender;

(b) delivering the incoming email to an inbox folder if the sender is not a paying sender and if the recipient has elected to receive nonpaying email from the sender;

(c) delivering the incoming email to a junk mail folder if the sender is a paying sender and if the recipient has not elected to receive paying email from the sender;

(d) delivering the incoming email to an inbox folder if the sender is a paying sender and if the recipient has elected to receive paying email from paying senders.

9. The method of claim 8, further comprising storing a recipient'"'"'s email routing preferences and a sender'"'"'s payment status in a database.

10. The method of claim 8, wherein the sender is identified as a paying sender using a secure token embedded in the incoming email.

11. The method of claim 8, wherein the sender is identified as a paying sender using a secure token that is embedded in the incoming email and that is issued and authenticated by a digital signature processor.

12. An apparatus comprising:

code, which when executed is configured to selectively deliver an incoming email to an inbox folder or a junk mail folder based on first and second user preference settings, wherein the first user preference setting controls whether an email recipient receives nonpaying emails from a particular sender, and wherein the second user preference setting controls whether an email recipient receives commercial bulk email from paying senders in the inbox folder; and

an accounting module configured to authenticate a sender of commercial bulk email as a paying sender, wherein the accounting module causes a charge to be applied to an account associated with the paying sender upon receipt of commercial bulk email from the paying sender in the inbox folder.

13. The apparatus of claim 12, further comprising a database configured to store first and second user preference settings for a plurality of users.

14. The apparatus of claim 12, wherein the accounting module is further configured to periodically compile a list of charges associated with the sender of commercial bulk email.

15. The apparatus of claim 12, wherein the accounting module authenticates a paying sender of commercial bulk email using a secure token embedded in the email.

16. The apparatus of claim 12, wherein the accounting module uses a digital signature processor to authenticate the sender of commercial bulk email.

17. The apparatus of claim 12, wherein the accounting module authenticates the paying sender of commercial bulk email using a secure token embedded in the email.

18. The apparatus of claim 12, wherein an incoming paid commercial bulk email includes a secure token, and wherein the accounting module authenticates the secure token using a digital signature processor.

19. An apparatus comprising:

a first instruction configured to identify a sender of an email and determine if the sender is a paying sender;

a second instruction configured to determine if a recipient of the email has elected to receive nonpaying email from the sender;

a third instruction configured to determine if a recipient of the email has elected to receive commercial bulk email from a paying sender;

a fourth instruction configured to determine if the email is commercial bulk email; and

a fifth instruction configured to deliver the email to an inbox folder or a junk mail folder based on the determinations made by the first and fourth instructions, and at least one of the second and third instructions.

20. The apparatus of claim 19, wherein the determination made in the first instruction is based on whether a secure token is included in the email.

21. The apparatus of claim 19, wherein the determination made by the first instruction is performed by a digital signature processor that authenticates a secure token included in the email.

22. The apparatus of claim 19, further comprising a server that hosts the first, second, third, fourth and fifth instructions.