19 Messages
•
290 Points
.mil cannot receive my email, again
I have been a Homestead (HS) customer for 21 years. This same thing happens every 4-5 years. A couple of weeks ago I posted about gmail and .mil bouncing my email. This usually happens when someone at my shared IP posts a bunch of spam and the shared IP gets blacklisted. In the past, my account was moved to another IP. Can this happen now?
This incident -
#1 posted here asking for help. Couple of days later the response is tech can't help because my email uses CloudFlare [for encryption because RoundCube isn't encrypted.]
#2 Called Tech Support and agent said she fixed it. Yes, fixed gmail but not .mil.
#3 Called Tech Support and agent said she made some adjustments but problem on .mil end, that my email signature is not being read.
#4 Called Tech Support and agent said he made some adjustments but problem on .mil end, that my email signature is not being read. Told me to contact .mil tech support to see why not reading my cert. My contact at .mil had his tech guy look at it. That tech says my email coming from HS does not have complete signature/certificate so .mil times out trying to accept my email.
#5 Called Tech Support and agent walked us thru several possibilities and escalated to engineering. Same thing - .mil issue for not accepting signature. So what is wrong with the signature on my HS email that .mil won't accept????
I need this case escalated to someone who can look at the codes in the bounce message and figure out what is wrong that .mil cannot recognize the signature/certificate on my email. ***** is my highlight. There appears to be no way that I can whitelist my .mil contacts. This has to be fixed. This is my livelihood and that of my employees. I cannot respond to .mil email, cannot submit work product, and cannot invoice them to get paid.
This is the information from the bounce message:
A message that you sent has not yet been delivered to one or more of its
recipients after more than 4 hours on the queue on bosmailout08.eigbox.net.
The message identifier is: 1r8mJV-0007As-9S
The date of the message is: Fri, 01 Dec 2023 03:02:38 +0800
The subject of the message is: Test email
The address to which the message has not yet been delivered is:
richard.f.jenkins1@NAVY.mil
***** host sec-jeemsg.eemsg.mail.mil [156.112.250.14]
Delay reason: SMTP error from remote mail server after end of data:
451 #4.7.5 Unable to verify signature - key server unavailable*****
No action is required on your part. Delivery attempts will continue for
some time, and this warning may be repeated at intervals if the message
remains undelivered. Eventually the mail delivery software will give up,
and when that happens, the message will be returned to you.
Action: delayed
Final-Recipient: rfc822;richard.f.jenkins1@navy.mil
Status: 4.0.0
Remote-MTA: dns; sec-jeemsg.eemsg.mail.mil
Diagnostic-Code: smtp; 451 #4.7.5 Unable to verify signature - key server unavailable
Received: from bosmailscan06.eigbox.net ([10.20.15.6])
by bosmailout08.eigbox.net with esmtp (Exim)
id 1r8mJV-0007As-9S
for richard.f.jenkins1@navy.mil; Thu, 30 Nov 2023 14:03:05 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=forensicgenealogyservices.com; s=dkim; h=Sender:Content-Transfer-Encoding:
Content-Type:Message-ID:Subject:To:From:Date:MIME-Version:Reply-To:Cc:
Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id:
List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
bh=O37VSkI3Ab2ma/hCPCAn7t035glq0URexFIttVb780E=; b=cyF3h/ZBmgM8a98ZrMJq7GP78
EMxbthbe7udAcWpRVCbJM8VouafIaEp2NrnWAxkTyLjM25d6gkVGdRXttsHX0lm91q/koq4CdZvtK
+AbEvZOIaUOHbvrhuSfJlOxzBti50wPH2+1GpD2CLZSeVYqpHe5liqAwU5tcifN3/L1PVCL9y6Rpy
X6BGxqB3zFd09gOV2l6PHfEtCZd5nz0vM4dtMF7mR/8qL21SWJNTOFBUl2y5B0jcKpcF6Rvb2j5ng
d/ITeQI+e/WZDj+l4L6LWTQILxga4B2563nanj/76xJcXmsUXNU+846B1/37PXiW9JFAGXOCPXAFU
cLLDDrobg==;
Received: from [10.115.3.32] (helo=bosimpout12)
by bosmailscan06.eigbox.net with esmtp (Exim)
id 1r8mJU-0006C6-SP
for richard.f.jenkins1@navy.mil; Thu, 30 Nov 2023 14:03:04 -0500
Received: from boswebmail15.eigbox.net ([10.20.16.15])
by bosimpout12 with
id Gj312B00M0KVxlm01j34d3; Thu, 30 Nov 2023 14:03:04 -0500
X-Authority-Analysis: v=2.3 cv=dOg9ZNRb c=1 sm=1 tr=0
a=fXWB4kgb58BbqYPqR/PhaA==:117 a=7D3N0J9MXTOo4CiSH6wmYQ==:17
a=kj9zAlcOel0A:10 a=BNY50KLci1gA:10 a=EUsgOysyAo3KeYOn71AA:9 a=CjuIK1q_8ugA:10
Received: from [127.0.0.1] (helo=homestead)
by boswebmail15.eigbox.net with esmtp (Exim)
id 1r8mJ4-0005Pg-UN
for richard.f.jenkins1@navy.mil; Thu, 30 Nov 2023 14:02:38 -0500
Received: from 122.55.94.34.pldt.net ([122.55.94.34])
by emailmg.homestead.com
with HTTP (HTTP/1.1 POST); Thu, 30 Nov 2023 14:02:38 -0500
MIME-Version: 1.0
Date: Fri, 01 Dec 2023 03:02:38 +0800
From: Dee Dee King <king@forensicgenealogyservices.com>
To: richard.f.jenkins1@navy.mil
Subject: Test email
Message-ID: <c8d3523510e91e964e3639811413c7cd@forensicgenealogyservices.com>
X-Sender: king@forensicgenealogyservices.com
User-Agent: Roundcube Webmail/1.3.14
Content-Type: text/plain; charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bit
X-EN-AuthUser: king@forensicgenealogyservices.com
Sender: Dee Dee King <king@forensicgenealogyservices.com>
X-EN-Class: impinc
dee_dee7318
19 Messages
•
290 Points
8 months ago
And when it finally timed out and attempts to deliver failed :
Diagnostic-Code: smtp; 451 #4.7.5 Unable to verify signature - key server unavailable: retry timeout exceeded
0
0
mike_j
78 Messages
•
906 Points
8 months ago
Hello Dee Dee7318.
Thanks for your message. The DMARC record for your domain gives a syntax error. The current record is missing valid email addresses that are used for reporting. The email addresses in the DMARC record will receive email delivery statistics and failure reports, and they are mandatory.
You can use the following link to create a valid DMARC record.
DMARC Record Generator - Create DMARC DNS Records - MxToolbox
After the DMARC record is corrected the issue should be resolved.
1
0