Test mail from h2jammy.yushei.net
alexlai@h2Jammy:~$ telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 h2Jammy.yushei.net ESMTP Postfix (Ubuntu)
EHLO h2jammy.yushei.net
250-h2Jammy.yushei.net
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250-SMTPUTF8
250 CHUNKING
MAIL FROM: alexlai@h2jammy.yushei.net
250 2.1.0 Ok
RCPT TO: rai.sousuke@mac.com
250 2.1.5 Ok
RCPT TO: rai.sousuke@gmail.com
250 2.1.5 Ok
DATA
354 End data with <CR><LF>.<CR><LF>
Subject: from h2jammy.yushei.net
Time 2024-04-26 07:22
Hi
Bye
.
250 2.0.0 Ok: queued as 99B222964925C
quit
221 2.0.0 Bye
Connection closed by foreign host.
alexlai@h2Jammy:~$ systemctl status opendkim
● opendkim.service - OpenDKIM Milter
Loaded: loaded (/lib/systemd/system/opendkim.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2024-04-25 18:29:17 CST; 13h ago
Docs: man:opendkim(8)
man:opendkim.conf(5)
man:opendkim-lua(3)
man:opendkim-genkey(8)
man:opendkim-genzone(8)
man:opendkim-testkey(8)
http://www.opendkim.org/docs.html
alexlai@h2Jammy:~$ dig +short TXT mail._domainkey.h2jammy.yushei.net
"v=DKIM1; h=sha256; k=rsa; t=y; \" \"p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxA2IAxLyotkJGq9XaoIJF1f3lcYWZRHnNxl671GPHCIh7XYTgp5LMOUWbXaODht7yAmOCBRpL8bHur+fD0bs7YGx/wJ7hI4lmsOBx6OoFyHJMmR9e4ABcBTskpOnVOuJtMhX0Jn375BJzyXIQE40mTvQgX0zmZgY0KjA2" "0tLV/GywvCTINonJBZfDK1RLB1FIxITZhmy+4B4mL\" \"NjGVdus0MNaoHhcR0VE0Ahmdys6DZ4M/H4aEhNY9Kdfkm6EZ3hIZ2+945M3L/FO+Nn+/R/tAKXq+oLzHNM49XxEj0JQnI3eaaVwQqKsUUIrbDNLmM909Yx1IK/Rgk19lT5AgnNjQIDAQAB\" ) ; ----- DKIM key mail for h2jammy.yushei.net"
alexlai@h2Jammy:~$ systemctl status postfix
● postfix.service - Postfix Mail Transport Agent
Loaded: loaded (/lib/systemd/system/postfix.service; enabled; vendor preset: enabled)
Active: active (exited) since Thu 2024-04-25 18:30:41 CST; 13h ago
Docs: man:postfix(1)
Process: 22084 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 22084 (code=exited, status=0/SUCCESS)
CPU: 2ms
四 25 18:30:41 h2Jammy systemd[1]: Starting Postfix Mail Transport Agent...
Return-path: <alexlai@h2jammy.yushei.net>
Original-recipient: rfc822;rai.sousuke@mac.com
Received: from qs51p00im-qukt01060501.me.com by p124-mailgateway-smtp-7866dcbd46-hmbq5 (mailgateway 2415B105) with SMTP id d59a4b66-0ce0-4bb0-8fa0-bac6d77d92b2 for <rai.sousuke@mac.com>; Thu, 25 Apr 2024 23:23:16 GMT
X-Apple-MoveToFolder: Junk
X-Apple-Action: JUNK/Junk
X-Apple-UUID: d59a4b66-0ce0-4bb0-8fa0-bac6d77d92b2
Received: from h2Jammy.yushei.net (59-126-118-194.hinet-ip.hinet.net [59.126.118.194]) by qs51p00im-qukt01060501.me.com (Postfix) with ESMTPS id 01168D801D1 for <rai.sousuke@mac.com>; Thu, 25 Apr 2024 23:23:14 +0000 (UTC)
X-ICL-SCORE: 4.122033040041
X-ICL-INFO: GAtbVUweB1BHSVVESAQGUkFIRFcUWUIPAApbVRYSFhEAREQfHVlbBhQVClVYVVJfVxgKEgBcVws1 EVQdGV1bG1sAEwQQVV9MGxwSVVhWUl9XEVQdGV1bG1sAEwQQVV9MGxwSVVhDXxJIW1NOVgEEVFtI V09WAQ9WV1kOEhRfC0AdSywWFV1PTAwMFR8dWRgMEA1EVwhERF9XTF9aSQIAT0RIXlpJCQJMHRAI EgwdXxJbEQ8ZHUQYDBANRFccVAtAABcNGRdHWEBVFA8TRRIKUEVLUkdMAgNQRktURkseD1s3S1RF QQYCW0dMJTcQAnwDGBQfWQFFRQoQEEgZHUQIQFULBUpaQlcLWwoJAgtFXQc1FAcUVlNZD1c=
x-spam-flag: yes
x-suspected-spam: true
Authentication-Results: bimi.icloud.com; bimi=skipped reason="insufficient dmarc"
X-ARC-Info: policy=fail; arc=none
Authentication-Results: arc.icloud.com; arc=none
Authentication-Results: dmarc.icloud.com; dmarc=none header.from=h2jammy.yushei.net
X-DMARC-Info: pass=none; dmarc-policy=(nopolicy); s=u0; d=u0; pdomain=yushei.net
X-DMARC-Policy: none
Authentication-Results: dkim-verifier.icloud.com; dkim=none <-- not signed
Authentication-Results: spf.icloud.com; spf=softfail (spf.icloud.com: domain of transitioning alexlai@h2jammy.yushei.net does not designate 59.126.118.194 as permitted sender) smtp.mailfrom=alexlai@h2jammy.yushei.net
Received-SPF: softfail (spf.icloud.com: domain of transitioning alexlai@h2jammy.yushei.net does not designate 59.126.118.194 as permitted sender) receiver=spf.icloud.com; client-ip=59.126.118.194; helo=h2Jammy.yushei.net; envelope-from=alexlai@h2jammy.yushei.net
Received: from h2jammy.yushei.net (localhost [127.0.0.1]) by h2Jammy.yushei.net (Postfix) with ESMTP id 99B222964925C; Fri, 26 Apr 2024 07:21:56 +0800 (CST)
Subject: from h2jammy.yushei.net
Message-Id: <20240425232213.99B222964925C@h2Jammy.yushei.net>
Date: Fri, 26 Apr 2024 07:21:56 +0800 (CST)
From: alexlai@h2jammy.yushei.net
X-CLX-Shades: Deliver
X-MANTSH: 1TFkXGxoaHxEKWUQXZUZ5UBgZc2VCG0sRCllNF25PRkNcT1gRCl9ZFwcbExEKX00 XbVhPUxEKWUkXHR9xGwYbHxp3BgcTHQYaBhoGGBkGGnEaEBp3BhoGGgYZGgYHHxoGGgYacRoQG ncGGhEKWV4XaGN5EQpDThcHSVNuXExzGHlwR0YaR29acAd1ZlJsGnJHZFpzS0NTHxEKWFwXGQQ aBB8aBRsaGgQdGwQbHBoEExgQGx4aHxoRCl5ZF05zY1oFEQpNXBceHREKTFoXb3hpTWNrEQpFW RdNEQpMXxd6BQUFBQUFBQUFZREKTU4XaREKTEYXTWsRCkNaFx8TBBsYHAQbGxIEGxMeEQpCXhc bEQpEXhcaEQpCRRdtektvXBkeb30cWREKQk4XaURvbUNPElh9bUURCkJMF216S29cGR5vfRxZE QpCbBdtektvXBkeb30cWREKQkAXb0VnRmZIBRxtTXARCkJYF2ZSXFpkY2ZiZH1/EQpCeBdofn9 zAV0FQElGWxEKTV4XBxsRCnBoF219eUh/e2xIT0l8EAcZGhEKbX4XBxsRClhNF0sR
X-Proofpoint-ORIG-GUID: -cyDvfY2SZml0mEpZ-_LxF0XmNpYaiy5
X-Proofpoint-GUID: -cyDvfY2SZml0mEpZ-_LxF0XmNpYaiy5
from h2jammy.yushei.net
To determine if the DKIM signature is properly applied to your outgoing email, let's examine the email headers provided:
Authentication-Results Headers: Authentication-Results: dkim-verifier.icloud.com; dkim=none: This header indicates that the email did not pass DKIM verification when checked by iCloud's DKIM verifier. Received Headers: Received: This header shows the path the email took before reaching its destination. Received-SPF: Indicates a softfail for SPF (Sender Policy Framework) authentication, suggesting that the sending IP address is not explicitly permitted by the domain's SPF record. DKIM-Signature Header: There is no DKIM-Signature header present in the provided email headers. This suggests that either DKIM signing was not configured for the outgoing email or it was removed or modified during transit. Based on the absence of the DKIM-Signature header and the result of the DKIM verification showing "dkim=none," it appears that the email was not properly signed with DKIM when it was sent from your domain.
To ensure DKIM signing is properly configured:
Verify that DKIM signing is enabled and configured correctly on your mail server (Postfix or whichever mail server you are using). Check the configuration of your DKIM key and ensure it matches the DNS TXT record for your domain's DKIM signature. Confirm that the email is being sent through the configured DKIM signing process and that the DKIM-Signature header is included in outgoing emails. If DKIM signing is configured correctly and the DKIM-Signature header is still missing or failing verification, you may need to investigate further to identify any misconfigurations or issues with your email server setup.