此原始邮件有什么问题？

Question

最近，我打开了一个带有后缀的邮件服务器。经过大量配置和设置（例如DKIM和rDNS）后，不幸的是，收件箱中仍然阻止了向Gmail的外发邮件。（获取垃圾邮件）

现在我不知道接下来要做什么以增强信心。

这里是Gmail从我的邮件服务器收到的最新“原始邮件”。

Received-SPF: pass (google.com: domain of [email protected] designates 1.2.3.4 as permitted sender) client-ip=1.2.3.4;
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Thu, 24 Nov 2016 17:30:55 +0330
From: [email protected]
To: =?UTF-8?Q?=D8=B4=D8=A8=DA=A9=D9=87_=D9=87=D9=85=D8=B1=D8=A7=D9=87_?=
 =?UTF-8?Q?=D8=AF=D8=A7=D9=86=D8=B4?= <[email protected]>
Subject: DKIM algorithm with 2048 key
Message-ID: <[email protected]>
User-Agent: Roundcube Webmail/1.1.6

TEST

并发送到[email protected]对此报告做出了回应：

This message is an automatic response from Port25's authentication verifier
service at verifier.port25.com.  The service allows email senders to perform
a simple check of various sender authentication mechanisms.  It is provided
free of charge, in the hope that it is useful to the email community.  While
it is not officially supported, we welcome any feedback you may have at
<[email protected]>.

Thank you for using the verifier,

The Port25 Solutions, Inc. team

==========================================================
Summary of Results
==========================================================
SPF check:          pass
DomainKeys check:   neutral
DKIM check:         pass
DKIM check:         pass
SpamAssassin check: ham

==========================================================
Details:
==========================================================

HELO hostname:  mail.mydomain.tld
Source IP:      1.2.3.4
mail-from:      [email protected]

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result:         pass 
ID(s) verified: [email protected]
DNS record(s):
    mydomain.tld. SPF (no records)
    mydomain.tld. 14400 IN TXT "v=spf1 a mx ip4:1.2.3.100 ~all"
    mydomain.tld. 14400 IN A 1.2.3.100
    mydomain.tld. 14400 IN MX 10 mail.mydomain.tld.
    mail.mydomain.tld. 14400 IN A 1.2.3.4

----------------------------------------------------------
DomainKeys check details:
----------------------------------------------------------
Result:         neutral (message not signed)
ID(s) verified: [email protected]
DNS record(s):

----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result:         pass (matches From: [email protected])
ID(s) verified: header.d=mydomain.tld
Canonicalized Headers:
    date:Thu,'20'24'20'Nov'20'2016'20'13:33:53'20'+0330'0D''0A'
    from:[email protected]'0D''0A'
    to:[email protected]'0D''0A'
    subject:DKIM'20'algorithm'20'with'20'2048'20'key'0D''0A'
    in-reply-to:<[email protected]>'0D''0A'
    references:<[email protected]>'0D''0A'
    dkim-signature:v=1;'20'a=rsa-sha256;'20'c=relaxed/simple;'20'd=mydomain.tld;'20's=mail;'20't=1479981833;'20'bh=q5cyARPl5zX/knmvCnEy11G7/r6gcljJ44qrvv5DErY=;'20'h=Date:From:To:Subject:In-Reply-To:References:From;'20'b=

Canonicalized Body:
    TEST'0D''0A'


DNS record(s):
    mail._domainkey.mydomain.tld. 14400 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArPpOXRz6vYf19XExCZ528I7s3EOR4YJYdsq0w8QQhbd8coDXOTpoK8rdMhcgvX+X/fvP2R9uEBP7y2U53Y312CsP4vfrAFUIRvqP28PGeN55dpCtfN603xURrTp4ee0qPkdC3N3aVrbnHLgDOiFZcrncHAXkOc7H1dsMs6ARj+qLrRjyrj7+MyCw6R49exhC0bhoHTuglhd7zivVKytt/ySaUZANDKBKFhLWATBLAHS98PtYWVieTeSA2oDCn+IKgDD5RZYECNe0VXhbMh+hrbpcKfsmZWsCtx0PH+Aoe22idd241vkkp4MZqqwY8nsb0uYmCKZgcTB8teMgzz1bfwIDAQAB"

Public key used for verification: mail._domainkey.mydomain.tld (2048 bits)

NOTE: DKIM checking has been performed based on the latest DKIM specs
(RFC 4871 or draft-ietf-dkim-base-10) and verification may fail for
older versions.  If you are using Port25's PowerMTA, you need to use
version 3.2r11 or later to get a compatible version of DKIM.

