Actions
Feature #3307
openFeature #3076: migrate to new (2018-03) server "host2.osmocom.org"
migrate mail.osmocom.org / lists.osmocom.org to container on host2
Start date:
05/29/2018
Due date:
% Done:
30%
Spec Reference:
Checklist
- actually run a MTA on host2
- configure MTA / mailman setup, test it using a test mailing list
- nginx reverse proxy with /static
- atomically import list configs + archives + port-forward from old server
- update DNS to point to host2 for web + MTA
- letsencrypt for posterious+hyperkitty
- ensure old machine relays mails for lists.osmocom.org
Related issues
Updated by laforge over 3 years ago
- Related to Feature #3305: migrate openmoko.org mail + lists to osmocom.org added
Updated by laforge about 3 years ago
- Checklist item actually run a MTA on host2 added
- Checklist item configure MTA / mailman setup, test it using a test mailing list added
- Checklist item nginx reverse proxy with /static added
- Checklist item atomically import list configs + archives + port-forward from old server added
- Checklist item update DNS to point to host2 for web + MTA added
- Checklist item letsencrypt for posterious+hyperkitty added
- Status changed from New to In Progress
- % Done changed from 0 to 30
- mailman3 containers running for web, core, postgres
- lists have been re-created in mailman3
import of lists/archives has been tested for osmocom.org in #3305, worked fine so far. Migration of lists.osmocom.org will be done at a later point after the entire setup has been properly tested.
Updated by laforge about 3 years ago
- Checklist item ensure old machine relays mails for lists.osmocom.org added
Actions
