Sometimes it's the small issues in Notes/Domino that are very bothersome. I have a customer that receive a lot of e-mail and I mean a lot - there are only 6 employees but they still receive thousands of e-mails a day. All e-mail is channeled into a single database as this is how they read e-mail and every employee needs to read every e-mail. The e-mails are preprocessed using a few mail rules and put into one of two views depending on these rules.
Recently they have started receiving the above error message when roaming around the office or to their home computer (the screenshot is from a user roaming to his home computer). I did a search on developerWorks and it appears to be a known issue. Unfortunately none of the workarounds will work for us. The situation is further worsened by the fact that the Notes mail client just isn't fast enough for this type of broker-type user that needs to scan a LOT of e-mail. I know that this probably isn't a core use-case so that's a problem we have to deal with.
Since the workarounds will not work we are planning to do the following:
- Instead of using mail rules to maintain an inbox with all messages and 2 views with the e-mail as processed by the mail rules we will maintain three mail databases (one for the inbox and one for each of the views).
- The above will mean we can remove the mail rules which should help the server.
- Create a mail only mail database and remove all calendar code from the template to improve client performance.
- Do away with the ($Inbox) folder and only have a single view in the database showing all documents. The view will be styled as a simplified ($Inbox).
- Try to implement a very aggressive archiving schedule to keep the mail databases down to a minimum.
It's going to be interesting to see how it pans out.