You are on page 1of 8

SMAS ( Simple Mail Accessing System )

_____________________________________________________________________________

• TITLE OF THE PROJECT:

SIMPLE MAIL ACCESSING SYSTEM (SMAS)

• INTRODUCTION:

RFC 1939 dictates the features and commands of Post Office


Protocol Version 3 (POP3). Further, RFC 821, and updated version RFC
5321 [2008] dictates the features and commands of Simple Mail
Transfer Protocol (SMTP). These two protocols form the basis of Mail
Interchange System or Applications. The client side is implemented as
software, such as Windows Live Mail, Microsoft Outlook, Microsoft
Office Outlook, or any other mail software packages. These client
softwares are either pre-installed with the operating system or can be
as a separate application but cannot embed with a website directly to
facilitate users all over the network. The Server version is implemented
as a stand-alone or distributed application, that uses the Operating
System based Network Socket API to let the client applications connect
to them and interchange the required mailing information’s as a byte
stream. But these servers differ from any other servers on the Internet
or Intranet. The Mail Server must implement the POP3 and SMTP
protocols at application layer, as guided by RFC 1939, RFC 821 or RFC
5321. These protocols are nothing but text commands that the client
send to the server to perform the required work. The server in return,
processes the client command sent the client back with either the
query status, reply message or error report. The client receives this
reply and proceeds as required or can say “QUIT” to disconnect from
server.
Due to the complexity of the protocol’s processing on server,
Mail Client systems are generally available as commercial packages.

SRIJIT CHOWDHURY, Course: MCA Page - i


SMAS ( Simple Mail Accessing System )
_____________________________________________________________________________

But, the limitations of these commercial packages lies with the volume
of Mail processing did with them, and the higher cost of purchase or
maintenance. These limitations make the commercial Mail Client
packages inefficient for implementation or testing on a small-office or a
home based Intranet work systems.

• OBJECTIVE OF THE PROJECT:

The proposed project work, SMAS would deal with ‘SIMPLE


MAIL ACCESSING SYSTEM’, which would be applied to all websites
eager to get intra and internet mail access from their site. The project
would be compiled to PHP and would be deployed to a APACHE Web
Server with MySQL as database server.

I designed this Mail Client with the following objectives in mind:

1. Implement the minimal set of POP3 and SMTP command set as


required by their respective RFCs.
2. Minimize the cost of deployment and maintenance.
3. Can be deployed on any machine, with minimal hardware
requirements.
4. Interoperable over multiple client, operating systems and
network environment, with ease of use.
5. Simplified UI and deployment requirement can even be used
by novice users.

• PROJECT CATEGORY:

SRIJIT CHOWDHURY, Course: MCA Page - ii


SMAS ( Simple Mail Accessing System )
_____________________________________________________________________________

The project would be built with PHP using MySQL (Relational


Database Management System). Care would be taken to fully
utilise the PHP language (server side) and HTML (client side script). The
RDBMS back-end engine would be optimally burdened for necessary
searching, sorting and filtering via standard SQL queries.

• TOOLS/PLATFORM, HARDWARES & SOFTWARES


TO BE USED:

In the analysis phase I found that the ‘Simple Mail Accessing


System’ might be developed by PHP 5.3 (An open source server side
language) with MySQL/5.1.37 (A RDBMS back-end database engine)
and Apache/2.2.12 (Win32) as web server. Firstly I choose Widows
OS as the platform of my project due to its widest acceptability (though
LINUX or UNIX is also good for this project.) Secondly I choose PHP to
harvest the open source server side language with zero cost to use.
Thirdly I choose MySQL due to its tightest integration with PHP.
Fourthly I choose Dreamweaver8.0 for front end designing of web
pages for descent looking.

This project was developed on my Intel Dual Core 1.73GHz PC


with 512MB DDR2-RAM installed with Windows XP Professional, and
hopefully would run on P-III 550MHz PC with 128MB SDRAM installed
with Windows 2000 Home Edition at the lowest end. Detail testing
results would be submitted later.

SRIJIT CHOWDHURY, Course: MCA Page - iii


SMAS ( Simple Mail Accessing System )
_____________________________________________________________________________

• A COMPLETE STRUCTURE OF THE PROGRAM:

(I) Analysis:

CONTEXT DIAGRAM

PERSON INTER-MAIL
USER

Request for Request replied


creating new
account Request
for
Inter-mail access
Request replied

Request
for
SMAS Admin page
access
ADMINISTRATOR
Request replied

Request replied

Request for Request


Intra-mail access for
Inter-mail access

INTRA-MAIL
USER Request replied

ADMINISTRATOR

SRIJIT CHOWDHURY, Course: MCA Page - iv


SMAS ( Simple Mail Accessing System )
_____________________________________________________________________________

Data Flow Diagram

WEB
SERVER
SENDER (SMAS) Database

Mail
SMTP
server RECEIVER
SERVER File
System

IMAP
SERVER

POP
SERVER

SRIJIT CHOWDHURY, Course: MCA Page - v


SMAS ( Simple Mail Accessing System )
_____________________________________________________________________________

(ii) ERD

username
id name user_pass
password uid

level registered_me 1 1 time


Has logged_users
mbers
1 1

countr
level
y

Has H
ba Prio as
s r
m ed i ity
ail nt
in ra
g

message
ac_id
N N

usernam email_account mail


e sentdate

mail_i
d
email host userfrom status
userto
password subjec
t

SRIJIT CHOWDHURY, Course: MCA Page - vi


SMAS ( Simple Mail Accessing System )
_____________________________________________________________________________

• Data Structure for all modules:

1. Table Name: registered_members

Data Leng
Field Name Type th Purpose
Id Int 4 Unique identity the registered member
Name Varchar 65 Name of the registered member
Email Varchar 65 Email ID of registered member
Password Varchar 65 Password of the registered member
Country Varchar 65 Country name of the registered member

2. Table Name: logged_users

Data Leng
Field Name Type th Purpose
int
Uid (identity) 11 Unique identity of the logged user
Username Varchar 65 User name of logged member
user_pass Varchar 65 Hashed username-password combination
Time Time Date and time of login
Level Int 1 User level

3. Table Name: mail

Data Lengt
Field Name Type h Purpose
userTo Tinytext User name of the recipient user (intra mail)
userFrom Tinytext User name of the sender (intra mail user)
Medium
Subject text Subject of the mail
Message Long text Message (body) of the mail
Status Text Status (read or unread) of the message
sentDate Text Date of the sending mail
mail_id Int 80 Unique Identity of the mail

4. Table Name: email_account

SRIJIT CHOWDHURY, Course: MCA Page - vii


SMAS ( Simple Mail Accessing System )
_____________________________________________________________________________

Data Lengt
Field Name Type h Purpose
ac_id Int 11 Unique identity of the email account
Username Varchar 65 Name of the registered user
Email Varchar 65 Email address of the account
Password Varchar 40 Password of the email account
Host Varchar 40 Host name of the email id

SRIJIT CHOWDHURY, Course: MCA Page - viii

You might also like