From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: 0.99 bug: gnus encodes text/plain in base64 when attachments are present
Date: 03 Dec 1999 22:05:28 +0300 [thread overview]
Message-ID: <m3903brgjr.fsf@vvv.vsu.ru> (raw)
Hi,
in pgnus 0.99, according to ChangeLog, mm-body-charset-encoding-alist
was defaulted to nil. Previously, it contained a record that
text/plain parts in koi8-r should be sent using 8bit CTE.
Now, in 0.99, a single-part messages in koi8-r are sent usint 8bit
CTE, but as long as the message contains some attachment (say, a zip
file), the text/plain part is also encoded in base64.
Is this a feature or a bug? Should i set
mm-body-charset-encoding-alist manually to force gnus always use 8bit
CTE for koi8-r?
Best regards, -- Vladimir.
reply other threads:[~1999-12-03 19:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3903brgjr.fsf@vvv.vsu.ru \
--to=vvv@vvv.vsu.ru \
/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).