1
Why do I get this when the domain is disabled on the server and a former client sends to me from 3rd party server?
Question asked by Brian Bjerring-Jensen - 5/19/2025 at 2:34 AM
Unanswered
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

failed: host smartermail.cloudpros.dk (93.176.78.69) said:
550 Invalid domain or domain is disabled.
Reporting-MTA: dns; send.one.com
Received-from-MTA: dns; smtpclient.apple (62.107.17.188)
Arrival-Date: Mon, 19 May 2025 09:15:59 +0000
X-Original-ID: e0a3b1d6-3491-11f0-b159-e90f2b8e16ca

Final-Recipient: rfc822; shutupandtakemymoney@iwillfartyouintheface.com 
Action: failed
Status: 5.0.0
Remote-MTA: dns; smartermail.cloudpros.dk (93.176.78.69)
Diagnostic-Code: smtp; 550 Invalid domain or domain is disabled.
Received: from smtpclient.apple (62-107-17-188.norlyscustomer.net [62.107.17.188])
    by mailrelay2.pub.mailoutpod2-cph3.one.com (Halon) with ESMTPSA
    id e0a3b1d6-3491-11f0-b159-e90f2b8e16ca;
    Mon, 19 May 2025 09:15:59 +0000 (UTC)
From: Flemming <flemming@lindelov.com>
Content-Type: multipart/alternative;
    boundary="Apple-Mail=_FA461189-4378-4F6E-A296-68E8F37A3ADA"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.500.181.1.5\))
Subject: Fwd: VIP-adgang til Agentdagen 2025
Message-Id: <05A8FB88-55E7-4044-BD42-3A5BEF9B1E8B@lindelov.com>
References: <e8931e7fb9b64b48a1d26209a61d6a09@25d51ba0e08446a1ab1303ef60fb7c6b>
To: "Brian" <bbj@cloudpros.dk>
Date: Mon, 19 May 2025 11:15:46 +0200
X-Mailer: Apple Mail (2.3826.500.181.1.5)


4 Replies

Reply to Thread
0
root orchild Replied
Hello,

Maybe domain lindelov.com is disabled on your server.
0
It was. But when using MX records then it shouldnt matter.
0
mh Replied
If the domain exists on the local server, even if disabled, MX records won't matter as far as I would think. No need to look up something that is right there already, so just deliver to it. Or in this case, bounce because it was disabled. You'll need to delete it, or make a backup first.
We had a similar issue with a client who used to be a Microsoft tenant, and the old company left their domain in their setup for a while. No one from Microsoft could email as it would default to the old tenant setup since it was still defined in MS servers having the domain for mail, and others hosted in MS would get bounces.
0
It makes no sense of you set it to MX records and it doesnt validate or use it.

Reply to Thread

Enter the verification text