SMTP Standard:

SMTP, short for Simple Mail Transfer Protocol, is an application layer protocol for
transmission of electronic mail on the internet. SMTP is the very popular email protocol that
allows two different users on two different servers to exchange textual data between each
other. SMTP manages the transmission of email messages on the Internet. It is a part of
TCP/IP suite of protocols that ensure smooth movement of electronics mails via the internet.

MIME Standard:
MIME is short for Multipurpose Internet Mail Extensions. MIME, as the name
suggests, is an email application program that extends the email messages format to support
more than just textual messages, such as audio, video, pictures, and so on. It was developed
to overcome some serious limitations in SMTP. MIME augments the internet email protocol
to enable transmission of non-ASCII data through emails, as opposed to SMTP which only
transmission of text messages over the internet. In fact, MIME was developed mainly for
SMTP, but the content types defined by MIME can also be used for communication protocols
outside the email ecosystem, such as HTTP.

S/MIME Standard:
Secure Multipurpose Internet Mail Extensions (S/MIME)
  A set of specifications for securing electronic mail. S/MIME is based upon the widely
used MIME standard and describes a protocol for adding cryptographic security services
through MIME encapsulation of digitally signed and encrypted objects. The basic security
services offered by S/MIME are authentication, non-repudiation of origin, message integrity,
and message privacy. Optional security services include signed receipts, security labels,
secure mailing lists, and an extended method of identifying the signer’s certificate(s).

What is the difference between a MIME content type and a MIME transfer encoding?

Emulate Version, Content-Type, and Content-Transfer-Encoding. These three headers

decide the idea of the remainder of the email message. For example, the Content-Type has
been set to message/plain. Nonetheless, the incentive for this header can be any substantial
MIME type, like picture/jpeg (for a JPEG design picture), or message/html (for a HTML-
organized message). Obviously, for the email to be appropriately delivered in the email
customer, the customer should see how to deliver a picture or HTML report.
Rigorously speaking MIME and content sort are two unique things. Emulate is a bunch of
norms that was composed to expand the capacities of email messages and has since been
applied all the more comprehensively to web content and HTTP. Content sort is a header
utilized both in email messages and HTTP.
For all intents and purposes, be that as it may, content sort and MIME type are utilized
reciprocally.
What is the difference between transport mode and tunnel mode in IP Security?
The differences are as below:

Tunnel mode:

 Tunnel mode protects the internal routing information by encrypting the IP header of
the original packet. The original packet is encapsulated by a another set of IP headers.
 It is widely implemented in site-to-site VPN scenarios.
 NAT traversal is supported with the tunnel mode.
 Additional headers are added to the packet; so the payload MSS is less.

Transport mode:

 The transport mode encrypts only the payload and ESP trailer; so the IP header of the
original packet is not encrypted.
 The IPsec Transport mode is implemented for client-to-site VPN scenarios.
 NAT traversal is not supported with the transport mode.
 MSS is higher, when compared to Tunnel mode, as no additional headers are required.
 The transport mode is usually used when another tunnelling protocol (such as GRE,
L2TP) is used to first encapsulate the IP data packet, then IPsec is used to protect the
GRE/L2TP tunnel packets.

Difference Table is as below:

Transport mode Tunnel mode

Here end hosts do IPsec encapsulation of IPsec gateways provide service to other
their own data; hence IPsec needs to hosts in peer-to-peer tunnels; hence the
implemented on each end-hosts end-hosts don’t need IPsec.

Lower overhead than tunnel mode More overhead required

No edits on IP header The entire packet is hashed or encrypted;

IP header is applied to the packet during
transit.

Used in securing communication from one Used to tunnel traffic from one site to
device to another. another

It is good for ESP host-to-host traffic It is good for VPNs, gateway-to-gateway

security.

Provides protection primarily to upper layer Provides protection to entire IP packet

protocols