System and method for generic loop detection

• US 9,628,412 B2
• Filed: 05/07/2013
• Issued: 04/18/2017
• Est. Priority Date: 05/08/2012
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: St. Clair, Brian, Humphreys, Joseph
• Primary Examiner(s): TRUONG, LAN DAI T
• Application Number:
  US13/889,291
• Publication Number:
  US 20130304833A1
• Time in Patent Office: 1,442 Days
• Field of Search: 709206, 709201, 709202, 709203
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/02 using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages
• CPC Class Codes: H04L 51/212 using filtering or selective blocking

Abstract

A system and method for detecting generic loops is described. In one example, an inbound email is inspected for a loop token. If a loop token is found, then an event identification and a sender identification is extracted. The extracted sender identification and event identification is applied to a loop token record, and the inbound email is conditionally discarded based on the application to the loop token record.

Claims

1. A computer-implemented method for blacklisting an email sender, the computer having at least a processor and a memory, the method comprising:

inspecting, by an email system, a first inbound email with a first token in the first inbound email;

creating, by the email system, a second token from the first token, the second token having a counter, and inserting the second token in the first inbound email to replace the first token;

receiving, by the email system, a second inbound email with the second token; and

,

adding, by the email system, a sender of the second inbound email to a blacklist and storing the blacklist at the email system.

2. The method of claim 1, further comprising:

extracting an event identification and a sender identification from the first token of the first inbound email;

applying the extracted sender identification and event identification to a token record; and

conditionally discarding the first inbound email, by the email system, based on the applying of the extracted sender identification and event identification to the token record.

3. The method of claim 2, wherein conditionally discarding the first inbound email comprises discarding if the token record indicates that all inbound emails are to be discarded that have tokens containing the extracted sender identification and even identification.

4. The method of claim 2, wherein the extracted sender identification identifies a penultimate sender, the penultimate sender being a sender preceding a sender from which the first inbound email is received.

5. The method of claim 2, wherein the first token further comprises a loop counter and wherein the first inbound email is discarded if the loop counter exceeds a predefined number of counts.

6. The method of claim 2, wherein inspecting comprises inspecting an In-Reply-To header of the first inbound email.

7. The method of claim 2, further comprising:

comparing the sender identification and the event identification against a. blacklist; and

if the sender identification and the event identification are on the blacklist, then discarding the first inbound email.

8. The method of claim 7, wherein a sender is on the blacklist for a specific event.

9. The method of claim 8, wherein a sender is on the blacklist for a specific time duration.

10. The method of claim 7, further comprising removing the sender from the blacklist for the event after a specific time duration.

11. The method of claim 7, further comprising sending a notification to a user that the user is blacklisted for the specific event.

12. The method of claim 1, further comprising:

inspecting an outbound email for a token before receiving the first inbound email; and

creating the first token for the outbound email if the outbound email has no token, the first token identifying the sender of the outbound email using a sender identification and an event using an event identification.

13. The method of claim 12, wherein the first token further comprises a counter.

14. The method of claim 1, further comprising:

generating a loop state for the first inbound email, the loop state containing a sender identification and an event Identification;

storing the loop state in a cache of the email system;

receiving an outbound email for an a specific event corresponding to the event identification after generating the loop state; and

generating a second token based on the generated loop state and attaching the second token to the outbound email.

15. The method of claim 14, wherein the loop state further contains a timestamp.

16. The method of claim 1, further comprising

receiving an outbound email with the first token and inserting the second token into the outbound email.

17. The method of claim 16, wherein the second inbound email is a reply to the outbound email.

18. A non-transitory computer-readable medium having instructions stored thereon that when executed cause a computer to perform operations comprising:

inspecting a first inbound email with a first token in the first inbound email;

creating a second token from the first token, the second token having a counter, and inserting the second token in the first inbound email to replace the first token;

receiving a second inbound email with the second token; and

adding a sender of the second inbound email to a blacklist and storing the blacklist at the email system.

19. The medium of claim 18, the operations further comprising receiving an outbound email with the first token and inserting the second token into the outbound email.

20. The medium of claim 19, wherein the second inbound email is a reply to the outbound email.

21. An email application server comprising:

a network interface for connection to a plurality of email client terminals to receive an inbound email; and

a processing unit includes a memory configured to execute functions of the email application server including to inspect a first Inbound email with a first token In the first inbound email, to create a second token from the first token, the second token having a counter, and insert the second token in the first inbound email to replace the first token, to receive a second inbound email with the second token, and to add a sender of the second inbound email to a blacklist and storing the blacklist at the email system.

22. The email application server of claim 21, wherein the processing unit is further configured to receive an outbound email with the first token and to insert the second token into the outbound email.

23. The email application server of claim 22, wherein the second inbound email is a reply to the outbound email.