Automated SMTP server

ABSTRACT

The project Entitle “SMTP MAIL SERVER” deals with identifying the clients to send
and receive mail with the login. This utility will allow multiple clients to login under the login
name and still have personalized mail information, enabling them to send and receive mails.
Each user willing to avail the services offered by the mail server application should exist as a
user before he can send or receive mails. This is made possible by prompting each user to enter
his user-id and password before he can send or view his mails. This project has Inbox, compose
and address list. E-mail is one of the most common and reliable methods of communication for
both personal and business purposes. It also plays an important role in each and every Web site.
This role will be in the type of automated e-mails from the server after posting information from
a form. A message has to be composed in compose box. This message is stored in inbox
directory of receiver. This file should be combination of the sender’s user-id and sub. The file
transmitted is moved from sender compose to receiver inbox. The recipient can view the
message by selecting the appropriate file no. This is also provision for the replying and deleting
the message .This utility also enables users, working under different login names to
communicate with each other. We can send files through attachments. In this we attach the files
to the mail by browsing option. From desktop or any drive we can select files and we will attach
them to the mail which we want to send presently and then we send them to the receiver.

Existing SYSTEM

The current system has a login created for each user and has their mail box created
or associated with each one of them. The administrator maintains them. This is a complex setting
in which each user can send and receive mails throughout the world. Each user and his mailbox
have to be taken care of by the administrator.

PROPOSED SYSTEM

The system to be developed should allow users to login into a common user account
and each and every user has a unique id and password. The system is also responsible for
creating mailboxes for every user. This solves the purpose of having multiple user account s and
their maintenance. The number of logins to be administered will be less and each user has
privacy to his incoming messages.

MODULE DESCRIPTION:

The project consists of the following six modules:

1.User administration.
2.Mail organization.
3.Message composition.
4.Message Address list
5.Message Inbox.
6.Message Deletion.

User Administration Module

It deals with the creation of users and user maintenance . Every user willing to use the
mail server application should be existing as a user before they can send or receiving mails. Each
user is needed to specify the user name, password and date of creation .

A unique user-id is created or generated automatically and is associated with each user by
the system.

The users password should not be displayed as they are typed. Users should be allowed to
change their password as and when required . The users can be deleted only by the administrator.
The admin user is by default created by the system and his password can be changed after he
locks in as admin. The list of users created can be viewed in a tabulated output.

Mail Organization Module

This module deals the organization of mails. When the users are created ,a directory with
the user-id as its name should be created along with four sub directories:

Inbox, Compose and Address list.

The Compose box contains the transmitted messages.
The inbox contains all the incoming messages.
The Address list box contains the users messages that can be recovered
Message Composition Module

This module deals with composing messages . It forms the information such as:

“From” (Sender’s user-id), “To”(Receivers user-id), “Date of Transmission”, “Subject”,

and “Message” to be transmitted. The message is converted and stored as a file in the outbox of
the sender before it is being transmitted. The file name should be the combination of the
sender’s user-id and receiver’s user-id.

The module prompts the user for the file information that has to be transmitted. The messages
can be user-typed information at runtime or messages that are part of the file. The user is
supposed to type in the message or specify the file name. Other information such as from whom,
the message is transmitted, to whom, it is being transmitted, date of transmission are also
accepted.
This information is stored in a file that has the name of the user-id concatenated along with the
name of the receiver’s user-id . The composed messages is then stored in the outbox of the
sender. This file remains till it is selected and transmitted by transmit module. Every user’s
composed message is stored in the user’s outbox.

Message Address list Module

This module is responsible for having all the massages, which have been stored in the user’s
Address. Once the user create all the contents of the file are displayed in the view file. These
Contents are, from whom the message has been sent, date on which it was received, subject and
the messages

Message Deletion Module

This module allows a user to delete a message by letting him browse through a list of
messages that is part of his inbox. A provision is provided where the deleted messages can be
recovered.

An option to empty the delete folder is provided so that recovering of deleted message is
not possible.

SOFTWARE REQUIREMENTS

The software used in this project is:

Operating System: Windows 2000.

Language : Internet Information Server 5.0 with .NET Framework installed.

Visual studio. Net

Data Base :Oracle 8i.

HARDWARE REQUIREMENTS

The hardware used in this project is:

RAM : 256 MB.

Processor : P-IV Processor.

Hard Disk : 20 GB
.
Memory :32 MB.