DKIM hmailserver 및 NameCheap Setup

DKIM을 사용하여 hmailserver를 설정하려고했습니다. >https://www.hmailserver.com/forum/viewtopic.php?t=29402 DKIM hmailserver 및 NameCheap Setup

을 그리고이 사이트 내 키를 생성 - -

나는이 가이드를 따라했다>https://www.port25.com/dkim-wizard/

도메인 이름 :

DomainKey 선택기 linnabary.us : DKIM

키 크기 : 1024

pem 파일을 만들었습니다.

-----BEGIN RSA PRIVATE KEY----- 
<key> 
-----END RSA PRIVATE KEY-----

그것을 저장된 내가 NameCheap에서이 작업을 설정할 때 나는, TXT 레코드를 선택 @ 나의 호스트를 설정하고이 라인을 넣어, 마이너스 hmailserver

로로드 물론 키;

v=DKIM1; k=rsa; p=<KEY>

지금은 함께 테스트 할 때 ->http://www.isnotspam.com

그것은 다음과 같이 내 DKIM 키를 말한다;

---------------------------------------------------------- 
DKIM check details: 
---------------------------------------------------------- 

Result: invalid 
ID(s) verified: [email protected] 
Selector= 
domain= 
DomainKeys DNS Record=._domainkey.

제 기록에 명백한 오류가 있는지 궁금합니다.

편집;

이메일에 다음과 같은 내용이 포함되어 있습니다.

dkim-signature: v=1; a=rsa-sha256; d=linnabary.us; s=dkim;

다음은 NameCheap에서의 설정과 같습니다.

그리고 여기가에서 다음 테스트 이메일입니다; 당신의 TXT 항목에 대한

This message is an automatic response from isNOTspam's authentication verifier service. 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 . 

Thank you for using isNOTspam. 

The isNOTspam team 

========================================================== 
Summary of Results 
========================================================== 

SPF Check : pass 
Sender-ID Check : pass 
DKIM Check : invalid 
SpamAssassin Check : ham (non-spam) 
========================================================== 
Details: 
========================================================== 

HELO hostname: [69.61.241.46] 
Source IP: 69.61.241.46 
mail-from: [email protected] 
Anonymous To: [email protected] 
--------------------------------------------------------- 
SPF check details: 
---------------------------------------------------------- 

Result: pass 
ID(s) verified: [email protected] 
DNS record(s): 
linnabary.us. 1799 IN TXT "v=spf1 a mx ip4:69.61.241.46 ~all" 


---------------------------------------------------------- 
Sender-ID check details: 
---------------------------------------------------------- 

Result: pass 

ID(s) verified: [email protected] 
DNS record(s): 
linnabary.us. 1799 IN TXT "v=spf1 a mx ip4:69.61.241.46 ~all" 


---------------------------------------------------------- 
DKIM check details: 
---------------------------------------------------------- 

Result: invalid 
ID(s) verified: [email protected] 
Selector= 
domain= 
DomainKeys DNS Record=._domainkey. 

---------------------------------------------------------- 
SpamAssassin check details: 
---------------------------------------------------------- 
SpamAssassin 3.4.1 (2015-04-28) 

Result: ham (non-spam) (04.6points, 10.0 required) 

pts rule name description 
---- ---------------------- ------------------------------- 


* 3.5 BAYES_99 BODY: Bayes spam probability is 99 to 100% 
* [score: 1.0000] 
* -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 
* -0.0 SPF_PASS SPF: sender matches SPF record 
* 0.2 BAYES_999 BODY: Bayes spam probability is 99.9 to 100% 
* [score: 1.0000] 
* 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily 
* valid 
* 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS 
* 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 
X-Spam-Status: Yes, hits=4.6 required=-20.0 tests=BAYES_99,BAYES_999, 
DKIM_SIGNED,RDNS_NONE,SPF_HELO_PASS,SPF_PASS,T_DKIM_INVALID autolearn=no 
autolearn_force=no version=3.4.0 
X-Spam-Score: 4.6 

To learn more about the terms used in the SpamAssassin report, please search 
here: http://wiki.apache.org/spamassassin/ 

========================================================== 
Explanation of the possible results (adapted from 
draft-kucherawy-sender-auth-header-04.txt): 
========================================================== 

"pass" 
the message passed the authentication test. 

"fail" 
the message failed the authentication test. 

"softfail" 
the message failed the authentication test, and the authentication 
method has either an explicit or implicit policy which doesn't require 
successful authentication of all messages from that domain. 

"neutral" 
the authentication method completed without errors, but was unable 
to reach either a positive or a negative result about the message. 

