From: Roman Belenov <roman@nstl.nnov.ru>
Cc: ding@gnus.org
Subject: Re: Problem with MIME in From:/Reply-To: fields
Date: 08 Aug 2000 18:55:30 +0400 [thread overview]
Message-ID: <u66pbssyl.fsf@nstl.nnov.ru> (raw)
In-Reply-To: ShengHuo ZHU's message of "08 Aug 2000 10:03:26 -0400"
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> Oops. I was using the external decoder of base64.el.
>
> (setq base64-decoder-program "mmencode"
> base64-decoder-switches '("-u"))
>
> So, there is also a bug in the base64 lisp decorder.
Ok, it worked (although version of mmencode I've found didn't do
padding and lost last character in my example - I had to add it
myself). But it takes much more time to enter mailbox with external
base64 decoder; I'll try to fix base64.el (although I don't sure I can
- my elisp is still not good).
--
With regards, Roman.
next prev parent reply other threads:[~2000-08-08 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-07 11:37 Roman Belenov
2000-08-08 4:10 ` ShengHuo ZHU
2000-08-08 11:07 ` Roman Belenov
2000-08-08 14:03 ` ShengHuo ZHU
2000-08-08 14:55 ` Roman Belenov [this message]
2000-08-09 13:33 ` François Pinard
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=u66pbssyl.fsf@nstl.nnov.ru \
--to=roman@nstl.nnov.ru \
--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).