πŸ“„
Webhosting

Resolving Relay Access Denied When Sending Email

πŸ“… 11 November 2026 ✏️ 11 November 2026 ⏱ 5 min leestijd

Getting the ‘Relay Access Denied’ error message when sending email? Read here what this means and how to resolve it step by step.

The error message Relay Access Denied means that the mail server refuses to forward your message to the recipient, because you are not correctly authenticated or because your mail program is using the wrong settings. You usually resolve this by checking the SMTP authentication, using the correct port, and checking whether your IP address is not accidentally being rejected by the server.

What exactly does Relay Access Denied mean

A mail server does not simply send email for anyone who asks: that would give spammers free rein. A server only allows ‘relay’ (forwarding your message to another domain) if you have proven that you are allowed to send through that server. You provide that proof with a username and password when sending (SMTP authentication). If that authentication is missing, or something is not right in your settings, the server refuses the message and you receive the Relay Access Denied message back.

This is therefore not a problem with the recipient or your internet connection, but with the connection between your mail program and the outgoing mail server.

Common causes

There are a number of situations that repeatedly lead to this error message:

  • Your mail program has not checked ‘SMTP authentication required’.
  • You are using the wrong port for outgoing mail (for example port 25 instead of 465 or 587).
  • Your password has been changed, but not updated in your mail program.
  • You are sending mail via a network (such as a business wifi network) that the server does not recognize as trusted.
  • The server does not (temporarily) recognize your IP address as authorized, for example after switching providers.
  • You are using the wrong sender address, which does not belong to the account you are logged in with.
πŸ’‘ Tip: Always first test whether logging in to webmail does work. If that works fine, you know for sure that the problem lies in your mail program’s settings and not with the account itself.

Step by step solution

1

Check SMTP authentication

Open your mail program’s server settings and make sure that for the outgoing server (SMTP) the option ‘login required’ or ‘authentication’ is enabled, with the same email address and password as your incoming server.

2

Check the correct port and security

Use port 587 with STARTTLS, or port 465 with SSL for outgoing mail. Port 25 is blocked by many internet providers or not accepted for authentication.

3

Compare sender address and login account

Make sure that the sender address exactly matches the account you are logging in with. A mismatch here often leads directly to a rejection.

4

Re-enter the password in your mail program

If the password has recently been changed, re-enter it on every device and every mail program you send with, including phone and tablet.

5

Check whether your IP is not blocked

Check in your hosting panel (for example Plesk, under mail or security settings) whether your IP address has not accidentally been blocked after multiple failed login attempts.

How to prevent this in the future

Where possible, set up your mail program automatically via your provider’s setup wizard, instead of manually entering ports and servers: this prevents typos. Store passwords in a managed password vault so you can consistently fill them in everywhere after a change. When using a new internet connection or mobile network, immediately check whether sending still works, so you don’t only notice something is wrong when an important message fails to arrive.

Not sure whether your business email is set up correctly, or want to switch to a provider with clear mail configuration? Then check out the options for business email or read how you can smoothly switch to Tandata without hassle with your existing mail accounts.

Frequently Asked Questions

Why does sending work at home, but not at the office?

Some business networks block certain SMTP ports or have their own firewall that filters outgoing mail. In that case, consult with your network administrator or try a different port (587 instead of 465).

Can I test this problem myself without a mail program?

Yes, log in to your domain’s webmail environment. If sending works there, the problem lies with your mail program’s settings and not with your account or password.

Is Relay Access Denied the same as a bounce message?

No. With Relay Access Denied, your message is immediately rejected by your own outgoing server, even before it is on its way. A bounce occurs after a message has already been sent, but could not be delivered to the recipient.

Conclusion

Relay Access Denied almost always points to an authentication or settings problem between your mail program and the outgoing server. Check SMTP authentication, the port used, and whether the sender address matches your login account, and the problem is usually quickly resolved. If you get stuck, the knowledge base can help you further or you can contact support directly.

View web hosting β†’

Was dit artikel nuttig?