public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Stefan Baur <X2Go-ML-1@baur-itcs.de>
To: cygwin@cygwin.com
Subject: Re: urgent help for tool
Date: Wed, 24 Oct 2018 14:39:00 -0000	[thread overview]
Message-ID: <7d431ad9-23c6-1ec7-e41a-0084949d8764@baur-itcs.de> (raw)
In-Reply-To: <20181023075504.GE3310@calimero.vinschen.de>


[-- Attachment #1.1: Type: text/plain, Size: 1706 bytes --]

Am 23.10.18 um 09:55 schrieb Corinna Vinschen:
>> It doesn't help for the old versions of cygwin that are being
>> reported. That's why they're getting that message—because it's an old
>> version.  They're not spamming, they're doing exactly what the message
>> told them to do. The message was unfortunate from the get-go.
> Indeed.  It seemd like a good idea at the time...
> 
>> Now that has come up yet again, I do wonder if the mailing list
>> software could somehow trap an unquoted FAST_CWD message and just
>> reply with a message that includes a link to the FAQ entry, rather
>> than send the message onto the list. Probably more trouble than it's
>> worth.
> We're just users of the sourceware infrastructure.  What we could try
> by ourselves is to create an automated reply.  The mail and the
> automated reply would still hit the mailing list, but nobody would
> have to bother to reply anymore.  This could even be a simple
> procmail filter.  I'll look into it (but will need time).

Now this may be a nasty hack, buuuut ...

if you can either get hold of the current mailing list's subscriber
list, to auto-subscribe everyone to a new list, or you are able change
the current mailinglist's address to, say, cygwin-ml@cygwin.com, you
could set up an autoresponder at cygwin@cygwin.com instead.

That autoresponder would then point people at the FAQ entry, and also
contain a message that the mailing list has moved to the new address.

Kind Regards,
Stefan Baur

-- 
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2018-10-24 14:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <126044976.64091860.1540220616710.JavaMail.zimbra@u-psud.fr>
2018-10-22 15:05 ` Samir Bouaziz
2018-10-22 15:10   ` john doe
2018-10-22 17:49     ` Marco Atzeri
2018-10-22 21:14       ` Brian Inglis
2018-10-22 22:27         ` Thomas Wolff
2018-10-22 22:37           ` Vince Rice
2018-10-23  7:57             ` Corinna Vinschen
2018-10-24 14:39               ` Stefan Baur [this message]
2018-10-24 20:50                 ` Andrey Repin
2018-10-24 21:06                   ` Hans-Bernhard Bröker
2018-10-24 21:44                     ` Vince Rice

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7d431ad9-23c6-1ec7-e41a-0084949d8764@baur-itcs.de \
    --to=x2go-ml-1@baur-itcs.de \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).