Chapter 1

OBJECTIVE OF THE PROJECT

1.1 Abstract

2

This Mailing system is designed to provide a communication channel inside an

organization between different clients (Organization staff) on the network. The main

objective of the project is to develop a fully functional Mailing System that enhances

communications among the members of the organization in a reliable, cost-effective and

secure way. Thus it helps the organization to improve the performance of its teams in

the corporate sector. This system design shall be able to provide the following facilities

to the users:

1. System shall accept the mails from authorized users providing security. Submitted

messages will be delivered to appropriate person only. It provides the facility to review

messages from the respective folders. Effective Communication has become an integral

part of organizations today. The rapid development of mailing system (intranets) may

provide construction and design teams with an innovative tool for meeting these

growing communication challenges. 

2. A project specific mailing system uses a database server to store mails information

and the organizational information such as user’s details including the personal

information and information requests. Teams members can be then access this

information using the Mailing System. As information changes, the server content can

be easily updated with new or revised data. This flexible approach allows

geographically remote project teams to access timely, consistent and accurate

information without expensive typesetting, printing, distribution and mailing charges.

1.2 Objective

Secure Mailing: - The objective of this project is to describe the basic features of e-

mailing system and identify the E-mails which consist of offensive, anti-social elements

through some special keywords i.e. managed by administrator and block them.

Detection of suspicious user: - It helps in identifying the suspicious user who sends

suspicious mail that contains harmful data like spam, virus or executable file.

Security: -It provides security to the organisation that adapts it. Members of the

organisation can securely communicate with each other and can send secure data (that

should not share to the outside world) to the other members of the organisation.

User friendly: -It provides user friendly environment. Members of organisation can

easily use it without knowing background details of it.3

Maintains redundancy: -It maintains redundancy in the database and provides a unique

user id to the user.

Cost Effective: -It is cost effective because organisation do not have to pay for

interacting the employees. And user can mail any number of mails.

4

Chapter 2

INTRODUCTION

5

Electronic mail (also known as email or e-mail) is one of the most commonly used services

on the Internet, allowing people to send messages to one or more recipients. Email was

invented by Ray Tomlinson in 1972. Many people are now using various email services to

communicate with each other. But some emails have harmful content in it that can affect our

PC, Laptop,…etc. In this project, suspicious users who send harmful emails are identified by

determining the keywords used by him/her. The keywords such as bomb, RDX, are found in

the mails which are sent by the user. All these blocked mails are checked by the administrator

and identify the users who sent such mails. This is very useful in real-time scenario in which

you can resume the anti-social activities.

2.1 OVERVIEW OF PROJECT

1) Login Module

2) Registration Module

3) Administration Module

4) Managing harmful keywords Module

5) User Module

6) Composing Mail Module

2.1.1 Login Module

This module is used by administrator and users (who are authenticated) to login into the Java

Secure Mail. The login details of the specified person will be entered and hence can enter into

the Java Secure Mail. If a user is not authenticated then it notifies login details are not

correct.

2.1.2 Registration Module

This module is used by the unauthenticated users who are unregistered. The users must

register themselves by unique username such that they can login into the Java Secure Mail. If

6

a user of same username is already exists then it notifies user already exists. If password and

confirm password is not matched then it notifies password is not matched.

2.1.3 Administration Module

This module is used by the administrator to perform the functions like managing the

keywords, entering new keywords and to check out the block list of the discarded mails.

2.1.4 Managing harmful keywords Module

This module is used by the administrator to perform the functions like addition, deletion and

modification of the harmful keywords. The harmful keywords are sent to the database and

hence managed by the administrator. If keyword already exists then it tells to the

administrator.

2.1.5 User Module

This module is used by the users to do operations like composing mail, checking out the

mails in inbox and finally sending the mails to the authenticated users by attaching a message

or file.

2.1.6 Composing Mail Module

This module is used by the users for composing mail. In this module, user specifies header

and body of the file and attaches a file. Header contains address of the recipient and subject

of mail. Body contains actual description of mail. We can attach any type of file in it. If a file

is .exe file then it will considers as harmful file. It notifies to the user that mail has sent or

not.

2.2 History

Email is much older than Arpanet or the Internet. It was never invented; it evolved from very

simple beginnings. Early email was just a small advance on what we know these days as a

file directory - it just put a message in another user's directory in a spot where they could see

it when they logged in. Simple as that. Just like leaving a note on someone's desk. Probably

the first email system of this type was MAILBOX, used at Massachusetts Institute of

7

Technology from 1965. Another early program to send messages on the same computer was

called SNDMSG. Ray Tomlinson is credited with inventing email in 1972. Like many of the

Internet inventors, Tomlinson worked for Bolt Beranek and Newman as an ARPANET

contractor. He picked the @ symbol from the computer keyboard to denote sending messages

from one computer to another. So then, for anyone using Internet standards, it was simply a

matter of nominating name-of-the-user@name-of-the-computer. Internet pioneer Jon Postel,

who we will hear more of later, was one of the first users of the new system, and is credited

with describing it as a "nice hack". It certainly was, and it has lasted to this day. 

By 1974 there were hundreds of military users of email because ARPANET eventually

encouraged it. Email became the savior of Arpanet, and caused a radical shift in Arpa's

purpose. Things developed rapidly from there. Larry Roberts invented some email folders for

his boss so he could sort his mail, a big advance. In 1975 John Vital developed some software

to organize email. By 1976 email had really taken off, and commercial packages began to

appear. Within a couple of years, 75% of all ARPANET traffic was email.

Email took us from Arpanet to the Internet. Here was something that ordinary people all over

the world wanted to use.

One of the first new developments when personal computers came on the scene was "offline

readers". Offline readers allowed email users to store their email on their own personal

computers, and then read it and prepare replies without actually being connected to the

network - sort of like Microsoft Outlook can do today. The first important email standard was

called SMTP, or simple message transfer protocol. SMTP was very simple and is still in use -

however, as we will hear later in this series, SMTP was a fairly naïve protocol, and made no

attempt to find out whether the person claiming to send a message was the person they

purported to be. Forgery was (and still is) very easy in email addresses. These basic flaws in

the protocol were later to be exploited by viruses and worms, and by security frauds and

spammers forging identities. Some of these problems are still being addressed in 2004. But as

it developed email started to take on some pretty neat features. One of the first good

commercial systems was Eudora, developed by Steve Dorner in 1988. Not long after Pegasus

mail appeared. 

When Internet standards for email began to mature the POP (or Post Office Protocol) servers

began to appear as a standard - before that each server was a little different. POP was an

8

important standard to allow users to develop mail systems that would work with each other.

These were the days of per-minute charges for email for individual dialup users. For most

people on the Internet in those days email and email discussion groups were the main uses.

