Email errors

We are a college. I can send emails anywhere except to my local ISP address. When I do, I get a delayed error and then a 4.4.7 error. Looking up this error, I find this:
Numeric Code: 4.4.7

Possible Cause: The message in the queue has expired.
The sending server tried to relay or deliver the message,
but the action was not completed before the message
expiration time occurred. This NDR may also indicate that
a message header limit has been reached on a remote server
or that some other protocol timeout occurred during
communication with the remote server.
Troubleshooting: This code typically indicates an issue on the
receiving server. Verify the validity of the recipient address,
and verify that the receiving server is configured to receive
messages correctly. You may have to reduce the number of
recipients in the header of the message for the host that you
are receiving this NDR from. If you resend the message, it is
placed in the queue again. If the receiving server is on line,
the message is delivered.

Our isp says it is not there problem.

Any ideas. Nothing remains in my exchange queue.

 

What do you mean by "my local ISP address "?

Are you trying to e-mail your ISP (their tech support perhaps)?

or do you mean the address you have with your ISP at home?

or do you mean a .local address.

or something else?

 

My address that I have at home with my ISP.

 

I think the first thing to see is if your network's DNS system recognises the e-mail domain. The domain is the bit after the @ in your e-mail address. To do that use NSLOOKUP. For example if you were e-mailing me@my.com, then you'd use the command:

NSLOOKUP my.com

I would guess that you might have an e-mail address along the lines of me@myaccount.isp.net where isp.net is specific to your ISP, and "myaccount" is a name specific to your account. If this is the case you may find that

nslookup isp.net

gets a successful IP address resolution, but

nslookup myaccount.isp.net

fails. This will occur if your ISP settings for your specfic account's address hasn't got to the DNS servers you are using.

On review, if you get to this point and NSLOOKUP for your home e-mail domain is failing, the first thing to do is to talk to your College's ISP. Tell them of the problem and they should be able to resolve it at their DNS servers. Then, as long as the college's DNS server is forwarding to your college's ISP's DNS servers the change will be inherited within the college network. Only go to my suggestions below if your college's ISP doesn't fix the problem.

If you get failures to resolve your e-mail domain, the mail server on your domain will be unable to send e-mails to that address. If this is the case the simplest fix may be to add a record for your e-mail domain (e.g. myaccount.isp.net) manually into your DNS server. I think you should be able to add an MX record for the e-mail domain, but you may find just adding an A record might do the job. You will have to create a zone for your e-mail domain.

However, there are knock on effects to this. Once you add a zone for that domain, your DNS server will stop looking elsewhere to resolve names for addresses in that domain. So you will have to have a mapping for every address in that domain that you use. That's simple if your address is me@myaccount.isp.net as it will probably just be the MX record and an A record for www. If your address is along the lines of me@aol.com, then this could be a big issue.

If this problem affects more than just this one address, and/or the address is difficult to isolate (it is a me@isp.net address) a better way forward may be to review the forwarders your DNS server is using. Changing forwarders may sort the problem. It may be worth discussing this with your ISP. They may be able to suggest a DNS server to forward to (depending on how good they are).

Don't forget to keep a record of any changes you make to DNS so that you can reverse them if they don't correct the problem or have unforseen knock on effects.

If I'm barking up the wrong tree and NSLOOKUPS all pass, then the problem lies elsewhere.

 

Thanks,

I will check it out in the morning. This is the error I am getting:

Could not deliver the message in the time limit specified. Please retry or contact your administrator.
<xxxxx.xxxxx.edu #4.4.7>

This error just started this week. Nothing is in the exchange queue. I have contacted my ISP, they said that nothing is wrong on their end. I have not made any changes to any of the servers. The only thing that has changed in the last few weeks, is a reboot of the firewall.

 

One other thing....when I say my local ISP. That is the ISP the college uses, I also use for my home address. I can't email the ISP tech support or my home address.

Now is also appears that we cannot email the local high school, who also uses the same ISP. We receive email in from them but not send to them. We get the same 4.4.7 error. We can email a high school in a nearby town that uses a different ISP.

Does any of this make any sense?

Thanks so much.

Sue

 

I firmly believe it's a dorked up DNS.
Who is your ISP?
What is the name of your Domain?
Where is DNS forwarded to?
If you feel any of this information is sensitive then I understand.
Just hard to diagnose assuming everything else is correct.

 

My isp gives me 2 IP addresses to use. I can ping 207.177.24.1 with no problem. When I ping 207.177.24.2 I always time out, then I ping it again and it works.

Sue

 

Problem solved!! I put in a support call with Microsoft and those wonderful people fixed it.

They said it was a "edns problem with packet size ". They had me run a simple dos command on the dns server.

All it well.

Thanks for all your help.

Sue

 

What was the dos command ? I am having a simular issue since changing a router out.

WFoxCat

 

To work around this problem, turn off EDNS0 support in Windows Server 2003. To do this, follow these steps: 1. Start a command prompt.
2. Type dnscmd /Config /EnableEDnsProbes 0, and then press ENTER.

Hope this helps.

Sue

 

Well, I am running 2000 server, this command does not work for 2000. I am sure this is along the line of a fix to what sounds like the same symptoms. The only thing I did was change out the router. I am going to put the old router back and see if it resolves.

Thanks

 

This is what is listed for Windows 2000 server:

1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters
4. Point to New on the Edit menu, and then click DWORD Value.
5. Type EnableSendErrorSuppression, and then press ENTER.
6. Right-click EnableSendErrorSuppression, and then click Modify.
7. In the Value data box, type 0, and then click OK.
8. On the File menu, click Exit to quit Registry Editor.
9. Restart the DNS service.