电子邮件标头中包含敏感信息？

发布于 2024-10-20 12:03:26 字数 171 浏览 7 评论 0原文

如果删除了“收件人：电子邮件”，电子邮件标头中是否存在任何敏感信息？

我问这个问题的原因是因为我正在启动一个项目（像许多其他项目一样）来记录收到的垃圾邮件。我计划发布标题（删除我的电子邮件和姓名）。

所以我想知道是否有垃圾邮件发送者（或其他任何人）可以根据标题内容检索私人信息

？

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

慕烟庭风 2024-10-27 12:03:26

嗯，有路由路径 - Received 标头显示哪些服务器中继了它，以及它们的 IP 地址。如果您担心在那里暴露 DNS 名称和 IP 地址，您可能需要将其删除。还有 Message-ID，它在源服务器上应该是唯一的，但在这种情况下并不真正相关：

Delivered-To: [email protected]
Received: by 10.150.52.9 with SMTP id z9cs167242ybz; Wed, 2 Mar 2011
 01:23:55 -0800 (PST)
Received: by 10.204.123.144 with SMTP id p16mr7228369bkr.25.1299057834954;
 Wed, 02 Mar 2011 01:23:54 -0800 (PST)
Return-Path: <[email protected]>
Received: from www.example.org (www.example.org [127.25.43.2]) by
 mx.example.com with SMTP id b20si16526479bkb.8.2011.03.02.01.23.53; Wed, 02
 Mar 2011 01:23:53 -0800 (PST)
Received-SPF: unknown (example.com: domain of [email protected] uses a
 mechanism not recognized by this client. unknown  mechanisms: ))
 client-ip=89.250.243.218;
Authentication-Results: mx.example.com; spf=permerror (example.com: domain of
 [email protected] uses a mechanism not recognized by this client. unknown
  mechanisms: )) [email protected]
Received: (qmail 16028 invoked from network); 2 Mar 2011 10:23:57 +0100
Received: from unknown (HELO localhost) (127.0.0.1) by localhost with SMTP;
 2 Mar 2011 10:23:57 +0100
X-Mailer: [redacted] v3.0
X-Priority: 3
MIME-Version: 1.0
Date: Wed, 02 Mar 2011 10:23:57 +0100
Subject: [redacted]
Content-Type: multipart/alternative; boundary="=_932aa962c78a5f164be3066dcfdce0e7"
From: "[email protected]" <[email protected]>
Reply-To: [email protected]
Message-ID: <[email protected]>
To: [email protected]

因此，最相关的部分将是路由数据 - 除非您使用托管服务您可以隐藏在人群中（例如gMail），这可以用来猜测收件人的域名。

Well, there's the routing path - the Received headers show which servers relayed it, together with their IP addresses. If you are worried about exposing DNS names and IP addresses there, you may want to remove them. There's also Message-ID, which should be unique at the origin server, but that is not really relevant in this case:

Delivered-To: [email protected]
Received: by 10.150.52.9 with SMTP id z9cs167242ybz; Wed, 2 Mar 2011
 01:23:55 -0800 (PST)
Received: by 10.204.123.144 with SMTP id p16mr7228369bkr.25.1299057834954;
 Wed, 02 Mar 2011 01:23:54 -0800 (PST)
Return-Path: <[email protected]>
Received: from www.example.org (www.example.org [127.25.43.2]) by
 mx.example.com with SMTP id b20si16526479bkb.8.2011.03.02.01.23.53; Wed, 02
 Mar 2011 01:23:53 -0800 (PST)
Received-SPF: unknown (example.com: domain of [email protected] uses a
 mechanism not recognized by this client. unknown  mechanisms: ))
 client-ip=89.250.243.218;
Authentication-Results: mx.example.com; spf=permerror (example.com: domain of
 [email protected] uses a mechanism not recognized by this client. unknown
  mechanisms: )) [email protected]
Received: (qmail 16028 invoked from network); 2 Mar 2011 10:23:57 +0100
Received: from unknown (HELO localhost) (127.0.0.1) by localhost with SMTP;
 2 Mar 2011 10:23:57 +0100
X-Mailer: [redacted] v3.0
X-Priority: 3
MIME-Version: 1.0
Date: Wed, 02 Mar 2011 10:23:57 +0100
Subject: [redacted]
Content-Type: multipart/alternative; boundary="=_932aa962c78a5f164be3066dcfdce0e7"
From: "[email protected]" <[email protected]>
Reply-To: [email protected]
Message-ID: <[email protected]>
To: [email protected]

So, the most relevant part would be the routing data - unless you use a hosted service where you can hide in the crowd (e.g. gMail), this could be used to guess the domain of the recipient.

回复收藏 0 原文

~没有更多了~