MxToolbox: how to investigate email delivery problems with Mindflow

Aditya GaurChannel Partnership Specialist

Process Automation

A customer can email your support team, but your reply bounces. Which domain should you check? The customer’s MX records tell you where their domain receives mail. They tell you little about the reputation of the server that sent your reply. Choosing the right lookup is the first step in making MxToolbox useful.

Start with the failed message

Ask for the delivery time, the recipient domain, the responding mail server and the exact SMTP response. Keep the original message in the support system. A ticket can usually carry the response code and a short diagnostic excerpt without copying the email body. Determine whether your organization was sending or receiving the message.

When people cannot reach your domain, check its MX records. Lower preference numbers take priority. Compare the hostnames and preferences with your mail provider’s setup instructions. If an administrator recently changed a record, record the previous value and its time to live. Two resolvers may legitimately return different answers while cached records expire.

When your messages bounce, use your provider’s mail trace to identify the sending IP and the recipient’s response. A blocklist lookup on that IP can help explain a reputation-related rejection. A listing alone does not establish why a specific recipient rejected the message. For an authentication failure, check the SPF result for the envelope sender, the DKIM result for the signing domain, and their alignment with the visible From domain under DMARC. MxToolbox tools

Build a small enrichment workflow

  1. Start from a delivery ticket. Ask whether mail was inbound or outbound and whether the organization controls the domain or sending service.

  2. Use the relevant lookup through the MxToolbox API. Store the lookup type, the exact input, the timestamp and the returned observation. Keep the API credential in the connection. Check the limits for your subscription before scheduling repeated checks. MxToolbox API reference

  3. Add the result to the original ticket. If the lookup returns no data or a quota error, record that outcome explicitly. Assign the ticket to the mail administrator who can access provider logs.

  4. Close the ticket after a fresh delivery test succeeds. Include the message trace or the administrator’s verification alongside the lookup.

For example, a customer’s gateway may respond that a sending IP has poor reputation while your public MX records look healthy. In that case, give the outbound provider the sending IP, time and response. Changing your inbound MX records would leave the delivery problem in place.

In Mindflow, the same ticket can hold the initial report, the lookup and the owner’s response. Start with one direction of delivery and one lookup. Test against a resolved incident before adding more checks. MxToolbox integration in Mindflow

Related articles

Process Automation

The Rise of Prompt-Based Automation

Sagar GaurMarketing Specialist

Related articles

Process Automation

The Rise of Prompt-Based Automation

Sagar GaurMarketing Specialist

Related articles

Process Automation

The Rise of Prompt-Based Automation

Sagar GaurMarketing Specialist

Less busywork. More possibility.

Let your agents handle the routine. Make room for what comes next.

Automation intelligence, delivered monthly.

Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.

© 2026 Mindflow — All rights reserved.

SOC 2 Type II
ISO 27001
GDPR
France 2030
Bpifrance
Île-de-France

Less busywork. More possibility.

Let your agents handle the routine. Make room for what comes next.

Automation intelligence, delivered monthly.

Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.

© 2026 Mindflow — All rights reserved.

SOC 2 Type II
ISO 27001
GDPR
France 2030
Bpifrance
Île-de-France

Automation intelligence, delivered monthly.

Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.

© 2026 Mindflow — All rights reserved.

SOC 2 Type II
ISO 27001
GDPR
France 2030
Bpifrance
Île-de-France