Exchange Message Tracking
Troubleshooting why I could receive email to all recipients but could not send email from exchange - I ran the Message Tracking troubleshooting assistant with these parameters: "get-messagetrackinglog -Recipients:stevev@elrepsales.com -Sender "rspelham@yourais.com" -Server "AIS-SERVER" -EventID "FAIL" -MessageSubject "RE: NuVo New Product" -Start "1/20/2010 7:37:00 AM" -End "1/21/2010 7:47:00 AM"" And received this response: "no results." I did this for two or three other specific emails - same resluts.Troubleshooting why I could receive email to all recipients but could not send email from exchange (Mailflow Troubleshooter) - I ran the "Users receive unexpected non delivery reports ..." trouble shooting assistant for the error 550 4.4.7 QUEUE.Expired: message expired # #.In the results: Warnings: AREA:Message Tracking SERVER:AIS-Server was this response "Unable to find message tracking log events since 01/14/2010 12:58:00 on AIS-Server. Make sure that message tracking is enabled."In the same report results: Informational: Message tracking is enabled on server AIS-SERVER, the log service is started, and the log files are located at 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\MessageTracking'.Granted I don't know ____ from shinola - but what is this telling me?Thanks - Rick
January 21st, 2010 4:19pm

Hi,Is message tracking enabled?In Exchange System manager, expand Servers then right click on your server name and select properties.Under the general tab, make sure that enable message tracking is checked.Cheers,Miguel Miguel Fra / Falcon ITSComputer & Network Support, Miami, FL
Free Windows Admin Tool Kit Click here and download it now
January 21st, 2010 7:40pm

For the error code 550 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 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. Which server roles are on the AIS-Server? Please describe the exchange topology Could you provide the details and the header info of received NDR? Does the outbound mail flow fail from all internal users, and to all external domains? Please troubleshoot the issue based on the steps in this articleJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com
January 22nd, 2010 5:38am

Miguel,It turns out that it was a SmartHost issue. I eliminated the SmartHost configuration using straight DNS instead - it appears to be working well now. Thank you for your help.Cheers to you...Rick Pelham
Free Windows Admin Tool Kit Click here and download it now
January 22nd, 2010 4:43pm

James,It turns out that it was a SmartHost issue. I eliminated the SmartHost configuration using straight DNS instead - it appears to be working well now. Thank you for your help.Thank you...Rick Pelham
January 22nd, 2010 4:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics