|Re: undeliverable We do not relay from [message #106817]
||Fri, 12 January 2007 16:36
Registered: July 2006
using http://www.dnsstuff.com/ did not find any record of 220.127.116.11 in a |
rbl. However, I did notice the 5.3.0 number and assuming that is an error
code per http://support.microsoft.com/kb/284204
Numeric Code: 5.3.0
First Available: Exchange Server 2003
Possible Causes: Exchange Server 2003 has a feature that permits Exchange
2003 to operate without the Message Transfer Agent (MTA). If a message was
sent incorrectly by using the MTA route, this delivery status notification
is returned to the sender.
Note Although Exchange 2003 can operate without the MTA, Microsoft does not
recommend or support this configuration.
To turn on this feature and to prevent the messages from queuing to the MTA,
follow these steps:1. Disable the MTA service.
2. Set the DWORD value to 0 in the following registry subkeys for every
information store database and public folder store:
Name>\<PrivMDB_GUID>\Gateway In Threads
Name>\<PrivMDB_GUID>\Gateway Out Threads
When you do this, you are making store resources that are associated with
MTA delivery available.
3. Restart the information store.
Troubleshooting: Check your routing topology. Use the WinRoute tool to make
sure that the routes are correctly replicated between servers and routing
Not sure if the above is the problem, but worth checking into.
"Brian Tillman" <email@example.com> wrote in message
: Hans <Hans@discussions.microsoft.com> wrote:
: > The following recipient(s) could not be reached:
: > (firstname.lastname@example.org) on 12.01.2007 20:36
: > 553 5.3.0 <email@example.com>... We do not relay
: > from
: > 18.104.22.168
: > Why do I get this error message and how could I fix it?
: It appears that the everyday.com server is configured to reject
: from the IP address 22.214.171.124. Only the admins of the everyday.com
: server can address that. It usually means that your mail client's IP
: address is in a realtime black list if IP addresses.
: Brian Tillman