Email bounces back 3

[199002003]

Thanks in Advance

Starting this PM, I get a bunch of bounced back email from my hosting company; I was able to send the email from my yahoo account. Am I misconfigure something on my end? Please help.


'john@testabc.com' on 11/1/2006 4:34 PM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<exchange1.art.local #5.7.1 smtp;551 5.7.1 Unable to Resolve IP Address >

 

[monsterjta]

Possibly need to setup an RDNS entry on your ISP's or your external DNS server?

Hope This Helps,

Good Luck!

(I do what I can with what I know)

 

[199002003]

could it be my hosting company reject my domain to send email to their end? It was working fine though.

 

[monsterjta]

I don't believe they are rejecting you purposely, per se. However, I do suspect a DNS issue. The the following resource link below. This may also help in identifying the problem.

http://www.microsoft.com/exchange/techinfo/tips/trblsht_tip01.asp

Hope This Helps,

Good Luck!

(I do what I can with what I know)

 

[199002003]

Thanks a bunch; I have gone through the article and the SMTP setting(relay settings) are all there. if my Exchange server can't locate the DNS, then I won't be able to ping the name at all, but I can ping it fine.

 

[BigFunkyChief]

We has some trouble like this...the RDNS entry with the ISP corrected our problem.

"Rule #1 - When stumped, check your Event Logs!

 

[monsterjta]

Go to dnsstuff.com and check your entries. Check all resolution for your domain, as well as you mail.domain.com record. It is also important that you check your Reverse DNS resolution, and make sure you are receiving a successful result.

Hope This Helps,

Good Luck!

(I do what I can with what I know)

 

[199002003]

did the RDNS and got the following error:

ERROR* There is no A record for sjc-static-192.168.200.188.mpowercom.net. (may be negatively cached).

To see the reverse DNS traversal, to make sure that all DNS servers are reporting the correct results

 

[monsterjta]

Ok, so it sounds like you need to have your ISP setup a Reverse DNS entry for mail.yourdomain.com. This DNS entry should match the public IP address of your Exchange server (your MX to A record).

Question: Do you host your own external DNS services, or is it your ISP? If you don't know, most likely it's your ISP. Essentially, whomever is dishing out your IP's to your company...you need to call them and ask them to setup a RDNS entry on their DNS server.

Hope This Helps,

Good Luck!

(I do what I can with what I know)

 

[monsterjta]

NOTE: that this may or may not resolve your issue, but it's a good practice to do this anyway.

I'm assuming for the reverse DNS lookup on dnsstuff.com, you entered to search for mail.yourdomain.com?

Hope This Helps,

Good Luck!

(I do what I can with what I know)

 

[199002003]

Thanks a lot Monsterjta; I contacted my hosting company and they found my PTR record only populated on one of the Database servers and he had asked me to request the PTR change so that it gets populate on all of the database servers.

Question: Do you host your own external DNS services,(my hosting company hosts the DNS for my domain, and my ISP only hosts the T1 line for us, nothing else.)

 

[58sniper]

Most don't host their public DNS. Monsterjta said it was good practice to have a valid rDNS entry. It's actually more than that. It's REQUIRED. Per the RFC.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[monsterjta]

No, I don't host my own external DNS...primarily for security and resources limitations at the moment. My ISP is authoritative over my external DNS records (ie: RDNS), but this is the only records that matter to me as far as depending on them. This is usually a very simple request to your ISP.

Good luck with that. Let me know if you have success! If not, then we'll have to dig a little further(gulp).

 

[199002003]

Could it be the Exchange server name? (it was working for so long and all of the sudden, it just wend south)



'john@testabc.com' on 11/1/2006 4:34 PM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<exchange1.art.local #5.7.1 smtp;551 5.7.1 Unable to Resolve IP Address >

Do I need to change the Name "exchange1.art.local (this is my internal domain name though; I assumed if the name is setup correctly it doesn't really matter .local or not, as long as the Mx record and the PTR is set. Can you please confirm?

 

[monsterjta]

