General discussion

Locked

Unable to Relay

By quintar51 ·
I'm getting 'Unable to relay' anytime I try to send email to @"mydomain.com". I have 2 machines, one is my DC with DNS installed, the other is my Exchange 2000 server. I also have a 3rd machine, which is a client.

I went through several articles in MS. Looked at 323669, which involved recreating a key in the Metabase in IIS.

Also went through 289553, which makes sure my recepient policy includes @"mydomain.com".

My DNS does have an MX record pointing to my Email server. What else am I missing??

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Unable to Relay

by larboz In reply to Unable to Relay

I deal with this often in my job. I have found that most often this occurs when you are recieving an e-mail from 1 pop server and sendin out through a unrelated smtp server. make sure the the reply to address is the address that you use on the smtp server and then see if you can change that somewhere else (web gui if there is one) hope this helpes some. relay error is spam prevention so you see this often.

Collapse -

Unable to Relay

by quintar51 In reply to Unable to Relay

I only one have mail server I'm sending to and trying to receive from, which is my email server. Where can I check for the 'reply-to-address' in Exchnage?

Collapse -

Unable to Relay

by quintar51 In reply to Unable to Relay

Just wanted to add that I am able to send mail internaly, but not from outside my domain. Also, is the problem strictly on my end, or does my ISP also come into play here? As part of the 'unable to relay' error message, it does show my correct IP address, so I would assume that the problem is strictly on my end.

Collapse -

Unable to Relay

by CG IT In reply to Unable to Relay

sending to and from on a intranet means you've got the Exchange/DNS configuration correct. trying to send yourself email to and from a workstation and getting a "unable to relay" means that Exchange can not find a means to send the email to another mail server and have that mail server send the message back to your mail server. [Every email server denies relaying now a days. If they don't they will get blacklisted as spammers will find it and abuse the relay capabilities]. What I do to test inbound and outbound message capabilities is to send a email to my dummy hotmail account. I can have a workstation next to me and have hotmail open, send a email to that account via Outlook on the server and watch for the mail to arrive into my hotmail account. I then send it back and watch for it to come into my Outlook mailbox. That circumvents the relay blocking.

Collapse -

Unable to Relay

by CG IT In reply to Unable to Relay

to clarify, if your trying to send mail addressed to user@mydomain.com from user@mydomain.com your mail server has to find another mail server which will accept the mail and foward it back to your mail server [relaying]. There isn't a loopback SMTP connector which will allow you to send mail to yourself, or in other words, your mail server can not create a SMTP port 25 connector to itself to send mail to itself. Hense the need to find a mail server to connect to and ask it to relay the email back to it. All Email servers deny relaying due to spam.

Collapse -

Unable to Relay

by CG IT In reply to Unable to Relay

that is why you can send mail intranet as it's addressed to a different account but not send it to yourself without relaying through another server. Relaying is like addressing mail to the postmaster at a post office in another city with another letter inside addressed to someone else. The postmaster postmarks the letter from his post office, then fowards that mail to whom ever. Who ever gets the letter sees the postmark from the postmaster's post office and not your postmark from your city's post office therefore the original location of the letter is unknown. In email, it's the same principle.

Collapse -

Unable to Relay

by CG IT In reply to Unable to Relay

it's also possible that your ISP has put a block on port 25 to unknown email servers[to prevent unknown mail servers from connecting to it][another spam prevention measure]. If mail is being bounced back as a NDR, that's probably because @mydomain.com isnt a FQDN therefore doesn't have a name server listing in WHOIS. So when your ISP tries to find a "registered" name server that knows who is @mydomain.com to find the address and the appropriate MX pointer record it comes up blank. No one knows WHOIS @mydomain.com therefore sorry no mail and it's returned NDR.

Collapse -

Unable to Relay

by quintar51 In reply to Unable to Relay

It seems that I manage to fix the relay problem for now using article q293800. I configured the Default SMTP Server in IIS on my DC and added a new domain, and specified 'Allow the Incoming Mail to be Relayed to this Domain', and configured my Email Server as the Smart Host. However, now, I'm just not receiving the mail on my clients. I also ran the SMTP test from Microsoft (using telnet) and it 'sent' mail successfully. The mail though, does not show up when I check it on the client machine. (This is not going very smoothly for me).

Collapse -

Unable to Relay

by quintar51 In reply to Unable to Relay

Point value changed by question poster.

Collapse -

Unable to Relay

by quintar51 In reply to Unable to Relay

okay, regarding my 2nd issue, where my mail is not being received by any of the clients, I figured out that my DC/DNS server receives it, and keeps it in c:\mailroot\queue directory.

- How do I configured my Exchange server to pick up mail fromthis directory?

I'll appreciate any suggestions. Thanks.

Back to Software Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums