Course Code : BCS-052

Course Title : Network Programming and Administration

Assignment Number : BCA(V)/052/Assignment/2025-26
Maximum Marks : 100
Weightage : 25%
Last Date of Submission : 31st October,2025(For July 2025 Session)
30th April, 2026 (For January 2026 Session)

There are three questions in this assignment. In total, they carry 80 marks. Answer all
the questions. 20 marks are for viva voce. You may use illustrations and diagrams to
enhance the explanations. Please go through the guidelines regarding assignments given
in the Programme Guide for the format of presentation.
Q1. What is SMTP? How does it differ from Internet Mail Access Protocol (IMAP)? (30
marks)

Solution:

Introduction

Email communication over the internet depends on several protocols that enable the sending,
receiving, and management of messages between users and mail servers. Among the most
critical protocols are SMTP (Simple Mail Transfer Protocol) and IMAP (Internet Mail
Access Protocol), which serve complementary but distinct roles in the email system. SMTP
is the protocol responsible for sending and routing outgoing mail, while IMAP is designed for
retrieving and managing incoming mail stored on servers.

What is SMTP?

SMTP (Simple Mail Transfer Protocol) is the primary protocol used for sending, routing,
and relaying email messages between mail servers on the internet. It governs how emails
are transmitted from the sender’s device to the recipient’s mail server.

• Purpose:
SMTP handles the transfer of email messages from the email client to the mail server
and between mail servers until the message reaches the recipient’s server.
• Protocol Type:
SMTP is a push protocol, meaning it pushes email data outward, initiating the
transfer from the sender server toward the recipient server.
• Port Numbers:
The traditional and standard ports for SMTP are:
o Port 25: Standard SMTP, mainly used for server-to-server communication.
o Port 587: SMTP mail submission port for client to server email sending with
authentication.
o Port 465: SMTP secured with SSL/TLS encryption (deprecated but still used
by some services).
 • How SMTP Works:

o A user composes an email and triggers sending via their email client (MUA -
Mail User Agent).
o The email client connects to the outgoing SMTP server (MTA - Mail
Transfer Agent).
o The SMTP server verifies the recipient address and figures out the best route
to forward the email, usually by looking up the recipient server’s address
using DNS MX records.
o The message is sent from SMTPS to the next mail server until it reaches the
recipient’s mail server.
• Limitations:
SMTP only manages email transmission; it does not provide mechanisms for email
retrieval or storage on clients.
It treats emails as simple messages and does not handle message status (read/unread).
• Email Envelope:
SMTP transmits information about the envelope (sender and recipient addresses)
separately from the message body, which allows flexible routing.

SMTP Workflow Example

• Alice writes an email to Bob and hits send.

• Alice’s email client connects to her outgoing SMTP server and transfers the mail
using SMTP commands (e.g., HELO, MAIL FROM, RCPT TO, DATA).
• The SMTP server assesses how to deliver the mail, looks up Bob’s mail server via
DNS, and forwards it.
• The process repeats if there are intermediary mail relays until Bob’s mail server
receives the message.

What is IMAP?
IMAP (Internet Message Access Protocol) is a protocol used for accessing, retrieving, and
managing email messages stored on a mail server.

• Purpose:
IMAP is designed to enable clients to view and manipulate messages stored on the
server without necessarily downloading them permanently. This allows email to be
synchronized across multiple devices.
• Protocol Type:
IMAP is a pull or access protocol because clients request data from the server as
needed.
• Port Numbers:
o Port 143: Standard IMAP.
o Port 993: IMAP over SSL (IMAPS), encrypted for secure communication.
• How IMAP Works:

o User’s email client connects to the mail server.