----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result:         pass (matches From: [email protected])
ID(s) verified: header.d=mydomain.tld
Canonicalized Headers:
    date:Thu,'20'24'20'Nov'20'2016'20'13:33:53'20'+0330'0D''0A'
    from:[email protected]'0D''0A'
    to:[email protected]'0D''0A'
    subject:DKIM'20'algorithm'20'with'20'2048'20'key'0D''0A'
    in-reply-to:<[email protected]>'0D''0A'
    references:<[email protected]>'0D''0A'
    dkim-signature:v=1;'20'a=rsa-sha256;'20'c=relaxed/simple;'20'd=mydomain.tld;'20's=mail;'20't=1479981833;'20'bh=q5cyARPl5zX/knmvCnEy11G7/r6gcljJ44qrvv5DErY=;'20'h=Date:From:To:Subject:In-Reply-To:References:From;'20'b=

Canonicalized Body:
    TEST'0D''0A'


DNS record(s):
    mail._domainkey.mydomain.tld. 14400 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArPpOXRz6vYf19XExCZ528I7s3EOR4YJYdsq0w8QQhbd8coDXOTpoK8rdMhcgvX+X/fvP2R9uEBP7y2U53Y312CsP4vfrAFUIRvqP28PGeN55dpCtfN603xURrTp4ee0qPkdC3N3aVrbnHLgDOiFZcrncHAXkOc7H1dsMs6ARj+qLrRjyrj7+MyCw6R49exhC0bhoHTuglhd7zivVKytt/ySaUZANDKBKFhLWATBLAHS98PtYWVieTeSA2oDCn+IKgDD5RZYECNe0VXhbMh+hrbpcKfsmZWsCtx0PH+Aoe22idd241vkkp4MZqqwY8nsb0uYmCKZgcTB8teMgzz1bfwIDAQAB"

Public key used for verification: mail._domainkey.mydomain.tld (2048 bits)

NOTE: DKIM checking has been performed based on the latest DKIM specs
(RFC 4871 or draft-ietf-dkim-base-10) and verification may fail for
older versions.  If you are using Port25's PowerMTA, you need to use
version 3.2r11 or later to get a compatible version of DKIM.

----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.4.0 (2014-02-07)

