From: Mark Thomas <pgh_mthomas@yahoo.com>
Subject: MIME Encoding of attachments
Date: Fri, 01 Feb 2002 14:51:23 -0500 [thread overview]
Message-ID: <wf1elk557si.fsf@svelte.home> (raw)
I regularly deal with an MTA that wraps lines that are longer than
~~120 characters. This usually isn't a problem, but sometimes when I
send an attachment as text/plain, it gets mangled.
What is the "correct" way to handle this? Should I just use
application/octet-stream as the type? Currently I set
mm-use-ultra-safe-encoding to t, which seems excessive; besides, the
doc-string for that variable says it should not be set directly.
Instead of having Gnus decide how to encode a part on its own, is
there some way I tell Gnus to use a particular encoding for a part?
Some special "encoding" tag I can add to the MML line, for example?
Cheers,
-Mark
next reply other threads:[~2002-02-01 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 19:51 Mark Thomas [this message]
2002-02-02 2:00 ` Daniel Pittman
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=wf1elk557si.fsf@svelte.home \
--to=pgh_mthomas@yahoo.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).