Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Machanism and Method to improve the utility of mail server storage space

IP.com Disclosure Number: IPCOM000234897D
Publication Date: 2014-Feb-13
Document File: 8 page(s) / 252K

Publishing Venue

The IP.com Prior Art Database

Abstract

This system provides a mechanism to improve the utility of mail server storage space using communal storage space. When user sends a bulk mail to many other users, with our mechanism, a local communal storage space on the server and global communal storage space for different servers will be used to save just one copy for the bulk mail. When receivers check the mail, it will link to the communal storage space or global communal space. This will save much storage space.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 8

Machanism and Method to improve the utility of mail server storage space

Nowadays, more and more enterprises are using their own email server to communicate inside the company. However, the email storage space can be easily run out especially when clients using IMAP protocol. So how to manage email storage space has become a common problem for enterprises.

Here is a common case, if a user sends a bulk mail to many other users (E.g.: Newsletter/Announcement with attachment to 1000 colleagues), the message will be sent to each receiver's mail space on the servers, which means, 1000 copies of the bulk mail on the server. Obviously, it will consume much space on the server and space on the client's storage space.

With our mechanism, when a user sends a bulk mail to many other users, a local communal storage space on the server and global communal storage space for different serverswill be used to save just one copy for the bulk mail. When receivers check the mail, it will link to the communal storage space or global communal space. This will save much storage space.

The details are as below:


3.1. Synchronize Mail to Communal Storage Space


1). When the sender send out an email, the sender's mail server begins to check if it triggers the Synchronize Process by using the Trigger Rule R1. If R1 equals false, the Synchronize Process will not be triggered, the original mail will be sent directly; If R1 equals true, the Synchronize Process will be triggered, continue with step 2).

Trigger Rule:


R1= [ ($MailSize > 5M) && ($ReceiversAmount > 100) ] || [($MailSize >1M) && ($MailSize * $ReceiversAmount >500M) ]


2). Synchronize the mail to sender's Local Communal Storage Space and Global Communal Storage Space .


3). If receiver's mail server is not the same as sender's mail server, and remote mail server (e.g. SERVER1) has more than the certain ratio (eg. 20%) of the receivers. Synchronize the mail to the remote Local communal Storage Space. For remote receivers in SERVER1, they will get the mail which is actually linked to the Remote Communal Storage Space.


4). If receiver's mail server is not the same as sender's mail server, and remote mail server has less than the certain ratio (eg.

1


Page 02 of 8

20%) of the receivers. All the receivers will get the mail which is actually linked to Global Communal Storage Space. The flow chart is as below:

2


Page 03 of 8

3


Page 04 of 8


3.2. Receivers get the mail


1) If the receiver is on the same server as the sender, it will link to the local communal storage space when receiver needs to check the mail.


2) If the receiver is on the different server from the sender and the mail has synchronized to receiver's local server from sender's server, it will link to the receiver's local communal storage space when receiver needs to check the mail.


3) If the receiver is on the different server from the sender and the mail is not synchronized to receiver's local server, it will link to the global communal storage spa...