JobAdder email domain checks before the next mailshot

Start with the affected message type

Record whether the missing email is a mailshot, candidate submission, float, automatic response or another workflow. Confirm the visible From address and the account that generated it.

A message sent directly from a recruiter’s connected mailbox may not be equivalent to the affected JobAdder workflow. Keep a comparison message, but do not treat a successful direct send as proof that every platform route is configured correctly.

Confirm ownership and sending verification

JobAdder’s domain-verification documentation describes confirming ownership and reviewing SMTP/domain settings. Have the responsible administrator establish the current verification state and whether the domain is active for sending.

If you do not have access, ask for the state and the exact records issued for your own domain. You do not need someone’s credentials to organise the investigation.

Treat “ownership confirmed” and “ready to send through the intended workflow” as checks to verify, not labels to assume are interchangeable.

Use account-issued DNS records

The documented workflow includes SPF and DKIM TXT records, MX records for the sending subdomain and a CNAME associated with tracking. The examples show Mailgun infrastructure. Their exact hostnames and values must come from the account’s setup instructions.

Send those instructions to the DNS administrator. Ask them to record which hostname each value belongs to. A record intended for a dedicated subdomain should not be installed by replacing the root domain’s normal mail configuration.

Do not remove existing mail records to make an example “look right”. A small-looking DNS edit can affect unrelated business email.

Check the support activation step

The official workflow describes contacting JobAdder support for the relevant CNAME activation. Confirm whether that step applies to your setup and whether it has been completed.

If records appear correct but the workflow remains unverified, give support the account, sending domain, observed state and time. Ask which verification or activation condition is still missing rather than repeatedly editing records without a reason.

Review the sender address for each workflow

Refari’s documented integration instructions call out sender settings for candidate submissions/floats and automatic responses. That is a useful reminder that different message features may have separate sender settings.

Check the current JobAdder interface and support instructions for your account. This guide does not claim that all tenants show the same menus or use the same integration.

Ask which address a real recipient sees, not merely which address the team expects to be used.

Verify a received message

After the administrator confirms setup, send a controlled message through the actual affected workflow to an authorised recipient. Inspect the original received-message headers and record the folder and time.

Our header explainer can explain recorded authentication results. It does not establish the trust of a header block or verify DNS. A passing result also does not guarantee the next campaign reaches every inbox.

If the remaining question is placement across test providers, use the testing guide. Keep candidate data out of diagnostic messages.

Give support a complete brief

Collect the workflow, visible sender, domain-verification state, relevant account-issued records, support-activation status and one exact affected example. Keep the original error if there is one.

The handoff builder turns those observations into a concise request without sending the information to us.