Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mail being bounced back from different domains

Status
Not open for further replies.

itpro34

MIS
Jan 2, 2003
34
US
My client is being inundated with “Could not deliver the message in the time limit specified. Please retry or contact your administrator” from different domains when trying to send mail.

I have checked to see if they are on any blacklists and I could find any with my clients domain “Nottinghamproperties.com”

Any assistance would be greatly appreciated.

Thanks
Michael
 
Sounds like you are either a relay or are getting bounce backs from spammers using your address.

Either block them at your bridgehead or create an outlook server side rule.
 
Thanks for the reply Z.
The user is actually trying to e-mail a legitamate e-mail address but it comes back undeliverable
 
So it is probably a DNS problem. On the exchange server, try the following:

(note one that is failing (mail.something.com)
command prompt
nslookup
set type=mx
mail.something.com

You'll probably get a failure. You then need to sort out the DNS server that your Exchange box points at. For testing purposes, I normally add 195.92.195.92 (resolver @ theplanet) as a secondary DNS on the Exchange server.
 
nslookup -q=mx mail.something.com
will do it all on one line.

Make sure you get a valid MX record, then see if you can telnet to it over port 25.


Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)
 
Could not deliver the message in the time limit specified" can also mean you client's ISP has some issues, you may want to check that too.
One way to tell is if it is random, check the ISP, if it is always the same domains that bounce, check ISP and MX's as suggested above.

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC!
[/sub]
 
I'd be curious as to if the other side has multiple MX records, and if you can successfully send to lower priority records without issue.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)
 
Thanks for all the replys everyone. I found out what the problem was. It seemed as if the mail with attachments were getting hung up in the queue. Once AV (Symantec) was disabled the mail went right through without problem. I performed two (2) tasks.

1. In Symantec console I created new group and moved the Exchange server to the new group..

2. In Symantec console I edited the "Client Preferences" so that Symantec was NOT scanning the Exchange database.

Number two (2) is a text book configuration. Number one (1) was found on a white paper from Symantec.

Thanks again everyone for your help on this.

Mike
 
Oooh Symantec, how I love that company ... NOT!

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC!
[/sub]
 
Ah - yep. You're lucky the problem wasn't worse than that. Scanning the mdbdata folder with a file level scanner is NOT a good idea, and can lead to database corruption and Exchange instability.

Once you have the client permissions adjusted, make sure that if you're using the Symantec Mail Security for Exchange that you're also exluding the temp folder that it uses for the quarantine, or you'll see other errors in your event logs.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top