# MailBaby Feedback Loop and Abuse Reports: Avoid Suspensions Source: https://srvscripts.com/guides/mailbaby-feedback-loops-abuse-reports/ Updated: 2026-10-03 Publisher: srvScripts (https://srvscripts.com/) Every large mailbox provider offers a feedback loop: when a recipient marks a message as spam, the provider sends a copy of the complaint to whoever is responsible for the sending IP. When your server relays through MailBaby, that IP belongs to InterServer, so the complaint lands with them first. How they process it, and what they expect from you, determines whether a handful of complaints stays a minor event or becomes a blocked account. This guide explains the mechanism and sets out the response. In short: When a recipient reports mail sent through MailBaby as spam, the mailbox provider’s feedback-loop report goes to InterServer, which matches it to the message in its 60-day log and records the complaint against the individual sender address… **Short answer:** When a recipient reports mail sent through MailBaby as spam, the mailbox provider’s feedback-loop report goes to InterServer, which matches it to the message in its 60-day log and records the complaint against the individual sender address on your account, not the server; a rising complaint rate lowers that address’s score and eventually blocks it. Complaints appear in the portal log and the REST API rather than as emails to you, while escalated abuse reports arrive as a ticket with a deadline. Respond by identifying whether the cause was a compromise, an unsolicited list or an unclear transactional template, fixing it, and replying to InterServer with what you did. ## How a complaint travels The recipient clicks the spam button. Their provider generates an abuse report in ARF format containing the original message, or as much of it as the provider is willing to share, and sends it to the address registered for the sending IP’s feedback loop. MailBaby is registered for the loops offered by the major providers as part of managing the IP pools; you do not need to register anything yourself and could not, since the IPs are not yours. MailBaby parses the report, matches it to the original message in its 60-day log using the message identifier and recipient, and records the complaint against the sending address on your account. That is the key difference from running your own IPs: complaints are attributed to the individual sender, not to the server, and the relay’s scoring uses them at that granularity. A sender address whose complaint rate climbs is scored more harshly on subsequent messages, then blocked. The account as a whole is affected only if complaints spread across many addresses, which is what happens on a server with a mass-mailing customer or a widespread compromise. Direct abuse reports, meaning a message from a recipient or a blocklist operator to InterServer’s abuse desk rather than an automated loop, are handled by people and reach you as a ticket or email from InterServer. They carry more weight and shorter deadlines. ## What reaches you Feedback-loop complaints are visible in the portal log as an outcome against the message, and a rising complaint count for an address shows in the same log and through the REST API’s log endpoint. There is no automatic per-complaint email to you; the design assumes you monitor the log or poll the API. [The REST API guide](/guides/mailbaby-rest-api/) includes a poller that alerts on new blocks; extend it to count complaints per address per day and you have early warning. An abuse report escalated by InterServer arrives as a notification tied to your account. It states the sending address, the recipient domain or reporter, and a deadline. Treat it as urgent: the relay side has already limited the address, and the question is whether your account keeps its reputation tier. ## The response procedure Establish what was sent before anything else. Pull the address’s recent log entries from the portal or the API and look at subjects, volume and recipient spread. Three patterns account for nearly every case. A compromised mailbox or script sends unsolicited mail to strangers. Volume is high, subjects are repetitive, recipients are unrelated to the customer. Follow [the compromise and delisting guide](/guides/mailbaby-compromised-account-delisting/): reset credentials, find and remove the script, purge the queue, then delist. A legitimate customer mails a list that did not ask for it. Volume is moderate, subjects are marketing, recipients are many but plausible. The customer is probably buying or scraping lists, which is prohibited content under the acceptable use policy regardless of how the customer describes it. Suspend the customer’s mailing until they can show consent for every recipient, and apply the practices in [the newsletter guide](/guides/mailbaby-newsletter-sending-limit/) before they resume. Transactional mail is being reported by recipients who do not recognise it. Volume is low and the complaint rate is small in absolute terms. Look at the message: an unclear sender name, a missing unsubscribe link on what is effectively a notification, or a from address the recipient does not associate with the service. Fix the template and move on. Reply to InterServer’s report within the stated deadline, stating which of these it was and what you did. A concise, factual response with timestamps is what keeps the account in good standing; silence is what gets accounts paused. ## Reduce complaints structurally Complaint rate is a ratio, so the goal is fewer complaints per message delivered, not zero complaints. The levers that matter on a hosting server: - Require `List-Unsubscribe` headers, including the one-click variant, on any customer sending to a list. Recipients who can unsubscribe in one click do not report. - Cap per-domain hourly sending below the relay’s 6,000 limit so a bad list run stays small; see [the outbound limits guide](/guides/exim-outbound-mail-limits-whm/). - Make DKIM signing at the source mandatory, so complaints are attributed to the right domain and your reputation is not diluted across customers. - Screen new customers against the prohibited categories at signup rather than after the first report. ## Verify Once a month, pull the complaint counts per sender for the previous thirty days from the API log and compare against messages delivered. Any sender above roughly one complaint per thousand deliveries needs a conversation before the relay makes the decision for you. The common pitfall is treating a feedback-loop complaint as a false positive because the customer says the recipient opted in; the relay does not adjudicate consent, it counts complaints, and the customer’s assurance changes nothing about the score. ## MailBaby feedback loop at a glance Covers: How a complaint travels, What reaches you, The response procedure and Reduce complaints structurally. **Official documentation:** [RFC 5321 (SMTP)](https://www.rfc-editor.org/rfc/rfc5321), [Linux man pages](https://man7.org/linux/man-pages/). **Related guides:** [MailBaby with Postfix on Ubuntu/Debian as an authenticated smarthost](https://srvscripts.com/guides/postfix-mailbaby-smarthost-ubuntu-debian/) · [Whitelisting MailBaby in cPanel greylisting, CSF and SpamAssassin](https://srvscripts.com/guides/whitelist-mailbaby-cpanel/) · [Email forwarders with MailBaby: SRS, strict forwarding errors and backoffs](https://srvscripts.com/guides/mailbaby-srs-strict-forwarding-errors/). ## Frequently asked questions ### Do I need to register for Gmail or Microsoft feedback loops if I use MailBaby? No. The sending IPs belong to InterServer, so MailBaby is registered for the major providers’ feedback loops on your behalf and you could not register them yourself. Your job is to watch the complaint counts per sender in the portal log or through the REST API. ### Does one spam complaint get my MailBaby account blocked? No. Complaints are attributed to the individual sender address and scored as a rate against that address’s deliveries. An address is blocked only when its complaint rate climbs, and the account as a whole is affected only when complaints spread across many addresses, as with a mass-mailing customer or a widespread compromise. ### What complaint rate is acceptable for mail sent through MailBaby? Treat roughly one complaint per thousand delivered messages as the ceiling for any single sender. Pull the per-sender counts for the previous thirty days each month and talk to any customer above that line before the relay blocks the address for you.