From: Russ Allbery <rra@stanford.edu>
Subject: Re: gnus chokes on this junk mail
Date: 12 Jan 1998 14:44:36 -0800 [thread overview]
Message-ID: <m3en2dia7f.fsf@windlord.Stanford.EDU> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 12 Jan 1998 23:34:21 +0100
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Stefan Waldherr <swa@cs.cmu.edu> writes:
>> 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.
> Does it hang forever, or does it just take lots of time?
It just takes a lot of time (upwards of five to ten minutes on my
machine). An unavoidable side effect of slow regex matching, I think,
although one could argue that Gnus should simply bail on attempting to
match anything with a To header over a certain length.
I've considered just procmailing such messages away, as they're invariably
spam.
--
Russ Allbery (rra@stanford.edu) <URL:http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~1998-01-12 22:44 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
1998-01-12 22:34 ` Lars Magne Ingebrigtsen
1998-01-12 22:44 ` Russ Allbery [this message]
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=m3en2dia7f.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).