|
Size: 1614
Comment: rewrote for more clarity and added Caveat
|
← Revision 9 as of 2015-09-02 15:53:50 ⇥
Size: 1765
Comment: Make command formatting consistent
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #pragma page-filename DOC/versions/15958293 | #pragma page-filename DOC/versions/4030624 |
| Line 14: | Line 14: |
| {{{ archives/private/<listname>.mbox/<list>.mbox}}} | {{{ archives/private/<listname>.mbox/<listname>.mbox}}} |
| Line 16: | Line 16: |
| which is where Mailman keeps the cumulative archive mbox for <list>. Then you can run | which is where Mailman keeps the cumulative archive mbox for <listname>. Then you can run |
| Line 18: | Line 18: |
| {{{ bin/arch --wipe <listname>}}} | {{{ bin/arch --wipe <listname> }}} |
| Line 20: | Line 22: |
| to initialize the archive from the default mbox. If you are adding messages to an existing archive, you have two recommended choices. You can run the first command above to add your messages and then append your file.mbox to Mailman's <listname>.mbox, or you can merge the files first and then run the second command with the --wipe option to rebuild the archive. In either case, you should stop Mailman before beginning and start Mailman again after you're finished to prevent Mailman's trying to add messages concurrently with you. | to initialize the archive from the default mbox. If you are adding messages to an existing archive, you have two recommended choices[1]. You can run the first command above to add your messages and then append your file.mbox to Mailman's <listname>.mbox, or you can merge the files first and then run the second command with the --wipe option to rebuild the archive. In either case, you should stop Mailman before beginning and start Mailman again after you're finished to prevent Mailman's trying to add messages concurrently with you. |
| Line 26: | Line 28: |
| Your mbox file must not contain any unescaped lines beginning exactly with 'From ' in message bodies as these will be interpreted as message separators. There is a bin/cleanarch script to help find and fix such lines if any. Run it whit the --help option for more information. | Your mbox file must not contain any unescaped lines beginning exactly with 'From ' in message bodies as these will be interpreted as message separators. There is a bin/cleanarch script to help find and fix such lines if any. Run it with the --help option for more information. |
| Line 28: | Line 30: |
[1] See [[http://mail.python.org/pipermail/mailman-users/2007-April/056687.html|this post]] for some more choices and detail.<<BR>> |
5.1. How do I import an archive into a new mailing list?
If your archive is in mbox format you can import it with
bin/arch <listname> path/to/your/file.mbox
If it's not in mbox format then you need to figure out how to convert it from whatever form it's in to mbox.
If you are importing an archive into a new list which currently has no archives, first copy your .mbox to
archives/private/<listname>.mbox/<listname>.mbox
which is where Mailman keeps the cumulative archive mbox for <listname>. Then you can run
bin/arch --wipe <listname>
to initialize the archive from the default mbox. If you are adding messages to an existing archive, you have two recommended choices[1]. You can run the first command above to add your messages and then append your file.mbox to Mailman's <listname>.mbox, or you can merge the files first and then run the second command with the --wipe option to rebuild the archive. In either case, you should stop Mailman before beginning and start Mailman again after you're finished to prevent Mailman's trying to add messages concurrently with you.
Caveat
Your mbox file must not contain any unescaped lines beginning exactly with 'From ' in message bodies as these will be interpreted as message separators. There is a bin/cleanarch script to help find and fix such lines if any. Run it with the --help option for more information.
[1] See this post for some more choices and detail.
Converted from the Mailman FAQ Wizard
This is one of many Frequently Asked Questions.