Sending
Fix sending and setup errors
Use the message you see to find the cause and complete the fix.
Fix “Add your postal address in Settings before sending a test email.”
What happened: Your test send failed with this message.
Why: InboxJoy requires a postal address for CAN-SPAM compliance before it sends any email, including tests.
How to fix it: Open Settings → Workspace, add your postal address, and try again.
Fix “This recipient is suppressed and cannot receive test emails.”
What happened: Your test send failed with this message.
Why: The test address is on your workspace’s do-not-contact list.
How to fix it: Remove the address from Settings → Sending if that was unintentional, or test with a different address.
Wait after 20 test sends in one day
What happened: Test sends stopped working after the twentieth send in one day.
Why: InboxJoy limits Azure test sends to 20 per workspace per day to prevent misuse.
How to fix it: Wait until the next day, when the limit resets.
Fix “Address pending — reconnect”
What happened: A mailbox shows this message instead of an email address.
Why: The OAuth connection did not fully complete.
How to fix it: Open the Mailboxes page and use the Reconnect action for that mailbox.
Clear a “needs attention” banner
What happened: You connected a mailbox, but InboxJoy shows a needs attention banner.
Why: The mailbox can send, but InboxJoy could not set up inbound reply detection for it.
How to fix it: Reconnect the mailbox so replies can automatically stop follow-ups for that lead.
Clear “Ramp paused” or “Sending held”
What happened: The mailbox warm-up shows one of these badges and little or nothing is going out.
Why: The mailbox’s bounce rate rose enough to mark its health as degraded or critical. Days in that state do not count toward the warm-up ramp, and a critical mailbox is held back from sending entirely.
How to fix it: Clean the list behind the campaign — the bounce rate is the cause, not the mailbox. Once 24 hours pass with no new bounce, a critical mailbox returns to half volume by itself and recovers from there; you do not need to reconnect it or start a new ramp. See Manage warm-up and sending limits.