unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Dmitry Alexandrov <321942@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Reply to list [was: Different key maps in different dired buffers]
Date: Wed, 08 Jun 2016 14:43:39 +0300	[thread overview]
Message-ID: <87inxjkis4.fsf@quux> (raw)
In-Reply-To: <20160605205812056555404@bob.proulx.com> (Bob Proulx's message of "Sun, 5 Jun 2016 21:29:26 -0600")

Bob Proulx <bob@proulx.com> writes:

> Dmitry Alexandrov wrote:
>> >> ... seems to implicate the Stanford newsgroup gateway.
>> >
>> > I’ll try to post this message to ‘gnu.emacs.help‘ via a proper news
>> > server (news.gnus.org) and not with Gnus, let see what will happen.
>>
>> That is it!  References are broken.
>
> I think it is confirmed.
>
>> So what we could do with it, besides avoiding posting here via
>> ‘gnu.emacs.help’?
>
> That is the problem.  It is available.  People will use it.  We can't
> stop people from posting to the news group.

Well, being a listmaster, actually, you could, I guess.  I am not
familiar with GNU Mailman, but there must be sophisticated filtering
features.  But that would be too radical solution, of course.

Instead, I imagined, sending to anyone who posts via Usenet an
auto-reply mail that explains the problem and advises switching to Gmane
might be feasible as a temporary measure.

I’ve started to dig through GNU Mailman’s documentation (which seems to
be not ready yet) to find something about auto-responder and ran across
a note that Mailman has NNTP support on its own.

Then I’ve searched the Web a bit and found a page [0] which hints, that
usenet.stanford.org was blamed unfairly — it is a mere Usenet server,
while mail-to-news gating is done here, on gnu.org.

[0] https://www.gnu.org/usenet/usenet.html

Is that page still actual?

>> It would be logical to report this issue to the gateway maintainers (or
>> how else should be they called?) at Stanford, I have no idea though,
>> where to report to them to.
>
> Now that we have determined it to be the problem I guess we should
> contact them and see if they can address the problem somehow.  I don't
> know who maintains the gateway.  I have never had any interaction with
> them.
>
>> Or is it <listmaster@gnu.org>’s (is there any?) business to deal with
>> broken gateways?
>
> Well... I think that is me!

Nice to meet you, by the way.  :-)

> AFAIK the listmaster address is now untended.  AFAIK it was replaced
> with mailman@gnu.org for use with Mailman.  AFAIK (a lot of softening
> here) that happened around 2003 according to notes left behind in
> files so it has been a while.  Regardless of the actual history it
> predates my involvement by many years.  Which is why I have AFAIK so
> many times.
>
> These days the mailing list admins on the non-FSF side of things are
> myself and Karl.  Karl and I handle almost all of the mailing list day
> to day activity.  That includes all of the anti-spam and helping
> people with subscription and with large file problems and so forth.
> The FSF admins maintain the Mailman installation and Mailman upgrades.
> But they don't get involved in the day to day maintenance.
>
> And so you could write to mailman@gnu.org but that would just fall
> through to me or Karl at some point. :-) You could write to
> help-gnu-emacs-owner@gnu.org and that would reach the owners of this
> mailing list.  Which includes several other people in addition to
> myself and the -owner address is always a good thing to do when
> dealing with a specific mailing list.  Anyone of the group there could
> help.

Thank you for the details.

> Meanwhile, while investigating the listmaster address, I ran across
> another related untended mailbox that is 1.2G in size holding 71345
> messages piling up from 2006 that all appear to be spam.  Oh joy.
> Not! :-)
>
> In any case, I will try to chase down who is the maintainer of the
> Stanford news to mail gateway and contact them about the problem.  It
> has been this way for years.  It will probably take a while to get
> fixed.



  reply	other threads:[~2016-06-08 11:43 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26  8:14 Different key maps in different dired buffers Whitfield Diffie
2016-05-26  9:06 ` tomas
2016-05-26 12:25   ` Stefan Monnier
2016-05-26 12:37     ` tomas
2016-05-26 14:03 ` Drew Adams
2016-05-26 15:05   ` Whitfield Diffie
2016-05-26 15:24     ` Drew Adams
2016-05-26 17:46     ` Dmitry Alexandrov
2016-05-26 17:59       ` Whitfield Diffie
2016-05-26 18:05         ` Drew Adams
2016-05-27  7:09           ` Reply to list [was: Different key maps in different dired buffers] tomas
2016-05-27  8:02             ` Eli Zaretskii
2016-05-27 16:46               ` Glenn Morris
2016-05-27 18:44                 ` Eli Zaretskii
2016-06-03 23:38                   ` Bob Proulx
     [not found]                   ` <mailman.787.1464997128.1216.help-gnu-emacs@gnu.org>
2016-06-04  1:40                     ` Emanuel Berg
2016-06-04  2:12                       ` Bob Proulx
     [not found]                       ` <mailman.789.1465006376.1216.help-gnu-emacs@gnu.org>
2016-06-04  2:51                         ` Emanuel Berg
2016-06-04 15:52                           ` Dmitry Alexandrov
2016-06-04 19:41                             ` Bob Proulx
2016-06-04 19:48                               ` Emanuel Berg
2016-06-06  2:57                                 ` Bob Proulx
     [not found]                                 ` <mailman.953.1465181882.1216.help-gnu-emacs@gnu.org>
2016-06-06  3:11                                   ` Emanuel Berg
2016-06-04 20:05                               ` Stefan Monnier
2016-06-05 10:28                                 ` Dmitry Alexandrov
     [not found]                             ` <mailman.857.1465069271.1216.help-gnu-emacs@gnu.org>
2016-06-05 12:44                               ` Dmitry Alexandrov
2016-06-05 13:35                                 ` Dmitry Alexandrov
2016-06-06  3:29                                   ` Bob Proulx
2016-06-08 11:43                                     ` Dmitry Alexandrov [this message]
2016-06-09 23:35                                       ` Emanuel Berg
2016-06-16  0:45                                       ` Bob Proulx
     [not found]                                       ` <mailman.1575.1466037955.1216.help-gnu-emacs@gnu.org>
2016-06-16  5:24                                         ` Emanuel Berg
     [not found]                                   ` <mailman.955.1465183780.1216.help-gnu-emacs@gnu.org>
2016-06-06  6:20                                     ` Emanuel Berg
2016-06-06 22:03                                       ` Bob Proulx
     [not found]                                       ` <mailman.1023.1465250629.1216.help-gnu-emacs@gnu.org>
2016-06-06 22:55                                         ` Emanuel Berg
2016-06-04 17:30                           ` Bob Proulx
     [not found]                           ` <mailman.837.1465055573.1216.help-gnu-emacs@gnu.org>
2016-06-04 18:35                             ` Emanuel Berg
2016-06-05 11:00                               ` Dmitry Alexandrov
     [not found]                               ` <mailman.895.1465124454.1216.help-gnu-emacs@gnu.org>
2016-06-05 23:29                                 ` Emanuel Berg
     [not found]                           ` <mailman.850.1465061448.1216.help-gnu-emacs@gnu.org>
2016-06-04 19:04                             ` Emanuel Berg
2016-05-27 11:42             ` Whitfield Diffie

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87inxjkis4.fsf@quux \
    --to=321942@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).