Solved

Can't send emails to some domains

Posted on 2006-07-06
13
894 Views
Last Modified: 2011-09-20
Hi Experts,

I have a problem with sending outgoing emails from my exchange to some specific domains, usually domains like (.co.uk - .co.ae - .net.sa)

I have a SMTP Connector setup on the Frontend Exchange and configured to use DNS and with an address Space of (*). When i ticked the (Allow messages to be relayed to these domains) the messages gone out but i can't keep this because i don't want to put my mail server in the street :)

How can this problem be managed without configuring my mail server for open relay ??
0
Comment
Question by:ashkaat
  • 7
  • 4
13 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 17049840
I am surprised that the setting fixed the problem.

Can you do nslookups on any of the domains that you are having problems with?

For example... microsoft.com:

C:\>nslookup
Default Server:  server.domain.co.uk
Address:  192.168.1.1

> set type=mx
> microsoft.com
Server:  server.domain.co.uk
Address:  192.168.1.1

Non-authoritative answer:

microsoft.com   MX preference = 10, mail exchanger = mailc.microsoft.com
microsoft.com   MX preference = 10, mail exchanger = maila.microsoft.com
microsoft.com   MX preference = 10, mail exchanger = mailb.microsoft.com

maila.microsoft.com     internet address = 131.107.1.7
maila.microsoft.com     internet address = 131.107.1.6
mailb.microsoft.com     internet address = 131.107.3.123
mailb.microsoft.com     internet address = 205.248.102.77
mailc.microsoft.com     internet address = 205.248.102.78
mailc.microsoft.com     internet address = 205.248.102.79
>

When you have the MX server information, see if you can telnet to port 25 of the remote server.

For example (using the above information)
telnet maila.microsoft.com 25

Simon.
0
 
LVL 3

Author Comment

by:ashkaat
ID: 17067223
Hi Sembee,

I'm also suprised about this, i can DNS to these domains and i get the responsible MX Record for them .. for example:

C:\>nslookup

> qatar.net.qa
Name:    qatar.net.qa
Address:  82.148.100.100

> set type=mx
> qatar.net.qa

qatar.net.qa    MX preference = 10, mail exchanger = mail.qatar.net.qa
qatar.net.qa    nameserver = ns2.qatar.net.qa
qatar.net.qa    nameserver = ns3.qatar.net.qa
qatar.net.qa    nameserver = ns1.qatar.net.qa
mail.qatar.net.qa       internet address = 82.148.100.100
ns1.qatar.net.qa        internet address = 212.77.192.10
ns2.qatar.net.qa        internet address = 212.77.192.13
ns3.qatar.net.qa        internet address = 212.77.192.15
0
 
LVL 3

Author Comment

by:ashkaat
ID: 17067239
When i tried to send an email from my domain though Telnet to this domain, i get:
550 5.7.1 Unable to relay for aawqtr@qatar.net.qa

When i tried to Telnet "mail.qatar.net.qa" on 25, i get:

220 ****************************************************************
Connection to host lost.


The above lines is exactly like i recieve !!!???
0
 
LVL 3

Author Comment

by:ashkaat
ID: 17067248
For another domain "sps.net.sa", when i tried to send from my side, i get:
550 5.7.1 Unable to relay for aaw@sps.net.sa

But when i tried to connect to "mail@sps.net.sa" i could connect and send my mail .. they are using ESMTP

Any Suggestions ??
0
 
LVL 104

Expert Comment

by:Sembee
ID: 17067739
The lines you are receiving from mail.qatar.net.qa means that they have a Cisco PIX with the fixup SMTP option enabled. That is well known for causing problems.

When you setup the SMTP Connector, is it set to use the frontend server ONLY as the bridgehead? No smart host has been configured?
You haven't attempted to configure a smarthost directly on any of the SMTP virtual servers?

The results you are seeing are odd, to say the least. It indicates that you can connect to the servers directly. Therefore the problem must be inside your Exchange configuration somewhere. I am wondering if you have looped back on yourself somewhere.

Simon.
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 3

Author Comment

by:ashkaat
ID: 17070928
The configuration of the Connector is to use DSN to route and only My Frontend Server is used as local bridgehead. No Smart hosts are configured on any of the SMTP Virtual Servers.

I don't think i've looped back because other internet emails are going out with no problems.
0
 
LVL 3

Author Comment

by:ashkaat
ID: 17088035
Are we run out of Suggestions Here ?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 17089871
Check that your DNS, Reverse DNS and SMTP banner are correct.
http://www.amset.info/exchange/dnsconfig.asp

If that doesn't fix it, then you will have to presume that you are being blocked by the remote sites and route email through your ISPs SMTP Server.

Simon.
0
 
LVL 3

Author Comment

by:ashkaat
ID: 17121192
Hi Sembee,

I've made sure that everything is configured well including the DNS and SMTP banner. I still have the problem, nad i don't think these domains are blocking us because they are our company partners !!!
0
 
LVL 3

Author Comment

by:ashkaat
ID: 17121236
Now, the problem is occuring with Hotmail and Yahoo !
0
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
ID: 17121302
If the remote sites are using a third party blacklist they may not know that they are blocking you. It is one of the reasons why I don't use third party blacklists as you don't have any control over them.

If it is happening with Hotmail and Yahoo then you have no other choice but to use an SMTP Connector to route email through your ISP.

As you haven't supplied your domain name I cannot check whether you are on any DNS or IP blacklists.
There are tools on the internet that can do the checks for you - dnsstuff.com has some.

Simon.
0

Featured Post

Swamped with email signature updates?

Have you been given a load of changes to make to your users’ email signatures? Having to manually implement multiple signatures for every department? Let Exclaimer save you from being swamped with email signature updates!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
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…
To show how to generate a certificate request 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 Servers >> Certificates…

867 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

12 Experts available now in Live!

Get 1:1 Help Now