Troubleshooting Email failure in Exchange 2007

Hi,

A message has been received by the Exchange 2007 store but failed to reach the User.  No NDR was received by sender or recipient.  The sender successfully sent a mail through earlier in the day but recorded a different IP address.  

Mail tracking reported following facts for the non delivered message:

Event ID #1 Receive    Source: SMTP
Event ID #2 FAIL          Source: Routing

Can you advise how I can take this further and understand where it failed?

Thanks
buddlesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

R--RCommented:
Check if it is stucked in queue.
Check message tracking.

Is this happening for one user only or all?
0
akhalighiCommented:
any logs in windows event logs (applications) regarding this failure ?
do you have any anti-spam running ?
0
buddlesAuthor Commented:
Those event IDs were from the tracker and no nothing in the queue.  Just this one mail from this sender.  

Nothing in the logs and yes to AV (Sophos) but nothing recorded there.  Recieved fine from them earlier in the day.


Can anyone help decipher the routing failure reason?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

SurajCommented:
get the error from message tracking from command shell.

get-messagetrackinglog -sender user@senddomain.com -recipients user@recipientdomain.com |fl

pls share the results
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SurajCommented:
I am still waiting for the reply...to my comment ID: 37733198
0
buddlesAuthor Commented:
Apologies x-sam, completely missed your reply.  Thanks for the command, shows message was too large.  Why would MS not put this into the normal tracker GUI!

Timestamp               : 15/03/2012 17:39:28
ClientIp                :
ClientHostname          : x-mail
ServerIp                :
ServerHostname          :
SourceContext           :
ConnectorId             :
Source                  : ROUTING
EventId                 : FAIL
InternalMessageId       : 357898
MessageId               : <1ea5f.26873729.3c9382f2@aol.com>
Recipients              : {abi@x.co.uk}
RecipientStatus         : {550 5.2.3 RESOLVER.RST.SendSizeLimit; message too large for this sender}
TotalBytes              : 28068127
RecipientCount          : 1
RelatedRecipientAddress :
Reference               : {<5ebef9e4-6312-4377-a443-95a502ddaebb>}
MessageSubject          : Fwd: gsgsghgs
Sender                  : x@aol.com
ReturnPath              : x@aol.com
MessageInfo             :
0
buddlesAuthor Commented:
Excellent pointer.  Shows much more detail than the Tracker GUI.

Message was too large.
0
SurajCommented:
Well it would be there but you need to select appropriate options :-)
MS rocks

x-sam
Microsoft Corp.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.