Importing from sympa¶
There is a script to do that, called
scripts/import.sympa.py. It tries to import configuration, subscribers, and archive for one list at a time. Not everything is imported, but most of it is... and the script is currently not very well tested. Though some real import were done successfully.
- you do not need to provide them again
- double check those files before trying to import
You need to start the script from the main colibri directory. If you start it with no argument, you'll be given the usage:
% ./scripts/import.sympa.py You need to supply exactly two arguments to this script: * the path for the main directory of sympa * the path for the web configuration file sympa.conf * the name of the mailing list to import Example : scripts/import.sympa.py /opt/sympa /etc/sympa.conf test\@mysite.org
Here is an example
# ./scripts/import.sympa.py /opt/sympa /vservers/web/etc/sympa.conf firstname.lastname@example.org -> Created new list email@example.com -> Imported 37 subscribers, created 34 new users/profiles -> Import archives from '/firstname.lastname@example.org' -> The colibri archive dir is '/usr/olocal/www-rw/colibri/rw/archives' importing /email@example.com/2008-06/arctxt -> /firstname.lastname@example.org/2008/6/text importing /email@example.com/2007-05/arctxt -> /firstname.lastname@example.org/2007/5/text importing /email@example.com/2005-05/arctxt -> /firstname.lastname@example.org/2005/5/text ...
The script does a lot of checks, and should hopefully give meaningful message when a problem is found.
In this example, 3 subscribers already had an account in the database. They were recognized only using the email address, which is compared to all (primary and secondary) addresses known in the colibri database.
Once the script was run, double check owner/group/permissions for the directories/files created in rw/archives.