System and method for managing emails in an enterprise

• US 20050262208A1
• Filed: 06/16/2004
• Published: 11/24/2005
• Est. Priority Date: 05/21/2004
• Status: Abandoned Application

• Current Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Original Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Inventors: Daloya, David, Haviv, Eyal, Shlezinger, Doron
• Application Number:
  US10/869,530
• Publication Number:
  US 20050262208A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/212 using filtering or selective blocking

Abstract

This disclosure provides a system and method for managing emails in an enterprise. In one embodiment, an enterprise email manager is operable to receive a first email to one or more expected recipients. The first email is identified as an adverse email based, at least in part, on one or more of a plurality of enterprise parameters and quarantined. A report email is generated based on the first email, with the report email comprising information identifying the first email and the report email is operable to present dynamic administrative actions associated with the first email. The enterprise email manager then communicates the report email to at least a particular one of the expected recipients.

Claims

1. An enterprise email manager operable to:

receive a first email to one or more expected recipients;

identify the first email as an adverse email based, at least in part, on one or more of a plurality of enterprise parameters;

quarantine the first email;

generate a report email based on the first email, the report email comprising information identifying the first email and the report email operable to present dynamic user-managed actions associated with the first email; and

communicate the report email to at least a particular one of the expected recipients.

2. The enterprise email of claim 1, the user-managed actions comprising at least one of the following:

release;

delete;

leave; and

not spam.

3. The enterprise email manager of claim 1 further operable to:

receive a selection of one of the user-managed actions associated with the first email; and

process the first email based, at least in part, on the received selection.

4. The enterprise email manager of claim 3 further operable to generate a user parameter based on the received selection.

5. The enterprise email manager of claim 4 further operable to:

receive a second email to one or more expected recipients, the second email being substantially similar to the first email;

compare the user parameter to the one or more expected recipients of the second email; and

at least partially in response to the user parameter being associated with a particular one of the expected recipients of the second email, communicate the second email to the particular recipient.

6. The enterprise email manager of claim 3, the received selection comprising a Hyper Text Markup Language (HTML) request.

7. The enterprise email manager of claim 1 further operable to:

receive a second email to one or more expected recipients, the particular one of the expected recipients from the first email being one of the expected recipients from the second email;

identify the second email as an adverse email based, at least in part, on at least one of the plurality of enterprise parameters;

quarantine the second email; and

wherein the manager operable to generate the report email comprises manager operable to generate the report email based, at least in part, on the first and second emails, the information comprising first information identifying the first email, the report email further comprising second information identifying the second email and the report email further operable to present dynamic user-managed actions associated with the second email.

8. The enterprise email manager of claim 7 further operable to communicate the generated report email to the particular one of the expected recipients based on predetermined criteria.

9. The enterprise email manager of claim 8, the predetermined criteria selected from the group consisting of:

a predetermined time;

in response to a request from the particular one of the expected recipients;

upon receipt of a number of emails for the particular one of the expected recipients;

or

a number of quarantined emails for the particular one of the expected recipients.

10. The enterprise email manager of claim 1, the report email further operable to present global actions associated with the first and second emails.

11. The enterprise email manager of claim 1, the report email comprising a plain text email associated with an HTML attachment.

12. The enterprise email manager of claim 1 further operable to:

compare the first email to at least one user parameter; and

generate and communicate the report email at least partially in response to the comparison.

13. The enterprise email manager of claim 1, at least a subset of the plurality of enterprise parameters comprising an enterprise-wide policy.

14. The enterprise email manager of claim 1 comprising:

a plurality of scanning engines, each scanning engine operable to;

receive the first email; and

identify the first email as an adverse email; and

a quarantine manager operable to;

receive the identified email from one of the scanning engines;

quarantine the email in a quarantine repository;

generate the report email; and

communicate the report email to the particular one of the expected recipients.

15. A method for managing emails in an enterprise comprising:

receiving a first email to one or more expected recipients;

identifying the first email as an adverse email based, at least in part, on one or more of a plurality of enterprise parameters;

quarantining the first email;

generating a report email based on the first email, the report email comprising information identifying the first email and the report email operable to present dynamic user-managed actions associated with the first email; and

communicating the report email to at least a particular one of the expected recipients.

16. The method of claim 15, the user-managed actions comprising at least one of the following:

release;

delete;

leave; and

not spam.

17. The method of claim 15 further comprising:

receiving a selection of one of the user-managed actions associated with the first email; and

processing the first email based, at least in part, on the received selection.

18. The method of claim 17 further operable to generate a user parameter based on the received selection.

19. The method of claim 17 further comprising:

receiving a second email to one or more expected recipients, the second email being substantially similar to the first email;

comparing the user parameter to the one or more expected recipients of the second email; and

at least partially in response to the user parameter being associated with a particular one of the expected recipients of the second email, communicating the second email to the particular recipient.

