Home Download Learn more Tech Help

550 relay not permitted error

The error "550 relay not permitted" or "554 relay access denied" means a mail server won't accept outgoing (SMTP) mail from the sender. This is part of how mail servers protect themselves from spam and forged messages. There are several reasons that the error can happen.

If none of your mail goes out:

Your mail client or server is set up for a different form of authentication. The solution is to set up your mail client or server to use a verification method that standard Tiger Envelopes supports, or switch to Business Envelopes.

Standard Tiger Envelopes supports

POP before SMTP
IMAP before SMTP
IP address verification

Tiger Business Envelopes supports these and others such as ESMTP AUTH.

Your mail client is trying to send a message using a server that you don't have permission to use. Almost all mail servers only accept mail from users that have accounts with the mail server's host.
Your mail client is using the right mail server, but it's not authenticating itself to the server properly. For example, you might need to check your mail immediately before you send a message, or use the more advanced configuration options, such as user/password authentication for SMTP.
You are using an IP address that your mail server doesn't expect. Many service providers only accept outgoing messages from their own IP addresses.
The host name of your own machine is not available via reverse DNS. Some mail servers insist that it is.

If your mail to most places is working fine:

One of the mail servers that your mail server is talking to sent back the "relay not permitted" error and your server just passed it back to you.
Someone has launched an attack on a particular site. This appears to be what happened to Mailvault.

Usually it means you need to use a mail server that you have permission to use and configure your mail client for it correctly. Otherwise, you might try using a different outgoing mail server if you can to see if that server can successfully communicate with the downstream server.

Go back to the Support FAQ