"temperror" 
a temporary (recoverable) error occurred attempting to authenticate 
the sender; either the process couldn't be completed locally, or 
there was a temporary failure retrieving data required for the 
authentication. A later retry may produce a more final result. 

"permerror" 
a permanent (unrecoverable) error occurred attempting to 
authenticate the sender; either the process couldn't be completed 
locally, or there was a permanent failure retrieving data required 
for the authentication. 


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

From [email protected] Wed Apr 12 17:41:22 2017 
Return-path: <[email protected]> 
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on isnotspam.com 
X-Spam-Flag: YES 
X-Spam-Level: **** 
X-Spam-Report: 
* 3.5 BAYES_99 BODY: Bayes spam probability is 99 to 100% 
* [score: 1.0000] 
* -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 
* -0.0 SPF_PASS SPF: sender matches SPF record 
* 0.2 BAYES_999 BODY: Bayes spam probability is 99.9 to 100% 
* [score: 1.0000] 
* 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily 
* valid 
* 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS 
* 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 
X-Spam-Status: Yes, hits=4.6 required=-20.0 tests=BAYES_99,BAYES_999, 
DKIM_SIGNED,RDNS_NONE,SPF_HELO_PASS,SPF_PASS,T_DKIM_INVALID autolearn=no 
autolearn_force=no version=3.4.0 
Envelope-to: [email protected] 
Delivery-date: Wed, 12 Apr 2017 17:41:22 +0000 
Received: from [69.61.241.46] (helo=linnabary.us) 
by localhost.localdomain with esmtp (Exim 4.84_2) 
(envelope-from <[email protected]>) 
id 1cyMGg-0007x2-1Q 
for [email protected]; Wed, 12 Apr 2017 17:41:22 +0000 
dkim-signature: v=1; a=rsa-sha256; d=linnabary.us; s=dkim; 
c=relaxed/relaxed; q=dns/txt; h=From:Subject:Date:Message-ID:To:MIME-Version:Content-Type:Content-Transfer-Encoding; 
bh=Ns4aRUgWUtil4fiVnvitgeV+q1K/smEYtRGN497S5Ew=; 
b=Nc2Kzrzas0QqMpWM4fnF5o5wLWlWYFxlGlAipe+85H9cwGgc4hvEKUj1UvgB6I2VHUbJ0OGN/sJO9tjWgwlGypaUuW7Q8x/iI0UtC6cn7X6ZLHT+K6A2A6MdoyR1NF4xxvqPadcmcQwnrY0Tth4ycydpQMlBCZS30sc1qUjUrN0= 
Received: from [192.168.1.12] (Aurora [192.168.1.12]) 
by linnabary.us with ESMTPA 
; Wed, 12 Apr 2017 13:41:28 -0400 
To: [email protected] 
From: Admin <[email protected]> 
Subject: Welcome to Linnabary 
Message-ID: <[email protected]> 
Date: Wed, 12 Apr 2017 13:41:28 -0400 
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 
Thunderbird/45.8.0 
MIME-Version: 1.0 
Content-Type: text/plain; charset=utf-8; format=flowed 
Content-Transfer-Encoding: 7bit 
X-DKIM-Status: invalid (pubkey_unavailable) 
I honestly have no idea what I should put in here in order to protect 
myself from filters, so I'm just making it up as I go. 

- Tad

출처

2017-04-12 Kayot

'dkim._domainkey.linnabary.us'에 대한 TXT 레코드를 볼 수 없습니다. 테스트 이메일의 서명은 어떻게 보이나요? 올바른 도메인 ('d = linnabary.us')과 선택자 ('s = dkim')가 포함되어 있습니까? 또한 ** 비밀 키 생성을 위해 온라인 도구를 사용하지 마십시오 **! 'openssl' 또는 유사하게 사용하여 컴퓨터에서 생성하십시오. 링크 된 사이트가 POST 요청의 응답으로 공개/개인 키 쌍을 보냅니다. 그들이 그것을 저장하지 않는다고해도, 실제로는 그렇지 않은 wheather를 확인할 방법이 없으므로, 열쇠를 얻었을 때 이미 손상된 것으로 간주되어야합니다. – mata

호스트 값은 dkim._domainkey해야한다. 현재 도메인 키는 dkim._domainkey.linnabary.us.linnabary.us에 있으므로 여기에 도메인을 추가하지 않아도됩니다.

그런 이유로 테스트 전자 메일에 대한 응답으로 X-DKIM-Status: invalid (pubkey_unavailable) - 공개 키를 발견 할 수 없습니다.

출처

2017-04-12 18:31:08 mata

그게 문제였습니다. 이제 모든 것이 작동합니다. – Kayot

답변

관련 문제