Hello @idealynx,
Thank you for sharing the error message.
550 5.7.708 Service unavailable. Access denied, traffic not accepted from this IP
This response is coming from the remote SMTP/email service provider. It usually means their server is rejecting the connection or email traffic from your website/server IP address.
Could you please confirm which email service provider you are using with FluentSMTP? For example, Microsoft 365/Outlook, Google Workspace/Gmail, SendGrid, Mailgun, Amazon SES, etc.
Since this appears to be an IP reputation or provider-side restriction, we recommend reaching out to your email service provider’s support team and sharing the exact error message with them. They should be able to confirm why traffic from your server IP is not being accepted and advise the next steps to resolve it.
Thanks.
-
This reply was modified 1 week, 2 days ago by
Sujoy Chandra Das.
-
This reply was modified 1 week, 1 day ago by
Yui.
Hello @idealynx,
Thank you for reaching out to us! I am sorry to hear about the frustration you’ve experienced over the last few hours while setting up your email account.
The error message you received, “550 5.7.708 Service unavailable. Access denied, traffic not accepted from this IP,” is a direct response from your email service provider’s server. Essentially, this means the receiving server has blocked the connection from your specific SMTP server’s IP address. This typically happens due to the reputation of the IP address being used, rather than a configuration error within the FluentSMTP plugin itself.
To help us narrow this down and find the best path forward, could you please let me know:
- Which SMTP Connection type are you currently using (e.g., Amazon SES, SendGrid, Gmail, or a custom SMTP provider)?
- Are you experiencing this error across all outgoing emails, or is it specific to certain recipient domains?
Once we identify the connection type, we can determine if this is a temporary block or if we need to look into configuring a dedicated IP or a different authentication method to bypass these reputation filters.
Hello @ibrahimsharif, I’m using Microsoft 365 through GoDaddy. The problem affects ALL outgoing emails processed through FluentSMTP v2.4.0 using Send Test Email. Sending emails through the Microsoft 365 portal is NOT affected, which is why GoDaddy technical support is refusing to help me resolve this issue.
Prior to the introduction of FluentSMTP v2.4.0, configuring the email through your dashboard worked perfectly most of the time. Just so you know, GoDaddy handles the email, Cloudflare handles the domain, and Cloudways hosts the website.
Hello @ibrahimsharif,
I should also mention that the website we’re discussing was a migration from one domain to another. That said, I did update the Active Email Connections to the new domain and email address after I moved the website. Is that acceptable, or do you recommend deactivating or uninstalling the FluentSMTP plugin BEFORE the migration?
-
This reply was modified 1 week, 1 day ago by
idealynx.
@ibrahimsharif, does the “550 5.7.708 Service unavailable. Access denied, traffic not accepted from this IP” sometimes happen with newly created email accounts? I read that Microsoft recommends a 60-day tenant exclusion as a fix. Can I do that myself in EAC, Entra, or Defender?
Quick update: GoDaddy reviewed the Microsoft 365 account and believes the issue may be because the mailbox is newly created and is still being provisioned across Microsoft’s servers. They advised allowing 24–48 hours for provisioning to complete before testing FluentSMTP again.
Normal Outlook mail from the account works, while messages sent through FluentSMTP’s Microsoft 365/OAuth connection are accepted by Microsoft but subsequently rejected with 550 5.7.708 AS(7910).
Have you encountered this with newly created Microsoft 365/GoDaddy mailboxes before, where FluentSMTP/OAuth sending doesn’t work properly until Microsoft finishes provisioning the account?
I can now confirm that this was a Microsoft 365 email provisioning problem for new email accounts. Following GoDaddy’s advice, I waited 24 hours before trying another Test Email, and it succeeded. I just thought I would pass this along to any others who may be experiencing the same.
