Bonjour, Today I start working on a python script to migrate a mailman2 mailing list (archives and config.pck) using the discourse API only. If anyone is interested, it is happening here and I’ll update this topic with progress. Any comment on whatever people need or comments about how to better d…

For the record, the migration script reached a stage where it is usable and a HOWTO is available: [Bild] HOWTO migrate from mailman2 to discourse support I started working on this script last year and had the opportunity to put it to the test in May 2021 when migrating th…

digest_members : discarded. It is not possible to request a digest mode on a per-category basis. Maybe “Watching first post” would be a rough equivalent, depending how often there are new threads/topics and how often in practice a digest was sent on the list.

A first version of the script was published at mailman2discourse · PyPI . It works for me, hopefully it will also help others. If not let me know and I’ll try to adapt the script.

How does it deal with lists where from_is_list is set to Munge From or Wrap Message (or the equivalent DMARC-only settings are used)? Is it able to work out which user sent those messages?

It does not, I’ll take a look at what it would require.

Thanks. If it helps, the original sender’s email address appears often (always?) appears in the “Cc:” header of the email, at least when from_is_list is Munge From.

from_is_list from_is_list This applies to all non-digest messages sent by the list. For settings that apply only to messages whose From: domain publishes a DMARC p=reject or p=quarantine policy, see the dmarc_moderation_action description in the Sender filters section. If set to Munge From, it …

Maybe your question is related to how mails are imported from the archives rather than implementing the feature in Discourse?

Discourse operates essentially in the same way as Mailman 2 with from_is_list = Munge From – with those settings every Mailman list email is “From: listname@example.com ” (rather than “From: joebloggs@email.com ”) – and similarly every email notification from Discourse is from the same forum email add…

Thanks for explaining. The mailman2discourse script does not play a role in this because it does not import the messages. The import of the messages is done via the Discourse mbox importer . I think it would set the author of all mails to listname@example.com . I do not see anything in discourse/scri…

I see now, thanks. Unfortunately I’ve also got reply_goes_to_list set to “This list” (which changes the “Reply-To:” header) so we’d have to think of another solution. Or maybe not… I’ll post a question to the other topic. Thanks for your help.

Skript für Mailman2 zu Discourse-Migration wird erstellt

Unterstützung

dachary (Loïc Dachary) 12. Juni 2021 um 22:50 12

Für die Akten: Das Migrationsskript hat einen Zustand erreicht, in dem es nutzbar ist, und eine HOWTO ist verfügbar:

2 „Gefällt mir“

Thema		Antworten	Aufrufe
HOWTO migrate from mailman2 to discourse Support	2	1229	12. Juni 2021
Convert mailing list to self hosted discourse Migration	1	928	5. Januar 2020
Continuing to run Mailman and Discourse using the exact email addresses (as Mailman) in parallel Migration	5	1547	11. Februar 2022
Forwarding long email chains to Discourse Feature	5	1980	5. April 2018
Can Email-In be used to "ingest" a mailing list? Support	11	2655	9. Februar 2023

Skript für Mailman2 zu Discourse-Migration wird erstellt

Verwandte Themen