Excellent. Now we are all green here (ignore the MX record since we
intentionally don't have one): https://intodns.com/spamassassin.org
In a week or two we should be able to add in ns2.ena.com after getting
the nod from our CTO who is out of pocket for a couple of weeks.
Dave
On 05/11/2017 11:34 AM, Kevin A. McGrail wrote:
FYI
-------- Forwarded Message --------
Subject: [jira] [Updated] (INFRA-14135) Please change DNS Servers
for spamassassin.org
Date: Thu, 11 May 2017 16:25:04 +0000 (UTC)
From: Chris Lambertus (JIRA) <j...@apache.org>
To: kmcgr...@apache.org
[
https://issues.apache.org/jira/browse/INFRA-14135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Lambertus updated INFRA-14135:
------------------------------------
Status: Waiting for user (was: Waiting for Infra)
DNS server replaced as requested.
Please change DNS Servers for spamassassin.org
----------------------------------------------
Key: INFRA-14135
URL: https://issues.apache.org/jira/browse/INFRA-14135
Project: Infrastructure
Issue Type: Task
Components: DNS
Reporter: Kevin A. McGrail
Assignee: Chris Lambertus
Priority: Minor
Please change the DNS servers for spamassassin.org to remove
ns.hyperreal.org and replace it with ns2.pccc.com.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
