×

Email service

  • US 7,673,000 B2
  • Filed: 04/28/2003
  • Issued: 03/02/2010
  • Est. Priority Date: 04/28/2003
  • Status: Expired due to Fees
First Claim
Patent Images

1. A method with computer readable instructions executable on a hardware processor, the method comprising:

  • Implementing one or more of primary database devices, one or more plurality of secondary database devices, one or more file sharing devices and a topological data storage device for one or more email clients on a distribution network;

    wherein each email within the network includes an email header and an email message;

    wherein the email header comprise a set of metadata corresponding to the RFC 2822 and the email header is an index use for the indexing the email message that is stores separately;

    wherein the one or more primary database devices and the one or more secondary database devices are used to store plurality of the email headers;

    wherein the one or more secondary database devices serve as a backup database of the one or more primary databases;

    using a log shipping process to replicate email headers from at least one of the primary database devices to at least one of the secondary database devices to eliminate a single point of failure;

    issuing at least one or more email-related requests by the one or more email clients;

    executing, by a load balancer, a load balancing algorithm to forward at least one or more email-related requests and to select at least one or more stateless protocol servers available to ensure the one or more email-related requests are serviced;

    each email-related requests include;

    an email, port assignments, number of sockets per server, worker threads, buffer sizes, physical storage address of each email client, and email client capacity data;

    using each stateless protocol server to parse one or more email-related requests by separate the email header and the email message that are in each email contained in one or more email-related requests;

    using each stateless protocol server to store the email header in the one or more primary database devices and to store the email message to one or more file share devices;

    setting a state of the email header to a committed state as the email message is successfully written into the one or more file share devices; and

    retrieving addresses that correspond to the email-related request or a requesting email clients for each of the one or more primary database devices and each of one or more file share devices;

    using the retrieving addresses by the one or more stateless protocol servers to access the one or more primary database devices and accessing one or more file share devices;

    wherein maintaining at least two copies of the email headers on the at least one of the file share devices to ensure a higher availability for a specific group of email clients that have a particular class of service;

    wherein the set of metadata in each email header includes data from a group consisting of a transaction state, a sender of the email, a subject of the email, a receipt date of the email, a size of the email message, an email recipient preference, email folder hierarchy data, a rule for filtering of the email message, an identification of an email recipient, a globally unique identifier of the email message, and a timestamp of when the email header was last modified;

    wherein each said stateless protocol server using a messaging protocol by which consistency in email header is maintained between the one or more of primary database devices and one or more plurality of secondary database devices.

View all claims
  • 2 Assignments
Timeline View
Assignment View
    ×
    ×