Email management system

• US 20030200267A1
• Filed: 04/22/2002
• Published: 10/23/2003
• Est. Priority Date: 04/22/2002
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Garrigues, James F.
• Application Number:
  US10/127,520
• Publication Number:
  US 20030200267A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources

Abstract

An email system for controlling unsolicited email may include a server to manage email messages. The server may be configured to receive an email message from a sender. The email message may include a destination address of an email client and may include a code. If the included code is not a valid authorization code, the email server may not provide the email message to the email client. A request code for requesting an authorization code may be provided to the sender. If the email server receives an email message including the request code from the email sender, the email server may provide a portion of the email message to the email client for determining whether or not to provide an authorization code to the email sender.

Claims

1. A system comprising:

a plurality of email clients;

a server configured to;

receive an email message from a sender, wherein the email message comprises a destination address of one of the plurality of email clients;

determine if the email message comprises a valid authorization code; and

if the email message comprises a valid authorization code, provide the email message to the email client indicated by the destination address of the email message, and if the email message does not comprise a valid authentication code, not provide the email message to the email client indicated by the destination address of the email message.

2. The system as recited in claim 1, wherein the server is further configured access a database of authorization codes for email addresses to determine whether an authorization code provided with the email message is valid or invalid.

3. The system as recited in claim 1, wherein the server is further configured to, if the email message does not comprise a valid authorization code, send a reply email message to the sender of the email message, wherein the reply email message includes information for requesting a valid authorization code.

4. The system as recited in claim 3, wherein the information for requesting the valid authorization code includes a request code.

5. The system as recited in claim 4, wherein the information for requesting the valid authorization code further includes instructions on how to use the request code.

6. The system as recited in claim 4, wherein the information for requesting the valid authorization code further includes a time-to-live indicator corresponding to the request code, wherein the time-to-live indicator indicates a time at which the request code is scheduled to expire.

7. The system as recited in claim 4, wherein the request code is encoded in a non-text format.

8. The system as recited in claim 1, wherein the server is further configured to determine if the email message comprises a valid request code, wherein the valid request code identifies the email message as a request for a valid authorization code of an addressed client, and wherein if the email message comprises a valid request code, provide at least a portion of the email message to the email client indicated by the destination address of the email message.

9. The system as recited in claim 8, wherein, if the email message comprises a valid request code, the addressed email client is configured determine whether or not to send to send a valid authorization code to the sender in response to the email message including the valid request code.

10. The system as recited in claim 1, wherein, if the email message comprises a valid authorization code, the server is configured to provide the email message to the email client indicated by the destination address of the email message by storing the email message in an email box for the client.

11. The system as recited in claim 11, further comprising a database, wherein the database is configured to store one or more destination addresses and one or more authorization codes for each destination address, and wherein, to determine if the authorization code is a valid authorization code, the server is further configured to:

locate a destination address of the email message within the database; and

compare the one or more authorization codes corresponding to the destination address with the authorization code of the email message.

12. The system as recited in claim 11, wherein the database is further configured to store a request code for a destination address, wherein the request code is used to request an authorization code for the destination address.

13. The system as recited in claim 12, wherein the database is further configured to store a time-to-live indicator for the request code, wherein the time-to-live indicator indicates a time at which the request code is scheduled to expire.

14. A device, comprising:

a processor;

a memory operable to store program instructions, wherein the program instructions are executable by the processor to;

receive an email message from a sender, wherein the email message comprises a destination address corresponding to an email client;

determine if the email message comprises a valid authorization code; and

if the email message does not comprise a valid authorization code, not provide the message to the email client.

15. The device as recited in claim 14, wherein, if the email message does not comprise a valid authorization code, the program instructions are further executable to delete the email message.

16. The device as recited in claim 14, wherein the program instructions are further executable to, if the email message comprises a valid authorization code, provide the email message for access by the addressed email client.

17. The device as recited in claim 14, wherein the program instructions are further executable to, if the email message does not comprise the authorization code, send a reply email message to the sender of the email message, wherein the reply email message includes information for requesting a valid authorization code.

18. The device as recited in claim 17, wherein the information for requesting the authorization code includes a request code.

19. The device as recited in claim 18, wherein the information for requesting the authorization code further includes instructions on how to use the request code and a subject field of a request message to request an authorization code.

20. The device as recited in claim 18, wherein the request code is encoded in a non-text format.

21. The device as recited in claim 18, wherein the information for requesting the authorization code further includes a time-to-live indicator corresponding to the request code, wherein the time-to-live indicator indicates a time at which the request code is scheduled to expire.

