Microsoft Mail Internet Headers Version 2.0
Received: from mgear.com ([xxx.xx.xx.xx] RDNS failed) by xx.com with
Microsoft SMTPSVC(5.0.2195.6713);
Fri, 21 Jan 2005 12:31:23 -0700
Date: Fri, 21 Jan 2005 11:49:33 -0800
Message-Id: <10501211149...@mgear.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
From: "Postmaster" <postm...@mgear.com>
Sender: <postm...@mgear.com>
To: <my email address>
Subject: Undeliverable Mail
X-Mailer: <SMTP32 v8.05>
Return-Path: <>
X-OriginalArrivalTime: 21 Jan 2005 19:31:23.0562 (UTC)
FILETIME=[CAA9F8A0:01C4FFEF]
I changed some of the information to x's.
--
Dave
Well, without knowing whether mgear.com or the IP /server information
belongs to you, it's hard to say.
Then it ain't you, babe. What's your question?
You said someone external to your network got this, right?
And none of the IP/host info is yours?
Then it's probably spoofing, or a virus, and nothing to do with you.
But it's always good to check that your server isn't open to being used as a
relay, including authenticated relay.
All right, you said the recipient was a client, so I assumed you meant it
was someone external.
If you see a message that purports to be from an address internal to the
network (as in, for a domain Exchange is handling), and yet it has Internet
Mail headers, it isn't internal, and yes, it's probably a result of
spoofing. Anybody can spoof you....
Another possibility is that someone, somewhere, who has the recipient's name
in their address book, has a virus that is spoofing the sender.
In any case, it doesn't sound like it's a problem with the Exchange server.
Presuming Exchange 2000/2003:
See http://www.msexchange.org/tutorials/MF005.html for a good overview of
relaying and spam.
Also see http://www.vamsoft.com/orf/authattack.asp - if you don't have
strong/complex password policies enabled, force regular password changes,
have enabled guest, etc., someone may exploit authenticated relay. If you
don't need authenticated relay, disable it. You can always have any external
POP users use their own ISP's SMTP server for outbound mail anyway.