X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 7AA193893653 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=berkeley.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=carrier AT berkeley DOT edu DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berkeley-edu.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=NPKikcE/uVWy5yTuOJMDisg749cajddt6NoFyc+6A00=; b=AYkMrce+G1zn8neVExabG8Xjd+d+3fqRP1hquXu9eQVAW5a6W0SH+RPOU0i8o2TD+r BwcJCSApXY/38PRRL1J8tRHwPDnDAtmBc/LPgk/RqSdlOHnS6hgLENkpepQ1UDJ815/D Vo2I3Nw6J5b0MjnFWZtAv0+OQbGar04SJr4I4jtyCtnLC2dtIfDETHbK12W6E6ndChth fLpq/Cy0VNRrBoA9svWq7o4T7O+WyD8bRHI5z71Q2fS/WpWEid8Cn7IOhqfOpOzJtTo4 d/HGvLCJU64H0mlFG4O0eo/naV3kCy/NhwFZpxuZmklfkQCLgiXOJqFfwkpGDtfgVwXQ v29Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=NPKikcE/uVWy5yTuOJMDisg749cajddt6NoFyc+6A00=; b=IluMJyH9ErURVKBlMRLjU0qkrF9iwUAKnp+LipjqvswJhsltwDXmPGslC4UWwOraak KUhIOMLT2YscbyeGf3C0zoefA/UYOi0MKkW7dul4wmtlj1Yndvm8MCbl8JjvmpEiUC9G sgn8bxiP5BlFmIldtFflyNqIeL1NTqbrAPFd8kewMJyzmdscwlpOaQSNjF2VWKaNmkdv h8iHejKtQda0Ad8bjfuBUro67sjVjao0mnxX8MelNHlyaDPB2bfLA4eZCbsHRTmuPBJ0 AXZm1GxXyCVZY7Sxhc6N6AGMyFl0KAPmouWLqImlQwOnQR9m8eUUCdCw0P9zkMXpDHma WXyA== X-Gm-Message-State: AGi0Puag8aZYjxpBkXVEunexi2aukMnGjv/Rj1caZu4K9FBKvSLCCYJG NsF/mePT4zGn0YW413Ti6Wal47zohlU= X-Google-Smtp-Source: APiQypJCdMX7PoW6cHz5duI04ucfhVyColtP/Y2EtTzM3HXcygE1C89f1or+CV9/2uIMkNsyFAWELQ== X-Received: by 2002:a17:902:8543:: with SMTP id d3mr10377342plo.314.1587754708049; Fri, 24 Apr 2020 11:58:28 -0700 (PDT) Date: Fri, 24 Apr 2020 11:58:26 -0700 From: Stephen Carrier To: cygwin AT cygwin DOT com Subject: Re: Two naive questions Message-ID: <20200424185826.GA10854@iguana.crashland.org> References: <20200417174902 DOT GA32412 AT iguana DOT crashland DOT org> <169450016 DOT 20200417211620 AT yandex DOT ru> <20200420172017 DOT GA17660 AT iguana DOT crashland DOT org> <889844652 DOT 20200422125750 AT yandex DOT ru> <20200423164934 DOT GB32059 AT iguana DOT crashland DOT org> <20200423191312 DOT GA12831 AT cgf DOT cx> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20200423191312.GA12831@cgf.cx> User-Agent: Mutt/1.12.2 (2019-09-21) X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" On Thu, Apr 23, 2020 at 03:13:12PM -0400, Christopher Faylor wrote: > On Thu, Apr 23, 2020 at 09:49:34AM -0700, Stephen Carrier wrote: > >On Wed, Apr 22, 2020 at 12:57:50PM +0300, Andrey Repin wrote: > >>You can ask list management software to resend past messages. I don't > >>recall specifics, and given the recent change, they may be entirely > >>obsolete. You can check https://www.list.org/ for directions. > > > >As I commented upthread (Monday) I have seen instructions on how to > >recall messages. I tried them, and they did not work. I tried again > >more recently, and the instructions did not work, and I received bounce > >messages to the effect that the request was not understood. I also > >commented above that I had looked at the mailman documentation for > >which you provide a link, and did not find any method described for > >recalling messages. > > Apparently you're not reading the whole cygwin mailing list thread on this > subject: > > https://cygwin.com/pipermail/cygwin/2020-April/thread.html I have been following the whole thread, and my comments were in the context of the whole thread. The subject I was addressing was whether either the current or previous versions of the list supported retrieval of old messages. Neither the previous or current incarnations of the list do this, according to me, but what do I know? > To reiterate, cygwin.com's hosting site "sourceware.org" went through a > hardware and software change in March. If you're attempting to use > instructions from before the move to new hardware and different mailing > list software then they won't work. Yes, I had heard. I was not complaining, just reporting results of an investigation to save others the trouble of doing it for themselves. > >If you think I am mistaken, please find the information on how to do this > >and provide a specific link. Providing a link to the main documentation > >page and suggesting that others go looking is to send them on a wild-goose > >chase aka waste of time. > > > >It would be a useful feature, I agree, and if I simply failed to find > >what I was looking for, I would welcome correction. > > Information provided information here: > > https://cygwin.com/pipermail/cygwin/2020-April/244545.html > https://cygwin.com/pipermail/cygwin/2020-April/244546.html Yes, I appreciated your contribution, but that wasn't the subject under discussion, which was retrieving messages via the mail list. I was replying to someone else. > To summarize: You can click on the mailto link of any message in the > archive and it will invoke your email client with the proper In-Reply-To > set. That will allow you to reply to the sender of the message and > maintain proper threading. If you want to send to the list, replace the > "To" with the email address of the list. Yes! In this message: https://cygwin.com/pipermail/cygwin/2020-April/244568.html I said that your suggestion was a good one. Maybe you missed it? That's when I was replying to you! > I am aware that some people may find this incredibly daunting but that's > what's available given the software that we're using. Read the thread > for why we're using the mailman2 software. Yeah, I haven't been complaining or advocated that we use anything different. [ additional proposed solutions that are perfectly good, snipped. ] > If none of this meets your needs then maybe some of the other sites > that archive the cygwin list will have something more to your liking. If you don't mind, I'll continue to participate in the list, which I like very much the way it is. Have you confused me with someone else? > cgf Stephen -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple