mujmap VS spec

Put everything into a single notmuchmail database. It wil deduplicate the emails and even provide a fast local search interface for all of your mails https://notmuchmail.org/

For gmail you can use lieer to pull everything https://github.com/gauteh/lieer (tho it can take hours to pull ewerything). Fastmail has a similar tool https://github.com/elizagamedev/mujmap

If you unpack tour mbox into maildir then you can import that too into notmuch

After everything is in notmuch you can easily push everything to fastmail with isync/mbsync https://isync.sourceforge.io/

As a bonus point you now also have a easily updatable local backup of your e-mails.

- It's far simpler to implement, once email verification is taken care the actual Domain Verification check is five lines of code.

> It works, and works well, and is supported by all the major domain providers.

You're right that registrar adoption is quite high, which is because it was a GoDaddy and 1&1 (now IONOS) initiative but when I last checked it wasn't implemented at Google, Facebook and many of the others larger providers for domain verification (to be clear: neither is my solution!!!)

1. https://github.com/Domain-Connect/spec/blob/master/Domain%20... (http://www.domainconnect.org currently failing with cert expiry)

2. https://news.ycombinator.com/item?id=35828772

3. https://domainverification.org/create-record

IMO this is an API that should be implemented on your end (dnsimple), not theirs. There are a relatively small number of DNS providers which all provide essentially the same interface (CRUD operations on records), but there are a huge number of services that need to set up DNS records, including open source projects self-hosted by many individuals. It's not realistic for DNS providers to implement integration with every possible service, but the opposite is totally doable.

If dnsimple implemented something like DomainConnect, Fastmail could easily integrate. And it's a win-win because it sends traffic your way.

As I said, I found[0] DomainConnect to not be a good fit for open source projects in its current form. I've done some work on a new protocol which you can learn more about here[1]. Would be interested to hear your thoughts from the perspective of a DNS provider.

[0]: https://github.com/Domain-Connect/spec/issues/64

[1]: https://takingnames.io/blog/introducing-takingnames-io

Yeah, I read the website and the entire spec. I think it's pretty good, but it's built by big names for big names. There's nothing wrong with that, but I'm concerned it might not be appropriate for things like self-hosting open source projects. Hopefully I'm wrong. I'm having a good discussion with the spec developers here: https://github.com/Domain-Connect/spec/issues/64