I don't mind earning some kudo's if I'm able to help you.
First of all, when sending mail from your iCloud, do you see -any- related connection in your exim mainlog or exim rejectlog? So any proof that iCloud is trying to make a connection with your server? Because that should be there.
However I've seen some other issues with could in some cases also caus some culprit, mostly with sending mail in fact.
with ns1 and ns2 both hosted by the DA server.
With only 1 ip while in fact you should have 2 ip's. However, that is something for another time, it's good behaviour, not an issue.
But you seem to have a nameserver issue.
ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns1.imperiumhq.com
ns2.imperiumhq.com
This one can cause receiving mail issues.
intoDNS: Checking health and configurtion of DNS server and mail server for domainimperiumhq.com.
intodns.com
As long as this is not fixed, you have a real problem. It seems the nameservers are present at the parent servers, so glue records correct.
But it seems they are not setup correctly on your directadmin server.
Then I'm wondering about something else.
Intodns gives ip 77.68.9.43 as ip for both your nameservers.
But when I use one of my own servers:
Code:
[root@server: ~]# nslookup ns2.imperiumhq.com
Server: 185.12.64.2
as you can see that is a totally different ip.
Did you change nameservers recently? If yes, then wait until the nameservers are fully synchronized around the world before things will work correctly. This can take up 24-48 hours.
And another thing:
ns1.server-77-68-9-43.da.direct
ns2.server-77-68-9-43.da.direct
are also still mentioned in intodns. Be sure to get rid of those.
As last a tip, can also be seen in intodns:
You require a rDNS/PTR record which is at this moment not available.
So your ip 77.68.9.43 needs to point to your servers FQDN hostname. Please do not use the 77.68.9.43.da.direct hostname for that. It works but you can run into issues when mailing outside.
Best is to create your own hostname like for example server.imperiumhq.com and create a DNS entry for it.
I've create a manual on how to create and change hostnames.
This is a guide on how to create a correct FQDN hostname on a sever or VPS. I created this newly here in this section, for easier reference and it's also easier to find. There is also another method, but the method described here is another method which is also still very usable. Before you...
forum.directadmin.com
Now after you've done this, go into your VPS control panel from your hoster or datacenter, and then point that ip to your FQDN hostname.
Feel free to ask further questions, however it's 00.36 AM here at the moment so I will shutdown my pc soon and go watch TV and be back tomorrow. But there are others also helping here so no worries.
