unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Bastos <dbastos@ic.ufrj.br>
Cc: jb@jeremybryant.net, 71893@debbugs.gnu.org
Subject: bug#71893: 27.1; Gnus pop3 download progress goes over 100%
Date: Sat, 28 Sep 2024 18:55:35 +0300	[thread overview]
Message-ID: <86jzev6adk.fsf@gnu.org> (raw)
In-Reply-To: <87plonvkxx.fsf@ic.ufrj.br> (message from Daniel Bastos on Sat, 28 Sep 2024 12:48:10 -0300)

> From: Daniel Bastos <dbastos@ic.ufrj.br>
> Cc: Daniel Bastos <dbastos@ic.ufrj.br>,  jb@jeremybryant.net,
>   71893@debbugs.gnu.org
> Date: Sat, 28 Sep 2024 12:48:10 -0300
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Eventually, if the problem is with the server, what do we want to do
> > with this bug report? what _can_ we do?
> 
> Right now I can't see what can we do.  By the way, this is not a bug
> report: Gnus doesn't appear to be at fault.  This is a request for help:
> I'm puzzled.  While the evidence is against the POP3 server, it's hard
> to think that a POP3 server would be shipped with such an obvious bug.

Maybe we have POP3 experts around that could chime on?





      reply	other threads:[~2024-09-28 15:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 22:27 bug#71893: 27.1; Gnus pop3 download progress goes over 100% Daniel Bastos
2024-07-02 22:50 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-20 10:07   ` Eli Zaretskii
2024-08-04  7:54     ` Eli Zaretskii
2024-08-12 12:54       ` Daniel Bastos
2024-08-31  7:53         ` Eli Zaretskii
2024-09-09 23:29           ` Daniel Bastos
2024-09-19 19:13             ` Daniel Bastos
2024-09-28  9:19               ` Eli Zaretskii
2024-09-28 15:48                 ` Daniel Bastos
2024-09-28 15:55                   ` Eli Zaretskii [this message]

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=86jzev6adk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71893@debbugs.gnu.org \
    --cc=dbastos@ic.ufrj.br \
    --cc=jb@jeremybryant.net \
    /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 public inbox

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

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).