These were many hundreds of these on a wide variety of topics, and as a body of newsgroups

they became known as USENET.

2.3 Global use 

Despite what the World Wide Web offers, email remains the most important application of

the Internet and the most widely used facility it has. Now more than 600 million people

internationally use email. With the World Wide Web, email started to be made available with

friendly web interfaces by providers such as Yahoo and Hotmail. Usually this was without

charge. Now that email was affordable, everyone wanted at least one email address, and the

medium was adopted by not just millions, but hundreds of millions of people. Email remains

the No. 1 form of communication in North America and Europe, cited by 87% and 74%

respectively of those polled its use as a main communications channel in the Asia-Pacific

region is at just 58%, according to Epsilon’s “Global Consumer Email Study.”

9

10

Chapter 3

Problem Statement

A great deal of business communication and workflow is centered on email, but we question

whether email is the ultimate long term solution for communication and workflow processes.

While email is a good method for anyone in the world to contact

you, that's also email's biggest problem. Most communication, both business and personal,

does not come from just anyone; it comes from other members of your organization, partners,

or team. It comes from "important people".

Email as a business communication mechanism has many inherent flaws:

It's totally insecure

Confidential business documents sent over email are not confidential. These documents

can be read both inside and outside of your organization. For example, your system

administrator can read the latest draft of your strategic acquisition agreement or medical

patient information.

It's too open

our mailboxes are filling with junk mail, and the situation is getting worse every month.

Due to the inherent general delivery design of email, this problem cannot be prevented,

even with the best designed email filters.

Email can be dangerous

Computer viruses are most commonly delivered through email because there is no

certification mechanism for email senders. In Microsoft Outlook, just clicking on an

email can initiate a new virus.

11

Delivery is not guaranteed

Just like postal mail, email may be delivered, or maybe not. Take the recent example of

Harvard acceptance letters that were deleted by AOL, thinking they were junk mail.

Email is not real time

There is too much delay to have an active conversation, which is why more and more

people are turning to instant messaging solutions (which also have their own security

problems).

It lacks ubiquitous access

it is problematic for most users to access their email from all locations, such as at home

or while on the road. This is the primary reason why web-based email became popular.

If you consider email for managing workflow, it has a number of additional problems:

It's a poor way to share files

they don't arrive in nicely organized directories that allow both parties see identical file

and directory structures.

There's no application framework

Email is for message-oriented content. It has no concept of a standard framework to

deliver active applications.

Its platform dependent

many organizations have members (such as development or graphics groups) who use

systems other than Microsoft Windows and Outlook, which means they are left out of

certain activities.

It's a haphazard workflow method

is email really the best possible driver of corporate and organizational workflow?

Email is adequate for communicating with the world-at-large, a general delivery mailbox, but

most business and organizational communications is oriented toward relatively small teams

of working relationships. Using email to drive internal business workflow is like running a

business based on receiving US postal mail as it arrives at the mailbox.

12

13

Chapter 4

SYSTEM STUDY

4.1 Information Gathering

The system being developed is economic with respect to Organization's point of view. It is

cost effective in the sense that has eliminated the paper posting work completely. The system

is also time effective because the mailing system is very fast which sends Email quickly as

per the user or organization requirement. The Emailing through JSM (Java Secure Mail) is

secure, flexible and pretend to virus, spam or hacking attack by outside world. The system

also collects the information of employee of organization who registered on it.

4.2 Feasibility AnalysisMany feasibility studies are disillusioning for both users and analysts. First, the study often

presupposes that when the feasibility document is being prepared, the analyst is in a position

to evaluate solutions. Second, most studies tend to overlook the confusion inherent in system

development the constraints and the assumed attitudes. If the feasibility study is to serve as a

decision document, it must answer three key questions:-

1. Is there a new and better way to do the job that will benefit the user?

2. What are the costs and savings of the alternative(s)?

3. What is recommended?

Once the feasibility study is done and proposal is approved, we move to the requirement

analysis. A feasibility study is the test to proposal according to its viability impact on the

14

organization, ability to meet user needs, and effective use of the resources. The objective of

the feasibility is not to solve the problem but to acquire a sense of its viability scope.

There are three key consideration involve in the feasibility analysis. Once it has been

determined that a project is feasible, we can go ahead and prepare the project specification

which finalizes project requirements.

Generally, feasibility studies are undertaken within tight time constraints and normally

culminate in a written and oral feasibility report. The contents and recommendations of such

a study will be used as a sound basis for deciding whether to prove, postpone or cancel the

project. Thus, since the feasibility study may lead to the commitment of large resources, it

becomes necessary that it should be conducted competently and that no fundamental errors of

judgment are made. The most successful system projects are not necessarily the biggest or

most visible business but rather those that truly meet user expectations. More projects fail

because of inflated expectations than for any other reason.

4.3 Feasibility considerationsThree key considerations are involved in the feasibility analysis:-

1. Economic

2. Technical

3. Behavioural.

Let's briefly review each consideration and how it relates to the system efforts.

Depending on the results of the initial investigations, the survey is expanded to a more

detailed feasibility study. A feasibility study is a test of a system proposal according to its

workability, impact on the organization, ability to meet user needs, and effective use of

resources.

It focuses on three major questions:

1. What are the user's demonstrable needs and how does a candidate system meet them?

2. What resources are available for given candidate systems? Is the problem worth solving?

3. What are the likely impacts of the candidate system on the organization? How well does it

fit within the organization's master MIS plan?

15

Each of these questions must be answered carefully. They revolve around investigation and

evaluation of the problem, identification and description of candidate systems, specification

of performance and the cost of each system, and final selection of the best system. The

objective of a feasibility study is not to solve the problem but to acquire a sense of its scope.

During the study, the problem definition is crystallized and aspects of the problem to be

included in the system are determined.

Consequently, costs and benefits are estimated with greater accuracy at this stage.

The result of the feasibility study is a formal proposal. This is simply a report-a formal

document detailing the nature and scope of the proposed solution. The proposal summarizes

what is known and what is going to be done.

It consists of the following:

1. Statement of the problem - a carefully worded statement of the problem that led to

analysis.

2. Summary of findings and recommendations- a list of the major findings and

recommendations of the study. It is ideal for the user who requires quick access to the results

of the analysis of the system under study. Conclusions are stated, followed by a list of the

recommendations and a justification for them.

3. Details of findings - an outline of the methods and procedures under taken by the existing

system, followed by coverage of the objectives and procedures of the candidate system.

Included are also discussions of output reports, file structures, and costs and benefits of the

candidate system.

4. Recommendations and conclusions - specific recommendations regarding the candidate

system, including personnel assignments, costs, project schedules and target dates.

After the proposal is reviewed by management, it becomes a formal agreement that paves the

