SMTP Error (state 13): 550 5.7.1 Unable to relay : error, smtp, 550, relay, unable

Do you send email out directly on Exchange or through a smart host?

Simon.

08.19.2007 at 09:59AM PDT, ID: 19726297

Simon,

I'm sending out directly on Exchange

Corey

08.19.2007 at 10:18AM PDT, ID: 19726347

chafer:

This is by design. Here is why. When you send from another network, you are relaying through the Exchange server from another network. If you opened the relay, you would be an open relay, spammers would take over your server, and you would be blacklisted. By default, Windows 2000 Server had open relays that had to be closed. Windows 2003 inproved security and closed relays by default.

If you want to relay, you have several choices. If the relays are coming from known static IP addresses, you can open relay just to those addresses. An example of this is when a company has a web server that is hosted and an Exchange server on the internal network. It is common to allow the web server to relay e-mail through the Exchange server. You simply go into the relay settings and specify the server name. HOWEVER, DO NOT OPEN RELAYING IN GENERAL OR YOUR SERVER WILL GRIND TO A HALT WHEN THE SPAMMERS TAKE IT OVER.

The best way to allow remote users to send maill through the Exchange server is to either use Outlook Web Access or a VPN connection and open the mail client using the VPN as the conduit. In either case, the user is authenticated by the domain and can send mail.

08.19.2007 at 10:23AM PDT, ID: 19726357

chafer:

As a follow-up, if you have to open relaying for a specific static address, do this. Open Exchange System Manager. Under servers, open your server name, then protocols > smtp > default virtual protocol (this assumes that you are not routing mail through a separate connector). Right click, go to properties, the hit the access tab. Under that, look for relay restrictions and click on relay. You can then add specific addresses to allow relaying. Do not open relaying to everyone on the Internet or your server will become useless.

08.19.2007 at 10:58AM PDT, ID: 19726416

I just opened the relay as a test to see if I was able to sent from my gmail account to my internal account and receive the same SMTP Error (state 13)

08.19.2007 at 11:01AM PDT, ID: 19726422

I also tried adding a few ip addresses from outside and got the same error

08.19.2007 at 11:07AM PDT, ID: 19726439

Rank: Savant

You don't have to do anything with the relay settings. No idea what the expert above is on about.

If you are replying to messages within Exchange, so either from Outlook or OWA you do not have to do anything with the relay settings.
I presume that you have tested this through OWA?

I am also pretty sure that is NOT an Exchange message, it is being generated by something else. That could be AV, Antispam or something on the firewall.
Again I am presuming there that everything is setup correctly, Outlook is being used configured to talk to an Exchange server and not a POP3/IMAP/SMTP server.

Whatever you have done to your relay settings, undo it as you have probably turned the server in to an open relay, which is a security risk.

Simon.

08.19.2007 at 11:38AM PDT, ID: 19726511

I changed the settings back after sending a test email from outside and got the same error. I think it's not an exchange issue either. My ISP has port 25 open forwarding it to my internal router and my internal router is setup to forward the request to my exchange server

08.19.2007 at 12:01PM PDT, ID: 19726575

Rank: Savant

Have you got message tracking enabled? That will show you what Exchange is doing with the message.

You need to work out what server is generating the message.

Simon.

08.19.2007 at 04:29PM PDT, ID: 19727360

I gave that a go and received this error:

The tracking database on ServerName.Domain.com is not available or the message has left the Exchange Organization

08.19.2007 at 07:17PM PDT, ID: 19727825

Rank: Savant

Was message tracking enabled? It sounds like it is not.
You need to enable on the properties of the server itself in ESM. That will then show if Exchange is sending the message out or not.

Simon.

08.19.2007 at 11:41PM PDT, ID: 19728539

Sending mail off SMTP ports may be blocked on your server by a firewall or Antivirus software. These two programs block these ports to prevent mass-mailing worms. Have you tried temporarily disabling either of those programs to see if either of these programs are causing the problem.

Also if you are using ISA, you may need to set up a rule to allow SMTP traffic through your ISA firewall.

08.20.2007 at 05:21PM PDT, ID: 19734718

Simon,

I successfully enabled message tracking and it shows the message was transferred to mx.google.com. I did receive the email in my gmail account, but once again when I reply to the email from my gmail account I receive the same PERM_FAILURE: SMTP Error (state 13): 550 5.7.1 Unable to relay for

I'm able to send internally and externally, the error occurs when I try to reply from an external email account.

08.20.2007 at 06:08PM PDT, ID: 19734883

meanyogurt:

I've experienced this before. Check to make sure ALL of your mail servers have proper MX records and verify what accounts are recieving/sending the message in Outlook.

08.21.2007 at 03:22AM PDT, ID: 19736473

check your queues. I don't know if Exchange server has sendmail switch. If so, redeploy sendmail switch. and reissue certificates.

08.21.2007 at 03:23AM PDT, ID: 19736477

Also see if the SMTP service has stopped on your server.

08.21.2007 at 04:26AM PDT, ID: 19736731

I just double checked and the MX record has the mail servers name. I also checked the SMTP service and it's up and running. I looked into the queue and wasn't able to find any messages.

08.21.2007 at 04:32AM PDT, ID: 19736776

Rank: Savant

The message you are getting is not an Exchange message. It is being generated by something else. What depends very much on the path that the messages take when they leave the server. It could be AV or Antispam software, a firewall or something outside of your network.

Simon.

08.21.2007 at 12:46PM PDT, ID: 19740919

Have you tried to send from a remote mail server and checked the headers of that message to see where it was rejected?

SPAM blockers sometimes see excessive messages from a particular mail user or domain and automatically block the mailer and/or domain from sending traffic to your mail server. The easiest way to tell is by going to a remote email account and looking at the full headings of that email. It will say rejected by XXX.YYY.ZZZ mail server.

08.21.2007 at 08:06PM PDT, ID: 19743172

I tried from another mail server and got the error below

The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.

08.22.2007 at 01:12AM PDT, ID: 19744301

Rank: Savant

That message means what it says.
The email address doesn't exist. However as it isn't clear what you tried from another mail server it is impossible to diagnose further.

Simon.

08.22.2007 at 08:33PM PDT, ID: 19751409

My mail servers are not Exchange server. I am soon transfering my mail servers to Exchange and wanted to see issues with Exchange server.

From what I see so farr, I can't see Exhange operating much differntly than what I use. There is a program called Sendmail Switch has been used by many mail servers to transfer mail back and forth. When I ran into a problem similar to this, the answer was to regenerate or update my certificates in the Sendmail program. We have to do this once every two years or all of a sudden we can't get incoming messages.

Does Exchange server Use Sendmail switch, I don't know????? If so, try regenerating your certificates.

08.27.2007 at 01:52AM PDT, ID: 19774295