INSTITUTE OF TECHNICAL EDUCATION AND

RESEARCH
SIKSHA ‘O’ ANUSANDHAN

(DEEMED TO BE UNIVERSITY)
DEPARTMENT OF COMPUTER SCIENCE AND INFORMATION TECHNOLOGY

ITER MAIL SYSTEM

PROJECT REPORT SUBMITTED BY:
Smruti Ranjan Nayak 1541017031
Sidharth Debasis 1541017042
Animesh Mishra 1541017268
Abinash Kumar Jena 1541017015

SUBJECT: WEB-DESIGN PROJECT REPORT

SEMESTER: 8TH
BRANCH & SEC: CSIT-‘A’

1
CERTIFICATE
It is hereby certified that this project report entitled “ITER Mail
System” submitted by Smruti Ranjan Nayak, Sidharth Debasis,
Animesh Mishra, Abinash Kumar Jena student of CSIT-A,8TH SEM,
ITER, SOA University in the partial fulfillment of the requirement for
the award of Bachelors of Technology (Computer Science Engineering)
is a record of students’ own study carried under my supervision &
guidance.
This report has not been submitted to any other university or institution
for the award of any degree.

Technical Head

2
ACKNOWLEDGEMENT

We sincerely express indebtedness to esteemed and revered guide Dr.

Smita Prava Mishra of Department Computer Science and Information
Technology for her invaluable guidance, supervision, and
encouragement throughout the work. Without her kind patronage and
guidance, the report would not have taken shape. Also, we thank her for
providing the computer lab facility. We would like to express our
sincere regards to her for advising and counseling from time to time. We
owe sincere thanks to all the faculties in Department of Computer
Science and Information Technology for their advice and counseling
from time to time.

3
 DECLARATION

We hereby declare that project report entitled “ITER MAIL SYSTEM”

submitted by Smruti Ranjan Nayak, Sidharth Debasis, Animesh Mishra,
Abinash Kumar Jena of CSIT-A ITER, SOA University in partial
fulfillment of the requirement for the award of the degree of B.TECH in
COMPUTER SCIENCE AND INFORMATION TECHNOLOGY
DEPARTMENT is a record of bonafide project work carried out by us
under the guidance of Dr. Smita Prava Mishra. The result embodied in
this thesis has not been submitted to any other institutions.

4
 CONTENTS

SL. No. TITLE PAGE

1 INTRODUCTION TO
ITER MAIL SYSTEM 7
1.1PROJECT DEFINITION 7
1.2 PROJECT USERS 7
1.3 PROJECT OVERVIEW 7
1.4 PROJECT REQUIREMENTS 8
1.5 OBJECTIVE 8
2 LITERATURE SURVEY: 9
2.1 EXISTING SYSTEM 9
2.2 PROPOSED SYSTEM: 9
2.3 FEASIBILITY STUDY 9
2.4 FUNCTIONAL REQUIREMENT 10
2.5 NON FUNCTIONAL 10
REQUIREMENT
3 DIAGRAM 13
3.1 FLOW CHART 13
3.2 USE CASE DIAGRAM 14
3.3CLASS DIAGRAM 15
3.4 SEQUENCE DIAGRAM 16
3.5 STATE CHART DIAGRAM 17
3.6 DATA FLOW DIAGRAM 18
3.7 E-R DIAGRAM 20
4 INTERFACE 25
5 CONCLUSION 29
6 REFERENCES 30

5
Abstract

This system facilitates mailing among users of an Intranet. Now-a-days

Organizations are growing fast and are increasing in size also. So these
Organizations are divided into departments. In the fast growing world
the information is needed as fast as possible. This can be accomplished
by passing the information quickly. Quick passing of mails is not
possible in Manual systems. This is because the information is passed
through persons of one department to another department. This leads to
the inconsistency and delay in delivering information. So we need a
system which is both quick and accurate. This can be achieved by
developing a web-based & Intranet Mailing System.

6
INTRODUCTION
Mailing services give free web based electronic mail. Mailing Services
enables you to acquire new customers and to increase growth
opportunities with existing customers. With a wide range of Direct Mail
Lists Services, label mailing or mail merge services, we enable you to
communicate with customers in a better way.
-Easier way to send and receive mails.
-Messages displayed in a sorted way.
-Address Book, which is used to save recipient address.