way for actual design and implementation. This is a crucial decision point in the life cycle.

Many projects die here, whereas the more promising ones continue through implementation.

Changes in the proposal are made in writing, depending on the complexity, size and cost of

16

the project. It is simply common sense to verify changes before committing the project to

design.

4.4 Steps in feasibility analysis

Eight steps are involved in the feasibility analysis. They are:

1. Form a project team and appoint a project leader.

2. Prepare system flowcharts.

3. Enumerate potential proposed systems.

4. Define and identify characteristics of proposed system.

5. Determine and evaluate performance and cost effectiveness of each proposed system.

6. Weight system performance and cost data.

7. Select the best proposed system.

8. Prepare and report final project directive to management

4.5 Types of Feasibilities

4.5.1 Economic FeasibilityEconomic analysis is the most frequently used technique for evaluating the effectiveness of a

proposed system. More commonly known as cost / benefit analysis; in this procedure we

determine the benefits and savings that are expected from a proposed system and compare

them with costs. We found the benefits outweigh the costs; we take a decision to design and

implement the new proposed system.

A system that can be developed technically and that will be used if installed must still be

profitable for the organization. The various financial and economic issues were raised during

the preliminary investigation. These issues were not of our concern in major and were studied

by the management. Since the system was developed for internal use of the organization. It

was ensured that after this system has been developed, it would save considerable time and

efforts of the concerned department.

The economic feasibility should demonstrate the net benefit of the proposed application in

light of the benefits and costs to the client. The large department have large amount of data,

17

information. Economic feasibility is send to different clients for approval and

acknowledgement before moving to next stage of system development process.

The following Economic Feasibility elements are expressed quantitatively in the analytical

worksheets and summarized in the business case.

The elements included

a. Increased agency revenue.

b. Decreased agency revenue.

c. Increased agency cost.

d. Decreased agency cost.

e. Other organizational benefits.

There isn’t an order or magnitude rule of thumb that applies generally.

The alternative dismissal/selection process depends on other things, such as, how well an

alternative meets the project purpose and need, and the totality of environmental impacts.

What if an alternative that cost 4 or 5 times more than other alternatives but in turn had 4 to 5

times less environmental impacts? Depending on the type of resources and impacts, you

might not be able to rule that alternative out on the basis of dollar cost alone.

Conversely, an alternative that was much cheaper than others but with unacceptable impacts

might be considered unacceptable depending on the resources, impacts and others values the

alternative brings with it.

The feasibility study is one of the most misunderstood aspects of developing a location-based

leisure facility. Yet, it is perhaps the most important step, as mistakes at this early stage can

permanently handicap the project’s performance, perhaps fatally. A good feasibility study is

more than just a set of financial projections. Done properly, it becomes the market-driven

strategic plan that is the road map for all subsequent decisions. As much as answering the

question “Is a project feasible?” a good study also addresses the question of what is most

feasible and what should all its attributes be to assure maximum success.

18

4.5.2 Technical Feasibility

This is concerned with specifying equipment and software that will successfully satisfy the

user requirement. The technical needs of the system may vary considerably, but might

include:

The facility to produce outputs in a given time.

Response time under certain conditions.

Ability to process a certain volume of transaction at a particular speed.

Facility to communicate data to distant location.

This project is technically feasible as it has got all the features necessary to form a healthy

environment for communication. The concepts & technology used in this project is perfectly

well and secure. Any organization’s employee having an account on mailing system can

access this project and make full use of it.

4.5.3 Behavioural Feasibility

It is mainly related to human organizational and political aspects. The points to be considered

are:

What changes will be brought with the system?

What organizational structures are disturbed?

What new skills will be required? Do the existing staff members have these skills?

If not, can they be trained in due course of time?

Generally project will not be rejected simply because of operational infeasibility but such

considerations are likely to critically affect the nature and scope of the eventual

recommendations.

The system working is quite easy to use and learn due to its simple but attractive interface.

User requires no special training for operating the system. They can easily work and operate

this system.

19

4.5.4 Social Feasibility

Social feasibility is a determination of whether a proposed project will be acceptable to the

people or not. This determination typically examines the probability of the project being

accepted by the group directly affected by the proposed system change. This system can

easily be adopted by the social organization because it recognises the suspicious user and

mails.

4.5.5 Management Feasibility

It is a determination of whether a proposed project will be acceptable to management. If

management does not accept a project or gives a negligible support to it, the analyst will tend

to view the project as a non-feasible one.

4.5.6 Legal Feasibility

Legal feasibility is a determination of whether a proposed project infringes on known Acts,

Statutes, as well as any pending legislation. Although in some instances the project might

appear sound, on closer investigation.

4.6 Technology Used

4.6.1 Java

Initially the language was called as “oak” but it was renamed as “java” in 1995.The primary

motivation of this language was the need for a platform-independent (i.e. architecture neutral)

language that could be used to create software to be embedded in various consumer electronic

devices.

Java is a programmer’s language

Java is cohesive and consistent

Except for those constraint imposed by the Internet environment. Java gives the

programmer, full control20

Finally Java is to Internet Programming where c was to System Programming.

4.6.1.1 Importance of java to the internet

Java has had a profound effect on the Internet. This is because; java expands the Universe of

objects that can move about freely in Cyberspace. In a network, two categories of objects are

transmitted between the server and the personal computer. They are passive information and

Dynamic active programs. in the areas of Security and probability. But Java addresses these

concerns and by doing so, has opened the door to an exciting new form of program called the

Applet.

4.6.1.2 Java architecture

Java architecture provides a portable, robust, high performing environment for development.

Java provides portability by compiling the byte codes for the Java Virtual Machine, which is

then interpreted on each platform by the run-time environment. Java is a dynamic system,

able to load code when needed from a machine in the same room or across the planet.

4.6.1.3 Compilation of code

When you compile the code, the Java compiler creates machine code (called byte code) for a

hypothetical machine called Java Virtual Machine (JVM). The JVM is supposed executed the

byte code. The JVM is created for the overcoming the issue of probability. The code is

written and compiled for one machine and interpreted on all machines .This machine is called

Java Virtual Machine.

4.6.1.4 COMPILING AND INTERPRETING JAVA SOURCE CODE

21

Fig. 4.1 Compiling and Interpreting Java Source Code

During run-time the Java interpreter tricks the byte code file into thinking that it is running on

a Java Virtual Machine. In reality this could be an Intel Pentium windows 95 or sun

SPARCstation running Solaris or Apple Macintosh running system and all could receive code

from any computer through internet and run the Applets.

4.6.1.5 Features of Java

I. Simple

Java was designed to be easy for the Professional programmer to learn and to use effectively.

If you are an experienced C++ Programmer, Learning Java will oriented features of C++.

Most of the confusing concepts from C++ are either left out of Java or implemented in a

