From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: failed decryption on gwene group?
Date: Tue, 06 Aug 2013 11:35:57 +0800 [thread overview]
Message-ID: <87zjsvwkwy.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <878v0fy0o6.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> asjo@koldfront.dk (Adam Sjøgren) writes:
>>
>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>>
>>>> There's about a ten-second wait between the "200" success message and
>>>> the closing of the connection.
>>>
>>> That is probably just an inactivity time out. "Oh, you are the silent
>>> type? Ok, I can't help you - bye bye."
>>>
>>> Try typing something, say "GROUP gmane.discuss".
>>
>> Okay, thanks. I tried typing the names of two groups that currently
>> won't open for me in gnus:
>>
>> GROUP gwene.com.ycombinator.news
>> 211 108741 1 108741 gwene.com.ycombinator.news
>> GROUP gmane.emacs.help
>> 211 91040 1 92753 gmane.emacs.help
>>
>> That looks like success to me! What now?
>
> I tried an ARTICLE command, and that worked as well. I asked for article
> number 33, as I was seeing this in *Messages*: gnutls.c: [1] Discarded
> message[33] due to invalid decryption.
Never mind, all the misbehaving groups show the same "message[33]" error.
next prev parent reply other threads:[~2013-08-06 3:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 13:02 Eric Abrahamsen
2013-08-03 13:11 ` Lars Magne Ingebrigtsen
2013-08-03 14:58 ` Ted Zlatanov
2013-08-04 2:18 ` Eric Abrahamsen
2013-08-04 11:36 ` Ted Zlatanov
2013-08-04 15:02 ` Eric Abrahamsen
2013-08-05 2:19 ` Lars Magne Ingebrigtsen
2013-08-05 2:54 ` Eric Abrahamsen
2013-08-05 7:41 ` Julien Danjou
2013-08-05 8:36 ` Eric Abrahamsen
2013-08-05 13:11 ` Adam Sjøgren
2013-08-06 2:51 ` Eric Abrahamsen
2013-08-06 3:10 ` Eric Abrahamsen
2013-08-06 3:35 ` Eric Abrahamsen [this message]
2013-08-08 6:25 ` Eric Abrahamsen
2013-08-03 13:51 ` Wolfgang Jenkner
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=87zjsvwkwy.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).