August 2006

Reminder: Meeting is tonight at the Exeter Library.

Our August Meeting will be held at the EXETER PUBLIC LIBRARY

in the multifunction room.

Date: Wednesday, August 16th
Time: 6:00pm to 9:00pm

This month’s topic: Scrutinizer – what it is, why you need it, and how it=
works. Mike Patterson from Somix wants to share with us how his software wh=
ich takes Cisco’s NetFlow data and makes some fantastic reports.

If you have a Cisco router you must attend this session – it’s that good.=

For Directions:

http://www.exeterpl.org/direct.html =


SEA-TUG is a technical user group (ie: for System Admins, not home users) me=
eting once a month on topics relating to IT Infrastructure, Hardware, Softwa=
re, Security, Patches, Deployment, etc. We are a registered Culminis user gr=
oup. We follow the popular User-Group format: a technical presentation follo=
wed by a technical/sales presentation (when appropriate). We are modeled aft=
er some of the more successful user groups such as the Boston Area Windows S=
erver User Group, only without the two-hour=20
drive back and forth.  

SMTP

 

Internet email is sent using Simple Mail Transfer Protocol (SMTP)
This is defined in RFC 821

Your email client connects to the SMTP server - usually port 25.

The email client will print a header to confirm it is, indeed, an email server running SMTP.

220 rglapache SMTP NAVIEG 2.1 bld 63; Thu, 17 Oct 2002 09:18:30 -0700Your email client will now get the attention of the SMTP server. It can do so with a “HELO” or an “EHLO” command. HELO is standard SMTP, and EHLO is extended and more or less asks the SMTP server to identify which advanced functions it supports.  

HELO localhost

The SMTP server responds to let the client know it is alive, well and waiting for commands.

250 rglapach Hello

The client identifies who the email is from using the “MAIL FROM:” command.

MAIL FROM:test@testingsmtp.com

The SMTP server responds with a confirmation that it’s okay to continue.

250<test@testingsmtp.com>… Sender ok

Now the client informs the SMTP server who the email is to be sent to using the “RCPT TO:” command. More than one of these commands may be used to send to more than one recipient.

RCPT TO: richlowe@internet-tips.net

The SMTP server responds that this is okay:

250 <richlowe@internet-tips.net>… Recipient ok

The client sends the command “DATA” to tell the SMTP server it will now send the message. After that, text is sent, line by line, until the entire message has been transmitted. The message is ended with a “.” on a line all by itself.

DATA
354 Enter mail, end with “.” on a line by itself
Message-Id:<02101708262848@testingsmtp.com>
From: test@testingsmtp.com
To:richlowe@internet–tips.net
Subject: This is a test of SMTP
This example shows how SMTP works. Pretty nifty, isn’t it?

.

You should note from the above that the “Message-id”, “To:” and “Subject:” (as well as others such as “Cc:”, “Bcc:” and so on) are sent to the email server as part of the message data. These are what displays as the “Subject” and “To” when you open the email. Note that the actual recipient and who the email is from is sent BEFORE the data.

The implication is that since these are part of the message they can be forged. In fact, that is exactly what spammers and some of the newer viruses do. Klez, for example, chooses a random email address for the “From:” and “To:” fields, making it appear that someone else has sent the message.

The SMTP server replies that this is fine and will be delivered.

250 M2002101709193007556 Message accepted for delivery

The client can either start another message or quit using the “QUIT” command.

© 2010 LANalyze Suffusion WordPress theme by Sayontan Sinha