Gammadyne Corporation

Relaying Denied

"Relaying" is when you send email to one mail server, expecting it to pass the email on to its intended recipient who resides on a different mail server (known as "non-local email").  A mail server will produce a "Relaying Denied" error when an unauthorized user attempts to send non-local email.

The server error comes in many forms.  Here are some of the most common ones:

550 Relaying denied
550 Relay not permitted
550 Relaying not allowed
550 5.7.1 Unable to Relay
550 5.7.1 <>... Relaying denied
553 SMTP Relaying Denied
553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)
554 <>: Relay access denied

Mail servers will not relay mail from just anyone.  Otherwise, spammers could flood the mail server, making it do their dirty work.  You must be authorized to use a mail server for relaying.  Unauthorized users will always receive the "Relaying Denied" error.

Preventing "Relaying Denied"
To use a mail server, you must prove to the mail server that you are authorized to send email.

  • By far the most common cause is that no user name and password were specified.  In Gammadyne Mailer, these fields are on the Servers/SMTP branch under "SMTP Authentication".  The user/password is often the same as for your email account, although sometimes the SMTP server has separate credentials.  If authentication is failing, you will need to contact the SMTP server's administrator.
  • This error can sometimes be circumvented by first checking for incoming email.  Some servers are smart enough to recognize that when you are properly authenticated to receive mail, then you should also be able to send mail.
  • Sometimes the Sender of the email is required to be a user on the server.  The Sender is where bounce-backs are sent when the email is undeliverable (it appears in the "MAIL FROM" SMTP command).  Most email programs always use the From: or Reply-To: header for the sender, and do not allow it to be specified.  In Gammadyne Mailer, it can be changed with the "Sender:" field on the "Headers" branch.
  • The "From:" header may need to be a user that is local to the SMTP server.  If the server is really restrictive, the From: header may need to be identical to the SMTP user name.  In other words, if you are logging on to the SMTP server with the account, then the From: header needs to be
  • If the mail server is on a Local Area Network, it may be necessary to specify the mail server's local IP address, not its name.
  • If the mail server belongs to your ISP, it is possible that the mail server will only relay mail for users that are currently connected to the ISP.  If you want to be able to send mail when using a different connection, you will need to ask your ISP if "SMTP authenticated login" is supported.  If it is, they will give you a user name and password.  In Gammadyne Mailer, this must be entered on the Servers/SMTP branch under "SMTP Authentication".
  • Occasionally, a mail server may require that the email program say hello properly.  This corresponds to the HELO/EHLO command in the SMTP protocol.  The mail server may require that this command reports a proper domain name that is authorized to send email.  Even though this practice is discouraged, some mail servers perform this check as a form of spam prevention.  In Gammadyne Mailer, this corresponds to the "Override EHLO Domain" field on the Send/Delivery branch (uncheck "Hide Advanced Settings" on the Options menu first).

Direct Delivery
The only other solution is to not use the mail server at all.  When using Gammadyne Mailer, you can check the "Direct Delivery" box on the Send/Delivery branch.  This will bypass the SMTP server altogether, and deliver each email directly to the recipient.  This has the additional benefit of eliminating a point of failure.  However, please read the entire article on Direct Delivery so that the disadvantages are understood.

Related Errors

450 Relaying temporarily denied. Cannot resolve PTR record for

550 5.7.1 <>... Relaying denied. IP name lookup failed []

This can occur if there is no "Reverse-DNS" record for your computer's IP address.  This is also known as a PTR record.  It converts an IP address to a domain name, such as "".  Normally this is something that your Internet Service Provider is responsible for providing.  So if you confirm that there is no PTR record for your IP address, you will have to ask your ISP's support department if they can provide one.

550 Relaying denied. IP name possibly forged

In this case, the PTR record does exist.  However, when the server queries the A record for the domain named in the PTR record, it does not match the original IP address.  To the mail server, it looks like you are trying to disguise your identity.  You need to fix your A record, or create one if it does not exist.