Email addresses of submitters are made public on Nabble.com

Asked by Carsten Schlipf

Hi all,

I submitted this bug: https://bugs.launchpad.net/hardy-backports/+bug/265065. As expected launchpad hides my Email address. However after I suddenly got more and more Spam to a careful used email address, I googled and found that my email address has been made public through this bug report on Nabble.com: http://www.nabble.com/-Bug-265065---NEW--Subversion-1.5.1-does-not-work-with-SSL-certificates-td19331874.html. Obviously only the email address of the submitter is affected.

This is very annoying. If it was my fault, please tell me, how I could have avoided that. If it's a bug in launchpad, I will certainly no longer post any bug reports as long as nabble makes my email address public.

Best regards,
Carsten

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Tormod Volden (tormodvolden) said :
#1

I understand your frustration. See also bug #111147. You also have to thank the genius who subscribed the ubuntu-backports mailing list (which is a public mailing list, available for instance on nabble.com) to the ubuntu-backports bug reports.

Adding a public mailing list to the package bug subscribers shouldn't be allowed. On the other hand, launchpad should try to reduce the damage in those cases this has been done by fixing the above bug.

Revision history for this message
dfalk (dfalk) said :
#2

How about here ( https://lists.ubuntu.com/archives/ubuntu-mozillateam-bugs/2008-September/052914.html ), where I've found my own email address? What's up? Launchpad should take care to keep this stuff secret! I don't even think other logged in users ought to know each other's addresses unless a person has explicitly allowed such a thing.

Can you help with this problem?

Provide an answer of your own, or ask Carsten Schlipf for more information if necessary.

To post a message you must log in.