tmcbeft
asked on
4.4.7 NDR Messages
Reporting-MTA: dns;server.ADdomain.net
Final-Recipient: rfc822;user@WEBdomain.Net
Action: delayed
Status: 4.4.7
Will-Retry-Until: Thu, 30 Mar 2006 10:29:25 -0600
X-Display-Name: First Last (E-mail)
--------------------------
I have one user who gets this error everytime she sends a message to that specific domain. She can send to other domains fine and to my knowledge no other users are having trouble sending to this specific domain or anywhere else.
When the messages she is trying to send are in the SMTP connector for the domain she can't send to, It says the remote server is not responding when you highlight the connector. When I do a reverse DNS lookup on myself I get mail.WEBdomain.com, but the Reporting MTA at the top has the DNS name as the name of the server as server.ADdomain.net.
She could send email to them up until a few weeks ago, any help is much appreciated.
Final-Recipient: rfc822;user@WEBdomain.Net
Action: delayed
Status: 4.4.7
Will-Retry-Until: Thu, 30 Mar 2006 10:29:25 -0600
X-Display-Name: First Last (E-mail)
--------------------------
I have one user who gets this error everytime she sends a message to that specific domain. She can send to other domains fine and to my knowledge no other users are having trouble sending to this specific domain or anywhere else.
When the messages she is trying to send are in the SMTP connector for the domain she can't send to, It says the remote server is not responding when you highlight the connector. When I do a reverse DNS lookup on myself I get mail.WEBdomain.com, but the Reporting MTA at the top has the DNS name as the name of the server as server.ADdomain.net.
She could send email to them up until a few weeks ago, any help is much appreciated.
They might have implemented reverse dns lookup. Log into a computer outside of your network, a home computer with a different ip address scheme. Start - run type in nslookup.
Type in mail.yourdomain.com
Then grab the ip that it gave you and type that again in the next line
X.X.X.X
this should return mail.yourdomain.com, if it doesn't then this might be your problem. you might need to contact your dns hosting provider and ask them if they support reverse dns.
AOL & Road Runner use this feature.
Type in mail.yourdomain.com
Then grab the ip that it gave you and type that again in the next line
X.X.X.X
this should return mail.yourdomain.com, if it doesn't then this might be your problem. you might need to contact your dns hosting provider and ask them if they support reverse dns.
AOL & Road Runner use this feature.
ASKER
First the delay warning and then it bounces it back and says
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
<server.ADdomain.net #4.4.7>
It looks like they have telnet disabled or I have the wrong address, I am working on getting a contact there so I'll check on the address when I can.
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
<server.ADdomain.net #4.4.7>
It looks like they have telnet disabled or I have the wrong address, I am working on getting a contact there so I'll check on the address when I can.
If you do not reverse dns setup it will not work on your network. It won't allow you to connect. Try it from a company network that has reverse dns setup.
ASKER
It turns out the other company had changed their domain in their email addresses and everybody in the department knew (and had been sending emails on behalf of the person who couldn't send) except that one user.
I am curious as to why it gave the error message it did for an incorrect email address for the points.
I am curious as to why it gave the error message it did for an incorrect email address for the points.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Because they deleted the old domain from dns. Your server was trying to deliver it. It tries for awhile and then finally it will error out.
It could be a poor grey listing deployment.
If you telnet to port 25 of the remote server, does it announce itself as server.addomain.net ?
Simon.