How can I change my robot name?
Once in a while, you can feel the need to change your robot name. First, stop Sympa.
Robot renaming in a nutshell
In any case, you first need to create a virtual host corresponding to your new robot name.
Then, you will have to migrate existing list on this new robot.
You will then have to modify or move the following:
- lists' archives,
- lists' spools,
- the database.
These operations can be done following two different steps.
Solution 1: through the web GUI
Once your new robot is created, you can rename (one by one) any list you own. This can be done by using the renaming page in the web interface, following this path in the menu:
Admin → Rename list
In this very simple interface, retype the current list's name in the “New list name:” field then select the new robot name in the drop-down menu.
Confirm changes by clicking the “Rename the list” button.
That's it. All the list's archives, spools and database entries are moved/renamed as necessary in the process.
Go on to the next list, and so on until you renamed all your lists.
Keep on trucking. 
Solution 2: using console
You can also do it the hard way (no, renaming your lists one by one is not the hard way).
You can choose to make these modifications manually, which can be a good option if you have a very large number of lists to move, in which case most of the following operations can be – carefully – scripted.
So, once your new robot is created, this is what you need to do:
Renaming the archives
Your default robot archives are located in the arc/ directory at the root of your Sympa installation.
You need to rename the directories to match the new robot name.
Handle the spools
The spool files must be renamed to match the new robot name.
They have the form: listname@old.robot.name.123456789.12345
It is likely that you will also have to modify the “X-sympa-To” header in the files.
Update the database
Then you must replace the robot name in the database wherever it appears. Looking at the database description, you can see that it appears in the following tables:
However, you just need to change it in admin_table, subscriber_table and netidmap_table (logs are history).
All set!