Address Blocked by Admins

If you're seeing errors like "Your sending address has been blocked by admins" or "Your recipient address has been blocked by admins", this page explains the common causes and how to resolve them.

Your Sending Address Has Been Blocked

This error means the email address you're trying to send from has been blocked at the server level. Common reasons include:

Common Causes

1. Excessive Cron Job Notifications

• Sending automated emails every minute from invalid senders to invalid recipients
• These flood our queue and trigger alerts
• If you need to relay server notifications, ensure they're actually necessary and properly configured

2. Invalid Recipient Issues

• Sending too many emails to non-existent addresses
• Using non-double-opt-in mailing lists (considered spam)
• May indicate compromised account or configuration errors

3. Compromised WordPress Forms

• Contact forms being exploited to send spam to third-party services
• Damages reputation with major providers (Gmail, Hotmail, Yahoo)

4. Policy Violations

• Circumventing the 400 emails/hour limit by rotating sender addresses
• Sending marketing emails (not permitted on our platform)
• Spoofing sender addresses from domains you don't own
• Using invalid sender addresses like "root@localhost"

5. SPF Record Issues

• Missing or incorrect SPF records causing rejections
• Fix your SPF record and contact support

6. v2board

• v2board installations are not permitted due to frequent problems they cause

7. Non-Human Communication

• Violating our "intended for human consumption" policy
• Automated system-to-system communications that aren't meant to be read

Your Recipient Address Has Been Blocked

This error means the email address you're trying to send to has been blocked. Common reasons include:

Common Causes

1. SMS Gateway Attempts

• Sending email to SMS gateways is forbidden by policy

2. Unwanted Communications

• Repeatedly sending to recipients who don't want the emails
• Continuing to send after bounce notifications

3. Excessive Automated Notifications

• Sending hundreds of cron job notifications to external services
• Wastes resources and affects rate limiting

4. Invalid Recipients

• Repeatedly attempting to send to non-existent addresses
• Sending to domains without valid MX records

5. Quota Management Issues

• Deliberately keeping mailboxes full to generate bounces
• Creates unnecessary server overhead

6. Third-Party Server Issues

• Recipient servers incorrectly reporting our IPs as blacklisted
• Causes our IPs to enter cooldown/mitigation periods

How to Resolve

If you believe your address has been blocked in error or have resolved the underlying issue:

1. Review the common causes above and fix any issues
2. Open a support ticket at https://accounts.mxroute.com/index.php?/tickets/
3. Explain what caused the block and what steps you've taken to prevent it

Important

These blocks are implemented to protect service quality for all users. Repeated violations may result in account termination.