Project

General

Profile

Feature #3305

Feature #3303: migrate openmoko.org into "archive mode" and remove dedicated server for it

migrate openmoko.org mail + lists to osmocom.org

Added by laforge 11 months ago. Updated 6 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
05/29/2018
Due date:
% Done:

60%

Spec Reference:

Description

As per http://lists.openmoko.org/pipermail/community/2017-October/069832.html

   * lisst: migrate the single remaining active
     (community at lists.openmoko.org) to another mailman instance, such as
     lists.osmocom.org.  We could configure mailman to retain the
     list-id and simply point the MX to the osmocom.org server, i.e. do
     this without any impact on the list address or users mail filtering
     rules.
   * e-mail: discontinue e-mail services at openmoko.org (except e-mail
     forwarding).  To my knowledge, only Joerg Reisenweber is using this
     service today - and to be fair, I would kindly suggest to use a
     different imap-capable home for his e-mail after about a decade
     of using the Openmoko legacy. Sorry :)

I think rather than completely discontinuing it, we can migrate it to osmocom.org where we already run mailman and a MTA. Only part missing is cyrus-imapd, which would make a nice addition on osmocom.org, anyway.


Related issues

Related to Osmocom.org Servers - Feature #3258: migrate to mailman3 + HyperKittyIn Progress2018-05-11

Related to Osmocom.org Servers - Feature #3307: migrate mail.osmocom.org / lists.osmocom.org to container on host2In Progress2018-05-29

Related to Osmocom.org Servers - Feature #3085: where to migrate openmoko-backup?In Progress2018-03-19

History

#1 Updated by laforge 11 months ago

  • Subject changed from migrate openmoko.org mail + lits to osmocom.org to migrate openmoko.org mail + lists to osmocom.org

#2 Updated by laforge 11 months ago

actually, it probably makes sense to run the entire lists.openmoko.org installation as a separate container on osmocom.org infrastructure. This way we don't get possible naming clashes with and or the like.

#3 Updated by laforge 11 months ago

  • Related to Feature #3258: migrate to mailman3 + HyperKitty added

#4 Updated by laforge 11 months ago

  • Related to Feature #3307: migrate mail.osmocom.org / lists.osmocom.org to container on host2 added

#5 Updated by laforge 10 months ago

  • Related to Feature #3085: where to migrate openmoko-backup? added

#6 Updated by laforge 10 months ago

laforge wrote:

actually, it probably makes sense to run the entire lists.openmoko.org installation as a separate container on osmocom.org infrastructure. This way we don't get possible naming clashes with and or the like.

If we first migrate to mailman3, then it would support the same mailing list name at different host/domain names.

#7 Updated by laforge 6 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 60
  • mailman3 containers running for web, core, postgres
  • list configuration has been converted to mailman3 for all lists
  • all archives have been imported into hyperkitty

pending tasks see checklist of #3307 and here

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)