Move email server into the infrastructure project
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 12
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Currently, our email server is hosted with Myra, and not under any sort of version control. It is not even obvious which configurations are in use, and how everything is set up.
The server could ideally move to a different host, as we have had issues with their infrastructure. But we can not move it to Digital Ocean as that would make mail delivery from it nearly impossible as their IP ranges have such a bad reputation.
As part of this move, also investigate how (and if) we can provide a MTA to allow *@php.net to use our mail server to send emails, to satisfy DKIM etc DMARC.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inventorying the current Myra-hosted email server, its configurations, and how the infrastructure project’s Ansible playbooks are organized. Compare hosting options, then investigate the MTA, DKIM, and DMARC requirements for *@php.net. Done means the configuration is version-controlled and the migration and mail-sending approach are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, shell
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100