Event ID/Source search
Keyword search
Example: Windows cannot unload your registry file
EventID.Net Splunk Add-on
Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
read more...
Event ID: 208 Source: MSExchangeMTA
| Source: MSExchangeMTA |
| Type: Error |
| Description: The default latest delivery time for message <message ID> has expired (<value> minutes after submission). A non-delivery report has been generated with reason code <error code> and diagnostic code <error code>. [<value> <value> <value> <value>](14). |
| English: Request a translation of the event description in plain English. |
| Concepts to understand: What is the role of the Exchange MTA Service? |
| Comments: EventID.Net As per Microsoft: "If a latest delivery time is not specified, a default is assumed based on the priority of the message or report: 4 hours for urgent, 24 hours for normal, and 36 hours for non-urgent. This timer has expired and the message is not delivered". See MSEX2KDB for more information about this problem. 
Thomas Fung See ME178539 on how to adjust message timeouts for the Exchange MTA.
Woodrow Wayne Collins Verify that the date and time settings are set appropriately for each server and computer involved in message submission and delivery. See ME169715. For description of MTA diagnostics logging options see ME153188. See also the "MTA Troubleshooting Guide" link.
|
| Private comment: Subscribers only. See example of private comment |
| Links: ME169715, ME153188, ME178539, MTA Troubleshooting Guide, MSEX2KDB |
| Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... |
| Feedback:
Send comments or solutions
- Notify me when updated
|
| Printer friendly |
Subscribe to EventID.Net now!