> If one were designing a way to harvest emails, this is how it would be done. a) Given that we're contacting your email provider, and it surely has not only your email address, but your mail contents, you must be mis-trusting your ISPs? You understand that email addresses are typically public information, and your ISP has much more private information on you (including which websites you visit, even if not the contents), right? And here, the ISP sees only the email address, not the contents. I don't see the "security" problem. b) If we do not send the email address by HTTP, then this is solved. What Magnus proposed in comment 3, I think that's a possible approach. However, this might break existing setups. We need some more data on that. But it could be feasible. alta88, I would appreciate you stopping personal attacks ("code is so poor", although this has good reasons to be done like that), and threats ("if it isn't fixed, and soon, I will..."). They are not helpful for a decision based on reason.
Bug 1594372 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> If one were designing a way to harvest emails, this is how it would be done. First off, please distinguish between "emails" (contents) and "email addresses" (what you tell others to contact you). These are completely different things. a) Given that we're contacting your email provider, and it surely has not only your email address, but your mail contents, you must be mis-trusting your ISPs? You understand that email addresses are typically public information, and your ISP has much more private information on you (including which websites you visit, even if not the contents), right? And here, the ISP sees only the email address, not the contents. I don't see the "security" problem. b) If we do not send the email address by HTTP, then this is solved. What Magnus proposed in comment 3, I think that's a possible approach. However, this might break existing setups. We need some more data on that. But it could be feasible. alta88, I would appreciate you stopping personal attacks ("code is so poor", although this has good reasons to be done like that), and threats ("if it isn't fixed, and soon, I will..."). They are not helpful for a decision based on reason.
> If one were designing a way to harvest emails, this is how it would be done. First off, please distinguish between "emails" (contents) and "email addresses" (what you tell others to contact you). These are completely different things. a) Given that we're contacting your email provider, and it surely has not only your email address, but your mail contents, you must be mis-trusting your ISP? You understand that email addresses are typically public information, and your ISP has much more private information on you (including which websites you visit, even if not the contents), right? And here, the ISP sees only the email address, not the contents. And this is a one-time action, when you set up the account. I don't see the "security" problem. b) If we do not send the email address by HTTP, then this is solved. What Magnus proposed in comment 3, I think that's a possible approach. However, this might break existing setups. We need some more data on that. But it could be feasible. alta88, I would appreciate you stopping personal attacks ("code is so poor", although this has good reasons to be done like that), and threats ("if it isn't fixed, and soon, I will..."). They are not helpful for a decision based on reason.
> If one were designing a way to harvest emails, this is how it would be done. First off, please distinguish between "emails" (contents) and "email addresses" (what you tell others to contact you). These are completely different things. a) Given that we're contacting your email provider, and it surely has not only your email address, but your mail contents, you must be mis-trusting your ISP? Even with your email address? If you feel like that, why don't you use a VPN, like I do? You understand that email addresses are typically public information, and your ISP has much more private information on you (including which websites you visit, even if not the contents), right? And here, the ISP sees only the email address, not the contents. And this is a one-time action, when you set up the account. I don't see the "security" problem. b) If we do not send the email address by HTTP, then this is solved. What Magnus proposed in comment 3, I think that's a possible approach. However, this might break existing setups. We need some more data on that. But it could be feasible. alta88, I would appreciate you stopping personal attacks ("code is so poor", although this has good reasons to be done like that), and threats ("if it isn't fixed, and soon, I will..."). They are not helpful for a decision based on reason.
> If one were designing a way to harvest emails, this is how it would be done. First off, please distinguish between "emails" (contents) and "email addresses" (what you tell others to contact you). These are completely different things. a) Given that we're contacting your email provider, and it surely has not only your email address, but your mail contents, you must be mis-trusting your ISP? Even with your email address? If you feel like that, why don't you use a VPN? You understand that email addresses are typically public information, and your ISP has much more private information on you (including which websites you visit, even if not the contents), right? And here, the ISP sees only the email address, not the contents. And this is a one-time action, when you set up the account. I don't see the "security" problem. b) If we do not send the email address by HTTP, then this is solved. What Magnus proposed in comment 3, I think that's a possible approach. However, this might break existing setups. We need some more data on that. But it could be feasible. alta88, I would appreciate you stopping personal attacks ("code is so poor", although this has good reasons to be done like that), and threats ("if it isn't fixed, and soon, I will..."). They are not helpful for a decision based on reason.
> If one were designing a way to harvest emails, this is how it would be done. First off, please distinguish between "emails" (contents) and "email addresses" (what you tell others to contact you). These are completely different things. a) Given that we're contacting your email provider, and it surely has not only your email address, but your mail contents, you must be mis-trusting your ISP? Even with your email address? If you have this little trust in your ISP, why don't you use a VPN? You understand that email addresses are typically public information, and your ISP has much more private information on you (including which websites you visit, even if not the contents), right? And here, the ISP sees only the email address, not the contents. And this is a one-time action, when you set up the account. I don't see the "security" problem. b) If we do not send the email address by HTTP, then this is solved. What Magnus proposed in comment 3, I think that's a possible approach. However, this might break existing setups. We need some more data on that. But it could be feasible. alta88, I would appreciate you stopping personal attacks ("code is so poor", although this has good reasons to be done like that), and threats ("if it isn't fixed, and soon, I will..."). They are not helpful for a decision based on reason.