This shows you the differences between two versions of the page.
Next revision | Previous revision Last revision Both sides next revision | ||
userdoc:lore [2018-09-13 20:21] mricon created |
userdoc:lore [2018-11-12 14:08] mricon |
||
---|---|---|---|
Line 27: | Line 27: | ||
- Switch to "Filters and blocked addresses" tab | - Switch to "Filters and blocked addresses" tab | ||
- Click "Create a new filter" | - Click "Create a new filter" | ||
- | - In the pop-up window, put the list address in the "To" field | + | - In the pop-up window, put the list address in the "Include these words" field |
- | - This is better than using the "List-Id" because that will exclude your own messages sent to that list | + | - This is better than using the "List-Id" because doing so will exclude your own messages sent to that list |
+ | - Do not worry, if anything extra is caught in this sweep, it will get filtered out during the next step | ||
- Click the "Search" button to make sure this looks sane | - Click the "Search" button to make sure this looks sane | ||
- Click the dropdown arrow in the search field to bring up the popup again | - Click the dropdown arrow in the search field to bring up the popup again | ||
Line 115: | Line 116: | ||
<code> | <code> | ||
- | tar full-archives.tar dir-with-mbox-files | + | tar cf full-archives.tar dir-with-mbox-files |
xz -9 full-archives.tar | xz -9 full-archives.tar | ||
</code> | </code> | ||
- | If the resulting file is smaller than a few MB, you can attach them to follow-up email to helpdesk@kernel.org. If the archive is larger than that, please upload it to a file sharing service, such as Google Drive: | + | If the resulting file is smaller than a few MB, you can attach it to the follow-up email to helpdesk@kernel.org. If the archive is larger than that, please upload it to a file sharing service, such as Google Drive: |
- Upload the .tar.xz file to drive.google.com | - Upload the .tar.xz file to drive.google.com | ||
Line 127: | Line 128: | ||
The kernel.org administrators will combine the archive they receive from you with the messages they have pre-collected, to make sure there is no interruption between when your archive collection was completed and when public-inbox starts receiving new messages. You will be notified when the mailing list is ready to be accessed via lore.kernel.org. | The kernel.org administrators will combine the archive they receive from you with the messages they have pre-collected, to make sure there is no interruption between when your archive collection was completed and when public-inbox starts receiving new messages. You will be notified when the mailing list is ready to be accessed via lore.kernel.org. | ||
+ | |||
+ | ====== Can you use mailman archives? ====== | ||
+ | |||
+ | We *can* use mailman's pipermail archives, but it's best if it's done as a final filler for anything not collected elsewhere, for these reasons: | ||
+ | |||
+ | - Mailman's pipermail .gz archives are not, technically, valid mailboxes (they don't properly escape "From " in message bodies). They must be mangled in order to be properly imported. | ||
+ | - They have bare minimal headers that don't include any "Received" lines, original recipients, cc's, or List-ID. | ||
+ | - They mangle the mime structure of the message to scrub any attachments, including digital signatures. | ||
+ | - They escape email addresses to make @->" at " replacements, which must then be replaced back. | ||
+ | |||
+ | We suggest you proceed with archive collection per above, and then fill in any missing bits with pipermail archives as the last step (the list-archive-marker.py script has automated functionality to do this). | ||
+ | |||