550 5.7.520 Access denied, Your organization does not allow external forwarding
Automatic forwarding to an outside address is blocked
Seen in Microsoft 365, Exchange Online
A mailbox rule or forwarding setting tried to forward mail to an external address, and the tenant's outbound spam policy blocks automatic external forwarding.
Common causes
- A user set up an inbox rule or mailbox forwarding to a personal or partner address.
- The default outbound anti-spam policy has automatic forwarding set to Automatic, which behaves as Off.
- An attacker created a forwarding rule on a compromised mailbox.
How to fix it
- Check the rule is legitimate; attackers often add forwarding rules to hijacked mailboxes.
- To allow it, create a custom outbound anti-spam policy in Microsoft Defender for just those users with automatic forwarding set to On.
- Otherwise, remove the forwarding rule and share mail another way, such as delegate access.
Got a different message? Paste it into the error explainer.
Related errors
- 550 5.4.1 Recipient address rejected: Access denied · Microsoft 365 rejected an unknown recipient at the edge
- 550 5.7.708 Service unavailable. Access denied, traffic not accepted from this IP · Microsoft 365 blocked the tenant's outbound mail
- 530 5.7.57 Client not authenticated to send anonymous mail during MAIL FROM · The app sent to smtp.office365.com without logging in
- 535 5.7.139 Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant · Microsoft 365 refused the SMTP AUTH login
- 550 5.1.8 Access denied, bad outbound sender · The sending account was blocked for spam
- 451 4.7.500 Access denied, please try again later · Microsoft 365 is temporarily throttling the sending IP
- 552 5.2.2 The recipient's inbox is out of storage space · The recipient's mailbox is full
- 552 5.3.4 Your message exceeded Google's message size limits · The message is larger than the server accepts
- 535 5.7.8 Username and Password not accepted · The SMTP login was rejected
- 450 4.2.0 <user@example.com>: Recipient address rejected: Greylisted · The message was greylisted; it will be accepted on retry
- 553 5.7.1 <user@example.com>: Sender address rejected: not owned by user · You logged in as one user but sent as another address
- 530 5.7.0 Must issue a STARTTLS command first · The server requires TLS before it accepts mail