ex_integration_coveralls VS mox

We expand based on ex_integration_coveralls. After the Elixir Application is started, a http worker is started up to expose the code coverage data in real time, which is convenient for communication with heterogeneous systems. The Coverage Push Gateway is responsible for regularly pulling the coverage data (Gateway can be a OTP Application, which allows ex_integration_coveralls to directly start up the custom GenServer Worker for interactive integration test system in the distributed OTP system), after the integration/system test system informs the end of the test, the Gateway pushes the coverage data to the Cover Center for code coverage rate display.

It's interesting how there is now

* Maddy: https://github.com/foxcpp/maddy

* Mox: https://github.com/mjl-/mox

* and Stalwart

which all see to aim for more or less the same niche. I wonder if we'll see two of those merge eventually.

Pitching my own: https://github.com/mjl-/mox has a "mox localserve" subcommand that runs a mail server on localhost for testing, including a pedantic mode and special addresses that cause failure conditions you may want to test for. This is actually a full mail server (SMTP, IMAP and much more) and it comes with a webmail client. The "localserve" mode was just so easy to implement that I couldn't resist.

Just run your own mail server on a Pi at home and get your ISP to set up a PTR record for you, assuming you are on a static IP. Mox is good and outputs all of the instructions for DNS etc.:

https://github.com/mjl-/mox

I have setup a mail server (thank you mox ) hosted on VPS in Linode and everything seems fine: no issue on SPF, DMARC, DKIM records, the reputation of the domain and of the IP is okay and the IP is not in any blacklist. Unfortunately, Google and MS are rejecting my emails, even if I added the DNS records that they asked to add in order validate my domain.