From: jidanni@jidanni.org
To: ding@gnus.org
Subject: Character of Death locks one out of all newsgroups
Date: Sat, 27 Dec 2008 05:25:01 +0800 [thread overview]
Message-ID: <87bpuytys2.fsf@jidanni.org> (raw)
One bad character locks me out of all newsgroups... until when, one
doesn't know. Great denial of service attack.
Debugger entered--Lisp error: (error "Can't rfc2047-encode `\x2563d\x2587c \x256cf\x7ecf'")
signal(error ("Can't rfc2047-encode `\x2563d\x2587c \x256cf\x7ecf'"))
error("Can't rfc2047-encode `%s'" "\x2563d\x2587c \x256cf\x7ecf")
rfc2047-encode(5 10)
rfc2047-encode-region(1 12)
nnrss-mime-encode-string("Re: \x2563d\x2587c亲\x256cf经历 3")
nnrss-check-group("BDSM \x25322\x25cf0\x25d37\x268a2" "")
nnrss-request-group("BDSM 一般討論" "" nil)
gnus-activate-group("nnrss:BDSM 一般討論" scan)
gnus-get-unread-articles(nil)
gnus-group-get-new-news()
Input was http://www.bdsm.com.tw/phorum/rss.php?1
If you can't rfc2047-encode something, then put a "bad character
character" in its place.
Firefox shows the line as
Re: 我的亲身经历 3
That would be still better that bombing out too.
Anyway, I had to use
C-k runs the command gnus-group-kill-group
to be able to use
g runs the command gnus-group-get-new-news
ever again. Else one must use many
M-g (translated from <escape> g) runs the command gnus-group-get-new-news-this-group
If I dare use
c runs the command gnus-group-catchup-current
I just get
Debugger entered--Lisp error: (error "Can't rfc2047-encode `\x2563d\x2587c \x256cf\x7ecf'")
signal(error ("Can't rfc2047-encode `\x2563d\x2587c \x256cf\x7ecf'"))
error("Can't rfc2047-encode `%s'" "\x2563d\x2587c \x256cf\x7ecf")
rfc2047-encode(5 10)
rfc2047-encode-region(1 12)
nnrss-mime-encode-string("Re: \x2563d\x2587c亲\x256cf经历 3")
nnrss-check-group("BDSM \x25322\x25cf0\x25d37\x268a2" "")
nnrss-request-group("BDSM 一般討論" "" nil)
gnus-activate-group("nnrss:BDSM 一般討論")
gnus-sequence-of-unread-articles("nnrss:BDSM 一般討論")
gnus-group-catchup("nnrss:BDSM 一般討論" nil)
gnus-group-catchup-current(nil)
call-interactively(gnus-group-catchup-current)
Who knows why it must encode things just to mark them as read.
I wonder how I ever can read this group again?
next reply other threads:[~2008-12-26 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 21:25 jidanni [this message]
2008-12-29 22:05 ` jidanni
2009-01-01 19:57 ` Reiner Steib
2009-01-02 21:11 ` jidanni
2009-01-05 4:18 ` Katsumi Yamaoka
2009-01-05 8:00 ` Katsumi Yamaoka
2009-01-05 17:48 ` jidanni
2009-01-05 22:10 ` Katsumi Yamaoka
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=87bpuytys2.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=ding@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).