No one has responded to this discussion for at least a year, so this information may be out of date. If you're looking for information about this topic, please search for a more recent discussion or post a new question.

Email sent by user A 2 weeks ago, showed up again as being sent by user B 2 days ago

  • 2 Followers
  • 6 Replies |
  • This post has 0 verified answers |
Answered (Not Verified) This question has suggested answer(s)

One of my colleagues sent out a new meeting invitation to our staff 2 weeks ago (and we received it). 2 days ago, we all received the same meeting invitation but this time, it shows as being sent from a different colleague, the message was cut off, and the colleague did not send it. Could you assist me on what to check to see if the 2nd collegue's email was hacked? any help would be greatly appreciated.

 

 

  • Post Points: 20
All Replies
  • Hi alNV,

     

    To troubleshoot the issue, you can do the following step:

    Please run the Delivery reports and check if there is any other emails have been sent which the user B didn’t send.

    For more information about Delivery reports, you can refer to the following link

    http://help.outlook.com/en-us/140/ms.exch.ecp.trackmessagesent.aspx

    To further troubleshooting, please post the two mail headers to us.

    Thanks,

    Jason Jiang

    • Top 25 Contributor
    • Post Points: 0
    Suggested by
  • Hi Jason,

    Thank you for the suggestion on the Delivery Reports. I will check that once I get the chance to.

    are you referring to the Internet Headers? If so, here are the ones from the 2 emails....

    From the original one:

    Received: from SN2PRD0510HT003.namprd05.prod.outlook.com (10.255.116.38) by

    CH1PRD0511HT003.namprd05.prod.outlook.com (10.255.159.38) with Microsoft SMTP

    Server (TLS) id 14.16.224.5; Thu, 18 Oct 2012 22:43:52 +0000

    Received: from SN2PRD0510MB396.namprd05.prod.outlook.com ([169.254.8.12]) by

    SN2PRD0510HT003.namprd05.prod.outlook.com ([10.255.116.38]) with mapi id

    14.16.0224.004; Thu, 18 Oct 2012 22:43:51 +0000

    Content-Type: application/ms-tnef; name="winmail.dat"

    Content-Transfer-Encoding: binary

    From: Stephanie D'Arcy <sdarcy@nvdm.org>

    To: Staff <staff@nvdm.org>

    Subject: Discovery Community Volunteer Event - Food Bank of Northern Nevada

    Thread-Topic: Discovery Community Volunteer Event - Food Bank of Northern

    Nevada

    Thread-Index: Ac2tggqsplVaspslR7uPiGX86Qiljw==

    Date: Thu, 18 Oct 2012 22:43:50 +0000

    Message-ID: <F93613F863AD9B4ABEA9BA9772A6D61A3E2D5992@SN2PRD0510MB396.namprd05.prod.outlook.com>

    Accept-Language: en-US

    Content-Language: en-US

    X-MS-Has-Attach:

    X-MS-Exchange-Organization-SCL: -1

    X-MS-TNEF-Correlator: <F93613F863AD9B4ABEA9BA9772A6D61A3E2D5992@SN2PRD0510MB396.namprd05.prod.outlook.com>

    MIME-Version: 1.0

    X-MS-Exchange-Organization-AuthSource: SN2PRD0510HT003.namprd05.prod.outlook.com

    X-MS-Exchange-Organization-AuthAs: Internal

    X-MS-Exchange-Organization-AuthMechanism: 04

    X-Originating-IP: [66.214.111.10]

    X-MS-Exchange-Organization-AVStamp-Mailbox: MSFTFF;1;0;0 0 0

    X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply

    Return-Path: <>

    X-EsetId: 00A1FD220617813351E5A2

    From the 2nd one (this is the one that was "NOT" sent:

    Received: from BL2PRD0510MB361.namprd05.prod.outlook.com ([169.254.2.225]) by

    BL2PRD0510HT004.namprd05.prod.outlook.com ([10.255.100.39]) with mapi id

    14.16.0233.002; Mon, 5 Nov 2012 03:29:43 +0000

    Content-Type: application/ms-tnef; name="winmail.dat"

    Content-Transfer-Encoding: binary

    From: Nicole Barde <nbarde@nvdm.org>

    To: Staff <staff@nvdm.org>

    Subject: Discovery Community Volunteer Event - Food Bank of Northern Nevada

    Thread-Topic: Discovery Community Volunteer Event - Food Bank of Northern

    Nevada

    Thread-Index: Ac27Bcsb0fbutew4THCYgGv+nmwATw==

    Date: Mon, 5 Nov 2012 03:29:42 +0000

    Message-ID: <63F05031-7CEC-4673-8937-BB0B73136983@nvdm.org>

    Accept-Language: en-US

    Content-Language: en-US

    X-MS-Has-Attach:

    X-MS-Exchange-Organization-SCL: -1

    X-MS-TNEF-Correlator: <63F05031-7CEC-4673-8937-BB0B73136983@nvdm.org>

    MIME-Version: 1.0

    X-MS-Exchange-Organization-AuthSource: BL2PRD0510HT004.namprd05.prod.outlook.com

    X-MS-Exchange-Organization-AuthAs: Internal

    X-MS-Exchange-Organization-AuthMechanism: 04

    X-Originating-IP: [24.176.178.22]

    X-MS-Exchange-Organization-AVStamp-Mailbox: MSFTFF;1;0;0 0 0

    X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply

    X-EsetId: 1217D4224832343244518B

    • Not Ranked
    • Post Points: 0
  • Hi alNV,

    I have checked your two email headers, it shows the emails was sent by his own account.

    So I want to suggest something.

    1. Please check is this account given a send as permissions to others?
    2. Please change the password for this account.

    Thanks,

    Jason Jiang

    • Top 25 Contributor
    • Post Points: 0
    Suggested by
  • Hi alNV,

    I would like to follow up with the question you posted previously. How are things going?

    Thanks,

    Jason Jiang

    • Top 25 Contributor
    • Post Points: 0
  • Thanks for checking Jason. Currently we have given up on the situation and assume that it was just a glitch at that one moment. We will get back to the issue if it happens again.

    • Not Ranked
    • Post Points: 0
  • Hi alnv,

    If you have any other questions when using Office 365, please feel free to post in the forum. We are more than happy to be of assistance.

    Thanks,

    Jason Jiang

     

    • Top 25 Contributor
    • Post Points: 0
Page 1 of 1 (7 items)