Recently I upgraded to R6.5 (with CD# C260YNA) from R5.06a, mail.box is receiving mail but it will not distrubute to relevant person mailboxes after Domino has been running for 2 days.
Details: After Domino had been kicked-off, in the first 2 days, nrouter and mail.box were running in good shape. In the third day (after 4:00 AM as nrouter task had been shut down and restarted due to mail.box compact), mail.box was successfully compacted, nrouter still received mail (both notes and internet mails) but it would not distrubute mails inside mail.box to relevant person mailboxes. Finally, mail.box was accumulating a long queue of undelivered mails.
I have tried in server console using command “tell router quit”. But nrouter would not quit. “tell router show queue” still had no response. Finally, I needed to restarting the domino server.
Very funny is that in the first kickoff of Domino, I can use server command “tell router quit” and “tell router start” gracefully.
After serveral days of inspection, I found out that a delivery thread was not released while working the 4:00AM mailbox compact.
This cause is due to one user account (created with R6.5 admin). After a certain time period, sessions of that account could not be dropped as found in R6.5 admin.
Later that user account couldn’t open that mailbox again with error message “Network Operation is not compleated in as reasonable amount of time …”. Subsequent incoming mails for that user account were queueing in mail.box and then returned to original sender. One delivery thread was jammed.
The main cause can be represented in this sequence:
User session not dropped → personal mailbox is hooked up → router will not deliver mail from mail.box to that personal mailbox → a delivery thread is hooked up → router will not waked up at 4:00 after shutting and starting nrouter task → all incoming e-mail are not distributed and queueing in mail.box.
I am still finding the reasons for it either the cause is coming from the domino R6.5 server, mailbox corruption, or user account created from R6.5 admin (all user accounts previously created under R5.06a are running in good shape).
Yes, I have the same problem.I upgraded from R6.0 to R6.03 last week.
But instead only email that not delivered, I also found that many agent that scheduled at night do not run. Both email and agent run after I try to type something in the server console.
From the Log, I found that there are no activity from 05:00 PM to 09:00AM (That when I type anything in the console), after that routing goes wild delivering many emails, and scheduled agent start to run.
I’m not sure if this will help or not, but I’ve seen the issue you mentioned, where typing anything in the server console causes a ton of activity to suddenly scroll by. To fix that, you can right-click on the Domino Server task down in the task bar and choose Properties. Disable the QuickEdit feature and then tell it to apply that to future windows with that same title.
If your issue wasn’t related to the Windows “DOS window” issue mentioned previously, you might enter the following at the server consle to see if it offers any insight:
set config debugrouter=3
You can also set the logging for the router to verbose by changing the setting in the config document for that server…under Router/SMTP–>Advanced–>Controls
This should hopefully provide additional information about what the router is thinking when it won’t do anything