o Emails stay on the server, and the client fetches only message headers or full
messages on demand.
o Users can read, delete, flag, or move messages; these actions are synchronized
with the server so messages remain consistent across devices.
o Supports multiple client connections simultaneously, enabling real-time
mailbox updates.
• Advantages:
o Emails persist on the server, allowing users to access their mailbox from
different devices (PCs, smartphones, tablets) while maintaining
synchronization.
o Supports folder (mailbox) creation and management on the server.
o Tracks message state information, such as read/unread or flagged.
• Limitations:
Requires ongoing internet access to interact with messages stored on the server unless
explicitly downloaded.
IMAP Workflow Example

• Bob connects his email client to his email server using IMAP.
• Bob sees the list of emails but they remain on the server.
• When Bob opens a message, the email client downloads it temporarily to display but
the original remains on the server.
• Bob replies or deletes emails, and these changes update the server instantly, syncing
all devices accessing that mailbox.

Key Differences Between SMTP and IMAP

Feature SMTP (Simple Mail IMAP (Internet Message Access

Transfer Protocol) Protocol)
Role in Email Handles sending and routing Manages retrieval and
Communication outgoing emails. management of incoming emails.
Protocol Type Push protocol (sending emails Pull protocol (clients fetch mails
from client/server to server). from server on demand).
Primary Function Transfers emails from sender Allows users to read, organize,
to recipient mail servers. and manage mail on the server.
Message Storage Transfers messages; does not Stores messages on the server,
store or manage them supports remote mailbox
permanently. management.
Access from Not applicable, focused on Allows simultaneous access from
Multiple Devices sending messages only. multiple clients with
synchronization.
Ports Used 25 (SMTP), 587 (submission), 143 (IMAP), 993 (IMAPS)
465 (SMTPS)
User Interaction Typically invisible to user; Users actively interact, viewing,
works in the background and managing emails remotely.
sending email.
State Management Does not track message states. Tracks message states such as
read/unread, flagged, deleted.
Typical Usage Sending email from client to Retrieving, reading, and
server or between servers. organizing email stored on server.

Summary and Conclusion

• SMTP is the backbone protocol for sending and routing emails between clients and
servers. Its push-based design ensures that outgoing mail is forwarded properly
between mail servers until it reaches its destination.
• IMAP is the protocol designed for retrieving and managing email stored on
servers, enabling users to access mailboxes from multiple devices while maintaining
synchronization and message state.
• SMTP and IMAP work together in the email ecosystem to enable reliable and
flexible email communication: SMTP for sending, IMAP for receiving and message
management.
• Understanding these protocols and their differences is critical for email system
administration, troubleshooting, and software development involving email services.
Q2. Explain any 5 Socket options. (30 marks)

Solution: In network programming, sockets provide endpoints for communication between

devices over a network. Socket options control various aspects of socket behavior and
performance. They allow programmers to customize socket functionality to suit specific
application needs, optimize communication, and manage resources effectively. Operating
systems typically provide a rich set of socket options, accessible through system calls like
setsockopt() and getsockopt() in languages such as C.

Understanding these options is crucial for designing robust and efficient networked
applications, especially in real-time, high-performance, or resource-constrained
environments.

1. SO_REUSEADDR (Reuse Address)

• Purpose:
Allows a socket to forcibly bind to a local address (IP address and port) already in use
by another socket in TIME_WAIT state.
• Explanation:
After a socket is closed, the operating system keeps the associated port unavailable for
a period (known as TIME_WAIT), preventing immediate reuse. Setting
SO_REUSEADDR enables a new socket to bind to the same address and port, even if
the previous socket is in TIME_WAIT. This is especially useful for server
applications that need to restart and bind to the same port without waiting.
• Use Case:
Web servers, database servers, or any TCP server needing quick restart on the same
port without delays.
• Example:

int opt = 1;
setsockopt(sockfd, SOL_SOCKET, SO_REUSEADDR, &opt,
sizeof(opt));

2. SO_KEEPALIVE (Keep-Alive Probes)

 • Purpose:
Enables periodic transmission of keep-alive messages on an idle connection to check
if the peer is still reachable.
• Explanation:
TCP connections may become idle for a long time. Without keep-alive, a broken
connection might not be detected promptly, leading to data loss or hanging
connections. Enabling SO_KEEPALIVE causes the OS to send keep-alive probes
after a period of inactivity. If no response is received after several retries, the
connection is considered dead and is closed.
• Use Case:
Long-lived connections like database connections, interactive sessions, or remote
shells where detecting dead peers early is essential.
• Configurable Parameters:
Keep-alive interval, probe count, and timeout can usually be tuned via system-level
settings.

3. SO_BROADCAST (Broadcast Permission)

• Purpose:
Permits sending packets to the broadcast address on the network.
• Explanation:
Broadcasting sends packets to all hosts in a subnet. By default, sockets do not allow
broadcast transmission for security reasons. Setting SO_BROADCAST enables a UDP
socket to send datagrams to the broadcast address (e.g., 255.255.255.255 in IPv4).
The socket must be set with this option before using broadcast addresses.
• Use Case:
LAN discovery protocols, network beaconing, or applications needing to
communicate with all machines on a subnet.

4. SO_LINGER (Linger on Close)

• Purpose:
Controls the behavior of a socket when closed with unsent data remaining.
• Explanation:
Normally, when a socket is closed, the system tries to send any remaining data in the
background. SO_LINGER modifies this behavior where the close operation can block
until the data is sent or a timeout occurs. The option is set by enabling/disabling linger
and specifying a timeout duration.
• Use Case:
Applications needing to control socket closing behavior explicitly, ensuring all data
are sent before closure or performing an abortive close for urgent shutdown.
• Example:

struct linger sl;

sl.l_onoff = 1; // Enable linger option
sl.l_linger = 10; // Wait 10 seconds before forceful close
setsockopt(sockfd, SOL_SOCKET, SO_LINGER, &sl, sizeof(sl));
5. SO_RCVBUF / SO_SNDBUF (Receive and Send Buffer Size)

• Purpose:
Sets the buffer sizes for receiving and sending data on a socket.
• Explanation:
These options define the size of the kernel buffer used to hold incoming packets
(receive buffer) or outgoing packets waiting to be sent (send buffer). Adjusting buffer
sizes can optimize network throughput and performance based on application
requirements and system characteristics.
• Use Case:
High-speed data transfer applications, streaming servers, or real-time systems
requiring tuning of socket buffer sizes for latency or throughput optimization.
• Example Usage:

int recv_buf_size = 65536; // 64 KB buffer

setsockopt(sockfd, SOL_SOCKET, SO_RCVBUF, &recv_buf_size,
sizeof(recv_buf_size));

Summary Table of Socket Options

Socket Option Purpose Usage Scenario Key Effect

SO_REUSEADDR Reuse local Restarting servers Allows rebinding

address/port quickly without to the same port
waiting immediately
SO_KEEPALIVE Keep connection Long-lived Sends probes to
alive on idle connections needing detect dead peers
failure detection
SO_BROADCAST Enable sending Network discovery Allows sending to
broadcast packets and broadcast broadcast address
messaging
SO_LINGER Control blocking Ensuring data is sent Blocks or aborts
behavior on close or closing socket close pending
immediately unsent data
SO_RCVBUF / Set buffer sizes for Performance tuning Adjusts kernel
SO_SNDBUF receiving/sending in high throughput buffer sizes for
applications efficiency

Conclusion

Socket options are powerful tools that allow network applications to operate efficiently and
reliably under diverse environments. The five options explained—SO_REUSEADDR,
SO_KEEPALIVE, SO_BROADCAST, SO_LINGER, SO_RCVBUF / SO_SNDBUF—
are among the most commonly used and serve crucial functions such as resource reuse,
connection reliability, network communication scope, graceful shutdown, and performance
optimization.
Q3. Explain various Disk Management functions. (20 marks)...