cleaner, more approachable manner. In Java there are a small number of clearly defined ways

to accomplish a given task.

II. Object Oriented

Java was not designed to be source-code compatible with any other language. This allowed

the Java team the freedom to design with a blank state. One outcome of this was a clean

usable, pragmatic approach to objects. The object model in Java is simple and easy to extend,

while simple types, such as integers, are kept as high-performance non-objects.

III. Robust

The multi-platform environment of the web places extraordinary demands on a program,

because the program must execute reliably in a variety of systems. The ability to create robust 22

Source code

Pc compiler

Macintosh compiler

SPARC Compiler

Java Byte code

Platform independ

ent

Java interpreter

Java interpreterm

acintosh

)))

Java interpreter(

SPARC)

programs was given a high priority in the design of Java. Java is strictly typed language; it

checks your code at compile time and runtime.

Java virtually eliminates the problems of memory management and deal location, which is

completely automatic. In a well-written Java program, all run-time errors can and should be

managed by your program.

4.6.2 JSP

The first Java Server Pages specification was released in 1999. Originally JSP was modelled

after other server-side template technologies to provide a simple method of embedding

dynamic code with static mark-up. When a request is made for the content of a JSP, a

container interprets the JSP, executes any embedded code, and sends the results in a response.

At the time this type of functionality was nothing terribly new, but it was and still is a helpful

enhancement to Servlets.

JSP has been revised several times since the original release, each added functionality, and is

currently in version 2.0. The JSP specifications are developed alongside the Servlet

specifications and can be found on Sun Microsystems’

Java Server Pages product information page,http://java.sun.com/products/jsp. The

functionality defined by the JSP 2.0 specifications can be broken down as follows:

JSP

The JSP specifications define the basic syntax and semantics of a Java Server Page. A basic

Java Server Page consists of plain text and markup and can optionally take advantage of

embedded scripts and other functionality for creating dynamic content.

JavaBeans

JavaBeans are not defined by the JSP specifications, but JSP does provide support for easily

using and manipulating them. Often objects used on the server-side of a Web Application are

in the form of what is commonly called a JavaBean.

Custom Tags and JSP Fragments

JSP provides a mechanism for linking what would normally be static markup to custom Java

code. This mechanism is arguably one of the strong points of JSP and can be used in place of

or to complement embedded scripts of Java code.

Expression Language23

JSP includes a mechanism for defining dynamic attributes for custom tags. Any scripting

language can be used for this purpose; usually Java is implemented, but the JSP specification

defines a custom expression language designed specifically for the task. Often the JSP EL is

a much simpler and more flexible solution, especially when combined with JSP design

patterns that do not use embedded scripts.

Discussing the basics of JSP is the focus of this chapter. JavaBeans, Custom Tags, and the

JSP Expression Language are all fully discussed in later chapters after a proper foundation of

JSP is established.

4.6.2.1 JSP LIFE CYCLE

Much like Servlets, understanding JSP requires understanding the simple life cycle that JSP

follows. JSP follows a three-phase life cycle: initialization, service, and destruction, as shown

in Figure 3-1. This life cycle should seem familiar and is identical to the one described for

Servlets.

While a JSP does follow the Servlet life cycle, the methods have different names.

Initialization corresponds to the jspInit() method, service corresponds to the _jspService()

method, and destruction corresponds to the jspDestroy() method. The three phases are all

used the same as a Servlet and allow a JSP to load resources, provide service to multiple

client requests, and destroy loaded resources when the JSP is taken out of service.

JSP is designed specifically to simplify

the task of creating text producing HttpServlet

objects and does so by eliminating all the redundant parts of coding a Servlet. Unlike with

Servlets there is no distinction between a normal JSP and one meant for use with HTTP. All

JSP are designed to be used with HTTP and to generate dynamic content for the World Wide

Web. The single JSP _jspService () method is also responsible for generating responses to all

seven of the HTTP methods. For most practical purposes a JSP developer does not need to

know anything about HTTP, nor anything more than basic Java to code a dynamic JSP.

24

4.6.3 JDBC4.6.3.1 What is JDBC?

One can write a single program using the JDBC API, and the JDBC is a Java API for

