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 1 of 4)   01 | 02 | 03 | 04   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Exchange prob - with relay not allowed

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

Background - we have an all NT network, this box is a win2k advanced server with exchange 2k, nothing else. I discovered E2K requires it is run on a PDC, no good for our network, so when I set up this box I made it a domain of its own, and its own PDC. This is a test box only at this point. I open outlook on another machine, set it up to use this test exchange server, compose a test email, send it to myself, it appears to be sent, no errors, but never shows up. I tried to send a message to anohter person in the company, same results. I tried to send to a person outside the company, and get Relay Not Allowed.
<gripe>
I have set up FreeBSD many times, it has email server built in, I can send a message from the command line or gui to anywhere, anybody, and it works. Why doesn't this pig of a program Exchange work with the default settings?
</gripe>

As you can tell, I'm not too happy with this whole experience. I just want/expect the #@#$@ program to work, that's all.

Collapse -

Exchange prob - with relay not allowed

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

It appears that your trying to send your testbed E2K mail via your company connection to the internet and that your company has it's own mail service [hense its own FQDN]. What appears to be happening is that the receiving end services see that yourtrying to relay via your companies mail service [because it sees the ip address as belonging to your company and not your testbed]and is dening your testbed email [antispam measure]. I believe if you tried a noncompany internet connection your E2K mail server would work. Also your ISP DNS resolution [IP to Domain name] basically says your company NT domain belongs at that IP address. You've created a seperate domain for your E2K test bed and your ISP DNS resolution says nope doesn't belong to that address, therefore the receiving mail service says must be bogus, must be relaying so deny traffic.[antispam measure].

Collapse -

Exchange prob - with relay not allowed

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

hope that helps. your problem really is your ISP DNS resolution where the FQDN it says belongs at that IP address is your company and not your test bed domain.So it appears your test bed is trying to relay through your company and just about ALL mail services now deny relaying because of the Spam Black Listing of relaying mail services.

Collapse -

Exchange prob - with relay not allowed

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

Okay, so maybe setting this test box up as a seperate domain is not the way to go. When I installed W2K there was an option to set it up as a domain by itself or a child domain of an existing domain. I didn't choose that because we cannot make this the PDC for the company. Can it be a PDC of a child domain without effecting the the production domain controller? If necessary, I'll reinstall everything just to get it working correctly.

Collapse -

Exchange prob - with relay not allowed

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

Why can't I submit a reply to your reply without any 'rating'? And still leave the question open? The only way to get my reply submitted was to set not acceptable. That makes no sense to me. Sorry, I'm not in the greatest of moods this morning because of the Exchange problems.

Collapse -

Exchange prob - with relay not allowed

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

Oh for cryin out loud, ignore the above comment. Only took the server about half an hour to post my comment.

Collapse -

Exchange prob - with relay not allowed

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

I think perhaps what you need to do, for the purposes of allowing your workstations in one domain to use an Exchange server in another domain, would be to set up a trust relationship between the two domains first. Once you've done that, you should be able to send email from your NT domain through the Win2K Exchange server. BTW, just to be sure you understand the diff, Exchange 2K does not have to run on a Win2K DC, but it has to have Active Directory, so it has to be on a Win2K domain. I runExchange in several locations on Win2K member servers that are part of a Win2K AD domain. (I can't resist the urge to "educate" - sorry. . .)

You also have to have DNS set up properly in your Win2K domain. For your purposes, the easiest thingto do would be to make sure that your Win2K DNS server is NOT set up as a root server, but only as an authoritative server for your Win2K domain (could use it for your NT domain, too, I guess, if you want to). This means you have to delete the rootentry (".") in your DNS zone. Then, you can set it up to forward to your ISP's DNS servers, so that all domain names will be properly resolved.

Hope this helps!

Collapse -

Exchange prob - with relay not allowed

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

The trust relationship appears to be okay by default - I can see, in network neighborhood, and access the W2K server from any NT machine. I'm confused on the DNS part. Browsing the web works on the server, that indicates it works. As for the setup, I'm not sure where/how to delete the root entry. My setup looks like this in the DNS MMC -
DNS
simrad-5
Forward Zones
simrad-exchange.com
(contains among some folders -
start of authority - points to itself name server - points to the company NT dns server
host - points to itself)
reverse zones
(none)

So what do I change?
Thanks for the help.

Collapse -

Exchange prob - with relay not allowed

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

What I didn't explain fully is that your ISP issues you an IP address and if it's a static line like T1 or T3 or a Static DSL line, your company FQDN is resolved to that IP address. NOT your test bed domain name [which you just made up and is probably not registered]. Unlike the USPS which will deliver physical mail to an address regardless of who it's addressed to, unless there is a fowarder listed, SMTP uses Name Servers which translates the ip address to a name. You test bed is trying to send mail with its domain name [but your companies ip address] and other mail servers see that. Because relaying is a "bad" thing "spammers" relay to hide their identity, the other mail servers your test bed is trying to make a connection with say "Nope" not gonna do it.

So, try the telnet test to see if Exchange can open port 25 to send a email. open a command prompt and type telnet.exe press enter
at the telnet prompt type set<space>local_echo press enter now type open<space><domainname><space>25 you should see the Microsoft Exchange Mail server and version #

This means that atleast exchange can open port 25 to be able to send out email. Then for intranet email, you'll have to create a couple of dummy AD user accounts [one on the DC and one on a workstation, connect a workstation to the test bed domain and then send a intranet email to the work station, and a reply to the DC and see if that works. If your planning on migration your NT network to a W2K with AD network, thereis a whole migration package available for that.

Collapse -

Exchange prob - with relay not allowed

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

Synergy has the last piece of the puzzle on creating a MX record on your NT domain DNS [or your ISP] to point to your test bed domain Exchange server [provided a two way trust has been established between the two domains and that the users accounts on the NT domain are all replicated to the W2K AD domain]. Once the MX records are in place on the authoritative DNS server and user accounts are all replicated to the W2K AD domain, then email sent to the W2K domain user accounts will be fowarded toit via the NT domain Email server. [the NT domain email server acts as a bridgehead].

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

Related Discussions

Related Forums