20. The method of claim 17, the received selection comprising a Hyper Text Markup Language (HTML) request.

21. The method of claim 15 further comprising:

receiving a second email to one or more expected recipients, the particular one of the expected recipients from the first email being one of the expected recipients from the second email;

identifying the second email as an adverse email based, at least in part, on at least one of the plurality of enterprise parameters;

quarantining the second email; and

wherein generating the report email comprises generating the report email based, at least in part, on the first and second emails, the information comprising first information identifying the first email, the report email further comprising second information identifying the second email and the report email further operable to present dynamic user-managed actions associated with the second email.

22. The method of claim 21 further comprising communicating the generated report email to the particular one of the expected recipients based on predetermined criteria.

23. The method of claim 22, the predetermined criteria selected from the group consisting of:

a predetermined time;

in response to a request from the particular one of the expected recipients;

upon receipt of a number of emails for the particular one of the expected recipients;

or

a number of quarantined emails for the particular one of the expected recipients.

24. The method of claim 15, the report email further operable to present global actions associated with the first and second emails.

25. The method of claim 15, the report email comprising a plain text email associated with an HTML attachment.

26. The method of claim 15 further comprising:

comparing the first email to at least one user parameter; and

generating and communicating the report email at least partially in response to the comparison.

27. The method of claim 15, at least a subset of the plurality of enterprise parameters comprising an enterprise-wide policy.

28. A method for managing emails in an enterprise comprising:

receiving a first email at one of a plurality of scanning engine;

identifying the first email as an adverse email at the scanning engine;

receiving the identified email from one of the scanning engines at a quarantine manager;

quarantining the email in a quarantine repository;

generating a report email based on the first email, the report email comprising information identifying the first email and the report email operable to present dynamic user-managed actions associated with the first email; and

communicating the report email to at least a particular one of the expected recipients.

29. A server for managing emails in an enterprise comprising:

memory operable to store a plurality of enterprise parameters; and

one or more processors operable to;

receive a first email to one or more expected recipients;

identify the first email as an adverse email based, at least in part, on one or more of the plurality of enterprise parameters;

quarantine the first email in memory;

generate a report email based on the first email, the report email comprising information identifying the first email and the report email operable to present dynamic user-managed actions associated with the first email; and

communicate the report email to at least a particular one of the expected recipients.

30. The server of claim 29, the user-managed actions comprising at least one of the following:

release;

delete;

leave; and

not spam.

31. The server of claim 29, the one or more processors further operable to:

receive a selection of one of the user-managed actions associated with the first email; and

process the first email based, at least in part, on the received selection.

32. The server of claim 31, the one or more processors further operable to generate a user parameter based on the received selection.

33. The server of claim 31, the one or more processors further operable to:

receive a second email to one or more expected recipients, the second email being substantially similar to the first email;

compare the user parameter to the one or more expected recipients of the second email; and

at least partially in response to the user parameter being associated with a particular one of the expected recipients of the second email, communicate the second email to the particular recipient.

34. The server of claim 31, the received selection comprising a Hyper Text Markup Language (HTML) request.

35. The server of claim 29, the one or more processors further operable to:

receive a second email to one or more expected recipients, the particular one of the expected recipients from the first email being one of the expected recipients from the second email;

identify the second email as an adverse email based, at least in part, on at least one of the plurality of enterprise parameters;

quarantine the second email in memory; and

wherein the one or more processors operable to generate the report email comprises one or more processors operable to generate the report email based, at least in part, on the first and second emails, the information comprising first information identifying the first email, the report email further comprising second information identifying the second email and the report email further operable to present dynamic user-managed actions associated with the second email.

36. The server of claim 35, the one or more processors further operable to communicate the generated report email to the particular one of the expected recipients based on predetermined criteria.

37. The server of claim 36, the predetermined criteria selected from the group consisting of:

a predetermined time;

in response to a request from the particular one of the expected recipients;

upon receipt of a number of emails for the particular one of the expected recipients;

or

a number of quarantined emails for the particular one of the expected recipients.

38. The server of claim 29, the report email further operable to present global actions associated with the first and second emails.

39. The server of claim 29, the report email comprising a plain text email associated with an HTML attachment.

40. The server of claim 29, the one or more processors further operable to:

compare the first email to a user parameter; and

generate and communicate the report email at least partially in response to the comparison.

41. The server of claim 29, at least a subset of the plurality of enterprise parameters comprising an enterprise-wide policy.

42. A system for managing emails in an enterprise comprising:

means for receiving a first email to one or more expected recipients;

means for identifying the first email as an adverse email based, at least in part, on one or more of a plurality of enterprise parameters;

means for quarantining the first email;

means for generating a report email based on the first email, the report email comprising information identifying the first email and the report email operable to present dynamic user-managed actions associated with the first email; and

means for communicating the report email to at least a particular one of the expected recipients.