Domain and “From” Address Considerations(关于域名和发信邮箱)

英文原文:

   Think carefully about the addresses you send your email from. The “From” address will not only be visible to recipients in their email client (including in the preview pane), but will also collect reputation at some ISPs. This, along with the Subject line, will create the first impression a recipient will have of your email.

Think carefully about the domain of the address(es) from which you send your email. There are two reasons for this:

  • ISPs garner reputation across all email sent from a domain, regardless of how you’ve split up your mailings
  • Recipients need to be able to recognize your domain. Don’t collect an email address from a web form hosted at www.example-foo.com and then send an email from sender@example-bar.com. You will lose recognition and drive recipients to the spam button this way

   If you’re sending significant volumes of email, don’t send email from an ISP-based email address such as sender@hotmail.com. For example, if Yahoo! notices a significant volume of inbound messages coming from sender@hotmail.com, that email will be treated differently than if it were coming from a proper outbound email-sending domain (i.e., a domain that you own).

   Include correct WHOIS information for your domain so that receivers can look up details about who owns your sending domain. Your domain registrar will provide instructions about how to set up your WHOIS record. Receivers trust more established and transparent domains that are fully listed with the Internet registry over domains that are not.

译文:

   要非常注意发信邮箱地址,不仅收信人可以看到,邮件服务商也会查看邮箱的信用度。邮件标题行会给收信人第一印象。

   要非常注意邮箱地址所在的域名,这有两方面原因:

  • 不论你怎样分割邮件列表用多个发信人发信,只要是同一个域名,收信邮局都会收集并评判信用度。
  • 不要从网上注册很多邮箱,用不相关域名下的邮箱发信,这样收件人看到以后不会信任您的邮件,并且很容易让收件人点这是一封垃圾邮件。

   如果你要发送重要的邮件,尽量不要使用网上免费的邮箱,比如你用sender@hotmail.com给一个客户邮箱(yahoo邮箱)发送重要的邮件,客户标示为重要邮件,但是以后如果您从您的域名下的邮箱再发邮件,那yahoo会认为是不同来源的邮件。

   在域名的WHOIS记录上添加上详细信息,收信方会查看发送人的域名信息。你的域名注册商通常会提供怎样设置WHOIS记录。这样会建立更好的信用度。

Authentication(身份认证)

英文原文:

   Make sure that your domain is authenticated with Sender Policy Framework (SPF) and SenderID. These authentication methods lend credibility to your sending domain by confirming to email recipients that an email is actually from the domain it claims to be from. For more information, see Authenticating Your Email Address in the Amazon Simple Email Service Developer Guide. Test your authentication settings by sending email to an ISP inbox that you own (e.g., a Gmail account), and viewing the headers in the source of the message. The headers will tell you whether your authentication attempts have succeeded.

   You should also use DomainKeys or DomainKeys Identified Mail (DKIM) to sign your outbound email. This authentication step will lend credibility to your email by confirming to recipients that the content has not been changed in transit from sender to receiver. For a brief explanation of the difference between SPF and DKIM, go to the Wikipedia article, Email authentication. Test your authentication settings by sending email to an ISP inbox that you own (e.g., a Gmail account), and viewing the headers in the source of the message. The headers will tell you whether your authentication attempt succeeded.

译文:

   确保给您的域名加上了SPF认证机制,SPF人证可以确保邮件是从被认证的域名发出的邮件,从而增加邮件的信用度。更详细的信息请查阅《amazon ses 开发指南》。您可以通过向一些邮件服务商的邮箱发送邮件(例如gmail),然后查看邮件消息头部分,这样就可以查看认证设置是否成功。

   您应该给发出的邮件设好DKIM身份认证。DKIM可以确保邮件内容在传输过程中没有被修改,这样可以增加邮件的信用度。关于SPF和DKIM的区别,可以查阅Wikipedia百科上的关于邮件认证的文章。您可以通过向一些邮件服务商的邮箱发送邮件(例如gmail),然后查看邮件消息头部分,这样就可以查看认证设置是否成功。

Building and Maintaining Your List(创建和维护邮件列表)