Solution:

Disk management is a critical function of an operating system responsible for managing

storage devices such as hard disks, SSDs, and removable media. It involves several key
operations that ensure efficient storage utilization, data organization, and reliability. Proper
disk management enables the operating system to create, maintain, and control filesystems
and physical storage, ensuring data integrity and accessibility.

Key Disk Management Functions

1. Disk Partitioning
o Definition: Dividing a physical disk into logical sections called partitions.
Each partition can be treated as an independent disk by the operating system.
o Purpose: Enables the separation of data, allows multiple operating systems
installation, and helps organize data logically.
o Types of partitions: Primary partitions, extended partitions, and logical
drives exist to support flexible disk usage.
o Benefit: Enhances system organization and can improve data security and
recovery.
2. Formatting
o Definition: The process of preparing a disk partition for use by creating a
filesystem on it.
o Purpose: Formats create the structure needed for storing files and directories.
o Types: Low-level formatting (done by manufacturer) and high-level
formatting (creating filesystem structures like FAT32, NTFS, ext4).
o Benefit: Enables the operating system to manage storage space and access
files efficiently.
3. File System Management
o Definition: Managing the organization, storage, naming, retrieval, and access
control of files on storage devices.
o Functions include:
§ Creating and deleting files and directories.
§ Managing free space and allocating disk blocks to files.
§ Maintaining file metadata (e.g., timestamps, permissions).
o Role: Ensures that files are stored in an organized manner and are accessible
with minimal overhead.
4. Disk Space Allocation
o Definition: Allocating storage space on the disk for file storage in an efficient
manner.
o Methods:
§ Contiguous allocation: Files occupy consecutive blocks.
§ Linked allocation: Files consist of linked blocks, scattered around.
§ Indexed allocation: Index blocks keep track of file block locations.
o Goal: Maximize disk utilization, minimize fragmentation, and optimize
read/write performance.
5. Disk Scheduling
o Definition: Ordering and managing read/write requests for the disk to improve
efficiency.
 o Common Algorithms: First Come First Serve (FCFS), Shortest Seek Time
First (SSTF), SCAN, C-SCAN.
o Importance: Reduces seek time and latency, improving overall system
performance.
6. Disk Caching and Buffering
o Disk Caching: Temporary storage of frequently accessed disk data in fast
memory to speed up subsequent access.
o Buffering: Holding data in memory while being transferred between disk and
application to smooth out speed differences.
o Benefit: Enhances data access speed and system responsiveness.
7. Defragmentation
o Definition: The process of reorganizing scattered file fragments into
contiguous blocks.
o Purpose: Reduces access time and improves read/write performance by
minimizing head movement on spinning disks.
o Applicability: Particularly important for systems using file allocation methods
prone to fragmentation (e.g., FAT).
8. Disk Monitoring and Status Reporting
o Functions: Track disk health, free space, usage statistics, and report errors or
failures.
o Tools: SMART (Self-Monitoring, Analysis, and Reporting Technology) used
to monitor disk reliability.
o Goal: Detect problems early and alert users to prevent data loss.
9. Disk Security Management
o Functions: Implement access controls, encryption, and permissions to
safeguard data on disk.
o Mechanisms: User authentication, file access rights, and encrypted
filesystems.
o Importance: Prevent unauthorized access and data breaches.
10. Backup and Recovery Management
o Definition: Managing disk-based backups for data protection and enabling
system recovery during failures.
o Tools: Disk snapshots, incremental backups.
o Purpose: Ensures data availability and resilience against hardware or software
failures.

Conclusion

Disk management functions constitute a foundational aspect of operating system design and
ensure efficient, secure, and reliable storage utilization. From partitioning and formatting to
caching, scheduling, and security, these functions collectively maintain data integrity and
system performance. Mastery of disk management is essential for IT professionals and
computer science students, as it directly impacts system stability and user experience.