Dear Developers,
Since 11th July sourceforge has changed the way they're giving us access to our mailing list log. It used to contain the full email mbox for all the messages sent to the system.
Now they are giving us smaller, stripped mbox files that aren't as complete. I believe all messages are there, but headers are modified and email addresses are changed to bryce@...3609... etc.
We've been collecting our mailing list records ever since we started planning moving our mailing lists away from sourceforce. When it comes to do the import into the new mailman, I'm going to try and retain as much of the old messages as possible and then add on the stripped messages since then, but it would be nice to have the full log.
If anyone has a complete record of inkscape messages, please let me know. (also double cool if we have pre-sourceforce records, but no worries if they're lost to time)
Best Regards, Martin Owens
On Thu, Sep 14, 2017 at 05:49:18PM -0400, Martin Owens wrote:
Dear Developers,
Since 11th July sourceforge has changed the way they're giving us access to our mailing list log. It used to contain the full email mbox for all the messages sent to the system.
Now they are giving us smaller, stripped mbox files that aren't as complete. I believe all messages are there, but headers are modified and email addresses are changed to bryce@...3609... etc.
We've been collecting our mailing list records ever since we started planning moving our mailing lists away from sourceforce. When it comes to do the import into the new mailman, I'm going to try and retain as much of the old messages as possible and then add on the stripped messages since then, but it would be nice to have the full log.
If anyone has a complete record of inkscape messages, please let me know. (also double cool if we have pre-sourceforce records, but no worries if they're lost to time)
Best Regards, Martin Owens
I can probably send you files for July, August, and repeat until you move the lists, but there will be some issues:
1. I rotate my mbox files early on the 1st of the month in local time - I guess that doesn't matter, 11th July will definitely be within my July mbox, as will earlier mails.
2. I'll need to edit the mbox (I have several lists dropping into the same mbox) - possibility of accidentally deleting an inkscape mail from the copy.
3. And of course I didn't necessarily *receive* everything (a small amount of mail from all lists seems to fall through the cracks).
4. The real problem is headers - my own posts tend to have <SPAM> added to the subject by my ISP when they arrive here. But apart from that I add an X-Clacks overhead, and some headers from SpamAssassin, and of course all my mails have a chunk of headers starting "delivered to ken@...33..." through to various "received from" entries for my ISP, on top of the headers from sourceforge.
That last point is the bugbear - I don't want to go through editing the headers one-by-one to remove that information.
ĸen
Thanks for the help Ken,
On Fri, 2017-09-15 at 00:33 +0100, Ken Moffat wrote:
- The real problem is headers - my own posts tend to have <SPAM>
added to the subject by my ISP when they arrive here. But apart from that I add an X-Clacks overhead,
The website does that ;-) check the headers.
and some headers from SpamAssassin, and of course all my mails have a chunk of headers starting "delivered to ken@...33..." through to various "received from" entries for my ISP, on top of the headers from sourceforge. That last point is the bugbear - I don't want to go through editing the headers one-by-one to remove that information.
Anything I get is going to have to be processed via a script. Python has pretty good mailbox support, so it's just a matter of you being able to collect them all into a zip on request.
Best Regards, Martin Owens
participants (2)
-
Ken Moffat -
Martin Owens