all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bob Proulx <bob@proulx.com>
To: Angel de Vicente <angelv@iac.es>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs interface to Recoll other than Helm?
Date: Tue, 7 Nov 2017 13:19:26 -0700	[thread overview]
Message-ID: <20171107130630498581412@bob.proulx.com> (raw)
In-Reply-To: <877ev2yq05.fsf@iac.es>

Angel de Vicente wrote:
> Sorry for the double post. I thought the post with the attached images
> had been rejected so I post it again with the images as links to
> some URL in the Internet. The rest of the message is basically
> the same.

Thank you for the second message with the links.  For many people
(me!) it is much easier to deal with that than inline images.

As to the original large message with the inline images...  Not to
cause stress but to communicate the problems.  Those large messages
are always very painful for the lists.gnu.org mailing list server to
process when sending to a large mailing list.  This is a small list as
there are only 1410 subscribed members.  (And that does not count the
people reading from the associated newsgroup through the mail2news
gateway.)  Other lists are truly huge with many more members.  When
sending inline images to a large mailing list the total bandwidth is a
huge multiplier.  Often things are very delayed due to those messages.
An 800K message expands to 1.1T of consumed bandwidth to the entire
list for just that one single message.  Often the mailing list server
will be running far behind trying to push bandwidth through the
network.  Which means we have been forced to start capping the size of
messages on many mailing lists.  Also for anyone using their mobile
cell data plan those large messages eat up the data limit to the data
cap very quickly.

Large messages will either be automatically rejected or manually
rejected or manually approved.  One of the list moderators must have
decided to send that one on to the list.  If I had been at the
keyboard reviewing that held message I would have rejected it.  You
would have gotten a rejection notice with an explanation and hints as
to what could be done.  Because of the human factor the actions taken
are not always exactly the same.

Just giving a view into the behind the scenes operations... :-)

Bob



  reply	other threads:[~2017-11-07 20:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07 15:30 Emacs interface to Recoll other than Helm? Angel de Vicente
2017-11-07 15:37 ` Kaushal Modi
2017-11-07 16:17   ` Angel de Vicente
2017-11-07 17:09     ` Angel de Vicente
2017-11-07 20:19       ` Bob Proulx [this message]
2017-11-07 21:17         ` Angel de Vicente
2017-11-07 16:43   ` Angel de Vicente
2017-11-08 12:40     ` Angel de Vicente
2017-11-07 15:51 ` Joost Kremers

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=20171107130630498581412@bob.proulx.com \
    --to=bob@proulx.com \
    --cc=angelv@iac.es \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.