[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2913
  • Last Modified:

Users cannot receive email from outside of their domain

I am helping a medical office where the users are having a problem with sending and receiving email. They can send and receive internally but they cannot send or receive external email

Background info:
The office upgraded to a new server that is now running DNS, DHCP, AD, Exchange, and their practice management software. Their old server was still running. They have two domains set up practice.local and practice.com. A week ago the old server that was still running died so there were errors in DNS because the domains were secondary on the new server. I set these up a primary and everything seemed fine. However, I do not see any MX record in the practice.com domain.
A few days ago their laptops could not connect to the wireless router. They replaced the router with a Netgear router. The network and internet worked but the exchange stopped working. Users trying to send email to them was getting bounced. They were sending email ok to anyone on the domain but were unsure if external email was getting through. I have received email from them but when I send to them I get the following bounce.
There was a SMTP communication problem with the recipient's email server.  Please contact your system administrator.
<mx01.testing.com #5.5.0 smtp;553 sorry, relaying denied from your location [XX.XXX.XX.132] (#5.7.1)>  

I found out that they had a static ip and entered into the router. Everything works but the email and now I get the following bounce when I send to them:
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            <mx01.testing.com #5.7.1 smtp;550 5.7.1 Unable to relay for nicpt@lvprc.com>

So I am usure of where to go from here. I am unable to look at the config of the old router and nobody documented anything when it was set up a yaer ago.

Is the netgear the wrong device to work with exchange?
Is there a DNS problem since there is no MX record in practice.com?
Are there Exchange tools that I can download to see if something is misconfigured?
Are there DNS tools to download to see if something is misconfigured?

Thank you for your help
Dave
0
lmclabs
Asked:
lmclabs
  • 5
  • 4
1 Solution
 
ikm7176Commented:
Surely you need MX record for your domain. It should be configured on a public DNS servers (ISP or hosting providers). MX record is required for the mail delivery. check for the MX records. visit http://www.mxtoolbox.com and  make email diagnostic

If MX records already exists, make sure that the recipient policy is configured properly and practice.com is added to the reciepient policy.
 
0
 
lmclabsAuthor Commented:
Thanks I will check it out.

I was by there today and found out more info. They can send mail but cannot receive. Could it be a SMTP problem? Or a mapping problem with the Netgear router?
Thanks!  
0
 
lmclabsAuthor Commented:
Here is the output from  mxtoolbox.com:

RESULT: lvprc.dnsalias.net
Banner: server.lvprc.local Microsoft ESMTP MAIL Service, Version: 5.0.2195.6713 ready at Wed, 11 Jun 2008 09:51:39 -0700 [62 ms]  
Connect Time: 0.062 seconds - Good
Transaction Time: 0.344 seconds - Good
Relay Check: OK - This server is not an open relay.
Rev DNS Check: OK - 24.234.138.210 resolves to wsip-24-234-138-210.lv.lv.cox.net
GeoCode Info: Geocoding server is unavailable
Session Transcript: HELO please-read-policy.mxtoolbox.com
250 server.lvprc.local Hello [64.20.227.131] [47 ms]
MAIL FROM: <test@mxtoolbox.com>
250 2.1.0 test@mxtoolbox.com....Sender OK [62 ms]
RCPT TO: <test@mxtoolbox.com>
550 5.7.1 Unable to relay for test@mxtoolbox.com [62 ms]
QUIT
221 2.0.0 server.lvprc.local Service closing transmission channel [47 ms]
6/11/2008 11:51:41 AM Central Standard Time

RESULT: mailstore1.secureserver.net
Banner: pre-smtp20-01.prod.mesa1.secureserver.net ESMTP [62 ms]  
Connect Time: 0.031 seconds - Good
Transaction Time: 0.234 seconds - Good
Relay Check: OK - This server is not an open relay.
Rev DNS Check: OK - 64.202.166.11 resolves to mailstore1.secureserver.net
GeoCode Info: Geocoding server is unavailable
Session Transcript: HELO please-read-policy.mxtoolbox.com
250 pre-smtp20-01.prod.mesa1.secureserver.net [31 ms]
MAIL FROM: <test@mxtoolbox.com>
250 ok [47 ms]
RCPT TO: <test@mxtoolbox.com>
553 sorry, relaying denied from your location [64.20.227.131] (#5.7.1) [31 ms]
QUIT
221 pre-smtp20-01.prod.mesa1.secureserver.net Goodbye. [31 ms]
6/11/2008 11:56:09 AM Central Standard Time

What do you think?
0
Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

 
ikm7176Commented:
hi,

Can you explain more about the setup and the exchange version you are using?
can you resolve the MX record for your domain using nslookup?
>nslookup
>set q=mx
> "your domain name"

Iit should resolve to your public IP. can you post the output here?





0
 
lmclabsAuthor Commented:
> set q=mx
> lvprc.com
Server:  lvsbs.lvprc.local
Address:  192.168.75.3

lvprc.com
        primary name server = lvsbs.lvprc.local
        responsible mail addr = admin
        serial  = 493
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 900 (15 mins)
>
0
 
lmclabsAuthor Commented:
Exchange System

Microsoft Corporation

Version: 6.5.7638.1
0
 
ikm7176Commented:
i could not find the extended SMTP verbs when i telnet to your exchange server.
I gues your mapping is screwed up, plese check your netgear configurations

check the links below
http://support.microsoft.com/kb/153119
http://technet.microsoft.com/en-us/library/bb124688(EXCHG.65).aspx
0
 
lmclabsAuthor Commented:
Thanks. I checked the settings on the netgear and set it up SMTP on Port Forwarding to Exchange.
Below is the output

> set q=mx
> lvprc.com
Server:  lvsbs.lvprc.local
Address:  192.168.75.3

lvprc.com
        primary name server = lvsbs.lvprc.local
        responsible mail addr = admin
        serial  = 493
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 900 (15 mins)
>Banner: mail.lvprc.com Welcome to SpamFilterISP SMTP Server v3.1.3.599 - Unlicensed Evaluation Copy [62 ms]  
Connect Time: 0.062 seconds - Good
Transaction Time: 0.297 seconds - Good
Relay Check: OK - This server is not an open relay.
Rev DNS Check: OK - 24.234.138.210 resolves to wsip-24-234-138-210.lv.lv.cox.net
GeoCode Info: Geocoding server is unavailable
Session Transcript: HELO please-read-policy.mxtoolbox.com
250 Hello please-read-policy.mxtoolbox.com [47 ms]
MAIL FROM: <test@mxtoolbox.com>
250 Address Okay [62 ms]
RCPT TO: <test@mxtoolbox.com>
557 You are not allowed to send mail to test@mxtoolbox.com [62 ms]
 
RESULT: mailstore1.secureserver.net
Banner: pre-smtp18-02.prod.mesa1.secureserver.net ESMTP [78 ms]  
Connect Time: 0.031 seconds - Good
Transaction Time: 0.266 seconds - Good
Relay Check: OK - This server is not an open relay.
Rev DNS Check: OK - 64.202.166.11 resolves to mailstore1.secureserver.net
GeoCode Info: Geocoding server is unavailable
Session Transcript: HELO please-read-policy.mxtoolbox.com
250 pre-smtp18-02.prod.mesa1.secureserver.net [31 ms]
MAIL FROM: <test@mxtoolbox.com>
250 ok [31 ms]
RCPT TO: <test@mxtoolbox.com>
553 sorry, relaying denied from your location [64.20.227.131] (#5.7.1) [31 ms]
QUIT
221 pre-smtp18-02.prod.mesa1.secureserver.net Goodbye. [62 ms]
 
0
 
ikm7176Commented:
Glad that your issue has been resolved.  
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now