Well, anything is possible at this juncture. I guess a better question to ask you is did anything change recently with naming, IP addresses, pointer records, etc.

However, with the information I have at this point I do not think it is an issue with the name of your Exchange Server.

***********************

Thanks for your note, 58sniper...very insightful. I didn't read the whole RFC. However, seems to me I had to manually turn on reverse lookups in my environment. Which would lead me to believe that if a recipient domain didn't have a RDNS entry then it wouldn't matter to me or them.

Hope This Helps,

Good Luck!

(I do what I can with what I know)

 

[199002003]

I thank you for the information and kB; I haven't changed anything in regards of my Pointer records, MX, naming(it was a few months ago that I switched to different ISP and everything(email works fine)went well; one thing I changed couple days ago was the sender filter and Implemented the Tarpartime, I disabled it as of now.

 

[199002003]

Here is the actual DNS Lookup information that I just got:

Location: United States [City: Brisbane, California]

Preparation:
The reverse DNS entry for an IP is found by reversing the IP, adding it to "in-addr.arpa", and looking up the PTR record.
So, the reverse DNS entry for 216.70.183.82 is found by looking up the PTR record for
82.183.70.216.in-addr.arpa.
All DNS requests start by asking the root servers, and they let us know what to do next.
See How Reverse DNS Lookups Work for more information.

How I am searching:
Asking h.root-servers.net for 82.183.70.216.in-addr.arpa PTR record:
h.root-servers.net says to go to chia.arin.net. (zone: 216.in-addr.arpa.)
Asking chia.arin.net. for 82.183.70.216.in-addr.arpa PTR record:
chia.arin.net [192.5.6.32] says to go to ns2.mpowercom.net. (zone: 183.70.216.in-addr.arpa.)
Asking ns2.mpowercom.net. for 82.183.70.216.in-addr.arpa PTR record: Timed out [at 208.57.0.11]. Trying again.
Asking ns1.mpowercom.net. for 82.183.70.216.in-addr.arpa PTR record: Reports sjc-static-216.70.183.82.mpowercom.net. [from 208.57.0.10]

Answer:
216.70.183.82 PTR record: sjc-static-216.70.183.82.mpowercom.net. [TTL 604800s] [A=None] *ERROR* There is no A record for sjc-static-216.70.183.82.mpowercom.net. (may be negatively cached).

To see the reverse DNS traversal, to make sure that all DNS servers are reporting the correct results, you can Click Here.

Getting NS record list at g.root-servers.net... Done!
Looking up at the 7 216.in-addr.arpa. parent servers:

Server Response Time
figwort.arin.net [192.42.93.32] ns1.mpowercom.net. ns2.mpowercom.net. 24ms
epazote.arin.net [192.41.162.32] ns1.mpowercom.net. ns2.mpowercom.net. 31ms
dill.arin.net [192.35.51.32] ns1.mpowercom.net. ns2.mpowercom.net. 95ms
henna.arin.net [192.26.92.32] ns1.mpowercom.net. ns2.mpowercom.net. 3ms
indigo.arin.net [192.31.80.32] ns1.mpowercom.net. ns2.mpowercom.net. 72ms
chia.arin.net [192.5.6.32] ns1.mpowercom.net. ns2.mpowercom.net. 150ms
basil.arin.net [192.55.83.32] ns1.mpowercom.net. ns2.mpowercom.net. 268ms

Status: Records all match.

Looking up at the 2 183.70.216.in-addr.arpa. parent servers:

Server Response Time
ns2.mpowercom.net [208.57.0.11] sjc-static-216.70.183.82.mpowercom.net. 96ms
ns1.mpowercom.net [208.57.0.10] sjc-static-216.70.183.82.mpowercom.net. 98ms

Status: Records DO NOT all match: Results from ns2.mpowercom.net do not match results from ns1.mpowercom.net [TTL varies: 591613 vs 604800].

Thank you again,

 

[199002003]

Here is the Update,Ican send email to that specific domain now, it was the PRT record issue; Thank You all.