What is even worse when I check the mailing list
archives (on URL like this
there is my real e-mail address! I am making this
P1 since displaying my real e-mail instead of
email@example.com or the full name is clearly
unacceptable for me - that is spam source par
excellence! Do I have to change my e-mail address
because of this bug?
I am not sure what the $summary means here, can you clarify ?
About displaying email addresses in mailing archives - this
is not new behaviour, as you probably know ... "obfuscating"
or hiding emails has never been done on nb.org. Also I
can't see how it wouldt be possible to display your
@netbeans.org address in place of real addr, as the www
archives are just mirrors of the real lists, and you can
post to the real lists from any - and multiple - email
Dropping priority as there is nothing (newly) critical here,
though leaving as a P2 enhancement since spam is getting out
of control. Also a fix might be quick and simple.
David, Collab, what kind of address hiding/obfuscation would
you suggest ?
Accepting issue & researching issue.
I will update this issue by
1. Go to the archive for nbdev April 2003.
2. Compare how my name is displayed with the others. E.g. Jesse Glick
is displayed as "Jesse Glick", I am displayed as "firstname.lastname@example.org"
(I have provided the URL link in the previous comment). I did not mean
the individula message, I mean the page where you see all the messages.
Summary: It means there is no place on the whole site where can I
specify that my name is "David Strupl". I might have overlooked it -
can you please provide me an URL and we can close this issue.
Also this is not an old issue - I used to be displayed as David Strupl
when I was a SUN employee - some magic going on here? ;-)
No magic - this comes from your local mail client
configuration :-) The www archives really are just a mirror
of what happens on the regular email lists. The msgs
displayed there are copies of original email msgs - if I
look in my mail client at recent nbdev msgs, I see your msgs
coming from "Sender : email@example.com" - which is exactly
what the www archival script sees and displays. Presumably
you have somewhere in your mail client either configured
your "Real Name" as david@sol..., or maybe left it blank.
HTH with the name issue; leaving this issue open to address
the spam/address obfuscation query. BTW David note that
even if your full name is displayed on the "index" page of
the msg archive, the full address is displayed on an
individual mail msg, eg at
Libor's email is still visible; so changing your mail client
config will not remove the spam concern. Maybe this issue
can eventually address that.
Can you give me some details about the spam/address
obfuscation query issue?
I am just not exactly sure what you mean by
Aha. I apologize for making so much noise with this. I did not know
that the whole system does not know my identity while posting to the
news group. I thought that the www login process is somehow connected
to the news groups which is apparanently not the case. So sorry for
bringing this issue. I have decreased the priority to P3 and leaving
for you to decide whether to close the issue. Only a rhetorical
question in the end: shouldn't the whole site (www, newsgroups, cvs,
...) use one identity database? Or is there an enhancement request for
this - maybe for the new version of SourceCast?
Eric : address obfuscation = somehow hiding email addresses
on web pages from spam harvester type bots, usually by
automatically converting them into something a human can
read and understand and edit (eg jcatchpoole-remove-this-
xyzQWERAsdflkjhasdfy@netbeans.org), but a bot can not.
There are also more interesting types of obfuscation.
David : Hrm, in theory yes, but remember there is no way
for the mailing list/NNTP server to ID you via your mail
client, which is your primary means of posting to it -
except by completely fakeable "real name" or email address.
I don't see how to get around that ....
Changing issue summary to focus on email add obfuscation
as an anti-spam measure.
I opened internal pcn 17299 Request for enhancement.
I will update this issue as soon as I get a resoponse.
Should be by 5/9/03
More than 1 month after 5/9 - any news ?
The product manager has not addressed this issue yet. I do see that
other customers are interested in this.
I just reminded the product manager to take a look at this issue. I
should have his update by 6/24 now.
I haven't received an update from product management.
I have asked them again if there are any further thoughts on this
request now that we have multiple customer requests concerning this
I will update as soon as I get updated here.
Our management says that the whole issue of how we could
deal with spam filtering is being looked into at this time
and not having any insight into how or when it will be
addressed. Will update more as soon i get from them.
Thought I might add another customer comment. I consider this an
issue of great importance. I accidentally sent a message to a
Netbeans list from an account which is not spam-protected (just
forgot to modify the From: line). Apparently, there is no way to
have my message removed or altered now that it's in the archives.
To give an idea of the magnitude of this problem, I posted a (test)
address on a web site for a few months about a year ago to see what
would happen; now, about 6 months after taking it back off the web
page, I'm still receiving on the order of 100 spam messages a day
through that one address; and the only place I used that address was
on the web site. All my other sources of spam combined are a tiny
fraction of the number of messages generated from web posting (yes,
I compared them).
Pity is, my message to the Netbeans list was not sent from a test
I agree, the priority of this issue should be raised.
Please also note that I started to have this spam problem since I
submitted my adress to the Gmane.org mail-to-news web site, which
forces you to give your real e-mail address :-(
Patrick - I've just proposed on nbdiscuss that we enable the address
obfuscation scheme that Gmane has, see
This would help I hope.
The request for email obfuscation in the mailing list archives has
been considered for Danube Release of Sourcecast
Support will continue monitoring the RFE & will review in the
*** Issue 48106 has been marked as a duplicate of this issue. ***
We are now on Danube, but this seems to be still not done. Status ?
To Crm,This issue has been considered to be fixed in the future release of CEE.Hence marking it as resolved later for
support to track it.
Re-opening the issue for validating the issue for implementation in a future release.
This issue has been fixed in CEE 5.2.
We recently moved out from Collabnet's infrastructure
This is still a valid request.
Any update on this? There are several people complaining about it every week. Thanks!
Since Lea doesn't work for Oracle or on Kenai anymore, we might want to reassign this to an actual person that can and might do something to resolve the problem...
I do not know who that person would be... If I did, these issues would be assigned to them when I committed this comment.