This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
userdoc:lore [2018-09-21 16:40] mricon |
userdoc:lore [2018-11-12 14:08] mricon |
||
---|---|---|---|
Line 128: | 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). | ||
+ | |||