ALIAS MANAGEMENT PLATFORMS

• US 20100036925A1
• Filed: 08/07/2009
• Published: 02/11/2010
• Est. Priority Date: 08/07/2008
• Status: Abandoned Application

• Current Assignee: That Is, LLC
• Original Assignee: Tactara, LLC
• Inventors: Haffner, Crosby
• Application Number:
  US12/537,454
• Publication Number:
  US 20100036925A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 51/48 Message addressing, e.g. address format or anonymous messages, aliases

Abstract

Systems and methods of managing alias are disclosed. An alias management system can provide for creating distribution lists comprising one or more addresses. A list owner can utilize the system to retain ownership and control of the addresses by creating aliases for the list. Additionally, an alias policy can be established that includes rules and metrics that govern the use of the alias. The alias can be provided to alias users or members of a message distribution chain, preferably in exchange for a fee. The alias users can then use the alias to send message content, while the system can enforce the alias usage policy or provide an auditing trail on how the alias is used.

Claims

1. A method of managing aliases, the method comprising:

providing an alias management server;

storing a distribution list on the alias management server;

creating at least one alias that points to the distribution list;

establishing an alias policy governing usage of the at least one alias; and

providing at least one alias user the at least one alias according to the alias policy via an interface.

2. The method of claim 1, wherein the step of storing the distribution list includes allowing a list owner to upload the distribution list to the alias management server.

3. The method of claim 1, wherein the step of storing the distribution list includes aggregating the distribution list from addresses associated with a first distribution list owned by a first list owner, and with a second distribution list owned by a second, different list owner.

4. The method of claim 3, wherein the step of aggregating includes matching desired list attributes from the alias user with list attributes associated with the first and second distribution lists.

5. The method of claim 4, wherein the list attributes include address attributes.

6. The method of claim 1, where the step of establishing the alias policy includes establishing at least one alias usage metric.

7. The method of claim 6, further comprising updating the at least alias one usage metric according to the alias policy and in response to the at least one alias user interacting with the at least one alias.

8. The method of claim 6, further comprising enforcing rules of the alias policy as a function of alias usage metrics.

9. The method of claim 8, wherein the step of enforcing the rules includes taking an action selected from the group consisting of:

validating the at least one alias, validating the alias user using the at least one alias, restricting when a message sent to the at least one alias, restricting a number of messages sent to the at least one alias, restricting a rate that messages are sent to the at least one alias, restricting message content sent to the at least one alias, restricting a size of a message sent to the at least one alias, and disabling the at least one alias.

10. The method of claim 1, wherein the step of establishing the alias policy includes automatically updating one of the at least one alias and the alias policy in response to changes to the distribution list.

11. The method of claim 1, further comprising automatically updating the distribution list via a list interface provided to a list owner.

12. The method of claim 1, wherein the step of providing the at least one alias includes charging the at least one alias user a fee in exchange for access to the at least one alias.

13. The method of claim 1, further comprising authenticating the at least one alias user with respect to the alias management server according the alias policy.

14. The method of claim 1, wherein the at least one alias user is a member of distribution chain.

15. The method of claim 14, further comprising providing each member of the distribution chain their own alias that points to the distribution list.

16. The method of claim 14, further comprising provided each member of the distribution chain their own alias that points to another alias managed by the alias management server.

17. The method of claim 1, further comprising the alias management server, upon receipt of messaging from the at least one alias user to the at least one alias, causing a message to be sent to members of the distribution list.

18. The method of claim 17, further comprising the alias management server sending the message.

19. The method of claim 17, further comprising the alias management server authorizing a third party delivery service to send the message.

20. The method of claim 17, further comprising the alias management server configuring a secure virtual machine on a server operated by the at least one alias user and sending the message from the secure virtual machine.

21. The method of claim 17, further comprising the alias management server sending the message from a virtual content server having a temporary top level domain.