From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: failure using starttls with Oort gnus/imap
Date: Sat, 22 Mar 2003 15:31:35 +0100 [thread overview]
Message-ID: <m3he9va2wo.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <i7wuitlxum.fsf@hilbert.math.albany.edu>
William F Hammond <hammond@csc.albany.edu> writes:
> After moving to GNU Emacs 21.3. and using the overnight tarball
> dated 20030320, I get a somewhat different debug message, which matches
> byte-for-byte the debug message from ognus-0.16:
The problem seems to be more fundamental. `imap-open' may kill the
buffer it's been fed, for some reason or other, which makes
`mail-source-fetch-imap' very unhappy, since it created the buffer.
Perhaps Simon knows what the right fix for this should be? (I think
it's probably a mistake for `imap-open' to kill the buffer...)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2003-03-22 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <i74r6cl1w0.fsf@hilbert.math.albany.edu>
2003-03-17 13:55 ` Lars Magne Ingebrigtsen
[not found] ` <i7wuitlxum.fsf@hilbert.math.albany.edu>
2003-03-22 14:31 ` Lars Magne Ingebrigtsen [this message]
2003-03-22 17:25 ` Simon Josefsson
2003-03-23 13:56 ` William F Hammond
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=m3he9va2wo.fsf@quimbies.gnus.org \
--to=larsi@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).