MX record: all mail sent to addresses at opencraft.com is now processed by mail.opencraft.com. The previous server is still listed as a secondary MX, so if there are issues with the new server, we can quickly and gracefully fall back.
Mailing lists: configuration for these is now at List Index - OpenCraft Mail (you will need to make an account with your opencraft email to log in and adjust settings). The emails subscribed should be the same, but any custom / non default configuration will need to be manually updated.
If something is terribly wrong, and we need to revert to the old setup asap, navigate to the opencraft.com domain dns records in gandi and delete the 10 mail.opencraft.com. MX record. (also check that the mail.plebia.org MX record is still present) Then shut down the server at mail.opencraft.com. This should immediately revert everything back.
Kudos to @toxinu for helping with the migration and testing!
That’s it for now. More updates to come soon as we update docs, migrate archives, etc.
Nothing has touched relay.net.opencraft.hosting as part of mail migration, so that sounds like an unrelated issue. I don’t see those credentials defined in POSTFIX_SASL_USERS in ansible-secrets, so probably a recent run of that playbook has overwritten any temporarily added credentials.
There should be; I don’t know what’s happening there…
:/ Unfortunately not unless we contribute to the mailman project. However, the version installed is somewhat old (it’s the newest that is available in the ubuntu 18.04 repos). A lot of bugs were fixed between then and now. We can upgrade as soon as the playbooks work with ubuntu 20.04.
Search certainly should work. Will do some debugging on this.
Please note that we’re in a weird transition period, where many applications have the previous MX records still cached, so mail.plebia.org is still handling a lot of email for opencraft.com. If you don’t see an email in the new mail.opencraft.com archives, you may need to check the old archives address on plebia.org. This could go for several days.
That’s great news I’m glad there’s a possibility of a low-friction fix, and I can deal with a little inconvenience until then.
And your updated docs make this even easier, thank you!
That would have been me… added a postfix user to the relay server as part of ansible-secrets#283. The good news is, you should be able to follow the instructions on that PR to add your missing credentials for Sprints.
I don’t know where/if that was configured. firstname.lastname@example.org was previously an alias that pointed to xavier@ and gabriel@. Now it’s an unarchived mailing list with only gabriel and xavier subscribed. Perhaps @antoviaque or @gabriel had a filter in their mail software (gmail, fastmail) that did the forwarding?
I created it as private because we’re discussing a lot of internal/private details - private docs, private mailing lists, details about email addresses, etc. If you think that’s ok to be public, then sure, but I felt it safer to be private to avoid leaking anything sensitive.