RFC822 and RFC823 (Or the RSV versions 2822 & 2823). Read them, learn them,
study them, love them, for they are the holy writ of the wise prophets who
bestowed upon the world the gift of Internet email (and in doing so, gives
us meaningful employment). 



-----Original Message-----
From: James Lavoie [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 08, 2002 10:32 AM
To: Exchange Discussions
Subject: The great smtp mystery



I receive a message in my inbox sent to an email address that does not match
my own (completely different domain name). I use nslookup to resolve the
domain name of the sender's address and the domain doesn't exist. The
following day another employee receives a similar email with a "to:" address
that does not match our domain.
In both cases the recipients first name matched that of the first part of
the email address. 

Example:

Say my name is Jay and domain name is yahoo.com
I receive an email in my inbox sent to [EMAIL PROTECTED] - I have no mx record
for delta.com and my server is not configured to route delta.com inbound.

Can anyone explain this?

Thanks,
Jay

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to