From: Nevin Kapur <nevin@jhu.edu>
Subject: WARNING: The attached message make Gnus eat all resources
Date: Tue, 23 Jul 2002 10:58:53 -0400 [thread overview]
Message-ID: <m3ptxe8pjr.fsf@fermat.mts.jhu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
The attached message will make Gnus eat all resources for a *long*
time -- I C-g'd after about a minute. Debug on quit suggests
something to do with flow-fill and filladapt in turn.
On an unrelated note, when I tried to forward the message with C-c
C-f, it stripped out the Content-Type header which made the bug go
away.
-Nevin
[-- Attachment #2: Type: message/rfc822, Size: 2750 bytes --]
From: John Pettitt <jpp@cloudview.com>
Subject: Re: [Admin/Spamassasin] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0 and 4.2.1
Date: Mon, 22 Jul 2002 20:35:30 -0700
Message-ID: <5.1.0.14.2.20020722203245.00b5a868@gatekeeper.cloudview.com>
>Will people on this list please refrain from putting other people's
>mail on Razor? It's *not* helpful when important announcements end
>up in the bit bucket, to be found when the bucket's owner gets
>around to empty it.
Which translates as - if you want to stop people from seeing security
advisories submit them to razor. Perhaps would be better to configure
spam filters to ignore bugtraq so as to avoid this kind of attack.
John Pettitt Email: jpp@cloudview.com
"Do what you feel in your heart to be right for you'll be criticized anyway."
-
Eleanor Roosevelt
[-- Attachment #3: Type: text/plain, Size: 10 bytes --]
-Nevin
next reply other threads:[~2002-07-23 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 14:58 Nevin Kapur [this message]
2002-07-23 17:57 ` Reiner Steib
2002-07-23 18:10 ` Josh Huber
2002-07-23 20:11 ` Harry Putnam
2002-07-24 7:40 ` Niklas Morberg
2002-07-26 12:53 ` Simon Josefsson
2002-07-26 15:40 ` Nevin Kapur
2002-07-26 16:39 ` Simon Josefsson
2002-07-28 14:47 ` Nevin Kapur
2002-12-30 17:19 ` Lars Magne Ingebrigtsen
2002-12-30 17:17 ` Lars Magne Ingebrigtsen
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=m3ptxe8pjr.fsf@fermat.mts.jhu.edu \
--to=nevin@jhu.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).