3 ms·
interesting idea. a few issues come to mind: - people concerned enough about privacy to use such a service might have concerns about their emails being passed
by there 17y ago
interesting idea. a few issues come to mind:
- people concerned enough about privacy to use such a service might have concerns about their emails being passed through your service as well.
- the domains of that service might get blocked on certain sites due to abuse and people using multiple email addresses to create multiple accounts.
- spam filters might block the inbound emails because the 'to' address doesn't match up to the user's. though i can't imagine many would place a high probability on this metric since mailing lists and such would act the same way.
- newman314 17y agoWell, given that this would be a hosted service, the revenue model would be the redirect service and not name scraping. I have no interest in scraping names and think that that is completely unethical behavior. However, to further address your concerns, email addresses could be stored in such a way that the provider does not match or log any email transactions and acts strictly as a forward only model. Domains getting blocked is a fact of life and is something that will have to be managed. However, I hear you on potential abuse and part of the service would have to be ways to address that. I'm no fan of spammers and my primary interest in this is to manage the rapidly increasing insight that companies such as GOOG and MSFT have into their users by way of providing "free" services. Google Buzz and Latitude honestly creep the heck out of me. Wrt to spam filters, you can easily add the "to" addresses inside gmail as approved addresses so that should not be too much of an issue.