Client Computer Minimum Requirements For System Optimal Performance

1. Intel Celeron M340 processor with the clock speed of 1.50 GHz.
2. 256 MB of Random Access Memory (RAM).
3. 40 GB of Hard Disk Drive (HDD).
4. Network Interface Device (NID).
5. Screen resolution of 1399 * 768 pixels.

PSM 2 CD

The following items must be included in your PSM 2 CD.

1. Softcopy of your final PSM 2 report in .pdf and Word format.

2. All of the references referred and documents related (e.g. poster, log, etc) to your project.

3. The developed system (REMEMBER: It must include everything that is needed in order to let the system to run smoothly including hosting server, database, etc).

4. a readme.txt file that tells how to setup and configure your system.

5. a video about the walkthrough of your system (make a video to show how to use your system, take this as example "http://www.youtube.com/watch?v=WX_Xsonmkbg").

PSM 2 Poster

1. The poster must be in A3 size.
2. Specify your project's aim and introduction (introduction means what is your system doing and the fewer the word the better).
3. Show some of your system flows through printscreens.
4. Include UTM logo.
5. Include your name, IC No., matric No. and supervisor's name.

SFTS Synchronization

1. After SFTS logged into the registered eMail accounts, it keeps synchronizing with the eMail accounts every five minutes.
2. Alternatively, user can manually synchronize the eMail accounts by clicking "Refresh" button provided by the system.

Communication Protocol

1. SFTS communicates with the eMail servers with various types of protocols.
2. Simple Mail Transfer Protocol (SMTP) is used when SFTS is sending an eMail while Internet Mail Access Protocol (IMAP) and Post Office Protocol (POP3) is used when receiving eMails.

SFTS eMail Sending Problem

1. SFTS is having a problem in sending a multicast eMail. When a new eMail is composed and destined for more than one recipient, some of the recipients fail to receive it.
2. The cause of the problem is unknown but I am sure I will solve it.

eMail Address

1. When a user insert a recipient's eMail address in the new composing eMail, the system won't check the existance of the eMail.
2. Hence, the user has to insert the eMail correctly.

SFTS Private Key Characteristics

1. The private key assigned to the users can be copied by the users for backup purposes but if someone else especially those unauthorized secretly copies the key, the key is valid and usable in the system.
2. Future development and upgrade will prevent this phenomenon by only allowing the users to copy the key with the system new key copying sub-module instead of allowing the users to do this by themselves.

SFTS Account Username

1. When creating an account, the username can't contain the character "#" because the character has been reserved for the system.
2. Same thing happens to the registered eMail account, the character "#" is prohibited in the username.

Boxes Available In SFTS

1. The system mailbox is consisted of inboxes (one for each registered eMail account) and an outbox and a draft box.
2. The inboxes store the incoming eMails and outbox stores the sent eMails and the draft box stores the partially composed eMails.
3. There is only one outbox and one draft box (unlike inbox, one for each eMail account) that centralize the storage of eMails disregard of their eMail account.

Deletion Of eMail

1. When eMail(s) is deleted, it is not recoverable, hence, a confirmation dialog box will appear just before the deletion in order to allow the user to confirm the unrecoverable action.

SFTS Main Functions

1. The SFTS main functions are file transferring and cryptography.
2. In order to implemet those functions efficiently, two Java Libraries will be utilized; they are JCE (Java Cryptographic Extension) which implements the cryptographic function and JavaMail which implements file transferring function.

SFTS "chassis"

1. The "chassis" (aka the base structure) of the SFTS is a framework known as Struts.
2. Struts is a MVC (Model-View-Controller) framework which is freely available on the Internet and it is open-source.

System Account Credentials Editing

1. The system allows the changes of the password but the changes of the username is strictly prohibited since it is the identity to identify a user.

Contact Management

1. The system support contact management.
2. There is two types of contact

• Individual Contact
• Group Contact

3. After a contact is added, sender can access it immediately during new eMail composing without the necessary to remember the full address of the recipient(s).

User's eMail Account

1. Every user can create a maximum of five eMail accounts.
2. The eMail Service provider supported by the system is listed as followings

• Yahoo! Mail
• Gmail
• Windows Live Hotmail

Sending an encrypted eMail

1. When sending an encrypted eMail, only recipients who have SFTS accounts can receive it.
2. This is because encrypted eMail requires recipients' public keys to undergo encryption and only recipients who have SFTS accounts have public keys.

Sending an unencrypted eMail

1. When sending an unencrypted eMail, every recipient will receive it disregard whether she/he has a SFTS account (assuming recipients' eMail addressses entered by sender are correct).

Attachment

1. SFTS supports eMail attachment.
2. The maximum number of attachment supported by SFTS is 8 and the maximum size of each attachment is 25 MB.

eMail Message Format

1. SFTS supports rich-text format message. Common formatting such as bold, underline, italic, etc are available.
2. The formatting is the HTML (HyperText Markup Language) which is understandable by most text editors.
3. The proprietary formatting will not be processed and error message will be shown instead.

eMail Encryption

1. The level of encryption is divided into three levels, they are low, medium and strong.

2. Low level encryption

     - 1024-bit asymmetric encryption + 1 round 512-bit symmetric encryption

3. medium level encryption

     - 1024-bit asymmetric encryption + 3 round 512-bit symmetric encryption

4. strong level encryption

     - 2048-bit asymmetric encryption + 5 round 512-bit symmetric encryption

User's Key Pair

1. Each user will be given two pairs of keys (1 pair of 1024-bit private and public key and 1 pair of 2048-bit private and public key).

2. Public keys will be stored by the system while the private keys will be personally kept by the users.

3. Without the private keys, user can't view eMail's content and send eMail (user can only manage her/his contacts).

eMail Message Category

1. eMail message can be categorized into six major categories (I categorized personally). Please refer picture above for pictorial understanding.

Note

1. eMail with formatted message and attachment(s).

2. eMail with unformatted message and attachment(s).

3. eMail with formatted message but without attachment(s).

4. eMail with unformatted message but without attachment(s).

5. eMail without message but with attachment(s).

6. eMail without message and attachment(s).