SMTP or security changes
A password rotation, port change, expired certificate or TLS issue can interrupt the sending path.
A mailbox can work today and lose deliverability tomorrow. Schedule recurring checks in your dashboard to spot SMTP, security, authentication or reputation changes before they disrupt important outgoing email.
Recurring deliverability monitoring is included with an active paid subscription. No separate monitoring add-on is required.
SMTP settings, TLS certificates, domain authentication and sender reputation can change over time. A configuration update or a new spam signal may lower a mailbox score without an obvious warning in your application.
A password rotation, port change, expired certificate or TLS issue can interrupt the sending path.
Changes to SPF, DKIM or DMARC records can affect how receiving providers evaluate your messages.
Blocklist listings or other reputation signals may appear after a mailbox was configured and tested.
A sending system may accept a message even when a promotion later lands in spam. The sender can see a successful handoff while customers never notice the offer.
4 weekly sends × 1,000 recipients each
80 orders at an illustrative 2% purchase rate
Assumed average value per order
If all four campaigns go unseen
80 assumed orders × average order value = gross sales opportunity.
Illustration only, not a forecast, confirmed loss or promise. This is gross revenue before costs. Real inbox placement, conversions and sales vary. Monitoring can surface technical or reputation warnings, but cannot guarantee inbox placement or sales.
Choose how often MailBridgeAPI should check the connected mailbox, define the conditions that matter to your team, and keep a history of recurring reports beside your other deliverability checks.
Build a schedule in the dashboard. The shortest interval is 60 minutes, with options to choose the time and calendar cadence.
Choose the minimum score that is acceptable for this mailbox. You can also be alerted when a report fails or stays pending for more than five minutes.
Recurring reports are kept in the deliverability history and identified as automatic, so your team can follow changes over time.
Choose email alerts, mobile push notifications, or both. Email alerts go to your account email by default; you can enter another recipient. The alert includes the reason, mailbox and score, plus report details and a link to the full result.
Alerts are sent when a monitored issue is detected; recovery is recorded by later checks. A score is a diagnostic signal, not a guarantee that every provider will place a message in the inbox.
The alert email puts the result in context: a color-coded overall status, the mailbox and score, then diagnostic checks ordered by priority. Each check explains the finding and, when available, gives a recommended action. The full report remains one click away.
SPF record needs attention
Recommended actionReview the SPF record for this sending domain.
The sending domain has a record that needs correction.
A reputation signal deserves a closer look.
The mailbox accepted the diagnostic message.
Watch the mailbox used for order confirmations, receipts and customer updates.
Catch delivery problems affecting replies, case updates and service notifications.
Keep an eye on client mailboxes after credential rotations, DNS changes or provider updates.
Monitor the sender used for account notices, security messages and workflow alerts.
Add the SMTP settings for the mailbox you want to monitor in the MailBridgeAPI dashboard.
Set the cadence, score threshold, alert channels and recipient for that mailbox.
Review automatic checks, investigate changes and use the recommended actions to correct issues.
An active paid subscription includes up to 100 completed deliverability checks per account per UTC day. Recurring checks use this allowance; additional completed checks use global Credits.
Set up a recurring check for a connected mailbox, then let the dashboard and alerts keep your team informed.
MailBridgeAPI links the SMTP and IMAP mailbox you own or are authorized to use to an account API key and a mailbox API key. Every request selects that same mailbox: send from its address, read its received messages, or process them in your applications.
Explore the docsapikey + apikeyboxAPI endpoint requestAction through that mailboxPOST /sendemail/A POST request uses the SMTP connection of the mailbox selected by apikeybox and sends from that mailbox.
GET /getemail/A GET request uses the same mailbox key to retrieve messages from its configured IMAP folders.
YOUR LOGIC. YOUR WORKFLOW.Your authorized application handles the result in its workflows, automations, CRM, support tools, or AI systems.
Connect only a mailbox you own or are authorized to use. The provider must allow compatible SMTP or IMAP access, and its limits still apply.