socket 域名发送_如何使用其他人的域名发送电子邮件？

socket 域名发送

Being able to send out e-mail using your own domain name can be very nice, but what do you do when someone starts spewing out spam mail using your domain name? Today’s SuperUser Q&A post discusses the matter to help a frustrated reader.

能够使用您自己的域名发送电子邮件非常好，但是当有人开始使用您的域名发出垃圾邮件时您会怎么做？ 今天的超级用户问答环节讨论了此问题，以帮助沮丧的读者。

Today’s Question & Answer session comes to us courtesy of SuperUser—a subdivision of Stack Exchange, a community-driven grouping of Q&A web sites.

今天的“问答”环节由SuperUser提供，它是Stack Exchange的一个分支，该社区是由社区驱动的Q＆A网站分组。

Photo courtesy of Maria Elena (Flickr).

照片由Maria Elena(Flickr)提供 。

问题 (The Question)

SuperUser reader Jake M wants to know how someone has been able to send out e-mail using their personal domain:

超级用户阅读器Jake M想知道某人如何能够使用其个人域发送电子邮件：

Spammers or someone similar is sending e-mails to people using our domain name.

垃圾邮件发送者或类似的人正在使用我们的域名向人们发送电子邮件。

• The e-mails are from a user we did not create called: regeniaberry67a@ourdomain.com.au.

  这些电子邮件来自我们没有创建的用户： regeniaberry67a@ourdomain.com.au 。

• The e-mail is to: regeniaberry@ubtanet.com.

  电子邮件至： regeniaberry@ubtanet.com 。

• The content of the e-mail talks about a stock that is six cents but will go to fifteen cents and that people should buy it. It contains a link to Yahoo’s finance website, but I will not click it, so I am not sure if it is legitimate. We know of the e-mails because we get bounce-backs (the recipient must not exist).
  电子邮件的内容谈论的是六美分的股票，但涨到了十五美分，人们应该购买它。 它包含指向Yahoo财务网站的链接，但是我不会单击它，因此我不确定它是否合法。 我们之所以知道电子邮件，是因为我们收到了退信(收件人必须不存在)。

What would allow someone (or a bot) to send an e-mail under our domain name? Is there anything we can do to stop this? Is this Dictionary Spamming?

什么使某人(或机器人)可以使用我们的域名发送电子邮件？ 有什么我们可以阻止的吗？ 该词典是垃圾邮件吗？

How is someone doing this and is there anything that can be done to mitigate the situation?

某人如何做到这一点，有什么办法可以减轻这种情况？

答案 (The Answer)

SuperUser contributors Paul and AFH have the answer for us. First up, Paul:

超级用户贡献者Paul和AFH为我们提供了答案。 首先，保罗：

The SMTP protocol does not include any controls over the From and To fields in an e-mail. They can be whatever you like provided you have authority to send e-mails using the SMTP server.

SMTP协议不包含对电子邮件中“ 发件人”和“ 收件人”字段的任何控制。 只要您有权使用SMTP服务器发送电子邮件，它们就可以是您喜欢的任何内容。

So the short answer is nothing prevents anyone from using your domain in e-mails they send. Even normal users can put whatever e-mail address they like in their e-mail settings.

因此，简短的答案是没有什么可以阻止任何人在他们发送的电子邮件中使用您的域的。 即使是普通用户，也可以在他们的电子邮件设置中放入他们喜欢的任何电子邮件地址。

Spammers routinely use valid domain names as From addresses to avoid being blocked.

垃圾邮件发送者通常将有效域名用作发件人地址，以避免被阻止。

While you cannot stop someone from sending e-mails with your domain name, you can help e-mail servers around the world understand if e-mails sent from your domain name actually originated from you and are legitimate e-mails, so that any others can be discarded as spam.

虽然您无法阻止某人发送带有您的域名的电子邮件，但是您可以帮助世界各地的电子邮件服务器了解从您的域名发送的电子邮件是否实际上是您发的，并且是合法电子邮件，以便其他任何人可以作为垃圾邮件丢弃。

SPF

SPF

One way is to use SPF. This is a record that goes into DNS and lets the Internet know what servers are permitted to send e-mails on behalf of your domain. It looks like this:

一种方法是使用SPF。 这是进入DNS的记录，它使Internet知道允许哪些服务器代表您的域发送电子邮件。 看起来像这样：

• ourdomain.com.au.  IN TXT “v=spf1 mx ip4:123.123.123.123 -all”
  ourdomain.com.au。 在TXT中“ v = spf1 mx ip4：123.123.123.123 -all”

This says that the only valid sources of e-mail for ourdomain.com.au are the MX servers – the server defined as the recipient of e-mails for the domain, and another server at 123.123.123.123. E-mail from any other server should be considered spam.

也就是说，ourdomain.com.au的唯一有效电子邮件来源是MX服务器-定义为域电子邮件接收者的服务器，以及另一个服务器123.123.123.123。 来自任何其他服务器的电子邮件都应视为垃圾邮件。

Most e-mail servers will check for the presence of this DNS record and act accordingly.

大多数电子邮件服务器将检查此DNS记录的存在并采取相应措施。

DKIM

DKIM

While SPF is easy to set up, DKIM takes a little more effort and should be implemented by your e-mail server administrator. If you send your e-mail via an ISP e-mail server, they will often have methods for quick setup of DKIM.

尽管SPF易于设置，但DKIM会花费更多的精力，并且应由您的电子邮件服务器管理员来实施。 如果您通过ISP电子邮件服务器发送电子邮件，则它们通常会提供快速设置DKIM的方法。

DKIM works similarly to SSL certificates. A public/private key pair is generated. The private key is known only to the e-mail server, and it will sign any outgoing e-mails.

DKIM的工作方式类似于SSL证书。 生成公用/专用密钥对。 专用密钥仅对于电子邮件服务器是已知的，并且它将对所有外发电子邮件进行签名。

The public key is published using DNS. So any server receiving e-mails marked as coming from your domain can check that the e-mail was signed by retrieving the public key and checking the signature in the e-mails. If no signature is present, or it is incorrect, the e-mail can be considered spam.

公钥使用DNS发布。 因此，任何接收到标记为来自您的域的电子邮件的服务器都可以通过检索公钥并检查电子邮件中的签名来检查电子邮件是否已签名。 如果没有签名，或者签名不正确，则可以将电子邮件视为垃圾邮件。

Followed by the answer from AFH:

随后是AFH的回答：

An e-mail can contain any Reply-To address you choose. Some e-mail servers will send undeliverable notifications back to the Reply-To address rather than the originator. Online mail handlers like Gmail require you to validate any Reply-To address you use when composing online, but there is no such restriction when using a remote client with POP3/IMAP. And if you run your own e-mail server, you can probably also fake the From address.

电子邮件可以包含您选择的任何“ 回复”地址。 某些电子邮件服务器会将无法投递的通知发送回答复地址而不是发件人。 像Gmail这样的在线邮件处理程序要求您验证在进行在线撰写时使用的任何“ 回复”地址，但是在将远程客户端与POP3 / IMAP一起使用时没有这种限制。 而且，如果您运行自己的电子邮件服务器，则可能还可以伪造“ 发件人”地址。

Have something to add to the explanation? Sound off in the comments. Want to read more answers from other tech-savvy Stack Exchange users? Check out the full discussion thread here.

有什么补充说明吗？ 在评论中听起来不错。 是否想从其他精通Stack Exchange的用户那里获得更多答案？ 在此处查看完整的讨论线程 。

翻译自: https://www.howtogeek.com/199704/how-is-it-possible-to-send-e-mail-using-someone-elses-domain-name/

socket 域名发送