Bug #50181 | somehow I got on the MySQL spam list | ||
---|---|---|---|
Submitted: | 8 Jan 2010 11:11 | Modified: | 2 May 2012 18:56 |
Reporter: | Walter Doekes | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Websites: bugs.mysql.com | Severity: | S2 (Serious) |
Version: | N/A | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[8 Jan 2010 11:11]
Walter Doekes
[8 Jan 2010 11:45]
Giuseppe Maxia
Analyzing this report. I have created an account as you suggested. Will get back to you once I get some results.
[8 Jan 2010 12:48]
Peter Laursen
Also see: http://bugs.mysql.com/bug.php?id=49824 I also get lots of mail from MySQL I never asked for explictly. Most annoying after attending last UC I started getting mails from a handful of other vendors who had also attended the UC what were completely irrelevant to me. I was very angry that MySQL had shared my privacy with others without my permission. Some (two) of those were very difficult to get rid of actually, as they continued to send even after I unsubscribed - in one case I had to prepare a very aggressive BLOG and threaten to publish it if it did not stop.
[20 Jan 2010 21:43]
Giuseppe Maxia
After some research and experimenting, here's the result: * In your profile page, there is an option for the newsletter, which you can choose to receive or not. * The above option does not influence your receiving marketing email, which are sent to all the people who register; * You can unsubscribe from receiving further messages using the link at the bottom of the email itself; * Thus, everyone who registers, receives at least one message, and can opt out through the link at the bottom of the email. We have requested a more user friendly change of this "feature".
[22 Jan 2010 9:06]
Walter Doekes
Thank you for looking into this. As far as I'm concerned, you can close the issue. Or you could also keep it open for reference until the "feature" is fixed. Regards, Walter
[2 May 2012 19:03]
Vlad Safronov
Bug closed by user request. Privacy policy discussion will continue in Bug #49824.