DKIM hmailserver和NameCheap Setup(DKIM hmailserver and NameCheap Setup)
我一直在尝试用DKIM设置我的hmailserver。
我按照本指南 - > https://www.hmailserver.com/forum/viewtopic.php?t=29402
我用这个网站创建了我的密钥 - > https://www.port25.com/dkim-wizard/
域名：linnabary.us
DomainKey选择器：dkim
密钥大小：1024
我创建了一个pem文件;
-----BEGIN RSA PRIVATE KEY----- <key> -----END RSA PRIVATE KEY-----保存并将其加载到hmailserver中
当我在NameCheap上进行设置时，我选择了TXT Record，将我的主机设置为@，并将此行放入，当然是减去键;
v=DKIM1; k=rsa; p=<KEY>现在我用 - > http://www.isnotspam.com进行测试
它说我的DKIM键如下;
---------------------------------------------------------- DKIM check details: ---------------------------------------------------------- Result: invalid ID(s) verified: header.From=admin@linnabary.us Selector= domain= DomainKeys DNS Record=._domainkey.我想知道我的记录中是否有任何明显的错误。
编辑;
该电子邮件包含以下行;
dkim-signature: v=1; a=rsa-sha256; d=linnabary.us; s=dkim;这就是NameCheap上的设置;
这是下一个测试电子邮件;
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: admin@linnabary.us Anonymous To: ins-a64wsfm3@isnotspam.com --------------------------------------------------------- SPF check details: ---------------------------------------------------------- Result: pass ID(s) verified: smtp.mail=admin@linnabary.us 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: smtp.mail=admin@linnabary.us 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: header.From=admin@linnabary.us 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 admin@linnabary.us Wed Apr 12 17:41:22 2017 Return-path: <admin@linnabary.us> 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: ins-a64wsfm3@isnotspam.com 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 <admin@linnabary.us>) id 1cyMGg-0007x2-1Q for ins-a64wsfm3@isnotspam.com; 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: ins-a64wsfm3@isnotspam.com From: Admin <admin@linnabary.us> Subject: Welcome to Linnabary Message-ID: <8e8be6cd-6354-aeb9-b577-2b0efc25a1a1@linnabary.us> 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. - TadI've been trying to setup my hmailserver with DKIM.
I was following this guide -> https://www.hmailserver.com/forum/viewtopic.php?t=29402
And I created my keys with this site -> https://www.port25.com/dkim-wizard/
Domain name: linnabary.us
DomainKey Selector: dkim
Key size: 1024
I created a pem file;
-----BEGIN RSA PRIVATE KEY----- <key> -----END RSA PRIVATE KEY-----Saved it and loaded it into hmailserver
When I set this up on NameCheap I selected TXT Record, set my host as @, and put this line in, minus key of course;
v=DKIM1; k=rsa; p=<KEY>Now when I test with -> http://www.isnotspam.com
It says my DKIM key is as follows;
---------------------------------------------------------- DKIM check details: ---------------------------------------------------------- Result: invalid ID(s) verified: header.From=admin@linnabary.us Selector= domain= DomainKeys DNS Record=._domainkey.I was wondering if I am making any obvious errors in my record.
Edit;
The email contains the following line;
dkim-signature: v=1; a=rsa-sha256; d=linnabary.us; s=dkim;This is what the setup looks like on NameCheap;
And here is the next test email from ;
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: admin@linnabary.us Anonymous To: ins-a64wsfm3@isnotspam.com --------------------------------------------------------- SPF check details: ---------------------------------------------------------- Result: pass ID(s) verified: smtp.mail=admin@linnabary.us 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: smtp.mail=admin@linnabary.us 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: header.From=admin@linnabary.us 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 admin@linnabary.us Wed Apr 12 17:41:22 2017 Return-path: <admin@linnabary.us> 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: ins-a64wsfm3@isnotspam.com 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 <admin@linnabary.us>) id 1cyMGg-0007x2-1Q for ins-a64wsfm3@isnotspam.com; 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: ins-a64wsfm3@isnotspam.com From: Admin <admin@linnabary.us> Subject: Welcome to Linnabary Message-ID: <8e8be6cd-6354-aeb9-b577-2b0efc25a1a1@linnabary.us> 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
原文：https://stackoverflow.com/questions/43373085
更新时间：2020-12-04 10:12
最满意答案
是。 您将需要访问OMW，对象管理工作台。 如果您这样做，请将表格拉入默认项目，然后进入，就像您要对表格进行更改一样。 在该区域内，您应该能够看到哪些字段是“关键”字段。 这些字段需要在其中放置值，以使记录有效，然后保存。 否则，您将有机会创建重复记录。
如果您具有该访问权限，还可以在表中查看数据库。
根据数据库的不同，您可能需要写入视图（SQL）或逻辑（DB2）表。 可以有许多这些，每个都有不同的关键字段。
还有一个网站，您可以搜索该表，如果您使用标准JDE表，它可能包含该信息。
Yes. You will need to have access to OMW, Object Management Workbench. If you do, pull the table into your Default Project and go in like you are going to make changes to the table. Within that area, you should be able to see what fields are 'Key' fields. Those fields need to have values placed in them in order for the record to be valid and then be saved. Otherwise you stand the chance of creating duplicate records.
You can also look into the database at the table if you have that access.
Depending on the database, you may need to write to a view (SQL) or a logical (DB2) table. There can be many of these and each one will have different Key Fields.
There was also a website out there that you could search for the table and it might have that information included if you are using a standard JDE table.
相关问答
更多-
oracle JD EDWARDS ENTERPRISEONE 各模块操作详细教程[2023-07-02]
推荐你找oracle的视频教程学一下。你百度一下猎豹网校看看，是个专门的计算机网校，里面全是计算机教程，都是视频课程，你要的oracle数据库，视频一步步讲得很详细，另外还有SQL,MySQL,ACCESS等等常用的数据库都有。可能会有你需要的！他们网站里面编程教程很多。 -
您的问题：您在if语句中使用了{和}。 下次你可以使用像http://phpcodechecker.com/这样的PHP代码检查器 正确的代码： if (empty($_POST["name"]) or (empty($_POST["email"]) and empty($_POST["number"]))) { $error = "Your name and a contact method are required fields";} else { ...
-
出于某种原因，连接字符串必须与此不同。 对于仅运行查询的其他类，我不使用相同的连接字符串。 上面的连接字符串工作正常（当然有适当的值）。 它会提示输入密码，但这里的JDE人员想要这样。 The connection string has to be different for this, for some reason. I don't use the same connection string for the other classes that just run queries. The above ...
-
您可以同时选择和更新记录。 没问题（假设DOCO是Table1的主键）： Table1.Select PO cProcessedFlag = BC cProcessedFlag Table1.Fetch Next VA mnOrderNumber[DOCO] <- BC mnOrderNumber[DOCO] While SV File_IO_Status is equal to CO SUCCESS ... Table1.Update VA mnOrder ...
-
它看起来确实无法验证必填字段是否存在。 这很容易添加，但是，您应该在github上提交问题（或PR）。 It looks like indeed it fails to verify required fields are present. This would be easy to add however, you should file an issue (or a PR) on github.
-
创建一个对象，如： var post_object = new Emp_details { id= "Updated ID", name = "Updated Name" }; 并将此对象发布到您的控制器。您将收到此对象，并将Age设置为其默认值（如果为Nullable类型，则为null），其余字段将具有新数据/值。 create an object like : var post_object = new Emp_details { id= "Updated ID", nam ...
-
您可以通过在验证器javascript文件中编辑FormValidator方法的定义来更改此设置。 简单的解决方案是你添加FormValidator方法，如： $('#myform').validate({ // initialize the plugin rules: { field1: { required: true, email: true }, f ...
-
是。 您将需要访问OMW，对象管理工作台。 如果您这样做，请将表格拉入默认项目，然后进入，就像您要对表格进行更改一样。 在该区域内，您应该能够看到哪些字段是“关键”字段。 这些字段需要在其中放置值，以使记录有效，然后保存。 否则，您将有机会创建重复记录。 如果您具有该访问权限，还可以在表中查看数据库。 根据数据库的不同，您可能需要写入视图（SQL）或逻辑（DB2）表。 可以有许多这些，每个都有不同的关键字段。 还有一个网站，您可以搜索该表，如果您使用标准JDE表，它可能包含该信息。 Yes. You wil ...
-
Django伪造必填字段(Django Faking Required Fields)[2022-05-19]
你当然可以做到这一点，当有与用户有关的信息时，它会派上用场，在你需要创建对象时你不会知道自己。 因此，为此，您只需创建自己的表单并根据需要在表单中声明字段。 然后，您可以在创建对象之前在表单上运行验证。 例如，这是我得到的表格，由模特管理员使用; class EventAdminForm(forms.ModelForm): category = forms.ModelChoiceField( label=_("State/Province/Territory"), q ... -
通过2个请求可以UPDATE ： PUT and PATCH PUT更新要在其上执行操作的对象的所有字段。 它基本上遍历所有字段并逐个更新它们。 因此，如果在提供的数据中找不到必填字段，则会引发错误。 PATCH就是我们所说的部分更新。 您只能更新需要更改的字段。 因此，在您的情况下，将您的请求方法更改为PATCH ，您的工作将完成。 UPDATE is possible via 2 requests: PUT and PATCH PUT updates all the fields of the obje ...