IP Library Granted Patent US 8,499,042
Granted Patent B2
US 8,499,042 · App. 10/864,141 · Granted Jul 30, 2013

System for managing e-mail traffic

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,499,042
App. No.
10/864,141
Granted
Jul 30, 2013
Kind
B2
Abstract

According to a first embodiment of the invention, if an e-mail sender attempts to make too many connections within a predetermined period of time, the excess connections are automatically rejected. According to a second embodiment of the invention, an agreement is established between an e-mail sender and an e-mail recipient that states when the sender may send e-mail messages to the recipient. According to a third embodiment of the invention, trend data reflecting an amount of e-mail sent by a sender is collected. The trend data can be used to establish a rate limit for the sender. According to a fourth embodiment of the invention, separate rate limits are established for authenticated and unauthenticated mail from addresses. According to a fifth embodiment of the invention, a sender may have a rate at which their e-mail is transmitted reduced if they exceed predetermined rate limits.

Claims (76)

1. A computer implemented method for managing network traffic comprising:

receiving an incoming transmission at a recipient mail transfer agent (MTA) at a specific time;

determining an address belonging to a sender of the incoming transmission;

determining a date or time of day during which the sender is allowed to establish a connection to the recipient MTA using the address;

rejecting the connection if the date or time of day at which the incoming transmission is received does not lie within the date or time of day during which the sender is allowed to establish a connection;

determining a rate limit for transmissions sent from the sender based on a number of transmissions previously sent by the sender over a recurring period of time, the time of the incoming transmission lying within the time period, by:

maintaining a trend database including a historical trend of transmission activity by the sender over the recurring period of time; and

using the historical trend to establish the rate limit;

rejecting the connection if the rate limit has been exceeded by the sender; and

accepting the connection if the date or time of day at which the incoming transmission is received lies within the date or time of day during which the sender is allowed to establish a connection and the rate limit has not been exceeded by the sender;

further comprising:

determining the historical trend by averaging transmission activity of the sender during the recurring period of time over a predetermined number of recurring periods.

2. The computer implemented method of claim 1 , wherein the incoming transmission relates to an e-mail transmission sent using the simple mail transfer protocol (SMTP) and wherein the connection is a Transmission Control Protocol (TCP) connection.

3. The computer implemented method of claim 1 , wherein the incoming transmission is allowed only on a specified date or on specified dates and only at a specified time or specified times of day.

4. The computer implemented method of claim 1 , further comprising:

maintaining a conditional allowed list that specifies a date or time of day at which the sender can send the incoming transmission to the recipient MTA; and

wherein determining a date or time of day during which the sender is allowed to establish a connection to the recipient MTA comprises comparing the date or time of day at which the incoming transmission is received with the conditional allowed list.

5. The computer implemented method of claim 4 , wherein the incoming transmission is allowed only on a specified date or on specified dates and only at a specified time or times of day.

6. The computer implemented method of claim 1 , wherein the averaging transmission activity comprises:

averaging a number of messages sent by the sender.

7. The computer implemented method of claim 1 , wherein the averaging transmission activity comprises:

averaging an amount of data sent by the sender.

8. The computer implemented method of claim 1 , further comprising:

reaching an agreement with the sender to establish the date or time of day.

9. The computer implemented method of claim 1 , wherein the address comprises an Internet Protocol (IP) address.

10. A computer implemented method for managing network traffic comprising:

receiving an incoming transmission at a recipient mail transfer agent (MTA) at a specific time, wherein the incoming transmission relates to an e-mail transmission sent using the simple mail transfer protocol (SMTP);

determining an address belonging to a sender of the incoming transmission;

determining a date or time of day during which the sender is allowed to establish a Transmission Control Protocol (TCP) connection to the recipient MTA using the address;

rejecting the TCP connection if the date or time of day at which the incoming transmission is received does not lie within the date or time of day during which the sender is allowed to establish a TCP connection;

determining a rate limit for transmissions sent from the sender, wherein the rate limit is determined based on a number of transmissions previously sent by the sender over a recurring period of time, the time of the transmission lying within the time period, by:

maintaining a trend database including a historical trend of transmission activity by the sender over the recurring period of time; and

using the historical trend for the sender to establish the rate limit;

rejecting the TCP connection if the rate limit has been exceeded by the sender; and

accepting the TCP connection if the date or time of day at which the incoming transmission is received lies within the date or time of day during which the sender is allowed to establish a TCP connection and the rate limit has not been exceeded by the sender;

further comprising:

determining the historical trend by averaging transmission activity of the sender during the recurring period of time over a predetermined number of recurring periods.

