Well, that’s a massive bummer!
I thought Google hadn’t touched it since February 2015, but I stand corrected.
Looks like there was a complete redesign in 2020 and a logo touch-up in 2021.
I am thinking of using the APIs of GMAIL and Discourse and convert mail thread to discourse post. I have gone through the google apis and was able to get the emails but have a few questions about them.
- Mail can be downloaded in raw format which is the base64 encoded value of “Original message” of mail. Is that the same as mbox format or is it different?
- Is there any sample example of how to add posts and attachments to discourse through API?
Interesting. Is it possible to use the Gmail API to access emails from Google Groups or do you simply have a Gmail account that has all the emails that were sent to the group?
I suggest you save all message into individual *.eml files. You will need to decode the message before saving if the whole message (including the email headers) is base64 encoded. Afterwards follow the steps from Migrate a mailing list to Discourse (mbox, Listserv, Google Groups, etc) (minus the Google Groups steps). The import script will take care of posts, attachments and a lot more.
1 个赞
I am a member of the group so I am able to pull the mails using my email. The entire email message including headers will be part of the encoded string.
Will try your approach for import into discourse at least for a thread.
1 个赞
Well, in that case you might not even need the Gmail API. Connecting an email client like Thunderbird to your Gmail account and exporting individual emails or an mbox file should be enough…
Now I’d really like to know how this works. I was under the impression that Google Groups doesn’t support NNTP.
1 个赞
It’s not NNTP but Rest API.
3 个赞
My mailbox size is more than 200GB and to get specific group-related emails I might need to download all these mails using thunderbird also thunderbird is not showing the google groups all mails are under Inbox only. It is also downloading only 200 emails each time. So, I am not sure how long it could take to get mails etc.
Is there any alternative way to just get a google group data and export it to mbox?
Hi Gerhard Schlager,
We are trying to migrate our google groups to Discourse we followed all the above steps as per the document but it only creates the category in Discourse and not importing the data. Would really appreciate if you can respond on this one quickly.
The only way that we knew about doesn’t work anymore. If you know any way to get the data, then you should do that. If you know a way to get it, you should probably start getting it asap before that method too goes away.
If it’s in your mailbox then it might be possible to use that Gmail api to pull it down. It’ll be tricky though, as a developer would need access to a mailbox with google group data in it to write the code.
Unless an enterprise customer who requires it, I doubt that cdck (aka discourse.org) will be writing that code any time soon. You can ask in marketplace. I likely wouldn’t consider it for under $2000 and, given the frustration that I have had with the Google groups import script on the past, would likely require $5000. Or course, someone else may have better skills or more patience.
One approach that may work is using Integromat to write a conversion assuming google groups and discourse apps are available. Or using the http calls to call the rest APIs on their own.
Integromat is an integration data migration system. It’s very powerful and can do a lot with little to no coding.
我已经尝试过 Google Takeout，将自己设为我们的 Google Workspace 群组的所有者，并能够下载 Google 群组的对话。目前仍在尝试导入。
这种方法有几个缺点。
- 如果需要进行增量更新，则需要再次下载完整数据。
- 无法下载选择性的群组数据，而是会下载用户拥有所有者或管理员权限的所有群组的数据。
- 需要与 Google Workspace 管理员合作启用 Takeout，因为它默认情况下是禁用的。
3 个赞
您好 @Anjana_Raghavendra_P - 您是否设法使用此方法进行了简单的导入？
非常感谢！
是的，我能够从 takeout 下载 mbox 文件，并按照原始帖子中提到的步骤进行导入。
后来，由于我们使用的是 Discourse 的 PAAS 服务，因此将文件提供给了 Discourse 技术团队，他们成功地将内容导入了 Discourse 平台。
2 个赞
很高兴听到这个消息 - 谢谢！
我在 settings.yml 中将第一行 data_dir: /shared/import/data 从默认值更改时遇到了 @sturdy2 的问题。
要点：不要更改它，因为它指的是导入 Docker 内部的路径，而不是主机器上的路径。
我有一个关于重新启动导入的问题？
我不是开发人员，但我设法成功导入了来自 Topicbox Group Email 的两个 mbox 文件。我将我的测试导入设置在 Digital Ocean 上设置的 Discourse 的临时实例中。并且，由于上面关于设置 category.custom_fields["import_id"] = "mydir" 的说明，我能够将我的两个 mbox 样本文件导入到我已创建的 Discourse 的现有类别中。
太棒了！但是，如果我想导入更多 mbox 文件，我是否必须运行 FAQ 2.2 中提到的所有命令，该命令指示它将“删除所有内容”？
2 个赞
我成功地为两个不同的类别设置了我的“import_id”作为初始测试导入。它奏效了！我的两个 mbox 文件已导入到我指定的现有类别中。
我最终需要处理 18 个不同的类别。我对 Ruby 一无所知。我能否创建一个文件来为我的每个不同类别设置目录名称，这样我就不必在 Ruby 命令行界面中手动输入每一行？
2 个赞
是的。搜索更多 Google “ruby for each”。并创建一个包含部分类别的数组。
1 个赞
不，你不需要。导入器支持增量导入。下次运行时，它只会导入新数据。除非你想从头开始，否则请不要运行 2.2 中提到的命令。
不幸的是，目前还不可能。如果你想导入到现有类别中，则必须为每个类别分配 import_id。
2 个赞
感谢 @gerhard 如此出色的工作！我不是开发者，但我成功地从一个名为 Topicbox 的邮件列表系统迁移。我从 Topicbox 获取了 mbox 文件导入 Discourse。在试错过程中，我将所有内容记录在了博客文章中。所以，如果可以的话？我想在此分享这篇博客文章的链接，供其他想要迁移到 Discourse 的 Topicbox 用户参考。
4 个赞