From: Stefan Waldherr <swa@cs.cmu.edu>
Subject: Re: gnus chokes on this junk mail
Date: 10 Jan 1998 17:05:45 -0500 [thread overview]
Message-ID: <upkoh1khtmu.fsf@mind.learning.cs.cmu.edu> (raw)
In-Reply-To: <tx1pvm0dn59.fsf@cygnus.com>
>>>>> "Ken" == Ken Raeburn <raeburn@cygnus.com> writes:
Ken> Does emacs crash or does gnus simply report some error?
Nope, gnus simply stops.
Ken> size of the buffer-portion it's trying to match against -- such as the
Ken> entire "to:" field. Try cutting down the "to:" field significantly and
Ken> see if gnus can handle it then.
You were right. I removed a bunch of lines from the `To' field and gnus could
read the mail. Nevertheless I consider it a bug. In fact a nasty one.
S.
--
Stefan Waldherr office +1 (412) 268-3837
fax +1 (412) 268-5576
e-Mail swa@cs.cmu.edu
www http://www.waldherr.org/
next prev parent reply other threads:[~1998-01-10 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-08 11:07 Stefan Waldherr
1998-01-10 21:39 ` Ken Raeburn
1998-01-10 22:05 ` Stefan Waldherr [this message]
1998-01-12 22:34 ` Lars Magne Ingebrigtsen
1998-01-12 22:44 ` Russ Allbery
1998-01-13 21:11 ` Ken Raeburn
1998-02-02 18:24 ` Lars Magne Ingebrigtsen
1998-01-12 22:47 ` Stefan Waldherr
1998-01-12 22:51 ` Hrvoje Niksic
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=upkoh1khtmu.fsf@mind.learning.cs.cmu.edu \
--to=swa@cs.cmu.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).