Had a recent issue with a customer using Traveler 9.0.1.4 on Domino 9.0.1.4 where one user had three devices listed all with the same device ID (so essentially the same device). All devices were inactive and we wanted to clear them up. So, I issued the usual console commands:

1. Tell Traveler Delete * <username>
2. Tell Traveler Security Delete * <username>

but Traveler kept saying that no devices were found for the user. Issuing Tell Traveler User <username> confirmed that there were indeed no devices associated with the user. However, in the back-end SQL database i.e. https://lotustraveler.nsf the devices were still showing !

So that means that devices still have records within the SQL database itself and so I approached an SQL DBA (after reading an IBM technote suggesting this) and there were hundreds of tables in the Traveler SQL database so that line of investigation ended right there.

IBM came to the rescue though with a couple of very handy commands which my good friend Google search could not find which is why I’m sharing this with you:

“To manually remove the orphaned users and devices from the SQL db, you
may execute the following command:
.
tell traveler sql delete * from USERS where username=’fully qualified name’
Note: The name has to be within single quote.
.
tell traveler sql delete * from DEVICE where username=’fully qualified name’
Note: The name has to be within single quote.“

So as an example:

tell traveler sql delete * from USERS where username=’CN=Jo Bloggs/OU=Sales/O=Acme’

tell traveler sql delete * from DEVICE where username=’CN=Jo Bloggs/OU=Sales/O=Acme’

And there you have it…

The first steps taken were checking the SMTP headers to see had the message been modified by the mail gateway (McAfee).  Everything looked normal.  Checked the Domino logs, nothing unusual there.

Eventually we figured out, the common linkage was that the messages effected were last modified by the Traveler server.  The issue affected Traveler 9 users (who are all Apple iPhone/iPad users on this site) setting follow up flags from their devices.  Once a follow up flag is set on an external sender mail, then the “Who” column displays the person who received the mail rather than the sender in the Notes client (It remains fine on the iPhone/iPad however).

After opening a PMR with IBM, they  didn’t offer an immediate solution but started using the term “principal” field and have escalated to development (at the time of this writing we are still waiting to hear back) we managed to search online ourselves and find this -

http://www-01.ibm.com/support/docview.wss?uid=swg1LO77840

I have to say the title “SET AS FOLLOW UP MAY SET PRINCIPAL TO RECIPIENT” isn’t intatuively understood, but when we read :-

“If user flags a mail for follow up on a Mobile device and the message does not have the standard Principal field, Notes Traveler will mistakenly set the user as principal instead of the sender. This problem is only seen with the 9.0.1 Gold release.”

We understood the issue was exactly the same as ours, though it wasn’t exactly easy to find.  The issue is fixed in 9.0.1 IFI 1.  We’ve installed 9.0.1 IFI2 and the issue was resolved. Implementing the fix does not change back mails that were previously “changed” by the Traveler server.

Quite a simple fix, but even IBM’s own support couldn’t tell us the documented fix!

Another example of the good practice of ensuring that your Traveler server has the latest fix packs and interim fixes applied.

Hope this helps someone else out!  Let us know if it does.

Cormac McCarthy – Domino People Ltd

tell traveler cleanup and tell traveler netaddr

 “tell traveler cleanup” is designed to force the removal of users that haven’t connected since the allocated cleanup period, [based on what is in the Server Document for the Traveler server, “IBM Traveler” Tab,  “User Cleanup Timeout” field (default is 30 days)].  Note that this should happen automatically with the server in the background.

From running “tell traveler cleanup help” we can see the usage information as follows:

Usage: tell traveler Cleanup <option>

Where <option> includes:

•   Users – Remove all devices where the last sync time is older than the user cleanup timeout.

•   Bind – Clean up BIND table entries for unknown server

Running the command without a switch runs both Users and Bind command.

“tell traveler netaddr” tells you which network interfaces are available to Traveler and also. as importantly, which network interface it is  actually using.  I’d imagine this would be a great resource during a migration to new hardware/OS.

From running “tell traveler netaddr” we see the usage information as follows:

(ip address being used is pixelated obviously!)

Let us know if you’ve found this useful or if you’d like any advice on a Traveler 9 deployment!

Cormac McCarthy – Domino People Ltd