From: Russ Allbery <rra@stanford.edu>
Subject: Odd followup problem (XEmacs 21.1.12, Gnus 5.8.7)
Date: 20 Sep 2000 21:45:11 -0700 [thread overview]
Message-ID: <ylaed24alk.fsf@windlord.stanford.edu> (raw)
I just upgraded to XEmacs 21.1.12 and Gnus 5.8.7 (from XEmacs 21.1.7 and
Gnus 5.8.2), and also went from a non-MULE XEmacs to a MULE XEmacs if it
makes any difference. I'm now getting an odd occasional problem when I
follow up to news articles. I get the error:
Mail header "220 81296 ..." doesn't conform to RFC 822. skipping...
and a beep before getting the message editing buffer, and if I check the
" *Original Article*" buffer, the headers of the article have what looks
like the server return from the ARTICLE command on the first line (the 220
response code, the article number, and the message ID).
It only seems to do this for the first few times and then stops, until I
restart XEmacs. Everything seems to work fine, so it's just an annoyance
rather than a serious problem.
Does this ring a bell with anyone?
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next reply other threads:[~2000-09-21 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-21 4:45 Russ Allbery [this message]
2000-09-21 7:21 ` Kai Großjohann
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=ylaed24alk.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).