executing SQL, Statements(As a point of interest JDBC is trademarked name and is not an

acronym; nevertheless, JDBC is often thought of as standing for Java Database Connectivity.

It consists of a set of classes and interfaces written in the Java Programming language. JDBC

provides a standard API for tool/database developers and makes it possible to write database

applications using a pure Java API.

Using JDBC, it is easy to send SQL statements to virtually program will be able to send

SQL .statements to the appropriate database. The Combination of Java and JDBC lets a

programmer writes it once and run it anywhere.

4.6.3.2 What does JDBC do?

Simply put, JDBC makes it possible to do three things

Establish a connection with a database

Send SQL statements

Process the results

JDBC Driver Types

The JDBC drivers that we are aware of this time fit into one of four categories

JDBC-ODBC Bridge plus ODBC driver

Native-API party-java driver

JDBC-Net pure java driver

Native-protocol pure Java driver

An individual database system is accessed via a specific JDBC driver that implements the

java.sql.Driver interface. Drivers exist for nearly all-popular RDBMS systems, through few

are available for free. Sun bundles a free JDBC-ODBC bridge driver with the JDK to allow

access to a standard ODBC, data sources, such as a Microsoft Access database, Sun advises

against using the bridge driver for anything other than development and very limited

development.

JDBC drivers are available for most database platforms, from a number of vendors and in a

number of different flavours. There are four driver categories:

I. Type 1-JDBC-ODBC Bridge driver

II. Type 2-Native-API Party Java driver

25

III. Type 3-Net Protocol All Java Driver

IV. Type 4 Native Protocol All Java Driver

IV.6.4 MySQL (Structured Query Language)MySQL is a Relational Database Management System (RDBMS) that runs as a server

providing multi-user access to a number of databases .It is a cross platform database server

ideal for both small and large applications. It supports standard SQL for database creation.

The data in MySQL is stored in database objects called tables. The table is a collection of

related data entries and it consists of columns and rows. The system provided a simple

interface for quick book searching, lending and returning. The interface was designed to be

mainly used for the common browsers, making the system migration and usage easier.

IV.6.4.1 Database

A Database is a collection of interrelated data stored with a minimum of redundancy to serve

many applications. The database design is used to group data into a number of tables and

minimizes the artificiality embedded in using separate files. The tables are organized to:

Reduced duplication of data.

Simplify functions like adding, deleting, modifying data etc..,

Retrieving data

Clarity and ease of use

More information at low cost

4.6.4.2 Normalization

Normalization is built around the concept of normal forms. A relation is said to be in a

particular normal form if it satisfies a certain specified set of constraints on the kind of

functional dependencies that could be associated with the relation. The normal forms are used

to ensure that various types of anomalies and inconsistencies are not introduced into the

database.

First Normal Form

A relation R is in first normal form if and only if all underlying domains contained atomic

values only.

Second Normal Form

A relation R is said to be in second normal form if and only if it is in first normal form and

every non-key attribute is fully dependent on the primary key.

Third Normal Form

26

A relation R is transitively depends on the primary key. said to be in third normal form if and

only if it is in second normal form and every non key attribute is non-transitively depend on

the primary key.

IV.6.5 HTMLHypertext Mark-up Language (HTML), the languages of the worldwide web (WWW), allows

users to produces web pages that included text, graphics and pointer to other web pages

(Hyperlinks).

HTML is not a programming language but it is an application of ISO Standard 8879, SGML

(Standard Generalized Mark-up Language), but Specialized to hypertext and adapted to the

Web. The idea behind hypertext is one point to another point. We can navigate through the

information based on out interest and preference. A mark-up language is simply a series of

items enclosed within the elements should be displayed.

Hyperlinks are underlined or emphasized works that load to other documents or some

portions of the same document.

HTML can be used to display any type of document on the host computer, which can be

geographically at a different location. It is a versatile language and can be used on any

platform or desktop

HTML provides tags (special codes) to make the document look attractive.

HTML provides are not case-sensitive. Using graphics, fonts, different sizes, color, etc can

enhance the presentation of the document. Anything that is not a tag is part of the document

itself.

4.6.5.1 Advantages

A HTML document is small and hence easy to send over the net.It is small because it

does not include formatted information.

HTML is platform independent

HTML tags are not case-sensitive.

4.6.5.2 Basic HTML Tags

<!-- --> Specific Comments.

<HTML>…..</HTML> Start tag

<Title>……..</Title> Creates title of the page

<A>………..</A> Creates Hypertext links.

27

<B>………...</B> Creates hypertext links.

<Big>………</Big> Formats text in large-font

<Body>…….</Body> Contains all tags and text in the Html-document

<Center>……</Center> Creates Text

<DD>……….</DD> Definition of a term.

<TABLE>…..</TABLE> Creates table

<Td>…………</Td> Indicates table data in a table.

<Tr>………..</Tr> Designates a table row

<Th>……….</Th> Creates a heading in a table.

28

29

Chapter 5

SYSTEM ANALYSISAssuming that a new system is to be developed, the next phase is system analysis. Analysis

involved a detailed study of the current system, leading to specifications of a new system.

Analysis is a detailed study of various operations performed by a system and their

relationships within and outside the system. During analysis, data are collected on the

available files, decision points and transactions handled by the present system. Interviews,

on-site observation and questionnaire are the tools used for system analysis. Using the

following steps it becomes easy to draw the exact boundary of the new system under

consideration:

Keeping in view the problems and new requirements

Workout the pros and cons including new areas of the system

All procedures, requirements must be analysed and documented in the form of detailed data

flow diagrams (DFDs), data dictionary, logical data structures and miniature specifications.

System Analysis also includes sub-dividing of complex process involving the entire system,

identification of data store and manual processes.

The main points to be discussed in system analysis are:

Specification of what the new system is to accomplish based on the user requirements.

Functional hierarchy shows the functions to be performed by the new system and their

relationship with each other.

Function network which are similar to function hierarchy but they highlight those

functions which are common to more than one procedure.

List of attributes of the entities - these are the data items which need to be held about

each entity (record).

The selection process should be viewed as a project and a project team should be formed with

the help of management. The selection process consists of several steps, which are discussed

below:

30

5.1 Requirements analysis

The first step in selection understands the user's requirements within the framework of the

organization’s objectives and the environment in which the system is being installed.

5.2 System specifications:

System specifications must be clearly defined. These specifications must reflect the actual

applications to be handled by the system and include system objectives, flowcharts, input-

output requirements, file structure and cost.

5.3 Request for proposal:

After the requirement analysis and system specifications have been defined, a request for

proposal is prepared and sent to selected vendors for bidding.

5.4 Evaluation and validation:

The evaluation phase ranks various vendor proposals and determines the one best suited to

the user's requirements. It looks into items such as price, availability and technical support.

System validation ensures that the vendor can, in fact, match his/her claims, especially

system performance.

5.5 Vendor selection: This step determines the vendor with the best combination of reputation, reliability, service

record, training, delivery time, lease/finance terms. The selected vendors are invited to give a

presentation of their system. The system chosen goes through contract negotiations before

implementation.

31

32

Chapter 6

SYSTEM DESIGNBased on the user requirements and the detailed analysis of a new system, the new system

must be designed. This is the phase of system designing. It is a most crucial phase in the

development of a system. Normally, the design proceeds in two stages:

Preliminary or general design

Structure or detailed design

Preliminary or general design: In the preliminary or general design, the features of the new

system are specified. The costs of implementing these features and the benefits to be derived

are estimated. If the project is still considered to be feasible, we move to the detailed design

stage.

Structure or Detailed design: In the detailed design stage, computer oriented work begins in

earnest. At this stage, the design of the system becomes more structured. Structure design is a

blue print of a computer system solution to a given problem having the same components and

inter-relationship among the same components as the original problem. Input, output and

processing specifications are drawn up in detail. In the design stage, the programming

language and the platform in which the new system will run are also decided.

6.1 THE PRIMARY OBJECTIVE OF THE DESIGN:

Of course, is to deliver the requirements as specified in the feasibility report. In general, the

following design objectives should be kept in mind:

Practicality: The system must be stable and can be operated by the people with average

intellectual.

Efficiency: This involves accuracy, timeliness and comprehensiveness of the system

output.

Cost: it is desirable to aim for a system with a minimum cost subject to the condition that

it must satisfy all the requirements.

33

Flexibility: The system should be modifiable depending on the changing needs of the

user. Such modifications should not entail extensive reconstructing or recreation of

software. It should also be portable to different computer systems.

Security: This is very important aspect of the design and should cover areas of hardware

reliability, fall back procedures, physical security of data and provision for detection of

fraud and abuse. System design involves first logical design and then physical

construction of the system. The logical design describes the structure and characteristics

of features, like the outputs, inputs, files, databases and procedures. The physical

construction, which follows the logical design, produces actual program software, files

and a working system.

The designer normally will work under following constraints:

Hardware: The existing hardware will obviously affect the system design.

Software: The available software (operating system, utilities, language etc.) in the market

will constrain the design.

Budget: The budget allocated for the project will affect the scope and depth of design.

Time-scale: The new system may be required by a particular time (e.g. the start of a

financial year). This may put a constraint on the designer to find the best design.

Interface with other systems: The new system may require some data from another

computerized system or may provide data to another system in which case the files must

be compatible in format and the system must operate with a certain processing cycle.

6.2 Input Output Design For any system to work properly it is very necessary to keep a check over the input and

output of the system. In this system we have used MySQL database for storing and sending

information. So it imposes an additional constraint that the data inputted by the user should

conform to the standards for creating a table in MySQL database. For example there cannot

be 2 users having the same user name in the registration table.

34

6.3 User Interface DesignAny project how so ever good it may be would become failure if the end user it is meant to

cater cannot use it. For the end user to reap full benefits of the project the project should have

a good interface. Interface is the way a project links with the end users; it accepts the inputs

from the user and gives output to the user. For a project to be successful it should have a

clean and understandable interface.

6.3.1 Properties of a good interface

The text written should be clear.

Proper labelling should be done on labels and buttons.

Proper warnings should be provided to the user at all levels.

It should not be too bright in colours.

6.4 System Architecture

Below architecture diagram represents mainly flow of requests from users to database

through servers. In this scenario overall system is designed in three tires separately using

three layers called presentation layer, business logic layer and data link layer. This project

was developed using 3-tier architecture.

35

SERVER

User

Data Base

Request Response

URL Pattern:

Fig. 6.2 URL Pattern of System Architecture

URL pattern represents how the requests are flowing through one layer to another layer and

how the responses are getting by other layers to presentation layer through server in

architecture diagram.

36

Presentation Layer

SERVLETS AT THE SERVER

SIDE

URL Request sent through the browser

Response sent from the servlet

DATABASE

Verifying or updating the

database through a statement

Reply from the database according to

the statement

6.5 UML Diagrams

6.5.1 Unified Modelling Language

The Unified Modelling Language allows the software engineer to express an analysis model

using the modelling notation that is governed by a set of syntactic semantic and pragmatic

rules. A UML system is represented using five different views that describe the system from

distinctly different perspective. Each view is defined by a set of diagram, which is as follows.

6.5.1.1 USER MODEL VIEW

This view represents the system from the user’s perspective.

The analysis representation describes a usage scenario from the end-users perspective.

6.5.1.2 STRUCTURAL MODEL VIEW

In this model the data and functionality are arrived from inside the system.

This model view models the static structures.

6.5.1.3 BEHAVIORAL MODEL VIEW

It represents the dynamic of behavioural as parts of the system, depicting the interactions of

collection between various structural elements described in the user model and structural

model view.

6.5.1.4 IMPLEMENTATION MODEL VIEW

In this the structural and behavioural as parts of the system are represented as they are to be

built.

6.5.1.5 ENVIRONMENTAL MODEL VIEW

In this the structural and behavioural aspects of the environment in which the system is to be

implemented are represented.

UML is specifically constructed through two different domains they are:

UML Analysis modelling, this focuses on the user model and structural model views of

the system.

UML design modelling, which focuses on the behavioural modelling, implementation

modelling and environmental model views.

37

6.6 Class Diagrams

6.6.1 Admin

Fig. 6.3 Class Diagram for Admin

6.6.2 User

Compose Mailscomposing the mail

send the mail()

Sent MailsSent items

check the sent items()

UserMails

Compose()send()

InboxReceived mails

check the received mails()

Fig. 6.4 Class Diagram for User

38

KeywordsManage Keywords

Add Keywords()Display Keywords()

Update Keywords()AdminKeywordsAlert MailsInformative

Enter keywords()check mails()

Block ListAlert MailsInformative Mails

check mails()

6.7 Sequence Diagram

6.7.1 Admin

Admin Keywords Alert List Informative

Manage Keywords

Check Alert Mails

Check Informative Mails

Fig. 6.5 Sequence Diagram for Admin

6.7.2 USER

User Compose Mails Inbox Sent Items

Compose the mails to be sent

Check the mails

Check the sent mails

Fig. 6.6 Sequence Diagram for User

39

6.8 Object Diagram

6.8.1 Admin

Fig. 6.7 Object Diagram for Admin

6.8.2 User

Fig. 6.8 Object Diagram for User

40

41

Chapter 7

Data Flow Diagram

Graphical description of a system's data and how the processes transform the data is known

as Data Flow Diagram (or DFD).

Unlike detail flowcharts, DFD’s do not supply detailed descriptions of modules but

graphically describe a system's data and how the data interact with the system.

The following seven rules govern construction of data flow diagrams (DFD):

1. Arrows should not cross each other.

2. Squares, circles, and files must bear names.

3. Decomposed data flows must be balanced (all data flows on the decomposed

diagram must reflect flows in the original diagram).

4. No two data flows, squares, or circles can have the same name.

5. Draw all data flows around the outside of the diagram.

6. Choose meaningful names for data flows, processes, and data stores. Use strong

verbs followed by nouns.

7. Control information such as record counts, passwords, and validation

requirements are not pertinent to a data-flow diagram.

If too many events seem to be occurring at a given point, an analyst can decompose a data

conversion (circle). The new data conversions form a parent-child relationship with the

original data conversion: the child circle.

42

7.1 Context Level

Check data

Fig 7.1 Context Level DFD

43

User1.0

Email Scanning

AdminCompose

Response

Check Email

Suspicious/Normal

7.2 Level 1 DFD

Fig 7.2 Level 1 DFD

44

Admin

Sender

Receiver

Compose Mail

0.0

Detect harmful keywords

1.0

Database

Detect executable

File

1.1

Compose

Check Email

Check suspicious mail Check

(.exe) file

Alert/Normal Email Alert/Normal

Email

Suspicious/Normal

Response

Fetch Data

Information

45

Chapter 8

Descriptions of different input validations and checksInput is the term meaning either an entrance or changes which are inserted into a system and

which activate or modify a process. Validation is a process where data are subjected to series

of tests to determine the validity of a piece of data. There are a number of validations that is

implemented in this system. They are given below:

8.1 Registration of ClientClient who is un-authenticated can register through user register portal. Client has to enter the

personal information and choose a user name & password. If user name is already registered

by other user then JSM (Java Secure Mail) notifies “user name already exists”. If user name

is not registered then JSM provides this unique user name to new registered client. Client has

to choose a password and confirm password. If password and confirm password is same then

JSM registers client otherwise notifies “password and confirm password is not same”.

8.2 Login client/administratorAuthenticate client/administrator can login and use the system. Client/administrator has to

enter user name and password. If user name and password are correct then JSM depicts

Client/administrator module based on who is entering in the system. If user name or

password is incorrect then JSM notifies “user name or password is not correct”.

8.3 Compose MailThis module is used by client. If a registered user wants to send an Email to another

registered user then user has to compose a mail. In compose mail user has to enter header

(address and subject) and body of email. If address of the receiver is correct then JSM sends a

mail otherwise notifies “user name is not exists”. If user has harmful keyword as subject or

attaches an .exe file then admin catch and block this mail. Admin notifies to sender “Email

that you sent has harmful content” and sends an alert to the receiver “Email has harmful

content”.

8.3 Manage KeywordThis module is used by administrator. In this module administrator can add, delete and

modify harmful keyword. If admin wants to add a harmful keyword then he has to enter a

harmful keyword name. If keyword already exits then JSM notifies “keyword already exists”.

If admin wants to delete or modify a harmful keyword then he has to enter a harmful

keyword name. If keyword is not exits then JSM notifies “keyword is not found”. 46

47

Chapter 9

HARDWARE AND SOFTWARE REQUIREMENTS

9.1 Hardware requirementsThe project does not deal with any specific requirement about the h/w interfaces. It mainly

deals with user’s job to hide the data. The hardware require are basic fundamentals which are

required to run a program

Processor : Pentium-III (or) Higher

RAM : 64MB (or) Higher

Cache : 512MB

Hard disk : 10GB

9.2 Software requirements

Technology : Java, JSP and servlets

Web Technologies : HTML

Database : MySql

JDK Version : JDK1.6

Server : Tomcat5.5 or Glass Fish

Additional tools HTML Designing : Dream weaver Tool

Development Tool kit : NetBeans 6.9

48

49

Chapter 10

SYSTEM TESTING

10.1 Testing

During systems testing, the system is used experimentally to ensure that the software does not

fail. In other words, we can say that it will run according to its specifications and in the way

users expect. Special test data are input for processing, and the results examined. A limited

number of users may be allowed to use the system so that analyst can see whether they try to

use it in unforeseen ways. It is desirable to discover any surprises before the organization

implements the system and depends on it.

It should be clear in mind that the philosophy behind testing is to find errors. Test cases are

devised with this purpose in mind. A test case is a set of data that the system will process as

normal input. However, the data are created with the express intent of determining whether

the system will process them correctly. For example, test cases for inventory handling should

include situations in which this quantifies to be withdrawn from inventory exceed, equal and

are less than the actual quantities on hand. Each test case is designed with the intent of

finding errors in the way the system will process it. There are two general strategies for

testing software:

1. Code testing and

2. Specification testing.

In code testing, the analyst develops those cases to execute every instructions and path in a

program. Under specification testing, the analyst examines the program specifications and

then writes test data to determine how the program operates under specific conditions.

Regardless of which strategy the analyst follows, there are preferred practices to ensure that

the testing is useful. The levels of tests and types of test data, combined with testing libraries,

are important aspects of the actual test process.

Testing includes three parts:-

50

1. Testing- Error detection and error removal of newly developed program, so that it

produces specific output with correctness of live and artificial data.

2. Verification- It is also a kind of testing of system in simulated environment using

simulated data (alpha testing). It is done to detect and wait error regarding end user and

design specification we were specified in the earlier phase.

3. Validations- It refers to process of using software in a live environment in order to find

errors. Feedback of validation phase generally produces change in software to deal with error

and failure that are uncovered. Transaction that are extended and person using the system and

real and continue for several months.

Systems are not designed as entire systems nor are they tested as single systems. The analyst

must perform both unit and system testing.

Testing is of different types some of them are given below:-

1. Unit Testing

2. System Testing

10.1.1 Unit Testing

In unit testing the analyst tests the programs making up a system. For this reason, unit testing

is sometimes called program testing. Unit testing gives stress on the modules independently

of one another, to find errors. This helps the tester in detecting errors in coding and logic that

are contained within that module alone. The errors resulting from the interaction between

modules are initially avoided. For example, a hotel information system consists of modules to

handle reservations; guest check-in and check-out; restaurant, room service and

miscellaneous charges; convention activities; and accounts receivable billing. For each, it

provides the ability to enter, modify or retrieve data and respond to different types of

inquiries or print reports. The test cases needed for unit testing should exercise each condition

and option.

Unit testing can be performed from the bottom-up, starting with smallest and lowest-level

modules and proceeding one at a time. For each module in bottom-up testing a short program

is used to execute the module and provides the needed data, so that the module is asked to

perform the way it will when embedded within the larger system. 51

Test of individual module/program.

It is called program testing.

Valid and invalid data are entered to generate possible error. For Example: - Numeric error or

Date error.

It focuses in any module but not integrated part. It does not consider any linking error.

First stage of testing

Output – error free program.

All programs are working independently.

10.1.1.1 Black Box TestingIn this strategy some test cases are generated as input conditions that fully execute all

functional requirements for the program. This testing has been uses to find errors in the

following categories:

Incorrect or missing functions

Interface errors

Errors in data structure or external database access

Performance errors

Initialization and termination errors.

In this testing only the output is checked for correctness. The logical flow of the data is not

checked.

10.1.1.2 White Box Testing In this the test cases are generated on the logic of each module by drawing flow graphs of that

module and logical decisions are tested on all the cases. It has been uses to generate the test

cases in the following cases:

Guarantee that all independent paths have been executed.

Execute all logical decisions on their true and false Sides.

Execute all loops at their boundaries and within their operational bounds

Execute internal data structures to ensure their validity.

52

Unit Test Case for Administrator

TEST ID INPUT SPECIFICATION EXPECTED OUTPUT

Login Page

Administrator is asked to enter appropriate Login details (Email ID and password). If login details are correct then user redirect to the Client Page otherwise it shows “user name or password is not correct”.

1 Admin Main Page

It has four links:

1. Managed Keyword

2. Display Keyword

3. Alert List

4. Informative Mail list

It will ask to click on a link and redirect the

user corresponding page.

1.1

Manage Keywords

It manages the harmful keywords like

admin can add, delete and modify the

harmful keywords from the database.

Harmful keywords are the words that can

recognise harmful mails. Admin can also

logout or go to admin main page from it.

1.2 Display Keyword

It will show all harmful keywords that have been added by the user. Admin can also logout or go to admin main page from it.

It will show all the suspicious mails that have been sent by any user. Admin can

53

1.3

Alert mail list

recognise antisocial users. Admin can download Attachment of the mail from this page. User can also logout or go to client main page from it.

1.4 Informative mails

It will show all the informative mails that have been sent by any user. Admin can download Attachment of the mail from this page. User can also logout or go to client main page from it.

(Table 1)

Unit Test Case for user

TEST ID INPUT SPECIFICATION EXPECTED OUTPUT

Registration Page

It will ask to enter the user name, password and client personal details. If user name is unique then it will register to the user otherwise shows “User name already exists”.

Login Page

User is asked to enter appropriate Login details (Email ID and password). If login details are correct then user redirect to the Client Page otherwise it shows “user name or password is not correct”.

1

Client Main Page

It has three links:

5. Compose Mail

6. Inbox

7. Sent Mail

It will ask to click on a link and redirect the

user corresponding page. User can also 54

logout or go to client main page from it.

1.1 Compose page

It will ask the user to enter “to” (address of

recipient), subject, and attachment of the

file. If address of the recipient exits then it

will send the mail and notifies the user

otherwise shows “Email Id is not exists”.

Admin manages harmful content in it. If

subject matches with harmful keyword or

sender attaches .exe file then admin

generates an alert mail to the recipient and

also notifies to the sender. User can also

logout or go to client main page from it.

1.2 Inbox Page

It will show all the mails that have been received by the user. Client can download Attachment of the mail from this page. User can also logout or go to client main page from it.

1.3 Sent Mail Page

It will show all the mails that have been sent by the user. User can download Attachment of the mail from this page. User can also logout or go to client main page from it.

(Table 2)

10.1.2 System Testing

The important and essential part of the system development phase, after designing and

developing the software is system testing. We cannot say that every program or system

design is perfect and because of lack of communication between the user and the designer,

some error is there in the software development. The number and nature of errors in a newly

designed system depend on some usual factors like communication between the user and the

55

designer; the programmer's ability to generate a code that reflects exactly the systems

specifications and the time frame for the design.

Theoretically, a newly designed system should have all the parts or sub-systems are in

working order, but in reality, each sub-system works independently. This is the time to gather

all the subsystem into one pool and test the whole system to determine whether it meets the

user requirements. This is the last change to detect and correct errors before the system is

installed for user acceptance testing. The purpose of system testing is to consider all the likely

variations to which it will be subjected and then push the system to its limits.

Testing is an important function to the success of the system. System testing makes a logical

assumption that if all the parts of the system are correct, the goal will be successfully

activated. Another reason for system testing is its utility as a user-oriented vehicle before

implementation.

Testing of software after development all the modules are attached to make complete

program.

Test meets all requirements of the user.

All necessary outputs should be tested.

Installing of software.

System testing consists of the following three steps:

1. Program testing

2. String testing

3. User acceptance testing

10.1.3 Integrating Testing Integration testing ensures that software and subsystems work together a whole. It tests the

interface of all the modules to make sure that the modules behave properly when integrated

together.

10.1.4 Acceptance Testing It is a pre-delivery testing in which entire system is tested at client's site on real world data to

find errors.

56

10.2 Test Approach Testing can be done in two ways:

Bottom up approach

Top down approach

10.2.1 Bottom up ApproachTesting can be performed starting from smallest and lowest level modules and proceeding

one at a time. For each module in bottom up testing a short program executes the module and

provides the needed data so that the module is asked to perform the way it will when

embedded within the larger system. When bottom level modules are tested attention turns to

those on the next level that use the lower level ones they are tested individually and then

linked with the previously examined lower level modules.

10.2.2 Top down ApproachThis type of testing starts from upper level modules. Since the detailed activities usually

performed in the lower level routines are not provided stubs are written. A stub is a module

shell called by upper level module and that when reached properly will return a message to

the calling module indicating that proper interaction occurred. No attempt is made to verify

the correctness of the lower level module.

10.3 ValidationThe system has been tested and implemented successfully and thus ensured that all the

requirements as listed in the software requirements specification are completely fulfilled. In

case of erroneous input corresponding error messages are displayed

57

58

Chapter 11

SCREEN SHOTS

11.1 Home Page

Fig 11.1

It is the homepage where number of users’ login by entering their Email ID and passwords.

New user has to select the signup option to create a user account and then he can login.

11.2 Admin’s Login Page

Fig. 11.2

Here admin’s login by entering his username and password

60

11.3 Admin’s Main Page

Fig 11.3

Here is admin home page where he/she has the ability to manage keywords, encrypt

keywords. Admin has a feature of viewing the blocked mails

61

11.4 Adding a Keyword

Fig 11.4

Here admin adds numerous or harmful keywords by clicking the add button.

62

11.5 Displaying the Keyword

Fig 11.5

Here admin displays all the words which he/she had entered into the list

63

11.6 User’s Registration

Fig. 11.6

This is the User page where he/she enters his/her personal details and gets registered to Java

Secure Mail page

64

11.7 User’s Main Page

Fig 11.7

Here is User’s main page, it consists of compose mail, inbox and sent mail. Here user can

send mails, check the received mails and also able to see the sent mails

65

11.8 Composing a Mail by User

Fig 11.8

Here is the mail box where users can compose their mails.

66

11.9 Alert List of Blocked Mails in Admin Page

Fig 11.9

Here are the mails which had been got blocked in admin’s page due to hazardous information

in the mail

67

11.10 Message in Inbox of Other User

Fig 7.4.10

This screen gives the message in inbox of other user. Here user can read the received mails

and can download attached file.

68

69

Chapter 12

CONCLUSION, LIMITATION AND FUTURE SCOPE

12.1 Conclusion Email has been an efficient and popular communication mechanism as the number of Internet

user's increase. In many security informatics applications it is important to detect deceptive

communication in email.  In this application the mails are classified as suspicious or normal

using the keywords or .exe file. The mails containing these keywords and encrypted

keywords are classified as suspicious mails and they can be blocked and verified by the

administrator. The proposed work will be helpful for identifying the suspicious email and

also assist the investigators to get the information in time to take effective actions to reduce

the criminal activities.

12.2 Limitations1. The software does not use any back-up files for recovery of data when crashes of software

occur.

2. Administrator has to add suspicious keywords. Admin has to search the harmful keyword

and add into the database for better security. It increases effort of the admin.

3. This software does not use any sorting technique used for faster retrieval of access.

4. It supports SQL searching technique given by MySql.

5. The present application when implemented on internet requires a large database as the

backend.

6. It gathers everything in one location which is really good but if it is not prearranged then

you will spoil everything.

7. This software is not uploaded to the web server and running on PC only.

12.3 Future ScopeEven though the project fulfils the requirements of the present application there is always

scope for further work. According to the emerging changes and new versions, further work

can be done to improve the application since project is designed in flexible software.

70

This application which is a web based is of standalone application. This can be implemented

on internet by buying the network space and by creating a website. The present application

when implemented on internet requires a large database as the backend; this can be done by

using the MySql database as the backend. As we use encrypted keyword in this application

we can implement many encrypted algorithms like RSA, DES/3DES, BLOWFISH, AES,

IDEA and many more.

71

72

BIBLIOGRAPHY

WEB REFERENCES

http://google.com

http://www.tutorialspoint.com

BOOKS REFERENCES

The Complete Reference JAVA2 by Herbert Schildt Tata Mc Graw Hill India.

JAVA Server Programming Black book Kogent Solutions Inc.

Software Engineering by Pressman Tata Mc Graw Hill India.

Data Base Management System by Korth

73