It ends with my friends receiving an email like this:
It begins with me connecting to my mail server with telnet or netcat. After connecting, I have an SMTP session with it like this:
susam@nifty:~$ telnet mail.susam.in 25 Trying 22.214.171.124... Connected to susam.in. Escape character is '^]'. 220-krishna.ewebguru.net ESMTP Exim 4.69 #1 Mon, 15 Feb 2010 02:10:18 +0530 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail. EHLO 250-krishna.ewebguru.net Hello [126.96.36.199] 250-SIZE 52428800 250-PIPELINING 250-AUTH PLAIN LOGIN 250-STARTTLS 250 HELP AUTH PLAIN ×××××××××××× 235 Authentication succeeded MAIL FROM:<prun××××××@gmail.com> 250 OK RCPT TO:<prun××××××@gmail.com> 250 Accepted RCPT TO:<wes×××××××@gmail.com> 250 Accepted RCPT TO:<sus××××××@gmail.com> 250 Accepted RCPT TO:<ind××××××××××@gmail.com> 250 Accepted RCPT TO:<kart×××××××@gmail.com> 250 Accepted DATA 354 Enter message, ending with "." on a line by itself Date: Mon, 21 Dec 2012 10:28:00 +0530 From: "Prunthaban Kanthakumar" <prun××××××@gmail.com> To: "Prunthaban Kanthakumar" <prun××××××@gmail.com> Cc: "Susam Pal" <sus××××××@gmail.com>, "John Wesley" <wes×××××××@gmail.com>, "Indhu Bharathi" <ind××××××××××@gmail.com>, "Karthik" <kart×××××××@gmail.com> Subject: Experiment Successful I was working today (21 Dec, 2012) on an experiment to send messages to a space-time co-ordinate in the past. If this experiment is successful I should receive this mail on 15 Feb, 2010, a date in the past. It is quite funny that we can remember the past but not the future. So, when I receive this message on (15 Feb, 2010), I wouldn't remember that this is the result of a successful revolutionary experiment to be performed in future. I should have got this message time stamped by a trusted time stamping authority in order to prove that this message is indeed from the future but that has its own problems. Why would I, in the past, believe that such a trusted time stamping authority would exist in the future? Moreover, I don't have time to get all this done as the world is coming to an end today. . 250 OK id=1NglGq-0008JC-RK QUIT 221 krishna.ewebguru.net closing connection Connection closed by foreign host.
An internet message or email consists of two sections: header and body. The header usually consists of fields like 'From', 'To', 'Cc', 'Subject', etc. which are usually displayed to the user. It may have more fields like 'Message-ID', 'Return-Path', 'Content-Type', etc. which are usually not displayed to the user. But many email programs provide some mechanism to view them as well. For instance, in GMail, one can click the little arrow near the 'Reply' button and select the 'Show original' option to view the message with all the message headers. In Microsoft Office Outlook, selecting 'Options' from the 'View' menu in the message window shows all the message headers.
These headers, which are usually not displayed by the email program, are used by the email client and the various programs running on various mail servers to deliver the email to the recipient's inbox. For example, if the delivery of the email fails for some reason, a message describing the failure would be sent to the email address found in the 'Return-Path' field. This is usually the email address of the sender. This field is automatically added by the mail server before sending the email.
The actual message meant to be read by the recipient is contained in the message body. The message body begins after the message headers. The message header and the message body are separated by an empty line. These things can be seen in the above example.
When we compose an email using web based emails like GMail, Hotmail, etc. or email clients such as Microsoft Outlook, Thunderbird, etc. the client automatically enters the sender's email address in the 'From' field before sending the email. Similarly, it automatically uses the email addresses mentioned in the 'To' and 'Cc' fields as recipients of the email. The email client connects to the SMTP server and executes the necessary commands to send the email.
However, when we have a session with the SMTP server, we need to execute
those commands ourselves. For example, each recipient is specified with
RCPT TO command. The actual email message that is
displayed to the user by the various email clients begins after the
DATA command. The message headers such as 'From', 'Date',
etc. have to be composed manually.
This gives us more freedom while composing the message. We can specify a
future date in the 'Date' field. We can specify a false email address in
the 'From' field. There need not be any relation between the recipients
specified with the
RCPT TO command and the email addresses
specified in 'To' and 'Cc' fields. So, it is possible to send an email
to one person with the 'To' or 'Cc' field displaying the email address
of another person. Similarly, the 'From' field need not contain the
email address of the actual sender. SMTP is not concerned with the
correctness of these fields.
In the above example, I have composed an email with the email address of
a friend in the 'From' as well as 'To' headers. Similarly, I have
specified a future date in the 'Date' field. I have specified a false
email address in the
MAIL FROM command as well because the
email address specified there appears in the 'Return-Path' field in the
In the examples above, I have smudged or hidden parts of the authentication response and the email addresses with crosses for privacy reasons. The authentication response contains the credentials I use to log into my email server. For more on how to form an authentication response, see: AUTH CRAM-MD5.
Here are a couple of hyperlinks for further reading.