Rationalise MX across domains
Closed this issue · 3 comments
sebbacon commented
Email DNS and forwarding configuration is currently spread across webfaction, gandi, cloudflare and mailgun.
Move all domains to be handled by cloudflare (DNS) and mailgun (forwarding).
Currently, we set up specific mailboxes to forward to be support, and a catch-all to tech@.
Currently on cloudflare (mx in parens):
- op2.org.uk (mailgun)
- openprescribing.net (mailgun)
- retracted.net (mailgun)
- compare-trials.org (none)
- theycareforyou.org (none)
- openpathology.net (none)
- trialstracker.net (none)
- ebmdatalab.net (webfaction)
Currently MX/routing on mailgun (but only some set up to forward to the shared inbox):
- op2.org.uk
- openprescribing.net
- retracted.net
So the actions are:
- Change all existing routing in mailgun to route to shared inbox
- Set up routing rules in mailgun for ebmdatalab.net
- Set up DKIM/SPF for ebmdatalab.net (or not... do we every reply AS that domain?)
- Change ebmdatalab.net MX to mailgun
sebbacon commented
Current webfaction mailboxes for ebmdatalab.net:
- all
- compare-admin
- compare-team
- hello
sebbacon commented
Testing log:
- hello@retracted.net and hello@openprescribing.net both got to the shared inbox. Only the former got picked up in slack
- hello@ebmdatalab.net currently bouncing but this may be a lag in mailgun route updates
- but compare-team@ebmdatalab.net did receive a (junk) mail at 11:17
sebbacon commented
OK now they're all getting through