Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 409
  • Last Modified:

Exchange routing problem

Message header follows. As near as we can tell, there is no way we should have received this mail. It is really cause for concern. Hopefully I'm not exposing any security information on this forum with the info in this header.
Obviously, we're asking the question because the message was intended to stay in its own domain, and somehow leaked to the outside world and landed in ours.

TIA

slang9

Received: from mail.woodruff-sawyer.com (w-s.woodruff-sawyer.com [207.171.210.22]) by gl-2.genelabs.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
 id JD9ZCNGZ; Sun, 30 Apr 2000 15:17:31 -0700
Received: by MAIL with Internet Mail Service (5.5.2448.0)
 id <JDAAQ8BA>; Sun, 30 Apr 2000 15:21:02 -0700
Message-ID: <2D1B9C611DABD21183C4009027283C5E6EC069@MAIL>
From: Andy Barrengos <abarrengos@woodruff-sawyer.com>
To: "'Laura A. Larsen (Business Fax)'" <IMCEARFAX-Laura+20A+2E+20Larsen+40_FN=1+20+28510+29+20777-7001@woodruff-sawyer.com>

0
slang9
Asked:
slang9
1 Solution
 
Tim HolmanCommented:
I don't quite understand the problem.
It's an email from woodruff-sawyer to someone called Laura !
0
 
slang9Author Commented:
Correct, internal at woodruff-sawyer to another person at woodruff-sawyer.
We are not that firm, but it landed in our Exchange server and went to a user named Bruce.
0
 
RoninCommented:
I suppose that the problem in misconfiguration of the domain woodruf domain.
0
 
Tim HolmanCommented:
Contact the postmaster of this domain, and ask him/her, or even this Andy Barrengos chap ?
This message looks like a fax, sent to the woodruff fax server and relayed out to fax recipients.
0
 
danichCommented:
Whenever you are troubleshooting the IMS, you must turn on either archiving or protocol log (latter requires SMTP interface events as well) in Diagnostics logging. Either of these give you the true story; what the user sees as headers does not show everything.

Most likely your local user was BCC:ed for some reason. The actual recipient was a fax address of another person at Woodruff, and there was a BCC: line. This does not get exposed in the message the user sees (for obvious reasons), but will be captured in the archive or, better, the protocol log.
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

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

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