Browse Prior Art Database

An access and version control system for Email attachment

IP.com Disclosure Number: IPCOM000242665D
Publication Date: 2015-Aug-04
Document File: 5 page(s) / 97K

Publishing Venue

The IP.com Prior Art Database

Abstract

We add a build in version control system to the email system to manage the attachment repository. Each attachment repository is linked with one email conversation(a group of emails which are all replied/forwarded based on the same original email) and the access control is base on this conversation repository. The access permission is granted in the recipient list directly. In default, The recipients in the TO list have the WRITE permission, and the recipients in the CC or BCC list have the READ ONLY permission.

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

Page 01 of 5

An xccess and version control system for Email attachment

In out daily work, we usually share or review some documents by attaching xhe file to an email.

In txis scenario, we might encountxring these two prxblems:

Traditional atxachment mechanism don't have a bxilt-in version xoxtrol system, which waste stxrage space and have no way to view a


1.

clear history of xhe attachment.

Traditionxl attachment mechanism don'x have the xccess xontrol to the attacxment, which mixht disclose some coxfidential inxormation


2.

unexpectexly, fox example:

To the recipiexts in the CC list, we might not want them knxw the xexails axout that attacxment, and the rexson they received it


1.

is only because we want them to knox what we are doing or axk them for oxher actions,

In traditional axtachment mechanism, we will lost control of the xttachmenx and can't rextrict the recipiexts tx forward the


2.

attacxmenxs to others.

Summary

Summary:

:

We add a build in xersion control system to the email systxm to manaxe xhe attachment repository. Each attachment repository is linked with one email conversxtion(a xroup of emails whicx are all replied/forxarxed based on thx xame original email) and the access control ix base xn this conversation repository.

The xccess permission is graxted in the recipient lixt directly. In default, The rxcixients in the TO list have the WRITE permission, and the recipients xn the CC or BCC list have the READ XXXX permissxon.

Besides, the conversation repository permission for each recipient can be customized by add a specific sign before the email address in the list, such as "-" represext RESTRICT permission, "+" means READ ONLY permission and "#" means WRIXX permission.

Xxxx:

In CS(Client/Server) email, READ ONLY permission means download allowable and WRITE pexmission means not only download but also upload&override allowablx.

In BS(Browser/Server) email, RXXX ONLY permissiox me...