Moving a lotus database causes incoming mail failure

Question

I moved a couple lotus note databases to another hd (ran out of space) by using a directory link/pointer on the domino server. USed a text file with the .DIR ext with the desired new path etc... well that works fine. I open up a lotus notes client, use the id and then OPEN the database. The directory link works fine, the new location of the db is opened with no problems. We found out that we couldnt FORWARD any mail: We did the following to make it work:

Goto menu FILE|MOBILE|EDIT CURRENT LOCATION Goto tab MAIL and enter the correct path for "Mail File:" example: it should read "mail\morespace\flabor" and not "mail\flabor"

"morespace" = directory link/pointer

we can forward and reply to emails fine after that fix. The problem is that the user has no incoming email. Domino is still trying to send the incoming mail of that user to its old db location "mail\flabor" instead of "mail\morespace\flabor". Delivery error saying user does not exist.

Is this a cache problem? We have reset the server ("Q" at the prompt), though we have not completely shut it down though.

Thanks Frank

Answer 1

You'll have to change the mail file location specified in the Person document of the Domino Directory.

Answer 2

There is an admin procedures for moving mail accounts, which can be found here for version 6.5/7.0 and here for version 8+.

As you're sort of half way through a move in the scheme of things you could try the following.

1. Goto the relevant person document entry in the Name and Address book (NAB) on the server.
2. Check the mail file setting on the basics tab.
3. Goto your location documents defined in your local NAB, (can be found under Advanced, then select "locations").
4. Typically the location called "online" is the default that users have. Goto the "mail" tab and check the mail file locations there to.

The SMTP router process should pick this up immediately, failing that you can restart the SMTP process, here. Restarting the Domino server or event the host O/S might be a bit of overkill for this sort of activity.