This is a company so poorly trained, that their own support people claim to not have knowledge of email troubleshooting.
I went for days without email. When I received it, they claimed it was my mail client settings. So I proved that this was THEIR system.
Dan wrote this admission:
"I had already talked to our mail provider and a supervisor about this issue as I do not have that kind of email knowledge as we're mainly a DNS company. This is what they told me and I'm sorry you don't agree or if it was incorrect.
I'll let them know in case they'd like to look at the issue again.
Regards,
Daniel N.
No-IP Support"
People need to know this is a very sad service. I showed the issue inside their own system:
This one spent 7 days to get routed.
Received: from mx203.no-ip.com (mx203.no-ip.com [69.65.5.119])
by imf14.b.hostedemail.com (Postfix) with ESMTP
for redacted@execvps.com; Thu, 8 Oct 2020 00:43:21 +0000 (UTC)
Received: from mail1.no-ip.com (mail1.no-ip.com [8.23.224.50])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by mx203.no-ip.com (Postfix) with ESMTPS id 4C2Tgb15M3z72mW8
for redacted@execvps.com; Thu, 1 Oct 2020 18:22:51 -0500 (CDT)
Received: from mail1.no-ip.com (localhost.localdomain [127.0.0.1])
by mail1.no-ip.com (Postfix) with ESMTP id 8E4079EC5FE
for redacted@execvps.com; Thu, 1 Oct 2020 16:22:50 -0700 (PDT)
Received: from dtwmail1.msisurvey.com (dtwmail1.msisurvey.com [12.154.156.34])
by mail1.no-ip.com (Postfix) with ESMTP id 4D35D9EC5A6
for redacted@execvps.com; Thu, 1 Oct 2020 16:22:50 -0700 (PDT) read more