From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Denys Duchier <denys.duchier@univ-orleans.fr>
Cc: ding@gnus.org
Subject: Re: patch for "POP SSL connexion failed"
Date: Wed, 14 Nov 2007 21:07:02 +0900 [thread overview]
Message-ID: <b4msl39av4p.fsf@jpl.org> (raw)
In-Reply-To: <m37iklrz6b.fsf@cam.ac.uk>
>>>>> Leo wrote:
> On 2007-11-13 20:40 +0000, Denys Duchier wrote:
>> I don't know if it was a change in gnus (I did not update in a very long
>> time) or a change in my POP server, but I have been getting something
>> like over 10 failed connexions for every 1 success ever since I cvs
>> up'ed. Here is a fix that seems to work well for me:
> I have been complaining¹ about this bug for a long long time. Thanks for
> the patch.
The patch looks harmless also for people who have no problem with
pop3. Do you have signed a paper for FSF? Otherwise, since it
seems to be able to regard as a tiny change, do you wish to go
that way? Please write a ChangeLog entry by yourself, anyway.
Regards,
next prev parent reply other threads:[~2007-11-14 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 20:40 Denys Duchier
2007-11-14 8:47 ` Leo
2007-11-14 12:07 ` Katsumi Yamaoka [this message]
2007-11-14 15:28 ` Leo
2007-11-14 21:15 ` Denys Duchier
2007-11-14 22:16 ` Katsumi Yamaoka
2007-11-16 20:07 ` rahed
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=b4msl39av4p.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=denys.duchier@univ-orleans.fr \
--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).