11. The computer implemented method of claim 10 , further comprising:

maintaining a conditional allowed list that specifies a date or time of day at which the sender can establish a connection; and

wherein determining a date or time of day during which the sender is allowed to establish the TCP connection to the recipient using the address comprises comparing the date or time of day at which the incoming transmission is received with the conditional allowed list.

12. A system for managing network traffic comprising:

a server having a mail transfer agent (MTA) and non-transitory storage, wherein the non-transitory storage comprises instructions that, when executed by the MTA, configure the MTA to:

receive an incoming transmission at a specific time;

determine an address belonging to a sender of the incoming transmission;

determine a date or time of day during which the sender is allowed to send the incoming transmission to the server using the address;

reject the incoming transmission if the date or time of day at which the incoming transmission is received does not lie within the date or time of day during which the sender is allowed to send the incoming transmission;

determine a rate limit for transmissions sent from the sender, wherein the rate limit is determined based on a number of transmissions previously sent by the sender over a recurring period of time, the time of the transmission lying within the time period, by:

maintaining a trend database including a historical trend of transmission activity by the sender over the recurring period of time; and

using the historical trend for the sender to establish the rate limit;

reject the incoming transmission if the rate limit has been exceeded by the sender; and

accept the incoming transmission if the date or time of day at which the incoming transmission is received lies within the date or time of day during which the sender is allowed to send the incoming transmission and the rate limit has not been exceeded by the sender;

further comprising:

determining the historical trend by averaging transmission activity of the sender during the recurring period of time over a predetermined number of recurring periods.

13. The system of claim 12 , wherein the server is further configured to:

maintain a conditional allowed list that specifies a date or time of day at which the sender can send the incoming transmission to the server; and

wherein determining a date or time of day during which the sender is allowed to send the transmission to the server comprises comparing the date or time of day at which the incoming transmission is received with the conditional allowed list.

14. The system of claim 12 , wherein the averaging transmission activity comprises:

averaging a number of messages sent by the sender.

15. The system of claim 12 , wherein the averaging transmission activity comprises:

averaging an amount of data sent by the sender.

16. A system for managing network traffic comprising:

a server having a mail transfer agent (MTA) and non-transitory storage, wherein the non-transitory storage comprises instructions that, when executed by the MTA, configure the MTA to:

receive an incoming transmission at a specific time, wherein the incoming transmission relates to an e-mail transmission sent using the simple mail transfer protocol (SMTP);

determine an address belonging to a sender of the incoming transmission;

determine a date or time of day during which the sender is allowed to establish a Transmission Control Protocol (TCP) connection to the server using the address;

reject the TCP connection if the date or time of day at which the incoming transmission is received does not lie within the date or time of day during which the sender is allowed to establish a TCP connection;

determine a rate limit for transmissions sent from the sender, wherein the rate limit is determined based on a number of transmissions previously sent by the sender over a recurring period of time, the time of the incoming transmission lying within the time period, by:

maintaining a trend database including a historical trend of transmission activity by the sender over the recurring period of time; and

using the historical trend for the sender to establish the rate limit;

reject the TCP connection if the rate limit has been exceeded by the sender; and

accept the TCP connection if the date or time of day at which the incoming transmission is received lies within the date or time of day during which the sender is allowed to establish a TCP connection and the rate limit has not been exceeded by the sender;

further comprising:

determining the historical trend by averaging transmission activity of the sender during the recurring period of time over a predetermined number of recurring periods.

17. The system of claim 16 , wherein the server is further configured to:

maintain a conditional allowed list that specifies a date or time of day at which the sender can establish a TCP connection to the server; and

wherein determining a date or time of day during which the sender is allowed to establish a TCP connection to the server comprises comparing the date or time of day at which the incoming transmission is received with the conditional allowed list.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 16, 2013
From: UNWIRED PLANET, INC.
To: UNWIRED PLANET IP MANAGER, LLC
Reel/Frame 031030/0081 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 16, 2013
From: UNWIRED PLANET IP MANAGER, LLC
To: UNWIRED PLANET, LLC
Reel/Frame 031030/0115 →
MERGER Recorded Jun 26, 2012
From: OPENWAVE SYSTEMS INC.
To: UNWIRED PLANET, INC.
Reel/Frame 028447/0940 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 27, 2004
From: BROWN, BRUCE L.; SILBERMAN, SAMUEL G.; GRANOFF, MARK H.; CHAUBE, RAJESH P.; FLEISCHMAN, ROBERT M.; ZRALY, MICHAEL S.
To: OPENWAVE SYSTEMS INC.
Reel/Frame 015826/0747 →