22. The device as recited in claim 14, wherein the program instructions are further executable to, if the email message does not comprise the authorization code, determine if the email message comprises a valid request code, wherein the request code identifies the email message as a request for the authorization code of the client, and wherein if the email message comprises the request code, provide at least a portion of the email message to the email client indicated by the destination address of the email message.

23. The device as recited in claim 14, wherein the program instructions are further executable to, if the email message comprises an authorization code, determine if the authorization code is a valid authorization code by accessing a database of valid authorization codes.

24. The device as recited in claim 23, wherein, to determine if the authorization code is a valid authorization code, the program instructions are further executable to:

locate a destination address of the email message within the database;

retrieve one or more stored valid authorization codes from the database for the destination address; and

compare the one or more stored authorization codes from the database with the authorization code of the destination address.

25. The device as recited in claim 14, wherein the device is an email server.

26. The device as recited in claim 14, wherein the program instructions are further executable to determine if the email message comprises a valid authorization code by examining a username portion of the destination address.

27. A method comprising:

receiving an email message from a sender, wherein the email message comprises a destination address corresponding to an email client;

determining if the email message comprises a valid authorization code; and

if the email message does not comprise a valid authorization code, preventing the email message from reaching the email client indicated by the destination address of the email message.

28. The method as recited in claim 27, further comprising, if the email message does not comprise a valid authorization code, deleting the email message.

29. The method as recited in claim 27, further comprising, if the email message comprises a valid authorization code, providing the email message to the email client.

30. The method as recited in claim 27, further comprising, if the email message does not comprise a valid authorization code, sending a reply email message including information for requesting the authorization code to the sender of the email message.

31. The method as recited in claim 30, wherein the information for requesting the authorization code includes a request code.

32. The method as recited in claim 31, further comprising expiring the request code at a time indicated by a time-to-live indicator comprised by the information for obtaining the authorization code.

33. The method as recited in claim 27, further comprising:

determining if the email message comprises a valid request code identifying the email message as a request for a valid authorization code of the client; and

if the email message comprises a valid request code, providing at least a portion of the email message to the email client indicated by the destination address of the email message.

34. The method as recited in claim 33, further comprising, receiving user input indicating to send a valid authorization code in response to the message including the valid request code, wherein a valid authorization code is not sent if said user input is not received.

35. The method as recited in claim 27, further comprising accessing a database to determine if an authorization code of the email message is a valid authorization code.

36. The method as recited in claim 35, wherein determining if the authorization code is a valid authorization code comprises:

locating a destination address of the email message within the database;

retrieving one or more stored valid authorization codes from the database for the destination address; and

comparing the one or more stored authorization codes from the database with the authorization code of the destination address.

37. An article of manufacture comprising program instructions executable to implement:

receiving an email message from a sender, wherein the email message comprises a destination address corresponding to an email client;

determining if the email message comprises a valid authorization code; and

if the email message does not comprise a valid authorization code, preventing the email message from reaching the email client indicated by the destination address of the email message.

38. The article of manufacture as recited in claim 37, wherein the program instructions are further executable to implement, if the email message does not comprise the authorization code, deleting the email message.

39. The article of manufacture as recited in claim 37, wherein the program instructions are further executable to implement, if the email message comprises the authorization code, providing the email message for access by the addressed email client.

40. The article of manufacture as recited in claim 37, wherein the program instructions are further executable to implement, if the email message does not comprise the authorization code, sending a reply email message including information for requesting the authorization code to the sender of the email message.

41. The article of manufacture as recited in claim 40, wherein the information for requesting the authorization code includes a request code.

42. The article of manufacture as recited in claim 41, wherein the program instructions are further executable to implement expiring the request code at a time indicated by a time-to-live indicator comprised by the information for obtaining the authorization code.

43. The article of manufacture as recited in claim 37, wherein the program instructions are further executable to implement:

determining if the email message comprises a request code identifying the email message as a request for the authorization code of the client; and

if the email message comprises the request code, providing at least a portion of the email message to the email client indicated by the destination address of the email message.

44. The article of manufacture as recited in claim 43, wherein the program instructions are further executable to implement, providing a valid authorization code to the sender if instructed by the email client to provide a valid authorization code in response to the email message including the request code.

45. The article of manufacture as recited in claim 37, wherein the program instructions are further executable to implement, accessing a database to determine if an authorization code is a valid authorization code.