Parameter:
DEBUG_MAIL_TRACEShort description: Enables detailed mail trace logging for the Router – per recipient: lookup, hop, and delivery decision.
Profile
Parameter | DEBUG_MAIL_TRACE |
Category | Logging / Debug |
Component | Server |
Available since | 10.0 |
Supported versions | 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | 0 = off (default), 1 = basic, 2 = verbose (incl. recipient routing decisions) |
Description
For every mail, the Router task decides how to deliver it based on the recipients and the Connection/Domain documents.
DEBUG_MAIL_TRACE records in detail which lookup was performed for which recipient, which routes were considered, which next hop was chosen, and why a mail is placed into a particular mail.box.Ideal for topics such as mail stays stuck in mail.box, wrong server receives mail, routing fails only after several attempts, internet mail does not go out*.
Example configuration
DEBUG_MAIL_TRACE=2 Debug_Outfile=/local/notesdata/IBM_TECHNICAL_SUPPORT/mail_trace.log
Notes & pitfalls
- Level
2is very verbose – enable only temporarily.
- Takes effect immediately via
set config DEBUG_MAIL_TRACE=...; a restart is not strictly required.
- Entries appear in
console.logand inDebug_Outfile.
- Complementary to
DEBUG_NAMELOOKUP,Mail_Log_To_MiscEvents,Log_MailRouting.
- For pure SMTP topics, additionally enable SMTP inbound/outbound logging in
events4.nsf.