From: Simon Josefsson <jas@extundo.com>
Cc: <ding@gnus.org>, <bugs@gnus.org>
Subject: Re: [patch] imap.el imap-gssapi-open fix
Date: Thu, 15 Feb 2001 10:22:40 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.30.0102151016490.4037-100000@slipsten.extundo.com> (raw)
In-Reply-To: <dzcwvas25cw.fsf@pandora.inf.elte.hu>
On 15 Feb 2001, NAGY Andras wrote:
> Solution: in imap-gssapi-open, set imap-calculate-literal-size-first
> to the correct value, besides imap-client-eol, as seen in
> imap-kerberos4-open.
Thanks! Commited.
> Other possible occurrence: imap-shell-open also sets imap-client-eol
> but not imap-calculate-literal-size-first. As I'm unable to test
> this, not included in the patch.
In shell streams, \r's are usually not altered by the transport (imtest
do that). But it really depends on how the "shell" stream work --
if you run imtest in a shell-stream, you need to set i-c-l-s-f. I think
it should not be used when the shell stream is something like "ssh
mailserver imapd". I'm not sure there's a perfect default behaviour.
prev parent reply other threads:[~2001-02-15 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 23:48 NAGY Andras
2001-02-15 9:22 ` Simon Josefsson [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.30.0102151016490.4037-100000@slipsten.extundo.com \
--to=jas@extundo.com \
--cc=bugs@gnus.org \
--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).