Solved

why do I get this error

Posted on 2008-10-18
8
430 Views
Last Modified: 2012-05-05
I have a newly built domain server 2003 with active directory and DNS and DHCP and a newly built exchange server 2003 currently I have 1 active account in AD to test exchange, the account can send mail internally but cannot send to an external account and cannot recieve e-mail from and external account, when I send an e-mail from an exrenal account I get the following error 550 5.7.1 Unable to relay for... I have tried surfing this error and am now completely confused as all the setting they mention I have checked like relaying adding the domain IP Addresses and domain into the Only the below list but still cannot send and recieve can anyone help
0
Comment
Question by:Liono
  • 5
  • 3
8 Comments
 
LVL 31

Expert Comment

by:Henrik Johansson
ID: 22749985
The relay error for outgoing mail depends on DNS not matching forward and reverse resolving.
If you can manage the external DNS by your self create a PTR-record for the external IP pointing on the hostname. If you can't manage the external DNS by yourself, you nead to call your ISP.

If not receiving incoming mail, you nead to create a MX-record in your external domain to let others know what server the mail shall be delivered to.
0
 

Author Comment

by:Liono
ID: 22750044
I am using afraid.org as dns supplier
this is my DNS from them
6 subdomains
sos-consultancy.co.uk
 
 sos-consultancy.co.uk (G) A 78.32.153.131
 sos-consultancy.co.uk (G) MX 10:net-04.sos-consultancy.co.uk
 sos-consultancy.co.uk (G) MX 10:net-04.sos-consultancy.co.uk
 ftp.sos-consultancy.co.uk (G) A 78.32.153.131
 irc.sos-consultancy.co.uk (G) A 78.32.153.131
 net-04.sos-consultancy.co.uk (G) A 78.32.153.131

 thisseem to be extensive for one domain is this right or wrong


0
 
LVL 31

Expert Comment

by:Henrik Johansson
ID: 22750099
Is net-04 the mail server?
'nslookup 78.32.153.131' results as mail.sos-... instead of net-04. The PTR-record for 78.32.153.131 nead to be updated.

Another incorrect thing not related to the mail problem is that there's A-record for the aliases (irc,ftp) instead of CNAME-records (aliases) pointing on net-04
0
 

Author Comment

by:Liono
ID: 22751347
how can I get Net-04 which is my mail server to accept mail from Mail.sos-consultancy.co.uk and if I cannot do this the PTR -record that I need to change is that at my end or the ISP
0
Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

 
LVL 31

Expert Comment

by:Henrik Johansson
ID: 22751919
The PTR nead to be changed in the external DNS to get rid of the relaying error. If you can't do it by yourself, you nead to contact the ISP
mail.sos-... doesn't exist in the external DNS, so you can't send to @mail... from an external host.
The MX-record makes mail sent to @sos-consultancy.co.uk to arrive at net-04
0
 

Author Comment

by:Liono
ID: 22989725
OK so now I have rebuilt the exchange server and have tested using SMTPDIAG with the results below but I still cannot send or recieve mail although the smtp test say all is ok. I don't know why I get the following error

pjsoyza@sos-consultancy.co.uk
SMTP error from remote mail server after RCPT TO:<pjsoyza@sos-consultancy.co.uk>:
host mail.sos-consultancy.co.uk [78.32.153.131]:
550 5.7.1 Unable to relay for pjsoyza@sos-consultancy.co.uk
I have come to the conclusion that exchange is really nuts

I can nslookup and get the below results

> set type=mx
> sos-consultancy.co.uk
Server:  net01.sos-consultancy.co.uk
Address:  192.168.0.5

sos-consultancy.co.uk   MX preference = 10, mail exchanger = mail.sos-consultanc
y.co.uk
mail.sos-consultancy.co.uk      internet address = 192.168.0.7

C:\SMTP>smtpdiag peter.soyza@ace-ina.com pjsoyza@sos-consultancy.co.uk -d 78.32
153.131 /v

Searching for Exchange external DNS settings.
Computer name is IBM-01.

Checking SOA for sos-consultancy.co.uk.
Checking external DNS servers.
Checking internal DNS servers.

Checking TCP/UDP SOA serial number using DNS server [192.168.0.5].
TCP test succeeded.
UDP test succeeded.
Serial number: 144
SOA serial number match: Passed.

Checking local domain records.
Starting TCP and UDP DNS queries for the local domain. This test will try to
validate that DNS is set up correctly for inbound mail. This test can fail for
3 reasons.
    1) Local domain is not set up in DNS. Inbound mail cannot be routed to
local mailboxes.
    2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound mail,
but will affect outbound mail.
    3) Internal DNS is unaware of external DNS settings. This is a valid
