Pesky debugging and logging notes.ini settings
I’ve been investigating why our primary mail routing hub server is taking so long to route messages recently. The behavior started a few days ago (or maybe it’s been going on for a while and we didn’t notice it).
- Messages will queue in the mail.boxes for anywhere from 5 to 15 (maybe longer) minutes.
- They do NOT have the -check in progress- (which sometimes take place when Trend Micro ScanMail or IQSuite, our mail compliancy capturing software, is holding up the router).
- Then suddenly they all route at once.
- Then the process will start over again.
I looked at the configuration document and the notes.ini and these notes.ini settings are the ones I found associated with routing and debugging. At lunch time, I made changes to notes.ini as indicated below and restarted router and tm_grab. Initially, it didn’t do anything, but when I came back from eating, I found that hub1 is routing as expected now.
REMOVED:
log_mailrouting=40
debugrouter=3
LEFT AS IS:
? Console_LogLevel=2
DOESN’T DO ANYTHING:
debug_threadid=0
smtpclientdebug=0
The pesky debugging and extra logging options will get you every time. This is why it is always a good idea to only make changes to your notes.ini through a configuration document so that you know that they are there, and if possible make some notes somewhere so you know why you turned them on.
Unfortunately, there isn’t a comments section in a server configuration document like there is for server documents and connection documents.