Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Importing edited Mbox file from Gmail - Manipulation test

  • 1 답장
  • 1 이 문제를 만남
  • 3 보기
  • 최종 답변자: Matt

more options

I am testing the theory behind manipulated emails and what forensic evidence can be obtained.

I notice that when Google Takeout is used to export emails from a Gmail account and are subsequently edited (in this case, the body text), SPF alters from "PASS" to "NONE with IP 0.0.0.0" and DKIM completely disappears in the "Original Message" view, however the headers remain unchanged with the exception of the edits to the body text.

The unedited email indicates SPF as "Pass" and DKIM as "Pass" (first image). This changes in the second image once any alteration is applied to the original email.

Before importing the email via Thunderbird, I delete the original email in Gmail (including the trash) and then load the manipulated email to Thunderbird and subsequently to the Gmail inbox.

Is there an explanation for the change in SPF and disappearance of DKIM to the manipulated email?

I am testing the theory behind manipulated emails and what forensic evidence can be obtained. I notice that when Google Takeout is used to export emails from a Gmail account and are subsequently edited (in this case, the body text), SPF alters from "PASS" to "NONE with IP 0.0.0.0" and DKIM completely disappears in the "Original Message" view, however the headers remain unchanged with the exception of the edits to the body text. The unedited email indicates SPF as "Pass" and DKIM as "Pass" (first image). This changes in the second image once any alteration is applied to the original email. Before importing the email via Thunderbird, I delete the original email in Gmail (including the trash) and then load the manipulated email to Thunderbird and subsequently to the Gmail inbox. Is there an explanation for the change in SPF and disappearance of DKIM to the manipulated email?
첨부된 스크린샷

모든 댓글 (1)

more options

Details on the SPF standard can be found here. https://datatracker.ietf.org/doc/html/rfc7208 and DKIM here https://datatracker.ietf.org/doc/html/rfc6376

Both of these are server side technologies and well beyond the scope of this forum.