英文原文:

  Be careful how you collect email addresses. Many times in online forms or other sign-ups, people will provide bogus email addresses that, when you send email to them, will generate hard bounces and appear to the ISP as irresponsible sending.

  If your form continues to collect addresses that are hard bouncing on their first email attempt, ensure that the recipient confirms the address they’re entering. Present the address for confirmation, require duplicate fields for email address to ensure entries match, and disable client-side auto-fill if possible.

  You can utilize double opt-in (only sending email to an address whose owner has clicked on a verification link) to ensure that you don’t repeatedly send email to a bad address.

  You can use third-party vendors to check the viability of an email address before you send to it.

  You can also check the syntax of an email address to ensure that the address is at least reasonably correct (e.g., is the address composed correctly with a local part and @ symbol? Does the address resolve to a domain with an MX record?).

  You should be careful about allowing any user-defined input to be passed along to Amazon SES and the ISPs unchecked. Forums and form submissions can be especially tricky since the content can be completely user-generated (and spammers can fill out forms with their content), but email receivers don’t care – it’s your responsibility to ensure that you’re only sending email with high-quality content.

  It is highly unlikely you’ll ever have a standard alias (such as postmaster@, abuse@, or noc@) sign up for your email intentionally. You should have control over how you acquire email addresses, and only send email to addresses that belong to a real person who wants your email. This applies especially with role accounts, which are usually reserved for email watchdogs. Role accounts can be maliciously added to your list as a form of Internet sabotage to get you blocked. Ensure that your list does not include any role account aliases. For a complete list of role accounts you should watch out for, see Mailbox Names for Common Services, Roles and Functions.

  Don’t send email to third-party lists (purchased, rented, or otherwise collected outside of your purview). When you send email to a third-party list, you’re taking the risk of emailing addresses of an unknown origin. This could invite enforcement from ISPs if it turns out that the list contains spamtraps (special addresses set up by ISPs to monitor unsolicited email), bouncing addresses, or recipients who complain. Even if the email addresses on the third-party list are valid, you still don’t know whether the recipients will actually want your email and thus whether they will consider it spam. You should collect the email addresses yourself, directly from recipients.

译文:

小心收集邮件地址,从在线论坛或者其他认证的方式收集时,很多用户提供的都是虚假的邮件地址,当你给这个列表发送邮件的时候,会产生很多硬反弹,这样邮件服务商就会认为你在不负责任的乱发邮件。

当你让用户以提交表单的方式收集邮件地址的时候,输入错误要有提示,确保用户输入正确。或者让用户输入两次,去掉复制粘贴功能。

您可以通过给客户发一个确认信,邮件内容中包含一个确认链接,当用户点击邮件内链接的时候,您就可以去人这个邮件地址真实的存在。

您可以在发送邮件前,使用第三方的程序来验证邮件地址列表。

您也可以通过程序检查邮件地址格式的语法是否正确,还可以检查邮件地址域名的mx记录是否能正确解析。

要非常小心用户级功能直接通过amazon ses发送邮件,比如论坛中以提交表单地方式发送邮件,这些内容是不受控制的(垃圾邮件发送者可能会利用这一点),但是收信人是不关心这些的,发送高质量的邮件是您的责任。

在一些商业邮件系统,您不太可能能注册到一些重要的别名邮箱(如 postmaster@, abuse@, or noc@),所以您在获取邮件地址列表的时候,也应该去掉这些不太可能注册到的邮箱地址,这些特别的邮箱地址一般是商业邮局内部的邮箱地址,一般是作为监测的邮件地址。有些人可能会恶意给您提交这些地址,当您发送到这些邮件地址的时候,就会被商业邮局屏蔽掉您的邮件列表。所以您要检测您的邮件列表,确认不包括这些公共的服务、角色、功能类的邮箱地址。

不要发送从第三方获得的邮件地址列表(如购买的,租用的或者其他不是自己控制的方式内得到的)。当你发送第三方获取的邮件列表,您将冒着未知邮件地址来源的风险。 其中可能会包含商业邮局故意设置的陷阱邮件(邮局监测谁在发送垃圾邮件)、空地址反弹邮件或者用户投诉邮件。更有甚者,如果邮件列表不是正当获得的,你也就不知道是否收件人想接收您的邮件,因此收件人会认为是垃圾邮件。您应该自己从收件人那里直接获得邮件列表。

邮件群发软件 亚云邮件系统