Live data from Hacker News

Receiveee.com - disposable email address

receiveee.com

81–90 of 127 posts

Re: Receiveee.com - disposable email address

#81
post #79

For anyone wanting to stop signups from disposable email addresses I've found this service to be really good: http://www.block-disposable-email.com has a massive database and a bounty for new additions! We have 2 factor verification for http://8centsms.com/ but with the advent of disposable inbound SMS numbers via Twilio as well as disposable email addresses we were getting a bunch of people signing up and getting th…

I use disposable emails only to signup to services. I later save the email and pwd with 1Password. I've been doing this for a long time.

The reason I do this is because many startups (and non-startups) keep abusing on the amount of email they send you, even if I unsubscribe from their "newsletter" they come up with other non-newsletter emails - and this is just unbearable. I feel like being spammed most of the time.

The advantage of using disposable email is that I have access to the service, I decide when I receive emails and it's a great way to protect my account from being hacked (think of any recent social eng hack a la Amazon, Apple, etc. they couln't do it without your signin email).

A handful of other colleagues do the same thing. If you blacklist users who want to protect their privacy and want control over their inbox all you are doing is blocking (in our case) affluent users.

Re: Receiveee.com - disposable email address

#82
post #79

For anyone wanting to stop signups from disposable email addresses I've found this service to be really good: http://www.block-disposable-email.com has a massive database and a bounty for new additions! We have 2 factor verification for http://8centsms.com/ but with the advent of disposable inbound SMS numbers via Twilio as well as disposable email addresses we were getting a bunch of people signing up and getting th…

[deleted]

Re: Receiveee.com - disposable email address

#83
post #49

Earlier quoted context omitted.

Mailinator has a ton of different domains. You can check them all from mailinator.com though.

You can't get a full list of them on mailinator.com, since it makes it easy for a misguided website administrator to just ban the whole list. Instead, the site will randomly show one of the alternate domains on every page load. At one point, it would even give 'gmail.com' and other legitimate domains as the alternate if you tried to scrape them too quickly (or rather, they hypothetically-yet-definitely-didn't-do that…

You can still ban Mailinator by simply resolving DNS (or even only MX record) and reject if it matches 72.51.33.80.

Re: Receiveee.com - disposable email address

#86
Question for business owners/founders: how do you feel about people signing up for your services with these throwaway email addresses?

On the one hand, I respect people's privacy and right to use whatever email address they like.

On the other (more relevant) hand - I sometimes need to contact users who violate terms and conditions that their access may be switched off (I'd never do this without contacting them 2-3 times). Also, I might need to inform them that something has changed which might affect their usage. My service can be quite integral to a lot of apps, so to me that's an important feature...

Thoughts?

Re: Receiveee.com - disposable email address

#87

Question for business owners/founders: how do you feel about people signing up for your services with these throwaway email addresses? On the one hand, I respect people's privacy and right to use whatever email address they like. On the other (more relevant) hand - I sometimes need to contact users who violate terms and conditions that their access may be switched off (I'd never do this without contacting them 2-3 ti…

I'd be fine if people signed up with these to try it, but they should use a permanent address if they want to continue using it. I would have no sympathy at all if they lost their account.

Re: Receiveee.com - disposable email address

#88
post #83

Earlier quoted context omitted.

You can't get a full list of them on mailinator.com, since it makes it easy for a misguided website administrator to just ban the whole list. Instead, the site will randomly show one of the alternate domains on every page load. At one point, it would even give 'gmail.com' and other legitimate domains as the alternate if you tried to scrape them too quickly (or rather, they hypothetically-yet-definitely-didn't-do that…

You can still ban Mailinator by simply resolving DNS (or even only MX record) and reject if it matches 72.51.33.80.

That will only work if you know exactly how your entire mail stack will handle resolution and you re-implement it exactly on your frontend. Consider this case:

Resolving not-mailinator.whatever.com returns:

    not-mailinator.whatever.com. 86400 IN MX 10 a.bad-mailserver.com
    not-mailinator.whatever.com. 86400 IN MX 10 b.bad-mailserver.com
    not-mailinator.whatever.com. 86400 IN MX 10 c.bad-mailserver.com
    not-mailinator.whatever.com. 86400 IN MX 10 d.bad-mailserver.com
    not-mailinator.whatever.com. 86400 IN MX 10 e.bad-mailserver.com
    not-mailinator.whatever.com. 86400 IN MX 10 f.bad-mailserver.com
    not-mailinator.whatever.com. 86400 IN MX 10 g.bad-mailserver.com
    not-mailinator.whatever.com. 86400 IN MX 10 h.bad-mailserver.com
    not-mailinator.whatever.com. 86400 IN MX 10 mailinator.com
If you choose one at random, your frontend has a 90% chance of choosing a mail server that isn't mailinator. But when your MTA tries to send the message, it will notice that bad-mailserver.com is offline and try the other MXes, eventually hitting mailinator and delivering the message you tried to block.

You could put a limit on the number of MX records a domain can have, but Gmail has 5 and so you'd only reduce the chance of success to 80%.

Then you have to consider the mechanics of DNS. How many layers of CNAME indirection will you follow? Will you cache results? (If so, how will you trust that the responses are valid?) How long will you wait for DNS responses?

A poor implementation of DNS lookups will use unbounded time, unbounded bandwidth, and unbounded file descriptors. This isn't a hack you are going to code up in an afternoon, and one mistake means your website is going to randomly go down.

And so you have to ask: why? Why do you care if someone uses mailinator? Spammers are just going to set up their own domain or use someone's malware'd Windows box. And someone that wants to ignore your email is just going to have a procmail rule auto-submit your messages to Spamcop anyway.

So you gain nothing, spend a lot of time programming, and it won't solve any problems. In conclusion: worst idea ever.

Re: Receiveee.com - disposable email address

#89
post #79

For anyone wanting to stop signups from disposable email addresses I've found this service to be really good: http://www.block-disposable-email.com has a massive database and a bounty for new additions! We have 2 factor verification for http://8centsms.com/ but with the advent of disposable inbound SMS numbers via Twilio as well as disposable email addresses we were getting a bunch of people signing up and getting th…

DEA users are most likely long time internet users who care about their privacy and have learned to protect their email. At the same time, they have enough interest to register and try your stuff - so let them be... If the site requires users to enter an email address for freebies, savvy users will eventually find a way around it, as you suggested. You might also be blocking the early adopters. Eg. bloggers who want to review your stuff, etc!

Re: Receiveee.com - disposable email address

#90
Is this service really safe? It shows me a page with URL like https://receiveee.com/123456WC, and an email address of 123456XM@mailseal.de, so only the last two letters are different. Now once my email is sent and the address made public, isn't it very easy for someone to find out the page?
Post reply on HN