Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: new (?) version of the old nnml problem
Date: Fri, 20 Oct 2017 08:38:56 -0700	[thread overview]
Message-ID: <8760b9kewf.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86o9p127p4.fsf@zoho.com>

Emanuel Berg <moasen@zoho.com> writes:

> I wrote:
>
>>> Something happened to my Gnus. Or the remote
>>> connection? Now when I do
>>> `gnus-group-get-new-news' Gnus hangs until
>>> I do C-g. The broken POP processes pile up
>>> at `list-processes'.
>>
>> Because NNTP works so good and fast, can't
>> I get my mails thru that as well? :)
>
> nnml seems totally messed up :(
>
> I went into the server buffer and closed it,
> but when I go back to the group buffer to get
> NNTP, same thing! And then I go back to the
> server buffer and nnml is open once again?

I think if you hit "D" for "deny" the server will stay closed.

But it's a POP mail source that's causing the problem, not the nnml
store, right? I'm not sure that denying the server would prevent Gnus
from trying to retrieve the mail source.

Maybe confirm that POP access works from the command line first?

https://unix.stackexchange.com/questions/201818/checking-pop-mail-account-using-terminal




  reply	other threads:[~2017-10-20 15:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 14:27 Emanuel Berg
2017-10-20 14:42 ` Emanuel Berg
2017-10-20 14:51   ` Emanuel Berg
2017-10-20 15:38     ` Eric Abrahamsen [this message]
2017-10-20 15:46       ` Emanuel Berg
2017-10-20 15:48       ` Emanuel Berg
2017-10-20 16:08         ` Eric Abrahamsen
2017-10-20 17:11           ` Emanuel Berg
2017-10-20 17:36             ` Eric Abrahamsen
2017-10-20 15:57       ` Emanuel Berg
2017-10-20 16:11         ` Eric Abrahamsen
2017-10-20 17:12           ` Emanuel Berg
2017-10-20 17:45             ` Eric Abrahamsen
2017-10-20 18:40               ` Emanuel Berg
2017-10-20 21:20                 ` Eric Abrahamsen
2017-10-21  8:53                   ` Emanuel Berg
2017-10-23  5:51                   ` Emanuel Berg
2017-10-23 15:32                     ` Eric Abrahamsen
2017-10-23 18:31                       ` Emanuel Berg
2017-10-23 19:17                         ` Adam Sjøgren
2017-10-25 15:36                           ` Emanuel Berg
2017-10-25 19:02                             ` Eric Abrahamsen
2017-10-25 19:41                               ` Emanuel Berg
2017-10-25 21:22                                 ` Eric Abrahamsen
2017-10-26 17:17                                   ` Emanuel Berg
2017-10-26 22:55                                     ` Eric Abrahamsen
2017-11-06 15:49                                     ` Ted Zlatanov
2017-11-06 16:11                                     ` Robert Pluim
2017-11-06 16:20                                       ` Adam Sjøgren
2017-11-06 16:32                                         ` Robert Pluim
2017-11-07 23:53                                         ` Emanuel Berg
2017-11-08  0:28                                           ` Emanuel Berg
2017-10-23 22:33                         ` Eric Abrahamsen
2017-10-24 18:45                           ` Emanuel Berg
2017-10-20 15:44     ` Emanuel Berg

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=8760b9kewf.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.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 NNTP newsgroup(s).