From owner-freebsd-questions@freebsd.org Mon Oct 1 08:00:13 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2970E10983BC for ; Mon, 1 Oct 2018 08:00:13 +0000 (UTC) (envelope-from vas@admin.sibptus.ru) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc:5400:1ff:feaf:6afb]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C01B49362A for ; Mon, 1 Oct 2018 08:00:12 +0000 (UTC) (envelope-from vas@admin.sibptus.ru) Received: from vas by admin.sibptus.ru with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1g6t7j-0004gB-KR; Mon, 01 Oct 2018 15:00:11 +0700 Date: Mon, 1 Oct 2018 15:00:11 +0700 From: Victor Sudakov To: Yuri Pankov Cc: freebsd-questions@freebsd.org Subject: Re: Is FreeBSD's mailman broken? Message-ID: <20181001080011.GB17898@admin.sibptus.ru> References: <20181001055924.GA17074@admin.sibptus.ru> <57ee846f-db1e-20d1-7de0-d2828971c358@yuripv.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57ee846f-db1e-20d1-7de0-d2828971c358@yuripv.net> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: Victor Sudakov X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2018 08:00:13 -0000 Yuri Pankov wrote: > Victor Sudakov wrote: > > Dear Colleagues, > > > > https://lists.freebsd.org/mailman/subscribe/freebsd-announce seems to > > be broken. When trying to subscribe an address, I get the error message: > > > > "The hidden token didn't match. Did your IP change?" > > > > Who do I contact about this problem? > > > > My IP cannot have changed because I access the Internet via a single Squid > > proxy with a static IP. > > It did happen to me as well, the solution was to forcefully refresh the > list info window > (https://lists.freebsd.org/mailman/listinfo/freebsd-announce) in > browser, CTRL+F5. Thanks, worked for me too. It is interesting that this does not happen in all lists, just in some of them. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/