On 10/10/07, John DeCarlo <[EMAIL PROTECTED]> wrote:
> Very nice description.  Well done.

<ducking> Thanks.  I hope the thick South Asian accent doesn't throw
off Jeff.  :-)  </ducking>

> Just one nit.

What do you do with the nits you pick?  EBAY them?

> > So, given you trust your mail server, the above line with the
> > "by mx.yourdomain.org ..." is the only line you can be certain of.
> > What that line tells you is that your (ISP's) mail server received this
> > message from a host with an IP address 220.220.22.22 and _your_ mail

> Actually, it means that the message was received from a host that
> claimed to be 220.220.22.22, but unless your ISP does special checking,
> that may not be true.

At least wrt my mail servers, what's inside the () of "Received: from
blah.blah.com (blahost.blahcom.com [xx.xx.xx.xx])" are added by my
server.  So, at least during the SMTP transaction, the remote host,
rightly or wrongly, claimed the ownership of that IP address.  Yes,
you are right, IP-spoofing, man-in-the-middle, etc. etc. apply and you
can't be sure if the stranger you are talking to is the person they
claim to be.  Authenticated SMTP is a different matter, but we are
just talking about timestamps.


************************************************************************
* ==> QUICK LIST-COMMAND REFERENCE - Put the following commands in  <==
* ==> the body of an email & send 'em to: [EMAIL PROTECTED] <==
* Join the list: SUBSCRIBE COMPUTERGUYS-L Your Name
* Too much mail? Try Daily Digests command: SET COMPUTERGUYS-L DIGEST
* Tired of the List? Unsubscribe command: SIGNOFF COMPUTERGUYS-L
* New address? From OLD address send: CHANGE COMPUTERGUYS-L YourNewAddress
* Need more help? Send mail to: [EMAIL PROTECTED]
************************************************************************
* List archive at www.mail-archive.com/[email protected]/
* RSS at www.mail-archive.com/[email protected]/maillist.xml
* Messages bearing the header "X-No-Archive: yes" will not be archived
************************************************************************

Reply via email to