From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Cc: ding@gnus.org
Subject: Re: uudecode/ydecode troubles
Date: Sat, 11 Jan 2003 15:44:35 +0100 [thread overview]
Message-ID: <m31y3jpwz0.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <84vg0w4p77.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Fri, 10 Jan 2003 23:25:48 +0100")
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:
>
>> 1. uuencode doesn't give the least hint that there is uuencoded stuff in
>> the article. The uuencode section is hidden without buttons or marker
>> lines. Relevant file from nnml spool attached. uudecode is tried
>> without the user's doing, so the I-Love-You-Signature stuff can fool
>> Gnus. http://piology.org/ILOVEYOU-Signature-FAQ.html
>
> When I hit C-u g on your msg, I see no uuencoded stuff anywhere.
Wow. I used attach-file and manually changed the type to be
message/rfc822 (Gnus decided application/octet-stream).
Look as though Gnus decoded the thing without asking when I included
that file. I'm inlining the same file, read with C-x i and then
protected with regexp-replace ^ by "| ", rather than Attach File menu or
C-c RET f.
What the heck...?
I ask that all this automatic en- or decoding, binhex, uuencode, yenc
and all the other unstructured crap be totally disabled by default
unless it's MIME and has Content-Disposition: inline headers. There are
appropriate options in the Article menu when reading, no need to do any magic.
| X-From-Line: ma@dt.e-technik.uni-dortmund.de Fri Jan 10 13:32:37 2003
| Return-Path: <ma@dt.e-technik.uni-dortmund.de>
| X-Original-To: emma+testgnus@localhost.emma.line.org
| Delivered-To: emma+testgnus@localhost.emma.line.org
| Received: by merlin.emma.line.org (Postfix, from userid 500)
| id 2222E788B0; Fri, 10 Jan 2003 13:32:37 +0100 (CET)
| To: emma+testgnus@localhost.emma.line.org
| Subject: test
| From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
| Date: Fri, 10 Jan 2003 13:32:37 +0100
| X-Gnus-Mail-Source: directory:~/Mail/
| Message-ID: <m3hech2niy.fsf@merlin.emma.line.org>
| User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i586-suse-linux)
| MIME-Version: 1.0
| Content-Type: text/plain; charset=us-ascii
| Lines: 11
| Xref: merlin.emma.line.org testgnus:1
|
| begin 600 blah.txt
| %8FQA:`H`
| `
| end
|
| --
| Matthias Andree
--
Matthias Andree
next prev parent reply other threads:[~2003-01-11 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 12:44 Matthias Andree
2003-01-10 22:25 ` Kai Großjohann
2003-01-11 14:44 ` Matthias Andree [this message]
2003-01-11 21:06 ` Lars Magne Ingebrigtsen
2003-01-12 12:49 ` Matthias Andree
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=m31y3jpwz0.fsf@merlin.emma.line.org \
--to=ma@dt.e-technik.uni-dortmund.de \
--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).