It's also nice not receiving ads in the mail every hour of every day just because I wanted to try some new YC-startup's product.
It's also nice not receiving ads in the mail every hour of every day just because I wanted to try some new YC-startup's product.
Then, keep a separate Chrome profile that's logged into the fake facebook, and your identity is safe. Probably best to lock down all privacy settings on the fake user to absolute maximum lockdown, to avoid information leaking onto Facebook's public layer that may tie you to it.
That was the strategy I used when I worked for a company that did business with Facebook games. Those things were so spammy, I would never want my actual friends to be spammed with all the viral content. To this day I keep my fake account for any and all untrusted FB-related things.
I recently wanted to create an "Admin" account for a client I was developing a web-app for as I didn't want to link my personal facebook account to my work. But with the phone number requirement the account got flagged and rejected from the system.
Frustrating!
[0] http://mailinator.blogspot.com/2008/01/your-own-private-mail...
Edit: yes, this works perfectly.
It would be nice if there was a quick-and-easy open-source version of an in-memory mail server. I'd like to run my own service, but not enough to write a robust SMTP server from scratch.
I haven't surveyed the field extensively but this has been my experience with the common recommendations. If anyone knows of a server that already exists and would make it trivial to set up basic SMTP/IMAP/POP3 with authentication let me know.
Ideally the only configuration info I would need would be something like this:
allow_imap = True
allow_pop3 = True
allow_smtp = True
accept_mail_for = ['this_domain.com', 'another_domain.com']
#users
users = ['jeff@this_domain.com', 'molly@another_domain.com']
#forwards
forwards = {'jeff@this_domain.com': 'cookiecaper@some_domain.com'}
and then, a program like mail_server_passwd would ask me for my username and let me set a password, and that would be that. It shouldn't be any difficult to bootstrap a mail server, and right now setting something that has POP3, IMAP, and SMTP up can take hours for experienced admins unless they know the mail server(s) very well ahead of time.
[Warnings: OpenSMTPD apparently hasn't eaten anyone's mail yet, but it's hardly done. By design, it doesn't include as many options as other mail servers, some of which may be useful. I don't think OpenSMTPD been ported to non-OpenBSD yet. calomel.org tends to be out of date, inaccurate or dangerously incomplete.]
Also, some SMTP servers are probably pretty easy to modify. I use qpsmtpd[1], which is probably quite easy to modify. Then, all you need is a IMPAD that can read from memory..
I would like to have my mail in something like Redis. It would give easy access from different languages etc..
A lot of certification authorities will allow you to get a certificate for example.com if you can prove that you can reply to an email sent to an email address @example.com. If you configure an MX record pointing to the mailinator MTAs, then anybody can request a cert and ask to validate domain ownership by contacting whatever@example.com, and can subsequently browse the whatever@ mailbox on mailinator to read and reply to the confirmation email.
A security researcher once obtained a certificate for Microsoft's live.com domain by registering an email account sslcertificates@live.com and using it to reply to the CA's verification email.
http://www.theregister.co.uk/2011/04/11/state_of_ssl_analysi...