Result:         ham  (-3.8 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
-0.0 SPF_PASS               SPF: sender matches SPF record
-2.9 RP_MATCHES_RCVD        Envelope sender domain matches handover relay domain
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                            [score: 0.0000]
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
                            domain
 0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
 1.1 BODY_SINGLE_WORD       Message body is only one word (no spaces)

==========================================================
Explanation of the possible results (from RFC 5451)
==========================================================

SPF and Sender-ID Results
=========================

"none"
      No policy records were published at the sender's DNS domain.

"neutral"
      The sender's ADMD has asserted that it cannot or does not
      want to assert whether or not the sending IP address is authorized
      to send mail using the sender's DNS domain.

"pass"
      The client is authorized by the sender's ADMD to inject or
      relay mail on behalf of the sender's DNS domain.

"policy"
     The client is authorized to inject or relay mail on behalf
      of the sender's DNS domain according to the authentication
      method's algorithm, but local policy dictates that the result is
      unacceptable.

"fail"
      This client is explicitly not authorized to inject or
      relay mail using the sender's DNS domain.

"softfail"
      The sender's ADMD believes the client was not authorized
      to inject or relay mail using the sender's DNS domain, but is
      unwilling to make a strong assertion to that effect.

"temperror"
      The message could not be verified due to some error that
      is likely transient in nature, such as a temporary inability to
      retrieve a policy record from DNS.  A later attempt may produce a
      final result.

"permerror"
      The message could not be verified due to some error that
      is unrecoverable, such as a required header field being absent or
      a syntax error in a retrieved DNS TXT record.  A later attempt is
      unlikely to produce a final result.


DKIM and DomainKeys Results
===========================

"none"
      The message was not signed.

"pass"
      The message was signed, the signature or signatures were
      acceptable to the verifier, and the signature(s) passed
      verification tests.

"fail"
      The message was signed and the signature or signatures were
      acceptable to the verifier, but they failed the verification
      test(s).

"policy"
      The message was signed but the signature or signatures were
      not acceptable to the verifier.

"neutral"
      The message was signed but the signature or signatures
      contained syntax errors or were not otherwise able to be
      processed.  This result SHOULD also be used for other
      failures not covered elsewhere in this list.

"temperror"
      The message could not be verified due to some error that
      is likely transient in nature, such as a temporary inability
      to retrieve a public key.  A later attempt may produce a
      final result.

"permerror"
      The message could not be verified due to some error that
      is unrecoverable, such as a required header field being
      absent. A later attempt is unlikely to produce a final result.


==========================================================
Original Email
==========================================================

Return-Path: <[email protected]>
Received: from mail.mydomain.tld (1.2.3.4) by verifier.port25.com id h6qtgq20i3gp for <[email protected]>; Thu, 24 Nov 2016 05:03:56 -0500 (envelope-from <[email protected]>)
Authentication-Results: verifier.port25.com; spf=pass [email protected]
Authentication-Results: verifier.port25.com; domainkeys=neutral (message not signed) [email protected]
Authentication-Results: verifier.port25.com; dkim=pass (matches From: [email protected]) header.d=mydomain.tld
Authentication-Results: verifier.port25.com; dkim=pass (matches From: [email protected]) header.d=mydomain.tld
Received: from mail.mydomain.tld (localhost [127.0.0.1])
    by mail.mydomain.tld (Postfix) with ESMTP id C4A449FA85
    for <[email protected]>; Thu, 24 Nov 2016 13:33:53 +0330 (IRST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mydomain.tld;
    s=mail; t=1479981833;
    bh=q5cyARPl5zX/knmvCnEy11G7/r6gcljJ44qrvv5DErY=;
    h=Date:From:To:Subject:In-Reply-To:References:From;
    b=kbHJbY6k1nmQ0KmNL1ZsqQ9YP31Xdv3sfqzqJTriHrtiIO06Z4hHCsFYbrHTHL579
     tsVcPhAxLA4vxnZgASlQpYOhuJvUDe3C4EtPAjUA+9Tof1wbSeqWYFnHDHvRz4bbkP
     YKfg582YsITfw6ENEua0xKgw+ogFknWKLyeXfJXCxidO7MuNBgIWJdhYajTUmr/+WY
     yVg6D6StgiJl6tNS0U2C1qghvI/HF9wxan6+Uy8B4iTmuErzBCGly+hCbbdcl/MQOA
     sLAzh/HbsnxuOJj37QLPIpj5+dblKpAhmmR+jIQD8sAU2dCi6PvSAsYq8eOd4sgnB4
     +s9FmHfDamEJg==
Received: from inbox.mydomain.tld (localhost [127.0.0.1])
    (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
    (No client certificate requested)
    by mail.mydomain.tld (Postfix) with ESMTPSA id 9D4589F9B8
    for <[email protected]>; Thu, 24 Nov 2016 13:33:53 +0330 (IRST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mydomain.tld;
    s=mail; t=1479981833;
    bh=q5cyARPl5zX/knmvCnEy11G7/r6gcljJ44qrvv5DErY=;
    h=Date:From:To:Subject:In-Reply-To:References:From;
    b=kbHJbY6k1nmQ0KmNL1ZsqQ9YP31Xdv3sfqzqJTriHrtiIO06Z4hHCsFYbrHTHL579
     tsVcPhAxLA4vxnZgASlQpYOhuJvUDe3C4EtPAjUA+9Tof1wbSeqWYFnHDHvRz4bbkP
     YKfg582YsITfw6ENEua0xKgw+ogFknWKLyeXfJXCxidO7MuNBgIWJdhYajTUmr/+WY
     yVg6D6StgiJl6tNS0U2C1qghvI/HF9wxan6+Uy8B4iTmuErzBCGly+hCbbdcl/MQOA
     sLAzh/HbsnxuOJj37QLPIpj5+dblKpAhmmR+jIQD8sAU2dCi6PvSAsYq8eOd4sgnB4
     +s9FmHfDamEJg==
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Thu, 24 Nov 2016 13:33:53 +0330
From: [email protected]
To: [email protected]
Subject: DKIM algorithm with 2048 key
In-Reply-To: <[email protected]>
References: <[email protected]>
Message-ID: <[email protected]>
X-Sender: [email protected]
User-Agent: Roundcube Webmail/1.1.6
X-AV-Checked: ClamAV using ClamSMTP

TEST

您能帮我吗？谢谢

Answer 1

对于对此感到兴奋的人，大约2个月后，我的问题得到解决，而我没有采取任何措施。因此，我可以猜到这与我的域名信誉有关。如果您有同样的问题，建议您稍等片刻。另外，您可以将一些消息从新配置的服务器发送到您认识并信任的某些收件人。要求他们将此电子邮件地址添加到他们的联系人中。它会为您的服务器授予一定的权限，并可能使过程更快。祝你好运

此原始邮件有什么问题？

问题描述投票：0回答：1

1个回答

最新问题

此原始邮件有什么问题？

问题描述 投票：0回答：1

1个回答

最新问题

问题描述投票：0回答：1