General discussion

Locked

Exchange prob - with relay not allowed

By chipw ·
I installed MS Exchange 2000, have DNS working and AD set up, ran netdiag and dcdiag and both passed on everything they check. When I try to send a test email I get the following error -
550 5.7.1 Unable to relay. I read MS article 289553 and don'tquite understand instruction 4 -

"In the SMTP Address Properties dialog box, in the Address field, enter @expecteddomain.com where @expecteddomain.com is the domain that then sender is attempting to send to. Click Apply, and then click OK."

AsI understand this statement, I would have to add every domain that email will ever be sent to, this is not right at all. How many thousands of domains would I have to list here, too many. I obviosly don't understand something here correctly.

Could someone please shed some light on this for me?

This conversation is currently closed to new comments.

34 total posts (Page 2 of 4)   Prev   01 | 02 | 03 | 04   Next
Thread display: Collapse - | Expand +

All Comments

Collapse -

Exchange prob - with relay not allowed

by CG IT In reply to Exchange prob - with rela ...

[continued] server for the W2K Exchange server which would be a backend server. There is a great book by micosoft for exchange server [Microsoft Exchange 2000 Server Implementation and Administration Training Kit which includes a setting up a physical test bed using W2K AD and NT servers, Bridgehead mail servers, and the lot. I highly recommend it and it's well worth the $ spent on it. It goes into exactly what your trying to do, step by step.

Collapse -

Exchange prob - with relay not allowed

by chipw In reply to Exchange prob - with rela ...

DR,
I found a book at Barnes and Noble called MCSA/MCSE Training Kit: Microsoft Exchange 2000 Server Implementation and Administration
by Kay Unkroth, Microsoft
Is this the book you are referring to?

Collapse -

Exchange prob - with relay not allowed

by curlergirl In reply to Exchange prob - with rela ...

DR's got some pieces of the puzzle - his test will definitely tell you if your Exchange server and the SMTP server on it are working correctly. As far the internal piece of the email puzzle, you need to have a trust relationship between the domains, you need to have AD accounts on your Win2K server matching the NT network user id(s) that you are using to test, and the AD accounts need to have mailboxes set up. I'm not assuming anything here - you might already have all this in place, but I'm just making sure. When you say the trust relationship is "working by default", does this mean that you have actually set up a trust relationship or only that browsing is working between the two domains. In order to send or receive email through theWin2K domain, there has to be an actual trust relationship established between the two domains so that the Win2K domain can authenticate the users from the NT domain. This is done on the NT machine in User Manager for Domains, and on the Win2K machine in AD Domains and Trusts.

It appears your internal DNS is OK, if you can browse both externally and internally. If you can also browse and ping by name on both domains to the other domain, then you're definitely OK. However, you do need to be sure that there is an MX record somewhere (either on your own DNS servers, if they are authoritative for your domain, or on your ISP's DNS servers, if they are the authoritative ones) that points back to whatever external IP address is accessible to your Exchange server. If it's behind a firewall, you need to make sure that the firewall has the SMTP port 25 open.

Does this all check out?

Collapse -

Exchange prob - with relay not allowed

by chipw In reply to Exchange prob - with rela ...

First, telnet cannot connect to port 25 on the server from a remote client machine on the other network (or the server itself).
Second, I attempted to add an MX record on our DNS server but it will not register. I verified my settings with the helpfile, there's only two required and a third optional setting. The DNS server is an NT box. Error message:
Unable to register the record - please check your settings and try again. No matter how I put in the name of the server it will not register.Third, the trust relationship is now set up properly on both networks. Previously, I could see both networks through Net Neighborhood, just hadn't actually set up the trust relationship.
Fourth, ping by name machines on both networks works fine.

Collapse -

Exchange prob - with relay not allowed

by LordInfidel In reply to Exchange prob - with rela ...

Read your last comment about not being able to connect via 25 remotely.

That you need to look at your firewall. Make sure your says:

From ANY tcp <=1024 to your mail server tcp 25

And a inverse rule
From mail server tcp <=1024 to ANY tcp 25

Also on the mail server, make sure you can do DNS queries (not sure if that was asked before) Just do a nslookup, set type=mx and see if you can resolve yahoo or aol.

The unable to relay means that you need to set up the domains that are able to "relay" thru your mail server.

Every mail server does what is called Relay mail. It takes a piece of e-mail and then routes it to another server.

Now if left unchecked, any domain can route thru your mailserver; that is any one can send any piece of mail to your mail server, and your mail server will deliver, regardless of where it is being sent to.

So to close this off, you stop relaying except from either A) specified domains, B)IP's or subnets.

This then tells the mail server to only accept relay requests from trusted sources. So if you have a domain called mydomain.com

You then only want mydomain.com to be able to relay thru your mail server. If you have multiple domains, you have to add those in as well.

It does not mean that you add domains where to are sending "to". You add domains that you are sending "from".

That is how you stop the relay message.

Collapse -

Exchange prob - with relay not allowed

by chipw In reply to Exchange prob - with rela ...

Poster rated this answer

Collapse -

Exchange prob - with relay not allowed

by CG IT In reply to Exchange prob - with rela ...

yep That's the book! and well worth the $ spent on it. Lordinfidel also makes a very good point in adding domains to send mail FROM. Not TO. Further, if you can not telnet port 25, you have a problem with your configuration. The command set local_echo is like a loopback request to Exchange to open a connection [see Chapter 2 Intergration with Microsoft Windows 2000 , page 61 Checking the SMTP service, of Kay Unkroth's MCSE Microsoft Exchange 2000 Implementation and Administration Training kit [the one you found and hopefully bought].

Suggestion, Take the bloody server off your corporate network and run it stand alone until you get a good configuration running ADDING it to the corporate domain once it's configured properly and sending email back and forth from the server Outlook to a workstation Outlook and back.

I'll also direct you to Windows & .Net magazine and Windows Exchange Magazine forums. [I'll add a comment with the URL's for them. There is one forum strickly for Exchange 2000 Servers. Good source to ask questions, get answers.

Collapse -

Exchange prob - with relay not allowed

by CG IT In reply to Exchange prob - with rela ...

PS: you can add comments to answerers without rejecting answers and keep the question open by adding in comments to your question. I get more rejection of answers from questioners simply answering their initial question and finding out that their initial question didn't give enough information and wasn't really the problem they had.

Collapse -

Exchange prob - with relay not allowed

by CG IT In reply to Exchange prob - with rela ...

The Windows & .Net Magazine forums URL is http://www.winnetmag.com/forums/categories.cfm?catip=40

I've found them useful when I've had problems both with the servers and mail servers.

Collapse -

Exchange prob - with relay not allowed

by CG IT In reply to Exchange prob - with rela ...

ok in Lesson 3 page 26-27 coexistence with other messaging systems page 28 figure 1-14 shows a graphical depiction of how Exchange 2000 interfaces with other Mail services like Novell Groupwise. Exchange 5.5, ..also test bed with NT4 PDC's is on XIVii.

Yes, you can run Exchange mail system no on a PDC but Exchange HAS to have AD [to create mailboxes for user accounts when an user account is created.

Back to Software Forum
34 total posts (Page 2 of 4)   Prev   01 | 02 | 03 | 04   Next

Related Discussions

Related Forums