One of my sites have a returning problem. They rename are user giving him a new certificate (going from /DK/Cert1 to /DK/Cert2) and moves the user to a new Home server. Before Traveler works fine for the user. When the rename and move happens the user appears in the “IBM Lotus Notes Traveler” database both with the old and the new name, and traveler stops working for the user.
Resetting the user with “tell traveler reset * %shortname%” removes the new username from Travler. But the old name is still there. I remove that document manually.
After a while the old username appears again, and when syncing the new one also appears. Travler then gives an error and stops working.
Uninstalling Traveler from device (Nokia) and doing setup again creates the user document with new name, but a document with the old name also appears and the initial sync fails.
Although a different scenario you might want to treat this as a banned user scenario or at least try the commands referenced here from a lenghtly PMR with IBM. By the way, I removed a user via the NSF as well but this is apparently not recommended and it did not do anything. You may find that deleting the security settings work for you.