How can we get application email delivered without the client's DNS changes?

November 19, 2026 5 answers
Asked by 5m~claspfunnel_826

Our hosted application sends mail through a local SMTP server, but its public IP is listed by Spamhaus and Microsoft 365 is rejecting messages. The server lacks DKIM and reverse DNS, and the client won't add DNS records or provide a relay.

Can we fix this on our side, or do we need a different way to send?

Answers

r.739!mavqueno

Start by separating the IP address from the sending domain. Reverse DNS belongs to the IP's reverse zone, normally controlled by your hosting provider or ISP. Ask them to set the PTR for your outbound IP to a mail hostname, and make sure that hostname resolves back to the IP.

SPF and DKIM are different. Their records need to be published under the relevant sending domains, so whether you can do that yourself depends on which domain the application uses and who controls it. DMARC checks alignment with the visible From domain, so that matters too.

Check the actual Spamhaus listing and its removal requirements rather than assuming missing DKIM caused it. Fixing DNS is worthwhile, but it may not automatically clear a listing or guarantee delivery.

4c!ferrulepocket_853:

Also check which public IP actually makes the outbound connection. It may not be the address you expect if traffic goes through a gateway.

Reply to this answer
9g~canvasgizmo_315

If the application can send from a domain you control, use that domain for the From address and configure its authentication properly. That avoids needing the client to publish records, though they still need to accept the different sender address.

If the messages must appear to come from the client's domain, you generally need their cooperation to authorize and authenticate that mail. A dedicated sending subdomain could limit the scope, but they would still need to create or delegate it.

Reply to this answer
9u~canvaspocket_628

A hosted email delivery service is another option. The application can submit mail through its SMTP service instead of delivering directly from your server's listed IP.

That changes the sending infrastructure, not the ownership of the From domain. If you use the client's domain, the provider may still require DNS records for authentication. Check that before promising it as a no-client-changes fix.

Reply to this answer
4j!cobaltspanner_628

Since the messages are going to Microsoft 365 inboxes, ask the client's Microsoft 365 administrator about a supported relay or connector arrangement for the application. That requires tenant configuration and agreement on how the server is identified, so it isn't a workaround you can install unilaterally.

Allowlisting an IP might help in some setups, but it should not be treated as a substitute for fixing the sender configuration or investigating the listing.

Reply to this answer
q.741!zunquori

Put the choices in writing for the project meeting. Identify who controls the outbound IP and From domain, what each proposed fix needs from each team, and what happens if those changes are declined. A DNS change on your side may solve only part of the problem.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions