• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 181
  • Last Modified:

Some help on Exchange 2007 and message tracking

I had a user that reported she "didn't send" a particular email.  I can confirm it isn't in her sent email folder.  When I did the tracking on it, I found the email in the logs, and it shows all the same information as the email in question.  My question is how do I actually read the body of it and the attachment, not just the statistical information?
0
tsaico
Asked:
tsaico
  • 2
1 Solution
 
Jeffery HayesSystem Support Technician Commented:
Look at the message header for the mailbox the message was revived in.

In message tracking the only real thing you might notice is the IP address.

However if you look at the message header you can quickly see were the message was sent from along with who actually sent the message.

If possible can you provide the message header as I'll happy review it and let you know what I think occurred.

So far what it sounds like happen is that the message might have been spoofed which is really common.

As your want to look at both the following values..

Return-Path:
From:

Most times with spoofing one of these values won't be the same.
0
 
tsaicoAuthor Commented:
I had turned on journaling for that specific user.  It turned out she had written a rule to auto send emails when a certain condition applied, but didn't finish writing the rule, thinking it was a "draft" kind of thing that wouldn't be in effect.
0
 
tsaicoAuthor Commented:
While good advice, turned out it was a rule that was forwarding the email, and a other that was autodelting when she sends emails to herself.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now