This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 198388 - Blacklist option does not work
Summary: Blacklist option does not work
Status: RESOLVED WONTFIX
Alias: None
Product: www
Classification: Unclassified
Component: Admin (show other bugs)
Version: 7.0
Hardware: PC Linux
: P2 normal (vote)
Assignee: Marco Walther
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-06 13:47 UTC by Jesse Glick
Modified: 2017-10-03 17:28 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2011-05-06 13:47:50 UTC
Due to the well-known crappiness of the Oracle autoresponders, which send spam to public lists, for the lists I am moderator of I not only reject autoreplies but blacklist the sender, using the fourth link offered in the moderator's notification mail. (Who knows how long it will be before the sender gets back to work, and in some cases they have never even posted a real message anyway.) But messages keep coming in to the moderator from the same sender even though they were supposedly blacklisted.
Comment 1 Jan Pirek 2011-05-10 08:26:35 UTC
I can confirm that blacklisting does not work.

In list mobility_feedback@usersguide.netbeans.org we recently blacklisted user spamming the list, but it does not have any effect.

I am raising priority. This is real issue. We do not have moderator's manpower for setting any more lists as moderated.
Comment 2 Marco Walther 2011-11-14 23:50:49 UTC
Should work better now.
Comment 3 Jiri Kovalsky 2017-10-03 07:32:46 UTC
Still does not work. See papa@arbolone.ca's successful post [1] despite that address being blacklisted [2] a week earlier.

[1] https://netbeans.org/projects/www/lists/nbusers/archive/2017-10/message/17
[2] https://netbeans.org/projects/www/lists/nbusers/blacklist
Comment 4 Marco Walther 2017-10-03 17:28:14 UTC
That user is actually subscribed to the list in question. And the current setup is to query the blacklist only after the subscriber-check.

Works as specified.