configuration for certain topologies.
Checking MX records using TCP: ace-ina.com.
  MX:    cluster5.us.messagelabs.com (10)
  MX:    cluster5a.us.messagelabs.com (20)
  A:     cluster5.us.messagelabs.com [216.82.253.19]
  A:     cluster5.us.messagelabs.com [216.82.253.163]
  A:     cluster5.us.messagelabs.com [216.82.242.147]
  A:     cluster5.us.messagelabs.com [216.82.242.67]
  A:     cluster5.us.messagelabs.com [216.82.250.51]
  A:     cluster5.us.messagelabs.com [216.82.241.227]
  A:     cluster5.us.messagelabs.com [216.82.250.99]
  A:     cluster5.us.messagelabs.com [216.82.253.3]
  A:     cluster5a.us.messagelabs.com [216.82.242.67]
  A:     cluster5a.us.messagelabs.com [216.82.250.51]
  A:     cluster5a.us.messagelabs.com [216.82.241.227]
  A:     cluster5a.us.messagelabs.com [216.82.248.44]
  A:     cluster5a.us.messagelabs.com [216.82.248.45]
Checking MX records using UDP: ace-ina.com.
  MX:    cluster5a.us.messagelabs.com (20)
  MX:    cluster5.us.messagelabs.com (10)
  A:     cluster5a.us.messagelabs.com [216.82.250.51]
  A:     cluster5a.us.messagelabs.com [216.82.241.227]
  A:     cluster5a.us.messagelabs.com [216.82.248.44]
  A:     cluster5a.us.messagelabs.com [216.82.248.45]
  A:     cluster5a.us.messagelabs.com [216.82.242.67]
  A:     cluster5.us.messagelabs.com [216.82.253.163]
  A:     cluster5.us.messagelabs.com [216.82.242.147]
  A:     cluster5.us.messagelabs.com [216.82.242.67]
  A:     cluster5.us.messagelabs.com [216.82.250.51]
  A:     cluster5.us.messagelabs.com [216.82.241.227]
  A:     cluster5.us.messagelabs.com [216.82.250.99]
  A:     cluster5.us.messagelabs.com [216.82.253.3]
  A:     cluster5.us.messagelabs.com [216.82.253.19]
Both TCP and UDP queries succeeded. Local DNS test passed.

Checking remote domain records.
Starting TCP and UDP DNS queries for the remote domain. This test will try to
validate that DNS is set up correctly for outbound mail. This test can fail for
3 reasons.
    1) Firewall blocks TCP/UDP queries which will block outbound mail. Windows
2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP
queries first, then fall back to TCP queries.
    2) Internal DNS does not know how to query external domains. You must
either use an external DNS server or configure DNS server to query external
domains.
    3) Remote domain does not exist. Failure is expected.
Checking MX records using TCP: sos-consultancy.co.uk.
  MX:    mail.sos-consultancy.co.uk (10)
  A:     mail.sos-consultancy.co.uk [192.168.0.7]
Checking MX records using UDP: sos-consultancy.co.uk.
  MX:    mail.sos-consultancy.co.uk (10)
Both TCP and UDP queries succeeded. Remote DNS test passed.

Checking MX servers listed for pjsoyza@sos-consultancy.co.uk.
Connecting to mail.sos-consultancy.co.uk [192.168.0.7] on port 25.
Received:
220 Mail.SOS-Consultancy.co.uk Microsoft ESMTP MAIL Service, Version: 6.0.3790.
959 ready at  Tue, 18 Nov 2008 22:03:31 +0000


Sent:
ehlo ace-ina.com

Received:
250-Mail.SOS-Consultancy.co.uk Hello [192.168.0.10]
250-TURN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-X-EXPS GSSAPI NTLM LOGIN
250-X-EXPS=LOGIN
250-AUTH GSSAPI NTLM LOGIN
250-AUTH=LOGIN
250-X-LINK2STATE
250-XEXCH50
250 OK


Sent:
mail from: <peter.soyza@ace-ina.com>

Received:
250 2.1.0 peter.soyza@ace-ina.com....Sender OK

Sent:
rcpt to: <pjsoyza@sos-consultancy.co.uk>

Received:
250 2.1.5 pjsoyza@sos-consultancy.co.uk

Sent:
quit

Received:
221 2.0.0 Mail.SOS-Consultancy.co.uk Service closing transmission channel

Successfully connected to mail.sos-consultancy.co.uk.

0
 

Accepted Solution

by:
Liono earned 0 total points
ID: 23275066
this fixe my excgnage issue the problem was with the external DNS I changed the DNS servers and all working
0
 

Author Comment

by:Liono
ID: 23275070
all now working external DNS was wrong
0

Featured Post

Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now