HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Unless your application is doing a mail database open and reading / creating documents in each mail db then I don't see any reason to have an actual user mailbox. Setting up forwarding address on each person document would be enough since Domino will only try to resolve the Notes Name in Domino Directory and deliver it via the forwarding address.
Or maybe you have other specific use cases ?
Tinus Riyanto - Prisma Global Solusi.
The need to do this stems from how Domino apps interact with user mailboxes (old apps can assume the use of a Notes mailbox whereas better written apps do not assume that this is the case). To keep mail flowing, we created a shared mailbox for each site and assigned one as the users mailbox (access to the mailbox is given by Domino group membership). Some Caveats: Essentially, the shared mailboxes are public (to all Site personnel who share it) so you need to make staff aware of this (so they can remove items from Sent). But If you are using the CAA client, the mailbox is only accessible through web access so if you place the mailboxes on a server that is not running https this 'solves' that issue. You will need to create a 'generic' account for each site mailbox so that mail can be routed. Ideally, you need to update the mail interfacing apps so that they do not rely on someone having access to a Notes mailbox.