We are currently on ND 6.5.4 and are anxious to move on to 7.0.1. We make extensive use of Mailin/Functional mailboxes. Their addresses are used by both internal and external parties.
We have accumulated quite a collection of mailin databases over time using designs from R4.5 forward. We would like to upgrade all functional mailboxes to some current design template. Our current stumbling block is the mail template requirement that the Mail Owner be a Hierarchical name.
We do not want to deal with the problems that will ensue if we change all of our mailin database names to hierarchical unless we really have to. Too many customers have these names in their address books.
We can hack the design to remove the hierarchical requirement. Why was it put there in the first place?
What was the thinking behind this requirement? Requiring a selection from the Domino Directory I can easily understand. What are we risking if we remove this restriction?
Subject: Why Does the Mail Owner Need to be Hierarchical?
Hi Bob,
I am not sure I understand why this is a problem for you. If the mail in db’s are simply shared mail db’s then who cares who the owner is. Set the owner to some admin id that is hierarchical.
FYI… if you update the templates they will still work if you leave them alone. You just wont be able to change the preferences in them till you give some new name for the owner. We have lots of old ones that have never been changed and still work just fine.
Subject: Why Does the Mail Owner Need to be Hierarchical?
Greetings,
Lets try this again.
The mailin databases have names like WeCanHelpYou with Internet Addresses like WeCanHelpYou@Company.Com. So when a customer sends a message in to WeCanHelpYou@Company.Com they want an answer back from WeCanHelpYou and not from Admin/Org.
I tried adding /Org to one mailin database and found problems with internal people who had fixed addressing of WeCanHelpYou@Org which then could not be found.
I am not looking for a way around this problem. I just want to know why a great mind from Lotus decided that it was an improvement!
The mailin databases have names like WeCanHelpYou with Internet Addresses like WeCanHelpYou@Company.Com. So when a customer sends a message in to WeCanHelpYou@Company.Com they want an answer back from WeCanHelpYou and not from Admin/Org.
if you change the mail-in db’s document and make it’s name heirarchical then you need to change the mail file owner to heirarchical as well, that will pretty much cover the from address for any messages sent out of that mail file behaving as it always has. all of ours work this way without any problems.
I tried adding /Org to one mailin database and found problems with internal people who had fixed addressing of WeCanHelpYou@Org which then could not be found.
that’s because you just renamed it. you need to ADD the heirarchical name to be first in the list (mail-in db’s can have multiple names just like people), so you have WeCanHelpYou/Org first (primary) and then WeCanHelpYou second (alias - this one is for those hardcoded users to use).
I am not looking for a way around this problem. I just want to know why a great mind from Lotus decided that it was an improvement!
oh well, why post it in here then? contact lotus directly or use the feedback links (on the web page).
you can ignore my comments above and live with the problem if you want but it’s not that hard to make the necessary changes.
I had never been aware that the FullName field in the Database form was multi-valued. I was assuming that it was, like the InternetAddress field, single valued. Should not be a problem to work this one out now.