[kodablah]

> You can use Mailinator to do this already

While I'm a fan of Mailinator and their approach, I think the feature OP has about auto-clicking verify is unique. But yes, to do this right, you need the multi-domain approach of Mailinator instead of just aliases. Maybe Mailinator has an API or supports POP/IMAP that would make this possible, I haven't checked.

[naniwaduni]

Also exists: https://mailnesia.com/

[imhoguy]

You can easily use one of many opensource self-hosted temporary email projects with APIs. Just check Github.

Receiving email is pretty easy - own domain with MX record and some cheap VPS with Docker. No need to worry SPF, DKIM, DMARC, DSBL - you care about these when you have to send emails from the host.

[elamje]

If the site you are trying to login in to blocks mailinator, use <whateveryouwant>@notmailinator.com

[bionoid]

Last I checked it appeared like Mailinator's POP3 support was completely removed, and API access requires a subscription. It was priced way above what I was willing to pay (I think $150/mo)

[close04]

Also Mailinator is banned by multiple sites and I feel like that number is increasing (anecdata). Which means it's getting less and less useful for the purpose of "burner" email addresses.

[cenal]

You can point your own domain to mailinator mx records for free.

Don’t have a domain to throw spam at? Pick a sub domain and use that.

[close04]

I used Mailinator as the quick solution to access some one time resources on websites that forced me to register. It was the simplicity of the throwaway email that made it attractive to me. But when it's blocked on a website I usually wouldn't want to bother with c more complicated setup. If the effort is justified then I can probably use a regular email address. Other people might have different use cases.

[CapacitorSet]

Pointing your MX records to Mailinator is a one-time small effort, then it's just a matter to sending mail to [e-mail].

[close04]

I'm not sure if my use case was clear or perhaps I don't understand what the scenario you present does.

Say I want to comment on a news article and need to register. I don't want random-newspaper.com to have anything directly related to my person, including anything @mydomain.com. So I quickly punch in [e-mail] to register and once I'm done I can either forget the site and email ever existed or keep using it since it's non critical and losing access to it doesn't matter.

Ideally I would have different email addresses for every site so I can keep those identities separated and free of any personal information. Last time I used it like this was probably a decade ago because since then more and more sites starting rejecting @mailinator.com addresses. I found another such solution that I have been using for the past years but this is also going the same way (not a big issue yet).

[Dolores12]

service will check MX record of your email and refuse to register if it match mailinator's MX.