Wireshark-bugs: Re: [Wireshark-bugs] [Wireshark-dev] Wireshark-bugs mailing list archive shuttin

From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 28 Dec 2016 17:39:06 -0800
It looks like they archive via a mail subscription (the correct way) as
opposed to scraping our site (the bad and incorrect way) so they should
be unaffected.

On 12/28/16 12:50 AM, Alexis La Goutte wrote:
> Hi Gerald,
> 
> I will be also impact mail-archive ? (
> http://www.mail-archive.com/wireshark-bugs@xxxxxxxxxxxxx/info.html )
> because i looking direclty on web interface (and not subscribe to the
> mailing...)
> 
> Cheers
> 
> On Tue, Dec 27, 2016 at 8:50 PM, Gerald Combs <gerald@xxxxxxxxxxxxx
> <mailto:gerald@xxxxxxxxxxxxx>> wrote:
> 
>     Traditionally, Bugzilla hasn't had very strong antispam measures.
>     This has become a major issue for some public installations. For
>     example, the Eclipse project now requires explicit permission for
>     new users to open bugs:
> 
>     https://bugzilla.mozilla.org/show_bug.cgi?id=1306750
>     <https://bugzilla.mozilla.org/show_bug.cgi?id=1306750>
> 
>     We've been getting spam on bugs.wireshark.org
>     <http://bugs.wireshark.org> but fortunately for us the volume is
>     still low and it's easy enough to just set the "private" flag on the
>     offending bugs. However, we have a separate self-inflicted issue. We
>     log bug activity via the wireshark-bugs mailing list and those
>     messages are archived, which effectively means we provide cheap and
>     easy spam hosting at a popular web address. Cleaning up these
>     messages is an inconvenient and manual process.
> 
>     As a result I'm disabling the archive feature on the wireshark-bugs
>     mailing list this upcoming Saturday, December 31. The mailing list
>     itself will still be up and running and old archived messages will
>     still be available, but new messages will not be archived after that
>     date.
>     ___________________________________________________________________________
>     Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx
>     <mailto:wireshark-dev@xxxxxxxxxxxxx>>
>     Archives:    https://www.wireshark.org/lists/wireshark-dev
>     <https://www.wireshark.org/lists/wireshark-dev>
>     Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>     <https://www.wireshark.org/mailman/options/wireshark-dev>
>                  mailto:wireshark-dev-request@xxxxxxxxxxxxx
>     <mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe
> 
> 
> 
> 
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>