Common signs
- A 5xx error rejects the message permanently
- A 4xx error repeats or times out
- The error mentions authentication or policy
- The recipient or domain is reported as unknown
Use the error as evidence
A bounce is a delivery report from a sending or receiving system. The exact status code and explanation are more useful than a screenshot saying only “not delivered.” AIVIQ reads that evidence and tests the relevant public configuration before proposing a repair.
What to look for
Common categories include invalid recipients, routing failures, blocked sending systems, message-size limits, authentication failures and temporary provider conditions. The wording matters because unrelated DNS changes can make a different problem worse.
Copy the complete bounce code and technical explanation while removing message contents, personal names and unrelated addresses. Include the sending provider, recipient provider if known, time of failure and whether other destinations work.
Diagnosis and one ordinary repair pass for one sending or receiving incident starts at CAD $89. A clearly identified single DNS or mailbox-setting correction may qualify for CAD $49.
Safe expectations
AIVIQ verifies the agreed setting or flow with a basic test. Recipient-side blocking, compromised accounts, blacklists, migrations, historical recovery and multi-domain environments are quoted separately.
Before changing DNS or account settings, record the existing configuration. Use temporary access where needed, verify the agreed result, and remove that access afterward. AIVIQ does not claim access to private provider systems and does not promise a guaranteed repair time.
Start with the free public DNS check or send a written request through the main Business Email Rescue page. The hub explains all four price levels, exclusions, access rules and what happens after submission.
Questions
Keep it until diagnosis is complete because its status code and server explanation are useful evidence.
Share only what is needed. Redact message content, names and unrelated addresses whenever possible.