Tags:
Microsot, Exchange Server, 2003, Could not deliver the message in the time limit specified #4.4.7 Server with Mutliple Email Domains
Experiencing a problem sending e-mail to certain domains. Every now and then we get a bounce back message saying: Could not deliver the message in the time limit specified. Please retry or contact your administrator. <#4.4.7>.
Here is a picture of the environment Server 2003 Exchange Server 2003 T1 with static IPs MX record goes to spam company Mail A record points to exchange server DNS is setup correctly with forwarders and root hints Reveres DNS is setup correctly We are not blacklisted anywhere
Here is where I think the problem may be, but I do not know how to get around it. The exchange server is receiving email for 2 domains. Some users send out emails as domain1.com others as domain2.com
The Exchange server is identifying itself as mail.domain1.com and the PTR record is for mail.domain1.com. I believe we have the issue when users are sending mail out as domain2.com since now the mail server and the PTR record do not match the email domain of the user.
Am I correct in my assumption? Does anyone know how we get around this, or am I looking in the wrong place?
I believe we have the issue when users are sending mail out as domain2.com since now the mail server and the PTR record do not match the email domain of the user YOU ARE RIGHT.you should have reverse look up working for that new domain as well.otherwise anti-spam products would reject it for spamming activities.
Your ISP can create the PTR records for you thanks.
consultkhan: If you saw above i mentioned that the PTR record already exists for domain1.com and the ISP does not have the ability to create 2 PTR records for the same IP.
I'm not sure you read the original problem. The server is currently configured for two domains, it sends out emails from both domains. The issue is my ISP will only allow me to create one revers dns ptr record. So one domain has a reverse lookup that matches, and the other does not.
The problem is some ISP are now looking to make sure not only that you have a reverse ptr record, but that it matches your domain name. So 1 matches, and the other does not. The one that does not will be rejected.
I read and fully understood the problem. My answer was, the PTR doesn't matter - as long as it is valid (in that it is mail.domaina.com and mail.domaina.com actually exists in the forward zone) there is no problem, even if you want to send out as domainb. I have many sites configured with more than one domain - my own server has 6 domains on it, one IP address, one PTR.
>>The problem is some ISP are now looking to make sure not only that you have a reverse ptr record, but that it matches your domain name.
No, they dont. If you are having problems, there is something else wrong - most likely your SMTP greeting as I indicated.
As I said before - think about big hosting companies - they host tens of thousands of domains, do you really think they have one PTR for each domain?
The goal here is not to get into an argument. I've not worked nor been involved with a "big hosting company". Perhaps you have. Regardless I have explained EXACTLY why i am having a problem. I'm not trying to convince you of it.
The problem is, you are perceiving a problem that does not exist.
There is no problem with having a PTR that doesn't match the sending domain - if you don't believe it, and won't listen, there isn't a whole lot I can do really.
