Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Fri, 19 Sep 2008 15:55:27 -0400,    group: microsoft.public.exchange.admin        back       


imcoming mail failure   
I have one company that cannot send to our domain.  the failure they receive 
is:
550-xx.com [their IP] is currently not permitted to relay

they say it is on my end.  But I am receiving other mail fine.  What might 
cause this on my end?  Also, how can I check logs to see the failure on this 
end?

TIA
date: Fri, 19 Sep 2008 15:55:27 -0400   author:   John am

Re: imcoming mail failure   
how are they trying to send you email...?  if the error is coming from the 
IP address of their server, I don't see how this could be a problem on your 
side...are the messages even reaching your server?  you can crank up smtp 
protocol logging to see...although it's my bet that the messages are never 
even reaching your server...

-- 
Susan Conkey [MVP]



"John" <jadams@nospam.nospam> wrote in message 
news:uxd8qGpGJHA.1156@TK2MSFTNGP05.phx.gbl...
>I have one company that cannot send to our domain.  the failure they 
>receive is:
> 550-xx.com [their IP] is currently not permitted to relay
>
> they say it is on my end.  But I am receiving other mail fine.  What might 
> cause this on my end?  Also, how can I check logs to see the failure on 
> this end?
>
> TIA
date: Fri, 19 Sep 2008 13:16:53 -0700   author:   Susan

RE: imcoming mail failure   
Hi John,

Thank you for posting here and also thanks to Susan.

Based on research of the error message and experience, this kind of issue 
may possibly occur if the sender side DNS resolution has some problem or 
SMTP rely is not properly configured.

To check if it is also related to your Exchange server, I agree with Susan 
that you may need to leverage SMTP logging to check if the mail has arrived 
to your Exchange server end.

SMTP log
===================
First, enable SMTP log on your Default SMTP Virtual Server on the sender's 
server.

a. Please open Exchange System Manager.
b. Right click on "Default SMTP Virtual Server" and click Properties.
c. On the General tab, please check the option "Enable logging".
d. Select W3C Extended Log File Format from the list below.
e. Click the Properties button. In the General Properties tab, please 
confirm the following settings:
- Check the option Daily
- Check the option "Use local time for file naming and rollover"
- Confirm the setting for "Log file directory" to be
"C:\WINNT\System32\LogFiles"
- Check all the logging options on the Advanced tab.

Second, reproduce the issue.
Third, check the sender email address from the log file under 
C:\WINNT\System32\LogFiles\SMTPSVC#" (# is a number. The number for the 
Default SMTP Virtual Server is 1). 


At the same time, I recommend you run the Exchange Best Practices Analyzer 
v2.8 to detect and analyze you Exchange organization. Access the 
functionality for Exchange Performance Troubleshooting, Database Recovery 
Management, and Mail Flow Troubleshooter through single tools.

Microsoft Exchange Analyzers
<http://technet.microsoft.com/en-us/exchange/bb288481.aspx>
Best regards,

Hope this helps.


Robbin Meng(MSFT)

Microsoft CSS Online Newsgroup Support
date: Mon, 22 Sep 2008 10:53:28 GMT   author:   (Robbin Meng [MSFT])

Re: imcoming mail failure   
I do get the impression our problem is not on our server.  We had a problem 
with our DNS host publishing MX records incorrectly for about 1 week.  We 
fixed it eventually by switching hosts, but it seems some bad DNS records 
are still floating around the web.  This doesn't seem like it should be 
possible, since it has been correct for more than a week.  In one case 
though I was able to get the company to flush their DNS and then all was 
good.  If this is the case I understand there isn't much I can do about it, 
but, are there any suggestions?



""Robbin Meng [MSFT]""  wrote in message 
news:vrvpzFKHJHA.1652@TK2MSFTNGHUB02.phx.gbl...
>
> Hi John,
>
> Thank you for posting here and also thanks to Susan.
>
> Based on research of the error message and experience, this kind of issue
> may possibly occur if the sender side DNS resolution has some problem or
> SMTP rely is not properly configured.
>
> To check if it is also related to your Exchange server, I agree with Susan
> that you may need to leverage SMTP logging to check if the mail has 
> arrived
> to your Exchange server end.
>
> SMTP log
> ===================
> First, enable SMTP log on your Default SMTP Virtual Server on the sender's
> server.
>
> a. Please open Exchange System Manager.
> b. Right click on "Default SMTP Virtual Server" and click Properties.
> c. On the General tab, please check the option "Enable logging".
> d. Select W3C Extended Log File Format from the list below.
> e. Click the Properties button. In the General Properties tab, please
> confirm the following settings:
> - Check the option Daily
> - Check the option "Use local time for file naming and rollover"
> - Confirm the setting for "Log file directory" to be
> "C:\WINNT\System32\LogFiles"
> - Check all the logging options on the Advanced tab.
>
> Second, reproduce the issue.
> Third, check the sender email address from the log file under
> C:\WINNT\System32\LogFiles\SMTPSVC#" (# is a number. The number for the
> Default SMTP Virtual Server is 1).
>
>
> At the same time, I recommend you run the Exchange Best Practices Analyzer
> v2.8 to detect and analyze you Exchange organization. Access the
> functionality for Exchange Performance Troubleshooting, Database Recovery
> Management, and Mail Flow Troubleshooter through single tools.
>
> Microsoft Exchange Analyzers
> <http://technet.microsoft.com/en-us/exchange/bb288481.aspx>
> Best regards,
>
> Hope this helps.
>
>
> Robbin Meng(MSFT)
>
> Microsoft CSS Online Newsgroup Support
>
date: Wed, 24 Sep 2008 06:49:09 -0400   author:   John am

Re: imcoming mail failure   
Hello John,

Thanks for your reply.

First, I still suggest  you enable and check SMTP log so that you can 
monitor all inbound and outbound mail flow and see if their mails indeed 
arrived at your end or not. The Exchange BPA tool is an good  tool for 
automatically detection of overall health.

As for other suggestions I can think of , you may use the website 
http://network-tools.com/nslook/Default.asp to check if your/their external 
domain DNS records are correct or not on the Internet.

Hope it helps.


Best regards,
Robbin Meng(MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
date: Thu, 25 Sep 2008 11:16:10 GMT   author:   (Robbin Meng [MSFT])

Re: imcoming mail failure   
do your instructions for the logging apply to Exchange 2007?  I get the 
feeling they don't since I am not finding these settings...


""Robbin Meng [MSFT]""  wrote in message 
news:wlM$hAwHJHA.1652@TK2MSFTNGHUB02.phx.gbl...
> Hello John,
>
> Thanks for your reply.
>
> First, I still suggest  you enable and check SMTP log so that you can
> monitor all inbound and outbound mail flow and see if their mails indeed
> arrived at your end or not. The Exchange BPA tool is an good  tool for
> automatically detection of overall health.
>
> As for other suggestions I can think of , you may use the website
> http://network-tools.com/nslook/Default.asp to check if your/their 
> external
> domain DNS records are correct or not on the Internet.
>
> Hope it helps.
>
>
> Best regards,
> Robbin Meng(MSFT)
> This posting is provided "AS IS" with no warranties, and confers no 
> rights.
>
date: Thu, 25 Sep 2008 15:01:20 -0400   author:   John am

Re: imcoming mail failure   
Hi John,

If you are using Exchange 2007, please find it under: 

EMC -> Toolbox -> Mail flow tools ->  Message Tracking.

Hope this helps.

Best regards,
Robbin Meng(MSFT)
date: Fri, 26 Sep 2008 11:57:22 GMT   author:   (Robbin Meng [MSFT])

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us