Make sure system emails are delivered from any QA branch.

[treasuretron]

In GitLab by @richbodo on Dec 4, 2018, 16:01

Primary goal is science. Document what you find about outbound system email capabilities with mailgun so that others can build upon that knowledge.

Secondary goal is to make sure that outbound system email sends through as many QA environments as possible.

We can definitely make sure that outbound system email sends from dev through the mailgun API. We'll just trash the beta.spacebase.co url, use mail.spacebase.co for production, and dev.spacebase.co for dev. An hour of config and testing and we're done.

We might be able to make mailgun accept outbound API delivered mail from any platform.sh domain (so that mail delivery can be tested with any QA envinonment. Need to see what mailgun can do. Accepting from any platform.sh domain sucks so we might want to not do this some other way)

We might be able to make mailgun send via account/key from any rando IP address with no round trip DNS so that everyones local can use it. Probably get caught in spam filter but that's o.k. for QA.

Resolve this issue by doing the best that can be done in the time we have - create more issues as needed - we probably want documentation for sending from local.

I'm happy to set up postfix instances that can do basically anything if mailgun doesn't satisfy us, but lets try mailgun first.

Start documenting this stuff from this point in the wiki:

https://gitlab.com/spacebase/spacebase/wikis/mailgun

[treasuretron]

In GitLab by @richbodo on Dec 4, 2018, 16:20

changed the description

[treasuretron]

In GitLab by @richbodo on Jan 2, 2019, 17:47

removed milestone

[treasuretron]

In GitLab by @thomasmurphy on Feb 25, 2019, 22:15

assigned to @jayelless and unassigned @richbodo