From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: multipart uuencoded articles are not all marked read
Date: 25 Apr 2000 09:43:51 -0400 [thread overview]
Message-ID: <vxkk8hm70tk.fsf@mesquite.charcoal.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "21 Apr 2000 15:24:48 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> What would be a commonly-carried group that still features uuencoded
> multipart messages?
I happened to uncover it in a mail group. It's easy enough to get a
few test messages sent to yourself by uuencoding a small .gif and then
using split(1) to get (say) 50-line pieces to mail to yourself.
I wonder whether this is an unintended side effect of having
gnus-uu-unmark-articles-not-decoded set to t.
prev parent reply other threads:[~2000-04-25 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-12 15:27 Karl Kleinpaste
2000-04-21 13:24 ` Lars Magne Ingebrigtsen
2000-04-25 13:43 ` Karl Kleinpaste [this message]
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=vxkk8hm70tk.fsf@mesquite.charcoal.com \
--to=karl@charcoal.com \
/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).