1.1 Project Definition ITER Mail System

This project aims at developing a web based mail client that server
the user to send and receive mail through send mail as (MTA) message
transport and IAMP as the message delivery agent. The existing users
are needed to authenticate their identity and then they permitted to check
their mail in their mailbox. Also they can send mail. Organize mail
across the folder and can delete the necessary mail from mailbox. A
good user interface has been provided for performing all these tasks
easily.

1.2 Project Users

I. ADMIN: - Admin manages the Site and Upgrade and View the
Registered User
II.USER: - User uses the whole facility of Internal Mailing System.

1.3 Project Overview

To prepare new mailing system on PHP which provide all the
services provide by any general mailing services with some extra
features such as easy to operate, free messaging services are objective to

7
make this project at very huge level but we just learn how to make
mailing service system we are able in future to work over this project
easily and provide much better facilities. So here we are showing you
dummy project on mailing services prepared with help of PHP and some
other designing tools. Our vision for this project and training is to build
and maintains a customer-oriented culture. The customer satisfaction is
what we aspire for. Hence we are to provide a mailing service that is
easy and comfortable to control and function with certain additional
facilities.

1.4 Project Requirements (Software and Hardware specification)

 Hardware specification: - Processor:-Intel p4 dual or higher –Ram:-1
GB - Hard drive:-80 GB - Operating system: window10 pro
 Software specification: - Front-end :( dream viewer) - Tools used: -
sublime text - Technology: - PHP, HTML, - Back-end: - MY SQL. -
Web-server:-XAMPP–
Web browser: - Google chrome, Mozilla Firefox, internet
explorer.

1.5 OBJECTIVE:-
To prepare new mailing system on PHP which provide all the services
provide by any general mailing services with some extra features such as
easy to operate, free messaging services are objective to make this
project at very huge level but we just learn how to make mailing service
system we are able in future to work over this project easily and provide
much better facilities. So here we are showing you dummy project on
mailing services prepared with help of PHP and some other designing
tools.

8
2. LITERATURE SURVEY:
2.1EXISTING SYSTEM:
Present System is manually providing services to employees of
departments of an Organization. Employees have to go departments to
know some particular information. Sometimes information is passed by
manually between departments. This manual system will take time to
pass the information and sometimes it causes loss of information also.
There by causing loss of employee time also. Thus the present system
stated is time taking, insecure and costly.

2.2 PROPOSED SYSTEM:

As organization grows in size in terms of departments and
functionalities, it requires a quick and efficient system to achieve instant
communication between employees of same department or b/w
departments. The proposed system “Mail Server” serves organization’s
needs in a consistent and transparent manner. It should cater the needs of
information sharing. It allows the users to exchange their views thru
mails and send electronic files through attachments. It should have all
traditional things such as sent items, inbox, drafts etc. The users are
allows to send mails to multiple users using to, cc and bcc too. Thus the
system fulfills spontaneous needs of the organization.

2.3 FEASIBILITY STUDY:

Feasibility study is a system proposal according to its workability,

impact on the organization, ability to meet user’s needs and efficient use
of resources. Feasibility is the determination of whether or not a project
is worth doing. The proposed system must be evaluated from the
technical point of view first and if this technically impact on the
organization must be accessed. Generally feasibility studies are

9
undertaken within right time constraints. It should be conducted
completely and no fundamental errors of judgments are made. If
compatible social and technical systems can be devised then the system
must be tested for economic feasibility. Thus the tool is accessed for,
Technical feasibility, Behavioral, feasibility, Economical feasibility,
Operational feasibility.

2.4 FUNCTIONAL REQUIREMENT:

• A client side validation must be done to receive valid email-ids,
phone number and other relevant information at the time of
registration.
• Server must check for correct email-id and password pairs at the
time of login.
• Registered users must be able to send and receive mails between
each other.
• Users must be able to change the password.
• Users must be able to change profile image.
• Users must be able to log out from the mail server.

2.5 NON- FUNCTIONAL REQUIREMENT:

All IT systems at some point in their lifecycle need to consider non-
functional requirements and testing. For some projects these
requirements warrant extensive work and for other project domains a
quick check through may be sufficient. As a minimum, the following list
can be a helpful reminder to ensure you have covered the basics. Based
on your own project characteristics, I would recommend the topics are
converted into SMART (Specific, Measurable, Attainable, Realizable,

10
Time boxed /Traceable) requirements with the detail and rigor
appropriate to your project.
The list is also available at the bottom of the article as a one-page PDF
document. While it is easy to make the list longer by adding more items,
I would really like to hear how to make the list better while keeping it on
one page (and readable) to share with other visitors here.

SECURITY:
• Login requirements - access levels, CRUD levels
• Password requirements - length, special characters, expiry, recycling
policies
• Inactivity timeouts – durations, actions
PERFORMANCE:
• Response times - application loading, screen open and refresh times, etc
• Processing times – functions, calculations, imports, exports
• Query and Reporting times – initial loads and subsequent loads
CAPACITY:
• Throughput – how many transactions per hour does the system need to be able to
handle
• Storage – how much data does the system need to be able to store?
• Year-on-year growth requirements
AVAILABILITY:
• Hours of operation – when is it available? Consider weekends, holidays,
maintenance times, etc.
• Locations of operation – where should it be available from, what are the
connection requirements?
RELIABILITY:
• Mean Time Between Failures – What is the acceptable threshold for down-time?
E.g. one a year, 4,000 hours
• Mean Time To Recovery – if broken, how much time is available to get the
system back up again?

11
INTEGRITY:
• Fault trapping (I/O) – how to handle electronic interface failures, etc
• Bad data trapping - data imports, flag-and-continue or stop the import
policies, etc
• Data integrity – referential integrity in database tables and interfaces
• Image compression and decompression standards

12
3. DIAGRAM:
3.1 FLOW CHART

Login

No
If correct
credentials?

Yes

User home

When logout is selected

Logout

13
3.2 USE CASE DIAGRAM

Admin Use case:-

14
User Use-Case:-

15
3.4 SEQUENCE DIAGRAM

16
3.5 STATE CHART DIAGRAM:

17
3.6 DATA FLOW DIAGRAM
CONTEXT LEVEL DIAGRAM (LEVEL 0):-

DFD LEVEL 1:-

18
DFD Level 2:-

19
3.7 E-R Diagram
Tables
1. Registration

name
nationality
lastname

address

registration state
country

phoneno.
state
city

20
 2. Login

password squestion
userid

login

theme

answer

3 Drafts userid
message senderid

subject drafts
fcontent

fsize
fname
ftype
21
4.Outbox

senderid subject
userid

message outbox fname

fsize
ftype fcontent

5 .Themes tname

tname

22
6. Trash

userid senderid
subject

ftype trash message

fname
fcontent
fsize

23
 subject
senderid
7. Compose mail
userid

Compose mail fcontent

message

fname fsize

ftype

24
4: INTERFACE
i) Index page:
This is the main page of the website from which a user can go
for different functionalities.

25
Registration Page:-
Through this page the user can register himself/herself by proving all
necessary data.

Login page:-
Through this page a registered user can login into the website by
providing the valid email and password

26
Home page:-
Through this page the registered user can choose the options
shown below to manage the mails.

27
Change password page:-
A user can use this page to change the existing password.

Compose mail page:-

Through this page the user can sent emails to any other registered user.

28
 5. CONCLUSION

The proposed intranet Mail Server software developed using HTML,

CSS for front end deign and PHP is used in backend for data fetching
from file which turned out to be attractive, flexible and easy to use when
it comes to sending and receiving electronic mails. It is user friendly and
genuinely feasible.

The advantages and features aside, many new things can be added into
this project to make it a better one. These include incorporating
completely new features or modules as per user requirement. Adding,
updating and deleting folders can be a good idea. Also, an E-group can
be formed within the mail server system.

29
 6. REFERENCES
 https://www.w3schools.com
 https://www.tutorialspoint.com
 https://www.youtube.com
 https://www.gmail.com for Layout reference.

30